Add body.storage type
diff --git a/2004/04/13/jca-resource-adapter-coming-along-nicely.xml b/2004/04/13/jca-resource-adapter-coming-along-nicely.xml
index 0737ea8..ae47d17 100644
--- a/2004/04/13/jca-resource-adapter-coming-along-nicely.xml
+++ b/2004/04/13/jca-resource-adapter-coming-along-nicely.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>Hiram has been working hard lately getting the JCA Resource adapter working for ActiveMQ. Take a look at the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/apidocs/org/activemq/ra/package-summary.html" rel="nofollow">ra package</a> for more details.</p></div>
+<p>Hiram has been working hard lately getting the JCA Resource adapter working for ActiveMQ. Take a look at the <a shape="rect" href="http://activemq.codehaus.org/maven/apidocs/org/activemq/ra/package-summary.html">ra package</a> for more details.</p></div>
diff --git a/2004/04/13/jxta-support-available.xml b/2004/04/13/jxta-support-available.xml
index bd7576e..cf89faf 100644
--- a/2004/04/13/jxta-support-available.xml
+++ b/2004/04/13/jxta-support-available.xml
@@ -1,7 +1,7 @@
<div class="wiki-content maincontent">
-<p>I've just committed support for JXTA based transports. Its very early days and not yet tested but it allows the reuse of JXTA for NAT / firewall based navigation using <a shape="rect" class="external-link" href="http://p2psockets.jxta.org/" rel="nofollow">p2psockets</a>.</p>
+<p>I've just committed support for JXTA based transports. Its very early days and not yet tested but it allows the reuse of JXTA for NAT / firewall based navigation using <a shape="rect" href="http://p2psockets.jxta.org/">p2psockets</a>.</p>
<p>In addition we've now got SocketFactory and ServerSocketFactory based factories for TransportChannel / TransportServerChannel including a default implementation using SSL.</p></div>
diff --git a/2004/05/26/restful-jms-web-streaming-and-streamlet-demo-available.xml b/2004/05/26/restful-jms-web-streaming-and-streamlet-demo-available.xml
index 29dcb93..463d48b 100644
--- a/2004/05/26/restful-jms-web-streaming-and-streamlet-demo-available.xml
+++ b/2004/05/26/restful-jms-web-streaming-and-streamlet-demo-available.xml
@@ -1,11 +1,11 @@
<div class="wiki-content maincontent">
-<p><a shape="rect" class="external-link" href="http://activemq.codehaus.org" rel="nofollow">ActiveMQ</a> now supports a <a shape="rect" href="../../../rest.xml">RESTful API</a> to the message broker allowing any web capable device to publish and consume messages.</p>
+<p><a shape="rect" href="http://activemq.codehaus.org">ActiveMQ</a> now supports a <link><page ri:content-title="REST"></page><link-body>RESTful API</link-body></link> to the message broker allowing any web capable device to publish and consume messages.</p>
-<p>We also support <a shape="rect" href="../../../ajax.xml">Ajax</a> which are a JavaScript mechanism, working with the REST API to provide publish/subscribe based web applications, using the full power of a MOM from inside any web browser.</p>
+<p>We also support <link><page ri:content-title="Ajax"></page></link> which are a JavaScript mechanism, working with the REST API to provide publish/subscribe based web applications, using the full power of a MOM from inside any web browser.</p>
-<p>We've now <a shape="rect" href="../../../web-samples.xml">2 demos of using Streamlets</a> in CVS now (a real time stock portfolio and a chat application) along with a simple HTML forms only demo. </p>
+<p>We've now <link><page ri:content-title="Web Samples"></page><link-body>2 demos of using Streamlets</link-body></link> in CVS now (a real time stock portfolio and a chat application) along with a simple HTML forms only demo. </p>
<p>Unfortunately right now there's a bug in the IE JavaScript when using Streamlets so things don't work yet on IE but things work fine on Firefox, Mozilla and Safari. We should have the IE issue fixed real soon.</p></div>
diff --git a/2004/06/23/jgroups-and-jrms-support.xml b/2004/06/23/jgroups-and-jrms-support.xml
index 020d393..9273b1f 100644
--- a/2004/06/23/jgroups-and-jrms-support.xml
+++ b/2004/06/23/jgroups-and-jrms-support.xml
@@ -1,7 +1,7 @@
<div class="wiki-content maincontent">
-<p>For users who want reliable multicast support when messaging, ActiveMQ now supports both <a shape="rect" class="external-link" href="http://www.jgroups.org/" rel="nofollow">JGroups</a> and <a shape="rect" class="external-link" href="http://www.experimentalstuff.com/Technologies/JRMS/" rel="nofollow">JRMS</a> as pluggable <a shape="rect" href="../../../uri-protocols.xml">transport protocols</a>.</p>
+<p>For users who want reliable multicast support when messaging, ActiveMQ now supports both <a shape="rect" href="http://www.jgroups.org/">JGroups</a> and <a shape="rect" href="http://www.experimentalstuff.com/Technologies/JRMS/">JRMS</a> as pluggable <link><page ri:content-title="URI Protocols"></page><link-body>transport protocols</link-body></link>.</p>
<p>Code is available in CVS and the latest snapshot jar.</p></div>
diff --git a/2004/06/25/building-cluster-based-applications-with-activemq.xml b/2004/06/25/building-cluster-based-applications-with-activemq.xml
index 16602a7..1044cf9 100644
--- a/2004/06/25/building-cluster-based-applications-with-activemq.xml
+++ b/2004/06/25/building-cluster-based-applications-with-activemq.xml
@@ -1,7 +1,7 @@
<div class="wiki-content maincontent">
-<p>There's a new lightweight library available called <a shape="rect" class="external-link" href="http://activecluster.codehaus.org/" rel="nofollow">ActiveCluster</a> which provides a simple cluster abstraction on top of some of the core APIs in JMS. This API allows you to monitor nodes in a cluster, watch them come & go or update their state - or send and receive messages, direct to a member of the cluster or as the group as a whole. For more details on the API see this <a shape="rect" class="external-link" href="http://activecluster.codehaus.org/Overview" rel="nofollow">overview</a>.</p>
+<p>There's a new lightweight library available called <a shape="rect" href="http://activecluster.codehaus.org/">ActiveCluster</a> which provides a simple cluster abstraction on top of some of the core APIs in JMS. This API allows you to monitor nodes in a cluster, watch them come & go or update their state - or send and receive messages, direct to a member of the cluster or as the group as a whole. For more details on the API see this <a shape="rect" href="http://activecluster.codehaus.org/Overview">overview</a>.</p>
-<p>ActiveCluster can sit neatly on top of ActiveMQ to provide a lightweight, scalable and partitionable cluster communication fabric. See the <a shape="rect" class="external-link" href="http://activecluster.codehaus.org/Examples?refresh=1" rel="nofollow">examples</a> as a quick way to get started.</p></div>
+<p>ActiveCluster can sit neatly on top of ActiveMQ to provide a lightweight, scalable and partitionable cluster communication fabric. See the <a shape="rect" href="http://activecluster.codehaus.org/Examples?refresh=1">examples</a> as a quick way to get started.</p></div>
diff --git a/2004/08/17/new-faq-entries-on-distributed-queues-and-fast-producers.xml b/2004/08/17/new-faq-entries-on-distributed-queues-and-fast-producers.xml
index 420eed3..9767edc 100644
--- a/2004/08/17/new-faq-entries-on-distributed-queues-and-fast-producers.xml
+++ b/2004/08/17/new-faq-entries-on-distributed-queues-and-fast-producers.xml
@@ -1,10 +1,10 @@
<div class="wiki-content maincontent">
-<p>We did some harvesting of questions on the <a shape="rect" class="external-link" href="http://servlet.uwyn.com/drone/log/hausbot/activemq" rel="nofollow">IRC log</a> and have added a few new entries to the <a shape="rect" href="../../../faq.xml">FAQ</a></p>
+<p>We did some harvesting of questions on the <a shape="rect" href="http://servlet.uwyn.com/drone/log/hausbot/activemq">IRC log</a> and have added a few new entries to the <link><page ri:content-title="FAQ"></page></link></p>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.codehaus.org/How+do+distributed+queues+work?refresh=1" rel="nofollow">How do distributed queues work</a></li><li><a shape="rect" class="external-link" href="http://activemq.codehaus.org/What+happens+with+a+fast+producer+and+slow+consumer?refresh=1" rel="nofollow">What happens with a fast producer and slow consumer</a></li></ul>
+<ul><li><a shape="rect" href="http://activemq.codehaus.org/How+do+distributed+queues+work?refresh=1">How do distributed queues work</a></li><li><a shape="rect" href="http://activemq.codehaus.org/What+happens+with+a+fast+producer+and+slow+consumer?refresh=1">What happens with a fast producer and slow consumer</a></li></ul>
-<p>If you can think of any other questions please mail us on one of the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/mail-lists.html" rel="nofollow">mailing lists</a> or join us on </p><p><a shape="rect" class="external-link" href="irc://irc.codehaus.org/activemq" rel="nofollow">IRC</a></p> or post a comment to this blog.<p></p></div>
+<p>If you can think of any other questions please mail us on one of the <a shape="rect" href="http://activemq.codehaus.org/maven/mail-lists.html">mailing lists</a> or join us on </p><p><structured-macro ac:macro-id="64b65670-1e24-47a2-a09f-37ecc1f3b01d" ac:name="link" ac:schema-version="1"><parameter ac:name="">IRC</parameter><parameter ac:name="text">IRC</parameter><parameter ac:name="url">irc://irc.codehaus.org/activemq</parameter></structured-macro></p> or post a comment to this blog.<p></p></div>
diff --git a/2004/08/23/using-activemq-on-net.xml b/2004/08/23/using-activemq-on-net.xml
index 10708d0..3e1d586 100644
--- a/2004/08/23/using-activemq-on-net.xml
+++ b/2004/08/23/using-activemq-on-net.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p><a shape="rect" class="external-link" href="http://dotnetjunkies.com/WebLog/csteen/" rel="nofollow">Christopher Steen</a> describes <a shape="rect" class="external-link" href="http://dotnetjunkies.com/WebLog/csteen/archive/2004/08/20/22813.aspx" rel="nofollow">how to use</a> <a shape="rect" class="external-link" href="http://activemq.codehaus.org/" rel="nofollow">ActiveMQ</a> from .Net / in C# using <a shape="rect" class="external-link" href="http://www.ikvm.net/" rel="nofollow">IKVM</a>. Neat!</p></div>
+<p><a shape="rect" href="http://dotnetjunkies.com/WebLog/csteen/">Christopher Steen</a> describes <a shape="rect" href="http://dotnetjunkies.com/WebLog/csteen/archive/2004/08/20/22813.aspx">how to use</a> <a shape="rect" href="http://activemq.codehaus.org/">ActiveMQ</a> from .Net / in C# using <a shape="rect" href="http://www.ikvm.net/">IKVM</a>. Neat!</p></div>
diff --git a/2004/10/07/activemq-11-released-with-distributed-queues-and-topics-support.xml b/2004/10/07/activemq-11-released-with-distributed-queues-and-topics-support.xml
index ed59366..2fb414d 100644
--- a/2004/10/07/activemq-11-released-with-distributed-queues-and-topics-support.xml
+++ b/2004/10/07/activemq-11-released-with-distributed-queues-and-topics-support.xml
@@ -1,12 +1,12 @@
<div class="wiki-content maincontent">
-<p>I'm very pleased to announce the new 1.1 release of ActiveMQ. You can download it from the <a shape="rect" href="../../../download.xml">usual place</a></p>
+<p>I'm very pleased to announce the new 1.1 release of ActiveMQ. You can download it from the <link><page ri:content-title="Download"></page><link-body>usual place</link-body></link></p>
<p>This release represents a major increase in functionality; the new features in this release are:-</p>
<ul><li>distributed queues and topics and clusters of message brokers</li><li>auto-reconnection of clients across a cluster of brokers</li><li>support for high performance non-durable queues</li><li>wildcard support on queues (as well as topics)</li><li>transaction log and JDBC persistence in addition to JDBM and BDB</li><li>JNDI support for easy integration</li><li>HTTP tunnelling support</li><li>auto-broker discovery using Zeroconf (Apple Rendezvous) for a peer based network using high performance pointcast</li><li>composite destinations support (allowing a publish or subscribe operation on several queues and/or topics in one atomic operation, such as writing to N queues in one operation)</li><li>simpler pure-Java configuration API</li><li>heaps of bug fixes and new test cases</li></ul>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=10632" rel="nofollow">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=10632">release notes</a></p></div>
diff --git a/2004/11/02/activemq-and-hermes-startup-movie.xml b/2004/11/02/activemq-and-hermes-startup-movie.xml
index b0c782c..e56809f 100644
--- a/2004/11/02/activemq-and-hermes-startup-movie.xml
+++ b/2004/11/02/activemq-and-hermes-startup-movie.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>Mark Bucayan has kindly submitted a <a shape="rect" class="external-link" href="http://activemq.codehaus.org/HermesAndActiveMQ.html" rel="nofollow">Flash demo</a> showing how to use ActiveMQ inside Hermes. Great stuff!</p></div>
+<p>Mark Bucayan has kindly submitted a <a shape="rect" href="http://activemq.codehaus.org/HermesAndActiveMQ.html">Flash demo</a> showing how to use ActiveMQ inside Hermes. Great stuff!</p></div>
diff --git a/2004/12/20/activemq-15-released.xml b/2004/12/20/activemq-15-released.xml
index 140ec68..257a876 100644
--- a/2004/12/20/activemq-15-released.xml
+++ b/2004/12/20/activemq-15-released.xml
@@ -1,7 +1,7 @@
<div class="wiki-content maincontent">
-<p>The new <a shape="rect" href="../../../activemq-15-release.xml">1.5</a> release is out, hot on the heels of <a shape="rect" href="../../../activemq-14-release.xml">1.4</a> and <a shape="rect" href="../../../activemq-13-release.xml">1.3</a>. Get it while its hot! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>The new <link><page ri:content-title="ActiveMQ 1.5 Release"></page><link-body>1.5</link-body></link> release is out, hot on the heels of <link><page ri:content-title="ActiveMQ 1.4 Release"></page><link-body>1.4</link-body></link> and <link><page ri:content-title="ActiveMQ 1.3 Release"></page><link-body>1.3</link-body></link>. Get it while its hot! <emoticon ac:name="smile"></emoticon></p>
<p>We now have integrated support for Geronimo, Spring and now JBoss 4 (thanks for all the hard work Michael!). We should just drop into any other J2EE 1.4 container, thanks to JCA 1.5...</p></div>
diff --git a/2005/02/03/activemq-20-released.xml b/2005/02/03/activemq-20-released.xml
index 5e60c6b..4e2a539 100644
--- a/2005/02/03/activemq-20-released.xml
+++ b/2005/02/03/activemq-20-released.xml
@@ -1,6 +1,6 @@
<div class="wiki-content maincontent">
-<p>We're proud to announce the new <a shape="rect" href="../../../activemq-20-release.xml">ActiveMQ 2.0 Release</a>. This is a major release including lots of new functionality and performance improvements. A more detailed list of changes is <a shape="rect" class="external-link" href="http://jira.codehaus.org/secure/BrowseProject.jspa?id=10520&report=changelog" rel="nofollow">here</a>.</p>
+<p>We're proud to announce the new <link><page ri:content-title="ActiveMQ 2.0 Release"></page></link>. This is a major release including lots of new functionality and performance improvements. A more detailed list of changes is <a shape="rect" href="http://jira.codehaus.org/secure/BrowseProject.jspa?id=10520&report=changelog">here</a>.</p>
<p>This release includes</p>
diff --git a/2005/02/25/activemq-21-released-with-high-performance-journalling.xml b/2005/02/25/activemq-21-released-with-high-performance-journalling.xml
index 67f85b3..e6f462d 100644
--- a/2005/02/25/activemq-21-released-with-high-performance-journalling.xml
+++ b/2005/02/25/activemq-21-released-with-high-performance-journalling.xml
@@ -1,10 +1,10 @@
<div class="wiki-content maincontent">
-<p>The new <a shape="rect" href="../../../activemq-21-release.xml">ActiveMQ 2.1 Release</a> is out which includes full support for the high performance journal. </p>
+<p>The new <link><page ri:content-title="ActiveMQ 2.1 Release"></page></link> is out which includes full support for the high performance journal. </p>
<p>Our default persistence mechanism is now the journal for short term persistence and then JDBC (via Apache Derby by default) for long term storage. The journal is regularly checkpointed with the database which gives great high performance while still providing good resiliancy (messages are on disk, not in RAM like some other providers do).</p>
<p>This new release also includes a number of performance enhancements in both durable and non durable messaging as well as a number of bug fixes.</p>
-<p>You can get the release from the usual <a shape="rect" href="../../../download.xml">Download</a> page.</p></div>
+<p>You can get the release from the usual <link><page ri:content-title="Download"></page></link> page.</p></div>
diff --git a/2005/04/11/activemq-30-released.xml b/2005/04/11/activemq-30-released.xml
index 74d0448..4488b5d 100644
--- a/2005/04/11/activemq-30-released.xml
+++ b/2005/04/11/activemq-30-released.xml
@@ -1,9 +1,9 @@
<div class="wiki-content maincontent">
-<p>We're pleased to announce the <a shape="rect" href="../../../download.xml">3.0 release</a> of ActiveMQ. Alot of tuning, testing and fixes have been incorporated into this release. A few notable new features are</p>
+<p>We're pleased to announce the <link><page ri:content-title="Download"></page><link-body>3.0 release</link-body></link> of ActiveMQ. Alot of tuning, testing and fixes have been incorporated into this release. A few notable new features are</p>
-<ul><li>a new 'discovery' transport <a shape="rect" href="../../../uri-protocols.xml">protocol</a> for a pure client-only peer network - a self discovering cluster which automatically finds the brokers available on the network (as opposed to the 'peer' protocol which is a complete peer based JMS network).</li><li>migrated from the org.activemq to org.activemq package name hierarchy</li><li>improved support for more JDBC databases for persistence</li><li>an optimised wire protocol (which is unfortunately not compatible with 2.x)</li></ul>
+<ul><li>a new 'discovery' transport <link><page ri:content-title="URI Protocols"></page><link-body>protocol</link-body></link> for a pure client-only peer network - a self discovering cluster which automatically finds the brokers available on the network (as opposed to the 'peer' protocol which is a complete peer based JMS network).</li><li>migrated from the org.activemq to org.activemq package name hierarchy</li><li>improved support for more JDBC databases for persistence</li><li>an optimised wire protocol (which is unfortunately not compatible with 2.x)</li></ul>
-<p>For more details please see the <a shape="rect" href="../../../activemq-30-release.xml">release notes</a></p></div>
+<p>For more details please see the <link><page ri:content-title="ActiveMQ 3.0 Release"></page><link-body>release notes</link-body></link></p></div>
diff --git a/2005/06/06/using-activemq-with-the-spring-jmstemplate.xml b/2005/06/06/using-activemq-with-the-spring-jmstemplate.xml
index 12e05ac..03090b2 100644
--- a/2005/06/06/using-activemq-with-the-spring-jmstemplate.xml
+++ b/2005/06/06/using-activemq-with-the-spring-jmstemplate.xml
@@ -1,17 +1,16 @@
<div class="wiki-content maincontent">
<p>Spring supports a useful JMS abstraction called JmsTemplate which makes sending and consuming messages a little simpler than using the JMS APIs directly. The only downside of this abstraction is that each send() will create a connection, session, producer, send the message, then close them all down. This is a really inefficient operation with most JMS providers as each create of a connection, session, producer ends up being an RPC with the broker, if nothing else, for security reasons.</p>
-<p>In 3.1-M2 or later of ActiveMQ there's a <a shape="rect" href="../../../spring-support.xml">simple solution</a> using the org.activemq.pool.PooledConnectionFactory which will perform pooling of JMS resources (connection, session, producer) to make sending messages efficiently. The same thing is true if you wanna use a similar pattern to the JmsTemplate to send messages from inside EJBs.</p>
+<p>In 3.1-M2 or later of ActiveMQ there's a <link><page ri:content-title="Spring Support"></page><link-body>simple solution</link-body></link> using the org.activemq.pool.PooledConnectionFactory which will perform pooling of JMS resources (connection, session, producer) to make sending messages efficiently. The same thing is true if you wanna use a similar pattern to the JmsTemplate to send messages from inside EJBs.</p>
<p>Here's an example of it in use inside a Spring config file.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="7b9bb11a-30f0-4e85-aa75-6895f8975cf1" ac:name="code" ac:schema-version="1"><plain-text-body>
<!-- a pooling based JMS provider -->
- <bean id="jmsFactory" class="org.activemq.pool.PooledConnectionFactory">
- <property name="connectionFactory">
- <bean class="org.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL">
+ <bean id="jmsFactory" class="org.activemq.pool.PooledConnectionFactory">
+ <property name="connectionFactory">
+ <bean class="org.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL">
<value>tcp://localhost:61616</value>
</property>
</bean>
@@ -19,11 +18,10 @@
</bean>
<!-- Spring JMS Template -->
- <bean id="myJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
- <property name="connectionFactory">
- <ref local="jmsFactory"/>
+ <bean id="myJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
+ <property name="connectionFactory">
+ <ref local="jmsFactory"/>
</property>
</bean>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/2005/07/04/javaone-jug-slides-available-for-activemq-and-servicemix.xml b/2005/07/04/javaone-jug-slides-available-for-activemq-and-servicemix.xml
index 32b8cd3..16659a7 100644
--- a/2005/07/04/javaone-jug-slides-available-for-activemq-and-servicemix.xml
+++ b/2005/07/04/javaone-jug-slides-available-for-activemq-and-servicemix.xml
@@ -1,5 +1,6 @@
<div class="wiki-content maincontent">
-<p>We had a great JUG at JavaOne with plenty of beer and a few slides <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"> It was a fairly brief presentation, giving an overview of <a shape="rect" class="external-link" href="http://activemq.org/" rel="nofollow">ActiveMQ</a> and <a shape="rect" class="external-link" href="http://servicemix.org/" rel="nofollow">ServiceMix</a>. Thanks to all those who attended!</p>
+<p>We had a great JUG at JavaOne with plenty of beer and a few slides <emoticon ac:name="smile"></emoticon> It was a fairly brief presentation, giving an overview of <a shape="rect" href="http://activemq.org/">ActiveMQ</a> and <a shape="rect" href="http://servicemix.org/">ServiceMix</a>. Thanks to all those who attended!</p>
-<p>You can browse the slides <a shape="rect" class="external-link" href="http://servicemix.org/docs/JUG-06.28.05.ppt" rel="nofollow">PPT</a> or <a shape="rect" class="external-link" href="http://servicemix.org/docs/JUG-06.28.05.pdf" rel="nofollow">PDF</a></p></div>
+<p>You can browse the slides <a shape="rect" href="http://servicemix.org/docs/JUG-06.28.05.ppt">PPT</a> or <a shape="rect" href="http://servicemix.org/docs/JUG-06.28.05.pdf">PDF</a></p>
+</div>
diff --git a/2005/07/13/hermes-jms-messagestores-are-cool.xml b/2005/07/13/hermes-jms-messagestores-are-cool.xml
index d4e0fc2..1880c14 100644
--- a/2005/07/13/hermes-jms-messagestores-are-cool.xml
+++ b/2005/07/13/hermes-jms-messagestores-are-cool.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent">
-<p>Here is a <a shape="rect" class="external-link" href="http://hermesjms.com/demos/messagestores.html" rel="nofollow">great demo</a> of how useful the <a shape="rect" class="external-link" href="http://hermesjms.com" rel="nofollow">HermesJms</a> tool can be when working with a JMS provider like <a shape="rect" class="external-link" href="http://activemq.org" rel="nofollow">ActiveMQ</a>. Nice work Colin!</p></div>
+<p>Here is a <a shape="rect" href="http://hermesjms.com/demos/messagestores.html">great demo</a> of how useful the <a shape="rect" href="http://hermesjms.com">HermesJms</a> tool can be when working with a JMS provider like <a shape="rect" href="http://activemq.org">ActiveMQ</a>. Nice work Colin!</p></div>
diff --git a/2005/07/13/simpler-integration-of-the-activemq-broker-into-spring.xml b/2005/07/13/simpler-integration-of-the-activemq-broker-into-spring.xml
index 802ab44..349302d 100644
--- a/2005/07/13/simpler-integration-of-the-activemq-broker-into-spring.xml
+++ b/2005/07/13/simpler-integration-of-the-activemq-broker-into-spring.xml
@@ -1,14 +1,12 @@
<div class="wiki-content maincontent">
<p>It was often a bit harder than it might be to configure an ActiveMQ broker inside a Spring XML configuration file. We've just added a simple Spring FactoryBean to make this process much simpler...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="829c32f2-1ea0-485c-b13b-7bc52e046144" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<!-- lets deploy an embedded broker in this spring.xml -->
- <bean id="broker" class="org.activemq.spring.BrokerFactoryBean">
- <property name="config" value="classpath:foo/bar/broker.xml"/>
+ <bean id="broker" class="org.activemq.spring.BrokerFactoryBean">
+ <property name="config" value="classpath:foo/bar/broker.xml"/>
</bean>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>See <a shape="rect" href="../../../how-do-i-embed-a-broker-inside-a-connection.xml">more detail</a> or try the <a shape="rect" href="../../../spring-support.xml">Spring Support</a></p></div>
+<p>See <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><link-body>more detail</link-body></link> or try the <link><page ri:content-title="Spring Support"></page></link></p></div>
diff --git a/2005/07/15/great-blog-post-on-message-driven-pojos.xml b/2005/07/15/great-blog-post-on-message-driven-pojos.xml
index bc9d365..3b4a72a 100644
--- a/2005/07/15/great-blog-post-on-message-driven-pojos.xml
+++ b/2005/07/15/great-blog-post-on-message-driven-pojos.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p><a shape="rect" class="external-link" href="http://jroller.com/page/habuma/" rel="nofollow">Craig</a> has a great post on <a shape="rect" class="external-link" href="http://jroller.com/page/habuma/20050715#message_driven_pojos" rel="nofollow">message driven POJOs</a>. If you can make it to the <a shape="rect" class="external-link" href="http://www.nofluffjuststuff.com/show_view.jsp?showId=33" rel="nofollow">LoneStar Software Symposium</a> to see Craig's talk it sounds well worth attending. CoolBeans!</p>
+<p><a shape="rect" href="http://jroller.com/page/habuma/">Craig</a> has a great post on <a shape="rect" href="http://jroller.com/page/habuma/20050715#message_driven_pojos">message driven POJOs</a>. If you can make it to the <a shape="rect" href="http://www.nofluffjuststuff.com/show_view.jsp?showId=33">LoneStar Software Symposium</a> to see Craig's talk it sounds well worth attending. CoolBeans!</p>
-<p>Also of interest is a new <a shape="rect" class="external-link" href="http://confluence.atlassian.com/display/JIRAEXT/JMS+Service" rel="nofollow">JIRA plugin for JMS and ActiveMQ</a> - thanks for the heads up <a shape="rect" class="external-link" href="http://blogs.atlassian.com/rebelutionary/" rel="nofollow">Mike</a></p></div>
+<p>Also of interest is a new <a shape="rect" href="http://confluence.atlassian.com/display/JIRAEXT/JMS+Service">JIRA plugin for JMS and ActiveMQ</a> - thanks for the heads up <a shape="rect" href="http://blogs.atlassian.com/rebelutionary/">Mike</a></p></div>
diff --git a/2005/08/25/activemq-31-released-with-ruby-and-perl-support.xml b/2005/08/25/activemq-31-released-with-ruby-and-perl-support.xml
index 89a7402..9308802 100644
--- a/2005/08/25/activemq-31-released-with-ruby-and-perl-support.xml
+++ b/2005/08/25/activemq-31-released-with-ruby-and-perl-support.xml
@@ -1,9 +1,9 @@
<div class="wiki-content maincontent">
-<p>The long awaited <a shape="rect" href="../../../activemq-31-release.xml">ActiveMQ 3.1 Release</a> is finally out. Who-hoo! Many thanks to all those on the <a shape="rect" href="../../../team.xml">Team</a> who've helped.</p>
+<p>The long awaited <link><page ri:content-title="ActiveMQ 3.1 Release"></page></link> is finally out. Who-hoo! Many thanks to all those on the <link><page ri:content-title="Team"></page></link> who've helped.</p>
-<p>This release includes support for Ruby and Perl thanks to the <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> project together with <a shape="rect" href="../../../activemq-31-release.xml">heaps of new features</a> such as better persistence, journalling and integration with JNDI, JCA, Servlets, Spring, WebLogic and JBoss. </p>
+<p>This release includes support for Ruby and Perl thanks to the <a shape="rect" href="http://stomp.codehaus.org/">Stomp</a> project together with <link><page ri:content-title="ActiveMQ 3.1 Release"></page><link-body>heaps of new features</link-body></link> such as better persistence, journalling and integration with JNDI, JCA, Servlets, Spring, WebLogic and JBoss. </p>
-<p>Go on, <a shape="rect" href="../../../download.xml">Download</a> it today!</p>
+<p>Go on, <link><page ri:content-title="Download"></page></link> it today!</p>
<p>Enjoy!</p></div>
diff --git a/2005/09/14/activemq-integrates-with-openrico-ajax-library.xml b/2005/09/14/activemq-integrates-with-openrico-ajax-library.xml
index 100badb..486b0ef 100644
--- a/2005/09/14/activemq-integrates-with-openrico-ajax-library.xml
+++ b/2005/09/14/activemq-integrates-with-openrico-ajax-library.xml
@@ -1,7 +1,7 @@
<div class="wiki-content maincontent">
-<p>We've now migrated our real time portfolio <a shape="rect" href="../../../ajax.xml">Ajax</a> demo to use the <a shape="rect" class="external-link" href="http://openrico.org/" rel="nofollow">OpenRico</a> library. Cool Beans!</p>
+<p>We've now migrated our real time portfolio <link><page ri:content-title="Ajax"></page></link> demo to use the <a shape="rect" href="http://openrico.org/">OpenRico</a> library. Cool Beans!</p>
<p>This means you can now use an off the self Ajax library such as Rico for the browser side, then use ActiveMQ as the message broker on the server side for handling your scalable asynchronous messaging.</p>
-<p>I'm sure we're only scratching the surface of the <a shape="rect" href="../../../ajax.xml">Ajax</a> possibilities as we start to integrate asynchronous messaging and real time eventing into web applications.</p></div>
+<p>I'm sure we're only scratching the surface of the <link><page ri:content-title="Ajax"></page></link> possibilities as we start to integrate asynchronous messaging and real time eventing into web applications.</p></div>
diff --git a/2005/10/11/activemq-adds-xbean-support-for-custom-spring-xml-processing.xml b/2005/10/11/activemq-adds-xbean-support-for-custom-spring-xml-processing.xml
index ba47148..9749ebf 100644
--- a/2005/10/11/activemq-adds-xbean-support-for-custom-spring-xml-processing.xml
+++ b/2005/10/11/activemq-adds-xbean-support-for-custom-spring-xml-processing.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>Craig has a <a shape="rect" class="external-link" href="http://jroller.com/page/habuma/20051011" rel="nofollow">great post</a> which describes how XBean can really help provide a <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/XB/Custom+XML" rel="nofollow">customized XML language</a> with Spring XML configuration extensibility. We're really happy with it so far and have moved away from XSLT and custom DOM processing to the simpler XBean model in ActiveMQ and <a shape="rect" class="external-link" href="http://jencks.org" rel="nofollow">Jencks</a> with <a shape="rect" class="external-link" href="http://servicemix.org" rel="nofollow">ServiceMix</a> to follow suit real soon now.</p>
+<p>Craig has a <a shape="rect" href="http://jroller.com/page/habuma/20051011">great post</a> which describes how XBean can really help provide a <a shape="rect" href="http://docs.codehaus.org/display/XB/Custom+XML">customized XML language</a> with Spring XML configuration extensibility. We're really happy with it so far and have moved away from XSLT and custom DOM processing to the simpler XBean model in ActiveMQ and <a shape="rect" href="http://jencks.org">Jencks</a> with <a shape="rect" href="http://servicemix.org">ServiceMix</a> to follow suit real soon now.</p>
-<p>Whats cool is we've just about got a working XBean Ant task to auto-generate the configuration, the XSD and HTML documentaiton now. e.g. here's the <a shape="rect" class="external-link" href="http://codehaus.org/~jstrachan/servicemix.xsd.html" rel="nofollow">current</a> ServiceMix generated documentation.</p></div>
+<p>Whats cool is we've just about got a working XBean Ant task to auto-generate the configuration, the XSD and HTML documentaiton now. e.g. here's the <a shape="rect" href="http://codehaus.org/~jstrachan/servicemix.xsd.html">current</a> ServiceMix generated documentation.</p></div>
diff --git a/2005/10/26/activemq-32-released-with-stomp-10-and-improved-ajax.xml b/2005/10/26/activemq-32-released-with-stomp-10-and-improved-ajax.xml
index 88ec4de..ae3f2a8 100644
--- a/2005/10/26/activemq-32-released-with-stomp-10-and-improved-ajax.xml
+++ b/2005/10/26/activemq-32-released-with-stomp-10-and-improved-ajax.xml
@@ -1,8 +1,8 @@
<div class="wiki-content maincontent">
<p>This new release includes the following</p>
-<ul><li>Improved <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> 1.0 support to make it easy to create cross language clients such as for C, C#, Python, Ruby, Perl and Pike.</li><li>Ajax support now uses OpenRico as the default Ajax library</li><li>the Resource Adaptor now supports batching</li><li>demand based store and forward in networks</li><li>support for Informix JDBC</li><li>updated DTD for the latest Spring</li><li>various performance enhancements and bug fixes</li></ul>
+<ul><li>Improved <a shape="rect" href="http://stomp.codehaus.org/">Stomp</a> 1.0 support to make it easy to create cross language clients such as for C, C#, Python, Ruby, Perl and Pike.</li><li>Ajax support now uses OpenRico as the default Ajax library</li><li>the Resource Adaptor now supports batching</li><li>demand based store and forward in networks</li><li>support for Informix JDBC</li><li>updated DTD for the latest Spring</li><li>various performance enhancements and bug fixes</li></ul>
-<p>For more details please see the <a shape="rect" href="../../../activemq-32-release.xml">Release Notes</a></p></div>
+<p>For more details please see the <link><page ri:content-title="ActiveMQ 3.2 Release"></page><link-body>Release Notes</link-body></link></p></div>
diff --git a/2005/11/09/new-features-in-40-exclusive-consumers-and-message-groups.xml b/2005/11/09/new-features-in-40-exclusive-consumers-and-message-groups.xml
index b921235..bc3b26e 100644
--- a/2005/11/09/new-features-in-40-exclusive-consumers-and-message-groups.xml
+++ b/2005/11/09/new-features-in-40-exclusive-consumers-and-message-groups.xml
@@ -1,8 +1,8 @@
<div class="wiki-content maincontent">
-<p>We've documented some of the new features coming along in <a shape="rect" href="../../../changes-in-40.xml">the 4.x branch of ActiveMQ</a>. In particular the things I'm particularly happy about are</p>
+<p>We've documented some of the new features coming along in <link><page ri:content-title="Changes in 4.0"></page><link-body>the 4.x branch of ActiveMQ</link-body></link>. In particular the things I'm particularly happy about are</p>
-<ul><li><a shape="rect" href="../../../exclusive-consumer.xml">Exclusive Consumer</a></li><li><a shape="rect" href="../../../message-groups.xml">Message Groups</a></li></ul>
+<ul><li><link><page ri:content-title="Exclusive Consumer"></page></link></li><li><link><page ri:content-title="Message Groups"></page></link></li></ul>
-<p>I really love <a shape="rect" href="../../../message-groups.xml">Message Groups</a>, they totally rock! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"> Its well worth reading the overview of what they are and how they can be useful making a partitioned high performance grid style distributed system with ordering or fast caching etc.</p></div>
+<p>I really love <link><page ri:content-title="Message Groups"></page></link>, they totally rock! <emoticon ac:name="smile"></emoticon> Its well worth reading the overview of what they are and how they can be useful making a partitioned high performance grid style distributed system with ordering or fast caching etc.</p></div>
diff --git a/2005/11/23/new-discussion-forum-available.xml b/2005/11/23/new-discussion-forum-available.xml
index 3effae1..148b778 100644
--- a/2005/11/23/new-discussion-forum-available.xml
+++ b/2005/11/23/new-discussion-forum-available.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent">
-<p>Various users don't like joining busy email lists - we all get enough email as it is <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"> - so we've setup a <a shape="rect" class="external-link" href="http://forums.logicblaze.com/forums/show/1.page" rel="nofollow">discussion forum</a> you can use as an alternative to the mail lists. Enjoy!</p></div>
+<p>Various users don't like joining busy email lists - we all get enough email as it is <emoticon ac:name="smile"></emoticon> - so we've setup a <a shape="rect" href="http://forums.logicblaze.com/forums/show/1.page">discussion forum</a> you can use as an alternative to the mail lists. Enjoy!</p></div>
diff --git a/2005/12/09/activemq-4x-codebase-has-moved-to-apache.xml b/2005/12/09/activemq-4x-codebase-has-moved-to-apache.xml
index 78d26ac..546be04 100644
--- a/2005/12/09/activemq-4x-codebase-has-moved-to-apache.xml
+++ b/2005/12/09/activemq-4x-codebase-has-moved-to-apache.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
<p>You can surf it at <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/incubator/activemq/">https://svn.apache.org/repos/asf/incubator/activemq/</a>.</p>
-<p>For more details see <a shape="rect" href="../../../source.xml">Source</a>.</p></div>
+<p>For more details see <link><page ri:content-title="Source"></page></link>.</p></div>
diff --git a/2006/03/23/new-discussion-forums-available-at-nabble.xml b/2006/03/23/new-discussion-forums-available-at-nabble.xml
index e91e60a..fd5c615 100644
--- a/2006/03/23/new-discussion-forums-available-at-nabble.xml
+++ b/2006/03/23/new-discussion-forums-available-at-nabble.xml
@@ -1,14 +1,3 @@
<div class="wiki-content maincontent">
-Before posting you might want to read the <a shape="rect" href="../../../tips-for-getting-help.xml">Tips for getting help</a>.
-
-<p>Many users prefer to use online forums rather than joining a mail list which can lead to lots more email traffic so we use the online forums at <a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/" rel="nofollow">Nabble forums</a> which also work with our <a shape="rect" href="../../../mailing-lists.xml">Mailing Lists</a> so that both stay completely in sync. Use either the mailing lists or online forums, its completely up to you.</p>
-
-<h3 id="NewDiscussionForumsAvailableatNabble-ActiveMQForums"><a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/" rel="nofollow">ActiveMQ Forums</a></h3>
-
-<ul><li><a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html" rel="nofollow">ActiveMQ User Forum</a></li><li><a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html" rel="nofollow">ActiveMQ Developer Forum</a></li></ul>
-
-
-<h3 id="NewDiscussionForumsAvailableatNabble-MailingLists">Mailing Lists</h3>
-
-<p>If you prefer to use a mailing list instead then check out our <a shape="rect" href="../../../mailing-lists.xml">Mailing Lists</a>. Note that the Forums and <a shape="rect" href="../../../mailing-lists.xml">Mailing Lists</a> are kept in sync so its your choice which you use.</p></div>
+<structured-macro ac:macro-id="ece36784-c0df-42dd-9196-629185ecbe7e" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Discussion Forums"></page></link></parameter></structured-macro></div>
diff --git a/2006/06/16/performance-tuning-guide-available.xml b/2006/06/16/performance-tuning-guide-available.xml
index 708c8b1..281ec51 100644
--- a/2006/06/16/performance-tuning-guide-available.xml
+++ b/2006/06/16/performance-tuning-guide-available.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>We've created a <a shape="rect" class="external-link" href="http://devzone.logicblaze.com/site/apache-activemq-performance-tuning-guide.html" rel="nofollow">performance tuning guide</a> which takes you through the various different configurations and quality of service settings you can use to help tune your use of Apache ActiveMQ. Enjoy!</p></div>
+<div class="wiki-content maincontent"><p>We've created a <a shape="rect" href="http://devzone.logicblaze.com/site/apache-activemq-performance-tuning-guide.html">performance tuning guide</a> which takes you through the various different configurations and quality of service settings you can use to help tune your use of Apache ActiveMQ. Enjoy!</p></div>
diff --git a/2006/11/17/apache-activemq-402-released.xml b/2006/11/17/apache-activemq-402-released.xml
index 17f7331..e2030e8 100644
--- a/2006/11/17/apache-activemq-402-released.xml
+++ b/2006/11/17/apache-activemq-402-released.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>We are pleased to announce the release of <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/activemq-402-release.html">Apache ActiveMQ 4.0.2</a> please grab it while its hot!</p>
+<div class="wiki-content maincontent"><p>We are pleased to announce the release of <a shape="rect" href="http://incubator.apache.org/activemq/activemq-402-release.html">Apache ActiveMQ 4.0.2</a> please grab it while its hot!</p>
<p>This is primarily a bug fix release; we recommend all users of Apache ActiveMQ 4.x or later to upgrade. Enjoy!</p></div>
diff --git a/2007-april.xml b/2007-april.xml
index d9f0d5d..18af662 100644
--- a/2007-april.xml
+++ b/2007-april.xml
@@ -1,4 +1,5 @@
-<div class="wiki-content maincontent"><h2 id="id-2007April-April2007Report">April 2007 Report</h2>
+<div class="wiki-content maincontent"><h2>April 2007 Report</h2>
-<ul><li><a shape="rect" class="unresolved" href="#">ActiveMQ 4.1.1 Released</a></li><li>voted in a new committer, John Heitmann</li><li>the developer and user lists continue to be very active</li></ul></div>
+<ul><li><link><page ri:content-title="ActiveMQ 4.1.1 Released"></page></link></li><li>voted in a new committer, John Heitmann</li><li>the developer and user lists continue to be very active</li></ul>
+</div>
diff --git a/2007/01/19/activemq-410-released.xml b/2007/01/19/activemq-410-released.xml
index b517a6d..a98524c 100644
--- a/2007/01/19/activemq-410-released.xml
+++ b/2007/01/19/activemq-410-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Grab it while its hot! Download <a shape="rect" href="../../../activemq-410-release.xml">ActiveMQ 4.1.0 Release</a> now!</p></div>
+<div class="wiki-content maincontent"><p>Grab it while its hot! Download <link><page ri:content-title="ActiveMQ 4.1.0 Release"></page></link> now!</p></div>
diff --git a/2007/03/02/using-rails-and-activemq-with-activemessaging.xml b/2007/03/02/using-rails-and-activemq-with-activemessaging.xml
index a4828ec..08997bb 100644
--- a/2007/03/02/using-rails-and-activemq-with-activemessaging.xml
+++ b/2007/03/02/using-rails-and-activemq-with-activemessaging.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Andrew Kuklewicz just published a great article, <a shape="rect" class="external-link" href="http://www.infoq.com/articles/intro-active-messaging-rails" rel="nofollow">an introduction to ActiveMessaging, using Rails with ActiveMQ and Stomp</a> over on <a shape="rect" class="external-link" href="http://www.infoq.com" rel="nofollow">InfoQ</a>. Cool beans! </p></div>
+<div class="wiki-content maincontent"><p>Andrew Kuklewicz just published a great article, <a shape="rect" href="http://www.infoq.com/articles/intro-active-messaging-rails">an introduction to ActiveMessaging, using Rails with ActiveMQ and Stomp</a> over on <a shape="rect" href="http://www.infoq.com">InfoQ</a>. Cool beans! </p></div>
diff --git a/2007/03/09/java-c-c-csharp-vb-perl-python-php-ruby-pike-and-now-smalltalk.xml b/2007/03/09/java-c-c-csharp-vb-perl-python-php-ruby-pike-and-now-smalltalk.xml
index 0ceeb2e..b973274 100644
--- a/2007/03/09/java-c-c-csharp-vb-perl-python-php-ruby-pike-and-now-smalltalk.xml
+++ b/2007/03/09/java-c-c-csharp-vb-perl-python-php-ruby-pike-and-now-smalltalk.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>We've always had lots of support for <a shape="rect" href="../../../cross-language-clients.xml">Cross Language Clients and Protocols</a> but now there is a <a shape="rect" class="external-link" href="http://stomp.codehaus.org/Smalltalk" rel="nofollow">Smalltalk client</a> <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p></div>
+<div class="wiki-content maincontent"><p>We've always had lots of support for <link><page ri:content-title="Cross Language Clients"></page><link-body>Cross Language Clients and Protocols</link-body></link> but now there is a <a shape="rect" href="http://stomp.codehaus.org/Smalltalk">Smalltalk client</a> <emoticon ac:name="smile"></emoticon></p></div>
diff --git a/2007/03/28/nms-support-in-springnet-available-for-download.xml b/2007/03/28/nms-support-in-springnet-available-for-download.xml
index c1d1414..28b66a7 100644
--- a/2007/03/28/nms-support-in-springnet-available-for-download.xml
+++ b/2007/03/28/nms-support-in-springnet-available-for-download.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/">Apache NMS</a> is an API for messaging on the .Net platform in C# or VB.Net. Spring.Net offers several features to make it easier to work with .Net like the Spring Framework does for Java. Now the Spring.Messaging.Net library can be used to make it easier to work with NMS. For example it includes the NmsTemplate class (like the JmsTemplate class in Java) or the DefaultMessageListenerContainer.</p>
+<div class="wiki-content maincontent"><p><a shape="rect" href="http://activemq.apache.org/nms/">Apache NMS</a> is an API for messaging on the .Net platform in C# or VB.Net. Spring.Net offers several features to make it easier to work with .Net like the Spring Framework does for Java. Now the Spring.Messaging.Net library can be used to make it easier to work with NMS. For example it includes the NmsTemplate class (like the JmsTemplate class in Java) or the DefaultMessageListenerContainer.</p>
-<p>There is now a <a shape="rect" class="external-link" href="http://www.springframework.net/downloads/Spring.Messaging.Nms/" rel="nofollow">binary download of Spring.Messaging.NMS available</a>. Get it while its hot!</p></div>
+<p>There is now a <a shape="rect" href="http://www.springframework.net/downloads/Spring.Messaging.Nms/">binary download of Spring.Messaging.NMS available</a>. Get it while its hot!</p></div>
diff --git a/2007/04/03/activemq-feathercast-available.xml b/2007/04/03/activemq-feathercast-available.xml
index 40e3581..ebb5647 100644
--- a/2007/04/03/activemq-feathercast-available.xml
+++ b/2007/04/03/activemq-feathercast-available.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>James Strachan was interviewed for this months <a shape="rect" class="external-link" href="http://feathercast.org/?p=42" rel="nofollow">feathercast</a> discussing all things Apache ActiveMQ.</p></div>
+<div class="wiki-content maincontent"><p>James Strachan was interviewed for this months <a shape="rect" href="http://feathercast.org/?p=42">feathercast</a> discussing all things Apache ActiveMQ.</p></div>
diff --git a/2007/04/03/apache-activemq-411-released.xml b/2007/04/03/apache-activemq-411-released.xml
index 75b9466..dcba5b3 100644
--- a/2007/04/03/apache-activemq-411-released.xml
+++ b/2007/04/03/apache-activemq-411-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>We're proud to announce the <a shape="rect" href="../../../activemq-411-release.xml">ActiveMQ 4.1.1 Release</a> has just gone out with numberous bug fixes. Grab it while its hot!</p></div>
+<div class="wiki-content maincontent"><p>We're proud to announce the <link><page ri:content-title="ActiveMQ 4.1.1 Release"></page></link> has just gone out with numberous bug fixes. Grab it while its hot!</p></div>
diff --git a/2007/04/18/how-can-i-send-a-message-to-multiple-destinations-using-a-messageproducer.xml b/2007/04/18/how-can-i-send-a-message-to-multiple-destinations-using-a-messageproducer.xml
index e7e30d6..cb0863d 100644
--- a/2007/04/18/how-can-i-send-a-message-to-multiple-destinations-using-a-messageproducer.xml
+++ b/2007/04/18/how-can-i-send-a-message-to-multiple-destinations-using-a-messageproducer.xml
@@ -1,10 +1,8 @@
<div class="wiki-content maincontent"><p>How can I send a message to multiple Destinations using a MessageProducer? The trick is to pass null in for the destination when you create it; then you can specify the destination on each send.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1b0481f4-3aba-4bc2-a3a0-2ddac58514b0" ac:name="code" ac:schema-version="1"><plain-text-body>
MessageProducer producer = session.createProducer(null);
...
producer.send(destination, message);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/2007/06/08/integrating-activemq-web-console.xml b/2007/06/08/integrating-activemq-web-console.xml
index f051661..c1d3499 100644
--- a/2007/06/08/integrating-activemq-web-console.xml
+++ b/2007/06/08/integrating-activemq-web-console.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>There's an itneresting article on <a shape="rect" class="external-link" href="http://www.oreillynet.com/onjava/blog/2007/06/integrating_activemq_web_conso.html" rel="nofollow">Integrating ActiveMQ Web Console</a> by <a shape="rect" class="external-link" href="http://www.oreillynet.com/pub/au/1763" rel="nofollow">Dejan Bosanac</a> which is well worth a read. The next version of ActiveMQ, 5.0, will include the Web Console by default which should simplify things somewhat.</p></div>
+<div class="wiki-content maincontent"><p>There's an itneresting article on <a shape="rect" href="http://www.oreillynet.com/onjava/blog/2007/06/integrating_activemq_web_conso.html">Integrating ActiveMQ Web Console</a> by <a shape="rect" href="http://www.oreillynet.com/pub/au/1763">Dejan Bosanac</a> which is well worth a read. The next version of ActiveMQ, 5.0, will include the Web Console by default which should simplify things somewhat.</p></div>
diff --git a/2007/06/27/more-articles-on-apache-activemq-activemessaging-and-rails.xml b/2007/06/27/more-articles-on-apache-activemq-activemessaging-and-rails.xml
index acad14d..3cfe103 100644
--- a/2007/06/27/more-articles-on-apache-activemq-activemessaging-and-rails.xml
+++ b/2007/06/27/more-articles-on-apache-activemq-activemessaging-and-rails.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><p>There's been more interesting <a shape="rect" href="../../../articles.xml">Articles</a> lately on <a shape="rect" href="../../../index.xml">Apache ActiveMQ</a>, [ActiveMessaging and rails...</p>
+<div class="wiki-content maincontent"><p>There's been more interesting <link><page ri:content-title="Articles"></page></link> lately on <link><page ri:content-title="Index"></page><link-body>Apache ActiveMQ</link-body></link>, [ActiveMessaging and rails...</p>
-<ul><li><a shape="rect" class="external-link" href="http://notdennisbyrne.blogspot.com/2007/06/integrating-rails-and-activemq-with.html" rel="nofollow">Integrating Rails and ActiveMQ with ActiveMessaging/REST</a> by <a shape="rect" class="external-link" href="http://notdennisbyrne.blogspot.com/" rel="nofollow">(not) Dennis Byrne</a></li><li><a shape="rect" class="external-link" href="http://beechbonanza.blogspot.com/2007/06/asynchronous-messaging-with-rails.html" rel="nofollow">Asynchronous Messaging with Rails</a> by <a shape="rect" class="external-link" href="http://beechbonanza.blogspot.com/" rel="nofollow">Shane Harvie</a></li></ul>
+<ul><li><a shape="rect" href="http://notdennisbyrne.blogspot.com/2007/06/integrating-rails-and-activemq-with.html">Integrating Rails and ActiveMQ with ActiveMessaging/REST</a> by <a shape="rect" href="http://notdennisbyrne.blogspot.com/">(not) Dennis Byrne</a></li><li><a shape="rect" href="http://beechbonanza.blogspot.com/2007/06/asynchronous-messaging-with-rails.html">Asynchronous Messaging with Rails</a> by <a shape="rect" href="http://beechbonanza.blogspot.com/">Shane Harvie</a></li></ul>
<p>Check them out, they're both great.</p></div>
diff --git a/2007/12/15/apache-activemq-500-released.xml b/2007/12/15/apache-activemq-500-released.xml
index d17e0da..07661b8 100644
--- a/2007/12/15/apache-activemq-500-released.xml
+++ b/2007/12/15/apache-activemq-500-released.xml
@@ -1,7 +1,7 @@
-<div class="wiki-content maincontent"><p>I'm pleased to announce the Apache <a shape="rect" href="../../../activemq-500-release.xml">ActiveMQ 5.0.0 Release</a> has been made! Its packed with <a shape="rect" href="../../../new-features-in-50.xml">a ton of new features</a> such as:</p>
+<div class="wiki-content maincontent"><p>I'm pleased to announce the Apache <link><page ri:content-title="ActiveMQ 5.0.0 Release"></page></link> has been made! Its packed with <link><page ri:content-title="New Features in 5.0"></page><link-body>a ton of new features</link-body></link> such as:</p>
-<ul><li><a shape="rect" href="../../../amq-message-store.xml">AMQ Message Store</a> (Faster Persistence!)</li><li><a shape="rect" href="../../../message-cursors.xml">Message Cursors</a> (Producers don't block if you have a slow consumer)</li><li><a shape="rect" href="../../../blob-messages.xml">Blob Messages</a></li><li><a shape="rect" href="../../../command-agent.xml">Command Agent</a></li><li><a shape="rect" href="../../../enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> via <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Camel Integration</a></li><li><a shape="rect" href="../../../logging-a-warning-if-you-forget-to-start-a-connection.xml">Logging a warning if you forget to start a Connection</a></li><li><a shape="rect" href="../../../message-transformation.xml">Message Transformation</a></li><li><a shape="rect" href="../../../mirrored-queues.xml">Mirrored Queues</a></li><li><a shape="rect" href="../../../producer-flow-control.xml">Producer Flow Control</a></li></ul>
+<ul><li><link><page ri:content-title="AMQ Message Store"></page></link> (Faster Persistence!)</li><li><link><page ri:content-title="Message Cursors"></page></link> (Producers don't block if you have a slow consumer)</li><li><link><page ri:content-title="Blob Messages"></page></link></li><li><link><page ri:content-title="Command Agent"></page></link></li><li><link><page ri:content-title="Enterprise Integration Patterns"></page></link> via <a shape="rect" href="http://activemq.apache.org/camel/">Camel Integration</a></li><li><link><page ri:content-title="Logging a warning if you forget to start a Connection"></page></link></li><li><link><page ri:content-title="Message Transformation"></page></link></li><li><link><page ri:content-title="Mirrored Queues"></page></link></li><li><link><page ri:content-title="Producer Flow Control"></page></link></li></ul>
-<p><a shape="rect" href="../../../activemq-500-release.xml">Download it</a> today!</p></div>
+<p><link><page ri:content-title="ActiveMQ 5.0.0 Release"></page><link-body>Download it</link-body></link> today!</p></div>
diff --git a/2008/04/28/javaone-meetup-2008.xml b/2008/04/28/javaone-meetup-2008.xml
index 763c8b8..1ab857e 100644
--- a/2008/04/28/javaone-meetup-2008.xml
+++ b/2008/04/28/javaone-meetup-2008.xml
@@ -1,11 +1,11 @@
-<div class="wiki-content maincontent"><h1 id="JavaOneMeetup2008-JavaOneMeetup2008">JavaOne Meetup 2008 </h1>
+<div class="wiki-content maincontent"><h1>JavaOne Meetup 2008 </h1>
-<h2 id="JavaOneMeetup2008-ComemeetwiththefolksbehindApacheActiveMQ,Camel,CXFandServiceMixatJavaOne!">Come meet with the folks behind Apache ActiveMQ, Camel, CXF and ServiceMix at JavaOne! </h2>
+<h2>Come meet with the folks behind Apache ActiveMQ, Camel, CXF and ServiceMix at JavaOne! </h2>
-<div class="sectionColumnWrapper"><div class="sectionMacro">
-<div class="sectionMacroRow"><div class="columnMacro">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="javaone-meetup-2008.data/javaone-logo.gif" data-image-src="/confluence/download/attachments/84434/javaone-logo.gif?version=1&modificationDate=1209384762000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59672124" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="javaone-logo.gif" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/gif" data-linked-resource-container-id="84434" data-linked-resource-container-version="5"></span></p></div>
-<div class="columnMacro">
-<p>Please join us for an evening of food, drinks, conversation and open source antics at the <a shape="rect" class="external-link" href="http://www.zebulonsf.com/" rel="nofollow">Zebulon Cafe</a> - (<a shape="rect" class="external-link" href="http://maps.google.com/maps?f=q&hl=en&geocode=&q=83+Natoma+St,+San+Francisco,+CA&sll=37.787187,-122.399256&sspn=0.003705,0.003868&ie=UTF8&ll=37.785266,-122.401578&spn=0.014822,0.015471&t=h&z=16" rel="nofollow">Google Map</a>) in San Francisco on Monday, May 5, 2008 from 6-9PM. Some of the Apache committers behind these dynamic projects that will be there include Dan Kulp, Hiram Chirino, Guillaume Nodet, Rob Davies, Chris Custine and Bruce Snyder. ActiveMQ and Camel are each readying the next releases, CXF just graduated from the Incubator and the shiny, new ServiceMix 4.0 release is right around the corner. A big thanks to <a shape="rect" class="external-link" href="http://open.iona.com/" rel="nofollow">IONA Technologies</a> for sponsoring this event. We hope to see you there! </p></div></div></div></div>
-<p>In an attempt to help predict the head count, please <a shape="rect" class="external-link" href="http://tinyurl.com/3jmztl" rel="nofollow"><strong>add your name to the registration page</strong></a>. </p></div>
+<structured-macro ac:macro-id="6f2a684d-1242-465f-a1be-7bae4c02e8e3" ac:name="section" ac:schema-version="1"><rich-text-body>
+<structured-macro ac:macro-id="d37d7aa0-da35-4496-a655-3768daafc5c9" ac:name="column" ac:schema-version="1"><rich-text-body>
+<p><image><attachment ri:filename="javaone-logo.gif"></attachment></image></p></rich-text-body></structured-macro>
+<structured-macro ac:macro-id="861a23e3-45cf-414d-8f48-7170fdd7be94" ac:name="column" ac:schema-version="1"><rich-text-body>
+<p>Please join us for an evening of food, drinks, conversation and open source antics at the <a shape="rect" href="http://www.zebulonsf.com/">Zebulon Cafe</a> - (<a shape="rect" href="http://maps.google.com/maps?f=q&hl=en&geocode=&q=83+Natoma+St,+San+Francisco,+CA&sll=37.787187,-122.399256&sspn=0.003705,0.003868&ie=UTF8&ll=37.785266,-122.401578&spn=0.014822,0.015471&t=h&z=16">Google Map</a>) in San Francisco on Monday, May 5, 2008 from 6-9PM. Some of the Apache committers behind these dynamic projects that will be there include Dan Kulp, Hiram Chirino, Guillaume Nodet, Rob Davies, Chris Custine and Bruce Snyder. ActiveMQ and Camel are each readying the next releases, CXF just graduated from the Incubator and the shiny, new ServiceMix 4.0 release is right around the corner. A big thanks to <a shape="rect" href="http://open.iona.com/">IONA Technologies</a> for sponsoring this event. We hope to see you there! </p></rich-text-body></structured-macro></rich-text-body></structured-macro>
+<p>In an attempt to help predict the head count, please <a shape="rect" href="http://tinyurl.com/3jmztl"><strong>add your name to the registration page</strong></a>. </p></div>
diff --git a/2008/05/07/activemq-510-released.xml b/2008/05/07/activemq-510-released.xml
index 2a607a7..60a6546 100644
--- a/2008/05/07/activemq-510-released.xml
+++ b/2008/05/07/activemq-510-released.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-510-release.html">ActiveMQ 5.1.0 Release</a>. <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-510-release.html">ActiveMQ 5.1.0</a> is a much more stable message broker than 5.0.0 and we highly encourage all the 5.0.0 users to upgrade to this release.</p>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce the <a shape="rect" href="http://activemq.apache.org/activemq-510-release.html">ActiveMQ 5.1.0 Release</a>. <a shape="rect" href="http://activemq.apache.org/activemq-510-release.html">ActiveMQ 5.1.0</a> is a much more stable message broker than 5.0.0 and we highly encourage all the 5.0.0 users to upgrade to this release.</p>
-<p>For more details on the fixed issues see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11802&styleName=Html&projectId=10520&Create=Create">release notes</a>.</p></div>
+<p>For more details on the fixed issues see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11802&styleName=Html&projectId=10520&Create=Create">release notes</a>.</p></div>
diff --git a/2008/11/21/apache-activemq-520-released.xml b/2008/11/21/apache-activemq-520-released.xml
index 02ec3ef..e89725a 100644
--- a/2008/11/21/apache-activemq-520-released.xml
+++ b/2008/11/21/apache-activemq-520-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.2.0. Full details of the release and download links can be found in the <a shape="rect" href="../../../activemq-520-release.xml">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.2.0. Full details of the release and download links can be found in the <link><page ri:content-title="ActiveMQ 5.2.0 Release"></page><link-body>release page</link-body></link>.</p></div>
diff --git a/2009/01/12/activemq-in-action-free-chapters-available.xml b/2009/01/12/activemq-in-action-free-chapters-available.xml
index 84be6e4..86ae3d0 100644
--- a/2009/01/12/activemq-in-action-free-chapters-available.xml
+++ b/2009/01/12/activemq-in-action-free-chapters-available.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p><span class="confluence-embedded-file-wrapper image-right-wrapper"><img class="confluence-embedded-image confluence-external-resource image-right" src="http://www.manning.com/snyder/snyder_cover150.jpg" data-image-src="http://www.manning.com/snyder/snyder_cover150.jpg"></span></p>
+<div class="wiki-content maincontent"><p><image ac:align="right"><url ri:value="http://www.manning.com/snyder/snyder_cover150.jpg"></url></image></p>
<p><em>ActiveMQ in Action</em> is a thorough, practical guide to implementing message-oriented systems in Java using ActiveMQ. The book lays out the core of ActiveMQ in clear language, starting with the anatomy of a JMS message and moving quickly through connectors, message persistence, authentication and authorization. With the basics well in hand, you move into interesting examples of ActiveMQ at work, following a running Stock Portfolio application. You'll integrate ActiveMQ with containers like Geronimo and JBoss and learn to tie into popular Java-based technologies like Spring Framework.</p>
@@ -11,5 +11,5 @@
<ul><li>High-level designers of loosely-coupled distributed systems that follow a Service Oriented Architecture (SOA)</li><li>Software developers creating applications that use the ActiveMQ message broker</li><li>System administrators that must maintain a software system based on the ActiveMQ message broker</li></ul>
-<p><a shape="rect" class="external-link" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140" rel="nofollow">Grab your copy of ActiveMQ in Action now!</a> </p></div>
+<p><a shape="rect" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140">Grab your copy of ActiveMQ in Action now!</a> </p></div>
diff --git a/2009/03/10/40-off-of-activemq-in-action.xml b/2009/03/10/40-off-of-activemq-in-action.xml
index 4a24a97..53264eb 100644
--- a/2009/03/10/40-off-of-activemq-in-action.xml
+++ b/2009/03/10/40-off-of-activemq-in-action.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><p><span class="confluence-embedded-file-wrapper image-left-wrapper"><img class="confluence-embedded-image confluence-external-resource image-left" src="http://www.manning.com/snyder/snyder_cover150.jpg" data-image-src="http://www.manning.com/snyder/snyder_cover150.jpg"></span></p>
+<div class="wiki-content maincontent"><p><image ac:align="left"><url ri:value="http://www.manning.com/snyder/snyder_cover150.jpg"></url></image></p>
-<h3 id="id-40%OffofActiveMQinAction!-Getitwhileit'shot!">Get it while it's hot! </h3>
+<h3>Get it while it's hot! </h3>
-<p>For a limited time you can get the definitive book on ActiveMQ at a 40% discount! This discount applies to either the print+ebook or just the ebook. Though we're still hard at work on the <a shape="rect" class="external-link" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140" rel="nofollow">ActiveMQ in Action</a> book, you can download the chapters as we write them from the Manning Early Access Program today. For the 40% discount, just use the coupon code <strong>activemq40</strong> at the time of checkout. Hurry and get this discounted price while it lasts because this offer expires on Monday, 23 March 2009. </p>
+<p>For a limited time you can get the definitive book on ActiveMQ at a 40% discount! This discount applies to either the print+ebook or just the ebook. Though we're still hard at work on the <a shape="rect" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140">ActiveMQ in Action</a> book, you can download the chapters as we write them from the Manning Early Access Program today. For the 40% discount, just use the coupon code <strong>activemq40</strong> at the time of checkout. Hurry and get this discounted price while it lasts because this offer expires on Monday, 23 March 2009. </p>
-<h3 id="id-40%OffofActiveMQinAction!-IwanttopurchaseActiveMQinActiontoday!"><a shape="rect" class="external-link" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140" rel="nofollow">I want to purchase ActiveMQ in Action today!</a></h3></div>
+<h3><a shape="rect" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140">I want to purchase ActiveMQ in Action today!</a></h3></div>
diff --git a/2009/04/17/continuous-integration-server.xml b/2009/04/17/continuous-integration-server.xml
index fbd6d1b..4195321 100644
--- a/2009/04/17/continuous-integration-server.xml
+++ b/2009/04/17/continuous-integration-server.xml
@@ -1,8 +1,7 @@
-<div class="wiki-content maincontent"><p>ActiveMQ has been added to <a shape="rect" class="external-link" href="http://hudson.dev.java.net/" rel="nofollow">Hudson continuous-integration server</a> instance at Apache <a shape="rect" class="external-link" href="http://hudson.zones.apache.org/hudson/job/ActiveMQ/">http://hudson.zones.apache.org/hudson/job/ActiveMQ/</a>. Now you can have more insight into test runs and snapshot builds. Hudson will also send failure reports to our dev mailing list, making us address them promptly.<br clear="none">
+<div class="wiki-content maincontent"><p>ActiveMQ has been added to <a shape="rect" href="http://hudson.dev.java.net/">Hudson continuous-integration server</a> instance at Apache <a shape="rect" href="http://hudson.zones.apache.org/hudson/job/ActiveMQ/">http://hudson.zones.apache.org/hudson/job/ActiveMQ/</a>. Now you can have more insight into test runs and snapshot builds. Hudson will also send failure reports to our dev mailing list, making us address them promptly.<br clear="none">
As a part of this change, the snapshots location and Maven repository has changed. If you're using ActiveMQ snapshots in your projects, be sure to add the following repository to your Maven configuration:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<repositories>
+<structured-macro ac:macro-id="325943c3-a50e-4541-b3ee-d6876648c825" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><repositories>
<repository>
<id>hudson.snapshots</id>
<url>https://repository.apache.org/content/repositories/snapshots/</url>
@@ -10,6 +9,5 @@
<enabled>false</enabled>
</releases>
</repository>
-</repositories>]]></script>
-</div></div></div>
+</repositories></plain-text-body></structured-macro></div>
diff --git a/2009/08/07/activemq-reference-guide-kit-from-ttm-solutions-now-available.xml b/2009/08/07/activemq-reference-guide-kit-from-ttm-solutions-now-available.xml
index 8d6dba2..d47fbee 100644
--- a/2009/08/07/activemq-reference-guide-kit-from-ttm-solutions-now-available.xml
+++ b/2009/08/07/activemq-reference-guide-kit-from-ttm-solutions-now-available.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><h3 id="ActiveMQReferenceGuideKitfromTTMSolutionsNowAvailable-ActiveMQReferenceGuideKitfromTTMSolutionsNowAvailable">ActiveMQ Reference Guide Kit from TTM Solutions Now Available </h3>
+<div class="wiki-content maincontent"><h3>ActiveMQ Reference Guide Kit from TTM Solutions Now Available </h3>
<p>The Apache ActiveMQ Reference Guide Kit from Total Transaction Management (TTM) is an excellent programmers resource to help you implement, deploy, administer, and tune Apache ActiveMQ based systems.</p>
<p>Besides the Reference Guide, you will also receive sample applications called SecureChat and StockWatch, and a file based Security Plugin. The annual $20 subscription includes updates and enhancements throughout the year, as the Reference Guide Kit is updated to reflect Apache ActiveMQ changes and enhancements.</p>
-<p><a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php" rel="nofollow">Click here for the ActiveMQ Reference Guide Kit</a></p></div>
+<p><a shape="rect" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php">Click here for the ActiveMQ Reference Guide Kit</a></p></div>
diff --git a/2009/10/13/activemq-530-released.xml b/2009/10/13/activemq-530-released.xml
index 8b6f5f8..f659df1 100644
--- a/2009/10/13/activemq-530-released.xml
+++ b/2009/10/13/activemq-530-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.3.0. Full details of the release and download links can be found in the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-530-release.html">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.3.0. Full details of the release and download links can be found in the <a shape="rect" href="http://activemq.apache.org/activemq-530-release.html">release page</a>.</p></div>
diff --git a/2009/10/13/apache-activemq-530-has-an-official-specjms2007-result.xml b/2009/10/13/apache-activemq-530-has-an-official-specjms2007-result.xml
index 4490fd4..a92f330 100644
--- a/2009/10/13/apache-activemq-530-has-an-official-specjms2007-result.xml
+++ b/2009/10/13/apache-activemq-530-has-an-official-specjms2007-result.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>Apache ActiveMQ 5.3.0 has an official <a shape="rect" class="external-link" href="http://www.spec.org/jms2007/" rel="nofollow">SPECjms2007®</a> result, thanks to some great work by <a shape="rect" class="external-link" href="http://www.dvs.tu-darmstadt.de/staff/ksachs/" rel="nofollow">Kai Sachs</a> from the <a shape="rect" class="external-link" href="http://www.dvs.tu-darmstadt.de/" rel="nofollow">Databases and Distributed Systems Group</a> at the Technical University Darmstadt in Germany. Complete details can be found in the official results submission that is linked from the <a shape="rect" class="external-link" href="http://www.dvs.tu-darmstadt.de/news/specjms2007Results.html" rel="nofollow">announcement</a>.<br clear="none">
+<div class="wiki-content maincontent"><p>Apache ActiveMQ 5.3.0 has an official <a shape="rect" href="http://www.spec.org/jms2007/">SPECjms2007®</a> result, thanks to some great work by <a shape="rect" href="http://www.dvs.tu-darmstadt.de/staff/ksachs/">Kai Sachs</a> from the <a shape="rect" href="http://www.dvs.tu-darmstadt.de/">Databases and Distributed Systems Group</a> at the Technical University Darmstadt in Germany. Complete details can be found in the official results submission that is linked from the <a shape="rect" href="http://www.dvs.tu-darmstadt.de/news/specjms2007Results.html">announcement</a>.<br clear="none">
Needless to say, 5.3.0 does nicely in both horizontal (number of destinations) and vertical (load per destination) scalability.<br clear="none">
It is fitting to see Apache ActiveMQ being used in the world's first SPECjms2007 submission.</p></div>
diff --git a/2010/03/23/activemq-531-released.xml b/2010/03/23/activemq-531-released.xml
index 9ca3c52..096b310 100644
--- a/2010/03/23/activemq-531-released.xml
+++ b/2010/03/23/activemq-531-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.3.1. Full details of the release and download links can be found in the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-531-release.html">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.3.1. Full details of the release and download links can be found in the <a shape="rect" href="http://activemq.apache.org/activemq-531-release.html">release page</a>.</p></div>
diff --git a/2010/05/11/activemq-532-released.xml b/2010/05/11/activemq-532-released.xml
index a58d41d..c62c01e 100644
--- a/2010/05/11/activemq-532-released.xml
+++ b/2010/05/11/activemq-532-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.3.2. Full details of the release and download links can be found on the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-532-release.html">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.3.2. Full details of the release and download links can be found on the <a shape="rect" href="http://activemq.apache.org/activemq-532-release.html">release page</a>.</p></div>
diff --git a/2010/05/18/50-off-activemq-in-action.xml b/2010/05/18/50-off-activemq-in-action.xml
index 5896ce5..54373a4 100644
--- a/2010/05/18/50-off-activemq-in-action.xml
+++ b/2010/05/18/50-off-activemq-in-action.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><p><span class="confluence-embedded-file-wrapper image-left-wrapper"><img class="confluence-embedded-image confluence-external-resource image-left" src="http://www.manning.com/snyder/snyder_cover150.jpg" data-image-src="http://www.manning.com/snyder/snyder_cover150.jpg"></span> </p>
+<div class="wiki-content maincontent"><p><image ac:align="left"><url ri:value="http://www.manning.com/snyder/snyder_cover150.jpg"></url></image> </p>
-<h3 id="id-50%OffActiveMQInAction!-50%OffActiveMQInAction!">50% Off ActiveMQ In Action! </h3>
+<h3>50% Off ActiveMQ In Action! </h3>
-<p>The <a shape="rect" class="external-link" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140" rel="nofollow">ActiveMQ In Action</a> book has made available a new early access release before going into final review and copy editing. All 14 chapters are included in this MEAP release. </p>
+<p>The <a shape="rect" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140">ActiveMQ In Action</a> book has made available a new early access release before going into final review and copy editing. All 14 chapters are included in this MEAP release. </p>
<p>For a limited time you can get the definitive book on ActiveMQ at a 50% discount! Just use the coupon code <strong>activemq50</strong> at the time of checkout. Hurry and get this discounted price while it lasts because this offer expires on Monday, May 31, 2010. </p>
-<h3 id="id-50%OffActiveMQInAction!-IwanttopurchaseActiveMQinActiontoday!"><a shape="rect" class="external-link" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140" rel="nofollow">I want to purchase ActiveMQ in Action today!</a> </h3></div>
+<h3><a shape="rect" href="http://www.manning.com/affiliate/idevaffiliate.php?id=1063_140">I want to purchase ActiveMQ in Action today!</a> </h3></div>
diff --git a/2010/06/29/free-excerpt-from-activemq-in-action.xml b/2010/06/29/free-excerpt-from-activemq-in-action.xml
index 0050ebe..44eccdd 100644
--- a/2010/06/29/free-excerpt-from-activemq-in-action.xml
+++ b/2010/06/29/free-excerpt-from-activemq-in-action.xml
@@ -1,3 +1,3 @@
-<div class="wiki-content maincontent"><div class="sectionColumnWrapper"><div class="sectionMacro"><div class="sectionMacroRow"><div class="columnMacro"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://www.manning.com/snyder/snyder_cover150.jpg" data-image-src="http://www.manning.com/snyder/snyder_cover150.jpg"></span> <span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://www.manning.com/ibsen/ibsen_cover150.jpg" data-image-src="http://www.manning.com/ibsen/ibsen_cover150.jpg"></span></p></div><div class="columnMacro"><p> <a shape="rect" class="external-link" href="http://fusesource.com" rel="nofollow">FuseSource</a> is offering a free excerpt from <a shape="rect" class="external-link" href="http://manning.com/snyder" rel="nofollow">ActiveMQ in Action</a> and <a shape="rect" class="external-link" href="http://manning.com/ibsen" rel="nofollow">Camel in Action</a> books at <a shape="rect" class="external-link" href="http://fusesource.com/fuse/apache-books/" rel="nofollow">http://fusesource.com/fuse/apache-books/</a>. <br clear="none">
-Find out more on how ActiveMQ stores messages and what's the role of transactions in Camel and get your discount.</p></div></div></div></div></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="3d2a508e-ad39-4a9b-94f4-c7017a450eeb" ac:name="section" ac:schema-version="1"><rich-text-body><structured-macro ac:macro-id="9d2cd6de-f0f3-4393-9aec-a11bd1b1a104" ac:name="column" ac:schema-version="1"><rich-text-body><p><image><url ri:value="http://www.manning.com/snyder/snyder_cover150.jpg"></url></image> <image><url ri:value="http://www.manning.com/ibsen/ibsen_cover150.jpg"></url></image></p></rich-text-body></structured-macro><structured-macro ac:macro-id="d06eb367-ccf4-4718-a8bf-a4f49c9f0972" ac:name="column" ac:schema-version="1"><rich-text-body><p> <a shape="rect" href="http://fusesource.com">FuseSource</a> is offering a free excerpt from <a shape="rect" href="http://manning.com/snyder">ActiveMQ in Action</a> and <a shape="rect" href="http://manning.com/ibsen">Camel in Action</a> books at <a shape="rect" href="http://fusesource.com/fuse/apache-books/">http://fusesource.com/fuse/apache-books/</a>. <br clear="none">
+Find out more on how ActiveMQ stores messages and what's the role of transactions in Camel and get your discount.</p></rich-text-body></structured-macro></rich-text-body></structured-macro></div>
diff --git a/2010/08/17/apache-activemq-540-released.xml b/2010/08/17/apache-activemq-540-released.xml
index 68cc171..819f2bd 100644
--- a/2010/08/17/apache-activemq-540-released.xml
+++ b/2010/08/17/apache-activemq-540-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.4.0. Full details of the release and download links can be found on the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-540-release.html">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce ActiveMQ 5.4.0. Full details of the release and download links can be found on the <a shape="rect" href="http://activemq.apache.org/activemq-540-release.html">release page</a>.</p></div>
diff --git a/2010/09/03/official-activemq-540-specjms2007-result-confirms-45-60-performance-improvement.xml b/2010/09/03/official-activemq-540-specjms2007-result-confirms-45-60-performance-improvement.xml
index 2cef375..f35deec 100644
--- a/2010/09/03/official-activemq-540-specjms2007-result-confirms-45-60-performance-improvement.xml
+++ b/2010/09/03/official-activemq-540-specjms2007-result-confirms-45-60-performance-improvement.xml
@@ -1,3 +1,3 @@
-<div class="wiki-content maincontent"><p>Apache ActiveMQ 5.4.0 has an official <a shape="rect" class="external-link" href="http://www.spec.org/jms2007/" rel="nofollow">SPECjms2007®</a> result, thanks to the <a shape="rect" class="external-link" href="http://www.dvs.tu-darmstadt.de/" rel="nofollow">Databases and Distributed Systems Group</a> at the Technical University Darmstadt in Germany. Complete details can be found in the official result submissions: <a shape="rect" class="external-link" href="http://www.spec.org/jms2007/results/res2010q3/jms2007-20100802-00021.html" rel="nofollow">227 SPECjms2007@Vertical</a> and <a shape="rect" class="external-link" href="http://www.spec.org/jms2007/results/res2010q3/jms2007-20100802-00022.html" rel="nofollow">100 SPECjms2007@Horizontal</a>.<br clear="none">
+<div class="wiki-content maincontent"><p>Apache ActiveMQ 5.4.0 has an official <a shape="rect" href="http://www.spec.org/jms2007/">SPECjms2007®</a> result, thanks to the <a shape="rect" href="http://www.dvs.tu-darmstadt.de/">Databases and Distributed Systems Group</a> at the Technical University Darmstadt in Germany. Complete details can be found in the official result submissions: <a shape="rect" href="http://www.spec.org/jms2007/results/res2010q3/jms2007-20100802-00021.html">227 SPECjms2007@Vertical</a> and <a shape="rect" href="http://www.spec.org/jms2007/results/res2010q3/jms2007-20100802-00022.html">100 SPECjms2007@Horizontal</a>.<br clear="none">
If you were happy with the performance of version 5.3.0, 5.4.0 will make you smile brighter, depending on your work load it will be between 45% and 60% better.</p></div>
diff --git a/2010/09/22/apache-activemq-541-released.xml b/2010/09/22/apache-activemq-541-released.xml
index f07e001..97e8317 100644
--- a/2010/09/22/apache-activemq-541-released.xml
+++ b/2010/09/22/apache-activemq-541-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce the ActiveMQ 5.4.1 maintenance release. Full details of the release and download links can be found on the <a shape="rect" href="../../../activemq-541-release.xml">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce the ActiveMQ 5.4.1 maintenance release. Full details of the release and download links can be found on the <link><page ri:content-title="ActiveMQ 5.4.1 Release"></page><link-body>release page</link-body></link>.</p></div>
diff --git a/2010/12/02/apache-activemq-542-released.xml b/2010/12/02/apache-activemq-542-released.xml
index 03e04fc..5151152 100644
--- a/2010/12/02/apache-activemq-542-released.xml
+++ b/2010/12/02/apache-activemq-542-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce the ActiveMQ 5.4.2 maintenance release. Full details of the release and download links can be found on the <a shape="rect" href="../../../activemq-542-release.xml">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce the ActiveMQ 5.4.2 maintenance release. Full details of the release and download links can be found on the <link><page ri:content-title="ActiveMQ 5.4.2 Release"></page><link-body>release page</link-body></link>.</p></div>
diff --git a/2011/04/01/apache-activemq-550-released.xml b/2011/04/01/apache-activemq-550-released.xml
index 1775801..d08e060 100644
--- a/2011/04/01/apache-activemq-550-released.xml
+++ b/2011/04/01/apache-activemq-550-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is delighted to announce ActiveMQ 5.5.0. Full details of the release and download links can be found on the <a shape="rect" href="../../../activemq-550-release.xml">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is delighted to announce ActiveMQ 5.5.0. Full details of the release and download links can be found on the <link><page ri:content-title="ActiveMQ 5.5.0 Release"></page><link-body>release page</link-body></link>.</p></div>
diff --git a/2011/04/04/activemq-in-action-is-now-available-in-print-and-e-book.xml b/2011/04/04/activemq-in-action-is-now-available-in-print-and-e-book.xml
index 5531d4d..078cee3 100644
--- a/2011/04/04/activemq-in-action-is-now-available-in-print-and-e-book.xml
+++ b/2011/04/04/activemq-in-action-is-now-available-in-print-and-e-book.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><p><span class="confluence-embedded-file-wrapper image-left-wrapper"><img class="confluence-embedded-image confluence-external-resource image-left" src="http://www.manning.com/snyder/snyder_cover150.jpg" data-image-src="http://www.manning.com/snyder/snyder_cover150.jpg"></span> </p>
+<div class="wiki-content maincontent"><p><image ac:align="left"><url ri:value="http://www.manning.com/snyder/snyder_cover150.jpg"></url></image> </p>
-<h3 id="ActiveMQInActionisNowAvailableinPrintandE-Book!-ActiveMQInActionisNowAvailableinPrintandE-Book!">ActiveMQ In Action is Now Available in Print and E-Book! </h3>
+<h3>ActiveMQ In Action is Now Available in Print and E-Book! </h3>
-<p>The <a shape="rect" class="external-link" href="http://bit.ly/2je6cQ" rel="nofollow">ActiveMQ In Action</a> book has now been fully released in both e-book and in print – get your own copy today! </p>
+<p>The <a shape="rect" href="http://bit.ly/2je6cQ">ActiveMQ In Action</a> book has now been fully released in both e-book and in print – get your own copy today! </p>
-<p><a shape="rect" class="external-link" href="http://bit.ly/2je6cQ" rel="nofollow">ActiveMQ In Action</a>, the definitive guide to master ActiveMQ is now available in print and ebook. ActiveMQ in Action starts from the anatomy of a JMS message and moves quickly through connectors, message persistence, authentication, and authorization. By following a running example (a stock portfolio app), you’ll pick up the best practices distilled by the authors from their long and deep involvement with this technology. Every Manning Publications print book purchase includes a complimentary ebook which comes in three formats: PDF, mobi, and epub when available. </p>
+<p><a shape="rect" href="http://bit.ly/2je6cQ">ActiveMQ In Action</a>, the definitive guide to master ActiveMQ is now available in print and ebook. ActiveMQ in Action starts from the anatomy of a JMS message and moves quickly through connectors, message persistence, authentication, and authorization. By following a running example (a stock portfolio app), you’ll pick up the best practices distilled by the authors from their long and deep involvement with this technology. Every Manning Publications print book purchase includes a complimentary ebook which comes in three formats: PDF, mobi, and epub when available. </p>
-<h3 id="ActiveMQInActionisNowAvailableinPrintandE-Book!-IwanttopurchaseActiveMQinActionnow!"><a shape="rect" class="external-link" href="http://bit.ly/2je6cQ" rel="nofollow">I want to purchase ActiveMQ in Action now!</a> </h3></div>
+<h3><a shape="rect" href="http://bit.ly/2je6cQ">I want to purchase ActiveMQ in Action now!</a> </h3></div>
diff --git a/2012/04/27/activemq-cpp-version-342-released.xml b/2012/04/27/activemq-cpp-version-342-released.xml
index 3065cf4..2eb9707 100644
--- a/2012/04/27/activemq-cpp-version-342-released.xml
+++ b/2012/04/27/activemq-cpp-version-342-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/">ActiveMQ-CPP</a> is out, you can download the source bundles <a shape="rect" href="../../../cms/activemq-cpp-342-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" href="http://activemq.apache.org/cms/">ActiveMQ-CPP</a> is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.4.2 Release" ri:space-key="AMQCPP"></page><link-body>here</link-body></link>.</p></div>
diff --git a/2012/05/04/apachenmsactivemq-v155-released.xml b/2012/05/04/apachenmsactivemq-v155-released.xml
index de0ec39..bd4c5fe 100644
--- a/2012/05/04/apachenmsactivemq-v155-released.xml
+++ b/2012/05/04/apachenmsactivemq-v155-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Today marks the official release of <a shape="rect" href="../../../nms/download.xml">Apache.NMS.ActiveMQ</a> v1.5.5. We put a lot of work into this one fixing bugs that were found since the 1.5.4 release. This release features a fix for a critical issue related to connection failure. </p></div>
+<div class="wiki-content maincontent"><p>Today marks the official release of <link><page ri:content-title="Download" ri:space-key="NMS"></page><link-body>Apache.NMS.ActiveMQ</link-body></link> v1.5.5. We put a lot of work into this one fixing bugs that were found since the 1.5.4 release. This release features a fix for a critical issue related to connection failure. </p></div>
diff --git a/2012/05/07/apache-activemq-560-released.xml b/2012/05/07/apache-activemq-560-released.xml
index 71baf31..b232118 100644
--- a/2012/05/07/apache-activemq-560-released.xml
+++ b/2012/05/07/apache-activemq-560-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is delighted to announce ActiveMQ 5.6.0. Full details of the release and download links can be found on the <a shape="rect" href="../../../activemq-560-release.xml">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is delighted to announce ActiveMQ 5.6.0. Full details of the release and download links can be found on the <link><page ri:content-title="ActiveMQ 5.6.0 Release"></page><link-body>release page</link-body></link>.</p></div>
diff --git a/2012/06/02/activemq-cpp-version-343-released.xml b/2012/06/02/activemq-cpp-version-343-released.xml
index f34c136..b575784 100644
--- a/2012/06/02/activemq-cpp-version-343-released.xml
+++ b/2012/06/02/activemq-cpp-version-343-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/">ActiveMQ-CPP</a> is out, you can download the source bundles <a shape="rect" href="../../../cms/activemq-cpp-343-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" href="http://activemq.apache.org/cms/">ActiveMQ-CPP</a> is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.4.3 Release" ri:space-key="AMQCPP"></page><link-body>here</link-body></link>.</p></div>
diff --git a/2012/06/29/activemq-cpp-version-344-released.xml b/2012/06/29/activemq-cpp-version-344-released.xml
index 2f534b5..244d3c8 100644
--- a/2012/06/29/activemq-cpp-version-344-released.xml
+++ b/2012/06/29/activemq-cpp-version-344-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/">ActiveMQ-CPP</a> is out, you can download the source bundles <a shape="rect" href="../../../cms/activemq-cpp-344-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" href="http://activemq.apache.org/cms/">ActiveMQ-CPP</a> is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.4.4 Release" ri:space-key="AMQCPP"></page><link-body>here</link-body></link>.</p></div>
diff --git a/2012/10/08/apache-activemq-570-released.xml b/2012/10/08/apache-activemq-570-released.xml
index 4891c94..05fc721 100644
--- a/2012/10/08/apache-activemq-570-released.xml
+++ b/2012/10/08/apache-activemq-570-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is delighted to announce Apache ActiveMQ 5.7.0. All details of the release and download links can be found on the <a shape="rect" href="../../../activemq-570-release.xml">release page</a>.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is delighted to announce Apache ActiveMQ 5.7.0. All details of the release and download links can be found on the <link><page ri:content-title="ActiveMQ 5.7.0 Release"></page><link-body>release page</link-body></link>.</p></div>
diff --git a/2012/10/12/activemq-cpp-v345-released.xml b/2012/10/12/activemq-cpp-v345-released.xml
index 74a2ff3..5512671 100644
--- a/2012/10/12/activemq-cpp-v345-released.xml
+++ b/2012/10/12/activemq-cpp-v345-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can <a shape="rect" href="../../../cms/activemq-cpp-345-release.xml">download</a> the source bundles here.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can <link><page ri:content-title="ActiveMQ-CPP 3.4.5 Release" ri:space-key="AMQCPP"></page><link-body>download</link-body></link> the source bundles here.</p></div>
diff --git a/2012/12/21/activemq-cpp-version-350-released.xml b/2012/12/21/activemq-cpp-version-350-released.xml
index 001b439..99acc8a 100644
--- a/2012/12/21/activemq-cpp-version-350-released.xml
+++ b/2012/12/21/activemq-cpp-version-350-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../cms/activemq-cpp-350-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.5.0 Release" ri:space-key="AMQCPP"></page><link-body>here</link-body></link>.</p></div>
diff --git a/2013/02/12/apache-activemq-580-released.xml b/2013/02/12/apache-activemq-580-released.xml
index de997a2..2441f45 100644
--- a/2013/02/12/apache-activemq-580-released.xml
+++ b/2013/02/12/apache-activemq-580-released.xml
@@ -1,8 +1,8 @@
<div class="wiki-content maincontent"><p>The Apache ActiveMQ team is delighted to announce the release of Apache ActiveMQ 5.8.0.</p>
-<p>This release adds <a shape="rect" href="../../../amqp.xml">AMQP</a> support and resolves 160 issues and enhancements.</p>
+<p>This release adds <link><page ri:content-title="amqp"></page><link-body>AMQP</link-body></link> support and resolves 160 issues and enhancements.</p>
-<p>Full details and download link can be found in the <a shape="rect" href="../../../activemq-580-release.xml">release</a> page.</p>
+<p>Full details and download link can be found in the <link><page ri:content-title="activemq 5.8.0 release"></page><link-body>release</link-body></link> page.</p>
<p>A big thanks to everyone who contributed to this release.</p></div>
diff --git a/2013/06/10/apachenmsactivemq-v160-released.xml b/2013/06/10/apachenmsactivemq-v160-released.xml
index f6d15b0..18445da 100644
--- a/2013/06/10/apachenmsactivemq-v160-released.xml
+++ b/2013/06/10/apachenmsactivemq-v160-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>After almost a year we've <a shape="rect" class="external-link" href="http://activemq.apache.org/nms/apachenmsactivemq-v160.html">released v1.6.0</a> of Apache.NMS.ActiveMQ. This version offers many new features and fixes many issues that were found over the course of the last year. The release implement the Apache.NMS API v1.6.0</p></div>
+<div class="wiki-content maincontent"><p>After almost a year we've <a shape="rect" href="http://activemq.apache.org/nms/apachenmsactivemq-v160.html">released v1.6.0</a> of Apache.NMS.ActiveMQ. This version offers many new features and fixes many issues that were found over the course of the last year. The release implement the Apache.NMS API v1.6.0</p></div>
diff --git a/2013/10/21/apache-activemq-590-released.xml b/2013/10/21/apache-activemq-590-released.xml
index 33b812d..a3a702b 100644
--- a/2013/10/21/apache-activemq-590-released.xml
+++ b/2013/10/21/apache-activemq-590-released.xml
@@ -4,7 +4,7 @@
<ul><li>New hawtio web console</li><li>Replicated leveldb message store</li><li>Runtime configuration</li></ul>
-<p>Full details and download link can be found in the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-590-release.html">release page</a></p>
+<p>Full details and download link can be found in the <a shape="rect" href="http://activemq.apache.org/activemq-590-release.html">release page</a></p>
<p>A big thanks to everyone who contributed to this release.</p></div>
diff --git a/2014/06/10/apache-activemq-5100-released.xml b/2014/06/10/apache-activemq-5100-released.xml
index 431f4ed..ba721f8 100644
--- a/2014/06/10/apache-activemq-5100-released.xml
+++ b/2014/06/10/apache-activemq-5100-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(0,0,0);">The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.10.0.</span></p><p><span style="color: rgb(0,0,0);">This release addresses over 200 issues and introduces many improvements particularly in MQTT and AMQP support.</span></p><p><span style="color: rgb(0,0,0);"> </span></p><p>Full details and download link can be found in the <a shape="rect" href="../../../activemq-5100-release.xml">release page</a></p><p><span style="color: rgb(0,0,0);"> </span></p><p>A big thanks to everyone who contributed to this release.</p><p><span style="color: rgb(0,0,0);"><br clear="none"></span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(0,0,0);">The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.10.0.</span></p><p><span style="color: rgb(0,0,0);">This release addresses over 200 issues and introduces many improvements particularly in MQTT and AMQP support.</span></p><p><span style="color: rgb(0,0,0);"> </span></p><p>Full details and download link can be found in the <link><page ri:content-title="ActiveMQ 5.10.0 Release"></page><plain-text-link-body>release page</plain-text-link-body></link></p><p><span style="color: rgb(0,0,0);"> </span></p><p>A big thanks to everyone who contributed to this release.</p><p><span style="color: rgb(0,0,0);"><br clear="none"></span></p></div>
diff --git a/2015/01/22/apache-activemq-5101-released.xml b/2015/01/22/apache-activemq-5101-released.xml
index 6c7a4ba..0fd6364 100644
--- a/2015/01/22/apache-activemq-5101-released.xml
+++ b/2015/01/22/apache-activemq-5101-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.10.1.</p><p>This release addresses several issues in the 5.10.0 release.</p><p>Thank you to all of the contributors, helping to make ActiveMQ more stable.</p><p> </p><p>Please see the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5101-release.html">release page</a> for download links and more information!</p><p> </p></div>
+<div class="wiki-content maincontent"><p>The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.10.1.</p><p>This release addresses several issues in the 5.10.0 release.</p><p>Thank you to all of the contributors, helping to make ActiveMQ more stable.</p><p> </p><p>Please see the <a shape="rect" href="http://activemq.apache.org/activemq-5101-release.html">release page</a> for download links and more information!</p><p> </p></div>
diff --git a/2015/02/04/apache-activemq-5110-released.xml b/2015/02/04/apache-activemq-5110-released.xml
index 4a64c84..6536b38 100644
--- a/2015/02/04/apache-activemq-5110-released.xml
+++ b/2015/02/04/apache-activemq-5110-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is delighted to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5110-release.html">ActiveMQ 5.11.0</a></span></p><p><span style="color: rgb(34,34,34);line-height: 1.4285715;">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p><div><span style="color: rgb(34,34,34);"><br clear="none"></span></div><p><br clear="none"><span style="color: rgb(34,34,34);"> </span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is delighted to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5110-release.html">ActiveMQ 5.11.0</a></span></p><p><span style="color: rgb(34,34,34);line-height: 1.4285715;">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p><div><span style="color: rgb(34,34,34);"><br clear="none"></span></div><p><br clear="none"><span style="color: rgb(34,34,34);"> </span></p></div>
diff --git a/2015/02/18/apache-activemq-5102-released.xml b/2015/02/18/apache-activemq-5102-released.xml
index b53f9fc..b8c1d55 100644
--- a/2015/02/18/apache-activemq-5102-released.xml
+++ b/2015/02/18/apache-activemq-5102-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.10.2.</p><p>This release addresses bugs in the 5.10.1 release, including AMQ-5564 which addresses a potential memory leak.</p><p>Thank you to Timothy Bish and Claus Ibsen for promptly addressing AMQ-5564.  And thank you to Hadrian Zbarcea for merging commits in preparation for the release.</p><p><span style="line-height: 1.4285715;"> </span></p><p>Please see the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5102-release.html">release page</a> for download links and more information!</p></div>
+<div class="wiki-content maincontent"><p>The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.10.2.</p><p>This release addresses bugs in the 5.10.1 release, including AMQ-5564 which addresses a potential memory leak.</p><p>Thank you to Timothy Bish and Claus Ibsen for promptly addressing AMQ-5564.  And thank you to Hadrian Zbarcea for merging commits in preparation for the release.</p><p><span style="line-height: 1.4285715;"> </span></p><p>Please see the <a shape="rect" href="http://activemq.apache.org/activemq-5102-release.html">release page</a> for download links and more information!</p></div>
diff --git a/2015/02/18/apache-activemq-5111-released.xml b/2015/02/18/apache-activemq-5111-released.xml
index 4d8baa5..8e67ea9 100644
--- a/2015/02/18/apache-activemq-5111-released.xml
+++ b/2015/02/18/apache-activemq-5111-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.11.1.</p><p>This release addresses issues in the 5.11.0 release, including AMQ-5564 which addresses a potential memory leak..</p><p>Thank you to Timothy Bish and Claus Ibsen for promptly addressing AMQ-5564.  And thank you to Hadrian Zbarcea for merging commits in preparation for the release.</p><p> </p><p>Please see the <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5111-release.html">release page</a> for download links and more information!</p></div>
+<div class="wiki-content maincontent"><p>The Apache ActiveMQ team is proud to announce the release of Apache ActiveMQ 5.11.1.</p><p>This release addresses issues in the 5.11.0 release, including AMQ-5564 which addresses a potential memory leak..</p><p>Thank you to Timothy Bish and Claus Ibsen for promptly addressing AMQ-5564.  And thank you to Hadrian Zbarcea for merging commits in preparation for the release.</p><p> </p><p>Please see the <a shape="rect" href="http://activemq.apache.org/activemq-5111-release.html">release page</a> for download links and more information!</p></div>
diff --git a/2015/08/13/apache-activemq-5112-released.xml b/2015/08/13/apache-activemq-5112-released.xml
index 67bdf1e..dd62272 100644
--- a/2015/08/13/apache-activemq-5112-released.xml
+++ b/2015/08/13/apache-activemq-5112-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is delighted to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5112-release.html">ActiveMQ 5.11.2</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is delighted to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5112-release.html">ActiveMQ 5.11.2</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2015/08/14/apache-activemq-5120-released.xml b/2015/08/14/apache-activemq-5120-released.xml
index 48ddacd..0a9db2f 100644
--- a/2015/08/14/apache-activemq-5120-released.xml
+++ b/2015/08/14/apache-activemq-5120-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="wiki-content"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is happy to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5120-release.html">ActiveMQ 5.12.0</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div></div>
+<div class="wiki-content maincontent"><div class="wiki-content"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is happy to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5120-release.html">ActiveMQ 5.12.0</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div></div>
diff --git a/2015/10/16/apache-activemq-5121-released.xml b/2015/10/16/apache-activemq-5121-released.xml
index 42e7dbd..8d18e88 100644
--- a/2015/10/16/apache-activemq-5121-released.xml
+++ b/2015/10/16/apache-activemq-5121-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5121-release.html">ActiveMQ 5.12.1</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5121-release.html">ActiveMQ 5.12.1</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2015/11/03/activemq-5113-released.xml b/2015/11/03/activemq-5113-released.xml
index 11c5f3b..954a6b8 100644
--- a/2015/11/03/activemq-5113-released.xml
+++ b/2015/11/03/activemq-5113-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is delighted to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5113-release.html">ActiveMQ 5.11.3</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is delighted to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5113-release.html">ActiveMQ 5.11.3</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2015/12/03/apache-activemq-5130-released.xml b/2015/12/03/apache-activemq-5130-released.xml
index ad613b7..715995b 100644
--- a/2015/12/03/apache-activemq-5130-released.xml
+++ b/2015/12/03/apache-activemq-5130-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5130-release.html">ActiveMQ 5.13.0</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5130-release.html">ActiveMQ 5.13.0</a></span></p><p><span style="color: rgb(34,34,34);">A hearty thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2016/01/13/apache-activemq-5122-released.xml b/2016/01/13/apache-activemq-5122-released.xml
index cb97787..8ec7539 100644
--- a/2016/01/13/apache-activemq-5122-released.xml
+++ b/2016/01/13/apache-activemq-5122-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5122-release.html">ActiveMQ 5.12.2</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5122-release.html">ActiveMQ 5.12.2</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2016/02/08/apache-activemq-5131-released.xml b/2016/02/08/apache-activemq-5131-released.xml
index 7df861b..fe63e02 100644
--- a/2016/02/08/apache-activemq-5131-released.xml
+++ b/2016/02/08/apache-activemq-5131-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5131-release.html">ActiveMQ 5.13.1</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5131-release.html">ActiveMQ 5.13.1</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2016/03/07/apache-activemq-5132-released.xml b/2016/03/07/apache-activemq-5132-released.xml
index 9344380..e97ddeb 100644
--- a/2016/03/07/apache-activemq-5132-released.xml
+++ b/2016/03/07/apache-activemq-5132-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5132-release.html">ActiveMQ 5.13.2</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5132-release.html">ActiveMQ 5.13.2</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2016/05/03/apache-activemq-5133-released.xml b/2016/05/03/apache-activemq-5133-released.xml
index c1dae95..efdc32f 100644
--- a/2016/05/03/apache-activemq-5133-released.xml
+++ b/2016/05/03/apache-activemq-5133-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5133-release.html">ActiveMQ 5.13.3</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5133-release.html">ActiveMQ 5.13.3</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2016/07/21/apache-activemq-5134-released.xml b/2016/07/21/apache-activemq-5134-released.xml
index ff3633c..eff0a17 100644
--- a/2016/07/21/apache-activemq-5134-released.xml
+++ b/2016/07/21/apache-activemq-5134-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5134-release.html">ActiveMQ 5.13.4</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" href="http://activemq.apache.org/activemq-5134-release.html">ActiveMQ 5.13.4</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2016/08/08/apache-activemq-5140-released.xml b/2016/08/08/apache-activemq-5140-released.xml
index 3e3068a..4401cc1 100644
--- a/2016/08/08/apache-activemq-5140-released.xml
+++ b/2016/08/08/apache-activemq-5140-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5140-release.html">ActiveMQ 5.14.0</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" href="http://activemq.apache.org/activemq-5140-release.html">ActiveMQ 5.14.0</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2016/10/03/apache-activemq-5141-released.xml b/2016/10/03/apache-activemq-5141-released.xml
index 13bd7e3..156499b 100644
--- a/2016/10/03/apache-activemq-5141-released.xml
+++ b/2016/10/03/apache-activemq-5141-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5141-release.html">ActiveMQ 5.14.1</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" href="http://activemq.apache.org/activemq-5141-release.html">ActiveMQ 5.14.1</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2016/12/09/apache-activemq-5142-released.xml b/2016/12/09/apache-activemq-5142-released.xml
index 31a5912..846fa43 100644
--- a/2016/12/09/apache-activemq-5142-released.xml
+++ b/2016/12/09/apache-activemq-5142-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5142-release.html">ActiveMQ 5.14.2</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" href="http://activemq.apache.org/activemq-5142-release.html">ActiveMQ 5.14.2</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2017/03/03/apache-activemq-5144-released.xml b/2017/03/03/apache-activemq-5144-released.xml
index 026f9bf..329bde8 100644
--- a/2017/03/03/apache-activemq-5144-released.xml
+++ b/2017/03/03/apache-activemq-5144-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5144-release.html">ActiveMQ 5.14.4</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" href="http://activemq.apache.org/activemq-5144-release.html">ActiveMQ 5.14.4</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2017/04/17/apache-activemq-5145-released.xml b/2017/04/17/apache-activemq-5145-released.xml
index dcd24bf..eab06f0 100644
--- a/2017/04/17/apache-activemq-5145-released.xml
+++ b/2017/04/17/apache-activemq-5145-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5145-release.html">ActiveMQ 5.14.5</a><br clear="none">A big thanks to everyone who contributed to this release.<br clear="none">We look forward to your feedback.</p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ team is pleased to announce the release of <a shape="rect" href="http://activemq.apache.org/activemq-5145-release.html">ActiveMQ 5.14.5</a><br clear="none">A big thanks to everyone who contributed to this release.<br clear="none">We look forward to your feedback.</p></div>
diff --git a/2017/07/06/apache-activemq-5150-released.xml b/2017/07/06/apache-activemq-5150-released.xml
index 3a05092..ceb32c2 100644
--- a/2017/07/06/apache-activemq-5150-released.xml
+++ b/2017/07/06/apache-activemq-5150-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5150-release.html">ActiveMQ 5.15.0</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" href="http://activemq.apache.org/activemq-5150-release.html">ActiveMQ 5.15.0</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/2017/10/23/apache-activemq-5152-released.xml b/2017/10/23/apache-activemq-5152-released.xml
index 6de7b8f..22a734d 100644
--- a/2017/10/23/apache-activemq-5152-released.xml
+++ b/2017/10/23/apache-activemq-5152-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5152-release.html">ActiveMQ 5.15.2</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" href="http://activemq.apache.org/activemq-5152-release.html">ActiveMQ 5.15.2</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p></div>
diff --git a/40-rc-1-guide.xml b/40-rc-1-guide.xml
index 90e2602..482abca 100644
--- a/40-rc-1-guide.xml
+++ b/40-rc-1-guide.xml
@@ -1,40 +1,21 @@
<div class="wiki-content maincontent">
-<h1 id="id-4.0RC1Guide-ActiveMQ4.0-RC-1ReleaseGuide">ActiveMQ 4.0-RC-1 Release Guide</h1>
+<h1>ActiveMQ 4.0-RC-1 Release Guide</h1>
+<structured-macro ac:macro-id="17ebdd42-c7a8-4eb7-a100-f0f437346bd8" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Release Info"></page></link></parameter></structured-macro>
-<h2 id="id-4.0RC1Guide-GeneralReleaseInformation">General Release Information</h2>
-
-<ul><li><a shape="rect" class="external-link" href="http://jira.activemq.org/jira/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel" rel="nofollow">Current RoadMap</a></li><li><a shape="rect" href="release-guide.xml">Release Guide</a></li><li><a shape="rect" class="external-link" href="http://wiki.apache.org/incubator/SigningReleases">Signing Releases</a></li><li><a shape="rect" class="external-link" href="http://apache.org/dev/mirrors.html">Apache Mirror Guidelines</a></li></ul>
-
-<h2 id="id-4.0RC1Guide-ReleaseManager">Release Manager</h2>
+<h2>Release Manager</h2>
<p><strong>Hiram Chirino</strong></p>
-<h2 id="id-4.0RC1Guide-Specialissues">Special issues</h2>
+<h2>Special issues</h2>
<p>We are still in the Incubator so need to ensure that all the proper disclaimers are in place and that the artifacts are all properly named <strong>incubator-activemq</strong>.</p>
-<h2 id="id-4.0RC1Guide-OpenIssuesHoldinguptheRelease">Open Issues Holding up the Release</h2>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Macro params are invalid
-</div>
+<h2>Open Issues Holding up the Release</h2>
+<structured-macro ac:macro-id="7f85f0ae-2822-4605-ab32-ebb3aa92f7d9" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11727&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro><structured-macro ac:macro-id="868dcc2d-8785-4981-a107-a08e9d4fe594" ac:name="jiraissues" ac:schema-version="1"></structured-macro>
+<h2>Issues Resolved for this Release</h2>
+<structured-macro ac:macro-id="3e18b6b8-907d-438e-bdec-0a23f820a52a" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11727&status=5&status=6&sorter/field=issuekey&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=1000&reset=true&decorator=none"></url></parameter></structured-macro><structured-macro ac:macro-id="bba04820-7f10-4ff3-b1a2-53f3286f6910" ac:name="jiraissues" ac:schema-version="1"></structured-macro>
-<h2 id="id-4.0RC1Guide-IssuesResolvedforthisRelease">Issues Resolved for this Release</h2>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Macro params are invalid
-</div>
-
-
-<h2 id="id-4.0RC1Guide-HowtoHelp">How to Help</h2>
-
-<p>Everyone in the ActiveMQ community can help with releases; users, developers, commmiters are all encouraged to test out a release and post any comments to the <a shape="rect" href="mailing-lists.xml">activemq-dev@ mailing list</a> or create a <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ">JIRA</a> issue.</p>
-
-<p>ActiveMQ is available in both source and binary distributions. See <a shape="rect" href="getting-started.xml">Getting Started</a>.</p></div>
+<structured-macro ac:macro-id="bfcc4b7b-12e5-4794-ae41-818eb0fc337d" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="How you can help release"></page></link></parameter></structured-macro></div>
diff --git a/58-migration-guide.xml b/58-migration-guide.xml
index b6209c1..025b75d 100644
--- a/58-migration-guide.xml
+++ b/58-migration-guide.xml
@@ -4,8 +4,9 @@
<code>activemq-core</code> has been replaced with <code>activemq-client</code> and <code>activemq-broker</code>. The various message stores have their own activemq-xx-store module. The uber module <code>activemq-all</code> remains.</li><li>Changed JMX Mbean ObjectNames will effect scripts or tools that directly reference Mbean names<br clear="none">
All mbeans now share the type=Broker attribute, which gives them containment. In this way, consumers hang off of destinations, which hang off the broker.<br clear="none">
The different Mbean types are identified by the presence of specific identifiers in their ObjectNames. The mapping from old to new ObjectName is as follows:
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Old Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> New Name </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Broker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=Broker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=Queue|Topic,Destination=<destination identifier> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker,destinationType=Queue|Topic,destinationName=<destination identifier> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Connector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=Connector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker,connector=clientConnectors </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> NetworkConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=NetworkConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker,connector=networkConnectors </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Connection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=Connection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker,connector=*,connectionViewType=remoteAddress|clientId </p></td></tr></tbody></table></div>
-</li><li>OSGi integration has changed. The full details are at <a shape="rect" href="osgi-integration.xml">OSGi Integration</a>. In summary:
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Old Name </p></th><th colspan="1" rowspan="1"><p> New Name </p></th></tr><tr><td colspan="1" rowspan="1"><p> Broker </p></td><td colspan="1" rowspan="1"><p> Type=Broker </p></td><td colspan="1" rowspan="1"><p> type=Broker </p></td></tr><tr><td colspan="1" rowspan="1"><p> Destination </p></td><td colspan="1" rowspan="1"><p> Type=Queue|Topic,Destination=<destination identifier> </p></td><td colspan="1" rowspan="1"><p> type=Broker,destinationType=Queue|Topic,destinationName=<destination identifier> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Connector </p></td><td colspan="1" rowspan="1"><p> Type=Connector </p></td><td colspan="1" rowspan="1"><p> type=Broker,connector=clientConnectors </p></td></tr><tr><td colspan="1" rowspan="1"><p> NetworkConnector </p></td><td colspan="1" rowspan="1"><p> Type=NetworkConnector </p></td><td colspan="1" rowspan="1"><p> type=Broker,connector=networkConnectors </p></td></tr><tr><td colspan="1" rowspan="1"><p> Connection </p></td><td colspan="1" rowspan="1"><p> Type=Connection </p></td><td colspan="1" rowspan="1"><p> type=Broker,connector=*,connectionViewType=remoteAddress|clientId </p></td></tr></tbody></table>
+</li><li>OSGi integration has changed. The full details are at <link><page ri:content-title="OSGi Integration"></page></link>. In summary:
<ol><li>There is a single uber OSGI bundle</li><li>The broker and webconsole are now configured via config admin pid files through an OSGi managed service factory.</li></ol>
- </li><li>The ActiveMQ binary file <code>bin/run.jar</code> has been renamed to <code>bin/activemq.jar</code>.</li></ol></div>
+ </li><li>The ActiveMQ binary file <code>bin/run.jar</code> has been renamed to <code>bin/activemq.jar</code>.</li></ol>
+</div>
diff --git a/59-migration-guide.xml b/59-migration-guide.xml
index 6590290..aad8caf 100644
--- a/59-migration-guide.xml
+++ b/59-migration-guide.xml
@@ -1,5 +1,6 @@
<div class="wiki-content maincontent"><p>There are some changes in 5.9 that may require user intervention</p>
<ol><li>Schema change to JDBC Persistence Adapter. XID column type change.</li></ol>
-<ul><li>If you use XA transactions you need to ensure there are no XA transactions pending completion before you upgrade. Some mode detail in <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4628">AMQ-4628</a></li></ul></div>
+<ul><li>If you use XA transactions you need to ensure there are no XA transactions pending completion before you upgrade. Some mode detail in <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-4628">AMQ-4628</a></li></ul>
+</div>
diff --git a/activation-spec-properties.xml b/activation-spec-properties.xml
index a06d622..3f9100f 100644
--- a/activation-spec-properties.xml
+++ b/activation-spec-properties.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><p>An Activation Spec is used to configure the message delivery to an MDB. The ejb-jar.xml deployment descriptor needs to include a <activation-config> element inside the <message-driven> element like:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<activation-config>
+<div class="wiki-content maincontent"><p>An Activation Spec is used to configure the message delivery to an MDB. The ejb-jar.xml deployment descriptor needs to include a <activation-config> element inside the <message-driven> element like:</p><structured-macro ac:macro-id="67b5dd3d-e074-4650-88dd-258d28a396a4" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><activation-config>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>queue.testQueue</activation-config-property-value>
@@ -9,6 +8,5 @@
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
</activation-config>
-]]></script>
-</div></div><p>Here, the value for destination is the physical name of the desired destination. The value for destinationType is the class name that defines the type of destination. It should be javax.jms.Queue or javax.jms.Topic.<br clear="none">  </p><p>The Activation Spec properties that can be configured are:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Required</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>acknowledgeMode</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Auto-acknowledge</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The JMS Acknowledgement mode to use. Valid values are: Auto-acknowledge or Dups-ok-acknowledge</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>clientId</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set in resource adapter</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The JMS Client ID to use (only really required for durable topics)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>destinationType</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>yes</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The type of destination; a queue or topic</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>destination</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>yes</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The destination name (queue or topic name)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>enableBatch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Used to enable transaction batching for increased performance</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxMessagesPerBatch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of messages per transaction batch</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxMessagesPerSessions</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>This is actually the prefetch size for the subscription. (Yes, badly named).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxSessions</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of concurrent sessions to use</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>messageSelector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The JMS <a shape="rect" href="selectors.xml">Message Selector</a> to use on the subscription to perform content based routing filtering the messages</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>noLocal</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Only required for topic subscriptions; indicates if locally published messages should be included in the subscription or not</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>password</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set in resource adapter</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The password for the JMS connection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>subscriptionDurability</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>NonDurable</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not a durable (topic) subscription is required. Valid values are: Durable or NonDurable</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>subscriptionName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the durable subscriber. Only used for durable topics and combined with the clientID to uniquely identify the durable topic subscription</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>userName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set in resource adapter</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The user for the JMS connection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useRAManagedTransaction</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Typically, a resource adapter delivers messages to an endpoint which is managed by a container. Normally, this container likes to be the one that wants to control the transaction that the inbound message is being delivered on. But sometimes, you want to deliver to a simpler container system that will not be controlling the inbound transaction. In these cases, if you set useRAManagedTransaction to true, the resource adapter will commit the transaction if no exception was generated from the MessageListener and rollback if an exception is thrown.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>initialRedeliveryDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The delay before redeliveries start. Also configurable on the ResourceAdapter</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maximumRedeliveries</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of redeliveries or -1 for no maximum. Also configurable on the ResourceAdapter</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>redeliveryBackOffMultiplier</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The multiplier to use if exponential back off is enabled. Also configurable on the ResourceAdapter</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>redeliveryUseExponentialBackOff</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>To enable exponential backoff. Also configurable on the ResourceAdapter</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">useJndi</td><td colspan="1" rowspan="1" class="confluenceTd">no</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, use <span>destination as a jndi name</span></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Maximising Throughput of MDBs</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you want to maximise throughput of MDBs you should really set the <strong>maxSessions</strong> to something fairly large to increase the concurrency. Then set <strong>maxMessagesPerSessions</strong> to something big (say) 1000.</p><p>This assumes you have large numbers of messages available (say more than <strong>maxSessions</strong> * <strong>maxMessagesPerSession</strong>). Otherwise the <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch</a> will end up <a shape="rect" href="i-do-not-receive-messages-in-my-second-consumer.xml">starving other consumers</a>.</p><p>So if you don't have that many messages available, but maybe they take a while to process then you might want to set a lower value of <strong>maxMessagesPerSessions</strong></p></div></div></div>
+</plain-text-body></structured-macro><p>Here, the value for destination is the physical name of the desired destination. The value for destinationType is the class name that defines the type of destination. It should be javax.jms.Queue or javax.jms.Topic.<br clear="none">  </p><p>The Activation Spec properties that can be configured are:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Required</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>acknowledgeMode</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>Auto-acknowledge</p></td><td colspan="1" rowspan="1"><p>The JMS Acknowledgement mode to use. Valid values are: Auto-acknowledge or Dups-ok-acknowledge</p></td></tr><tr><td colspan="1" rowspan="1"><p>clientId</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>set in resource adapter</p></td><td colspan="1" rowspan="1"><p>The JMS Client ID to use (only really required for durable topics)</p></td></tr><tr><td colspan="1" rowspan="1"><p>destinationType</p></td><td colspan="1" rowspan="1"><p>yes</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>The type of destination; a queue or topic</p></td></tr><tr><td colspan="1" rowspan="1"><p>destination</p></td><td colspan="1" rowspan="1"><p>yes</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>The destination name (queue or topic name)</p></td></tr><tr><td colspan="1" rowspan="1"><p>enableBatch</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Used to enable transaction batching for increased performance</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxMessagesPerBatch</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>The number of messages per transaction batch</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxMessagesPerSessions</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>This is actually the prefetch size for the subscription. (Yes, badly named).</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxSessions</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>The maximum number of concurrent sessions to use</p></td></tr><tr><td colspan="1" rowspan="1"><p>messageSelector</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>The JMS <link><page ri:content-title="Selectors"></page><plain-text-link-body>Message Selector</plain-text-link-body></link> to use on the subscription to perform content based routing filtering the messages</p></td></tr><tr><td colspan="1" rowspan="1"><p>noLocal</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Only required for topic subscriptions; indicates if locally published messages should be included in the subscription or not</p></td></tr><tr><td colspan="1" rowspan="1"><p>password</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>set in resource adapter</p></td><td colspan="1" rowspan="1"><p>The password for the JMS connection</p></td></tr><tr><td colspan="1" rowspan="1"><p>subscriptionDurability</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>NonDurable</p></td><td colspan="1" rowspan="1"><p>Whether or not a durable (topic) subscription is required. Valid values are: Durable or NonDurable</p></td></tr><tr><td colspan="1" rowspan="1"><p>subscriptionName</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>The name of the durable subscriber. Only used for durable topics and combined with the clientID to uniquely identify the durable topic subscription</p></td></tr><tr><td colspan="1" rowspan="1"><p>userName</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>set in resource adapter</p></td><td colspan="1" rowspan="1"><p>The user for the JMS connection</p></td></tr><tr><td colspan="1" rowspan="1"><p>useRAManagedTransaction</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Typically, a resource adapter delivers messages to an endpoint which is managed by a container. Normally, this container likes to be the one that wants to control the transaction that the inbound message is being delivered on. But sometimes, you want to deliver to a simpler container system that will not be controlling the inbound transaction. In these cases, if you set useRAManagedTransaction to true, the resource adapter will commit the transaction if no exception was generated from the MessageListener and rollback if an exception is thrown.</p></td></tr><tr><td colspan="1" rowspan="1"><p>initialRedeliveryDelay</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>1000</p></td><td colspan="1" rowspan="1"><p>The delay before redeliveries start. Also configurable on the ResourceAdapter</p></td></tr><tr><td colspan="1" rowspan="1"><p>maximumRedeliveries</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>The maximum number of redeliveries or -1 for no maximum. Also configurable on the ResourceAdapter</p></td></tr><tr><td colspan="1" rowspan="1"><p>redeliveryBackOffMultiplier</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>The multiplier to use if exponential back off is enabled. Also configurable on the ResourceAdapter</p></td></tr><tr><td colspan="1" rowspan="1"><p>redeliveryUseExponentialBackOff</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>To enable exponential backoff. Also configurable on the ResourceAdapter</p></td></tr><tr><td colspan="1" rowspan="1">useJndi</td><td colspan="1" rowspan="1">no</td><td colspan="1" rowspan="1">false</td><td colspan="1" rowspan="1">when true, use <span>destination as a jndi name</span></td></tr></tbody></table><structured-macro ac:macro-id="f8da2771-f135-46c6-93a9-bdea3c50c06e" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Maximising Throughput of MDBs</parameter><rich-text-body><p>If you want to maximise throughput of MDBs you should really set the <strong>maxSessions</strong> to something fairly large to increase the concurrency. Then set <strong>maxMessagesPerSessions</strong> to something big (say) 1000.</p><p>This assumes you have large numbers of messages available (say more than <strong>maxSessions</strong> * <strong>maxMessagesPerSession</strong>). Otherwise the <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>prefetch</plain-text-link-body></link> will end up <link><page ri:content-title="I do not receive messages in my second consumer"></page><plain-text-link-body>starving other consumers</plain-text-link-body></link>.</p><p>So if you don't have that many messages available, but maybe they take a while to process then you might want to set a lower value of <strong>maxMessagesPerSessions</strong></p></rich-text-body></structured-macro></div>
diff --git a/activemq-11-release.xml b/activemq-11-release.xml
index 064e993..bd7cd93 100644
--- a/activemq-11-release.xml
+++ b/activemq-11-release.xml
@@ -1,21 +1,18 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ1.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This release represents a major increase in functionality; the new features in this release are:-</p>
<ul><li>distributed queues and topics and clusters of message brokers</li><li>auto-reconnection of clients across a cluster of brokers</li><li>support for high performance non-durable queues</li><li>wildcard support on queues (as well as topics)</li><li>transaction log and JDBC persistence in addition to JDBM and BDB</li><li>JNDI support for easy integration</li><li>HTTP tunnelling support</li><li>auto-broker discovery using Zeroconf (Apple Rendezvous) for a peer based network using high performance pointcast</li><li>composite destinations support (allowing a publish or subscribe operation on several queues and/or topics in one atomic operation, such as writing to N queues in one operation)</li><li>simpler pure-Java configuration API</li><li>heaps of bug fixes and new test cases</li></ul>
-<h2 id="ActiveMQ1.1Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-1.1.zip" rel="nofollow">activemq-1.1.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-1.1-src.zip" rel="nofollow">activemq-1.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-1.1.tar.gz" rel="nofollow">activemq-1.1.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>[activemq-1.1-src.tar.gz</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>http://dist.codehaus.org/activemq/distributions/activemq-1.1-src.tar.gz <br clear="none">
-]</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-1.1.zip">activemq-1.1.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-1.1-src.zip">activemq-1.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-1.1.tar.gz">activemq-1.1.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p>[activemq-1.1-src.tar.gz</p></td><td colspan="1" rowspan="1"><p>http://dist.codehaus.org/activemq/distributions/activemq-1.1-src.tar.gz <br clear="none">
+]</p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ1.1Release-Changelog">Changelog</h2>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<h2>Changelog</h2>
+<structured-macro ac:macro-id="0c7542d0-be14-4142-a2f0-c24003c84dc5" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=10632&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=10632" rel="nofollow">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=10632">release notes</a></p></div>
diff --git a/activemq-12-release.xml b/activemq-12-release.xml
index e3efffe..ae2039e 100644
--- a/activemq-12-release.xml
+++ b/activemq-12-release.xml
@@ -1,23 +1,20 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ1.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This release represents a major increase in functionality; the new features in this release are:-</p>
<ul><li>heaps of bug fixes and new test cases</li></ul>
-<h2 id="ActiveMQ1.2Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.2.zip" rel="nofollow">activemq-release-1.2.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.2-src.zip" rel="nofollow">activemq-release-1.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.2.tar.gz" rel="nofollow">activemq-release-1.2.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>[activemq-release-1.2-src.tar.gz</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-1.2-src.tar.gz <br clear="none">
-]</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.2.zip">activemq-release-1.2.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.2-src.zip">activemq-release-1.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.2.tar.gz">activemq-release-1.2.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p>[activemq-release-1.2-src.tar.gz</p></td><td colspan="1" rowspan="1"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-1.2-src.tar.gz <br clear="none">
+]</p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ1.2Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11120&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11120&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="4025f22b-ca17-4d67-9e1d-b90c51496e0b" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=11120&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-11-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 1.1 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-13-release.xml b/activemq-13-release.xml
index a4cd0ca..a1200c4 100644
--- a/activemq-13-release.xml
+++ b/activemq-13-release.xml
@@ -1,24 +1,21 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ1.3Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This release represents a major increase in functionality; the new features in this release are:-</p>
<ul><li>heaps of bug fixes and new test cases</li></ul>
-<h2 id="ActiveMQ1.3Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.3.zip" rel="nofollow">activemq-release-1.3.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.3-src.zip" rel="nofollow">activemq-release-1.3-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.3.tar.gz" rel="nofollow">activemq-release-1.3.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>[activemq-release-1.3-src.tar.gz</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-1.3-src.tar.gz <br clear="none">
-]</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.3.zip">activemq-release-1.3.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.3-src.zip">activemq-release-1.3-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.3.tar.gz">activemq-release-1.3.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p>[activemq-release-1.3-src.tar.gz</p></td><td colspan="1" rowspan="1"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-1.3-src.tar.gz <br clear="none">
+]</p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ1.3Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11270&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11270&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="e9498894-8bf7-4e20-84c7-203a325fdd64" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=11270&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-12-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 1.2 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-14-release.xml b/activemq-14-release.xml
index eee91da..8eeee45 100644
--- a/activemq-14-release.xml
+++ b/activemq-14-release.xml
@@ -1,23 +1,20 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ1.4Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This release represents a major increase in functionality; the new features in this release are:-</p>
<ul><li>heaps of bug fixes and new test cases</li></ul>
-<h2 id="ActiveMQ1.4Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.4.zip" rel="nofollow">activemq-release-1.4.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.4-src.zip" rel="nofollow">activemq-release-1.4-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.4.tar.gz" rel="nofollow">activemq-release-1.4.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>[activemq-release-1.4-src.tar.gz</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-1.4-src.tar.gz <br clear="none">
-]</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.4.zip">activemq-release-1.4.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.4-src.zip">activemq-release-1.4-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.4.tar.gz">activemq-release-1.4.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p>[activemq-release-1.4-src.tar.gz</p></td><td colspan="1" rowspan="1"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-1.4-src.tar.gz <br clear="none">
+]</p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ1.4Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11390&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11390&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="616e19c1-e654-47b8-8bed-6eaf54cf6594" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=11390&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-13-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 1.3 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-15-release.xml b/activemq-15-release.xml
index 01ee234..b9d91bf 100644
--- a/activemq-15-release.xml
+++ b/activemq-15-release.xml
@@ -1,23 +1,20 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ1.5Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This release is mostly a bug fix release:-</p>
<ul><li>A few bug fixes for J2EE compliance</li></ul>
-<h2 id="ActiveMQ1.5Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.5.zip" rel="nofollow">activemq-release-1.5.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.5-src.zip" rel="nofollow">activemq-release-1.5-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.5.tar.gz" rel="nofollow">activemq-release-1.5.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>[activemq-release-1.5-src.tar.gz</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-1.5-src.tar.gz <br clear="none">
-]</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.5.zip">activemq-release-1.5.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.5-src.zip">activemq-release-1.5-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-1.5.tar.gz">activemq-release-1.5.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p>[activemq-release-1.5-src.tar.gz</p></td><td colspan="1" rowspan="1"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-1.5-src.tar.gz <br clear="none">
+]</p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ1.5Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11422&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11422&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="2a076594-8dfd-438b-b38f-875b1182835d" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=11422&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-14-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 1.4 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-20-release.xml b/activemq-20-release.xml
index 3612740..818b4d7 100644
--- a/activemq-20-release.xml
+++ b/activemq-20-release.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ2.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This is a major release including lots of new functionality and performance improvements:</p>
@@ -10,19 +10,16 @@
<p>This new 2.0 wire format is incompatible with previous releases, so when upgrading please be sure to upgrade across your system. The wire format should not change now for some time, certainly not until another major release.</p>
-<h2 id="ActiveMQ2.0Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.0.zip" rel="nofollow">activemq-release-2.0.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.0-src.zip" rel="nofollow">activemq-release-2.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.0.tar.gz" rel="nofollow">activemq-release-2.0.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>[activemq-release-2.0-src.tar.gz</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-2.0-src.tar.gz <br clear="none">
-]</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.0.zip">activemq-release-2.0.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.0-src.zip">activemq-release-2.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.0.tar.gz">activemq-release-2.0.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p>[activemq-release-2.0-src.tar.gz</p></td><td colspan="1" rowspan="1"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-2.0-src.tar.gz <br clear="none">
+]</p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ2.0Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11420&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11420&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="7b92f849-6cdf-48e6-8a98-9db3ed0834d4" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=11420&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-15-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 1.5 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-21-release.xml b/activemq-21-release.xml
index 225e6af..f96d800 100644
--- a/activemq-21-release.xml
+++ b/activemq-21-release.xml
@@ -1,24 +1,21 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ2.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This release includes full support for the high performance journal. Our default persistence mechanism is now the journal for short term persistence and then JDBC (via Apache Derby by default) for long term storage. The journal is regularly checkpointed with the database for high performance and high resiliency.</p>
<p>This new release includes a number of performance enhancements in both durable and non durable messaging as well as a number of bug fixes.</p>
-<h2 id="ActiveMQ2.1Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.1.zip" rel="nofollow">activemq-release-2.1.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.1-src.zip" rel="nofollow">activemq-release-2.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.1.tar.gz" rel="nofollow">activemq-release-2.1.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>[activemq-release-2.1-src.tar.gz</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-2.1-src.tar.gz <br clear="none">
-]</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.1.zip">activemq-release-2.1.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.1-src.zip">activemq-release-2.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-release-2.1.tar.gz">activemq-release-2.1.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p>[activemq-release-2.1-src.tar.gz</p></td><td colspan="1" rowspan="1"><p>http://dist.codehaus.org/activemq/distributions/activemq-release-2.1-src.tar.gz <br clear="none">
+]</p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ2.1Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11499&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11499&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="3a45cb04-e039-4820-8723-d514abd4526e" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=11499&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-20-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 2.0 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-30-release.xml b/activemq-30-release.xml
index cdf760c..703dc1d 100644
--- a/activemq-30-release.xml
+++ b/activemq-30-release.xml
@@ -1,24 +1,21 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ3.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This new release includes the following</p>
-<ul><li>a new 'discovery' transport <a shape="rect" href="uri-protocols.xml">protocol</a> for a pure client-only peer network - a self discovering cluster which automatically finds the brokers available on the network (as opposed to the 'peer' protocol which is a complete peer based JMS network).</li><li>migrated from the org.activemq to org.activemq package name hierarchy</li><li>improved support for more JDBC databases for persistence</li><li>an optimised wire protocol (which is unfortunately not compatible with 2.x)</li><li>more test cases and fixes of the <a shape="rect" href="jca-container.xml">JCA Container</a></li><li>various performance enhancements and bug fixes</li></ul>
+<ul><li>a new 'discovery' transport <link><page ri:content-title="URI Protocols"></page><link-body>protocol</link-body></link> for a pure client-only peer network - a self discovering cluster which automatically finds the brokers available on the network (as opposed to the 'peer' protocol which is a complete peer based JMS network).</li><li>migrated from the org.activemq to org.activemq package name hierarchy</li><li>improved support for more JDBC databases for persistence</li><li>an optimised wire protocol (which is unfortunately not compatible with 2.x)</li><li>more test cases and fixes of the <link><page ri:content-title="JCA Container"></page></link></li><li>various performance enhancements and bug fixes</li></ul>
-<h2 id="ActiveMQ3.0Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.0.zip" rel="nofollow">activemq-3.0.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.0-src.zip" rel="nofollow">activemq-3.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.0.tar.gz" rel="nofollow">activemq-3.0.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.0-src.tar.gz" rel="nofollow">activemq-3.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.0.zip">activemq-3.0.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.0-src.zip">activemq-3.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.0.tar.gz">activemq-3.0.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.0-src.tar.gz">activemq-3.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ3.0Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11500&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11500&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="f214b00e-ab9d-4881-8e53-a6c15a42c09b" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=11500&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-21-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 2.1 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-31-release.xml b/activemq-31-release.xml
index 94fcb91..a2042cb 100644
--- a/activemq-31-release.xml
+++ b/activemq-31-release.xml
@@ -1,26 +1,23 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ3.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This new release includes the following</p>
-<ul><li>New <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> support to make it easy to create cross language clients such as for Ruby or Perl etc. (Python, C and .Net coming soon)</li><li>XPath based selectors and demand based publishing, making it easy to implement <a shape="rect" class="external-link" href="http://servicemix.org/WS+Notification" rel="nofollow">WS-Notification</a> on top of ActiveMQ</li><li>a pooling JMS ConnectionFactory for better support of the Spring JMSTemplate outside of a JCA container</li><li>improved JNDI support to allow easy dynamic creation of Queues and Topics, to handle different connection settings and to reuse standard JNDI properties</li><li>Increased support for the number of <a shape="rect" href="jdbc-support.xml">databases and JDBC drivers</a> to include
+<ul><li>New <a shape="rect" href="http://stomp.codehaus.org/">Stomp</a> support to make it easy to create cross language clients such as for Ruby or Perl etc. (Python, C and .Net coming soon)</li><li>XPath based selectors and demand based publishing, making it easy to implement <a shape="rect" href="http://servicemix.org/WS+Notification">WS-Notification</a> on top of ActiveMQ</li><li>a pooling JMS ConnectionFactory for better support of the Spring JMSTemplate outside of a JCA container</li><li>improved JNDI support to allow easy dynamic creation of Queues and Topics, to handle different connection settings and to reuse standard JNDI properties</li><li>Increased support for the number of <link><page ri:content-title="JDBC Support"></page><link-body>databases and JDBC drivers</link-body></link> to include
<ul><li>Apache Derby</li><li>Oracle</li><li>Sybase</li><li>DB2</li><li>SQLServer</li><li>Postgresql</li><li>MySQL</li><li>Axion</li><li>HSQL</li></ul>
</li><li>improved authentication at the connection and destination level</li><li>More flexible prefetch policy configurations for more control over queue dispatching and performance tuning</li><li>improved support for priority message ordering</li><li>cleaner servlet integration</li><li>better XA integration to allow outbound producers to reuse inbound JMS sessions</li><li>improved support for WebSphere and JBoss</li><li>easier journal file size and checkpoint period configuration</li><li>jabber transport</li><li>various performance enhancements and bug fixes</li></ul>
-<h2 id="ActiveMQ3.1Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.1.zip" rel="nofollow">activemq-3.1.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.1-src.zip" rel="nofollow">activemq-3.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.1.tar.gz" rel="nofollow">activemq-3.1.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.1-src.tar.gz" rel="nofollow">activemq-3.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.1.zip">activemq-3.1.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.1-src.zip">activemq-3.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.1.tar.gz">activemq-3.1.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.1-src.tar.gz">activemq-3.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ3.1Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11501&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11501&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="734eb27c-b8f6-4715-b880-1907d691ed20" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&fixfor=11501&sorter/field=issuekey&sorter/order=DESC&tempMax=100&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-30-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 3.0 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-32-release.xml b/activemq-32-release.xml
index b526bfc..f26e103 100644
--- a/activemq-32-release.xml
+++ b/activemq-32-release.xml
@@ -1,23 +1,20 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ3.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This new release includes the following</p>
-<ul><li>Improved <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> 1.0 support to make it easy to create cross language clients such as for C, C#, Python, Ruby, Perl and Pike.</li><li>Ajax support now uses OpenRico as the default Ajax library</li><li>the Resource Adaptor now supports batching</li><li>demand based store and forward in networks</li><li>support for Informix JDBC</li><li>updated DTD for the latest Spring</li><li>various performance enhancements and bug fixes</li></ul>
+<ul><li>Improved <a shape="rect" href="http://stomp.codehaus.org/">Stomp</a> 1.0 support to make it easy to create cross language clients such as for C, C#, Python, Ruby, Perl and Pike.</li><li>Ajax support now uses OpenRico as the default Ajax library</li><li>the Resource Adaptor now supports batching</li><li>demand based store and forward in networks</li><li>support for Informix JDBC</li><li>updated DTD for the latest Spring</li><li>various performance enhancements and bug fixes</li></ul>
-<h2 id="ActiveMQ3.2Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.zip" rel="nofollow">activemq-3.2.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2-src.zip" rel="nofollow">activemq-3.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.tar.gz" rel="nofollow">activemq-3.2.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2-src.tar.gz" rel="nofollow">activemq-3.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.zip">activemq-3.2.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2-src.zip">activemq-3.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.tar.gz">activemq-3.2.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2-src.tar.gz">activemq-3.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ3.2Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11610&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11610&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="b8c785ae-8206-49dd-b5c9-8d7c264d7dfd" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&fixfor=11610&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-31-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 3.1 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-321-release.xml b/activemq-321-release.xml
index 9fab03b..cd87bc5 100644
--- a/activemq-321-release.xml
+++ b/activemq-321-release.xml
@@ -1,19 +1,16 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ3.2.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This release is a bug fix release and users of previous versions of 3.2 are encouraged to upgrade to this version.</p>
-<h2 id="ActiveMQ3.2.1Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.1.zip" rel="nofollow">activemq-3.2.1.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.1-src.zip" rel="nofollow">activemq-3.2.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.1.tar.gz" rel="nofollow">activemq-3.2.1.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.1-src.tar.gz" rel="nofollow">activemq-3.2.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.1.zip">activemq-3.2.1.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.1-src.zip">activemq-3.2.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.1.tar.gz">activemq-3.2.1.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.1-src.tar.gz">activemq-3.2.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ3.2.1Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11715&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11715&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="03b2865f-ddfe-4560-861a-5df69548bb43" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&pid=10520&types=1&types=2&types=4&types=3&fixfor=11715&statusIds=5&statusIds=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-32-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 3.2 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-322-release.xml b/activemq-322-release.xml
index ca99bc9..19fbb7e 100644
--- a/activemq-322-release.xml
+++ b/activemq-322-release.xml
@@ -1,19 +1,16 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ3.2.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This release is a bug fix release and users of previous versions of 3.2 are encouraged to upgrade to this version.</p>
-<h2 id="ActiveMQ3.2.2Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.2.zip" rel="nofollow">activemq-3.2.2.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.2-src.zip" rel="nofollow">activemq-3.2.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.2.tar.gz" rel="nofollow">activemq-3.2.2.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.2-src.tar.gz" rel="nofollow">activemq-3.2.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.2.zip">activemq-3.2.2.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.2-src.zip">activemq-3.2.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.2.tar.gz">activemq-3.2.2.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/activemq-3.2.2-src.tar.gz">activemq-3.2.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ3.2.2Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11723&styleName=Html&projectId=10520&Create=Create" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?version=11723&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="8e517002-3efb-4615-8af9-0e710c7488b0" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11723&status=5&status=6&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>You may also want to look at <a shape="rect" href="activemq-321-release.xml">the previous Changelog</a></p></div>
+<p>You may also want to look at <link><page ri:content-title="ActiveMQ 3.2.1 Release"></page><link-body>the previous Changelog</link-body></link></p></div>
diff --git a/activemq-40-m4-release.xml b/activemq-40-m4-release.xml
index cba8dfc..ed4ee9c 100644
--- a/activemq-40-m4-release.xml
+++ b/activemq-40-m4-release.xml
@@ -1,18 +1,16 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ4.0M4Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
-<p>This is the first milestone release of 4.x since the move to Apache so the package names have changed from org.activemq to org.apache.activemq. For a full list see the <a shape="rect" href="changes-in-40.xml">Changes in 4.0</a>.</p>
+<p>This is the first milestone release of 4.x since the move to Apache so the package names have changed from org.activemq to org.apache.activemq. For a full list see the <link><page ri:content-title="Changes in 4.0"></page></link>.</p>
-<p>This release of ActiveMQ includes a large number of <a shape="rect" href="changes-in-40.xml">new features</a> such as <a shape="rect" href="masterslave.xml">MasterSlave</a> and <a shape="rect" href="message-groups.xml">Message Groups</a> together with numerous bug fixes.</p>
+<p>This release of ActiveMQ includes a large number of <link><page ri:content-title="Changes in 4.0"></page><link-body>new features</link-body></link> such as <link><page ri:content-title="MasterSlave"></page></link> and <link><page ri:content-title="Message Groups"></page></link> together with numerous bug fixes.</p>
-<h2 id="ActiveMQ4.0M4Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-M4.zip">activemq-4.0-M4.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-M4-src.zip">activemq-4.0-M4-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-M4.tar.gz">activemq-4.0-M4.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-M4-src.tar.gz">activemq-4.0-M4-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-M4.zip">activemq-4.0-M4.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-M4-src.zip">activemq-4.0-M4-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-M4.tar.gz">activemq-4.0-M4.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-M4-src.tar.gz">activemq-4.0-M4-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ4.0M4Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11726" rel="nofollow">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://jira.activemq.org/jira/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11726">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div></div>
+<structured-macro ac:macro-id="8d93ac92-0500-4bfe-942f-1385b04c0286" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://jira.activemq.org/jira/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11726&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro></div>
diff --git a/activemq-40-rc2-release.xml b/activemq-40-rc2-release.xml
index 1e1dd82..0370233 100644
--- a/activemq-40-rc2-release.xml
+++ b/activemq-40-rc2-release.xml
@@ -1,30 +1,27 @@
<div class="wiki-content maincontent">
-<h2 id="ActiveMQ4.0RC2Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This is the second release candiate release of 4.0.</p>
-<p>This release of ActiveMQ includes a large number of <a shape="rect" href="changes-in-40.xml">new features</a> such as <a shape="rect" href="masterslave.xml">MasterSlave</a> and <a shape="rect" href="message-groups.xml">Message Groups</a> together with numerous bug fixes.</p>
+<p>This release of ActiveMQ includes a large number of <link><page ri:content-title="Changes in 4.0"></page><link-body>new features</link-body></link> such as <link><page ri:content-title="MasterSlave"></page></link> and <link><page ri:content-title="Message Groups"></page></link> together with numerous bug fixes.</p>
-<h3 id="ActiveMQ4.0RC2Release-Warnings">Warnings</h3>
+<h3>Warnings</h3>
<p>When upgrading from a previous release you are advised to clear down the journal files and persistent database first before upgrading to this jar as the binary format of messages is not compatible with 3.x or earlier 4.x releases.</p>
-<h3 id="ActiveMQ4.0RC2Release-Whathaschanged">What has changed</h3>
+<h3>What has changed</h3>
-<p>The 4.x branch of ActiveMQ has now moved to the Apache Incubator so the package names have changed from org.activemq to org.apache.activemq. For a full list see the <a shape="rect" href="changes-in-40.xml">Changes in 4.0</a>.</p>
+<p>The 4.x branch of ActiveMQ has now moved to the Apache Incubator so the package names have changed from org.activemq to org.apache.activemq. For a full list see the <link><page ri:content-title="Changes in 4.0"></page></link>.</p>
-<h2 id="ActiveMQ4.0RC2Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-RC2.zip">activemq-4.0-RC2.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-RC2-src.zip">activemq-4.0-RC2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-RC2.tar.gz">activemq-4.0-RC2.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-RC2-src.tar.gz">activemq-4.0-RC2-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-RC2.zip">activemq-4.0-RC2.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-RC2-src.zip">activemq-4.0-RC2-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-RC2.tar.gz">activemq-4.0-RC2.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://cvs.apache.org/repository/incubator-activemq/distributions/activemq-4.0-RC2-src.tar.gz">activemq-4.0-RC2-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ4.0RC2Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11750">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11750">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="3568981f-91dc-4af7-ad4b-a49717f05b55" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="https://issues.apache.org/activemq/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11750&sorter/field=issuekey&sorter/order=DESC&tempMax=1000&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>Also see the previous <a shape="rect" href="activemq-40-m4-release.xml">ActiveMQ 4.0 M4 Release</a></p></div>
+<p>Also see the previous <link><page ri:content-title="ActiveMQ 4.0 M4 Release"></page></link></p></div>
diff --git a/activemq-40-release.xml b/activemq-40-release.xml
index b39faa8..773face 100644
--- a/activemq-40-release.xml
+++ b/activemq-40-release.xml
@@ -1,53 +1,44 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ4.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
-<p>This is the 4.0 release of Apache ActiveMQ. This release of Apache ActiveMQ includes a large number of <a shape="rect" href="changes-in-40.xml">new features</a> such as <a shape="rect" href="masterslave.xml">MasterSlave</a> and <a shape="rect" href="message-groups.xml">Message Groups</a> together with numerous bug fixes.</p>
+<p>This is the 4.0 release of Apache ActiveMQ. This release of Apache ActiveMQ includes a large number of <link><page ri:content-title="Changes in 4.0"></page><link-body>new features</link-body></link> such as <link><page ri:content-title="MasterSlave"></page></link> and <link><page ri:content-title="Message Groups"></page></link> together with numerous bug fixes.</p>
-<h3 id="ActiveMQ4.0Release-Warnings">Warnings</h3>
+<h3>Warnings</h3>
<p>When upgrading from a previous release you are advised to clear down the journal files and persistent database first before upgrading to this jar as the binary format of messages is not compatible with 3.x or earlier 4.0 milestone releases. </p>
-<h3 id="ActiveMQ4.0Release-Knownissues">Known issues</h3>
+<h3>Known issues</h3>
-<p>Some folks have found issues with acknowledgements, particularly when using auto-ack mode. This has been fixed in 4.0.1 which will be released shortly. Until then we recommend you disable <a shape="rect" href="connection-configuration-uri.xml">optimizeAcknowledge</a>. e.g. connect via</p>
+<p>Some folks have found issues with acknowledgements, particularly when using auto-ack mode. This has been fixed in 4.0.1 which will be released shortly. Until then we recommend you disable <link><page ri:content-title="Connection Configuration URI"></page><link-body>optimizeAcknowledge</link-body></link>. e.g. connect via</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1c57366d-fb90-4fe9-b78b-95402c62f258" ac:name="code" ac:schema-version="1"><plain-text-body>
tcp://localhost:61616?jms.optimizeAcknowledge=false
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>The source distributions do not build as is anymore due to changes in the way the maven repo is now setup at Apache. You must first apply the following <a shape="rect" href="activemq-40-release.data/amq4-build.patch?version=1&modificationDate=1150318678000&api=v2" data-linked-resource-id="3263" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="amq4-build.patch" data-linked-resource-content-type="text/x-patch" data-linked-resource-container-id="36141" data-linked-resource-container-version="12">patch</a> before doing the build. You will need to download the patch and apply it using the patch command.</p>
+<p>The source distributions do not build as is anymore due to changes in the way the maven repo is now setup at Apache. You must first apply the following <link><attachment ri:filename="amq4-build.patch"></attachment><link-body>patch</link-body></link> before doing the build. You will need to download the patch and apply it using the patch command.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="91f79a80-5459-4350-a9df-c59951da64a7" ac:name="code" ac:schema-version="1"><plain-text-body>
cd ${path-to-activemq-source-distro}
patch -p 0 < ${path-to-amq4-build.patch}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="ActiveMQ4.0Release-Whathaschanged">What has changed</h3>
+<h3>What has changed</h3>
-<p>The 4.x branch of Apache ActiveMQ has now moved to the Apache Incubator so the package names have changed from org.activemq to org.apache.activemq. For a full list see the <a shape="rect" href="changes-in-40.xml">Changes in 4.0</a>.</p>
+<p>The 4.x branch of Apache ActiveMQ has now moved to the Apache Incubator so the package names have changed from org.activemq to org.apache.activemq. For a full list see the <link><page ri:content-title="Changes in 4.0"></page></link>.</p>
-<h2 id="ActiveMQ4.0Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Download</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.zip">incubator-activemq-4.0.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0-src.zip">incubator-activemq-4.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.tar.gz">incubator-activemq-4.0.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0-src.tar.gz">incubator-activemq-4.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Distribution in gz package</p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Download</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.zip">incubator-activemq-4.0.zip</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0-src.zip">incubator-activemq-4.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in zip package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.tar.gz">incubator-activemq-4.0.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Binary Distribution in gz package</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0-src.tar.gz">incubator-activemq-4.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p>Source Distribution in gz package</p></td></tr></tbody></table>
-<h2 id="ActiveMQ4.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h2>SVN Tag Checkout</h2>
+<structured-macro ac:macro-id="497437e5-e037-401e-a9dd-847fdc296bd3" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/incubator/activemq/tags/activemq-4.0
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ4.0Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&pid=10520&fixfor=11660">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&pid=10520&fixfor=11660">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="8b7fb8e1-5345-4ccd-b51b-6c43b7304faf" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11660&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>Also see the previous <a shape="rect" href="activemq-40-rc2-release.xml">ActiveMQ 4.0 RC2 Release</a></p></div>
+<p>Also see the previous <link><page ri:content-title="ActiveMQ 4.0 RC2 Release"></page></link></p></div>
diff --git a/activemq-401-release.xml b/activemq-401-release.xml
index 8fa6915..424306c 100644
--- a/activemq-401-release.xml
+++ b/activemq-401-release.xml
@@ -1,29 +1,30 @@
-<div class="wiki-content maincontent"><p>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="e8c22b09-3bcf-4961-9bc2-8f0c7641feae" ac:name="html" ac:schema-version="1"><plain-text-body>
+<!--
+{warning:title=The Release is still in progress}
+You are previewing the release page for unreleased version of ActiveMQ. The download links on the page below will not work until it is offically released.
-</p>
+Until the release is approved you could try the current build: http://people.apache.org/~chirino/incubator-activemq-4.0.1-RC1/maven1/incubator-activemq/distributions/
+{warning}
+-->
+</plain-text-body></structured-macro></p>
-<h2 id="ActiveMQ4.0.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<h2>New and Noteworthy</h2>
<p>This is a minor bug fix release. All previous installations of Apache ActiveMQ 4.0 are recommended to upgrade to this release.</p>
-<h2 id="ActiveMQ4.0.1Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1.zip">incubator-activemq-4.0.1.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1.zip.asc">incubator-activemq-4.0.1.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1-src.zip">incubator-activemq-4.0.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1-src.zip.asc">incubator-activemq-4.0.1-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary for Unix</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1.tar.gz">incubator-activemq-4.0.1.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1.tar.gz.asc">incubator-activemq-4.0.1.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1-src.tar.gz">incubator-activemq-4.0.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1-src.tar.gz.asc">incubator-activemq-4.0.1-src.tar.gz.asc</a></p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Binary for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1.zip">incubator-activemq-4.0.1.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1.zip.asc">incubator-activemq-4.0.1.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1-src.zip">incubator-activemq-4.0.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1-src.zip.asc">incubator-activemq-4.0.1-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Binary for Unix</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1.tar.gz">incubator-activemq-4.0.1.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1.tar.gz.asc">incubator-activemq-4.0.1.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1-src.tar.gz">incubator-activemq-4.0.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.1-src.tar.gz.asc">incubator-activemq-4.0.1-src.tar.gz.asc</a></p></td></tr></tbody></table>
-<h2 id="ActiveMQ4.0.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h2>SVN Tag Checkout</h2>
+<structured-macro ac:macro-id="c6de6663-a103-4b0e-b354-a8397b6f9cd2" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/incubator/activemq/tags/activemq-4.0.1
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ4.0.1Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11780&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11780&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="c00ff1c9-4ae1-4d1f-a4b6-242420b352fd" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11780&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>Also see the previous <a shape="rect" href="activemq-40-release.xml">ActiveMQ 4.0 Release</a></p></div>
+<p>Also see the previous <link><page ri:content-title="ActiveMQ 4.0 Release"></page></link></p></div>
diff --git a/activemq-402-release.xml b/activemq-402-release.xml
index 4ed31d0..20e725b 100644
--- a/activemq-402-release.xml
+++ b/activemq-402-release.xml
@@ -1,25 +1,20 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ4.0.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor bug fix release. All previous installations of Apache ActiveMQ 4.0.1 are recommended to upgrade to this release.</p>
-<h2 id="ActiveMQ4.0.2Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2.zip">incubator-activemq-4.0.2.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2.zip.asc">incubator-activemq-4.0.2.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2-src.zip">incubator-activemq-4.0.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2-src.zip.asc">incubator-activemq-4.0.2-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary for Unix</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2.tar.gz">incubator-activemq-4.0.2.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2.tar.gz.asc">incubator-activemq-4.0.2.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2-src.tar.gz">incubator-activemq-4.0.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2-src.tar.gz.asc">incubator-activemq-4.0.2-src.tar.gz.asc</a></p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Binary for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2.zip">incubator-activemq-4.0.2.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2.zip.asc">incubator-activemq-4.0.2.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2-src.zip">incubator-activemq-4.0.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2-src.zip.asc">incubator-activemq-4.0.2-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Binary for Unix</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2.tar.gz">incubator-activemq-4.0.2.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2.tar.gz.asc">incubator-activemq-4.0.2.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2-src.tar.gz">incubator-activemq-4.0.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/incubator-activemq-4.0.2-src.tar.gz.asc">incubator-activemq-4.0.2-src.tar.gz.asc</a></p></td></tr></tbody></table>
-<h2 id="ActiveMQ4.0.2Release-SVNTagCheckout">SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h2>SVN Tag Checkout</h2>
+<structured-macro ac:macro-id="9fa8cc37-c891-4e8d-a3e3-ca1d15c70e78" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/incubator/activemq/tags/activemq-4.0.2
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ4.0.2Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11783&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11783&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="0f3fb5c8-0599-412e-905b-bd2abd34969e" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11783&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>Also see the previous <a shape="rect" href="activemq-401-release.xml">ActiveMQ 4.0.1 Release</a></p></div>
+<p>Also see the previous <link><page ri:content-title="ActiveMQ 4.0.1 Release"></page></link></p></div>
diff --git a/activemq-410-release.xml b/activemq-410-release.xml
index 9d61949..56d8f4c 100644
--- a/activemq-410-release.xml
+++ b/activemq-410-release.xml
@@ -1,11 +1,8 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png"></span></p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="7eb0ee22-25e8-40c4-93e7-7b231d410e59" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png"></url></image></p></rich-text-body></structured-macro>
-
-
-
-<div style="min-height:200px">
-<h2 id="ActiveMQ4.1.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<structured-macro ac:macro-id="c53e9a16-861b-44a4-9315-41722329fbd8" ac:name="div" ac:schema-version="1"><parameter ac:name="style">min-height:200px</parameter><rich-text-body>
+<h2>New and Noteworthy</h2>
<p>This is release contains several major enhancements such as:</p>
@@ -14,28 +11,20 @@
<p>It also contains a slew of bug fixes that are tracked in the change log.</p>
-<h2 id="ActiveMQ4.1.0Release-DownloadHere">Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/apache-activemq-4.1.0-incubator.zip">apache-activemq-4.1.0-incubator.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/apache-activemq-4.1.0-incubator.zip.asc">incubator-activemq-4.1.0.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Binary for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/apache-activemq-4.1.0-incubator.tar.gz">apache-activemq-4.1.0-incubator.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/apache-activemq-4.1.0-incubator.tar.gz.asc">incubator-activemq-4.1.0.tar.gz.asc</a></p></td></tr></tbody></table></div>
+<h2>Download Here</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Binary for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/apache-activemq-4.1.0-incubator.zip">apache-activemq-4.1.0-incubator.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/apache-activemq-4.1.0-incubator.zip.asc">incubator-activemq-4.1.0.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Binary for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/apache-activemq-4.1.0-incubator.tar.gz">apache-activemq-4.1.0-incubator.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://people.apache.org/repo/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/apache-activemq-4.1.0-incubator.tar.gz.asc">incubator-activemq-4.1.0.tar.gz.asc</a></p></td></tr></tbody></table>
-</div>
+</rich-text-body></structured-macro>
-
-
-
-<h2 id="ActiveMQ4.1.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h2>SVN Tag Checkout</h2>
+<structured-macro ac:macro-id="555f21ec-222c-48eb-924c-4afaccbc4b25" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/tags/activemq-4.1.0
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ4.1.0Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11691&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11691&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
+<structured-macro ac:macro-id="e45b257b-5f8b-4949-b9f8-d1e7da3d4e24" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="columns">type;key;summary</parameter><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/secure/IssueNavigator.jspa?view=rss&&pid=10520&fixfor=11691&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro>
-
-<p>Also see the previous <a shape="rect" href="activemq-402-release.xml">ActiveMQ 4.0.2 Release</a></p></div>
+<p>Also see the previous <link><page ri:content-title="ActiveMQ 4.0.2 Release"></page></link></p></div>
diff --git a/activemq-411-release.xml b/activemq-411-release.xml
index 86a3e88..9a04fe5 100644
--- a/activemq-411-release.xml
+++ b/activemq-411-release.xml
@@ -1,59 +1,46 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png"></span></p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="41cfe7e2-77b3-4f0a-b9bb-a34cb5af876b" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png"></url></image></p></rich-text-body></structured-macro>
-
-
-
-<div style="min-height:200px">
-<h2 id="ActiveMQ4.1.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<structured-macro ac:macro-id="b324427f-3e30-4c8c-b056-1a7aaacb22f3" ac:name="div" ac:schema-version="1"><parameter ac:name="style">min-height:200px</parameter><rich-text-body>
+<h2>New and Noteworthy</h2>
<p>Contains slew of bug fixes that are tracked in the change log.</p>
-<h2 id="ActiveMQ4.1.1Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2>
+<h2>Getting the Binary Distributions</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1.zip">apache-activemq-4.1.1.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1.zip.asc">apache-activemq-4.1.1.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1.tar.gz">apache-activemq-4.1.1.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1.tar.gz.asc">apache-activemq-4.1.1.tar.gz.asc</a></p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1.zip">apache-activemq-4.1.1.zip</a></p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1.zip.asc">apache-activemq-4.1.1.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1.tar.gz">apache-activemq-4.1.1.tar.gz</a></p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1.tar.gz.asc">apache-activemq-4.1.1.tar.gz.asc</a></p></td></tr></tbody></table>
-<h2 id="ActiveMQ4.1.1Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2>
+<h2>Getting the Binaries using Maven 2</h2>
-<p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p>
+<p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="31b69de9-6a99-471d-809c-0f83c4c47c48" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>4.1.1</version>
</dependency>
-]]></script>
-</div></div>
-</div>
+</plain-text-body></structured-macro>
+</rich-text-body></structured-macro>
+
+<h2>Getting the Source Code</h2>
+
+<h3>Source Distributions</h3>
+
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1-src.zip">apache-activemq-4.1.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1-src.zip.asc">apache-activemq-4.1.1-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1-src.tar.gz">apache-activemq-4.1.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1-src.tar.gz.asc">apache-activemq-4.1.1-src.tar.gz.asc</a></p></td></tr></tbody></table>
+<h3>SVN Tag Checkout</h3>
-
-<h2 id="ActiveMQ4.1.1Release-GettingtheSourceCode">Getting the Source Code</h2>
-
-<h3 id="ActiveMQ4.1.1Release-SourceDistributions">Source Distributions</h3>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1-src.zip">apache-activemq-4.1.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1-src.zip.asc">apache-activemq-4.1.1-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1-src.tar.gz">apache-activemq-4.1.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.1/apache-activemq-4.1.1-src.tar.gz.asc">apache-activemq-4.1.1-src.tar.gz.asc</a></p></td></tr></tbody></table></div>
-
-
-<h3 id="ActiveMQ4.1.1Release-SVNTagCheckout">SVN Tag Checkout</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="34c1cfa9-0ea8-4d66-9f01-2c2cf172511f" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-4.1.1
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ4.1.1Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11800&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11800&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
+<structured-macro ac:macro-id="d8bdcfa0-84ce-4997-b564-8b0b7d7c4444" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="columns">type;key;summary</parameter><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=10520&fixfor=11800&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro>
-
-<p>Also see the previous <a shape="rect" href="activemq-410-release.xml">ActiveMQ 4.1.0 Release</a></p></div>
+<p>Also see the previous <link><page ri:content-title="ActiveMQ 4.1.0 Release"></page></link></p></div>
diff --git a/activemq-412-release.xml b/activemq-412-release.xml
index 8d11cc3..653bce4 100644
--- a/activemq-412-release.xml
+++ b/activemq-412-release.xml
@@ -1,59 +1,46 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png"></span></p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="adb7e2bb-80d2-4600-a407-b06e9be999bf" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png"></url></image></p></rich-text-body></structured-macro>
-
-
-
-<div style="min-height:200px">
-<h2 id="ActiveMQ4.1.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<structured-macro ac:macro-id="d9aaef9d-e61f-4f60-842f-267fbd13e127" ac:name="div" ac:schema-version="1"><parameter ac:name="style">min-height:200px</parameter><rich-text-body>
+<h2>New and Noteworthy</h2>
<p>Contains slew of bug fixes that are tracked in the change log.</p>
-<h2 id="ActiveMQ4.1.2Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2>
+<h2>Getting the Binary Distributions</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-bin.zip">apache-activemq-4.1.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-bin.zip.asc">apache-activemq-4.1.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-bin.tar.gz">apache-activemq-4.1.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-bin.tar.gz.asc">apache-activemq-4.1.2-bin.tar.gz.asc</a></p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-bin.zip">apache-activemq-4.1.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-bin.zip.asc">apache-activemq-4.1.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-bin.tar.gz">apache-activemq-4.1.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-bin.tar.gz.asc">apache-activemq-4.1.2-bin.tar.gz.asc</a></p></td></tr></tbody></table>
-<h2 id="ActiveMQ4.1.2Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2>
+<h2>Getting the Binaries using Maven 2</h2>
-<p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p>
+<p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1745a3eb-65f2-4234-8e75-0c772cc44a84" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>4.1.2</version>
</dependency>
-]]></script>
-</div></div>
-</div>
+</plain-text-body></structured-macro>
+</rich-text-body></structured-macro>
+
+<h2>Getting the Source Code</h2>
+
+<h3>Source Distributions</h3>
+
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-src.zip">apache-activemq-4.1.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-src.zip.asc">apache-activemq-4.1.2-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-src.tar.gz">apache-activemq-4.1.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-src.tar.gz.asc">apache-activemq-4.1.2-src.tar.gz.asc</a></p></td></tr></tbody></table>
+<h3>SVN Tag Checkout</h3>
-
-<h2 id="ActiveMQ4.1.2Release-GettingtheSourceCode">Getting the Source Code</h2>
-
-<h3 id="ActiveMQ4.1.2Release-SourceDistributions">Source Distributions</h3>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-src.zip">apache-activemq-4.1.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-src.zip.asc">apache-activemq-4.1.2-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-src.tar.gz">apache-activemq-4.1.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/4.1.2/apache-activemq-4.1.2-src.tar.gz.asc">apache-activemq-4.1.2-src.tar.gz.asc</a></p></td></tr></tbody></table></div>
-
-
-<h3 id="ActiveMQ4.1.2Release-SVNTagCheckout">SVN Tag Checkout</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="cab11c13-707c-4236-af36-710492cceb2b" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-4.1.2
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ4.1.2Release-Changelog">Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11801&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
+<h2>Changelog</h2>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11801&styleName=Html&projectId=10520&Create=Create">release notes</a></p>
-<div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
+<structured-macro ac:macro-id="b3cfbe4b-3b3f-4e40-96a2-7fa80738b266" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="columns">type;key;summary</parameter><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=10520&fixfor=11801&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro>
-
-<p>Also see the previous <a shape="rect" href="activemq-411-release.xml">ActiveMQ 4.1.1 Release</a></p></div>
+<p>Also see the previous <link><page ri:content-title="ActiveMQ 4.1.1 Release"></page></link></p></div>
diff --git a/activemq-500-release.xml b/activemq-500-release.xml
index 9a5b12d..a7b7c81 100644
--- a/activemq-500-release.xml
+++ b/activemq-500-release.xml
@@ -1,45 +1,28 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="/confluence/download/attachments/72278/activemq-5.x-box-reflection.png?version=1&modificationDate=1207832700000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59671794" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="activemq-5.x-box-reflection.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="72278" data-linked-resource-container-version="14"></span></p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="921c3ad5-f110-467b-bb7d-7d9b55a9522a" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><attachment ri:filename="activemq-5.x-box-reflection.png"></attachment></image></p></rich-text-body></structured-macro><structured-macro ac:macro-id="ce86d20d-34ec-4b96-b6cc-8b5cb02c3705" ac:name="div" ac:schema-version="1"><parameter ac:name="style">min-height:200px</parameter><rich-text-body>
+
+<structured-macro ac:macro-id="a026b8c3-72f3-403d-a6c6-021861aa59ce" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.0"></page></link></parameter></structured-macro>
+
+<h2>Getting the Binary Distributions</h2>
-<div style="min-height:200px">
-
-<h2 id="ActiveMQ5.0.0Release-NewFeaturesin5.0">New Features in 5.0</h2>
-
-<p>In the 5.0 release of Apache ActiveMQ there are the following new features:</p>
-
-<ul><li><a shape="rect" href="amq-message-store.xml">AMQ Message Store</a> (Faster Persistence!)</li><li><a shape="rect" href="message-cursors.xml">Message Cursors</a> (To handle very large number of stored messages)</li><li><a shape="rect" href="blob-messages.xml">Blob Messages</a></li><li><a shape="rect" href="command-agent.xml">Command Agent</a></li><li><a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> via <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Camel Integration</a></li><li><a shape="rect" href="logging-a-warning-if-you-forget-to-start-a-connection.xml">Logging a warning if you forget to start a Connection</a></li><li><a shape="rect" href="message-transformation.xml">Message Transformation</a></li><li><a shape="rect" href="mirrored-queues.xml">Mirrored Queues</a></li><li><a shape="rect" href="producer-flow-control.xml">Producer Flow Control</a></li></ul>
-
-<h2 id="ActiveMQ5.0.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0.zip">apache-activemq-5.0.0.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0.zip.asc">apache-activemq-5.0.0.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0.tar.gz">apache-activemq-5.0.0.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0.tar.gz.asc">apache-activemq-5.0.0.tar.gz.asc</a></p></td></tr></tbody></table>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0.zip">apache-activemq-5.0.0.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0.zip.asc">apache-activemq-5.0.0.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0.tar.gz">apache-activemq-5.0.0.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0.tar.gz.asc">apache-activemq-5.0.0.tar.gz.asc</a></p></td></tr></tbody></table></div>
+<structured-macro ac:macro-id="196f5825-a4a1-4fcd-a316-82ac54d91923" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Do not use Safari to download, the above URLs use redirection</parameter><rich-text-body>
+<p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" href="http://www.mozilla.com/en-US/firefox/">FireFox</a></p></rich-text-body></structured-macro>
+<h2>Getting the Binaries using Maven 2</h2>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Do not use Safari to download, the above URLs use redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" class="external-link" href="http://www.mozilla.com/en-US/firefox/" rel="nofollow">FireFox</a></p></div></div>
+<p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p>
-<h2 id="ActiveMQ5.0.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2>
-
-<p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="be4e8bb9-5179-4982-a18a-1653698cac71" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.0.0</version>
</dependency>
-]]></script>
-</div></div>
-</div>
-
-
-<h2 id="ActiveMQ5.0.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.0.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0-src.zip">apache-activemq-5.0.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0-src.zip.asc">apache-activemq-5.0.0-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0-src.tar.gz">apache-activemq-5.0.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0-src.tar.gz.asc">apache-activemq-5.0.0-src.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.0.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.0.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.0.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11712&styleName=Html&projectId=10520&Create=Create">release notes</a></p><p></p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
-<p>Also see the previous <a shape="rect" href="activemq-411-release.xml">ActiveMQ 4.1.1 Release</a></p></div>
+</plain-text-body></structured-macro>
+</rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0-src.zip">apache-activemq-5.0.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0-src.zip.asc">apache-activemq-5.0.0-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0-src.tar.gz">apache-activemq-5.0.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apache-activemq-5.0.0-src.tar.gz.asc">apache-activemq-5.0.0-src.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="9a8558b6-ff9b-47aa-b6e6-1e3cd4e1c992" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.0.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11712&styleName=Html&projectId=10520&Create=Create">release notes</a></p><p><structured-macro ac:macro-id="58aa6862-801e-4b2a-b296-a9e50b5f9259" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="columns">type;key;summary</parameter><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=10520&fixfor=11712&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 4.1.1 Release"></page></link></p></div>
diff --git a/activemq-510-release.xml b/activemq-510-release.xml
index a831dd6..e79abf2 100644
--- a/activemq-510-release.xml
+++ b/activemq-510-release.xml
@@ -1,46 +1,23 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="3a4d805f-5a60-4fe0-9d1e-092bf9446812" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><structured-macro ac:macro-id="0f60386e-cdcc-429b-bbf3-96f0ef2b5c54" ac:name="div" ac:schema-version="1"><parameter ac:name="style">min-height:200px</parameter><rich-text-body>
+
+<structured-macro ac:macro-id="d62d6b9c-662a-4fe8-89d6-03c8c27c9db6" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.1"></page></link></parameter></structured-macro>
+
+<h2>Getting the Binary Distributions</h2>
-<div style="min-height:200px">
-
-<h2 id="ActiveMQ5.1.0Release-NewFeaturesin5.1">New Features in 5.1</h2>
-
-<p>In the 5.1.x release of Apache ActiveMQ there are the following new features:</p>
-
-<ul><li>You can use the new <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/DestinationSource.html">DestinationSource</a> on an ActiveMQConnection to access the available queues or topics or listen to queues/topics being created or deleted.
-<h2 id="ActiveMQ5.1.0Release-NewFeaturesin5.1.1">New Features in 5.1</h2></li><li>Support for more graceful handling of <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ-1517">timeouts within MessageProducer.send</a></li><li>Add the option for a <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ-1572">backup channel that is already connected for the Failover transport</a></li><li>ActiveMQ configuration can now validate against an XSD which means that it can be embedded in a spring configuration file.</li><li>Stomp can now handle delivering Map and Object messages.</li></ul>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-bin.zip">apache-activemq-5.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/apache-activemq-5.1.0-bin.zip.asc">apache-activemq-5.1.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-bin.tar.gz">apache-activemq-5.1.0-bin.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-bin.tar.gz.asc">apache-activemq-5.1.0-bin.tar.gz.asc</a></p></td></tr></tbody></table>
+<structured-macro ac:macro-id="f470ad0a-c90b-4aed-ae1c-a47258e4bbf7" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Do not use Safari to download, the above URLs use redirection</parameter><rich-text-body>
+<p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" href="http://www.mozilla.com/en-US/firefox/">FireFox</a></p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ5.1.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2>
+<structured-macro ac:macro-id="52a39382-420f-473f-b1ee-7c98a4a63d05" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro>
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-bin.zip">apache-activemq-5.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/apache-activemq-5.1.0-bin.zip.asc">apache-activemq-5.1.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-bin.tar.gz">apache-activemq-5.1.0-bin.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-bin.tar.gz.asc">apache-activemq-5.1.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div>
-
-
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Do not use Safari to download, the above URLs use redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" class="external-link" href="http://www.mozilla.com/en-US/firefox/" rel="nofollow">FireFox</a></p></div></div>
-
-<h2 id="ActiveMQ5.1.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul>
-
-<div class="confluence-information-macro confluence-information-macro-tip"><p class="title">Error When Expanding Tarballs</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<structured-macro ac:macro-id="1039a25b-c5ed-4fa0-8c2e-0bccd4ff54e7" ac:name="tip" ac:schema-version="1"><parameter ac:name="title">Error When Expanding Tarballs</parameter><rich-text-body>
<p>When expanding the binary tarballs you might wind up experiencing the following: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e796ae17-de14-452c-97a2-48a300eb1828" ac:name="code" ac:schema-version="1"><plain-text-body>
$ tar zxvf /path/to/apache-activemq-5.1.0-bin.tar.gz
apache-activemq-5.1.0/bin/run.jar
apache-activemq-5.1.0/activemq-all-5.1.0.jar
@@ -52,32 +29,21 @@
tar: Unexpected EOF in archive
tar: A lone zero block at 61740
tar: Error exit delayed from previous errors
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>These errors are a product of an open <a shape="rect" class="external-link" href="http://jira.codehaus.org/browse/MASSEMBLY-302" rel="nofollow">bug in Maven</a> and are innocuous and won't affect anything.</p></div></div>
+<p>These errors are a product of an open <a shape="rect" href="http://jira.codehaus.org/browse/MASSEMBLY-302">bug in Maven</a> and are innocuous and won't affect anything.</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ5.1.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2>
+<h2>Getting the Binaries using Maven 2</h2>
-<p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p>
+<p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c6bf1393-c057-4f86-821b-9bfd3c176877" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.1.0</version>
</dependency>
-]]></script>
-</div></div>
-</div>
-
-
-<h2 id="ActiveMQ5.1.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.1.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-src.zip">apache-activemq-5.1.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-src.zip.asc">apache-activemq-5.1.0-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-src.tar.gz">apache-activemq-5.1.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-src.tar.gz.asc">apache-activemq-5.1.0-src.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.1.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.1.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.1.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11802&styleName=Html&projectId=10520&Create=Create">release notes</a></p><p></p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
-<p>Also see the previous <a shape="rect" href="activemq-500-release.xml">ActiveMQ 5.0.0 Release</a></p></div>
+</plain-text-body></structured-macro>
+</rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-src.zip">apache-activemq-5.1.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-src.zip.asc">apache-activemq-5.1.0-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-src.tar.gz">apache-activemq-5.1.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.1.0/apache-activemq-5.1.0-src.tar.gz.asc">apache-activemq-5.1.0-src.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="e95d37ce-297f-4204-9eed-717027d99571" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.1.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11802&styleName=Html&projectId=10520&Create=Create">release notes</a></p><p><structured-macro ac:macro-id="8642b5a0-fa7e-4975-95bf-3ab5e6147c11" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="columns">type;key;summary</parameter><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=10520&fixfor=11802&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.0.0 Release"></page></link></p></div>
diff --git a/activemq-5100-release.xml b/activemq-5100-release.xml
index 8454334..70d2c56 100644
--- a/activemq-5100-release.xml
+++ b/activemq-5100-release.xml
@@ -1,27 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.10.0Release-ActiveMQ5.10.0Release">ActiveMQ 5.10.0 Release</h2><p>Apache ActiveMQ 5.10.0 resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5061?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.0%20ORDER%20BY%20status%20DESC%2C%20priority%20DESC">more than 234 issues</a>, mostly bug fixes and improvements. It has the following new features:</p><h3 id="ActiveMQ5.10.0Release-NewFeaturesandnoteworthyimprovementsandfixes">New Features and noteworthy improvements and fixes</h3><ul><li>Java 8 support</li><li>Apache Shiro Security Plugin - <a shape="rect" class="external-link" href="http://activemq.apache.org/shiro.html">http://activemq.apache.org/shiro.html</a></li><li>Hardened MQTT support</li><li>Hardened AMQP support</li><li>Hardened LevelDB store</li><li>Improved RAR/JCA adapter</li><li>Improved Runtime configuration plugin</li><li>Improved Web console</li></ul><h3 id="ActiveMQ5.10.0Release-MigrationGuide">Migration Guide</h3><ul><li>Removed <code>org.apache.activemq.camel.converter.IdentityMessageReuseConverter</code> class from the <code>activemq-camel</code> component.</li></ul><h2 id="ActiveMQ5.10.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.0/apache-activemq-5.10.0-bin.zip">apache-activemq-5.10.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.0/apache-activemq-5.10.0-bin.zip.asc">apache-activemq-5.10.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.0/apache-activemq-5.10.0-bin.tar.gz">apache-activemq-5.10.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.0/apache-activemq-5.10.0-bin.tar.gz.asc">apache-activemq-5.10.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.10.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.10.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="2b816b48-0ce8-4428-9f7a-3ce13990b456" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.10.0 Release</h2><p>Apache ActiveMQ 5.10.0 resolves <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5061?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.0%20ORDER%20BY%20status%20DESC%2C%20priority%20DESC">more than 234 issues</a>, mostly bug fixes and improvements. It has the following new features:</p><h3>New Features and noteworthy improvements and fixes</h3><ul><li>Java 8 support</li><li>Apache Shiro Security Plugin - <a shape="rect" href="http://activemq.apache.org/shiro.html">http://activemq.apache.org/shiro.html</a></li><li>Hardened MQTT support</li><li>Hardened AMQP support</li><li>Hardened LevelDB store</li><li>Improved RAR/JCA adapter</li><li>Improved Runtime configuration plugin</li><li>Improved Web console</li></ul><h3>Migration Guide</h3><ul><li>Removed <code>org.apache.activemq.camel.converter.IdentityMessageReuseConverter</code> class from the <code>activemq-camel</code> component.</li></ul><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.0/apache-activemq-5.10.0-bin.zip">apache-activemq-5.10.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.0/apache-activemq-5.10.0-bin.zip.asc">apache-activemq-5.10.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.0/apache-activemq-5.10.0-bin.tar.gz">apache-activemq-5.10.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.0/apache-activemq-5.10.0-bin.tar.gz.asc">apache-activemq-5.10.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="22429d97-e64a-4d5a-a414-f45c4a71f6af" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="68d18794-fb7b-463d-8646-351f4e4bb4f8" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.10.0</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.10.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.10.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.10.0/activemq-parent-5.10.0-source-release.zip">activemq-parent-5.10.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.10.0/activemq-parent-5.10.0-source-release.zip.asc">activemq-parent-5.10.0-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.10.0Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.0</a></p><h2 id="ActiveMQ5.10.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324950">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-590-release.xml">ActiveMQ 5.9.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="c4f08922-bdc7-4ccc-b40c-959a578a51f2" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.10.0/activemq-parent-5.10.0-source-release.zip">activemq-parent-5.10.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.10.0/activemq-parent-5.10.0-source-release.zip.asc">activemq-parent-5.10.0-source-release.zip.asc</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.0</a></p><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324950">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.9.0 Release"></page></link></p></div>
diff --git a/activemq-5101-release.xml b/activemq-5101-release.xml
index 42879a3..5669e1a 100644
--- a/activemq-5101-release.xml
+++ b/activemq-5101-release.xml
@@ -1,27 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.10.1Release-ActiveMQ5.10.1Release">ActiveMQ 5.10.1 Release</h2><p>Apache ActiveMQ 5.10.1 resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5514?jql=fixVersion%20%3D%205.10.1%20AND%20project%20%3D%20AMQ">33 issues</a>, mostly bug fixes.</p><h3 id="ActiveMQ5.10.1Release-GettingtheBinaryDistributions"><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.1/apache-activemq-5.10.1-bin.zip">apache-activemq-5.10.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.1/apache-activemq-5.10.1-bin.zip.asc">apache-activemq-5.10.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.1/apache-activemq-5.10.1-bin.tar.gz">apache-activemq-5.10.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.1/apache-activemq-5.10.1-bin.tar.gz.asc">apache-activemq-5.10.1-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.10.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.10.1Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="87e9bf30-9a8a-4aef-b07c-763a2f49a1cf" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.10.1 Release</h2><p>Apache ActiveMQ 5.10.1 resolves <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5514?jql=fixVersion%20%3D%205.10.1%20AND%20project%20%3D%20AMQ">33 issues</a>, mostly bug fixes.</p><h3><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.1/apache-activemq-5.10.1-bin.zip">apache-activemq-5.10.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.1/apache-activemq-5.10.1-bin.zip.asc">apache-activemq-5.10.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.1/apache-activemq-5.10.1-bin.tar.gz">apache-activemq-5.10.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.1/apache-activemq-5.10.1-bin.tar.gz.asc">apache-activemq-5.10.1-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="d9e7c120-555c-4df2-908d-62a8e6d0ba0a" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="067bb458-fa21-4f3e-8b63-835ba93a7094" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.10.1</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.10.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.10.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.10.1/activemq-parent-5.10.1-source-release.zip">activemq-parent-5.10.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.10.1/activemq-parent-5.10.1-source-release.zip.asc">activemq-parent-5.10.1-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.10.1Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.1</a></p><h2 id="ActiveMQ5.10.1Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12326456">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-5100-release.xml">ActiveMQ 5.10.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="f43d3185-ed06-471c-9bf1-19a2e1fc09f3" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.10.1/activemq-parent-5.10.1-source-release.zip">activemq-parent-5.10.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.10.1/activemq-parent-5.10.1-source-release.zip.asc">activemq-parent-5.10.1-source-release.zip.asc</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.1</a></p><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12326456">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.10.0 Release"></page></link></p></div>
diff --git a/activemq-5102-release.xml b/activemq-5102-release.xml
index e25fd6e..cc6999c 100644
--- a/activemq-5102-release.xml
+++ b/activemq-5102-release.xml
@@ -1,27 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.10.2Release-ActiveMQ5.10.2Release">ActiveMQ 5.10.2 Release</h2><p>Apache ActiveMQ 5.10.2 resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.2">2 issues</a>, both bug fixes.</p><h3 id="ActiveMQ5.10.2Release-GettingtheBinaryDistributions"><span>Getting the Binary Distributions</span></h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.10.2/apache-activemq-5.10.2-bin.zip">apache-activemq-5.10.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.10.2/apache-activemq-5.10.2-bin.zip.asc">apache-activemq-5.10.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.10.2/apache-activemq-5.10.2-bin.tar.gz">apache-activemq-5.10.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.10.2/apache-activemq-5.10.2-bin.tar.gz.asc">apache-activemq-5.10.2-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.10.2Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.10.2Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="2939d36d-7f54-4a70-8c2e-734014a5eff0" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.10.2 Release</h2><p>Apache ActiveMQ 5.10.2 resolves <a shape="rect" href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.2">2 issues</a>, both bug fixes.</p><h3><span>Getting the Binary Distributions</span></h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.10.2/apache-activemq-5.10.2-bin.zip">apache-activemq-5.10.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.10.2/apache-activemq-5.10.2-bin.zip.asc">apache-activemq-5.10.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.10.2/apache-activemq-5.10.2-bin.tar.gz">apache-activemq-5.10.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.10.2/apache-activemq-5.10.2-bin.tar.gz.asc">apache-activemq-5.10.2-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="8f5aa4d1-456e-4952-96e7-af4f6fd37e33" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="95101944-74fe-438e-984e-95532caab72b" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.10.2</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.10.2Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.10.2Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.10.2/activemq-parent-5.10.2-source-release.zip">activemq-parent-5.10.2-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.10.2/activemq-parent-5.10.2-source-release.zip.asc">activemq-parent-5.10.2-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.10.2Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.2</a></p><h2 id="ActiveMQ5.10.2Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329390">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-5100-release.xml">ActiveMQ 5.10.1 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="70b40244-080e-414e-8345-5c612650771f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.10.2/activemq-parent-5.10.2-source-release.zip">activemq-parent-5.10.2-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.10.2/activemq-parent-5.10.2-source-release.zip.asc">activemq-parent-5.10.2-source-release.zip.asc</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.10.2</a></p><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329390">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.10.0 Release"></page><plain-text-link-body>ActiveMQ 5.10.1 Release</plain-text-link-body></link></p></div>
diff --git a/activemq-5110-release.xml b/activemq-5110-release.xml
index 2fcf185..da8c2b9 100644
--- a/activemq-5110-release.xml
+++ b/activemq-5110-release.xml
@@ -1,24 +1,7 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ5.11.0Release-ActiveMQ5.11.0Release">ActiveMQ 5.11.0 Release</h2><p>Apache ActiveMQ 5.11.0 resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.11.0%20AND%20project%20%3D%20AMQ">more than 130 issues</a>, mostly bug fixes and improvements. It is build with and requires jdk 1.7</p><p></p><h2 id="ActiveMQ5.11.0Release-NewFeaturesin5.11.0">New Features in 5.11.0</h2><ul class="alternate"><li><span style="line-height: 1.4285715;">Destination import/export for lock down mode <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5218">AMQ-5218</a></span></li><li><p>Dynamic camel root loading <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5351">AMQ-5351</a></p></li><li><p>MQTT - QOS2 mapped to virtual topics <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5290">AMQ-5290</a></p></li><li>start scripts simplification <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5378">AMQ-5378</a></li><li>Recover scheduler database option <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3758">AMQ-3758</a></li><li>Jetty 8</li><li>Karaf 2.4.1</li></ul><h2 id="ActiveMQ5.11.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.11.0/apache-activemq-5.11.0-bin.zip">apache-activemq-5.11.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.11.0/apache-activemq-5.11.0-bin.zip.asc">apache-activemq-5.11.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.11.0/apache-activemq-5.11.0-bin.tar.gz">apache-activemq-5.11.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.11.0/apache-activemq-5.11.0-bin.tar.gz.asc">apache-activemq-5.11.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.11.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.11.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><h2>ActiveMQ 5.11.0 Release</h2><p>Apache ActiveMQ 5.11.0 resolves <a shape="rect" href="https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.11.0%20AND%20project%20%3D%20AMQ">more than 130 issues</a>, mostly bug fixes and improvements. It is build with and requires jdk 1.7</p><p><structured-macro ac:macro-id="040e0ddd-57d4-4e33-add5-cd6a987016ec" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.11"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.11.0/apache-activemq-5.11.0-bin.zip">apache-activemq-5.11.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.11.0/apache-activemq-5.11.0-bin.zip.asc">apache-activemq-5.11.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.11.0/apache-activemq-5.11.0-bin.tar.gz">apache-activemq-5.11.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.11.0/apache-activemq-5.11.0-bin.tar.gz.asc">apache-activemq-5.11.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="dd53c3d9-5de0-4c37-aee0-d527229b69fd" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="100579c4-0862-40d1-ad3f-2fba066f4d24" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.11.0</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.11.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.11.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.11.0/activemq-parent-5.11.0-source-release.zip">activemq-parent-5.11.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.0/activemq-parent-5.11.0-source-release.zip.asc">activemq-parent-5.11.0-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.11.0Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.0</a></p><h2 id="ActiveMQ5.11.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324951&projectId=12311210">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-5100-release.xml">ActiveMQ 5.10.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="91c55dac-7402-4731-83fb-ae1c63f43e62" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.11.0/activemq-parent-5.11.0-source-release.zip">activemq-parent-5.11.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.0/activemq-parent-5.11.0-source-release.zip.asc">activemq-parent-5.11.0-source-release.zip.asc</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.0</a></p><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324951&projectId=12311210">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.10.0 Release"></page></link></p></div>
diff --git a/activemq-5111-release.xml b/activemq-5111-release.xml
index 73f7352..a13d45c 100644
--- a/activemq-5111-release.xml
+++ b/activemq-5111-release.xml
@@ -1,27 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.11.1Release-ActiveMQ5.11.1Release">ActiveMQ 5.11.1 Release</h2><p>Apache ActiveMQ 5.11.1 resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.11.1">6 issues</a>, mostly bug fixes.</p><h3 id="ActiveMQ5.11.1Release-GettingtheBinaryDistributions"><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.11.1/apache-activemq-5.11.1-bin.zip">apache-activemq-5.11.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.11.1/apache-activemq-5.11.1-bin.zip.asc">apache-activemq-5.11.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/5.11.1/apache-activemq-5.11.1-bin.tar.gz">apache-activemq-5.11.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.11.1/apache-activemq-5.11.1-bin.tar.gz.asc">apache-activemq-5.11.1-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.11.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.11.1Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.11.1 Release</h2><p>Apache ActiveMQ 5.11.1 resolves <a shape="rect" href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.11.1">6 issues</a>, mostly bug fixes.</p><h3><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.11.1/apache-activemq-5.11.1-bin.zip">apache-activemq-5.11.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.11.1/apache-activemq-5.11.1-bin.zip.asc">apache-activemq-5.11.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/5.11.1/apache-activemq-5.11.1-bin.tar.gz">apache-activemq-5.11.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.11.1/apache-activemq-5.11.1-bin.tar.gz.asc">apache-activemq-5.11.1-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.11.1</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.11.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.11.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.11.1/activemq-parent-5.11.1-source-release.zip">activemq-parent-5.11.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.11.1/activemq-parent-5.11.1-source-release.zip.asc">activemq-parent-5.11.1-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.11.1Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.1</a></p><h2 id="ActiveMQ5.11.1Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329382">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-5110-release.xml">ActiveMQ 5.11.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.11.1/activemq-parent-5.11.1-source-release.zip">activemq-parent-5.11.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.11.1/activemq-parent-5.11.1-source-release.zip.asc">activemq-parent-5.11.1-source-release.zip.asc</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.1</a></p><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329382">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.11.0 Release"></page></link></p></div>
diff --git a/activemq-5112-release.xml b/activemq-5112-release.xml
index eebaa3e..ca1e752 100644
--- a/activemq-5112-release.xml
+++ b/activemq-5112-release.xml
@@ -1,27 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.11.2Release-ActiveMQ5.11.2Release">ActiveMQ 5.11.2 Release</h2><p>Apache ActiveMQ 5.11.2 resolves several<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329669"> issues</a>, mostly bug fixes.</p><h3 id="ActiveMQ5.11.2Release-GettingtheBinaryDistributions"><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.2/apache-activemq-5.11.2-bin.zip">apache-activemq-5.11.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.2/apache-activemq-5.11.2-bin.zip.asc">apache-activemq-5.11.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.2/apache-activemq-5.11.2-bin.tar.gz">apache-activemq-5.11.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.2/apache-activemq-5.11.2-bin.tar.gz.asc">apache-activemq-5.11.2-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.11.2Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.11.2Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.11.2 Release</h2><p>Apache ActiveMQ 5.11.2 resolves several<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329669"> issues</a>, mostly bug fixes.</p><h3><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.2/apache-activemq-5.11.2-bin.zip">apache-activemq-5.11.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.2/apache-activemq-5.11.2-bin.zip.asc">apache-activemq-5.11.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.2/apache-activemq-5.11.2-bin.tar.gz">apache-activemq-5.11.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.2/apache-activemq-5.11.2-bin.tar.gz.asc">apache-activemq-5.11.2-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.11.2</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.11.2Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.11.2Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.11.2/activemq-parent-5.11.2-source-release.zip">activemq-parent-5.11.2-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.11.2/activemq-parent-5.11.2-source-release.zip.asc">activemq-parent-5.11.2-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.11.2Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.1</a></p><h2 id="ActiveMQ5.11.2Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329669">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-5111-release.xml">ActiveMQ 5.11.1 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.11.2/activemq-parent-5.11.2-source-release.zip">activemq-parent-5.11.2-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.11.2/activemq-parent-5.11.2-source-release.zip.asc">activemq-parent-5.11.2-source-release.zip.asc</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.1</a></p><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329669">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.11.1 Release"></page></link></p></div>
diff --git a/activemq-5113-release.xml b/activemq-5113-release.xml
index dc5f65e..c015434 100644
--- a/activemq-5113-release.xml
+++ b/activemq-5113-release.xml
@@ -1,27 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.11.3Release-ActiveMQ5.11.3Release">ActiveMQ 5.11.3 Release</h2><p>Apache ActiveMQ 5.11.3 resolves several<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329669"> issues</a>, mostly bug fixes.</p><h3 id="ActiveMQ5.11.3Release-GettingtheBinaryDistributions"><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.3/apache-activemq-5.11.3-bin.zip">apache-activemq-5.11.3-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.3/apache-activemq-5.11.3-bin.zip.asc">apache-activemq-5.11.3-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.3/apache-activemq-5.11.3-bin.tar.gz">apache-activemq-5.11.3-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.11.3/apache-activemq-5.11.3-bin.tar.gz.asc">apache-activemq-5.11.3-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.11.3Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.11.3Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.11.3 Release</h2><p>Apache ActiveMQ 5.11.3 resolves several<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329669"> issues</a>, mostly bug fixes.</p><h3><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.3/apache-activemq-5.11.3-bin.zip">apache-activemq-5.11.3-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.3/apache-activemq-5.11.3-bin.zip.asc">apache-activemq-5.11.3-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.3/apache-activemq-5.11.3-bin.tar.gz">apache-activemq-5.11.3-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.11.3/apache-activemq-5.11.3-bin.tar.gz.asc">apache-activemq-5.11.3-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.11.3</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.11.3Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.11.3Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.11.3/activemq-parent-5.11.3-source-release.zip">activemq-parent-5.11.3-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.11.3/activemq-parent-5.11.3-source-release.zip.asc">activemq-parent-5.11.3-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.11.3Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.3">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.3</a></p><h2 id="ActiveMQ5.11.3Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333254">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-5112-release.xml">ActiveMQ 5.11.2 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.11.3/activemq-parent-5.11.3-source-release.zip">activemq-parent-5.11.3-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.11.3/activemq-parent-5.11.3-source-release.zip.asc">activemq-parent-5.11.3-source-release.zip.asc</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.3">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.11.3</a></p><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333254">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.11.2 Release"></page></link></p></div>
diff --git a/activemq-5120-release.xml b/activemq-5120-release.xml
index 25e62f7..10be526 100644
--- a/activemq-5120-release.xml
+++ b/activemq-5120-release.xml
@@ -1,27 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.12.0Release-ActiveMQ5.12.0Release">ActiveMQ 5.12.0 Release</h2><p>Apache ActiveMQ 5.12.0 resolves several<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329258"> issues</a>, and provides significant improves to the <a shape="rect" href="amqp.xml">AMQP</a> and <a shape="rect" href="mqtt.xml">MQTT</a> support in the broker as well as fixing issues with <a shape="rect" href="stomp.xml">STOMP</a> and <a shape="rect" href="mqtt.xml">MQTT</a> over WebSockets plus much much more.</p><h3 id="ActiveMQ5.12.0Release-GettingtheBinaryDistributions"><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.zip">apache-activemq-5.12.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.tar.gz">apache-activemq-5.12.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.12.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.12.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.12.0 Release</h2><p>Apache ActiveMQ 5.12.0 resolves several<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329258"> issues</a>, and provides significant improves to the <link><page ri:content-title="AMQP"></page></link> and <link><page ri:content-title="MQTT"></page></link> support in the broker as well as fixing issues with <link><page ri:content-title="Stomp"></page><plain-text-link-body>STOMP</plain-text-link-body></link> and <link><page ri:content-title="MQTT"></page></link> over WebSockets plus much much more.</p><h3><span style="font-size: 20.0px;font-weight: normal;line-height: 1.5;">Getting the Binary Distributions</span></h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.zip">apache-activemq-5.12.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.tar.gz">apache-activemq-5.12.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.0/apache-activemq-5.12.0-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.12.0</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.12.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.12.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.0/activemq-parent-5.12.0-source-release.zip">activemq-parent-5.12.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.0/activemq-parent-5.12.0-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.0/activemq-parent-5.12.0-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.0/activemq-parent-5.12.0-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.12.0Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.0</a></p><h2 id="ActiveMQ5.12.0Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329258">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-5112-release.xml">ActiveMQ 5.11.2 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.0/activemq-parent-5.12.0-source-release.zip">activemq-parent-5.12.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.12.0/activemq-parent-5.12.0-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.0/activemq-parent-5.12.0-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.0/activemq-parent-5.12.0-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.0</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329258">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.11.2 Release"></page></link></p></div>
diff --git a/activemq-5121-release.xml b/activemq-5121-release.xml
index faf3423..6319c37 100644
--- a/activemq-5121-release.xml
+++ b/activemq-5121-release.xml
@@ -1,27 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.12.1Release-ActiveMQ5.12.1Release">ActiveMQ 5.12.1 Release</h2><p>Apache ActiveMQ 5.12.1 includes several improvements and resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269"> issues</a></p><h3 id="ActiveMQ5.12.1Release-GettingtheBinaryDistributions"><span>Getting the Binary Distributions</span></h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.zip">apache-activemq-5.12.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.tar.gz">apache-activemq-5.12.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.12.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.12.1Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.12.1 Release</h2><p>Apache ActiveMQ 5.12.1 includes several improvements and resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269"> issues</a></p><h3><span>Getting the Binary Distributions</span></h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.zip">apache-activemq-5.12.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.tar.gz">apache-activemq-5.12.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.12.1/apache-activemq-5.12.1-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.12.1</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.12.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.12.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.1/activemq-parent-5.12.1-source-release.zip">activemq-parent-5.12.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.1/activemq-parent-5.12.1-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.1/activemq-parent-5.12.1-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.1/activemq-parent-5.12.1-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.12.1Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.1</a></p><h2 id="ActiveMQ5.12.1Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-5120-release.xml">ActiveMQ 5.12.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.1/activemq-parent-5.12.1-source-release.zip">activemq-parent-5.12.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.12.1/activemq-parent-5.12.1-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.1/activemq-parent-5.12.1-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.1/activemq-parent-5.12.1-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.1</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.12.0 Release"></page></link></p></div>
diff --git a/activemq-5122-release.xml b/activemq-5122-release.xml
index 9bbd7d9..8d44cda 100644
--- a/activemq-5122-release.xml
+++ b/activemq-5122-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.12.2Release-ActiveMQ5.12.2Release">ActiveMQ 5.12.2 Release</h2><p>Apache ActiveMQ 5.12.2 includes several improvements and resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269"> issues</a></p><h3 id="ActiveMQ5.12.2Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.2/apache-activemq-5.12.2-bin.zip">apache-activemq-5.12.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.2/apache-activemq-5.12.2-bin.tar.gz">apache-activemq-5.12.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.12.2Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.12.2Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.12.2 Release</h2><p>Apache ActiveMQ 5.12.2 includes several improvements and resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333269"> issues</a></p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.2/apache-activemq-5.12.2-bin.zip">apache-activemq-5.12.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.2/apache-activemq-5.12.2-bin.tar.gz">apache-activemq-5.12.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/apache-activemq-5.12.2-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.12.2</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.12.2Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.12.2Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.2/activemq-parent-5.12.2-source-release.zip">activemq-parent-5.12.2-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/activemq-parent-5.12.2-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/activemq-parent-5.12.2-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.12.2/activemq-parent-5.12.2-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.12.2Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.2</a></p><h2 id="ActiveMQ5.12.2Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333874">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p>Also see the previous <a shape="rect" href="activemq-5121-release.xml">ActiveMQ 5.12.1 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.12.2/activemq-parent-5.12.2-source-release.zip">activemq-parent-5.12.2-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/activemq-parent-5.12.2-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/activemq-parent-5.12.2-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.12.2/activemq-parent-5.12.2-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.12.2</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12333874">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="bc75a322-bf74-4b0c-a476-77cb4c068f65" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.12.1 Release"></page></link></p></div>
diff --git a/activemq-5130-release.xml b/activemq-5130-release.xml
index 7f1ff27..f05ed94 100644
--- a/activemq-5130-release.xml
+++ b/activemq-5130-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.13.0Release-ActiveMQ5.13.0Release">ActiveMQ 5.13.0 Release</h2><p>Apache ActiveMQ 5.13.0 includes several resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848"> issues</a> as well as new features such as the new <a shape="rect" href="auto.xml">auto transport</a> protocol, <a shape="rect" href="networks-of-brokers.xml#NetworksofBrokers-virtualconsumers">dynamic network support for virtual destinations</a>, and much more.</p><h3 id="ActiveMQ5.13.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.zip">apache-activemq-5.13.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.tar.gz">apache-activemq-5.13.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.13.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.13.0Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.13.0 Release</h2><p>Apache ActiveMQ 5.13.0 includes several resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848"> issues</a> as well as new features such as the new <link><page ri:content-title="AUTO"></page><plain-text-link-body>auto transport</plain-text-link-body></link> protocol, <link ac:anchor="virtualconsumers"><page ri:content-title="Networks of Brokers"></page><plain-text-link-body>dynamic network support for virtual destinations</plain-text-link-body></link>, and much more.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.zip">apache-activemq-5.13.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.tar.gz">apache-activemq-5.13.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.13.0/apache-activemq-5.13.0-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.13.0</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.13.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.13.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.13.0/activemq-parent-5.13.0-source-release.zip">activemq-parent-5.13.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.0/activemq-parent-5.13.0-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.0/activemq-parent-5.13.0-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.0/activemq-parent-5.13.0-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.13.0Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.0</a></p><h2 id="ActiveMQ5.13.0Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5121-release.xml">ActiveMQ 5.12.1 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.13.0/activemq-parent-5.13.0-source-release.zip">activemq-parent-5.13.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.13.0/activemq-parent-5.13.0-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.13.0/activemq-parent-5.13.0-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.13.0/activemq-parent-5.13.0-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.0</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329848">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="d7263b8f-20fb-40fd-b3cf-7d4f3152769a" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.12.1 Release"></page></link></p></div>
diff --git a/activemq-5131-release.xml b/activemq-5131-release.xml
index ede92b6..bef26d8 100644
--- a/activemq-5131-release.xml
+++ b/activemq-5131-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.13.1Release-ActiveMQ5.13.1Release">ActiveMQ 5.13.1 Release</h2><p>Apache ActiveMQ 5.13.1 includes over 40 resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334251"> issues</a> and improvements.</p><h3 id="ActiveMQ5.13.1Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.zip">apache-activemq-5.13.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.tar.gz">apache-activemq-5.13.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.13.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.13.1Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.13.1 Release</h2><p>Apache ActiveMQ 5.13.1 includes over 40 resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334251"> issues</a> and improvements.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.zip">apache-activemq-5.13.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.tar.gz">apache-activemq-5.13.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.13.1/apache-activemq-5.13.1-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.13.1</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.13.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.13.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.13.1/activemq-parent-5.13.1-source-release.zip">activemq-parent-5.13.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.1/activemq-parent-5.13.1-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.1/activemq-parent-5.13.1-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.1/activemq-parent-5.13.1-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.13.1Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.1</a></p><h2 id="ActiveMQ5.13.1Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334251">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5130-release.xml">ActiveMQ 5.13.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.13.1/activemq-parent-5.13.1-source-release.zip">activemq-parent-5.13.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.13.1/activemq-parent-5.13.1-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.13.1/activemq-parent-5.13.1-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.13.1/activemq-parent-5.13.1-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.1</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334251">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="a09acd51-e00b-45ea-b58d-d9689ac2f7ac" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.13.0 Release"></page></link></p></div>
diff --git a/activemq-5132-release.xml b/activemq-5132-release.xml
index f963e69..597ad29 100644
--- a/activemq-5132-release.xml
+++ b/activemq-5132-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.13.2Release-ActiveMQ5.13.2Release">ActiveMQ 5.13.2 Release</h2><p>Apache ActiveMQ 5.13.2 includes over 15 resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334774"> issues</a> and improvements.</p><h3 id="ActiveMQ5.13.2Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.zip">apache-activemq-5.13.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.tar.gz">apache-activemq-5.13.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.13.2Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.13.2Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.13.2 Release</h2><p>Apache ActiveMQ 5.13.2 includes over 15 resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334774"> issues</a> and improvements.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.zip">apache-activemq-5.13.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.tar.gz">apache-activemq-5.13.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.2/apache-activemq-5.13.2-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.13.2</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.13.2Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.13.2Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.13.2/activemq-parent-5.13.2-source-release.zip">activemq-parent-5.13.2-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.2/activemq-parent-5.13.2-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.2/activemq-parent-5.13.2-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.13.2/activemq-parent-5.13.2-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.13.2Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.2</a></p><h2 id="ActiveMQ5.13.2Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334774">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5131-release.xml">ActiveMQ 5.13.1 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.13.2/activemq-parent-5.13.2-source-release.zip">activemq-parent-5.13.2-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.13.2/activemq-parent-5.13.2-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.13.2/activemq-parent-5.13.2-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.13.2/activemq-parent-5.13.2-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.2</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334774">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="1fd75519-317d-4f14-a7d7-58e7120af6f8" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.13.1 Release"></page></link></p></div>
diff --git a/activemq-5133-release.xml b/activemq-5133-release.xml
index 35a16a7..bb80dee 100644
--- a/activemq-5133-release.xml
+++ b/activemq-5133-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.13.3Release-ActiveMQ5.13.3Release">ActiveMQ 5.13.3 Release</h2><p>Apache ActiveMQ 5.13.3 includes over 25 resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12335045"> issues</a> and improvements.</p><h3 id="ActiveMQ5.13.3Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.zip">apache-activemq-5.13.3-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.tar.gz">apache-activemq-5.13.3-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.13.3Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.13.3Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.13.3 Release</h2><p>Apache ActiveMQ 5.13.3 includes over 25 resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12335045"> issues</a> and improvements.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.zip">apache-activemq-5.13.3-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.tar.gz">apache-activemq-5.13.3-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/apache-activemq-5.13.3-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.13.3</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.13.3Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.13.3Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/activemq-parent-5.13.3-source-release.zip">activemq-parent-5.13.3-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/activemq-parent-5.13.3-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/activemq-parent-5.13.3-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.3/activemq-parent-5.13.3-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.13.3Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.3">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.3</a></p><h2 id="ActiveMQ5.13.3Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12335045">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5132-release.xml">ActiveMQ 5.13.2 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/activemq-parent-5.13.3-source-release.zip">activemq-parent-5.13.3-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/activemq-parent-5.13.3-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/activemq-parent-5.13.3-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.3/activemq-parent-5.13.3-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.3">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.3</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12335045">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="e6b9ae45-2a20-4d8a-b2b7-90c1feecb76a" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.13.2 Release"></page></link></p></div>
diff --git a/activemq-5134-release.xml b/activemq-5134-release.xml
index cc78fc1..f6fa09b 100644
--- a/activemq-5134-release.xml
+++ b/activemq-5134-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.13.4Release-ActiveMQ5.13.4Release">ActiveMQ 5.13.4 Release</h2><p>Apache ActiveMQ 5.13.4 includes 30 resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12335661&projectId=12311210"> issues</a> and improvements.</p><h3 id="ActiveMQ5.13.4Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.zip">apache-activemq-5.13.4-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.tar.gz">apache-activemq-5.13.4-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.13.4Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.13.4Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.13.4 Release</h2><p>Apache ActiveMQ 5.13.4 includes 30 resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12335661&projectId=12311210"> issues</a> and improvements.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.zip">apache-activemq-5.13.4-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.tar.gz">apache-activemq-5.13.4-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/apache-activemq-5.13.4-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.13.4</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.13.4Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.13.4Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/activemq-parent-5.13.4-source-release.zip">activemq-parent-5.13.4-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/activemq-parent-5.13.4-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/activemq-parent-5.13.4-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.13.4/activemq-parent-5.13.4-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.13.4Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.4">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.4</a></p><h2 id="ActiveMQ5.13.4Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12335661&projectId=12311210">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5133-release.xml">ActiveMQ 5.13.3 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/activemq-parent-5.13.4-source-release.zip">activemq-parent-5.13.4-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/activemq-parent-5.13.4-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/activemq-parent-5.13.4-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.13.4/activemq-parent-5.13.4-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.4">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.13.4</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12335661&projectId=12311210">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="b9818866-8541-4ef2-a060-90d6c813094b" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.13.3 Release"></page></link></p></div>
diff --git a/activemq-5140-release.xml b/activemq-5140-release.xml
index 1b4e702..6696b0f 100644
--- a/activemq-5140-release.xml
+++ b/activemq-5140-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.14.0Release-ActiveMQ5.14.0Release">ActiveMQ 5.14.0 Release</h2><p>Apache ActiveMQ 5.14.0 includes many resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334188"> issues</a>, and provides several new features including AMQP over WebSockets and improved support durable subscriptions over a network bridge.</p><h3 id="ActiveMQ5.14.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.zip">apache-activemq-5.14.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.tar.gz">apache-activemq-5.14.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.14.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.14.0Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.14.0 Release</h2><p>Apache ActiveMQ 5.14.0 includes many resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334188"> issues</a>, and provides several new features including AMQP over WebSockets and improved support durable subscriptions over a network bridge.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.zip">apache-activemq-5.14.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.tar.gz">apache-activemq-5.14.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/apache-activemq-5.14.0-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.14.0</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.14.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.14.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/activemq-parent-5.14.0-source-release.zip">activemq-parent-5.14.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/activemq-parent-5.14.0-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/activemq-parent-5.14.0-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.0/activemq-parent-5.14.0-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.14.0Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.0</a></p><h2 id="ActiveMQ5.14.0Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334188">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5134-release.xml">ActiveMQ 5.13.4 Release</a></p><p> </p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/activemq-parent-5.14.0-source-release.zip">activemq-parent-5.14.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/activemq-parent-5.14.0-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/activemq-parent-5.14.0-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.0/activemq-parent-5.14.0-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.0</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334188">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="dadebb1a-1e2e-438a-bb1f-3cc886c34f12" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.13.4 Release"></page></link></p><p> </p></div>
diff --git a/activemq-5141-release.xml b/activemq-5141-release.xml
index 23c2c3b..6f1627b 100644
--- a/activemq-5141-release.xml
+++ b/activemq-5141-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.14.1Release-ActiveMQ5.14.1Release">ActiveMQ 5.14.1 Release</h2><p>Apache ActiveMQ 5.14.1 includes many resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338124"> issues</a> and bug fixes.</p><h3 id="ActiveMQ5.14.1Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.zip">apache-activemq-5.14.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.tar.gz">apache-activemq-5.14.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.14.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.14.1Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.14.1 Release</h2><p>Apache ActiveMQ 5.14.1 includes many resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338124"> issues</a> and bug fixes.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.zip">apache-activemq-5.14.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.tar.gz">apache-activemq-5.14.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/apache-activemq-5.14.1-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.14.1</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.14.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.14.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/activemq-parent-5.14.1-source-release.zip">activemq-parent-5.14.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/activemq-parent-5.14.1-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/activemq-parent-5.14.1-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.1/activemq-parent-5.14.1-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.14.1Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.1</a></p><h2 id="ActiveMQ5.14.1Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338124">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5140-release.xml">ActiveMQ 5.14.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/activemq-parent-5.14.1-source-release.zip">activemq-parent-5.14.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/activemq-parent-5.14.1-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/activemq-parent-5.14.1-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.1/activemq-parent-5.14.1-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.1</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338124">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="d76d3a07-cefd-42e0-a549-2d68cb893a80" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.14.0 Release"></page></link></p></div>
diff --git a/activemq-5142-release.xml b/activemq-5142-release.xml
index ad67b01..5b9ff3d 100644
--- a/activemq-5142-release.xml
+++ b/activemq-5142-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.14.2Release-ActiveMQ5.14.2Release">ActiveMQ 5.14.2 Release</h2><p>Apache ActiveMQ 5.14.2 includes many resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338329"> issues</a> and bug fixes.</p><h3 id="ActiveMQ5.14.2Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.zip">apache-activemq-5.14.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.tar.gz">apache-activemq-5.14.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.14.2Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.14.2Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.14.2 Release</h2><p>Apache ActiveMQ 5.14.2 includes many resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338329"> issues</a> and bug fixes.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.zip">apache-activemq-5.14.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.tar.gz">apache-activemq-5.14.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/apache-activemq-5.14.2-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.14.2</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.14.2Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.14.2Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/activemq-parent-5.14.2-source-release.zip">activemq-parent-5.14.2-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/activemq-parent-5.14.2-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/activemq-parent-5.14.2-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.2/activemq-parent-5.14.2-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.14.2Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.2</a></p><h2 id="ActiveMQ5.14.2Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338329">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5141-release.xml">ActiveMQ 5.14.1 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/activemq-parent-5.14.2-source-release.zip">activemq-parent-5.14.2-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/activemq-parent-5.14.2-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/activemq-parent-5.14.2-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.2/activemq-parent-5.14.2-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.2</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338329">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="1d77b94e-dec6-4b0c-95b8-ec1808dbd878" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.14.1 Release"></page></link></p></div>
diff --git a/activemq-5143-release.xml b/activemq-5143-release.xml
index b4f18ed..9b8e386 100644
--- a/activemq-5143-release.xml
+++ b/activemq-5143-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.14.3Release-ActiveMQ5.14.3Release">ActiveMQ 5.14.3 Release</h2><p>Apache ActiveMQ 5.14.3 includes several resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338822"> issues</a> and bug fixes.</p><h3 id="ActiveMQ5.14.3Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.zip">apache-activemq-5.14.3-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz">apache-activemq-5.14.3-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.14.3Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.14.3Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.14.3 Release</h2><p>Apache ActiveMQ 5.14.3 includes several resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338822"> issues</a> and bug fixes.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.zip">apache-activemq-5.14.3-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz">apache-activemq-5.14.3-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/apache-activemq-5.14.3-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.14.3</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.14.3Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.14.3Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/activemq-parent-5.14.3-source-release.zip">activemq-parent-5.14.3-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/activemq-parent-5.14.3-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/activemq-parent-5.14.3-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.3/activemq-parent-5.14.3-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.14.3Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.3">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.3</a></p><h2 id="ActiveMQ5.14.3Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338822">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5142-release.xml">ActiveMQ 5.14.2 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/activemq-parent-5.14.3-source-release.zip">activemq-parent-5.14.3-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/activemq-parent-5.14.3-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/activemq-parent-5.14.3-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.3/activemq-parent-5.14.3-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.3">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.3</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338822">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="aaded409-2824-4b78-b519-30e72bc5e113" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.14.2 Release"></page></link></p></div>
diff --git a/activemq-5144-release.xml b/activemq-5144-release.xml
index 5504c35..cdb9dc5 100644
--- a/activemq-5144-release.xml
+++ b/activemq-5144-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.14.4Release-ActiveMQ5.14.4Release">ActiveMQ 5.14.4 Release</h2><p>Apache ActiveMQ 5.14.4 includes several resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338909"> issues</a> and bug fixes.</p><h3 id="ActiveMQ5.14.4Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.zip">apache-activemq-5.14.4-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.tar.gz">apache-activemq-5.14.4-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.14.4Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.14.4Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.14.4 Release</h2><p>Apache ActiveMQ 5.14.4 includes several resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338909"> issues</a> and bug fixes.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.zip">apache-activemq-5.14.4-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.tar.gz">apache-activemq-5.14.4-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/apache-activemq-5.14.4-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.14.4</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.14.4Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.14.4Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/activemq-parent-5.14.4-source-release.zip">activemq-parent-5.14.4-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/activemq-parent-5.14.4-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/activemq-parent-5.14.4-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.14.4/activemq-parent-5.14.4-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.14.4Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.4">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.4</a></p><h2 id="ActiveMQ5.14.4Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338909">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5143-release.xml">ActiveMQ 5.14.3 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/activemq-parent-5.14.4-source-release.zip">activemq-parent-5.14.4-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/activemq-parent-5.14.4-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/activemq-parent-5.14.4-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.14.4/activemq-parent-5.14.4-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.4">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.4</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338909">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="98b6d6b8-a3a3-4bc9-94d8-4b9ffb9c9552" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.14.3 Release"></page></link></p></div>
diff --git a/activemq-5145-release.xml b/activemq-5145-release.xml
index 30f83b2..c87e581 100644
--- a/activemq-5145-release.xml
+++ b/activemq-5145-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.14.5Release-ActiveMQ5.14.5Release">ActiveMQ 5.14.5 Release</h2><p>Apache ActiveMQ 5.14.5 includes several resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338909"> issues</a> and bug fixes.</p><h3 id="ActiveMQ5.14.5Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.14.5/apache-activemq-5.14.5-bin.zip&action=download">apache-activemq-5.14.5-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.14.5/apache-activemq-5.14.5-bin.tar.gz&action=download">apache-activemq-5.14.5-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.14.5Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.14.5Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.14.5 Release</h2><p>Apache ActiveMQ 5.14.5 includes several resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338909"> issues</a> and bug fixes.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.14.5/apache-activemq-5.14.5-bin.zip&action=download">apache-activemq-5.14.5-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.14.5/apache-activemq-5.14.5-bin.tar.gz&action=download">apache-activemq-5.14.5-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/apache-activemq-5.14.5-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.14.5</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.14.5Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.14.5Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.14.5/activemq-parent-5.14.5-source-release.zip">activemq-parent-5.14.5-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/activemq-parent-5.14.5-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/activemq-parent-5.14.5-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.14.5/activemq-parent-5.14.5-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.14.5Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.5">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.5</a></p><h2 id="ActiveMQ5.14.5Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12339772">release notes</a></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5144-release.xml">ActiveMQ 5.14.4 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.14.5/activemq-parent-5.14.5-source-release.zip">activemq-parent-5.14.5-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/activemq-parent-5.14.5-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/activemq-parent-5.14.5-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.14.5/activemq-parent-5.14.5-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.5">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.14.5</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12339772">release notes</a></p><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="c9a03419-6ce8-48b5-859c-13cbb7cb3474" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.14.4 Release"></page></link></p></div>
diff --git a/activemq-5150-release.xml b/activemq-5150-release.xml
index c22de44..cd0f97d 100644
--- a/activemq-5150-release.xml
+++ b/activemq-5150-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.15.0Release-ActiveMQ5.15.0Release">ActiveMQ 5.15.0 Release</h2><p>Apache ActiveMQ 5.15.0 includes several resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338054"> issues</a> and bug fixes.</p><h3 id="ActiveMQ5.15.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.zip">apache-activemq-5.15.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.tar.gz">apache-activemq-5.15.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.15.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.15.0Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.15.0 Release</h2><p>Apache ActiveMQ 5.15.0 includes several resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338054"> issues</a> and bug fixes.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.zip">apache-activemq-5.15.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.zip.sha1">SHA1</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.tar.gz">apache-activemq-5.15.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/apache-activemq-5.15.0-bin.tar.gz.sha1">SHA1</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.15.0</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.15.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.15.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/activemq-parent-5.15.0-source-release.zip">activemq-parent-5.15.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/activemq-parent-5.15.0-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/activemq-parent-5.15.0-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.0/activemq-parent-5.15.0-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.15.0Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.0</a></p><h2 id="ActiveMQ5.15.0Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338054">release notes</a></p><div class="confluence-information-macro confluence-information-macro-note"><p class="title">Java 8 Required</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The minimum Java version has been upgraded to Java 8.</p></div></div><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5145-release.xml">ActiveMQ 5.14.5 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/activemq-parent-5.15.0-source-release.zip">activemq-parent-5.15.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/activemq-parent-5.15.0-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/activemq-parent-5.15.0-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.0/activemq-parent-5.15.0-source-release.zip.sha1">SHA1</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.0">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.0</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338054">release notes</a></p><structured-macro ac:macro-id="e70ca3f1-0f56-47f3-8abe-cda8c5d368eb" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Java 8 Required</parameter><rich-text-body><p>The minimum Java version has been upgraded to Java 8.</p></rich-text-body></structured-macro><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="c7651598-142b-418b-a5f1-1720c8523d78" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.14.5 Release"></page></link></p></div>
diff --git a/activemq-5151-release.xml b/activemq-5151-release.xml
index 2b7493c..75c2298 100644
--- a/activemq-5151-release.xml
+++ b/activemq-5151-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.15.1Release-ActiveMQ5.15.1Release">ActiveMQ 5.15.1 Release</h2><p>Apache ActiveMQ 5.15.1 includes several resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341031"> issues</a> and bug fixes.</p><h3 id="ActiveMQ5.15.1Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.zip">apache-activemq-5.15.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.zip.sha512">SHA512</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.tar.gz">apache-activemq-5.15.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.tar.gz.sha512">SHA512</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.15.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.15.1Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.15.1 Release</h2><p>Apache ActiveMQ 5.15.1 includes several resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341031"> issues</a> and bug fixes.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.zip">apache-activemq-5.15.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.zip.sha512">SHA512</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.tar.gz">apache-activemq-5.15.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/apache-activemq-5.15.1-bin.tar.gz.sha512">SHA512</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.15.1</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.15.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.15.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/activemq-parent-5.15.1-source-release.zip">activemq-parent-5.15.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/activemq-parent-5.15.1-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/activemq-parent-5.15.1-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/5.15.1/activemq-parent-5.15.1-source-release.zip.sha512">SHA512</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.15.1Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.1</a></p><h2 id="ActiveMQ5.15.1Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341031">release notes</a></p><div class="confluence-information-macro confluence-information-macro-note"><p class="title">Java 8 Required</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The minimum Java version has been upgraded to Java 8.</p></div></div><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5150-release.xml">ActiveMQ 5.15.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/activemq-parent-5.15.1-source-release.zip">activemq-parent-5.15.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/activemq-parent-5.15.1-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/activemq-parent-5.15.1-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://archive.apache.org/dist/activemq/5.15.1/activemq-parent-5.15.1-source-release.zip.sha512">SHA512</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.1">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.1</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341031">release notes</a></p><structured-macro ac:macro-id="e70ca3f1-0f56-47f3-8abe-cda8c5d368eb" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Java 8 Required</parameter><rich-text-body><p>The minimum Java version has been upgraded to Java 8.</p></rich-text-body></structured-macro><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="26711eaf-a64b-44ac-b670-b361d4ded9af" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.15.0 Release"></page></link></p></div>
diff --git a/activemq-5152-release.xml b/activemq-5152-release.xml
index 621bb88..de498c0 100644
--- a/activemq-5152-release.xml
+++ b/activemq-5152-release.xml
@@ -1,35 +1,7 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p> </p><h2 id="ActiveMQ5.15.2Release-ActiveMQ5.15.2Release">ActiveMQ 5.15.2 Release</h2><p>Apache ActiveMQ 5.15.2 includes several resolved<a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341669"> issues</a> and bug fixes.</p><h3 id="ActiveMQ5.15.2Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.15.2/apache-activemq-5.15.2-bin.zip&action=download">apache-activemq-5.15.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.zip.sha512">SHA512</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.15.2/apache-activemq-5.15.2-bin.tar.gz&action=download">apache-activemq-5.15.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.tar.gz.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.tar.gz.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.tar.gz.sha512">SHA512</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.15.2Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.15.2Release-GettingtheBinariesusingMaven3">Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="0d3bbe74-1dd7-4c5b-a81e-f58906b1e1ab" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body><p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p> </p><h2>ActiveMQ 5.15.2 Release</h2><p>Apache ActiveMQ 5.15.2 includes several resolved<a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341669"> issues</a> and bug fixes.</p><h3>Getting the Binary Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p><em>Verify</em></p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.15.2/apache-activemq-5.15.2-bin.zip&action=download">apache-activemq-5.15.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.zip.sha512">SHA512</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.15.2/apache-activemq-5.15.2-bin.tar.gz&action=download">apache-activemq-5.15.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.tar.gz.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.tar.gz.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/apache-activemq-5.15.2-bin.tar.gz.sha512">SHA512</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="0b3139dd-d993-4394-9aa9-9be1a51f8ca7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 3</h2><p>To use this release in your maven project, the simplest dependency that you can use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ec406dc7-2a01-4e93-829c-542486399e50" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.15.2</version>
</dependency>
-]]></script>
-</div></div><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><div> </div>
-
-
-<h2 id="ActiveMQ5.15.2Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.15.2Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.15.2/activemq-parent-5.15.2-source-release.zip">activemq-parent-5.15.2-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/activemq-parent-5.15.2-source-release.zip.asc">ASC</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/activemq-parent-5.15.2-source-release.zip.md5">MD5</a>, <a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.15.2/activemq-parent-5.15.2-source-release.zip.sha512">SHA512</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.15.2Release-GitTag">Git Tag</h3><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.2</a></p><h2 id="ActiveMQ5.15.2Release-ChangeLog">Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341669">release notes</a></p><div class="confluence-information-macro confluence-information-macro-note"><p class="title">Java 8 Required</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The minimum Java version has been upgraded to Java 8.</p></div></div><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" class="external-link" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6013?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6013</a>
- -
- <span class="summary">Restrict classes that can be serialized in ObjectMessages</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
- for more information.</p></div></div><p> </p><p> </p><p>Also see the previous <a shape="rect" href="activemq-5150-release.xml">ActiveMQ 5.15.0 Release</a></p></div>
+</plain-text-body></structured-macro><p>If you need more fine grained control of your dependencies (activemq-all is an uber jar) pick and choose from the various components activemq-client, activemq-broker, activemq-xx-store etc.</p><structured-macro ac:macro-id="a2795b6b-929c-4360-b469-a02d8079ca4f" ac:name="div" ac:schema-version="1"><rich-text-body> </rich-text-body></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>Verify</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.15.2/activemq-parent-5.15.2-source-release.zip">activemq-parent-5.15.2-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/activemq-parent-5.15.2-source-release.zip.asc">ASC</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/activemq-parent-5.15.2-source-release.zip.md5">MD5</a>, <a shape="rect" href="https://www.apache.org/dist/activemq/5.15.2/activemq-parent-5.15.2-source-release.zip.sha512">SHA512</a></p></td></tr></tbody></table><h3>Git Tag</h3><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.2">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.15.2</a></p><h2>Change Log</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341669">release notes</a></p><structured-macro ac:macro-id="e70ca3f1-0f56-47f3-8abe-cda8c5d368eb" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Java 8 Required</parameter><rich-text-body><p>The minimum Java version has been upgraded to Java 8.</p></rich-text-body></structured-macro><structured-macro ac:macro-id="d4a0b50c-6902-45e0-a632-d3556603b45d" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This release affects applications using ObjectMessages. Please refer to <a shape="rect" href="http://activemq.apache.org/objectmessage.html">http://activemq.apache.org/objectmessage.html</a> and <structured-macro ac:macro-id="fe2b7e81-08f6-4199-8fab-dc8733befcb7" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6013</parameter></structured-macro> for more information.</p></rich-text-body></structured-macro><p> </p><p> </p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.15.0 Release"></page></link></p></div>
diff --git a/activemq-520-release.xml b/activemq-520-release.xml
index 214a595..ba6806d 100644
--- a/activemq-520-release.xml
+++ b/activemq-520-release.xml
@@ -1,42 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.2 is primarily a maintenance release which <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11841">resolves</a> </p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
-.
-
-<h2 id="ActiveMQ5.2.0Release-NewFeaturesin5.2">New Features in 5.2</h2>
-<p>The new features and enhancements in this release include:</p>
-
-<ul><li><a shape="rect" href="advisory-message.xml">Additional advisory messages</a> for messages delivered/consumed fast producers/slow consumers, Usage limits, Slaves become masters etc.</li><li>Enhanced ssl context configuration through spring/xbean</li><li>New individual acknowledge mode for message consumption</li><li>Ability to configure the automatic discarding of the items being sent to the dead letter queue</li><li>Ability to limit the maximum number of connections to a Broker</li><li>Ability to configure <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ-1244">separate lock</a> Datasource for JDBC Master slave.</li><li>activemq-camel and activemq-connection-pool now have their own modules, no longer in activemq-core</li><li>The default <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> brokerUrl now uses the <a shape="rect" href="failover-transport-reference.xml">failover transport</a>.</li><li>Uses Apache Camel <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/camel-150-release.html">1.5</a>.</li></ul><h2 id="ActiveMQ5.2.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-bin.zip">apache-activemq-5.2.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-bin.zip.asc">apache-activemq-5.2.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-bin.tar.gz">apache-activemq-5.2.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-bin.tar.gz.asc">apache-activemq-5.2.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Do not use Safari to download, the above URLs use redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" class="external-link" href="http://www.mozilla.com/en-US/firefox/" rel="nofollow">FireFox</a></p></div></div><p></p><h2 id="ActiveMQ5.2.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.2.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="b99a04f3-f6d6-46c7-8fd4-8e60d7398ba5" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p><structured-macro ac:macro-id="e19ea26c-0c8d-471b-a6b7-42cd75681069" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.2"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-bin.zip">apache-activemq-5.2.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-bin.zip.asc">apache-activemq-5.2.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-bin.tar.gz">apache-activemq-5.2.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-bin.tar.gz.asc">apache-activemq-5.2.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><structured-macro ac:macro-id="60ad5f08-4485-4c3a-8cd3-0b1d9f3ae3e2" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Do not use Safari to download, the above URLs use redirection</parameter><rich-text-body><p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" href="http://www.mozilla.com/en-US/firefox/">FireFox</a></p></rich-text-body></structured-macro><p><structured-macro ac:macro-id="f5c22e81-4286-40ce-9346-2da4250cdcd4" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="ccc28a51-3097-4b56-8154-b8ba1851e55a" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.2.0</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.2.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.2.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-src.zip">apache-activemq-5.2.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-src.zip.asc">apache-activemq-5.2.0-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-src.tar.gz">apache-activemq-5.2.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-src.tar.gz.asc">apache-activemq-5.2.0-src.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.2.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.2.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.2.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11841">release notes</a></p><p></p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
-<p>Also see the previous <a shape="rect" href="activemq-510-release.xml">ActiveMQ 5.1.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="13ab3b02-460c-433c-8d16-a3e7c780a372" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-src.zip">apache-activemq-5.2.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-src.zip.asc">apache-activemq-5.2.0-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-src.tar.gz">apache-activemq-5.2.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.2.0/apache-activemq-5.2.0-src.tar.gz.asc">apache-activemq-5.2.0-src.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="c53e1e9f-cad7-43e1-9a71-dafd8f4f8d2b" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.2.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11841">release notes</a></p><p><structured-macro ac:macro-id="231b862f-a00e-4b38-8136-025527fcc651" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="columns">type;key;summary</parameter><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=10520&fixfor=11841&sorter/field=priority"></url></parameter></structured-macro></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.1.0 Release"></page></link></p></div>
diff --git a/activemq-530-release.xml b/activemq-530-release.xml
index c87dbd6..96e5695 100644
--- a/activemq-530-release.xml
+++ b/activemq-530-release.xml
@@ -1,36 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.3 is primarily a maintenance release which <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11914&styleName=Html&projectId=10520">resolves</a> 334 issues.
-
-</p><h2 id="ActiveMQ5.3.0Release-NewFeaturesin5.3">New Features in 5.3</h2>
-<p>The new features and enhancements in this release include:</p>
-
-<ul><li>New <a shape="rect" href="kahadb.xml">KahaDB</a> persistent storage</li><li><a shape="rect" class="external-link" href="http://camel.apache.org">Camel 2.0.0</a> along with its web console</li><li>stomp over SSL and NIO support</li><li>Improved configuration - default one production oriented and a lot of use case configuration examples (like scalability and throughput)</li><li>Ability to query broker for statistics from non-Java clients (by sending a message)</li><li>More broker plugins included to help tracing messages in networks, improving logging, etc.</li><li>FTP support for blob messages</li><li>Improved activemq-admin to lookup for local processes if possible</li><li>... and much more</li></ul><h2 id="ActiveMQ5.3.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/apache-activemq-5.3.0-bin.zip">apache-activemq-5.3.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/apache-activemq-5.3.0-bin.zip.asc">apache-activemq-5.3.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/apache-activemq-5.3.0-bin.tar.gz">apache-activemq-5.3.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/apache-activemq-5.3.0-bin.tar.gz.asc">apache-activemq-5.3.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Do not use Safari to download, the above URLs use redirection</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" class="external-link" href="http://www.mozilla.com/en-US/firefox/" rel="nofollow">FireFox</a></p></div></div><p></p><h2 id="ActiveMQ5.3.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.3.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="d1f6a43b-b963-4d7e-a0b1-565b2869d36c" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p><structured-macro ac:macro-id="69d45a4a-ad25-46b5-91be-7f9af439f37a" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.3"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/apache-activemq-5.3.0-bin.zip">apache-activemq-5.3.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/apache-activemq-5.3.0-bin.zip.asc">apache-activemq-5.3.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/apache-activemq-5.3.0-bin.tar.gz">apache-activemq-5.3.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/apache-activemq-5.3.0-bin.tar.gz.asc">apache-activemq-5.3.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><structured-macro ac:macro-id="559fe820-e936-4ce6-a30f-d68483feecf2" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Do not use Safari to download, the above URLs use redirection</parameter><rich-text-body><p>The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using <a shape="rect" href="http://www.mozilla.com/en-US/firefox/">FireFox</a></p></rich-text-body></structured-macro><p><structured-macro ac:macro-id="1479affa-0245-4cab-937b-af25354c4f89" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="8061e073-9557-4262-9b82-8067f5716191" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.3.0</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.3.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.3.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/activemq-parent-5.3.0-source-release.zip">activemq-parent-5.3.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/activemq-parent-5.3.0-source-release.zip.asc">activemq-parent-5.3.0-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/activemq-parent-5.3.0-source-release.tar.gz">activemq-parent-5.3.0-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/activemq-parent-5.3.0-source-release.tar.gz.asc">activemq-parent-5.3.0-source-release.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.3.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.3.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.3.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11914&styleName=Html&projectId=10520">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-520-release.xml">ActiveMQ 5.2.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="364f5aae-88cd-49f5-b326-0a4d91c26e66" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/activemq-parent-5.3.0-source-release.zip">activemq-parent-5.3.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/activemq-parent-5.3.0-source-release.zip.asc">activemq-parent-5.3.0-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/activemq-parent-5.3.0-source-release.tar.gz">activemq-parent-5.3.0-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.0/activemq-parent-5.3.0-source-release.tar.gz.asc">activemq-parent-5.3.0-source-release.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="3ca15ec1-353e-4644-b527-dde284e66580" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.3.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11914&styleName=Html&projectId=10520">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.2.0 Release"></page></link></p></div>
diff --git a/activemq-531-release.xml b/activemq-531-release.xml
index 4b604a4..c45ec9c 100644
--- a/activemq-531-release.xml
+++ b/activemq-531-release.xml
@@ -1,31 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.3 is primarily a maintenance release which <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12183">resolves</a> 98 issues.</p><p>The most improved areas in this release are:</p><ul><li>KahaDB message store - fixed performance limiting issues in indexes for both Queues and Topics</li><li>JDBC message store - a lot of improvements in reliability of this messages store</li><li><code>nio</code> and <code>stomp+nio</code> transports - fixed problems with leaking resources</li><li>OSGi integration - a lot of small improvements and better Apache Karaf integration</li><li>Web console security - secured against XSS and XSRF attacks</li></ul><h2 id="ActiveMQ5.3.1Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/apache-activemq-5.3.1-bin.zip">apache-activemq-5.3.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/apache-activemq-5.3.1-bin.zip.asc">apache-activemq-5.3.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/apache-activemq-5.3.1-bin.tar.gz">apache-activemq-5.3.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/apache-activemq-5.3.1-bin.tar.gz.asc">apache-activemq-5.3.1-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.3.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.3.1Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="1d6269ec-1eef-4e4b-8b73-3078f0ab3c7f" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.3 is primarily a maintenance release which <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12183">resolves</a> 98 issues.</p><p>The most improved areas in this release are:</p><ul><li>KahaDB message store - fixed performance limiting issues in indexes for both Queues and Topics</li><li>JDBC message store - a lot of improvements in reliability of this messages store</li><li><code>nio</code> and <code>stomp+nio</code> transports - fixed problems with leaking resources</li><li>OSGi integration - a lot of small improvements and better Apache Karaf integration</li><li>Web console security - secured against XSS and XSRF attacks</li></ul><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/apache-activemq-5.3.1-bin.zip">apache-activemq-5.3.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/apache-activemq-5.3.1-bin.zip.asc">apache-activemq-5.3.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/apache-activemq-5.3.1-bin.tar.gz">apache-activemq-5.3.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/apache-activemq-5.3.1-bin.tar.gz.asc">apache-activemq-5.3.1-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="dba18de2-08fb-4fa8-929b-27eeb69115e0" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="86a957fd-ab6c-4aaf-9967-199e5a0a6524" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.3.1</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.3.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.3.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/activemq-parent-5.3.1-source-release.zip">activemq-parent-5.3.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/activemq-parent-5.3.1-source-release.zip.asc">activemq-parent-5.3.1-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/activemq-parent-5.3.1-source-release.tar.gz">activemq-parent-5.3.1-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/activemq-parent-5.3.1-source-release.tar.gz.asc">activemq-parent-5.3.1-source-release.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.3.1Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.3.1
-]]></script>
-</div></div><h2 id="ActiveMQ5.3.1Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12183">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-530-release.xml">ActiveMQ 5.3.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="b45a04cb-5581-4aad-842f-0fd3b2d37907" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/activemq-parent-5.3.1-source-release.zip">activemq-parent-5.3.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/activemq-parent-5.3.1-source-release.zip.asc">activemq-parent-5.3.1-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/activemq-parent-5.3.1-source-release.tar.gz">activemq-parent-5.3.1-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.1/activemq-parent-5.3.1-source-release.tar.gz.asc">activemq-parent-5.3.1-source-release.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="174c3439-b07e-45c2-a366-7b0ca7fcfef3" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.3.1
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12183">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.3.0 Release"></page></link></p></div>
diff --git a/activemq-532-release.xml b/activemq-532-release.xml
index bedf75f..1c9db36 100644
--- a/activemq-532-release.xml
+++ b/activemq-532-release.xml
@@ -1,31 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.3.2 is primarily a maintenance release which <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&&pid=10520&fixfor=12310&sorter/field=priority&sorter/order=DESC">resolves</a> 3 issues.</p><h2 id="ActiveMQ5.3.2Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/apache-activemq-5.3.2-bin.zip">apache-activemq-5.3.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/apache-activemq-5.3.2-bin.zip.asc">apache-activemq-5.3.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/apache-activemq-5.3.2-bin.tar.gz">apache-activemq-5.3.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/apache-activemq-5.3.2-bin.tar.gz.asc">apache-activemq-5.3.2-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.3.2Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.3.2Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="044a8bd2-0b89-4ac4-82b8-c51f27797322" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.3.2 is primarily a maintenance release which <a shape="rect" href="https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&&pid=10520&fixfor=12310&sorter/field=priority&sorter/order=DESC">resolves</a> 3 issues.</p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/apache-activemq-5.3.2-bin.zip">apache-activemq-5.3.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/apache-activemq-5.3.2-bin.zip.asc">apache-activemq-5.3.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/apache-activemq-5.3.2-bin.tar.gz">apache-activemq-5.3.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/apache-activemq-5.3.2-bin.tar.gz.asc">apache-activemq-5.3.2-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="85fb67c8-9909-43e5-833b-d4e2f6688176" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="f36ed2e6-24ef-4d39-a0c1-0521222e1789" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.3.2</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.3.2Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.3.2Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/activemq-parent-5.3.2-source-release.zip">activemq-parent-5.3.2-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/activemq-parent-5.3.2-source-release.zip.asc">activemq-parent-5.3.2-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/activemq-parent-5.3.2-source-release.tar.gz">activemq-parent-5.3.2-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/activemq-parent-5.3.2-source-release.tar.gz.asc">activemq-parent-5.3.2-source-release.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.3.2Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-parent-5.3.2
-]]></script>
-</div></div><h2 id="ActiveMQ5.3.2Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12310">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-531-release.xml">ActiveMQ 5.3.1 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="eec8319a-87bd-4eb3-bdd3-5d258c669ed2" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/activemq-parent-5.3.2-source-release.zip">activemq-parent-5.3.2-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/activemq-parent-5.3.2-source-release.zip.asc">activemq-parent-5.3.2-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/activemq-parent-5.3.2-source-release.tar.gz">activemq-parent-5.3.2-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.3.2/activemq-parent-5.3.2-source-release.tar.gz.asc">activemq-parent-5.3.2-source-release.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="237f1cbc-4887-48c0-af6d-adaafa2ce3d2" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-parent-5.3.2
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12310">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.3.1 Release"></page></link></p></div>
diff --git a/activemq-540-release.xml b/activemq-540-release.xml
index b52c0bc..0337ae0 100644
--- a/activemq-540-release.xml
+++ b/activemq-540-release.xml
@@ -1,38 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release has been retracted due to bug <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>. It is no longer downloadable from ASF servers. Please use the <a shape="rect" href="activemq-543-release.xml">ActiveMQ 5.4.3 Release</a> instead.</p></div></div><p>Apache ActiveMQ 5.4.0 is primarily a maintenance release which <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&&pid=10520&fixfor=12110&sorter/field=priority&sorter/order=DESC">resolves</a> 283 issues.</p><p></p><h2 id="ActiveMQ5.4.0Release-NewFeaturesin5.4.1">New Features in 5.4.1</h2>
-<ul><li><a shape="rect" href="encrypted-passwords.xml">Encrypted passwords</a></li><li>Added selector support in <a shape="rect" href="ajax.xml">Ajax</a></li></ul>
-
-
-<h2 id="ActiveMQ5.4.0Release-NewFeaturesin5.4">New Features in 5.4</h2>
-
-<ul><li><a shape="rect" href="delay-and-schedule-message-delivery.xml">Delay and Schedule Message Delivery</a></li><li>Message Priority</li><li><a shape="rect" href="websockets.xml">WebSockets</a></li><li><a shape="rect" href="osgi-integration.xml">Better OSGi support</a></li><li>Broker side options for updating failover clients automatically of new brokers joining and leaving the cluster - see <a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></li><li><a shape="rect" href="unix-shell-script.xml">Enhanced Shell Script</a> - for starting, stopping and managing the broker in a Unix environment</li><li><a shape="rect" href="web-console.xml#WebConsole-SecuringWebConsole">Easy way to configure Web Console</a></li><li><a shape="rect" href="rest.xml#REST-Consumingwithselectors">Selectors for Ajax and REST consumers</a></li><li>JaasDualAuthentcationPlugin</li><li><a shape="rect" href="security.xml#Security-Anonymousaccess">Anonymous users</a></li><li>Ajax Adapters</li><li>... and much more</li></ul>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Note: XML configuration is now validated against the schema</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The XML configuration syntax is now validated. The broker schema element is an alphabetically ordered sequence. Validation can now cause existing xml configuration files, with out of order elements, to fail to load with XML parse errors, halting the broker start. Fix any ordering issues to continue.</p></div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Note: New jetty XML configuration</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The jetty XML configuration now uses direct jetty bean syntax in the absence of xbean support. This renders existing (pre 5.4) jetty xml configuration invalid. It will be necessary to reapply custom changes using the default jetty.xml as a template.</p></div></div><h2 id="ActiveMQ5.4.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/apache-activemq-5.4.0-bin.zip">apache-activemq-5.4.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/apache-activemq-5.4.0-bin.zip.asc">apache-activemq-5.4.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/apache-activemq-5.4.0-bin.tar.gz">apache-activemq-5.4.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/apache-activemq-5.4.0-bin.tar.gz.asc">apache-activemq-5.4.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.4.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.4.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="f9843f57-8ffa-4e2d-aed7-ca64676d03e2" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><structured-macro ac:macro-id="f84f3922-0383-4445-8a21-e2a9b5143273" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>This release has been retracted due to bug <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>. It is no longer downloadable from ASF servers. Please use the <link><page ri:content-title="ActiveMQ 5.4.3 Release"></page></link> instead.</p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.4.0 is primarily a maintenance release which <a shape="rect" href="https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&&pid=10520&fixfor=12110&sorter/field=priority&sorter/order=DESC">resolves</a> 283 issues.</p><p><structured-macro ac:macro-id="6c0c82c6-e969-4973-b25b-3948ec1b774f" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.4"></page></link></parameter></structured-macro></p><structured-macro ac:macro-id="be629fd6-e0b7-4504-83ca-5ded30fd04f7" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Note: XML configuration is now validated against the schema</parameter><rich-text-body><p>The XML configuration syntax is now validated. The broker schema element is an alphabetically ordered sequence. Validation can now cause existing xml configuration files, with out of order elements, to fail to load with XML parse errors, halting the broker start. Fix any ordering issues to continue.</p></rich-text-body></structured-macro><structured-macro ac:macro-id="202916fb-1baf-4490-b21b-a002b32e8903" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Note: New jetty XML configuration</parameter><rich-text-body><p>The jetty XML configuration now uses direct jetty bean syntax in the absence of xbean support. This renders existing (pre 5.4) jetty xml configuration invalid. It will be necessary to reapply custom changes using the default jetty.xml as a template.</p></rich-text-body></structured-macro><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/apache-activemq-5.4.0-bin.zip">apache-activemq-5.4.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/apache-activemq-5.4.0-bin.zip.asc">apache-activemq-5.4.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/apache-activemq-5.4.0-bin.tar.gz">apache-activemq-5.4.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/apache-activemq-5.4.0-bin.tar.gz.asc">apache-activemq-5.4.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="af7f9ae5-2814-4cfb-8823-03ee81b5f09b" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="4dbc3884-dede-4340-9b6d-47e2327828fe" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.4.0</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.4.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.4.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/activemq-parent-5.4.0-source-release.zip">activemq-parent-5.4.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/activemq-parent-5.4.0-source-release.zip.asc">activemq-parent-5.4.0-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/activemq-parent-5.4.0-source-release.tar.gz">activemq-parent-5.4.0-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/activemq-parent-5.4.0-source-release.tar.gz.asc">activemq-parent-5.4.0-source-release.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.4.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.4.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12110">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-532-release.xml">ActiveMQ 5.3.2 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="9a795a0b-35bd-435b-a3d6-9bcc43a95d04" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/activemq-parent-5.4.0-source-release.zip">activemq-parent-5.4.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/activemq-parent-5.4.0-source-release.zip.asc">activemq-parent-5.4.0-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/activemq-parent-5.4.0-source-release.tar.gz">activemq-parent-5.4.0-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.0/activemq-parent-5.4.0-source-release.tar.gz.asc">activemq-parent-5.4.0-source-release.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="86c64a8d-fce1-4880-8c61-5f34b513dd8b" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12110">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.3.2 Release"></page></link></p></div>
diff --git a/activemq-541-release.xml b/activemq-541-release.xml
index f23484e..18e2ff1 100644
--- a/activemq-541-release.xml
+++ b/activemq-541-release.xml
@@ -1,38 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release has been retracted due to bug <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>. It is no longer downloadable from ASF servers. Please use the <a shape="rect" href="activemq-543-release.xml">ActiveMQ 5.4.3 Release</a> instead.</p></div></div><p>Apache ActiveMQ 5.4.1 is primarily a maintenance release which resolves<br clear="none"> <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&&pid=10520&fixfor=12332&sorter/field=priority&sorter/order=DESC">49 issues</a> mostly bug fixes and improvements</p><p></p><h2 id="ActiveMQ5.4.1Release-NewFeaturesin5.4.1">New Features in 5.4.1</h2>
-<ul><li><a shape="rect" href="encrypted-passwords.xml">Encrypted passwords</a></li><li>Added selector support in <a shape="rect" href="ajax.xml">Ajax</a></li></ul>
-
-
-<h2 id="ActiveMQ5.4.1Release-NewFeaturesin5.4">New Features in 5.4</h2>
-
-<ul><li><a shape="rect" href="delay-and-schedule-message-delivery.xml">Delay and Schedule Message Delivery</a></li><li>Message Priority</li><li><a shape="rect" href="websockets.xml">WebSockets</a></li><li><a shape="rect" href="osgi-integration.xml">Better OSGi support</a></li><li>Broker side options for updating failover clients automatically of new brokers joining and leaving the cluster - see <a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></li><li><a shape="rect" href="unix-shell-script.xml">Enhanced Shell Script</a> - for starting, stopping and managing the broker in a Unix environment</li><li><a shape="rect" href="web-console.xml#WebConsole-SecuringWebConsole">Easy way to configure Web Console</a></li><li><a shape="rect" href="rest.xml#REST-Consumingwithselectors">Selectors for Ajax and REST consumers</a></li><li>JaasDualAuthentcationPlugin</li><li><a shape="rect" href="security.xml#Security-Anonymousaccess">Anonymous users</a></li><li>Ajax Adapters</li><li>... and much more</li></ul>
-<h2 id="ActiveMQ5.4.1Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/apache-activemq-5.4.1-bin.zip">apache-activemq-5.4.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/apache-activemq-5.4.1-bin.zip.asc">apache-activemq-5.4.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/apache-activemq-5.4.1-bin.tar.gz">apache-activemq-5.4.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/apache-activemq-5.4.1-bin.tar.gz.asc">apache-activemq-5.4.1-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.4.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.4.1Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="4b367ff5-13b7-4a1d-8c60-d76b3c1de7c1" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><structured-macro ac:macro-id="4e2cfa20-544c-4f9d-b1a9-d80dfd1fed23" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>This release has been retracted due to bug <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>. It is no longer downloadable from ASF servers. Please use the <link><page ri:content-title="ActiveMQ 5.4.3 Release"></page></link> instead.</p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.4.1 is primarily a maintenance release which resolves<br clear="none"> <a shape="rect" href="https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&&pid=10520&fixfor=12332&sorter/field=priority&sorter/order=DESC">49 issues</a> mostly bug fixes and improvements</p><p><structured-macro ac:macro-id="02870b3e-799c-485f-ba21-42293f63a638" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.4"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/apache-activemq-5.4.1-bin.zip">apache-activemq-5.4.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/apache-activemq-5.4.1-bin.zip.asc">apache-activemq-5.4.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/apache-activemq-5.4.1-bin.tar.gz">apache-activemq-5.4.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/apache-activemq-5.4.1-bin.tar.gz.asc">apache-activemq-5.4.1-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="7a393d4f-4bf3-4ebd-8111-6540b1569140" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="c3dd93fd-58b8-4888-ac8e-8098f0a6d9ad" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.4.1</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.4.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.4.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/activemq-parent-5.4.1-source-release.zip">activemq-parent-5.4.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/activemq-parent-5.4.1-source-release.zip.asc">activemq-parent-5.4.1-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/activemq-parent-5.4.1-source-release.tar.gz">activemq-parent-5.4.1-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/activemq-parent-5.4.1-source-release.tar.gz.asc">activemq-parent-5.4.1-source-release.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.4.1Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.1
-]]></script>
-</div></div><h2 id="ActiveMQ5.4.1Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12332">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-540-release.xml">ActiveMQ 5.4.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="ecac7b3a-7a76-4a11-adb3-8a0e7b744099" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/activemq-parent-5.4.1-source-release.zip">activemq-parent-5.4.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/activemq-parent-5.4.1-source-release.zip.asc">activemq-parent-5.4.1-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/activemq-parent-5.4.1-source-release.tar.gz">activemq-parent-5.4.1-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.1/activemq-parent-5.4.1-source-release.tar.gz.asc">activemq-parent-5.4.1-source-release.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="dfaea627-5ec1-4e8b-935c-e1b7ac22c4fa" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.1
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12332">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.4.0 Release"></page></link></p></div>
diff --git a/activemq-542-release.xml b/activemq-542-release.xml
index e1ab508..9923807 100644
--- a/activemq-542-release.xml
+++ b/activemq-542-release.xml
@@ -1,31 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release has been retracted due to bug <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>. It is no longer downloadable from ASF servers. Please use the <a shape="rect" href="activemq-543-release.xml">ActiveMQ 5.4.3 Release</a> instead.</p></div></div><p>Apache ActiveMQ 5.4.2 is primarily a maintenance release which resolves<br clear="none"> <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12311210&status=5&status=6&fixfor=12315625&sorter/field=priority&sorter/order=DESC">61 issues</a> mostly bug fixes and improvements</p><h2 id="ActiveMQ5.4.2Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/apache-activemq-5.4.2-bin.zip">apache-activemq-5.4.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/apache-activemq-5.4.2-bin.zip.asc">apache-activemq-5.4.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/apache-activemq-5.4.2-bin.tar.gz">apache-activemq-5.4.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/apache-activemq-5.4.2-bin.tar.gz.asc">apache-activemq-5.4.2-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.4.2Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.4.2Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="ae8f560a-d855-4682-ac70-8bbe94de8c5d" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><structured-macro ac:macro-id="78fc3592-7d26-4a6d-b5cb-7fcec3f9a1bd" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>This release has been retracted due to bug <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>. It is no longer downloadable from ASF servers. Please use the <link><page ri:content-title="ActiveMQ 5.4.3 Release"></page></link> instead.</p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.4.2 is primarily a maintenance release which resolves<br clear="none"> <a shape="rect" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12311210&status=5&status=6&fixfor=12315625&sorter/field=priority&sorter/order=DESC">61 issues</a> mostly bug fixes and improvements</p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/apache-activemq-5.4.2-bin.zip">apache-activemq-5.4.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/apache-activemq-5.4.2-bin.zip.asc">apache-activemq-5.4.2-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/apache-activemq-5.4.2-bin.tar.gz">apache-activemq-5.4.2-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/apache-activemq-5.4.2-bin.tar.gz.asc">apache-activemq-5.4.2-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="d94f935d-2f37-4305-8b51-9f97d05eb7aa" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="dc8a7d64-629b-4a73-8aeb-bac76cbcec75" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.4.2</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.4.2Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.4.2Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/activemq-parent-5.4.2-source-release.zip">activemq-parent-5.4.2-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/activemq-parent-5.4.2-source-release.zip.asc">activemq-parent-5.4.2-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/activemq-parent-5.4.2-source-release.tar.gz">activemq-parent-5.4.2-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/activemq-parent-5.4.2-source-release.tar.gz.asc">activemq-parent-5.4.2-source-release.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.4.2Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.2
-]]></script>
-</div></div><h2 id="ActiveMQ5.4.2Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&styleName=Html&version=12315625">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-541-release.xml">ActiveMQ 5.4.1 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="7b9d6bc2-ab3d-4ec2-b5dc-63dc4ea36f9b" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/activemq-parent-5.4.2-source-release.zip">activemq-parent-5.4.2-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/activemq-parent-5.4.2-source-release.zip.asc">activemq-parent-5.4.2-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/activemq-parent-5.4.2-source-release.tar.gz">activemq-parent-5.4.2-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.2/activemq-parent-5.4.2-source-release.tar.gz.asc">activemq-parent-5.4.2-source-release.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="5c035ae4-6358-4731-8667-06d70907119a" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.2
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&styleName=Html&version=12315625">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.4.1 Release"></page></link></p></div>
diff --git a/activemq-543-release.xml b/activemq-543-release.xml
index b7af54e..338b7b9 100644
--- a/activemq-543-release.xml
+++ b/activemq-543-release.xml
@@ -1,31 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.4.3 is a maintenance release which resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>, a critical bug which caused the 5.4.0, 5.4.1, and 5.4.2 releases to be retracted.</p><h2 id="ActiveMQ5.4.3Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/apache-activemq-5.4.3-bin.zip">apache-activemq-5.4.3-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/apache-activemq-5.4.3-bin.zip.asc">apache-activemq-5.4.3-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/apache-activemq-5.4.3-bin.tar.gz">apache-activemq-5.4.3-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/apache-activemq-5.4.3-bin.tar.gz.asc">apache-activemq-5.4.3-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.4.3Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.4.3Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="9fdf537d-513e-48cf-908a-e526e633292a" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.4.3 is a maintenance release which resolves <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>, a critical bug which caused the 5.4.0, 5.4.1, and 5.4.2 releases to be retracted.</p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/apache-activemq-5.4.3-bin.zip">apache-activemq-5.4.3-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/apache-activemq-5.4.3-bin.zip.asc">apache-activemq-5.4.3-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/apache-activemq-5.4.3-bin.tar.gz">apache-activemq-5.4.3-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/apache-activemq-5.4.3-bin.tar.gz.asc">apache-activemq-5.4.3-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="374bb88a-aba4-4de4-b2a3-666eab66ba64" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="9a5a889b-7eea-4402-864a-fc08b9e275a1" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.4.3</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.4.3Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.4.3Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/activemq-parent-5.4.3-source-release.zip">activemq-parent-5.4.3-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/activemq-parent-5.4.3-source-release.zip.asc">activemq-parent-5.4.3-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/activemq-parent-5.4.3-source-release.tar.gz">activemq-parent-5.4.3-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/activemq-parent-5.4.3-source-release.tar.gz.asc">activemq-parent-5.4.3-source-release.tar.gz.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.4.3Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.3
-]]></script>
-</div></div><p>Also see the previous <a shape="rect" href="activemq-542-release.xml">ActiveMQ 5.4.2 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="d0df1094-e342-43c0-88c4-ed2e5213190f" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/activemq-parent-5.4.3-source-release.zip">activemq-parent-5.4.3-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/activemq-parent-5.4.3-source-release.zip.asc">activemq-parent-5.4.3-source-release.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source for Unix/Linux/Cygwin</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/activemq-parent-5.4.3-source-release.tar.gz">activemq-parent-5.4.3-source-release.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.4.3/activemq-parent-5.4.3-source-release.tar.gz.asc">activemq-parent-5.4.3-source-release.tar.gz.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="e1f2f090-5641-4dbd-81a9-bfb4c545b78f" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.3
+</plain-text-body></structured-macro><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.4.2 Release"></page></link></p></div>
diff --git a/activemq-550-release.xml b/activemq-550-release.xml
index b3a0898..361f5ae 100644
--- a/activemq-550-release.xml
+++ b/activemq-550-release.xml
@@ -1,38 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This release has been retracted due to bug <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>. It is no longer downloadable from ASF servers. Please use the <a shape="rect" href="activemq-551-release.xml">ActiveMQ 5.5.1 Release</a> instead.</p></div></div><p>Apache ActiveMQ 5.5.0 is primarily a maintenance release which resolves over <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+12315626+AND+status+in+%28Resolved%2C+Closed%29+ORDER+BY+priority+DESC">130 issues</a>, mostly bug fixes and improvements</p><p></p><h2 id="ActiveMQ5.5.0Release-NewFeaturesin5.5.0">New Features in 5.5.0</h2>
-<ul><li>Dependency on Java 1.6 (java 1.5 is no longer supported)</li><li>MDC logging (<a shape="rect" class="external-link" href="http://slf4j.org/" rel="nofollow">SLF4J</a>)</li><li>Upgrade to camel 2.7.0</li><li>DLQ processing per durable subscription</li><li>New network connector MBeans</li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/configurable-ioexception-handling.html">IOExceptionHandler</a> for JDBC store</li><li>Added support for <a shape="rect" class="external-link" href="http://commons.apache.org/daemon/">Apache Commons Daemon</a></li></ul>
-
-
-<h2 id="ActiveMQ5.5.0Release-Improvementsin5.5.0">Improvements in 5.5.0</h2>
-<ul><li>Improved support for recovery of durable subscribers with priority support</li><li>Improved performance for offline durable subscriptions with large message backlogs (JDBC store)</li><li>better support for Guest login via JAAS</li></ul>
-
-<h2 id="ActiveMQ5.5.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/apache-activemq-5.5.0-bin.zip">apache-activemq-5.5.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/apache-activemq-5.5.0-bin.zip.asc">apache-activemq-5.5.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/apache-activemq-5.5.0-bin.tar.gz">apache-activemq-5.5.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/apache-activemq-5.5.0-bin.tar.gz.asc">apache-activemq-5.5.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.5.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.5.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="ce18c011-1795-4e65-aad9-bce312d7065e" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><structured-macro ac:macro-id="a5253e2e-cc15-45bc-8855-51784e15c6bc" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>This release has been retracted due to bug <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>. It is no longer downloadable from ASF servers. Please use the <link><page ri:content-title="ActiveMQ 5.5.1 Release"></page></link> instead.</p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.5.0 is primarily a maintenance release which resolves over <a shape="rect" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+12315626+AND+status+in+%28Resolved%2C+Closed%29+ORDER+BY+priority+DESC">130 issues</a>, mostly bug fixes and improvements</p><p><structured-macro ac:macro-id="bb01b72c-face-4f5d-b367-c288641d1e1a" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.5"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/apache-activemq-5.5.0-bin.zip">apache-activemq-5.5.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/apache-activemq-5.5.0-bin.zip.asc">apache-activemq-5.5.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/apache-activemq-5.5.0-bin.tar.gz">apache-activemq-5.5.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/apache-activemq-5.5.0-bin.tar.gz.asc">apache-activemq-5.5.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="57c3b26b-459a-4457-b2a6-b39e0e437b35" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="06905d8a-dc91-4725-a5d6-5f102422459b" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.5.0</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.5.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.5.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/activemq-parent-5.5.0-source-release.zip">activemq-parent-5.5.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/activemq-parent-5.5.0-source-release.zip.asc">activemq-parent-5.5.0-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.5.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.5.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.5.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&styleName=Html&version=12315626">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-542-release.xml">ActiveMQ 5.4.2 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="dd3c9aeb-4c0b-442d-af88-c09ff004e47a" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/activemq-parent-5.5.0-source-release.zip">activemq-parent-5.5.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.0/activemq-parent-5.5.0-source-release.zip.asc">activemq-parent-5.5.0-source-release.zip.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="4fad5d4a-9ff0-426d-8920-e8de04c6fd5e" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.5.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&styleName=Html&version=12315626">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.4.2 Release"></page></link></p></div>
diff --git a/activemq-551-release.xml b/activemq-551-release.xml
index bff7346..46c7dc3 100644
--- a/activemq-551-release.xml
+++ b/activemq-551-release.xml
@@ -1,31 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.5.1 is a maintenance release which resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>, a critical bug which caused the 5.5.0 release to be retracted.</p><h2 id="ActiveMQ5.5.1Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/apache-activemq-5.5.1-bin.zip">apache-activemq-5.5.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/apache-activemq-5.5.1-bin.zip.asc">apache-activemq-5.5.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/apache-activemq-5.5.1-bin.tar.gz">apache-activemq-5.5.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/apache-activemq-5.5.1-bin.tar.gz.asc">apache-activemq-5.5.1-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.5.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.5.1Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="149e73d0-1690-45aa-bf52-478c3f1e622f" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.5.1 is a maintenance release which resolves <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-3491">AMQ-3491</a>, a critical bug which caused the 5.5.0 release to be retracted.</p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/apache-activemq-5.5.1-bin.zip">apache-activemq-5.5.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/apache-activemq-5.5.1-bin.zip.asc">apache-activemq-5.5.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/apache-activemq-5.5.1-bin.tar.gz">apache-activemq-5.5.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/apache-activemq-5.5.1-bin.tar.gz.asc">apache-activemq-5.5.1-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="889ab8bb-6dfa-4ca6-851d-3e53b6e329fa" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="d8b9a537-55f1-45da-9ca8-ad1f2c3ba842" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.5.1</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.5.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.5.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/activemq-parent-5.5.1-source-release.zip">activemq-parent-5.5.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/activemq-parent-5.5.1-source-release.zip.asc">activemq-parent-5.5.1-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.5.1Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.5.1
-]]></script>
-</div></div><p>Also see the previous <a shape="rect" href="activemq-550-release.xml">ActiveMQ 5.5.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="ae1ee154-3001-47c0-a6af-0aab887f2058" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/activemq-parent-5.5.1-source-release.zip">activemq-parent-5.5.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.5.1/activemq-parent-5.5.1-source-release.zip.asc">activemq-parent-5.5.1-source-release.zip.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="283e5b6b-9b9a-4516-902b-4330fea749e3" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.5.1
+</plain-text-body></structured-macro><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.5.0 Release"></page></link></p></div>
diff --git a/activemq-560-release.xml b/activemq-560-release.xml
index ce1fd09..8f6e057 100644
--- a/activemq-560-release.xml
+++ b/activemq-560-release.xml
@@ -1,33 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.6.0 is primarily a maintenance release which resolves over <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+12317974+AND+status+in+%28Resolved%2C+Closed%29+ORDER+BY+priority+DESC">435 issues</a>, mostly bug fixes and improvements</p><p></p><h2 id="ActiveMQ5.6.0Release-NewFeaturesin5.6.0">New Features in 5.6.0</h2>
-
-<ul class="alternate"><li>LevelDB Store</li><li>MQTT transport</li><li>New LDAP security module</li><li>Stomp 1.1 support</li><li>stomp+nio+ssl transport</li><li>Multi KahaDB persistence</li><li>Priority Failover URIs</li><li>Automatic client rebalance in broker cluster</li></ul><h2 id="ActiveMQ5.6.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/apache-activemq-5.6.0-bin.zip">apache-activemq-5.6.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/apache-activemq-5.6.0-bin.zip.asc">apache-activemq-5.6.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/apache-activemq-5.6.0-bin.tar.gz">apache-activemq-5.6.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/apache-activemq-5.6.0-bin.tar.gz.asc">apache-activemq-5.6.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.6.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.6.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="a087644e-729b-4432-8b75-fc8eb5c0461e" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.6.0 is primarily a maintenance release which resolves over <a shape="rect" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+12317974+AND+status+in+%28Resolved%2C+Closed%29+ORDER+BY+priority+DESC">435 issues</a>, mostly bug fixes and improvements</p><p><structured-macro ac:macro-id="d34296c8-a08c-466e-ac9b-d4728fe62c56" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.6"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/apache-activemq-5.6.0-bin.zip">apache-activemq-5.6.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/apache-activemq-5.6.0-bin.zip.asc">apache-activemq-5.6.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/apache-activemq-5.6.0-bin.tar.gz">apache-activemq-5.6.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/apache-activemq-5.6.0-bin.tar.gz.asc">apache-activemq-5.6.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="8ee71ef1-dbae-4f32-9f7d-f6c85c58ecba" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="7ddaa2b0-52f1-4757-9b95-74805093e5c3" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.6.0</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.6.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.6.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/activemq-parent-5.6.0-source-release.zip">activemq-parent-5.6.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/activemq-parent-5.6.0-source-release.zip.asc">activemq-parent-5.6.0-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.6.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.6.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.6.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12317974">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-551-release.xml">ActiveMQ 5.5.1 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="ad8e3944-b2c3-4d68-8b12-98a38a831240" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/activemq-parent-5.6.0-source-release.zip">activemq-parent-5.6.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.6.0/activemq-parent-5.6.0-source-release.zip.asc">activemq-parent-5.6.0-source-release.zip.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="b2594842-c4ec-44d7-b70b-6aaeb5f433c1" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.6.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12317974">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.5.1 Release"></page></link></p></div>
diff --git a/activemq-570-release.xml b/activemq-570-release.xml
index 35a207a..26e8732 100644
--- a/activemq-570-release.xml
+++ b/activemq-570-release.xml
@@ -1,31 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.7.0 is primarily a maintenance release which resolves nearly <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.7.0%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide">200 issues</a>, mostly bug fixes and improvements</p><p></p><ul><li>Java 7 support (compiled with jdk6 and validated with jdk7)</li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/websockets.html#WebSockets-SecureWebSockets">Secure WebSockets (wss) transport </a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/message-redelivery-and-dlq-handling.html#MessageRedeliveryandDLQHandling-BrokerRedelivery%28v5.7%29">Broker Based Redelivery</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/pluggable-storage-lockers.html">Pluggable Store Lockers</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/pluggable-storage-lockers.html#Pluggablestoragelockers-LeaseDatabaseLocker">Lease based database locker</a></li><li>Set a <a shape="rect" class="external-link" href="http://activemq.apache.org/redelivery-policy.html#RedeliveryPolicy-RedeliveryPolicyperDestination">RedeliveryPolicy per destination</a></li><li>Includes <a shape="rect" class="external-link" href="http://camel.apache.org/camel-2100-release.html">Apache Camel 2.10</a></li></ul><h2 id="ActiveMQ5.7.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/apache-activemq-5.7.0-bin.zip">apache-activemq-5.7.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/apache-activemq-5.7.0-bin.zip.asc">apache-activemq-5.7.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/apache-activemq-5.7.0-bin.tar.gz">apache-activemq-5.7.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/apache-activemq-5.7.0-bin.tar.gz.asc">apache-activemq-5.7.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.7.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.7.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="6c06cdf2-5a57-4f9c-a903-cba298a9b18e" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.7.0 is primarily a maintenance release which resolves nearly <a shape="rect" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.7.0%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide">200 issues</a>, mostly bug fixes and improvements</p><p><structured-macro ac:macro-id="c9a46d0d-78d5-44ee-9568-f75c7865756c" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.7"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/apache-activemq-5.7.0-bin.zip">apache-activemq-5.7.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/apache-activemq-5.7.0-bin.zip.asc">apache-activemq-5.7.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/apache-activemq-5.7.0-bin.tar.gz">apache-activemq-5.7.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/apache-activemq-5.7.0-bin.tar.gz.asc">apache-activemq-5.7.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="2f9cc2b7-2544-40bc-8ebf-7e4d5a86794c" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="b0952581-f297-475b-9e29-0672a1d54ba5" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-core</artifactId>
<version>5.7.0</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.7.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.7.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/activemq-parent-5.7.0-source-release.zip">activemq-parent-5.7.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/activemq-parent-5.7.0-source-release.zip.asc">activemq-parent-5.7.0-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.7.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.7.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.7.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12321258">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-560-release.xml">ActiveMQ 5.6.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="ebaa5719-945e-4667-afd4-ff51ce706a98" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/activemq-parent-5.7.0-source-release.zip">activemq-parent-5.7.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.7.0/activemq-parent-5.7.0-source-release.zip.asc">activemq-parent-5.7.0-source-release.zip.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="d385533c-f27b-4b80-b122-b5bd18d85a27" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.7.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12321258">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.6.0 Release"></page></link></p></div>
diff --git a/activemq-580-release.xml b/activemq-580-release.xml
index 9e7863b..8186c90 100644
--- a/activemq-580-release.xml
+++ b/activemq-580-release.xml
@@ -1,40 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.8.0 resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.8.0%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide">160 issues</a>, mostly bug fixes and improvements. It has the following new features:</p><p></p><ul><li><a shape="rect" href="amqp.xml">AMQP</a></li><li>new feature modules and activemq-client module allowing smaller foorprint</li><li>management via <a shape="rect" href="rest.xml#REST-REST-RestManagement">REST</a> with <a shape="rect" class="external-link" href="http://www.jolokia.org/" rel="nofollow">jolokia</a> jmx to http bridge</li><li>Includes <a shape="rect" class="external-link" href="http://camel.apache.org/camel-2103-release.html">Apache Camel 2.10.3</a></li><li>Java 7 support (compiled with jdk6 and validated with jdk7)</li><li><a shape="rect" href="pure-master-slave.xml">Pure Master Slave</a> no longer supported</li></ul> There are some changes in 5.8 that may require some code change
-
-<ol><li>New modules may effect your maven pom dependencies<br clear="none">
-<code>activemq-core</code> has been replaced with <code>activemq-client</code> and <code>activemq-broker</code>. The various message stores have their own activemq-xx-store module. The uber module <code>activemq-all</code> remains.</li><li>Changed JMX Mbean ObjectNames will effect scripts or tools that directly reference Mbean names<br clear="none">
-All mbeans now share the type=Broker attribute, which gives them containment. In this way, consumers hang off of destinations, which hang off the broker.<br clear="none">
-The different Mbean types are identified by the presence of specific identifiers in their ObjectNames. The mapping from old to new ObjectName is as follows:
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Old Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> New Name </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Broker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=Broker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=Queue|Topic,Destination=<destination identifier> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker,destinationType=Queue|Topic,destinationName=<destination identifier> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Connector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=Connector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker,connector=clientConnectors </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> NetworkConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=NetworkConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker,connector=networkConnectors </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Connection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Type=Connection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> type=Broker,connector=*,connectionViewType=remoteAddress|clientId </p></td></tr></tbody></table></div>
-</li><li>OSGi integration has changed. The full details are at <a shape="rect" href="osgi-integration.xml">OSGi Integration</a>. In summary:
- <ol><li>There is a single uber OSGI bundle</li><li>The broker and webconsole are now configured via config admin pid files through an OSGi managed service factory.</li></ol>
- </li><li>The ActiveMQ binary file <code>bin/run.jar</code> has been renamed to <code>bin/activemq.jar</code>.</li></ol><h2 id="ActiveMQ5.8.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/apache-activemq-5.8.0-bin.zip">apache-activemq-5.8.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/apache-activemq-5.8.0-bin.zip.asc">apache-activemq-5.8.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/apache-activemq-5.8.0-bin.tar.gz">apache-activemq-5.8.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/apache-activemq-5.8.0-bin.tar.gz.asc">apache-activemq-5.8.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.8.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.8.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="6c3bb079-92bb-42d3-a311-08ff6d5c107f" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.8.0 resolves <a shape="rect" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.8.0%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide">160 issues</a>, mostly bug fixes and improvements. It has the following new features:</p><p><structured-macro ac:macro-id="576415ce-1b9c-4bc0-b0bd-95de9d33823d" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.8"></page></link></parameter></structured-macro> <structured-macro ac:macro-id="5e84bd11-540b-4fd3-8caa-214f9e289b94" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="5.8 Migration Guide"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/apache-activemq-5.8.0-bin.zip">apache-activemq-5.8.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/apache-activemq-5.8.0-bin.zip.asc">apache-activemq-5.8.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/apache-activemq-5.8.0-bin.tar.gz">apache-activemq-5.8.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/apache-activemq-5.8.0-bin.tar.gz.asc">apache-activemq-5.8.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="b6e9d1a4-76b8-4c07-b014-c158bc3c2cd9" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="0d434389-7bb2-4dd2-a337-07ed9e3d98b8" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.8.0</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.8.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.8.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/activemq-parent-5.8.0-source-release.zip">activemq-parent-5.8.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/activemq-parent-5.8.0-source-release.zip.asc">activemq-parent-5.8.0-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.8.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.8.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.8.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12323282">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-570-release.xml">ActiveMQ 5.7.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="71b85c08-b789-45d0-8cbe-c335a03d8650" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/activemq-parent-5.8.0-source-release.zip">activemq-parent-5.8.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.8.0/activemq-parent-5.8.0-source-release.zip.asc">activemq-parent-5.8.0-source-release.zip.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="28afd1d4-f143-4d8e-bed4-e16141a668ad" ac:name="code" ac:schema-version="1"><plain-text-body>svn co http://svn.apache.org/repos/asf/activemq/tags/activemq-5.8.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12323282">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.7.0 Release"></page></link></p></div>
diff --git a/activemq-590-release.xml b/activemq-590-release.xml
index 4e7e845..5ae6dd6 100644
--- a/activemq-590-release.xml
+++ b/activemq-590-release.xml
@@ -1,34 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.9.0 resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.9.0%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide">more than 200 issues</a>, mostly bug fixes and improvements. It has the following new features:</p><p></p><ul><li><a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a> for shared nothing Master/Slave.</li><li><a shape="rect" href="runtime-configuration.xml">Runtime Configuration</a></li><li>Generic JMS XA connection pool in activemq-jms-pool module (has no ActiveMQ dependency)</li><li>MQTT over WebSockets support</li><li><a shape="rect" href="broker-camel-component.xml"><strong>broker</strong></a> Apache Camel component</li><li>Broker auto-restart upon losing master status</li><li>AMQP Hardening</li><li>LevelDB Hardening</li></ul> There are some changes in 5.9 that may require user intervention
-
-<ol><li>Schema change to JDBC Persistence Adapter. XID column type change.</li></ol>
-<ul><li>If you use XA transactions you need to ensure there are no XA transactions pending completion before you upgrade. Some mode detail in <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4628">AMQ-4628</a></li></ul><h2 id="ActiveMQ5.9.0Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.zip">apache-activemq-5.9.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.zip.asc">apache-activemq-5.9.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.tar.gz">apache-activemq-5.9.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.tar.gz.asc">apache-activemq-5.9.0-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.9.0Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.9.0Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="a9618579-f987-426c-99c3-608419c36a11" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.9.0 resolves <a shape="rect" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.9.0%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide">more than 200 issues</a>, mostly bug fixes and improvements. It has the following new features:</p><p><structured-macro ac:macro-id="1773bc8e-5c39-47f9-8d48-2a0bed14e6a7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.9"></page></link></parameter></structured-macro> <structured-macro ac:macro-id="ecff5725-a121-4a6f-912e-f363c0be03b7" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="5.9 Migration Guide"></page></link></parameter></structured-macro></p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.zip">apache-activemq-5.9.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.zip.asc">apache-activemq-5.9.0-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.tar.gz">apache-activemq-5.9.0-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/apache-activemq-5.9.0-bin.tar.gz.asc">apache-activemq-5.9.0-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="3efc85fe-93ec-47a7-a8f0-9b59c18f6490" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="9f7474f0-146e-46f1-ad4c-5e9d74a02845" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.9.0</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.9.0Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.9.0Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/activemq-parent-5.9.0-source-release.zip">activemq-parent-5.9.0-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/activemq-parent-5.9.0-source-release.zip.asc">activemq-parent-5.9.0-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.9.0Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.9.0
-]]></script>
-</div></div><h2 id="ActiveMQ5.9.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12323932">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-580-release.xml">ActiveMQ 5.8.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="f8a3a341-f39e-4877-b2e7-f3fa729b0384" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/activemq-parent-5.9.0-source-release.zip">activemq-parent-5.9.0-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/5.9.0/activemq-parent-5.9.0-source-release.zip.asc">activemq-parent-5.9.0-source-release.zip.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="de29d22d-2a2e-4108-bbd8-b1550d9f3342" ac:name="code" ac:schema-version="1"><plain-text-body>https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.9.0
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12323932">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.8.0 Release"></page></link></p></div>
diff --git a/activemq-591-release.xml b/activemq-591-release.xml
index 8b86959..611bf97 100644
--- a/activemq-591-release.xml
+++ b/activemq-591-release.xml
@@ -1,34 +1,9 @@
-<div class="wiki-content maincontent"><div style="padding-right:20px;float:left;margin-left:-20px;">
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png" data-image-src="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></span></p></div>
-
-
-<p>Apache ActiveMQ 5.9.1 resolves <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.9.1%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide">more than 120 issues</a>, mostly bug fixes and improvements. It has the following new features:</p><p></p><ul><li><a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a> for shared nothing Master/Slave.</li><li><a shape="rect" href="runtime-configuration.xml">Runtime Configuration</a></li><li>Generic JMS XA connection pool in activemq-jms-pool module (has no ActiveMQ dependency)</li><li>MQTT over WebSockets support</li><li><a shape="rect" href="broker-camel-component.xml"><strong>broker</strong></a> Apache Camel component</li><li>Broker auto-restart upon losing master status</li><li>AMQP Hardening</li><li>LevelDB Hardening</li></ul> There are some changes in 5.9 that may require user intervention
-
-<ol><li>Schema change to JDBC Persistence Adapter. XID column type change.</li></ol>
-<ul><li>If you use XA transactions you need to ensure there are no XA transactions pending completion before you upgrade. Some mode detail in <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4628">AMQ-4628</a></li></ul><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Note that the Hawtio console was removed in this release.</p></div></div><p> </p><h2 id="ActiveMQ5.9.1Release-GettingtheBinaryDistributions">Getting the Binary Distributions</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Windows Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.9.1/apache-activemq-5.9.1-bin.zip">apache-activemq-5.9.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.9.1/apache-activemq-5.9.1-bin.zip.asc">apache-activemq-5.9.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.9.1/apache-activemq-5.9.1-bin.tar.gz">apache-activemq-5.9.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.9.1/apache-activemq-5.9.1-bin.tar.gz.asc">apache-activemq-5.9.1-bin.tar.gz.asc</a></p></td></tr></tbody></table></div><p></p><h2 id="ActiveMQ5.9.1Release-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
-$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
-$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
-$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul><h2 id="ActiveMQ5.9.1Release-GettingtheBinariesusingMaven2">Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" class="external-link" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="8d355e45-970c-48cd-af6f-454a439cf7b1" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;margin-left:-20px;</parameter><rich-text-body>
+<p><image><url ri:value="http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png"></url></image></p></rich-text-body></structured-macro><p>Apache ActiveMQ 5.9.1 resolves <a shape="rect" href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.9.1%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide">more than 120 issues</a>, mostly bug fixes and improvements. It has the following new features:</p><p><structured-macro ac:macro-id="120e6c87-3ea9-4365-bd44-51df6e367d5e" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="New Features in 5.9"></page></link></parameter></structured-macro> <structured-macro ac:macro-id="a3f9de48-94da-4894-90ff-da409aebb365" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="5.9 Migration Guide"></page></link></parameter></structured-macro></p><structured-macro ac:macro-id="c273c1b3-0a32-4da9-a425-b28b85797307" ac:name="note" ac:schema-version="1"><rich-text-body><p>Note that the Hawtio console was removed in this release.</p></rich-text-body></structured-macro><p> </p><h2>Getting the Binary Distributions</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Windows Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.9.1/apache-activemq-5.9.1-bin.zip">apache-activemq-5.9.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.9.1/apache-activemq-5.9.1-bin.zip.asc">apache-activemq-5.9.1-bin.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Unix/Linux/Cygwin Distribution</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.9.1/apache-activemq-5.9.1-bin.tar.gz">apache-activemq-5.9.1-bin.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.9.1/apache-activemq-5.9.1-bin.tar.gz.asc">apache-activemq-5.9.1-bin.tar.gz.asc</a></p></td></tr></tbody></table><p><structured-macro ac:macro-id="8580a58a-f79f-4dd8-b3b6-c65ca018adab" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Verify Downloads"></page></link></parameter></structured-macro></p><h2>Getting the Binaries using Maven 2</h2><p>To use this release in your maven project, the proper dependency configuration that you should use in your <a shape="rect" href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html">Maven POM</a> is:</p><structured-macro ac:macro-id="48da5127-7d2f-4e50-8a21-4e3ee60bcd87" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.9.1</version>
</dependency>
-]]></script>
-</div></div><div></div>
-
-
-<h2 id="ActiveMQ5.9.1Release-GettingtheSourceCode">Getting the Source Code</h2><h3 id="ActiveMQ5.9.1Release-SourceDistributions">Source Distributions</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source Release</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.9.1/activemq-parent-5.9.1-source-release.zip">activemq-parent-5.9.1-source-release.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://www.apache.org/dist/activemq/5.9.1/activemq-parent-5.9.1-source-release.zip.asc">activemq-parent-5.9.1-source-release.zip.asc</a></p></td></tr></tbody></table></div><h3 id="ActiveMQ5.9.1Release-SVNTagCheckout">SVN Tag Checkout</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.9.1
-]]></script>
-</div></div><h2 id="ActiveMQ5.9.1Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12323932">release notes</a></p><p>Also see the previous <a shape="rect" href="activemq-580-release.xml">ActiveMQ 5.8.0 Release</a></p></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="28b32446-5faf-42c6-8905-2eb3bc630177" ac:name="div" ac:schema-version="1"></structured-macro><h2>Getting the Source Code</h2><h3>Source Distributions</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source Release</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi?path=/activemq/5.9.1/activemq-parent-5.9.1-source-release.zip">activemq-parent-5.9.1-source-release.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://www.apache.org/dist/activemq/5.9.1/activemq-parent-5.9.1-source-release.zip.asc">activemq-parent-5.9.1-source-release.zip.asc</a></p></td></tr></tbody></table><h3>SVN Tag Checkout</h3><structured-macro ac:macro-id="477248c5-d8d4-4559-a0b4-45455c37ca95" ac:name="code" ac:schema-version="1"><plain-text-body>https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.9.1
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12323932">release notes</a></p><p>Also see the previous <link><page ri:content-title="ActiveMQ 5.8.0 Release"></page></link></p></div>
diff --git a/activemq-artemis-roadmap.xml b/activemq-artemis-roadmap.xml
index b1c8735..f2e618f 100644
--- a/activemq-artemis-roadmap.xml
+++ b/activemq-artemis-roadmap.xml
@@ -1,58 +1,2 @@
-<div class="wiki-content maincontent"><p>The goal of this page is to identify the outstanding issues that must be addressed by Artemis in order to achieve some level of feature parity with ActiveMQ 5.x. The overall objective for working toward feature parity between ActiveMQ 5.x and Artemis is for Artemis to eventually become ActiveMQ 6.x. This page exists so that we can work together as a group to achieve this goal.</p><p></p><div class="toc-macro client-side-toc-macro" data-headerelements="H1,H2,H3,H4,H5,H6,H7"></div><div class="confluence-information-macro confluence-information-macro-note"><p class="title">Work in Progress</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">This page is a work in progress and will be updated frequently.</div></div><h1 id="ActiveMQArtemisRoadmap-Usingthispage">Using this page</h1><p>Feature items can be listed, with links to JIRA tickets for longer conversation and hashing out specific feature details</p><h1 id="ActiveMQArtemisRoadmap-Features/Scenarios">Features/Scenarios</h1><p>This section should be used to identify all the ActiveMQ 5.x features that Artemis needs. This should include <strong>all</strong> Artemis features that we can identify, including those from ActiveMQ that Artemis has already implemented. This will help us to more clearly track everything that Artemis needs.</p><p> </p><h3 id="ActiveMQArtemisRoadmap-AdvisorySupport">Advisory Support</h3><ul><li>Support for broker state change advisories (master -> slave, slave -> master)</li><li>Support for connection advisories (connect, disconnect, unclean disconnect, authn fail, authz fail)</li><li>Support for consumer advisories (new consumer, closed, slow consumer)</li><li>Support for producer advisories (new producer, closed, fast producer, message size exceeded, memoryLimit reached, storage limit reached)</li><li>Support for destination advisories (new dest, deleted)</li></ul><h3 id="ActiveMQArtemisRoadmap-BrokerClustering">Broker Clustering</h3><ul><li>Support full-duplex broker-to-broker cluster connections [
- <span class="jira-issue">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/ARTEMIS-838?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/newfeature.png">ARTEMIS-838</a>
- -
- <span class="summary">Support full duplex cluster-connections</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf">Open</span>
- </span>
-]</li></ul><h3 id="ActiveMQArtemisRoadmap-ActiveMQ5.xClientCompatibility">ActiveMQ 5.x Client Compatibility</h3><ul><li>Full support of Openwire (TODO: specifically, which versions)</li></ul><h3 id="ActiveMQArtemisRoadmap-DestinationInterceptors">Destination Interceptors</h3><ul><li>Virtual Topic equivalent support [
- <span class="jira-issue">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/ARTEMIS-550?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/improvement.png">ARTEMIS-550</a>
- -
- <span class="summary">Add support for virtual topic consumers</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf">Open</span>
- </span>
-]</li></ul><h3 id="ActiveMQArtemisRoadmap-DestinationFeatures">Destination Features</h3><ul><li>Destination Policy: Garbage collection and advisory support for that activity [
- <span class="jira-issue">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/ARTEMIS-1148?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/newfeature.png">ARTEMIS-1148</a>
- -
- <span class="summary">Artemis ServerPlugin support for Address changes</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf">Open</span>
- </span>
-]</li><li>Exclusive consumer support [
- <span class="jira-issue">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/ARTEMIS-854?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/subtask_alternate.png">ARTEMIS-854</a>
- -
- <span class="summary">Create basic exclusive consumer support within the broker</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf">Open</span>
- </span>
-]</li><li>Exclusive consumer features: consumersBeforeDispatchStarts, timeBeforeDispatchStarts [
- <span class="jira-issue">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/ARTEMIS-856?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/subtask_alternate.png">ARTEMIS-856</a>
- -
- <span class="summary">Support advanced exclusive consumer config options</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf">Open</span>
- </span>
-]</li></ul><h3 id="ActiveMQArtemisRoadmap-PluginSupport">Plugin Support</h3><ul><li>Destination Policies (there is a slew of functionality in ActiveMQ 5.x dest policies that should be detailed out)</li></ul><h3 id="ActiveMQArtemisRoadmap-StorageBackend">Storage Backend</h3><ul><li>Support for multiple shared persistence stores similar to multi-kahadb (allow for storage across multiple disk volumes.. ie.  queue://ORDER.> on /mnt/order queue://BILLING.> on /mnt/billing, etc) [
- <span class="jira-issue">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/ARTEMIS-839?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/newfeature.png">ARTEMIS-839</a>
- -
- <span class="summary">Support multiple backend data stores</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf">Open</span>
- </span>
-]</li></ul><h1 id="ActiveMQArtemisRoadmap-Migration">Migration</h1><p>This section should help to answer the end user question, <em>'How do I migrate from ActiveMQ 5.x to Artemis?'</em>. This should include the identification of any tools that can help make this easier, as well as documenting information and procedures specific to migrating.</p><p> </p><p> </p><h1 id="ActiveMQArtemisRoadmap-Wishlist">Wishlist</h1><h3 id="ActiveMQArtemisRoadmap-Protocolfeatures">Protocol features</h3><ul><li><p>Exclusive consumer support across all protocols STOMP, MQTT, AMQP, etc. [
- <span class="jira-issue">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/ARTEMIS-855?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/subtask_alternate.png">ARTEMIS-855</a>
- -
- <span class="summary">Support exclusive consumer over non-JMS protocols</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf">Open</span>
- </span>
-]</p></li></ul><h3 id="ActiveMQArtemisRoadmap-KahaDBMigrationTool">KahaDB Migration Tool</h3><ul><li>Support exporting messages from KahaDB format to Artemis</li></ul><h3 id="ActiveMQArtemisRoadmap-Over-the-wiremigrationtool">Over-the-wire migration tool</h3><ul><li>Support a tool for migrating messages from ActiveMQ 5.x brokers to Artemis-based brokers (for non-standard backends)<ul><li>Goal: preserve messageId</li></ul></li></ul></div>
+<div class="wiki-content maincontent"><p>The goal of this page is to identify the outstanding issues that must be addressed by Artemis in order to achieve some level of feature parity with ActiveMQ 5.x. The overall objective for working toward feature parity between ActiveMQ 5.x and Artemis is for Artemis to eventually become ActiveMQ 6.x. This page exists so that we can work together as a group to achieve this goal.</p><p><structured-macro ac:macro-id="69b5e409-31ec-491e-ba71-9c7954ea6395" ac:name="toc" ac:schema-version="1"></structured-macro></p><structured-macro ac:macro-id="d030f30b-14a9-4ac7-a081-82d6602e5687" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Work in Progress</parameter><rich-text-body>This page is a work in progress and will be updated frequently.</rich-text-body></structured-macro><h1>Using this page</h1><p>Feature items can be listed, with links to JIRA tickets for longer conversation and hashing out specific feature details</p><h1>Features/Scenarios</h1><p>This section should be used to identify all the ActiveMQ 5.x features that Artemis needs. This should include <strong>all</strong> Artemis features that we can identify, including those from ActiveMQ that Artemis has already implemented. This will help us to more clearly track everything that Artemis needs.</p><p> </p><h3>Advisory Support</h3><ul><li>Support for broker state change advisories (master -> slave, slave -> master)</li><li>Support for connection advisories (connect, disconnect, unclean disconnect, authn fail, authz fail)</li><li>Support for consumer advisories (new consumer, closed, slow consumer)</li><li>Support for producer advisories (new producer, closed, fast producer, message size exceeded, memoryLimit reached, storage limit reached)</li><li>Support for destination advisories (new dest, deleted)</li></ul><h3>Broker Clustering</h3><ul><li>Support full-duplex broker-to-broker cluster connections [<structured-macro ac:macro-id="2adc9b54-8b9c-4e98-a888-aa9f78c8d562" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">ARTEMIS-838</parameter></structured-macro>]</li></ul><h3>ActiveMQ 5.x Client Compatibility</h3><ul><li>Full support of Openwire (TODO: specifically, which versions)</li></ul><h3>Destination Interceptors</h3><ul><li>Virtual Topic equivalent support [<structured-macro ac:macro-id="e29ce835-58d9-4501-8ce5-376c1855df9c" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">ARTEMIS-550</parameter></structured-macro>]</li></ul><h3>Destination Features</h3><ul><li>Destination Policy: Garbage collection and advisory support for that activity [<structured-macro ac:macro-id="a0f4810f-33d9-4fae-996d-1110d7192dfa" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">ARTEMIS-1148</parameter></structured-macro>]</li><li>Exclusive consumer support [<structured-macro ac:macro-id="dbcbe533-86db-44be-bcd2-ced38d521fb9" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">ARTEMIS-854</parameter></structured-macro>]</li><li>Exclusive consumer features: consumersBeforeDispatchStarts, timeBeforeDispatchStarts [<structured-macro ac:macro-id="992343df-cd81-403f-a240-70ed09c45ed2" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">ARTEMIS-856</parameter></structured-macro>]</li></ul><h3>Plugin Support</h3><ul><li>Destination Policies (there is a slew of functionality in ActiveMQ 5.x dest policies that should be detailed out)</li></ul><h3>Storage Backend</h3><ul><li>Support for multiple shared persistence stores similar to multi-kahadb (allow for storage across multiple disk volumes.. ie.  queue://ORDER.> on /mnt/order queue://BILLING.> on /mnt/billing, etc) [<structured-macro ac:macro-id="045abe40-7168-41f9-b3ca-95fea254ad44" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">ARTEMIS-839</parameter></structured-macro>]</li></ul><h1>Migration</h1><p>This section should help to answer the end user question, <em>'How do I migrate from ActiveMQ 5.x to Artemis?'</em>. This should include the identification of any tools that can help make this easier, as well as documenting information and procedures specific to migrating.</p><p> </p><p> </p><h1>Wishlist</h1><h3>Protocol features</h3><ul><li><p>Exclusive consumer support across all protocols STOMP, MQTT, AMQP, etc. [<structured-macro ac:macro-id="206ce9fb-b130-409f-abeb-7b12907c5245" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">ARTEMIS-855</parameter></structured-macro>]</p></li></ul><h3>KahaDB Migration Tool</h3><ul><li>Support exporting messages from KahaDB format to Artemis</li></ul><h3>Over-the-wire migration tool</h3><ul><li>Support a tool for migrating messages from ActiveMQ 5.x brokers to Artemis-based brokers (for non-standard backends)<ul><li>Goal: preserve messageId</li></ul></li></ul></div>
diff --git a/activemq-c-clients.xml b/activemq-c-clients.xml
index 9e54bc3..c8e897f 100644
--- a/activemq-c-clients.xml
+++ b/activemq-c-clients.xml
@@ -1,4 +1,5 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQC++Clients-ActiveMQC++Integration">ActiveMQ C++ Integration</h2>
+<div class="wiki-content maincontent"><h2>ActiveMQ C++ Integration</h2>
-<p><a shape="rect" class="external-link" href="http://activemq.apache.org/cms/">CMS</a> is an easy-to-use JMS 1.1-like API. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.</p></div>
+<p><a shape="rect" href="http://activemq.apache.org/cms/">CMS</a> is an easy-to-use JMS 1.1-like API. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.</p>
+</div>
diff --git a/activemq-c-development.xml b/activemq-c-development.xml
index 9aa399e..fb86781 100644
--- a/activemq-c-development.xml
+++ b/activemq-c-development.xml
@@ -1,16 +1,16 @@
-<div class="wiki-content maincontent"><h1 id="ActiveMQCDevelopment-ActiveMQCPPDevelopmentPage">ActiveMQ CPP Development Page</h1>
+<div class="wiki-content maincontent"><h1>ActiveMQ CPP Development Page</h1>
<p>This page documents current and planned development of ActiveMQ CPP.  The table below lists development tasks and their current status</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Development Activeity <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Status <br clear="none" class="atl-forced-newline"> </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Openwire Support <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> in-progress <br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Development Activeity <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1"><p> Status <br clear="none" class="atl-forced-newline"> </p></th></tr><tr><td colspan="1" rowspan="1"><p> Openwire Support <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> in-progress <br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table>
-<h3 id="ActiveMQCDevelopment-OpenwireSupport"> Openwire Support</h3>
+<h3> Openwire Support</h3>
<p>This task adds support for the OpenWire protocol to ActiveMQ CPP.  The tasks involves the addition of new code, the activities are listed below, as well as who is working on them and what the status of each is.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Task Description <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Assigned to <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Status <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Task Info <br clear="none" class="atl-forced-newline"> </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Openwire Command / Marshallers generation scripts <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> In-Progress <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Loose Marshalling works, Tight still not working <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> WireFormat Negotiation Framework <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Mimic the DotNet version? <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Primitives Map <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Nate Mittler <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Completed </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Needs more testing for memory leaks and performance. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Primitive Map Marshalling <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Needs more testing, for leaks etc.  Add nested maps, lists. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> BaseDataStreamMarshallers Port <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> In-Progress <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Done, but serious unit testing is needed <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> BooleanStream Port <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Done <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> OpenWire Connector Framework Classes <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Tim / Nate <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Needs lots of testing <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> DataInputStreams / DataOutputStreams <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Done </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Task Description <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1"><p> Assigned to <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1"><p> Status <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1"><p> Task Info <br clear="none" class="atl-forced-newline"> </p></th></tr><tr><td colspan="1" rowspan="1"><p> Openwire Command / Marshallers generation scripts <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> In-Progress <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Loose Marshalling works, Tight still not working <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> WireFormat Negotiation Framework <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Mimic the DotNet version? <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Primitives Map <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Nate Mittler <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Completed </p></td><td colspan="1" rowspan="1"><p> Needs more testing for memory leaks and performance. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Primitive Map Marshalling <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Needs more testing, for leaks etc.  Add nested maps, lists. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> BaseDataStreamMarshallers Port <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> In-Progress <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Done, but serious unit testing is needed <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> BooleanStream Port <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Done <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> OpenWire Connector Framework Classes <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Tim / Nate <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Needs lots of testing <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> DataInputStreams / DataOutputStreams <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Tim Bish <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Completed <br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Done </p></td></tr></tbody></table>
-<h2 id="ActiveMQCDevelopment-OutstandingIssues">Outstanding Issues</h2>
+<h2>Outstanding Issues</h2>
<p>This section document issues that are outstanding...TDB</p></div>
diff --git a/activemq-command-line-tools-reference.xml b/activemq-command-line-tools-reference.xml
index d9e1cff..1e763e4 100644
--- a/activemq-command-line-tools-reference.xml
+++ b/activemq-command-line-tools-reference.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="ActiveMQCommandLineToolsReference-CommandLineTools">Command Line Tools</h1><p>The current script contains the entire functionality to manage activemq.</p><ul><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-activemq">activemq</a> - runs an activemq broker<br clear="none">(see <a shape="rect" href="unix-shell-script.xml">Unix Shell Script</a>)</li></ul><p>In versions prior 5.4.1 some management functionalities beyond controlling the service itself where part of the "activemq-admin" script.<br clear="none">This script is currently still part of the distribution to provide access to this for Windows users-</p><ul><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-activemq-admin">activemq-admin</a> - manages a broker instance</li></ul><p>In versions prior to 5.0 the functionality of activemq-admin script was scattered over multiple scripts, such as:</p><ul><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-stop">shutdown</a> - shutdowns an activemq broker</li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-list">list</a> - lists all running brokers in the specified JMX context</li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-query">query</a> - queries the JMX context for broker statistics and information</li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-bstat">bstat</a> - predefined query that displays useful broker statistics</li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-browse">browse</a> - browse the messages of a specific queue</li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-purge">purge</a> - delete selected destination's messages that matches the message selector</li></ul><p><span class="confluence-anchor-link" id="ActiveMQCommandLineToolsReference-activemq"></span></p><h2 id="ActiveMQCommandLineToolsReference-activemqscript">activemq script<br clear="none"><br clear="none"></h2><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><strong>Description of this script is valid for Windows platform.</strong> For Unix platform it is valid for broker versions prior to 5.4.0. With version 5.4.0 and later, ActiveMQ comes with enhanced <a shape="rect" href="unix-shell-script.xml">Unix Shell Script</a></p></div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Script Name</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq.bat, activemq</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Usage</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><em>activemq [options] [config]</em> or <em>java -jar run.jar start [options] [config]</em></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>Script to run an activemq broker either by specifying a broker configuration file or through a broker URI configuration.</p></td></tr></tbody></table></div><p><strong>Options:</strong></p><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>Syntax</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>System Define Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Help Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq --help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the help messages for the activemq script.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Version Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq --version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the activemq version information.</p></td></tr></tbody></table></div><p><strong>Examples:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Runs a broker using the default 'xbean:activemq.xml' as the broker configuration file.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq xbean:myconfig.xml</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Runs a broker using the file myconfig.xml as the broker configuration file that is located in the classpath.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq xbean:file:./conf/broker1.xml</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Runs a broker using the file broker1.xml as the broker configuration file that is located in the relative file path ./conf/broker1.xml</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq xbean:file:C:/ActiveMQ/conf/broker2.xml</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Runs a broker using the file broker2.xml as the broker configuration file that is located in the absolute file path C:/ActiveMQ/conf/broker2.xml</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq broker:(tcp://localhost:61616, tcp://localhost:5000)?useJmx=true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Runs a broker with two transport connectors and JMX enabled.¹</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq broker:(tcp://localhost:61616, network:tcp://localhost:5000)?persistent=false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Runs a broker with 1 transport connector and 1 network connector with persistence disabled.¹</p></td></tr></tbody></table></div><p>For details on how to configure using broker URI refer to: <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a></p><p><span class="confluence-anchor-link" id="ActiveMQCommandLineToolsReference-activemq-admin"></span></p><h2 id="ActiveMQCommandLineToolsReference-activemq-admin">activemq-admin</h2><p>As of ActiveMQ 5.x, the above standalone utilities have been incorporated into the activemq-admin command (with the exception of the activemq script), as follows:</p><ul><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-stop">activemq-admin stop</a></li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-list">activemq-admin list</a></li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-query">activemq-admin query</a></li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-bstat">activemq-admin bstat</a></li><li><a shape="rect" href="#ActiveMQCommandLineToolsReference-browse">activemq-admin browse</a></li></ul><p>The syntax of each task remains as described below. Note also that the activemq command is still supported.</p><p><span class="confluence-anchor-link" id="ActiveMQCommandLineToolsReference-stop"></span></p><h3 id="ActiveMQCommandLineToolsReference-stoptask">stop task</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Name</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>stop</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Usage</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><em>activemq-admin stop [options] [broker names]</em></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>Script to stop a running activemq broker. This task requires that JMX is enabled.</p></td></tr></tbody></table></div><p><strong>Options:</strong></p><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>Syntax</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Stop All Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--all</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>stop --all</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Stops all registered brokers in the specified JMX context</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMX URL Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxurl <url></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxurl service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Change the JMX service url to connect to. By default it connects to: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMX Authentication Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxuser user --jmxpassword password</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxuser smx --jmxpassword smx</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For cases where username/password based authentication of the JMX client is required. Not set by default.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>System Define Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Help Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the help messages for the stop script.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Version Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq --version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the activemq version information.</p></td></tr></tbody></table></div><p><strong>Examples:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin stop</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Stops the only running broker in the default JMX context. It assumes that there is only one running broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin stop --jmxurl service:jmx:rmi:///jndi/rmi://remotehost:1099/jmxrmi --all</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Stops all the running broker in the specified JMX context.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin stop localhost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Stops the broker named 'localhost' in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin stop localhost remotehost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Stops the brokers 'localhost' and 'remotehost' in the default JMX context.</p></td></tr></tbody></table></div><p><span class="confluence-anchor-link" id="ActiveMQCommandLineToolsReference-list"></span></p><h3 id="ActiveMQCommandLineToolsReference-listtask">list task</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Name</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>list</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Usage</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><em>activemq-admin list [options]</em></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>Script to list the names of all running brokers in the specified JMX context. This task requires that JMX is enabled.</p></td></tr></tbody></table></div><p><strong>Options:</strong></p><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>Syntax</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMX URL Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxurl <url></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxurl service:jmx:rmi:///jndi/rmi://remotehost:1099/jmxrmi</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Change the JMX service url to connect to. By default it connects to: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMX Authentication Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxuser user --jmxpassword password</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxuser smx --jmxpassword smx</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For cases where username/password based authentication of the JMX client is required. Not set by default.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>System Define Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Help Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the help messages for the list script.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Version Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq --version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the activemq version information.</p></td></tr></tbody></table></div><p><strong>Examples:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin list</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Lists the names of all running brokers in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin list --jmxurl service:jmx:rmi:///jndi/rmi://remotehost:1099/jmxrmi</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>List the names of all running brokers in the specified JMX context.</p></td></tr></tbody></table></div><p><span class="confluence-anchor-link" id="ActiveMQCommandLineToolsReference-query"></span></p><h3 id="ActiveMQCommandLineToolsReference-querytask">query task</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Name</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>query</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Usage</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><em>activemq-admin query [options]</em></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>Script to query the specified JMX context for mbean attributes and information. This script requires that JMX is enabled.</p></td></tr></tbody></table></div><p><strong>Options:</strong></p><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>Syntax</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Predefined Query Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-Q<type>=<name></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-QTopic=TEST.FOO, -QBroker=*host</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Predefined object name query option that queries a specific type of mbean object based on its type and selected identifier. Refer to the mbean reference table below for details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-xQ<type>=<name></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-xQTopic=ActiveMQ.Advisory.*, -xQNetworkConnector=*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Predefined object name query option that removes all mbeans that matches the query from the search result. Refer to the mbean reference table below for details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Object Name Query Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--objname <object name query></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--objname Type=<strong>Connect</strong>,BrokerName=local*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Query option loosely based on the JMX object name format, which lets you filter mbeans based on their object name information. Refer to the mbean reference table below for details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--xobjname <object name query></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--xobjname Type=Topic,Destination=ActiveMQ.Advisory.*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Object name query that removes all mbeans that matches the query from the search result. Refer to the mbean reference table below for details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>View Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--view <view list></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--view Type,BrokerName,Destination,EnqueueCount,DequeueCount</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Lets you specify the attributes and object name information to view. If the view is omitted, all attributes and information will be displayed.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMX URL Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxurl <url></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxurl service:jmx:rmi:///jndi/rmi://remotehost:1099/jmxrmi</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Change the JMX service url to connect to. By default it connects to: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMX Authentication Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxuser user --jmxpassword password</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxuser smx --jmxpassword smx</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For cases where username/password based authentication of the JMX client is required. Not set by default.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>System Define Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Help Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the help messages for the query script.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Version Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq --version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the activemq version information.</p></td></tr></tbody></table></div><p><strong>Examples:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin query</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display all attributes and object name information of all registered mbeans in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin query -QTopic=TEST.FOO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display all the attributes and object name information of the destination topic 'TEST.FOO'</p></td></tr></tbody></table></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin query -QQueue=*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display all the attributes and object name information of all registered queues.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin query -QTopic=*.FOO -xQTopic=ActiveMQ.Advisory.*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display all the attributes and object name information of all topics that ends with '.FOO' except those that also begins with 'ActiveMQ.Advisory.'.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin query -QBroker=local???? --view Type,BrokerName,EnqueueCount,DequeueCount</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the object type, broker name, enqueue count, and dequeue count information for all 9-letter brokers that begins with 'local'.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin query --objname Type=<strong>Connect</strong>,BrokerName=localhost -xQNetworkConnector=*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display all the attributes and object name information for all connections and connectors for broker 'localhost' except its network connectors.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin query --objname Type=Connection --xobjname Type=Connection,BrokerName=localhost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display all the attributes and object name information for all registered connections except those belonging to broker 'localhost'.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin query -QQueue=???? --objname Type=Connection --xobjname BrokerName=remote*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display all the attributes and object name information for all 4-letter queues and connections except those belonging to a broker that begins with 'remote'.</p></td></tr></tbody></table></div><p><strong>ActiveMQ MBean Reference:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Mbean Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Properties / ObjectName</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Attributes</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Broker</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>Type</strong>=Broker</li><li><strong>BrokerName</strong>=<broker identifier></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>BrokerId</li><li>TotalEnqueueCount</li><li>TotalDequeueCount</li><li>TotalConsumerCount</li><li>TotalMessages</li><li>TotalMessagesCached</li><li>MemoryLimit</li><li>MemoryPercentageUsed</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Destination</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>Type</strong>=Queue|Topic</li><li><strong>Destination</strong>=<destination identifier></li><li><strong>BrokerName</strong>=<name of broker></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>EnqueueCount</li><li>DequeueCount</li><li>ConsumerCount</li><li>Messages</li><li>MessagesCached</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>NetworkConnector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>Type</strong>=NetworkConnector</li><li><strong>BrokerName</strong>=<connector identifierr></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Connector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>Type</strong>=Connector</li><li><strong>ConnectorName</strong>=<connector identifier></li><li><strong>BrokerName</strong>=<name of broker></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>EnqueueCount</li><li>DequeueCount</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Connection</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>Type</strong>=Connection</li><li><strong>Connection</strong>=<connection identifier></li><li><strong>BrokerName</strong>=<name of broker></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>EnqueueCount</li><li>DequeueCount</li><li>DispatchQueueSize</li><li>Active</li><li>Blocked</li><li>Connected</li><li>Slow</li></ul></td></tr></tbody></table></div><p><span class="confluence-anchor-link" id="ActiveMQCommandLineToolsReference-bstat"></span></p><h3 id="ActiveMQCommandLineToolsReference-bstattask">bstat task</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Name</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>bstat</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Usage</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><em>activemq-admin bstat</em> [broker name]</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>Predefined query script that displays useful statistics regarding a broker and its components.</p></td></tr></tbody></table></div><p><strong>Examples:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin bstat</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display useful statistics for all registered brokers in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin bstat localhost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display useful statistics for the registered broker 'localhost'.</p></td></tr></tbody></table></div><p><span class="confluence-anchor-link" id="ActiveMQCommandLineToolsReference-browse"></span></p><h3 id="ActiveMQCommandLineToolsReference-browsetask">browse task</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Name</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>browse</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Usage</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><em>activemq-admin browse --amqurl <broker url> [options] <destinations></em> or <em>java -jar run.jar browse --amqurl <broker url> [options] <destinations></em></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>Script to browse selected destinations' messages.  The browse operation may not return all messages due to limitations of broker configuration and system resources.</p></td></tr></tbody></table></div><p><strong>Options:</strong></p><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>Syntax</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Broker URL Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--amqurl <url></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--amqurl tcp://localhost:61616</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specify the broker URL to connect to.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Message Selector Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--msgsel "<msgsel1,msgsel2,...>"</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--msgsel "JMSMessageID='*:10',JMSPriority>5"</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows you to filter the specific messages to view. Place the entire selector criteria in double quotes " ". You can use wildcard queries by enclosing the string message property in ' '. Other than using wildcard queries to filter string properties, other queries follows the message selector format.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Group View Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-V[header | custom | body]</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-Vheader, -Vcustom, -Vbody</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Let's you specify a specific group of message attributes to view. The header view shows all the standard JMS message headers. The custom view shows all the custom fields added to each JMS message. The body view shows the message body of the JMS message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Specific View Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--view <attr1>,[header:|custom:]<attr2>,...</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--view JMSMessageID='*:10',custom:MyCustomField</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Let's you specifically select a specific message attribute. It allows you to select specific attributes from the JMS and custom headers. You could add the tags header: and custom: to explicitly specify where the attribute belongs to. Refer to the message header table below for details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>System Define Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Help Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the help messages for the browse script.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Version Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq --version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the activemq version information.</p></td></tr></tbody></table></div><p><strong>Examples:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin browse --amqurl tcp://localhost:61616 TEST.FOO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Prints the JMS message header, custom message header, and message body of the messages in the queue 'TEST.FOO'</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin browse --amqurl tcp://localhost:61616 -Vheader,body TEST.FOO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Prints the JMS message header and message body of the messages in the queue 'TEST.FOO'</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin browse --amqurl tcp://localhost:61616 -Vheader --view custom:MyCustomField TEST.FOO TEST.BAR</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Prints all the JMS message header and the custom field 'MyCustomField' of the messages in the queue 'TEST.FOO' and 'TEST.BAR'.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin browse --amqurl tcp://localhost:61616 --msgsel "JMSMessageID='*:10',JMSPriority>5" TEST.FOO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Prints all the attributes of the messages in the queue 'TEST.FOO' that has a JMSMessageID that matches the wildcard query *:10 and has a JMSPriority greater than 5.</p></td></tr></tbody></table></div><p><strong>JMS Message Header Reference:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Header Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Header Type</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSCorrelation ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSDelivery Mode</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>int (1-Non-Persistent, 2-Persistent)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSDestination</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>javax.jms.Destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSExpiration</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>long</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSMessageID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSPriority</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>int</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSRedelivered</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>boolean</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSReplyTo</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>javax.jms.Destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSTimestamp</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>long</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMSType</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td></tr></tbody></table></div><p><span class="confluence-anchor-link" id="ActiveMQCommandLineToolsReference-purge"></span></p><h3 id="ActiveMQCommandLineToolsReference-purgetask">purge task</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Name</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>purge</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Usage</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><em>activemq-admin purge</em> [purge-options] <destinations></p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>Delete selected destination's messages that matches the message selector.</p></td></tr></tbody></table></div><p><strong>Options:</strong></p><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>Syntax</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMX URL Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxurl <url></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxurl service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Change the JMX service url to connect to. By default it connects to: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>JMX Authentication Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxuser user --jmxpassword password</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--jmxuser smx --jmxpassword smx</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For cases where username/password based authentication of the JMX client is required. Not set by default.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Message Selector Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--msgsel "<msgsel1,msgsel2,...>"</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--msgsel "JMSMessageID='*:10',JMSPriority>5"</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows you to filter the specific messages to view. Place the entire selector criteria in double quotes " ". You can use wildcard queries by enclosing the string message property in ' '. Other than using wildcard queries to filter string properties, other queries follows the message selector format.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>System Define Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Help Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--help</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the help messages for the browse script.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Version Option</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>--version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq --version</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display the activemq version information.</p></td></tr></tbody></table></div><p><strong>Examples:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin purge FOO.BAR</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Delete all the messages in queue FOO.BAR</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin purge --msgsel "JMSMessageID='*:10',JMSPriority>5" FOO.*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Delete all the messages in the destinations that matches FOO.* and has a JMSMessageID in", the header field that matches the wildcard *:10, and has a JMSPriority field > 5 in the", queue FOO.BAR <br clear="none"> To use wildcard queries, the field must be a string and the query enclosed in ''</p></td></tr></tbody></table></div><h3 id="ActiveMQCommandLineToolsReference-dstattask">dstat task</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Name</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>dstat</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Task Usage</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p><em>activemq-admin dstat</em> [destination type]</p></td></tr><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p>Predefined query script that displays useful statistics regarding destinations on a broker.</p></td></tr></tbody></table></div><p><strong>Examples:</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin dstat</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display useful statistics for all destinations on the broker in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-admin dstat topics</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Display useful statistics for the Topics that currently exist on the Broker.</p></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><h1>Command Line Tools</h1><p>The current script contains the entire functionality to manage activemq.</p><ul><li><link ac:anchor="activemq"></link> - runs an activemq broker<br clear="none">(see <link><page ri:content-title="Unix Shell Script"></page></link>)</li></ul><p>In versions prior 5.4.1 some management functionalities beyond controlling the service itself where part of the "activemq-admin" script.<br clear="none">This script is currently still part of the distribution to provide access to this for Windows users-</p><ul><li><link ac:anchor="activemq-admin"></link> - manages a broker instance</li></ul><p>In versions prior to 5.0 the functionality of activemq-admin script was scattered over multiple scripts, such as:</p><ul><li><link ac:anchor="stop"><plain-text-link-body>shutdown</plain-text-link-body></link> - shutdowns an activemq broker</li><li><link ac:anchor="list"></link> - lists all running brokers in the specified JMX context</li><li><link ac:anchor="query"></link> - queries the JMX context for broker statistics and information</li><li><link ac:anchor="bstat"></link> - predefined query that displays useful broker statistics</li><li><link ac:anchor="browse"></link> - browse the messages of a specific queue</li><li><link ac:anchor="purge"></link> - delete selected destination's messages that matches the message selector</li></ul><p><structured-macro ac:macro-id="02495172-e5eb-48f0-8318-c4ff5647a8e3" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">activemq</parameter></structured-macro></p><h2>activemq script<br clear="none"><br clear="none"></h2><structured-macro ac:macro-id="ec719b30-dc47-4944-91ed-20e2eb36914c" ac:name="note" ac:schema-version="1"><rich-text-body><p><strong>Description of this script is valid for Windows platform.</strong> For Unix platform it is valid for broker versions prior to 5.4.0. With version 5.4.0 and later, ActiveMQ comes with enhanced <link><page ri:content-title="Unix Shell Script"></page></link></p></rich-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Script Name</p></th><td colspan="1" rowspan="1"><p>activemq.bat, activemq</p></td></tr><tr><th colspan="1" rowspan="1"><p>Task Usage</p></th><td colspan="1" rowspan="1"><p><em>activemq [options] [config]</em> or <em>java -jar run.jar start [options] [config]</em></p></td></tr><tr><th colspan="1" rowspan="1"><p>Description</p></th><td colspan="1" rowspan="1"><p>Script to run an activemq broker either by specifying a broker configuration file or through a broker URI configuration.</p></td></tr></tbody></table><p><strong>Options:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Syntax</p></th><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>System Define Option</p></td><td colspan="1" rowspan="1"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>Help Option</p></td><td colspan="1" rowspan="1"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1"><p>activemq --help</p></td><td colspan="1" rowspan="1"><p>Display the help messages for the activemq script.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Version Option</p></td><td colspan="1" rowspan="1"><p>--version</p></td><td colspan="1" rowspan="1"><p>activemq --version</p></td><td colspan="1" rowspan="1"><p>Display the activemq version information.</p></td></tr></tbody></table><p><strong>Examples:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq</p></td><td colspan="1" rowspan="1"><p>Runs a broker using the default 'xbean:activemq.xml' as the broker configuration file.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq xbean:myconfig.xml</p></td><td colspan="1" rowspan="1"><p>Runs a broker using the file myconfig.xml as the broker configuration file that is located in the classpath.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq xbean:file:./conf/broker1.xml</p></td><td colspan="1" rowspan="1"><p>Runs a broker using the file broker1.xml as the broker configuration file that is located in the relative file path ./conf/broker1.xml</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq xbean:file:C:/ActiveMQ/conf/broker2.xml</p></td><td colspan="1" rowspan="1"><p>Runs a broker using the file broker2.xml as the broker configuration file that is located in the absolute file path C:/ActiveMQ/conf/broker2.xml</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq broker:(tcp://localhost:61616, tcp://localhost:5000)?useJmx=true</p></td><td colspan="1" rowspan="1"><p>Runs a broker with two transport connectors and JMX enabled.¹</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq broker:(tcp://localhost:61616, network:tcp://localhost:5000)?persistent=false</p></td><td colspan="1" rowspan="1"><p>Runs a broker with 1 transport connector and 1 network connector with persistence disabled.¹</p></td></tr></tbody></table><p>For details on how to configure using broker URI refer to: <link><page ri:content-title="Broker Configuration URI"></page></link></p><p><structured-macro ac:macro-id="a3804351-d111-4c58-b42c-e4a84ece705b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">activemq-admin</parameter></structured-macro></p><h2>activemq-admin</h2><p>As of ActiveMQ 5.x, the above standalone utilities have been incorporated into the activemq-admin command (with the exception of the activemq script), as follows:</p><ul><li><link ac:anchor="stop"><plain-text-link-body>activemq-admin stop</plain-text-link-body></link></li><li><link ac:anchor="list"><plain-text-link-body>activemq-admin list</plain-text-link-body></link></li><li><link ac:anchor="query"><plain-text-link-body>activemq-admin query</plain-text-link-body></link></li><li><link ac:anchor="bstat"><plain-text-link-body>activemq-admin bstat</plain-text-link-body></link></li><li><link ac:anchor="browse"><plain-text-link-body>activemq-admin browse</plain-text-link-body></link></li></ul><p>The syntax of each task remains as described below. Note also that the activemq command is still supported.</p><p><structured-macro ac:macro-id="9f87a0cb-cbd3-4abc-9afd-7e4c0a4d1b4e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">stop</parameter></structured-macro></p><h3>stop task</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Task Name</p></th><td colspan="1" rowspan="1"><p>stop</p></td></tr><tr><th colspan="1" rowspan="1"><p>Task Usage</p></th><td colspan="1" rowspan="1"><p><em>activemq-admin stop [options] [broker names]</em></p></td></tr><tr><th colspan="1" rowspan="1"><p>Description</p></th><td colspan="1" rowspan="1"><p>Script to stop a running activemq broker. This task requires that JMX is enabled.</p></td></tr></tbody></table><p><strong>Options:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Syntax</p></th><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>Stop All Option</p></td><td colspan="1" rowspan="1"><p>--all</p></td><td colspan="1" rowspan="1"><p>stop --all</p></td><td colspan="1" rowspan="1"><p>Stops all registered brokers in the specified JMX context</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMX URL Option</p></td><td colspan="1" rowspan="1"><p>--jmxurl <url></p></td><td colspan="1" rowspan="1"><p>--jmxurl service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td><td colspan="1" rowspan="1"><p>Change the JMX service url to connect to. By default it connects to: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMX Authentication Option</p></td><td colspan="1" rowspan="1"><p>--jmxuser user --jmxpassword password</p></td><td colspan="1" rowspan="1"><p>--jmxuser smx --jmxpassword smx</p></td><td colspan="1" rowspan="1"><p>For cases where username/password based authentication of the JMX client is required. Not set by default.</p></td></tr><tr><td colspan="1" rowspan="1"><p>System Define Option</p></td><td colspan="1" rowspan="1"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>Help Option</p></td><td colspan="1" rowspan="1"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1"><p>--help</p></td><td colspan="1" rowspan="1"><p>Display the help messages for the stop script.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Version Option</p></td><td colspan="1" rowspan="1"><p>--version</p></td><td colspan="1" rowspan="1"><p>activemq --version</p></td><td colspan="1" rowspan="1"><p>Display the activemq version information.</p></td></tr></tbody></table><p><strong>Examples:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin stop</p></td><td colspan="1" rowspan="1"><p>Stops the only running broker in the default JMX context. It assumes that there is only one running broker.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin stop --jmxurl service:jmx:rmi:///jndi/rmi://remotehost:1099/jmxrmi --all</p></td><td colspan="1" rowspan="1"><p>Stops all the running broker in the specified JMX context.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin stop localhost</p></td><td colspan="1" rowspan="1"><p>Stops the broker named 'localhost' in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin stop localhost remotehost</p></td><td colspan="1" rowspan="1"><p>Stops the brokers 'localhost' and 'remotehost' in the default JMX context.</p></td></tr></tbody></table><p><structured-macro ac:macro-id="6801ac7e-543d-4646-8225-36df3eb041a2" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">list</parameter></structured-macro></p><h3>list task</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Task Name</p></th><td colspan="1" rowspan="1"><p>list</p></td></tr><tr><th colspan="1" rowspan="1"><p>Task Usage</p></th><td colspan="1" rowspan="1"><p><em>activemq-admin list [options]</em></p></td></tr><tr><th colspan="1" rowspan="1"><p>Description</p></th><td colspan="1" rowspan="1"><p>Script to list the names of all running brokers in the specified JMX context. This task requires that JMX is enabled.</p></td></tr></tbody></table><p><strong>Options:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Syntax</p></th><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>JMX URL Option</p></td><td colspan="1" rowspan="1"><p>--jmxurl <url></p></td><td colspan="1" rowspan="1"><p>--jmxurl service:jmx:rmi:///jndi/rmi://remotehost:1099/jmxrmi</p></td><td colspan="1" rowspan="1"><p>Change the JMX service url to connect to. By default it connects to: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMX Authentication Option</p></td><td colspan="1" rowspan="1"><p>--jmxuser user --jmxpassword password</p></td><td colspan="1" rowspan="1"><p>--jmxuser smx --jmxpassword smx</p></td><td colspan="1" rowspan="1"><p>For cases where username/password based authentication of the JMX client is required. Not set by default.</p></td></tr><tr><td colspan="1" rowspan="1"><p>System Define Option</p></td><td colspan="1" rowspan="1"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>Help Option</p></td><td colspan="1" rowspan="1"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1"><p>--help</p></td><td colspan="1" rowspan="1"><p>Display the help messages for the list script.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Version Option</p></td><td colspan="1" rowspan="1"><p>--version</p></td><td colspan="1" rowspan="1"><p>activemq --version</p></td><td colspan="1" rowspan="1"><p>Display the activemq version information.</p></td></tr></tbody></table><p><strong>Examples:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin list</p></td><td colspan="1" rowspan="1"><p>Lists the names of all running brokers in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin list --jmxurl service:jmx:rmi:///jndi/rmi://remotehost:1099/jmxrmi</p></td><td colspan="1" rowspan="1"><p>List the names of all running brokers in the specified JMX context.</p></td></tr></tbody></table><p><structured-macro ac:macro-id="36aa53c3-86fd-402d-9eb1-8fb13ac5b9bf" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">query</parameter></structured-macro></p><h3>query task</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Task Name</p></th><td colspan="1" rowspan="1"><p>query</p></td></tr><tr><th colspan="1" rowspan="1"><p>Task Usage</p></th><td colspan="1" rowspan="1"><p><em>activemq-admin query [options]</em></p></td></tr><tr><th colspan="1" rowspan="1"><p>Description</p></th><td colspan="1" rowspan="1"><p>Script to query the specified JMX context for mbean attributes and information. This script requires that JMX is enabled.</p></td></tr></tbody></table><p><strong>Options:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Syntax</p></th><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>Predefined Query Option</p></td><td colspan="1" rowspan="1"><p>-Q<type>=<name></p></td><td colspan="1" rowspan="1"><p>-QTopic=TEST.FOO, -QBroker=*host</p></td><td colspan="1" rowspan="1"><p>Predefined object name query option that queries a specific type of mbean object based on its type and selected identifier. Refer to the mbean reference table below for details.</p></td></tr><tr><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p>-xQ<type>=<name></p></td><td colspan="1" rowspan="1"><p>-xQTopic=ActiveMQ.Advisory.*, -xQNetworkConnector=*</p></td><td colspan="1" rowspan="1"><p>Predefined object name query option that removes all mbeans that matches the query from the search result. Refer to the mbean reference table below for details.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Object Name Query Option</p></td><td colspan="1" rowspan="1"><p>--objname <object name query></p></td><td colspan="1" rowspan="1"><p>--objname Type=<strong>Connect</strong>,BrokerName=local*</p></td><td colspan="1" rowspan="1"><p>Query option loosely based on the JMX object name format, which lets you filter mbeans based on their object name information. Refer to the mbean reference table below for details.</p></td></tr><tr><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p>--xobjname <object name query></p></td><td colspan="1" rowspan="1"><p>--xobjname Type=Topic,Destination=ActiveMQ.Advisory.*</p></td><td colspan="1" rowspan="1"><p>Object name query that removes all mbeans that matches the query from the search result. Refer to the mbean reference table below for details.</p></td></tr><tr><td colspan="1" rowspan="1"><p>View Option</p></td><td colspan="1" rowspan="1"><p>--view <view list></p></td><td colspan="1" rowspan="1"><p>--view Type,BrokerName,Destination,EnqueueCount,DequeueCount</p></td><td colspan="1" rowspan="1"><p>Lets you specify the attributes and object name information to view. If the view is omitted, all attributes and information will be displayed.</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMX URL Option</p></td><td colspan="1" rowspan="1"><p>--jmxurl <url></p></td><td colspan="1" rowspan="1"><p>--jmxurl service:jmx:rmi:///jndi/rmi://remotehost:1099/jmxrmi</p></td><td colspan="1" rowspan="1"><p>Change the JMX service url to connect to. By default it connects to: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMX Authentication Option</p></td><td colspan="1" rowspan="1"><p>--jmxuser user --jmxpassword password</p></td><td colspan="1" rowspan="1"><p>--jmxuser smx --jmxpassword smx</p></td><td colspan="1" rowspan="1"><p>For cases where username/password based authentication of the JMX client is required. Not set by default.</p></td></tr><tr><td colspan="1" rowspan="1"><p>System Define Option</p></td><td colspan="1" rowspan="1"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>Help Option</p></td><td colspan="1" rowspan="1"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1"><p>--help</p></td><td colspan="1" rowspan="1"><p>Display the help messages for the query script.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Version Option</p></td><td colspan="1" rowspan="1"><p>--version</p></td><td colspan="1" rowspan="1"><p>activemq --version</p></td><td colspan="1" rowspan="1"><p>Display the activemq version information.</p></td></tr></tbody></table><p><strong>Examples:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin query</p></td><td colspan="1" rowspan="1"><p>Display all attributes and object name information of all registered mbeans in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin query -QTopic=TEST.FOO</p></td><td colspan="1" rowspan="1"><p>Display all the attributes and object name information of the destination topic 'TEST.FOO'</p></td></tr></tbody></table><table><tbody><tr><td colspan="1" rowspan="1"><p>activemq-admin query -QQueue=*</p></td><td colspan="1" rowspan="1"><p>Display all the attributes and object name information of all registered queues.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin query -QTopic=*.FOO -xQTopic=ActiveMQ.Advisory.*</p></td><td colspan="1" rowspan="1"><p>Display all the attributes and object name information of all topics that ends with '.FOO' except those that also begins with 'ActiveMQ.Advisory.'.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin query -QBroker=local???? --view Type,BrokerName,EnqueueCount,DequeueCount</p></td><td colspan="1" rowspan="1"><p>Display the object type, broker name, enqueue count, and dequeue count information for all 9-letter brokers that begins with 'local'.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin query --objname Type=<strong>Connect</strong>,BrokerName=localhost -xQNetworkConnector=*</p></td><td colspan="1" rowspan="1"><p>Display all the attributes and object name information for all connections and connectors for broker 'localhost' except its network connectors.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin query --objname Type=Connection --xobjname Type=Connection,BrokerName=localhost</p></td><td colspan="1" rowspan="1"><p>Display all the attributes and object name information for all registered connections except those belonging to broker 'localhost'.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin query -QQueue=???? --objname Type=Connection --xobjname BrokerName=remote*</p></td><td colspan="1" rowspan="1"><p>Display all the attributes and object name information for all 4-letter queues and connections except those belonging to a broker that begins with 'remote'.</p></td></tr></tbody></table><p><strong>ActiveMQ MBean Reference:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Mbean Type</p></th><th colspan="1" rowspan="1"><p>Properties / ObjectName</p></th><th colspan="1" rowspan="1"><p>Attributes</p></th></tr><tr><td colspan="1" rowspan="1"><p>Broker</p></td><td colspan="1" rowspan="1"><ul><li><strong>Type</strong>=Broker</li><li><strong>BrokerName</strong>=<broker identifier></li></ul></td><td colspan="1" rowspan="1"><ul><li>BrokerId</li><li>TotalEnqueueCount</li><li>TotalDequeueCount</li><li>TotalConsumerCount</li><li>TotalMessages</li><li>TotalMessagesCached</li><li>MemoryLimit</li><li>MemoryPercentageUsed</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p>Destination</p></td><td colspan="1" rowspan="1"><ul><li><strong>Type</strong>=Queue|Topic</li><li><strong>Destination</strong>=<destination identifier></li><li><strong>BrokerName</strong>=<name of broker></li></ul></td><td colspan="1" rowspan="1"><ul><li>EnqueueCount</li><li>DequeueCount</li><li>ConsumerCount</li><li>Messages</li><li>MessagesCached</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p>NetworkConnector</p></td><td colspan="1" rowspan="1"><ul><li><strong>Type</strong>=NetworkConnector</li><li><strong>BrokerName</strong>=<connector identifierr></li></ul></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>Connector</p></td><td colspan="1" rowspan="1"><ul><li><strong>Type</strong>=Connector</li><li><strong>ConnectorName</strong>=<connector identifier></li><li><strong>BrokerName</strong>=<name of broker></li></ul></td><td colspan="1" rowspan="1"><ul><li>EnqueueCount</li><li>DequeueCount</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p>Connection</p></td><td colspan="1" rowspan="1"><ul><li><strong>Type</strong>=Connection</li><li><strong>Connection</strong>=<connection identifier></li><li><strong>BrokerName</strong>=<name of broker></li></ul></td><td colspan="1" rowspan="1"><ul><li>EnqueueCount</li><li>DequeueCount</li><li>DispatchQueueSize</li><li>Active</li><li>Blocked</li><li>Connected</li><li>Slow</li></ul></td></tr></tbody></table><p><structured-macro ac:macro-id="60c898c5-ba0d-43b2-83a5-cb91b4f8efaa" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">bstat</parameter></structured-macro></p><h3>bstat task</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Task Name</p></th><td colspan="1" rowspan="1"><p>bstat</p></td></tr><tr><th colspan="1" rowspan="1"><p>Task Usage</p></th><td colspan="1" rowspan="1"><p><em>activemq-admin bstat</em> [broker name]</p></td></tr><tr><th colspan="1" rowspan="1"><p>Description</p></th><td colspan="1" rowspan="1"><p>Predefined query script that displays useful statistics regarding a broker and its components.</p></td></tr></tbody></table><p><strong>Examples:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin bstat</p></td><td colspan="1" rowspan="1"><p>Display useful statistics for all registered brokers in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin bstat localhost</p></td><td colspan="1" rowspan="1"><p>Display useful statistics for the registered broker 'localhost'.</p></td></tr></tbody></table><p><structured-macro ac:macro-id="712ec0d8-e5e9-4c0f-9242-2058c7d53e58" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">browse</parameter></structured-macro></p><h3>browse task</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Task Name</p></th><td colspan="1" rowspan="1"><p>browse</p></td></tr><tr><th colspan="1" rowspan="1"><p>Task Usage</p></th><td colspan="1" rowspan="1"><p><em>activemq-admin browse --amqurl <broker url> [options] <destinations></em> or <em>java -jar run.jar browse --amqurl <broker url> [options] <destinations></em></p></td></tr><tr><th colspan="1" rowspan="1"><p>Description</p></th><td colspan="1" rowspan="1"><p>Script to browse selected destinations' messages.  The browse operation may not return all messages due to limitations of broker configuration and system resources.</p></td></tr></tbody></table><p><strong>Options:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Syntax</p></th><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>Broker URL Option</p></td><td colspan="1" rowspan="1"><p>--amqurl <url></p></td><td colspan="1" rowspan="1"><p>--amqurl tcp://localhost:61616</p></td><td colspan="1" rowspan="1"><p>Specify the broker URL to connect to.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Message Selector Option</p></td><td colspan="1" rowspan="1"><p>--msgsel "<msgsel1,msgsel2,...>"</p></td><td colspan="1" rowspan="1"><p>--msgsel "JMSMessageID='*:10',JMSPriority>5"</p></td><td colspan="1" rowspan="1"><p>Allows you to filter the specific messages to view. Place the entire selector criteria in double quotes " ". You can use wildcard queries by enclosing the string message property in ' '. Other than using wildcard queries to filter string properties, other queries follows the message selector format.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Group View Option</p></td><td colspan="1" rowspan="1"><p>-V[header | custom | body]</p></td><td colspan="1" rowspan="1"><p>-Vheader, -Vcustom, -Vbody</p></td><td colspan="1" rowspan="1"><p>Let's you specify a specific group of message attributes to view. The header view shows all the standard JMS message headers. The custom view shows all the custom fields added to each JMS message. The body view shows the message body of the JMS message.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Specific View Option</p></td><td colspan="1" rowspan="1"><p>--view <attr1>,[header:|custom:]<attr2>,...</p></td><td colspan="1" rowspan="1"><p>--view JMSMessageID='*:10',custom:MyCustomField</p></td><td colspan="1" rowspan="1"><p>Let's you specifically select a specific message attribute. It allows you to select specific attributes from the JMS and custom headers. You could add the tags header: and custom: to explicitly specify where the attribute belongs to. Refer to the message header table below for details.</p></td></tr><tr><td colspan="1" rowspan="1"><p>System Define Option</p></td><td colspan="1" rowspan="1"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>Help Option</p></td><td colspan="1" rowspan="1"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1"><p>--help</p></td><td colspan="1" rowspan="1"><p>Display the help messages for the browse script.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Version Option</p></td><td colspan="1" rowspan="1"><p>--version</p></td><td colspan="1" rowspan="1"><p>activemq --version</p></td><td colspan="1" rowspan="1"><p>Display the activemq version information.</p></td></tr></tbody></table><p><strong>Examples:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin browse --amqurl tcp://localhost:61616 TEST.FOO</p></td><td colspan="1" rowspan="1"><p>Prints the JMS message header, custom message header, and message body of the messages in the queue 'TEST.FOO'</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin browse --amqurl tcp://localhost:61616 -Vheader,body TEST.FOO</p></td><td colspan="1" rowspan="1"><p>Prints the JMS message header and message body of the messages in the queue 'TEST.FOO'</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin browse --amqurl tcp://localhost:61616 -Vheader --view custom:MyCustomField TEST.FOO TEST.BAR</p></td><td colspan="1" rowspan="1"><p>Prints all the JMS message header and the custom field 'MyCustomField' of the messages in the queue 'TEST.FOO' and 'TEST.BAR'.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin browse --amqurl tcp://localhost:61616 --msgsel "JMSMessageID='*:10',JMSPriority>5" TEST.FOO</p></td><td colspan="1" rowspan="1"><p>Prints all the attributes of the messages in the queue 'TEST.FOO' that has a JMSMessageID that matches the wildcard query *:10 and has a JMSPriority greater than 5.</p></td></tr></tbody></table><p><strong>JMS Message Header Reference:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Header Name</p></th><th colspan="1" rowspan="1"><p>Header Type</p></th></tr><tr><td colspan="1" rowspan="1"><p>JMSCorrelation ID</p></td><td colspan="1" rowspan="1"><p>String</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSDelivery Mode</p></td><td colspan="1" rowspan="1"><p>int (1-Non-Persistent, 2-Persistent)</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSDestination</p></td><td colspan="1" rowspan="1"><p>javax.jms.Destination</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSExpiration</p></td><td colspan="1" rowspan="1"><p>long</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSMessageID</p></td><td colspan="1" rowspan="1"><p>String</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSPriority</p></td><td colspan="1" rowspan="1"><p>int</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSRedelivered</p></td><td colspan="1" rowspan="1"><p>boolean</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSReplyTo</p></td><td colspan="1" rowspan="1"><p>javax.jms.Destination</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSTimestamp</p></td><td colspan="1" rowspan="1"><p>long</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMSType</p></td><td colspan="1" rowspan="1"><p>String</p></td></tr></tbody></table><p><structured-macro ac:macro-id="71ca7af0-8ada-4ab6-865a-a7084464aa65" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">purge</parameter></structured-macro></p><h3>purge task</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Task Name</p></th><td colspan="1" rowspan="1"><p>purge</p></td></tr><tr><th colspan="1" rowspan="1"><p>Task Usage</p></th><td colspan="1" rowspan="1"><p><em>activemq-admin purge</em> [purge-options] <destinations></p></td></tr><tr><th colspan="1" rowspan="1"><p>Description</p></th><td colspan="1" rowspan="1"><p>Delete selected destination's messages that matches the message selector.</p></td></tr></tbody></table><p><strong>Options:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Syntax</p></th><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>JMX URL Option</p></td><td colspan="1" rowspan="1"><p>--jmxurl <url></p></td><td colspan="1" rowspan="1"><p>--jmxurl service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td><td colspan="1" rowspan="1"><p>Change the JMX service url to connect to. By default it connects to: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi</p></td></tr><tr><td colspan="1" rowspan="1"><p>JMX Authentication Option</p></td><td colspan="1" rowspan="1"><p>--jmxuser user --jmxpassword password</p></td><td colspan="1" rowspan="1"><p>--jmxuser smx --jmxpassword smx</p></td><td colspan="1" rowspan="1"><p>For cases where username/password based authentication of the JMX client is required. Not set by default.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Message Selector Option</p></td><td colspan="1" rowspan="1"><p>--msgsel "<msgsel1,msgsel2,...>"</p></td><td colspan="1" rowspan="1"><p>--msgsel "JMSMessageID='*:10',JMSPriority>5"</p></td><td colspan="1" rowspan="1"><p>Allows you to filter the specific messages to view. Place the entire selector criteria in double quotes " ". You can use wildcard queries by enclosing the string message property in ' '. Other than using wildcard queries to filter string properties, other queries follows the message selector format.</p></td></tr><tr><td colspan="1" rowspan="1"><p>System Define Option</p></td><td colspan="1" rowspan="1"><p>-D<key>=<value></p></td><td colspan="1" rowspan="1"><p>-Dactivemq.home=c:/ActiveMQ</p></td><td colspan="1" rowspan="1"><p>Sets a systems property. i.e Systems.getProperty("activemq.home"); will return c:/ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>Help Option</p></td><td colspan="1" rowspan="1"><p>-h or -? or --help</p></td><td colspan="1" rowspan="1"><p>--help</p></td><td colspan="1" rowspan="1"><p>Display the help messages for the browse script.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Version Option</p></td><td colspan="1" rowspan="1"><p>--version</p></td><td colspan="1" rowspan="1"><p>activemq --version</p></td><td colspan="1" rowspan="1"><p>Display the activemq version information.</p></td></tr></tbody></table><p><strong>Examples:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin purge FOO.BAR</p></td><td colspan="1" rowspan="1"><p>Delete all the messages in queue FOO.BAR</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin purge --msgsel "JMSMessageID='*:10',JMSPriority>5" FOO.*</p></td><td colspan="1" rowspan="1"><p>Delete all the messages in the destinations that matches FOO.* and has a JMSMessageID in", the header field that matches the wildcard *:10, and has a JMSPriority field > 5 in the", queue FOO.BAR <br clear="none"> To use wildcard queries, the field must be a string and the query enclosed in ''</p></td></tr></tbody></table><h3>dstat task</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Task Name</p></th><td colspan="1" rowspan="1"><p>dstat</p></td></tr><tr><th colspan="1" rowspan="1"><p>Task Usage</p></th><td colspan="1" rowspan="1"><p><em>activemq-admin dstat</em> [destination type]</p></td></tr><tr><th colspan="1" rowspan="1"><p>Description</p></th><td colspan="1" rowspan="1"><p>Predefined query script that displays useful statistics regarding destinations on a broker.</p></td></tr></tbody></table><p><strong>Examples:</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin dstat</p></td><td colspan="1" rowspan="1"><p>Display useful statistics for all destinations on the broker in the default JMX context.</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-admin dstat topics</p></td><td colspan="1" rowspan="1"><p>Display useful statistics for the Topics that currently exist on the Broker.</p></td></tr></tbody></table></div>
diff --git a/activemq-connection-uris.xml b/activemq-connection-uris.xml
index 1a061b7..61b285f 100644
--- a/activemq-connection-uris.xml
+++ b/activemq-connection-uris.xml
@@ -1,30 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQConnectionURIs-Transportconfigurationoptions">Transport configuration options</h2><p>One of the first kinds of URI you are likely to use is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All of the following URI configurations are based on the java.net.URI class which does not allow whitespace to be used. So if you are using <strong><code>failover:</code></strong> or <strong><code>static:</code></strong> URIs, do not put any whitespace around the <strong><code>','</code> </strong>symbol.</p></div></div><h3 id="ActiveMQConnectionURIs-TheAUTOTransport">The AUTO Transport</h3><p>Starting with 5.13.0 ActiveMQ has support for automatic wire protocol detection over TCP, SSL, NIO, and NIO SSL.  OpenWire, STOMP, AMQP, and MQTT are supported.  For details see the <a shape="rect" href="auto.xml">AUTO </a>Transport Reference.</p><h3 id="ActiveMQConnectionURIs-TheVMTransport">The VM Transport</h3><p>The VM transport allows clients to connect to each other inside the VM without the overhead of the network communication. The connection used is not that of a socket connection but instead uses direct method invocations to enable a high performance embedded messaging system.</p><p>The first client to use the VM connection will boot an embedded broker. Subsequent connections will attach that the same broker. Once all VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For more information see the <a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheAMQPTransport">The AMQP Transport</h3><p>As of 5.8.0 ActiveMQ has support for AMQP. For details see the <a shape="rect" href="amqp.xml">AMQP</a> Transport Reference.</p><h3 id="ActiveMQConnectionURIs-TheMQTTTransport">The MQTT Transport</h3><p>Starting with 5.6.0 ActiveMQ also supports <a shape="rect" class="external-link" href="http://mqtt.org/" rel="nofollow">MQTT</a>. Its a light weight publish/subscribe messaging transport. See the <a shape="rect" href="mqtt.xml">MQTT</a> Transport Reference for details.</p><h3 id="ActiveMQConnectionURIs-TheTCPTransport">The TCP Transport</h3><p>The TCP transport allows clients to connect a remote ActiveMQ using a a TCP socket.</p><p>For more information see the <a shape="rect" href="tcp-transport-reference.xml">TCP Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheNIOTransport">The NIO Transport</h3><p>Same as the TCP transport, except that the <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/New_I/O" rel="nofollow">New I/O (NIO)</a> package is used, which may provide better performance. The Java NIO package should not be confused with IBM's <a shape="rect" class="external-link" href="http://java.sys-con.com/read/46658.htm" rel="nofollow">AIO4J </a> package.</p><p>To switch from TCP to NIO, simply change the scheme portion of the URI. Here's an example as defined within a broker's XML configuration file.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
- ...
- <transportConnectors>
- <transportConnector name="nio" uri="nio://0.0.0.0:61616"/>
- </<transportConnectors>
- ...
-</broker>
-]]></script>
-</div></div><p>Trying to use nio transport url on the client side will instantiate the regular TCP transport. For more information see the <a shape="rect" href="nio-transport-reference.xml">NIO Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheSSLTransport">The SSL Transport</h3><p>This allows you to talk over TCP using SSL. For more information see the <a shape="rect" href="ssl-transport-reference.xml">SSL Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheNIOSSLTransport">The NIO SSL Transport</h3><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Availability</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Available since 5.6</p></div></div><p>Implementing SSL transport over NIO. This allows you to connect large number of SSL clients to a single broker instance. It's server side transport-option only</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
- ...
- <transportConnectors>
- <transportConnector name="nio+ssl" uri="nio+ssl://0.0.0.0:61616"/>
- </<transportConnectors>
- ...
-</broker>
-]]></script>
-</div></div><p>Trying to use <code>nio+ssl</code> transport url on the client side will instantiate the regular SSL transport.</p><h3 id="ActiveMQConnectionURIs-ThePeerTransport">The Peer Transport</h3><p>The Peer transport provides a peer-to-peer network with ActiveMQ. What actually happens is the peer transport uses the VM transport to create and connect to a local embedded broker but which configures the embedded broker to establish network connections to other peer embedded brokers.</p><p>For more information see the <a shape="rect" href="peer-transport-reference.xml">Peer Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheUDPTransport">The UDP Transport</h3><p>This allows you to talk over UDP.</p><p>For more information see the <a shape="rect" href="udp-transport-reference.xml">UDP Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheMulticastTransport">The Multicast Transport</h3><p>This allows you to talk over Multicast.</p><p>For more information see the <a shape="rect" href="multicast-transport-reference.xml">Multicast Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheHTTPandHTTPSTransport">The HTTP and HTTPS Transport</h3><p>This allows the ActiveMQ client and broker to tunnel over HTTP. If the client is not JMS you might want to look at <a shape="rect" href="rest.xml">REST</a> or <a shape="rect" href="ajax.xml">Ajax</a> support instead.</p><p>For more information see the <a shape="rect" href="http-and-https-transports-reference.xml">HTTP and HTTPs Transports Reference</a></p><h3 id="ActiveMQConnectionURIs-TheWebSocketsTransport">The WebSockets Transport</h3><p>This transport uses the new HTML5 WebSockets to exchange messages with the broker. For more information see the <a shape="rect" href="websockets.xml">WebSockets</a> Transport Reference</p><h3 id="ActiveMQConnectionURIs-TheStompTransport">The Stomp Transport</h3><p>A plain text transport that can be used with many languages. See <a shape="rect" href="stomp.xml">Stomp</a> for more details.</p><h2 id="ActiveMQConnectionURIs-GeneralPurposeURIs">General Purpose URIs</h2><p>You can configure other features via the URI syntax as follows...</p><h3 id="ActiveMQConnectionURIs-ConnectionConfigurationURI">Connection Configuration URI</h3><p>Any Apache ActiveMQ JMS connection can be configured using the URL or explicitly setting properties on the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a> or <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> objects themselves.</p><p>For more information see <a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a></p><h3 id="ActiveMQConnectionURIs-DestinationOptions">Destination Options</h3><p>You can configure various consumer related options using <a shape="rect" href="destination-options.xml">Destination Options</a> which allow you to configure destinations using URI syntax.</p><h3 id="ActiveMQConnectionURIs-BrokerConfigurationURI">Broker Configuration URI</h3><p>You can use a <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a> to configure an embedded broker, either using the BrokerFactory helper class from Java or using the activemq shell script. For more details see <a shape="rect" href="run-broker.xml">How to Run a Broker</a></p><h3 id="ActiveMQConnectionURIs-ConfiguringWireFormats">Configuring Wire Formats</h3><p>Any transport which involves marshalling messages onto some kind of network transport like TCP or UDP will typically use the <a shape="rect" href="openwire.xml">OpenWire</a> format. This is configurable to customize how things appear on the wire.</p><p>For more information see <a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a></p><h2 id="ActiveMQConnectionURIs-HighLevelProtocolURIs">High Level Protocol URIs</h2><p>The following higher level protocols can be configured via URI</p><h3 id="ActiveMQConnectionURIs-TheFailoverTransport">The Failover Transport</h3><p>The Failover transport layers reconnect logic on top of any of the other transports. This is what used to be the Reliable transport in ActiveMQ 3. Its configuration syntax allows you to specify any number of composite URIs. The Failover transport randomly chooses one of the composite URIs 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><p>For more information see the <a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheFanoutTransport">The Fanout Transport</h3><p>The Fanout transport layers reconnect and replicate logic on top of any of the other transports. It is used replicate commands to multiple brokers.</p><p>For more information see the <a shape="rect" href="fanout-transport-reference.xml">Fanout Transport Reference</a></p><h2 id="ActiveMQConnectionURIs-UsingDiscovery">Using Discovery</h2><p>Often when using transports like TCP you want to use <a shape="rect" href="discovery.xml">Discovery</a> to locate the available brokers. This is different from using, say, <a shape="rect" href="multicast-transport-reference.xml">Multicast</a> - as the actual main communication is over TCP but multicast is purely used to discover the location of brokers.</p><h3 id="ActiveMQConnectionURIs-TheDiscoveryTransport">The Discovery Transport</h3><p>The Discovery transport works just like the reliable transport, except that it uses a discovery agent to locate the list of URIs to connect to.</p><p>For more information see the <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-TheZeroConfTransport">The ZeroConf Transport</h3><p>The ZeroConf transport provides <a shape="rect" href="discovery.xml">Discovery</a> and it works like the <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport</a> but rather than using our own multicast based discovery mechanism (which allows you to configure the exact multicast address and port, etc.), the <a shape="rect" href="zeroconf.xml">ZeroConf</a> transport is used instead.</p><p>For more information see the <a shape="rect" href="zeroconf-transport-reference.xml">ZeroConf Transport Reference</a></p><h3 id="ActiveMQConnectionURIs-Serversideoptions">Server side options</h3><p>There are a number of options that can be used for changing behavior on the server for the <strong><code>TransportConnector</code></strong> in the ActiveMQ broker configuration. These are:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: red;"> <code>allowLinkStealing</code><br clear="none"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>This is enabled for default for MQTT transport.</p><p>Link Stealing is where the last of two or more connections with the same id (clientID for JMS) is deemed the valid connection and the older one is closed by the broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>discoveryURI</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If set, the multicast discovery address for client connections to find the broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>enableStatusMonitor</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will monitor connections to determine if they are blocked.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>name</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <strong><code>TransportConnector</code></strong> instance.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>rebalanceClusterClients</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will automatically re-balance clients across the cluster on changes of topology.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterClients</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If enabled, will update client connections (if they use the <strong><code>failover://</code></strong> transport) of changes to the broker cluster.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterClientsOnRemove</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will update clients if a broker is removed from the cluster.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterFilter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Comma separated list of regular expressions. Brokers with a name matching the pattern will be included for client updates.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>uri</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The bind address for the transport.</p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><strong>Note</strong>: properties in <span style="color: rgb(255,0,0);">red</span> are version 5.10 (and higher) options only.</p></div></div><p>Example configuration:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
- <!-- ... -->
-
- <transportConnectors>
- <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" enableStatusMonitor="true"/>
- </<transportConnectors>
-
- <!-- ... -->
-</broker>]]></script>
-</div></div></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="b3835dd1-a798-4505-9c25-7e63e623025d" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Configuring Transports"></page></link></parameter></structured-macro></p></div>
diff --git a/activemq-inactivitymonitor.xml b/activemq-inactivitymonitor.xml
index cd8dd7b..aac3672 100644
--- a/activemq-inactivitymonitor.xml
+++ b/activemq-inactivitymonitor.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="ActiveMQInactivityMonitor-ActiveMQInactivityMonitor">ActiveMQ InactivityMonitor</h1><p>The ActiveMQ InactivityMonitor is an active thread that checks the connection is still active and if it suspects the connection is not functioning correctly, it closes the connection.</p><p>Connections are monitored by:</p><ul><li>Ensuring data is read from the connection during the specified time period (Max Inactivity Duration).</li><li>Writing a <strong><code>KeepAliveInfo</code></strong> message to the connection if no <strong>normal</strong> activemq traffic is sent across the connection during the specified time period.</li></ul><p>Each connection has two InactivityMonitors associated, one on each end of the connection. The InactivityMonitor expects to receive data on the connection during a specified time period. If <strong>normal</strong> ActiveMQ traffic has not been sent across the connection during that period, it expects to receive a <strong><code>KeepAliveInfo</code></strong> message sent by the InactivityMonitor on the other end of the connection.</p><p>Using the default values; if no data has been written or read from the connection for 30 seconds, the InactivityMonitor kicks in. The InactivityMonitor throws an <strong><code>InactivityIOException</code></strong> and shuts down the transport associated with the connection. This results in the following <strong><code>DEBUG</code></strong> logging:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>2012-06-26 17:13:55,712 | DEBUG | 30000 ms elapsed since last read check. | org.apache.activemq.transport.AbstractInactivityMonitor | InactivityMonitor ReadCheck
+<div class="wiki-content maincontent"><h1>ActiveMQ InactivityMonitor</h1><p>The ActiveMQ InactivityMonitor is an active thread that checks the connection is still active and if it suspects the connection is not functioning correctly, it closes the connection.</p><p>Connections are monitored by:</p><ul><li>Ensuring data is read from the connection during the specified time period (Max Inactivity Duration).</li><li>Writing a <strong><code>KeepAliveInfo</code></strong> message to the connection if no <strong>normal</strong> activemq traffic is sent across the connection during the specified time period.</li></ul><p>Each connection has two InactivityMonitors associated, one on each end of the connection. The InactivityMonitor expects to receive data on the connection during a specified time period. If <strong>normal</strong> ActiveMQ traffic has not been sent across the connection during that period, it expects to receive a <strong><code>KeepAliveInfo</code></strong> message sent by the InactivityMonitor on the other end of the connection.</p><p>Using the default values; if no data has been written or read from the connection for 30 seconds, the InactivityMonitor kicks in. The InactivityMonitor throws an <strong><code>InactivityIOException</code></strong> and shuts down the transport associated with the connection. This results in the following <strong><code>DEBUG</code></strong> logging:</p><structured-macro ac:macro-id="db114f31-fb57-4d2d-8f2d-390f5a254728" ac:name="noformat" ac:schema-version="1"><plain-text-body>2012-06-26 17:13:55,712 | DEBUG | 30000 ms elapsed since last read check. | org.apache.activemq.transport.AbstractInactivityMonitor | InactivityMonitor ReadCheck
2012-06-26 17:13:55,712 | DEBUG | No message received since last read check for tcp:///127.0.0.1:52659! Throwing InactivityIOException. | org.apache.activemq.transport.AbstractInactivityMonitor | InactivityMonitor ReadCheck
2012-06-26 17:13:55,714 | DEBUG | Transport Connection to: tcp://127.0.0.1:52659 failed:
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:52659 |
@@ -10,11 +9,8 @@
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
-</pre>
-</div></div><h3 id="ActiveMQInactivityMonitor-AdvancedInactivityMonitorConfiguration">Advanced InactivityMonitor Configuration</h3><p>There are some configuration options to further fine tune the <code>InactivityMonitor</code>. Note, for most use cases the default values are just fine.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Parameter</th><th colspan="1" rowspan="1" class="confluenceTh">Default Value</th><th colspan="1" rowspan="1" class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>wireFormat.maxInactivityDuration</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Timeout, in milliseconds, after which the connection is closed by the broker if no data has been received.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>wireFormat.maxInactivityDurationInitalDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the maximum delay, in milliseconds, before connection inactivity monitoring is started.</p><p>This can prove useful if a broker is under load with many connections being created concurrently.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transport.useInactivityMonitor</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A value of <strong><code>false</code></strong> disables the <code>InactivityMonitor</code> completely and connections will never time out.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>transport.useKeepAlive</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Determines if a <strong><code>KeepAliveInfo</code></strong> message should be sent on an idle connection to prevent it from timing out.</p><p>Disabling the keep alive will still make connections time out when no data was received on the connection for the specified amount of time.</p></td></tr></tbody></table></div><p> </p><p>These parameters can be specified directly on the client side connection URL, e.g. <strong><code>tcp://localhost:61616?wireFormat.maxInactivityDuration=30000</code>, </strong>or on the broker's transport connector URL:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnectors>
- <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=30000&amp;wireFormat.maxInactivityDurationInitalDelay=10000"/>
+</plain-text-body></structured-macro><h3>Advanced InactivityMonitor Configuration</h3><p>There are some configuration options to further fine tune the <code>InactivityMonitor</code>. Note, for most use cases the default values are just fine.</p><table><tbody><tr><th colspan="1" rowspan="1">Parameter</th><th colspan="1" rowspan="1">Default Value</th><th colspan="1" rowspan="1">Description</th></tr><tr><td colspan="1" rowspan="1"><p><code>wireFormat.maxInactivityDuration</code></p></td><td colspan="1" rowspan="1"><p><code>30000</code></p></td><td colspan="1" rowspan="1"><p>Timeout, in milliseconds, after which the connection is closed by the broker if no data has been received.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>wireFormat.maxInactivityDurationInitalDelay</code></p></td><td colspan="1" rowspan="1"><p><code>10000</code></p></td><td colspan="1" rowspan="1"><p>Specifies the maximum delay, in milliseconds, before connection inactivity monitoring is started.</p><p>This can prove useful if a broker is under load with many connections being created concurrently.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>transport.useInactivityMonitor</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>A value of <strong><code>false</code></strong> disables the <code>InactivityMonitor</code> completely and connections will never time out.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>transport.useKeepAlive</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Determines if a <strong><code>KeepAliveInfo</code></strong> message should be sent on an idle connection to prevent it from timing out.</p><p>Disabling the keep alive will still make connections time out when no data was received on the connection for the specified amount of time.</p></td></tr></tbody></table><p> </p><p>These parameters can be specified directly on the client side connection URL, e.g. <strong><code>tcp://localhost:61616?wireFormat.maxInactivityDuration=30000</code>, </strong>or on the broker's transport connector URL:</p><structured-macro ac:macro-id="71606cd5-86b4-43fd-b0e4-3a4b7af305b4" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><transportConnectors>
+ <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=30000&amp;wireFormat.maxInactivityDurationInitalDelay=10000"/>
</transportConnectors>
-]]></script>
-</div></div><h3 id="ActiveMQInactivityMonitor-WhathappensifthemaxInactivityDurationandmaxInactivityDurationInitalDelayaresettodifferentvaluesoneithersideofthesameconnection?">What happens if the <code>maxInactivityDuration</code> and <code>maxInactivityDurationInitalDelay</code> are set to different values on either side of the same connection?</h3><p>At startup the InactivityMonitor negotiates the appropriate <strong><code>maxInactivityDuration</code></strong> and <strong><code>maxInactivityDurationInitalDelay</code></strong>. The shortest duration is taken for the connection.</p><h3 id="ActiveMQInactivityMonitor-CantheInactivityMonitoronaconnectionbedisabled?">Can the InactivityMonitor on a connection be disabled?</h3><p>Setting <strong><code>transport.useInactivityMonitor=false</code></strong> will disable the InactivityMonitor<strong>. </strong>Configuring <strong><code>wireFormat.maxInactivityDuration=0</code></strong> will achieve the same result.</p><h3 id="ActiveMQInactivityMonitor-PotentialIssues">Potential Issues</h3><p><a shape="rect" href="slow-networks-drop-large-messages.xml">slow-networks-drop-large-messages</a></p><p> </p></div>
+</plain-text-body></structured-macro><h3>What happens if the <code>maxInactivityDuration</code> and <code>maxInactivityDurationInitalDelay</code> are set to different values on either side of the same connection?</h3><p>At startup the InactivityMonitor negotiates the appropriate <strong><code>maxInactivityDuration</code></strong> and <strong><code>maxInactivityDurationInitalDelay</code></strong>. The shortest duration is taken for the connection.</p><h3>Can the InactivityMonitor on a connection be disabled?</h3><p>Setting <strong><code>transport.useInactivityMonitor=false</code></strong> will disable the InactivityMonitor<strong>. </strong>Configuring <strong><code>wireFormat.maxInactivityDuration=0</code></strong> will achieve the same result.</p><h3>Potential Issues</h3><p><link><page ri:content-title="Slow networks drop large messages"></page><plain-text-link-body>slow-networks-drop-large-messages</plain-text-link-body></link></p><p> </p></div>
diff --git a/activemq-message-properties.xml b/activemq-message-properties.xml
index bbd7c3c..a672753 100644
--- a/activemq-message-properties.xml
+++ b/activemq-message-properties.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>ActiveMQ Messages support the following default message properties:</strong></p><h2 id="ActiveMQMessageProperties-MessageAttributesAccessedasProperties:">Message Attributes Accessed as Properties:</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</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><code>JMSDestination</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>javax.jms.Destination</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><em>Set by the producer</em></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Destination used by the producer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSReplyTo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>javax.jms.Destination</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>User defined.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSType</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><code>""</code></td><td colspan="1" rowspan="1" class="confluenceTd"><p>User defined.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSDeliveryMode</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>DeliveryMode.PERSISTENT</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Indicator if messages should be persisted.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSPriority</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>4</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Value from <code>0-9</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSMessageID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>unique</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Unique identifier for the message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSTimestamp</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>long</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><em>Time the message was sent</em></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time in milliseconds.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSCorrelationID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>User defined.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSExpiration</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>long</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time in milliseconds to expire the message. A value of <code>0</code> means never expire.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSRedelivered</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code> if the message is being resent to the consumer, persisted via <u><a shape="rect" href="per-destination-policies.xml">persistJMSRedelivered</a></u></p></td></tr></tbody></table></div><h2 id="ActiveMQMessageProperties-JMSDefined:">JMS Defined:</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</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><code>JMSXDeliveryCount</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of attempts to send the message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Identity of the message group.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupSeq</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sequence number of the message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXProducerTXID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Transaction identifier.</p></td></tr></tbody></table></div><h2 id="ActiveMQMessageProperties-ActiveMQDefined:">ActiveMQ Defined:</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</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><code>JMSActiveMQBrokerInTime</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>long</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time stamp (in milliseconds) for when the message arrived at the broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSActiveMQBrokerOutTime</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>long</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time stamp (in milliseconds) for when the message left the broker.</p></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><p><strong>ActiveMQ Messages support the following default message properties:</strong></p><h2>Message Attributes Accessed as Properties:</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Type</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>JMSDestination</code></p></td><td colspan="1" rowspan="1"><p><code>javax.jms.Destination</code></p></td><td colspan="1" rowspan="1"><p><em>Set by the producer</em></p></td><td colspan="1" rowspan="1"><p>Destination used by the producer.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSReplyTo</code></p></td><td colspan="1" rowspan="1"><p><code>javax.jms.Destination</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>User defined.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSType</code></p></td><td colspan="1" rowspan="1"><p><code>String</code></p></td><td colspan="1" rowspan="1"><code>""</code></td><td colspan="1" rowspan="1"><p>User defined.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSDeliveryMode</code></p></td><td colspan="1" rowspan="1"><p><code>int</code></p></td><td colspan="1" rowspan="1"><p><code>DeliveryMode.PERSISTENT</code></p></td><td colspan="1" rowspan="1"><p>Indicator if messages should be persisted.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSPriority</code></p></td><td colspan="1" rowspan="1"><p><code>int</code></p></td><td colspan="1" rowspan="1"><p><code>4</code></p></td><td colspan="1" rowspan="1"><p>Value from <code>0-9</code>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSMessageID</code></p></td><td colspan="1" rowspan="1"><p><code>String</code></p></td><td colspan="1" rowspan="1"><p><code>unique</code></p></td><td colspan="1" rowspan="1"><p>Unique identifier for the message.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSTimestamp</code></p></td><td colspan="1" rowspan="1"><p><code>long</code></p></td><td colspan="1" rowspan="1"><p><em>Time the message was sent</em></p></td><td colspan="1" rowspan="1"><p>Time in milliseconds.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSCorrelationID</code></p></td><td colspan="1" rowspan="1"><p><code>String</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>User defined.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSExpiration</code></p></td><td colspan="1" rowspan="1"><p><code>long</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Time in milliseconds to expire the message. A value of <code>0</code> means never expire.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSRedelivered</code></p></td><td colspan="1" rowspan="1"><p><code>boolean</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>true</code> if the message is being resent to the consumer, persisted via <u><link><page ri:content-title="Per Destination Policies"></page><plain-text-link-body>persistJMSRedelivered</plain-text-link-body></link></u></p></td></tr></tbody></table><h2>JMS Defined:</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Type</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>JMSXDeliveryCount</code></p></td><td colspan="1" rowspan="1"><p><code>int</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Number of attempts to send the message.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSXGroupID</code></p></td><td colspan="1" rowspan="1"><p><code>String</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>Identity of the message group.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSXGroupSeq</code></p></td><td colspan="1" rowspan="1"><p><code>int</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Sequence number of the message.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSXProducerTXID</code></p></td><td colspan="1" rowspan="1"><p><code>String</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>Transaction identifier.</p></td></tr></tbody></table><h2>ActiveMQ Defined:</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Type</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>JMSActiveMQBrokerInTime</code></p></td><td colspan="1" rowspan="1"><p><code>long</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Time stamp (in milliseconds) for when the message arrived at the broker.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSActiveMQBrokerOutTime</code></p></td><td colspan="1" rowspan="1"><p><code>long</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Time stamp (in milliseconds) for when the message left the broker.</p></td></tr></tbody></table></div>
diff --git a/activemq-performance-module-users-manual.xml b/activemq-performance-module-users-manual.xml
index ec6f47f..05bb3a7 100644
--- a/activemq-performance-module-users-manual.xml
+++ b/activemq-performance-module-users-manual.xml
@@ -1,23 +1,13 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQPerformanceModuleUsersManual-RunningMaven2PerformanceTest">Running Maven 2 Performance Test</h2><p>This <a shape="rect" class="external-link" href="http://maven.apache.org">Maven 2</a> plugin allows you to run performance tests easily using the Maven command line or run tests automatically in <a shape="rect" class="external-link" href="http://maven.apache.org/continuum/">Continuum</a></p><h3 id="ActiveMQPerformanceModuleUsersManual-Prerequisites">Prerequisites</h3><p>Starting with ActiveMQ 5.5 and above the plugin can be obtained from maven or if you download the src from SVN you can build it yourself. Start with a complete build of Apache ActiveMQ and then do</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd activemq-tooling
+<div class="wiki-content maincontent"><h2>Running Maven 2 Performance Test</h2><p>This <a shape="rect" href="http://maven.apache.org">Maven 2</a> plugin allows you to run performance tests easily using the Maven command line or run tests automatically in <a shape="rect" href="http://maven.apache.org/continuum/">Continuum</a></p><h3>Prerequisites</h3><p>Starting with ActiveMQ 5.5 and above the plugin can be obtained from maven or if you download the src from SVN you can build it yourself. Start with a complete build of Apache ActiveMQ and then do</p><structured-macro ac:macro-id="c6fb7f0e-3ec4-4bc2-99f8-73981b4a2632" ac:name="code" ac:schema-version="1"><plain-text-body>cd activemq-tooling
mvn clean install
-]]></script>
-</div></div><p>To run the following Maven goals make sure you are inside a Maven2 project directory where its POM is enabled with the Maven2 plugin.</p><h3 id="ActiveMQPerformanceModuleUsersManual-Gettingstarted">Getting started</h3><p>To get started, switch to the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/sandbox/activemq-perftest/">activemq-perftest directory from the sandbox repo,</a> or to a directory containing your own Maven POM with the following plugin defined:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<plugin>
+</plain-text-body></structured-macro><p>To run the following Maven goals make sure you are inside a Maven2 project directory where its POM is enabled with the Maven2 plugin.</p><h3>Getting started</h3><p>To get started, switch to the <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/sandbox/activemq-perftest/">activemq-perftest directory from the sandbox repo,</a> or to a directory containing your own Maven POM with the following plugin defined:</p><structured-macro ac:macro-id="2c15fc65-ce23-493b-be3c-8ea36a92b396" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><plugin>
<groupId>org.apache.activemq.tooling</groupId>
<artifactId>activemq-perf-maven-plugin</artifactId>
<version>${activemq-version}</version>
-</plugin>]]></script>
-</div></div><p>In ActiveMQ versions prior to 5.8, the artifactId was <code>maven-activemq-perf-plugin</code>.</p><p>Type the following commands into separate shells (the broker line here is optional if you have a preconfigured one running):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn activemq-perf:broker -Durl=broker:tcp://localhost:61616
+</plugin></plain-text-body></structured-macro><p>In ActiveMQ versions prior to 5.8, the artifactId was <code>maven-activemq-perf-plugin</code>.</p><p>Type the following commands into separate shells (the broker line here is optional if you have a preconfigured one running):</p><structured-macro ac:macro-id="8fc512ad-245c-443a-a654-bdaac2c57077" ac:name="code" ac:schema-version="1"><plain-text-body>mvn activemq-perf:broker -Durl=broker:tcp://localhost:61616
mvn activemq-perf:consumer
mvn activemq-perf:producer
-]]></script>
-</div></div><p>If you run the broker on a different machine then change the producer and consumer commands to</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn activemq-perf:consumer -Dfactory.brokerURL=tcp://host:port
+</plain-text-body></structured-macro><p>If you run the broker on a different machine then change the producer and consumer commands to</p><structured-macro ac:macro-id="1ba10e61-a093-4898-a871-9d2804bc9b79" ac:name="code" ac:schema-version="1"><plain-text-body>mvn activemq-perf:consumer -Dfactory.brokerURL=tcp://host:port
mvn activemq-perf:producer -Dfactory.brokerURL=tcp://host:port
-]]></script>
-</div></div><p>where you switch host:port with the actual values.</p><p>When you run the producer & consumer, it generates an XML performance report in the current directory, so that you can graph and chart the results etc. See the <a shape="rect" href="sample-report.xml">sample report</a></p><h3 id="ActiveMQPerformanceModuleUsersManual-Mavengoals">Maven goals</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Goal</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-perf:broker</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Starts broker using the activemq configuration file located in "src\main\resources\broker-conf" where the default config is activemq.xml. <br clear="none" class="atl-forced-newline"> Parameters: <br clear="none" class="atl-forced-newline">  1. -DconfigType - specifies the type of configuration to use. Its value must be one of the filename in the "..\broker-config" directory (e.g. -DconfigType=kaha). <br clear="none" class="atl-forced-newline">  2. -DconfigFile - path to config file other than those in "src\..\broker-config".e.g -DconfigFile=c:\dir\activemq.xml)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-perf:consumer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Starts the consumer's performance testing. The generated report file can be found in the directory specified in the parameter "sysTest.reportDir".</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-perf:producer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Starts the producer's performance testing. The generated report file can be found in the directory specified in the parameter "sysTest.reportDir".</p></td></tr></tbody></table></div><p><sup>1</sup> <strong>Note</strong>:The parameters for both consumer and producers are described in the next section. (<a shape="rect" href="sample-report.xml">sample report</a>)</p><h3 id="ActiveMQPerformanceModuleUsersManual-ConfigurationforrunningasystemofJMSClients(Producer/Consumer)">Configuration for running a system of JMS Clients (Producer/Consumer)</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Configuration Key</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>sysTest.propsConfigFile</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use properties specified externally in a key=value properties file</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.clientPrefix</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>JmsConsumer or JmsProducer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the client name prefix that will be use for each system. By default it will use JmsConsumer for consumer systems, and JmsProducer for producer systems.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.numClients</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the number of JMS Clients to start.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.totalDests</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the total number of destinations to use for the whole system test.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.destDistro</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>all</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies how to distribute the destinations to the clients. Available values are (Invalid value will result to using the default value 'all')<sup>1</sup>:</p><ul><li>'all' - All clients will send/receive to all destinations. i.e. if there are 2 producers and 5 destinations, each producer will send a message to each individual destination.</li><li>'equal' - Clients will equally divide the destinations among themselves. i.e. if there are 2 producers and 5 destinations, each producer will send messages to 2 destinations. The fifth destination will not be used.</li><li>'divide' - Clients will divide the destinations among themselves regardless of equality. i.e. if there are 2 producers and 5 destinations, producer 1 will send to 3 destinations, while producer 2 will send to 2 destinations.</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.reportDir</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>./</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The directory where the sampler report will be saved.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.reportName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The default filename the sampler report will be saved us. There is usually no need to set this setting as the default value will create either JmsProducer_numClients#<em>numDests#</em><Dest Distro>.xml and JmsConsumer_numClients#_numDests#_<Dest Distro>.xml, where # represents the number of clients and destinations set for that system, and <Dest Distro> specifies the destination distribution for the system.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.reportType</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>xml</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the manner of generating the performance report. Available values are:</p><ul><li>'xml' - Write the performance report into an xml file. Specified by reportDirectory and reportName. A verbose summary will also be displayed at the end of the test.</li><li>'verbose' - All information will be written to the standard output, which includes settings, sampler data, and performance summary.</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.samplers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>tp,cpu</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the samplers that will be started. To use enable more than one sampler, separate the values by commas without spaces. Available values are:</p><ul><li>'tp' - Throughput sampler</li><li>'cpu' - CPU Usage sampler</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sysTest.spiClass</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>org.apache.activemq.tool.spi.ActiveMQClassLoaderSPI</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The service provider interface class that allows the client to create a generic connection factory. Current available SPI classes include:</p><ol><li>'org.apache.activemq.tool.ActiveMQPojoSPI'</li><li>'org.apache.activemq.tool.ActiveMQClassLoaderSPI'</li></ol></td></tr></tbody></table></div><p><sup>1</sup> <strong>Note</strong>: If the number of destinations is less than the number of clients and the distribution type is either 'equal' or 'divide', each client will send/receive from only one destination, distributing the destinations among the clients. i.e. if there are 5 producers and 2 destinations, 3 producers will send to destination 1, and 2 producers will send to destination 2. Also, a consumer can only receive from a single destination, unless composite destination is supported and specified.</p><h3 id="ActiveMQPerformanceModuleUsersManual-ConfigurationforrunningaJMSProducer">Configuration for running a JMS Producer</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Configuration Key</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>producer.sessTransacted</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies if the session created will be transacted or not. See the JMS Specifications for more details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.sessAckMode</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>autoAck</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specified the acknowledge mode of the session. See the JMS Specifications for more details. Available values are:</p><ol><li>'autoAck' - Session.AUTO_ACKNOWLEDGE</li><li>'clientAck' - Session.CLIENT_ACKNOWLEDGE</li><li>'dupsAck' - Session.DUPS_OK_ACKNOWLEDGE</li><li>'transacted' - Session.TRANSACTED</li></ol></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.commitAfterXMsgs</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Commit transaction after the specified amount of messages. Only used in conjunction with a transacted JMS Session (producer.sessTransacted=true and producer.sessAckMode=transacted)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.destName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>TEST.FOO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The prefix of the destination name to use. To specify a queue, prefix the destination name with 'queue://', for topics, prefix the destination with 'topic://'. If no prefix is specified, a topic will be created.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.destComposite</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If there are more than one destination, and destComposite=true, the destinations will be merged into one. This assumes that the provider supports composite destinations.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.deliveryMode</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>nonpersistent</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The message delivery mode that will be used for each producer. Available values are:</p><ol><li>'nonpersistent' - use non-persistent delivery mode. javax.jms.DeliveryMode.NON_PERSISTENT.</li><li>'persistent' - use persistent delivery mode. javax.jms.DeliveryMode.PERSISTENT.</li></ol></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.messageSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1024 bytes</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The size of each text message to send.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.msgFileName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If you want to send a fixed message from a particular file. The file needs to be a text file. The entire content of the file will be sent as message body. Specifying a file containing the message to be sent makes the producer ignore the property producer.messageSize. Use relative or full path. Example: -Dproducer.msgFileName=../message.xml</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.createNewMsg</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, each send will create a new JMS Message with the specified message size with incrementing text messages (i.e. Text Message 1, Text Message 2, ...). If false, only one message will be created before the send loop, and this message will be sent over and over again.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.sendDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0 ms</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Pause producer for sendDelay milliseconds after each message (allows producer throttling).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.sendType</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>time</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Send either time-based or message-count-based. Available values are:</p><ol><li>'time' - keep sending messages until a specific interval of time elapses.</li><li>'count' - keep sending messages until N messages has been sent.</li></ol></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.sendCount</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000000 msgs <br clear="none" class="atl-forced-newline"> (1 million)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If sendType=count, send this number of messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.sendDuration</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>300000 ms <br clear="none" class="atl-forced-newline"> (5 mins)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If sendType=time, send messages for this number of milliseconds.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.header</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>none</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specify message headers to be set on all messages. Headers use name=value syntax and can be separated using ':'. More than one header can be set on a single producer.header line, e.g. producer.header="JMSType=car:MyHeader=MyValue" (no spaces). Only one producer.header line is allowed!</p></td></tr></tbody></table></div><h3 id="ActiveMQPerformanceModuleUsersManual-ConfigurationforrunningaJMSConsumer">Configuration for running a JMS Consumer</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Configuration Key</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>consumer.sessTransacted</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies if the session created will be transacted or not. See the JMS Specifications for more details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.sessAckMode</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>autoAck</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specified the acknowledge mode of the session. See the JMS Specifications for more details. Available values are:</p><ol><li>'autoAck' - Session.AUTO_ACKNOWLEDGE</li><li>'clientAck' - Session.CLIENT_ACKNOWLEDGE</li><li>'dupsAck' - Session.DUPS_OK_ACKNOWLEDGE</li><li>'transacted' - Session.TRANSACTED</li></ol></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.commitAfterXMsgs</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Commit transaction after the specified amount of messages. Only used in conjunction with a transacted JMS Session (consumer.sessTransacted=true and consumer.sessAckMode=transacted)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.destName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>TEST.FOO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The prefix of the destination name to use. To specify a queue, prefix the destination name with 'queue://', for topics, prefix the destination with 'topic://'. If no prefix is specified, a topic will be created.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.destComposite</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If there are more than one destination, and destComposite=true, the destinations will be merged into one. This assumes that the provider supports composite destinations.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.durable</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, create a durable subscriber, otherwise create a message consumer. See the JMS Specifications for more details.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.asyncRecv</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, asynchronously receive messages using the onMessage() method, otherwise use the receive() method.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.recvDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0 ms</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Pause consumer for recvDelay milliseconds with each message (allows consumer throttling).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.recvType</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>time</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Receive either time-based or message-count-based. Available values are:</p><ol><li>'time' - keep receiving messages until a specific time interval has elapsed.</li><li>'count' - keep receiving until N messages has been received.</li></ol></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.recvCount</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000000 msgs <br clear="none" class="atl-forced-newline"> (1 million)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If recvType=count, receive this much messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.recvDuration</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>300000 ms <br clear="none" class="atl-forced-newline"> (5 mins)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If recvType=time, receive messages for this specific time duration.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.messageSelector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>none</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specify <a shape="rect" class="external-link" href="http://activemq.apache.org/selectors.html">message selector</a> for all consumers. E.g. consumer.messageSelector="MyHeader = 'MyValue' AND JMSType = 'car'"</p></td></tr></tbody></table></div><p><strong>Note</strong>: If you have more than one consumer receiving from multiple destinations, it is a good idea to change the sysTest.destDistro to 'equal', since by default it uses 'all' and a consumer can only receive from a single destination, hence all consumers will receive from the first destination in the list only.</p><h3 id="ActiveMQPerformanceModuleUsersManual-ConfigurationforSPIConnectionFactory:org.apache.activemq.tool.spi.ActiveMQPojoSPI">Configuration for SPI Connection Factory: org.apache.activemq.tool.spi.ActiveMQPojoSPI</h3><p><strong>Description:</strong> This provides details in configuring the JMS Connection Factory created by ActiveMQPojoSPI. Default values are based from the default values of the service provider org.apache.activemq.ActiveMQConnectionFactory.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Configuration Key</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>factory.brokerURL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>tcp://localhost:61616</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The url of the broker the client will connect to.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.userName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Username on the connection to use.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.password</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Password on the connection to use.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.clientID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Client ID the connection will use. If none is specified, it will be automatically generated.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.asyncSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, asynchronously send messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.asyncDispatch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, asynchronously dispatch messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.asyncSession</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, session will dispatch messages asynchronously.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.closeTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>15000 ms</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.copyMsgOnSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, creates a copy of the message to be sent.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.disableTimestamp</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, disable the setting of the JMSTimestamp.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.deferObjSerial</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, defer the serialization of message objects.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.optimAck</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, optimizes the acknowledgement of messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.optimDispatch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, optimizes the dispatching of messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchQueue</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000 messages</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of messages a queue consumer will cache in RAM before processing it.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchTopic</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>32766 messages</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of messages a topic consumer will cache in RAM before processing it.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.useCompression</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, compress message data.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.useRetroactive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, make consumers retroactive.</p></td></tr></tbody></table></div><h3 id="ActiveMQPerformanceModuleUsersManual-ConfigurationforSPIConnectionFactory:org.apache.activemq.tool.spi.ActiveMQClassLoaderSPI">Configuration for SPI Connection Factory: org.apache.activemq.tool.spi.ActiveMQClassLoaderSPI</h3><p><strong>Description:</strong> This provides details in configuring the JMS Connection Factory created by ActiveMQClassLoaderSPI. Default values are based from the default values of the service provider org.apache.activemq.ActiveMQConnectionFactory.</p><p>ActiveMQClassLoaderSPI loads from the classpath "org.apache.activemq.ActiveMQConnectionFactory" and configures it using reflection. Configuration is generally based on the API of the class loaded. General format is factory.YYY or factory.XXX.YYY, where the last variable (YYY) is the property to set and everything in between is the getter of the class to use to set (YYY). For example:</p><ol><li>To set the value for asyncSend in ActiveMQConnectionFactory, use:<br clear="none"> <code>factory.useAsyncSend=true</code>, which is equivalent to calling <code>factory.setUseAsyncSend(true)</code></li></ol><ol><li>To set the queue prefetch for ActiveMQConnectionFactory, use:<br clear="none"> <code>factory.prefetchPolicy.queuePrefetch=1</code>, which is equivalent to calling <code>factory.getPrefetchPolicy().setQueuePrefetch(1)</code></li></ol><p>It should be noted that the loaded class should implement the appropriate getter and setter methods. Nested objects should also be properly instantiated. For more information on configuring this SPI, refer to the specific provider API manual.</p><p>As of ActiveMQ 4.0.1, these are the available fields and default values:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Configuration Key</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchPolicy.optimizeDurableTopicPrefetch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchPolicy.durableTopicPrefetch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>100</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.password</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchPolicy.queueBrowserPrefetch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>500</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.useCompression</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.disableTimeStampsByDefault</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.optimizedMessageDispatch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.useRetroactiveConsumer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.alwaysSessionAsync</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.copyMessageOnSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchPolicy.topicPrefetch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>32766</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.useAsyncSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.redeliveryPolicy.backOffMultiplier</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchPolicy.inputStreamPrefetch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>100</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.closeTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>15000</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.userName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.optimizeAcknowledge</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.clientID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.objectMessageSerializationDefered</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.asyncDispatch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.redeliveryPolicy.initialRedeliveryDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchPolicy.queuePrefetch</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.redeliveryPolicy.maximumRedeliveries</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.redeliveryPolicy.useCollisionAvoidance</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.prefetchPolicy.maximumPendingMessageLimit</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>factory.redeliveryPolicy.useExponentialBackOff</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr></tbody></table></div><h3 id="ActiveMQPerformanceModuleUsersManual-Configurationforsamplers">Configuration for samplers</h3><p>There are two samplers built into the perfomance test tool. Both are configured with the same configuration keys, only prefixed with different sampler names.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Sampler</th><th colspan="1" rowspan="1" class="confluenceTh"><em>samplerName</em></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Throughput Sampler</td><td colspan="1" rowspan="1" class="confluenceTd">tpSampler</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">CPU Sampler</td><td colspan="1" rowspan="1" class="confluenceTd">cpuSampler</td></tr></tbody></table></div><p>For example, it is possible to configure the two samplers differently for a single test run, using the prefixes above as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn activemq-perf:producer -DtpSampler.duration=10000 -DcpuSampler.duration=15000]]></script>
-</div></div><p>By default, both samplers are used within a test run. This however, can be overridden through the use of the <code>sysTest.samplers</code> property.</p><h4 id="ActiveMQPerformanceModuleUsersManual-BeforeActiveMQ5.11">Before ActiveMQ 5.11</h4><p>Sampler configurations are not tied in to the test run, so it is possible for the sampler to run for longer than the actual test itself. For short run durations, the sampler may not even have ramped up before the test completes.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Configuration Key</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><em>samplerName</em>.duration</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>300000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The total duration (in ms) the sampler will run, including ramp up and ramp down time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><em>samplerName</em>.rampUpTime</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The ramp up time of the sampler, sampling will only start after the ramp up time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><em>samplerName</em>.rampDownTime</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The ramp down time of the sampler, sampling will stop when the sampler has executed for (duration - rampUpTime - rampDownTime) ms.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><em>samplerName</em>.interval</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The interval (in ms), the sampler will sample for data.</p></td></tr></tbody></table></div><h4 id="ActiveMQPerformanceModuleUsersManual-FromActiveMQ5.11">From ActiveMQ 5.11</h4><p>Sampler run duration is tied directly to the behavior of the client (producer/consumer). Due to the non-deterministic nature of count-based tests (where consumer.recvType or producer.sendType are set to <code>count</code>), duration, ramp up and ramp down times are ignored; the samplers are shut down when the client completes.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Configuration Key</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><em>samplerName</em>.duration</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For time-based tests, matches the consumer or producer duration.</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The total duration (in ms) the sampler will run, including ramp up and ramp down time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><em>samplerName</em>.rampUpTime</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null; defers to rampUpPercent.</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The ramp up time of the sampler, sampling will only start after the ramp up time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><em>samplerName</em>.rampDownTime</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null; defers to rampDownPercent.</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The ramp down time of the sampler, sampling will stop when the sampler has executed for (duration - rampUpTime - rampDownTime) ms.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><em>samplerName</em>.rampUpPercent</td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1" class="confluenceTd">The percentage of the overall run duration that the sampler should use to ramp up (0-100). Overridden by rampUpTime.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><em>samplerName</em>.rampDownPercent</td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1" class="confluenceTd">The percentage of the overall run duration that the sampler should use to ramp down (0-99). Overridden by rampDownTime.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><em>samplerName</em>.interval</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The interval (in ms), the sampler will sample for data.</p></td></tr></tbody></table></div><p>The time taken to ramp up and ramp down, whether defined through milliseconds or as a percentage cannot exceed the total duration.</p></div>
+</plain-text-body></structured-macro><p>where you switch host:port with the actual values.</p><p>When you run the producer & consumer, it generates an XML performance report in the current directory, so that you can graph and chart the results etc. See the <link><page ri:content-title="sample report"></page></link></p><h3>Maven goals</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Goal</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>activemq-perf:broker</p></td><td colspan="1" rowspan="1"><p>Starts broker using the activemq configuration file located in "src\main\resources\broker-conf" where the default config is activemq.xml. <br clear="none" class="atl-forced-newline"> Parameters: <br clear="none" class="atl-forced-newline">  1. -DconfigType - specifies the type of configuration to use. Its value must be one of the filename in the "..\broker-config" directory (e.g. -DconfigType=kaha). <br clear="none" class="atl-forced-newline">  2. -DconfigFile - path to config file other than those in "src\..\broker-config".e.g -DconfigFile=c:\dir\activemq.xml)</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-perf:consumer</p></td><td colspan="1" rowspan="1"><p>Starts the consumer's performance testing. The generated report file can be found in the directory specified in the parameter "sysTest.reportDir".</p></td></tr><tr><td colspan="1" rowspan="1"><p>activemq-perf:producer</p></td><td colspan="1" rowspan="1"><p>Starts the producer's performance testing. The generated report file can be found in the directory specified in the parameter "sysTest.reportDir".</p></td></tr></tbody></table><p><sup>1</sup> <strong>Note</strong>:The parameters for both consumer and producers are described in the next section. (<link><page ri:content-title="sample report"></page></link>)</p><h3>Configuration for running a system of JMS Clients (Producer/Consumer)</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Configuration Key</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>sysTest.propsConfigFile</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>Use properties specified externally in a key=value properties file</p></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.clientPrefix</p></td><td colspan="1" rowspan="1"><p>JmsConsumer or JmsProducer</p></td><td colspan="1" rowspan="1"><p>Specifies the client name prefix that will be use for each system. By default it will use JmsConsumer for consumer systems, and JmsProducer for producer systems.</p></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.numClients</p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Specifies the number of JMS Clients to start.</p></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.totalDests</p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Specifies the total number of destinations to use for the whole system test.</p></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.destDistro</p></td><td colspan="1" rowspan="1"><p>all</p></td><td colspan="1" rowspan="1"><p>Specifies how to distribute the destinations to the clients. Available values are (Invalid value will result to using the default value 'all')<sup>1</sup>:</p><ul><li>'all' - All clients will send/receive to all destinations. i.e. if there are 2 producers and 5 destinations, each producer will send a message to each individual destination.</li><li>'equal' - Clients will equally divide the destinations among themselves. i.e. if there are 2 producers and 5 destinations, each producer will send messages to 2 destinations. The fifth destination will not be used.</li><li>'divide' - Clients will divide the destinations among themselves regardless of equality. i.e. if there are 2 producers and 5 destinations, producer 1 will send to 3 destinations, while producer 2 will send to 2 destinations.</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.reportDir</p></td><td colspan="1" rowspan="1"><p>./</p></td><td colspan="1" rowspan="1"><p>The directory where the sampler report will be saved.</p></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.reportName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>The default filename the sampler report will be saved us. There is usually no need to set this setting as the default value will create either JmsProducer_numClients#<em>numDests#</em><Dest Distro>.xml and JmsConsumer_numClients#_numDests#_<Dest Distro>.xml, where # represents the number of clients and destinations set for that system, and <Dest Distro> specifies the destination distribution for the system.</p></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.reportType</p></td><td colspan="1" rowspan="1"><p>xml</p></td><td colspan="1" rowspan="1"><p>Specifies the manner of generating the performance report. Available values are:</p><ul><li>'xml' - Write the performance report into an xml file. Specified by reportDirectory and reportName. A verbose summary will also be displayed at the end of the test.</li><li>'verbose' - All information will be written to the standard output, which includes settings, sampler data, and performance summary.</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.samplers</p></td><td colspan="1" rowspan="1"><p>tp,cpu</p></td><td colspan="1" rowspan="1"><p>Specifies the samplers that will be started. To use enable more than one sampler, separate the values by commas without spaces. Available values are:</p><ul><li>'tp' - Throughput sampler</li><li>'cpu' - CPU Usage sampler</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p>sysTest.spiClass</p></td><td colspan="1" rowspan="1"><p>org.apache.activemq.tool.spi.ActiveMQClassLoaderSPI</p></td><td colspan="1" rowspan="1"><p>The service provider interface class that allows the client to create a generic connection factory. Current available SPI classes include:</p><ol><li>'org.apache.activemq.tool.ActiveMQPojoSPI'</li><li>'org.apache.activemq.tool.ActiveMQClassLoaderSPI'</li></ol></td></tr></tbody></table><p><sup>1</sup> <strong>Note</strong>: If the number of destinations is less than the number of clients and the distribution type is either 'equal' or 'divide', each client will send/receive from only one destination, distributing the destinations among the clients. i.e. if there are 5 producers and 2 destinations, 3 producers will send to destination 1, and 2 producers will send to destination 2. Also, a consumer can only receive from a single destination, unless composite destination is supported and specified.</p><h3>Configuration for running a JMS Producer</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Configuration Key</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>producer.sessTransacted</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Specifies if the session created will be transacted or not. See the JMS Specifications for more details.</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.sessAckMode</p></td><td colspan="1" rowspan="1"><p>autoAck</p></td><td colspan="1" rowspan="1"><p>Specified the acknowledge mode of the session. See the JMS Specifications for more details. Available values are:</p><ol><li>'autoAck' - Session.AUTO_ACKNOWLEDGE</li><li>'clientAck' - Session.CLIENT_ACKNOWLEDGE</li><li>'dupsAck' - Session.DUPS_OK_ACKNOWLEDGE</li><li>'transacted' - Session.TRANSACTED</li></ol></td></tr><tr><td colspan="1" rowspan="1"><p>producer.commitAfterXMsgs</p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Commit transaction after the specified amount of messages. Only used in conjunction with a transacted JMS Session (producer.sessTransacted=true and producer.sessAckMode=transacted)</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.destName</p></td><td colspan="1" rowspan="1"><p>TEST.FOO</p></td><td colspan="1" rowspan="1"><p>The prefix of the destination name to use. To specify a queue, prefix the destination name with 'queue://', for topics, prefix the destination with 'topic://'. If no prefix is specified, a topic will be created.</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.destComposite</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If there are more than one destination, and destComposite=true, the destinations will be merged into one. This assumes that the provider supports composite destinations.</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.deliveryMode</p></td><td colspan="1" rowspan="1"><p>nonpersistent</p></td><td colspan="1" rowspan="1"><p>The message delivery mode that will be used for each producer. Available values are:</p><ol><li>'nonpersistent' - use non-persistent delivery mode. javax.jms.DeliveryMode.NON_PERSISTENT.</li><li>'persistent' - use persistent delivery mode. javax.jms.DeliveryMode.PERSISTENT.</li></ol></td></tr><tr><td colspan="1" rowspan="1"><p>producer.messageSize</p></td><td colspan="1" rowspan="1"><p>1024 bytes</p></td><td colspan="1" rowspan="1"><p>The size of each text message to send.</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.msgFileName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>If you want to send a fixed message from a particular file. The file needs to be a text file. The entire content of the file will be sent as message body. Specifying a file containing the message to be sent makes the producer ignore the property producer.messageSize. Use relative or full path. Example: -Dproducer.msgFileName=../message.xml</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.createNewMsg</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, each send will create a new JMS Message with the specified message size with incrementing text messages (i.e. Text Message 1, Text Message 2, ...). If false, only one message will be created before the send loop, and this message will be sent over and over again.</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.sendDelay</p></td><td colspan="1" rowspan="1"><p>0 ms</p></td><td colspan="1" rowspan="1"><p>Pause producer for sendDelay milliseconds after each message (allows producer throttling).</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.sendType</p></td><td colspan="1" rowspan="1"><p>time</p></td><td colspan="1" rowspan="1"><p>Send either time-based or message-count-based. Available values are:</p><ol><li>'time' - keep sending messages until a specific interval of time elapses.</li><li>'count' - keep sending messages until N messages has been sent.</li></ol></td></tr><tr><td colspan="1" rowspan="1"><p>producer.sendCount</p></td><td colspan="1" rowspan="1"><p>1000000 msgs <br clear="none" class="atl-forced-newline"> (1 million)</p></td><td colspan="1" rowspan="1"><p>If sendType=count, send this number of messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.sendDuration</p></td><td colspan="1" rowspan="1"><p>300000 ms <br clear="none" class="atl-forced-newline"> (5 mins)</p></td><td colspan="1" rowspan="1"><p>If sendType=time, send messages for this number of milliseconds.</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.header</p></td><td colspan="1" rowspan="1"><p>none</p></td><td colspan="1" rowspan="1"><p>Specify message headers to be set on all messages. Headers use name=value syntax and can be separated using ':'. More than one header can be set on a single producer.header line, e.g. producer.header="JMSType=car:MyHeader=MyValue" (no spaces). Only one producer.header line is allowed!</p></td></tr></tbody></table><h3>Configuration for running a JMS Consumer</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Configuration Key</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>consumer.sessTransacted</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Specifies if the session created will be transacted or not. See the JMS Specifications for more details.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.sessAckMode</p></td><td colspan="1" rowspan="1"><p>autoAck</p></td><td colspan="1" rowspan="1"><p>Specified the acknowledge mode of the session. See the JMS Specifications for more details. Available values are:</p><ol><li>'autoAck' - Session.AUTO_ACKNOWLEDGE</li><li>'clientAck' - Session.CLIENT_ACKNOWLEDGE</li><li>'dupsAck' - Session.DUPS_OK_ACKNOWLEDGE</li><li>'transacted' - Session.TRANSACTED</li></ol></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.commitAfterXMsgs</p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>Commit transaction after the specified amount of messages. Only used in conjunction with a transacted JMS Session (consumer.sessTransacted=true and consumer.sessAckMode=transacted)</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.destName</p></td><td colspan="1" rowspan="1"><p>TEST.FOO</p></td><td colspan="1" rowspan="1"><p>The prefix of the destination name to use. To specify a queue, prefix the destination name with 'queue://', for topics, prefix the destination with 'topic://'. If no prefix is specified, a topic will be created.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.destComposite</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If there are more than one destination, and destComposite=true, the destinations will be merged into one. This assumes that the provider supports composite destinations.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.durable</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, create a durable subscriber, otherwise create a message consumer. See the JMS Specifications for more details.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.asyncRecv</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If true, asynchronously receive messages using the onMessage() method, otherwise use the receive() method.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.recvDelay</p></td><td colspan="1" rowspan="1"><p>0 ms</p></td><td colspan="1" rowspan="1"><p>Pause consumer for recvDelay milliseconds with each message (allows consumer throttling).</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.recvType</p></td><td colspan="1" rowspan="1"><p>time</p></td><td colspan="1" rowspan="1"><p>Receive either time-based or message-count-based. Available values are:</p><ol><li>'time' - keep receiving messages until a specific time interval has elapsed.</li><li>'count' - keep receiving until N messages has been received.</li></ol></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.recvCount</p></td><td colspan="1" rowspan="1"><p>1000000 msgs <br clear="none" class="atl-forced-newline"> (1 million)</p></td><td colspan="1" rowspan="1"><p>If recvType=count, receive this much messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.recvDuration</p></td><td colspan="1" rowspan="1"><p>300000 ms <br clear="none" class="atl-forced-newline"> (5 mins)</p></td><td colspan="1" rowspan="1"><p>If recvType=time, receive messages for this specific time duration.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.messageSelector</p></td><td colspan="1" rowspan="1"><p>none</p></td><td colspan="1" rowspan="1"><p>Specify <a shape="rect" href="http://activemq.apache.org/selectors.html">message selector</a> for all consumers. E.g. consumer.messageSelector="MyHeader = 'MyValue' AND JMSType = 'car'"</p></td></tr></tbody></table><p><strong>Note</strong>: If you have more than one consumer receiving from multiple destinations, it is a good idea to change the sysTest.destDistro to 'equal', since by default it uses 'all' and a consumer can only receive from a single destination, hence all consumers will receive from the first destination in the list only.</p><h3>Configuration for SPI Connection Factory: org.apache.activemq.tool.spi.ActiveMQPojoSPI</h3><p><strong>Description:</strong> This provides details in configuring the JMS Connection Factory created by ActiveMQPojoSPI. Default values are based from the default values of the service provider org.apache.activemq.ActiveMQConnectionFactory.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Configuration Key</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>factory.brokerURL</p></td><td colspan="1" rowspan="1"><p>tcp://localhost:61616</p></td><td colspan="1" rowspan="1"><p>The url of the broker the client will connect to.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.userName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>Username on the connection to use.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.password</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>Password on the connection to use.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.clientID</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>Client ID the connection will use. If none is specified, it will be automatically generated.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.asyncSend</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, asynchronously send messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.asyncDispatch</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, asynchronously dispatch messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.asyncSession</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If true, session will dispatch messages asynchronously.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.closeTimeout</p></td><td colspan="1" rowspan="1"><p>15000 ms</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.copyMsgOnSend</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If true, creates a copy of the message to be sent.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.disableTimestamp</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, disable the setting of the JMSTimestamp.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.deferObjSerial</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, defer the serialization of message objects.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.optimAck</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If true, optimizes the acknowledgement of messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.optimDispatch</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If true, optimizes the dispatching of messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchQueue</p></td><td colspan="1" rowspan="1"><p>1000 messages</p></td><td colspan="1" rowspan="1"><p>Number of messages a queue consumer will cache in RAM before processing it.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchTopic</p></td><td colspan="1" rowspan="1"><p>32766 messages</p></td><td colspan="1" rowspan="1"><p>Number of messages a topic consumer will cache in RAM before processing it.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.useCompression</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, compress message data.</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.useRetroactive</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, make consumers retroactive.</p></td></tr></tbody></table><h3>Configuration for SPI Connection Factory: org.apache.activemq.tool.spi.ActiveMQClassLoaderSPI</h3><p><strong>Description:</strong> This provides details in configuring the JMS Connection Factory created by ActiveMQClassLoaderSPI. Default values are based from the default values of the service provider org.apache.activemq.ActiveMQConnectionFactory.</p><p>ActiveMQClassLoaderSPI loads from the classpath "org.apache.activemq.ActiveMQConnectionFactory" and configures it using reflection. Configuration is generally based on the API of the class loaded. General format is factory.YYY or factory.XXX.YYY, where the last variable (YYY) is the property to set and everything in between is the getter of the class to use to set (YYY). For example:</p><ol><li>To set the value for asyncSend in ActiveMQConnectionFactory, use:<br clear="none"> <code>factory.useAsyncSend=true</code>, which is equivalent to calling <code>factory.setUseAsyncSend(true)</code></li></ol><ol><li>To set the queue prefetch for ActiveMQConnectionFactory, use:<br clear="none"> <code>factory.prefetchPolicy.queuePrefetch=1</code>, which is equivalent to calling <code>factory.getPrefetchPolicy().setQueuePrefetch(1)</code></li></ol><p>It should be noted that the loaded class should implement the appropriate getter and setter methods. Nested objects should also be properly instantiated. For more information on configuring this SPI, refer to the specific provider API manual.</p><p>As of ActiveMQ 4.0.1, these are the available fields and default values:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Configuration Key</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchPolicy.optimizeDurableTopicPrefetch</p></td><td colspan="1" rowspan="1"><p>1000</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchPolicy.durableTopicPrefetch</p></td><td colspan="1" rowspan="1"><p>100</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.password</p></td><td colspan="1" rowspan="1"><p>null</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchPolicy.queueBrowserPrefetch</p></td><td colspan="1" rowspan="1"><p>500</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.useCompression</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.disableTimeStampsByDefault</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.optimizedMessageDispatch</p></td><td colspan="1" rowspan="1"><p>true</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.useRetroactiveConsumer</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.alwaysSessionAsync</p></td><td colspan="1" rowspan="1"><p>true</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.copyMessageOnSend</p></td><td colspan="1" rowspan="1"><p>true</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchPolicy.topicPrefetch</p></td><td colspan="1" rowspan="1"><p>32766</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.useAsyncSend</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.redeliveryPolicy.backOffMultiplier</p></td><td colspan="1" rowspan="1"><p>5</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchPolicy.inputStreamPrefetch</p></td><td colspan="1" rowspan="1"><p>100</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.closeTimeout</p></td><td colspan="1" rowspan="1"><p>15000</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.userName</p></td><td colspan="1" rowspan="1"><p>null</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.optimizeAcknowledge</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.clientID</p></td><td colspan="1" rowspan="1"><p>null</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.objectMessageSerializationDefered</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.asyncDispatch</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.redeliveryPolicy.initialRedeliveryDelay</p></td><td colspan="1" rowspan="1"><p>1000</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchPolicy.queuePrefetch</p></td><td colspan="1" rowspan="1"><p>1000</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.redeliveryPolicy.maximumRedeliveries</p></td><td colspan="1" rowspan="1"><p>5</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.redeliveryPolicy.useCollisionAvoidance</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.prefetchPolicy.maximumPendingMessageLimit</p></td><td colspan="1" rowspan="1"><p>0</p></td></tr><tr><td colspan="1" rowspan="1"><p>factory.redeliveryPolicy.useExponentialBackOff</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr></tbody></table><h3>Configuration for samplers</h3><p>There are two samplers built into the perfomance test tool. Both are configured with the same configuration keys, only prefixed with different sampler names.</p><table><tbody><tr><th colspan="1" rowspan="1">Sampler</th><th colspan="1" rowspan="1"><em>samplerName</em></th></tr><tr><td colspan="1" rowspan="1">Throughput Sampler</td><td colspan="1" rowspan="1">tpSampler</td></tr><tr><td colspan="1" rowspan="1">CPU Sampler</td><td colspan="1" rowspan="1">cpuSampler</td></tr></tbody></table><p>For example, it is possible to configure the two samplers differently for a single test run, using the prefixes above as follows:</p><structured-macro ac:macro-id="201b85f5-de18-40d6-b623-52da8b1250dc" ac:name="code" ac:schema-version="1"><plain-text-body>mvn activemq-perf:producer -DtpSampler.duration=10000 -DcpuSampler.duration=15000</plain-text-body></structured-macro><p>By default, both samplers are used within a test run. This however, can be overridden through the use of the <code>sysTest.samplers</code> property.</p><h4>Before ActiveMQ 5.11</h4><p>Sampler configurations are not tied in to the test run, so it is possible for the sampler to run for longer than the actual test itself. For short run durations, the sampler may not even have ramped up before the test completes.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Configuration Key</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><em>samplerName</em>.duration</p></td><td colspan="1" rowspan="1"><p>300000</p></td><td colspan="1" rowspan="1"><p>The total duration (in ms) the sampler will run, including ramp up and ramp down time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><em>samplerName</em>.rampUpTime</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>The ramp up time of the sampler, sampling will only start after the ramp up time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><em>samplerName</em>.rampDownTime</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>The ramp down time of the sampler, sampling will stop when the sampler has executed for (duration - rampUpTime - rampDownTime) ms.</p></td></tr><tr><td colspan="1" rowspan="1"><p><em>samplerName</em>.interval</p></td><td colspan="1" rowspan="1"><p>1000</p></td><td colspan="1" rowspan="1"><p>The interval (in ms), the sampler will sample for data.</p></td></tr></tbody></table><h4>From ActiveMQ 5.11</h4><p>Sampler run duration is tied directly to the behavior of the client (producer/consumer). Due to the non-deterministic nature of count-based tests (where consumer.recvType or producer.sendType are set to <code>count</code>), duration, ramp up and ramp down times are ignored; the samplers are shut down when the client completes.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Configuration Key</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><em>samplerName</em>.duration</p></td><td colspan="1" rowspan="1"><p>For time-based tests, matches the consumer or producer duration.</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1"><p>The total duration (in ms) the sampler will run, including ramp up and ramp down time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><em>samplerName</em>.rampUpTime</p></td><td colspan="1" rowspan="1"><p>null; defers to rampUpPercent.</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1"><p>The ramp up time of the sampler, sampling will only start after the ramp up time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><em>samplerName</em>.rampDownTime</p></td><td colspan="1" rowspan="1"><p>null; defers to rampDownPercent.</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1"><p>The ramp down time of the sampler, sampling will stop when the sampler has executed for (duration - rampUpTime - rampDownTime) ms.</p></td></tr><tr><td colspan="1" rowspan="1"><em>samplerName</em>.rampUpPercent</td><td colspan="1" rowspan="1"><p>0</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1">The percentage of the overall run duration that the sampler should use to ramp up (0-100). Overridden by rampUpTime.</td></tr><tr><td colspan="1" rowspan="1"><em>samplerName</em>.rampDownPercent</td><td colspan="1" rowspan="1"><p>0</p><p><em>Ignored for count-based tests.</em></p></td><td colspan="1" rowspan="1">The percentage of the overall run duration that the sampler should use to ramp down (0-99). Overridden by rampDownTime.</td></tr><tr><td colspan="1" rowspan="1"><p><em>samplerName</em>.interval</p></td><td colspan="1" rowspan="1"><p>1000</p></td><td colspan="1" rowspan="1"><p>The interval (in ms), the sampler will sample for data.</p></td></tr></tbody></table><p>The time taken to ramp up and ramp down, whether defined through milliseconds or as a percentage cannot exceed the total duration.</p></div>
diff --git a/activemq-real-time.xml b/activemq-real-time.xml
index a2e35de..29757cb 100644
--- a/activemq-real-time.xml
+++ b/activemq-real-time.xml
@@ -12,9 +12,9 @@
<p>To enable cross-language support ,enable versioning of the wire format, and aid fast throughput - Apache ActiveBlaze is built on top of the Google's protobuf - a framework for efficiently encoding extensible data structures.</p>
-<h2 id="ActiveMQRealTime-lowlatencyreliablemulticast">low latency reliable multicast</h2>
+<h2>low latency reliable multicast</h2>
-<h2 id="ActiveMQRealTime-Groupmembership">Group membership</h2>
+<h2>Group membership</h2>
<p>Support for dynamic joining and leaving of groups, membership notifications and true point to point and queue messaging:</p>
<ul><li>Dynamic membership information</li><li>broadcast messaging</li><li>point-to-point</li><li>in boxes</li><li>configurable heartbeats</li></ul>
@@ -22,13 +22,13 @@
-<h2 id="ActiveMQRealTime-Clustermanagement">Cluster management</h2>
+<h2>Cluster management</h2>
<p>A distributed state map, with the following:</p>
<ul><li>Distributed state (Map)</li><li>Map change listeners</li><li>write locks</li><li>lock expiration</li><li>optional state and lock removal when a member leaves</li><li>automatic state and lock replication and failover</li></ul>
-<h2 id="ActiveMQRealTime-Inmoredetail...">In more detail ...</h2>
+<h2>In more detail ...</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="broadcasting.xml">Broadcasting</a></li><li><a shape="rect" href="group-membership.xml">Group Membership</a></li><li><a shape="rect" href="life-cycle.xml">Life Cycle</a></li><li><a shape="rect" href="the-activeblaze-message-type.xml">The ActiveBlaze Message type</a></li></ul></div>
+<structured-macro ac:macro-id="91ae2935-d0f6-4b85-ba65-3c2a8ae9d156" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/advisory-message.xml b/advisory-message.xml
index dc77ee1..fd86b03 100644
--- a/advisory-message.xml
+++ b/advisory-message.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><p>ActiveMQ supports advisory messages which allows you to watch the system using regular JMS messages. Currently we have advisory messages that support:</p><ul><li>consumers, producers and connections starting and stopping</li><li>temporary destinations being created and destroyed</li><li>messages expiring on topics and queues</li><li>brokers sending messages to destinations with no consumers.</li><li>connections starting and stopping</li></ul><p>Advisory messages can be thought as some kind of administrative channel where you receive information regarding what is happening on your JMS provider along with what's happening with producers, consumers and destinations. When you look at a broker via <a shape="rect" href="jmx.xml">JMX</a> you will see the advisory topics prefixed with <strong><code>ActiveMQ.Advisory.</code></strong>.</p><p>Every Advisory has the message <strong>type</strong> 'Advisory' and some predefined message properties:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>originBrokerId</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>StringProperty</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The id of the broker where the advisory originated.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5.x</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>originBrokerName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>StringProperty</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the broker where the advisory originated.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5.x</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>originBrokerURL</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>StringProperty</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The first URL of the broker where the advisory originated.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5.2</p></td></tr></tbody></table></div><p>In addition, some messages carry a <strong><code>Command</code></strong> object, which carries additional information about the nature of the advisory, e.g., a subscription to each of the destination returns an <strong><code>ActiveMQMessage</code></strong>. Specific <strong><code>DataStructure</code></strong> objects, e.g.,. <strong><code>ConsumerInfo</code>, <code>ProducerInfo</code></strong>, <strong><code>ConnectionInfo</code></strong> can be retrieved using <strong><code>ActiveMQMessage.getDataStructure()</code></strong>.</p><p>For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Destination advisoryDestination = AdvisorySupport.getProducerAdvisoryTopic(destination)
+<div class="wiki-content maincontent"><p>ActiveMQ supports advisory messages which allows you to watch the system using regular JMS messages. Currently we have advisory messages that support:</p><ul><li>consumers, producers and connections starting and stopping</li><li>temporary destinations being created and destroyed</li><li>messages expiring on topics and queues</li><li>brokers sending messages to destinations with no consumers.</li><li>connections starting and stopping</li></ul><p>Advisory messages can be thought as some kind of administrative channel where you receive information regarding what is happening on your JMS provider along with what's happening with producers, consumers and destinations. When you look at a broker via <link><page ri:content-title="JMX"></page></link> you will see the advisory topics prefixed with <strong><code>ActiveMQ.Advisory.</code></strong>.</p><p>Every Advisory has the message <strong>type</strong> 'Advisory' and some predefined message properties:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Property</p></th><th colspan="1" rowspan="1"><p>Type</p></th><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>originBrokerId</code></p></td><td colspan="1" rowspan="1"><p><code>StringProperty</code></p></td><td colspan="1" rowspan="1"><p>The id of the broker where the advisory originated.</p></td><td colspan="1" rowspan="1"><p>5.x</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>originBrokerName</code></p></td><td colspan="1" rowspan="1"><p><code>StringProperty</code></p></td><td colspan="1" rowspan="1"><p>The name of the broker where the advisory originated.</p></td><td colspan="1" rowspan="1"><p>5.x</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>originBrokerURL</code></p></td><td colspan="1" rowspan="1"><p><code>StringProperty</code></p></td><td colspan="1" rowspan="1"><p>The first URL of the broker where the advisory originated.</p></td><td colspan="1" rowspan="1"><p>5.2</p></td></tr></tbody></table><p>In addition, some messages carry a <strong><code>Command</code></strong> object, which carries additional information about the nature of the advisory, e.g., a subscription to each of the destination returns an <strong><code>ActiveMQMessage</code></strong>. Specific <strong><code>DataStructure</code></strong> objects, e.g.,. <strong><code>ConsumerInfo</code>, <code>ProducerInfo</code></strong>, <strong><code>ConnectionInfo</code></strong> can be retrieved using <strong><code>ActiveMQMessage.getDataStructure()</code></strong>.</p><p>For example:</p><structured-macro ac:macro-id="44dc8e29-8077-4e45-bfef-b8553dac52a1" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><plain-text-body>Destination advisoryDestination = AdvisorySupport.getProducerAdvisoryTopic(destination)
MessageConsumer consumer = session.createConsumer(advisoryDestination);
consumer.setMessageListener(this);
@@ -10,41 +9,27 @@
ProducerInfo prod = (ProducerInfo) aMsg.getDataStructure();
}
catch(JMSException e) {
- log.error("Failed to process message: " + msg);
+ log.error("Failed to process message: " + msg);
}
}
}
-]]></script>
-</div></div><h2 id="AdvisoryMessage-Thefollowingadvisorytopicsaresupported">The following advisory topics are supported</h2><h3 id="AdvisoryMessage-Clientbasedadvisories">Client based advisories</h3><div class="confluence-information-macro confluence-information-macro-tip"><p class="title">Tip</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>These are always generated.</p></div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Advisory Topics</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Properties</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Data Structure</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Connection</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Connection start & stop messages.</p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ConnectionInfo</code>, <code>RemoveInfo</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Producer.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Producer start & stop messages on a Queue.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='producerCount'</code> - the number of producers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ProducerInfo</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Producer.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Producer start & stop messages on a Topic.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='producerCount'</code> - the number of producers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ProducerInfo</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Consumer.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Consumer start & stop messages on a Queue.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='consumerCount'</code> - the number of Consumers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ConnectionInfo</code>, <code>RemoveInfo</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Consumer.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Consumer start & stop messages on a Topic.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='consumerCount'</code> - the number of Consumers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ConnectionInfo</code>, <code>RemoveInfo</code></p></td></tr></tbody></table></div><p>Note that the consumer start/stop advisory messages also have a <strong><code>consumerCount</code></strong> header to indicate the number of active consumers on the destination when the advisory message was sent. This means you can use the following selector to be notified when there are no active consumers on a given destination:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[consumerCount = 0
-]]></script>
-</div></div><h3 id="AdvisoryMessage-DestinationandMessagebasedadvisories">Destination and Message based advisories</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Advisory Topics</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Properties</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Data Structure</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PolicyEntry Property</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Queue create & destroy.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>DestinationInfo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Topic create & destroy.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>DestinationInfo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.TempQueue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Temporary Queue create & destroy.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>DestinationInfo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.TempTopic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Temporary Topic create & destroy.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>DestinationInfo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Expired.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Expired messages on a Queue.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the expired id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.Expired.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Expired messages on a Topic.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the expired id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.NoConsumer.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>No consumer is available to process messages being sent on a Queue.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>sendAdvisoryIfNoConsumers</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.NoConsumer.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>No consumer is available to process messages being sent on a Topic.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>sendAdvisoryIfNoConsumers</code></p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-tip"><p class="title">Tip</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><strong><code>NoConsumer</code></strong> topic advisories are sent only for non-persistent messages.</p></div></div><h3 id="AdvisoryMessage-Newadvisoriesinversion5.2">New advisories in version 5.2</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Advisory Topics</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Properties</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Data Structure</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PolicyEntry Property</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.SlowConsumer.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Slow Queue Consumer.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='consumerId'</code> - the consumer id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ConsumerInfo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForSlowConsumers</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.SlowConsumer.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Slow Topic Consumer.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='consumerId'</code> - the consumer id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ConsumerInfo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForSlowConsumers</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.FastProducer.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Fast Queue producer.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='producerId'</code> - the producer id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ProducerInfo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisdoryForFastProducers</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory. FastProducer.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Fast Topic producer.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='consumerId'</code>' - the producer id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ProducerInfo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisdoryForFastProducers</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MessageDiscarded.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message discarded.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the discarded id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForDiscardingMessages</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MessageDiscarded.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message discarded.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the discarded id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForDiscardingMessages</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MessageDelivered.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message delivered to the broker.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForDelivery</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MessageDelivered.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message delivered to the broker.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForDelivery</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MessageConsumed.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message consumed by a client.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForConsumed</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MessageConsumed.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message consumed by a client.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForConsumed</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.FULL</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A Usage resource is at its limit.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='usageName'</code> - the name of Usage resource</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryWhenFull</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MasterBroker</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A broker is now the master in a master/slave configuration.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>none</code></p></td></tr></tbody></table></div><h3 id="AdvisoryMessage-NewAdvisoriesin5.4">New Advisories in 5.4</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Advisory Topics</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Properties</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Data Structure</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PolicyEntry Property</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MessageDLQd.Queue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message sent to DLQ.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Always on</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForConsumed</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.MessageDLQd.Topic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Message sent to DLQ.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Always on</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForConsumed</code></p></td></tr></tbody></table></div><h3 id="AdvisoryMessage-Networkbridgeadvisories">Network bridge advisories</h3><p>Starting with ActiveMQ version 5.5 you can watch advisory topics for events related to the status of network bridges. You can get advisory messages when the network bridge is started or stopped.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Advisory Topics</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Properties</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Data Structure</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ActiveMQ.Advisory.NetworkBridge</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Network bridge being stopped or started.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Boolean="started"</code> - <strong><code>true</code></strong> if bridge is started, <strong><code>false</code></strong> if it is stopped.<br clear="none"><code>Boolean="createdByDuplex"</code> - <strong><code>true</code></strong> if the bridge is created by remote network connector.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>BrokerInfo</code> - provides data of the remote broker</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Always on</p></td></tr></tbody></table></div><h3 id="AdvisoryMessage-EnablingAdvisoriesDisabledbyDefault">Enabling Advisories Disabled by Default</h3><p>The advisories that are not turned on by default (see the last column) can be enabled on a <strong><code>PolicyEntry</code></strong> in the ActiveMQ Broker Configuration, e.g., to enable a message consumed advisory you can configure the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<destinationPolicy>
+</plain-text-body></structured-macro><h2>The following advisory topics are supported</h2><h3>Client based advisories</h3><structured-macro ac:macro-id="2c5ea69f-8a07-4ac7-bdf3-8dd608099786" ac:name="tip" ac:schema-version="1"><parameter ac:name="title">Tip</parameter><rich-text-body><p>These are always generated.</p></rich-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Advisory Topics</p></th><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Properties</p></th><th colspan="1" rowspan="1"><p>Data Structure</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Connection</code></p></td><td colspan="1" rowspan="1"><p>Connection start & stop messages.</p></td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1"><p><code>ConnectionInfo</code>, <code>RemoveInfo</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Producer.Queue</code></p></td><td colspan="1" rowspan="1"><p>Producer start & stop messages on a Queue.</p></td><td colspan="1" rowspan="1"><p><code>String='producerCount'</code> - the number of producers</p></td><td colspan="1" rowspan="1"><p><code>ProducerInfo</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Producer.Topic</code></p></td><td colspan="1" rowspan="1"><p>Producer start & stop messages on a Topic.</p></td><td colspan="1" rowspan="1"><p><code>String='producerCount'</code> - the number of producers</p></td><td colspan="1" rowspan="1"><p><code>ProducerInfo</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Consumer.Queue</code></p></td><td colspan="1" rowspan="1"><p>Consumer start & stop messages on a Queue.</p></td><td colspan="1" rowspan="1"><p><code>String='consumerCount'</code> - the number of Consumers</p></td><td colspan="1" rowspan="1"><p><code>ConnectionInfo</code>, <code>RemoveInfo</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Consumer.Topic</code></p></td><td colspan="1" rowspan="1"><p>Consumer start & stop messages on a Topic.</p></td><td colspan="1" rowspan="1"><p><code>String='consumerCount'</code> - the number of Consumers</p></td><td colspan="1" rowspan="1"><p><code>ConnectionInfo</code>, <code>RemoveInfo</code></p></td></tr></tbody></table><p>Note that the consumer start/stop advisory messages also have a <strong><code>consumerCount</code></strong> header to indicate the number of active consumers on the destination when the advisory message was sent. This means you can use the following selector to be notified when there are no active consumers on a given destination:</p><structured-macro ac:macro-id="c7af55a6-e07f-47e3-873e-b6af6e1ccd70" ac:name="code" ac:schema-version="1"><plain-text-body>consumerCount = 0
+</plain-text-body></structured-macro><h3>Destination and Message based advisories</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Advisory Topics</p></th><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Properties</p></th><th colspan="1" rowspan="1"><p>Data Structure</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>PolicyEntry Property</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Queue</code></p></td><td colspan="1" rowspan="1"><p>Queue create & destroy.</p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>DestinationInfo</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Topic</code></p></td><td colspan="1" rowspan="1"><p>Topic create & destroy.</p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>DestinationInfo</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.TempQueue</code></p></td><td colspan="1" rowspan="1"><p>Temporary Queue create & destroy.</p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>DestinationInfo</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.TempTopic</code></p></td><td colspan="1" rowspan="1"><p>Temporary Topic create & destroy.</p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>DestinationInfo</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Expired.Queue</code></p></td><td colspan="1" rowspan="1"><p>Expired messages on a Queue.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the expired id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.Expired.Topic</code></p></td><td colspan="1" rowspan="1"><p>Expired messages on a Topic.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the expired id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><code>none</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.NoConsumer.Queue</code></p></td><td colspan="1" rowspan="1"><p>No consumer is available to process messages being sent on a Queue.</p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>sendAdvisoryIfNoConsumers</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.NoConsumer.Topic</code></p></td><td colspan="1" rowspan="1"><p>No consumer is available to process messages being sent on a Topic.</p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>sendAdvisoryIfNoConsumers</code></p></td></tr></tbody></table><structured-macro ac:macro-id="76e55271-1de0-476c-b8f4-207dc9f3cc7a" ac:name="tip" ac:schema-version="1"><parameter ac:name="title">Tip</parameter><rich-text-body><p><strong><code>NoConsumer</code></strong> topic advisories are sent only for non-persistent messages.</p></rich-text-body></structured-macro><h3>New advisories in version 5.2</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Advisory Topics</p></th><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Properties</p></th><th colspan="1" rowspan="1"><p>Data Structure</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>PolicyEntry Property</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.SlowConsumer.Queue</code></p></td><td colspan="1" rowspan="1"><p>Slow Queue Consumer.</p></td><td colspan="1" rowspan="1"><p><code>String='consumerId'</code> - the consumer id</p></td><td colspan="1" rowspan="1"><p><code>ConsumerInfo</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryForSlowConsumers</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.SlowConsumer.Topic</code></p></td><td colspan="1" rowspan="1"><p>Slow Topic Consumer.</p></td><td colspan="1" rowspan="1"><p><code>String='consumerId'</code> - the consumer id</p></td><td colspan="1" rowspan="1"><p><code>ConsumerInfo</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryForSlowConsumers</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.FastProducer.Queue</code></p></td><td colspan="1" rowspan="1"><p>Fast Queue producer.</p></td><td colspan="1" rowspan="1"><p><code>String='producerId'</code> - the producer id</p></td><td colspan="1" rowspan="1"><p><code>ProducerInfo</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisdoryForFastProducers</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory. FastProducer.Topic</code></p></td><td colspan="1" rowspan="1"><p>Fast Topic producer.</p></td><td colspan="1" rowspan="1"><p><code>String='consumerId'</code>' - the producer id</p></td><td colspan="1" rowspan="1"><p><code>ProducerInfo</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisdoryForFastProducers</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MessageDiscarded.Queue</code></p></td><td colspan="1" rowspan="1"><p>Message discarded.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the discarded id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryForDiscardingMessages</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MessageDiscarded.Topic</code></p></td><td colspan="1" rowspan="1"><p>Message discarded.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the discarded id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryForDiscardingMessages</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MessageDelivered.Queue</code></p></td><td colspan="1" rowspan="1"><p>Message delivered to the broker.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryForDelivery</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MessageDelivered.Topic</code></p></td><td colspan="1" rowspan="1"><p>Message delivered to the broker.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryForDelivery</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MessageConsumed.Queue</code></p></td><td colspan="1" rowspan="1"><p>Message consumed by a client.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryForConsumed</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MessageConsumed.Topic</code></p></td><td colspan="1" rowspan="1"><p>Message consumed by a client.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryForConsumed</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.FULL</code></p></td><td colspan="1" rowspan="1"><p>A Usage resource is at its limit.</p></td><td colspan="1" rowspan="1"><p><code>String='usageName'</code> - the name of Usage resource</p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p><code>advisoryWhenFull</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MasterBroker</code></p></td><td colspan="1" rowspan="1"><p>A broker is now the master in a master/slave configuration.</p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><code>none</code></p></td></tr></tbody></table><h3>New Advisories in 5.4</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Advisory Topics</p></th><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Properties</p></th><th colspan="1" rowspan="1"><p>Data Structure</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>PolicyEntry Property</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MessageDLQd.Queue</code></p></td><td colspan="1" rowspan="1"><p>Message sent to DLQ.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p>Always on</p></td><td colspan="1" rowspan="1"><p><code>advisoryForConsumed</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.MessageDLQd.Topic</code></p></td><td colspan="1" rowspan="1"><p>Message sent to DLQ.</p></td><td colspan="1" rowspan="1"><p><code>String='orignalMessageId'</code> - the delivered id</p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td><td colspan="1" rowspan="1"><p>Always on</p></td><td colspan="1" rowspan="1"><p><code>advisoryForConsumed</code></p></td></tr></tbody></table><h3>Network bridge advisories</h3><p>Starting with ActiveMQ version 5.5 you can watch advisory topics for events related to the status of network bridges. You can get advisory messages when the network bridge is started or stopped.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Advisory Topics</p></th><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Properties</p></th><th colspan="1" rowspan="1"><p>Data Structure</p></th><th colspan="1" rowspan="1"><p>Default</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>ActiveMQ.Advisory.NetworkBridge</code></p></td><td colspan="1" rowspan="1"><p>Network bridge being stopped or started.</p></td><td colspan="1" rowspan="1"><p><code>Boolean="started"</code> - <strong><code>true</code></strong> if bridge is started, <strong><code>false</code></strong> if it is stopped.<br clear="none"><code>Boolean="createdByDuplex"</code> - <strong><code>true</code></strong> if the bridge is created by remote network connector.</p></td><td colspan="1" rowspan="1"><p><code>BrokerInfo</code> - provides data of the remote broker</p></td><td colspan="1" rowspan="1"><p>Always on</p></td></tr></tbody></table><h3>Enabling Advisories Disabled by Default</h3><p>The advisories that are not turned on by default (see the last column) can be enabled on a <strong><code>PolicyEntry</code></strong> in the ActiveMQ Broker Configuration, e.g., to enable a message consumed advisory you can configure the following:</p><structured-macro ac:macro-id="9502ed06-6214-4cb7-aa22-717b7fd2a4a9" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry topic=">" advisoryForConsumed="true"/>
+ <policyEntry topic=">" advisoryForConsumed="true"/>
</policyEntries>
</policyMap>
</destinationPolicy>
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Hint</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The <strong><code>></code></strong> character matches all topics - you can use wild-card matches for setting a destination policy - see <a shape="rect" href="wildcards.xml">Wildcards</a></p></div></div><h3 id="AdvisoryMessage-DisablingAdvisoryMessages">Disabling Advisory Messages</h3><p>The use of advisory messages incurs a small overhead in terms of memory and connection resources that is related to the number of destinations in your system. In some cases it can make sense to disable all advisories.</p><p>Advisories need to be disabled both on the Broker, via XML Configuration</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker advisorySupport="false">
-]]></script>
-</div></div><p>or from java code:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[BrokerService broker = new BrokerService();
+</plain-text-body></structured-macro><structured-macro ac:macro-id="ec51dc63-3e9c-481f-8962-6583fa4f8651" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Hint</parameter><rich-text-body><p>The <strong><code>></code></strong> character matches all topics - you can use wild-card matches for setting a destination policy - see <link><page ri:content-title="Wildcards"></page></link></p></rich-text-body></structured-macro><h3>Disabling Advisory Messages</h3><p>The use of advisory messages incurs a small overhead in terms of memory and connection resources that is related to the number of destinations in your system. In some cases it can make sense to disable all advisories.</p><p>Advisories need to be disabled both on the Broker, via XML Configuration</p><structured-macro ac:macro-id="52656f76-8b75-4ef0-9135-c8522bb3b2d5" ac:name="code" ac:schema-version="1"><plain-text-body><broker advisorySupport="false">
+</plain-text-body></structured-macro><p>or from java code:</p><structured-macro ac:macro-id="ecc0e18b-00a0-468a-b1c0-3179f4e488e2" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><plain-text-body>BrokerService broker = new BrokerService();
broker.setAdvisorySupport(false);
// ...
broker.start();
-]]></script>
-</div></div><p><em>and</em> on your <strong><code>ActiveMQConnectionFactory</code></strong> (because a subscription to an advisory topic will auto create it) via the <strong><code>brokerUrl</code></strong>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tcp://localhost:61616?jms.watchTopicAdvisories=false
-]]></script>
-</div></div><p>or via java code using the <strong><code>watchTopicAdvisories</code></strong> attribute on the <strong><code>ActiveMQConnectionFactory</code></strong>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory();
+</plain-text-body></structured-macro><p><em>and</em> on your <strong><code>ActiveMQConnectionFactory</code></strong> (because a subscription to an advisory topic will auto create it) via the <strong><code>brokerUrl</code></strong>:</p><structured-macro ac:macro-id="5fc78a1d-aa00-4204-9ee7-7c4d2f237104" ac:name="code" ac:schema-version="1"><plain-text-body>tcp://localhost:61616?jms.watchTopicAdvisories=false
+</plain-text-body></structured-macro><p>or via java code using the <strong><code>watchTopicAdvisories</code></strong> attribute on the <strong><code>ActiveMQConnectionFactory</code></strong>.</p><structured-macro ac:macro-id="3778eeca-7501-4303-9374-fda2e63aa39e" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><plain-text-body>ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory();
factory.setWatchTopicAdvisories(false);
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Advisory messages are required for <a shape="rect" href="networks-of-brokers.xml">dynamic network broker topologies</a> as <code>NetworkConnectors</code> subscribe to advisory messages. In the absence of advisories, a network must be statically configured.</p></div></div><h3 id="AdvisoryMessage-UsingtheDestinations">Using the Destinations</h3><p>All of the above destinations are really prefixes which are appended with important information (like the actual topic or queue, the client ID, producer ID, consumer ID etc). This allows you to reuse the power of publish/subscribe, <a shape="rect" href="wildcards.xml">Wildcards</a> and <a shape="rect" href="selectors.xml">Selectors</a> to filter the advisory messages as you see fit.</p><p>For example if you want to subscribe to expired messages on a topic <strong><code>FOO.BAR</code></strong> you could subscribe to <strong><code>ActiveMQ.Advisory.Expired.Topic.FOO.BAR</code></strong>. To subscribe to all messages of a certain kind of advisory just append <strong><code>.></code></strong> to the topic, e.g., to subscribe to all the consumers starting and stopping to topics and queues subscribe to <strong><code>ActiveMQ.Advisory.Consumer..></code></strong>.</p><h3 id="AdvisoryMessage-HelperMethods">Helper Methods</h3><p>Methods to get the advisory destination objects are available in <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/advisory/AdvisorySupport.html">AdvisorySupport</a> through the following methods.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[AdvisorySupport.getConsumerAdvisoryTopic()
+</plain-text-body></structured-macro><structured-macro ac:macro-id="535675d0-77ca-4a56-9600-69cccc65d3cc" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>Advisory messages are required for <link><page ri:content-title="Networks of Brokers"></page><plain-text-link-body>dynamic network broker topologies</plain-text-link-body></link> as <code>NetworkConnectors</code> subscribe to advisory messages. In the absence of advisories, a network must be statically configured.</p></rich-text-body></structured-macro><h3>Using the Destinations</h3><p>All of the above destinations are really prefixes which are appended with important information (like the actual topic or queue, the client ID, producer ID, consumer ID etc). This allows you to reuse the power of publish/subscribe, <link><page ri:content-title="Wildcards"></page></link> and <link><page ri:content-title="Selectors"></page></link> to filter the advisory messages as you see fit.</p><p>For example if you want to subscribe to expired messages on a topic <strong><code>FOO.BAR</code></strong> you could subscribe to <strong><code>ActiveMQ.Advisory.Expired.Topic.FOO.BAR</code></strong>. To subscribe to all messages of a certain kind of advisory just append <strong><code>.></code></strong> to the topic, e.g., to subscribe to all the consumers starting and stopping to topics and queues subscribe to <strong><code>ActiveMQ.Advisory.Consumer..></code></strong>.</p><h3>Helper Methods</h3><p>Methods to get the advisory destination objects are available in <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/advisory/AdvisorySupport.html">AdvisorySupport</a> through the following methods.</p><structured-macro ac:macro-id="11781ec9-61c0-4bb9-bd46-ea59d7e54c35" ac:name="code" ac:schema-version="1"><plain-text-body>AdvisorySupport.getConsumerAdvisoryTopic()
AdvisorySupport.getProducerAdvisoryTopic()
AdvisorySupport.getExpiredTopicMessageAdvisoryTopic()
AdvisorySupport.getExpiredQueueMessageAdvisoryTopic()
@@ -65,6 +50,5 @@
AdvisorySupport.getMessageConsumedAdvisoryTopic()
AdvisorySupport.getMasterBrokerAdvisoryTopic()
AdvisorySupport.getFullAdvisoryTopic()
-]]></script>
-</div></div><p>Some helper classes to deal with advisory messages are available in the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/package-summary.html">advisories</a> package.</p></div>
+</plain-text-body></structured-macro><p>Some helper classes to deal with advisory messages are available in the <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/package-summary.html">advisories</a> package.</p></div>
diff --git a/ajax.xml b/ajax.xml
index 74f33f1..475c3da 100644
--- a/ajax.xml
+++ b/ajax.xml
@@ -1,16 +1,15 @@
-<div class="wiki-content maincontent"><h1 id="Ajax-Introduction">Introduction</h1>
+<div class="wiki-content maincontent"><h1>Introduction</h1>
-<p>ActiveMQ supports <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Ajax_%28programming%29" rel="nofollow">Ajax</a> which is an Asychronous Javascript And Xml mechanism for real time web applications. This means you can create highly real time web applications taking full advantage of the publish/subscribe nature of ActiveMQ</p>
+<p>ActiveMQ supports <a shape="rect" href="http://en.wikipedia.org/wiki/Ajax_%28programming%29">Ajax</a> which is an Asychronous Javascript And Xml mechanism for real time web applications. This means you can create highly real time web applications taking full advantage of the publish/subscribe nature of ActiveMQ</p>
-<p>Ajax allows a regular DHTML client (with JavaScript and a modern version 5 or later web browser) to send and receive messages over the web. Ajax support in ActiveMQ builds on the same basis as the <a shape="rect" href="rest.xml">REST</a> connector for ActiveMQ which allows any web capable device to send or receive messages over JMS.</p>
+<p>Ajax allows a regular DHTML client (with JavaScript and a modern version 5 or later web browser) to send and receive messages over the web. Ajax support in ActiveMQ builds on the same basis as the <link><page ri:content-title="REST"></page></link> connector for ActiveMQ which allows any web capable device to send or receive messages over JMS.</p>
-<p>To see Ajax in action, try <a shape="rect" href="web-samples.xml">running the examples</a></p>
+<p>To see Ajax in action, try <link><page ri:content-title="Web Samples"></page><link-body>running the examples</link-body></link></p>
-<h1 id="Ajax-TheServlet">The Servlet</h1>
+<h1>The Servlet</h1>
<p>The AMQ AjaxServlet needs to be installed in your webapplications to support JMS over Ajax:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="cf8a34e3-339b-4d2e-abcd-14a0b1ec263c" ac:name="code" ac:schema-version="1"><plain-text-body>
...
<servlet>
<servlet-name>AjaxServlet</servlet-name>
@@ -21,110 +20,99 @@
<servlet-name>AjaxServlet</servlet-name>
<url-pattern>/amq/*</url-pattern>
</servlet-mapping>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The servlet both serves the required js files and handles the JMS requests and responses.</p>
-<h1 id="Ajax-JavascriptAPI">Javascript API</h1>
+<h1>Javascript API</h1>
-<p>The ajax featues of amq are provided on the client side by the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/js/amq.js">amq.js</a> script. Beginning with ActiveMQ 5.4, this script utilizes one of three different adapters to support ajax communication with the server. Current <a shape="rect" class="external-link" href="http://jquery.org" rel="nofollow">jQuery</a>, <a shape="rect" class="external-link" href="http://prototypejs.org" rel="nofollow">Prototype</a>, and <a shape="rect" class="external-link" href="http://www.dojotoolkit.org" rel="nofollow">Dojo</a> are supported, and recent versions of all three libraries are shipped with ActiveMQ.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<script type="text/javascript" src="js/jquery-1.4.2.min.js"></script>
-<script type="text/javascript" src="js/amq_jquery_adapter.js"></script>
-<script type="text/javascript" src="js/amq.js"></script>
-<script type="text/javascript">
+<p>The ajax featues of amq are provided on the client side by the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/js/amq.js">amq.js</a> script. Beginning with ActiveMQ 5.4, this script utilizes one of three different adapters to support ajax communication with the server. Current <a shape="rect" href="http://jquery.org">jQuery</a>, <a shape="rect" href="http://prototypejs.org">Prototype</a>, and <a shape="rect" href="http://www.dojotoolkit.org">Dojo</a> are supported, and recent versions of all three libraries are shipped with ActiveMQ.</p>
+<structured-macro ac:macro-id="ea161b97-6cb1-43f7-a745-306923234dd2" ac:name="code" ac:schema-version="1"><plain-text-body>
+<script type="text/javascript" src="js/jquery-1.4.2.min.js"></script>
+<script type="text/javascript" src="js/amq_jquery_adapter.js"></script>
+<script type="text/javascript" src="js/amq.js"></script>
+<script type="text/javascript">
var amq = org.activemq.Amq;
amq.init({
- uri: 'amq',
+ uri: 'amq',
logging: true,
timeout: 20
});
</script>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Including these scripts results in the creation of a javascript object called <code>amq</code>, which provides the API to send messages and to subscribe to channels and topics.</p>
-<h2 id="Ajax-Sendingamessage">Sending a message</h2>
+<h2>Sending a message</h2>
<p>All that is required to send a JMS message from the javascript client, is to call the method:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="8b2d1f60-54ee-4a0f-bc71-dd9306c9cf82" ac:name="code" ac:schema-version="1"><plain-text-body>
amq.sendMessage(myDestination,myMessage);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>where <code>myDestination</code> is the URL string address of the destination (e.g. "topic://MY.NAME" or "channel://MY.NAME") and <code>myMessage</code> is any well formed XML or plain text encoded as XML content.</p>
-<h2 id="Ajax-Receivingmessages">Receiving messages</h2>
+<h2>Receiving messages</h2>
-<p>To receive messages, the client must define a message handling function and register it with the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/js/amq.js">amq</a> object. For example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>To receive messages, the client must define a message handling function and register it with the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/js/amq.js">amq</a> object. For example:</p>
+<structured-macro ac:macro-id="a977b685-ac94-4ee9-847d-a46f1e798cff" ac:name="code" ac:schema-version="1"><plain-text-body>
var myHandler =
{
rcvMessage: function(message)
{
- alert("received "+message);
+ alert("received "+message);
}
};
amq.addListener(myId,myDestination,myHandler.rcvMessage);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>where <code>myId</code> is a string identifier that can be used for a later call to <code>amq.removeHandler(myId)</code> and <code>myDestination</code> is a URL string address of the destination (e.g. "topic://MY.NAME" or "channel://MY.NAME"). When a message is received, a call back to the <code>myHandler.rcvMessage</code> function passes the message to your handling code.<br clear="none">
The "message" is actually a text of the Text message or a String representation (<code>toString()</code>) in case of Object messages.</p>
-<p>Be aware that, by default, messages published via <a shape="rect" class="external-link" href="http://activemq.apache.org/stomp.html">Stomp</a> which include a <code>content-length</code> header will be converted by ActiveMQ to binary messages, and will not be visible to your web clients. Beginning with ActiveMQ 5.4.0, you can resolve this problem by always setting the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-2833"><code>amq-msg-type</code> header</a> to <code>text</code> in messages which will may be consumed by web clients.</p>
+<p>Be aware that, by default, messages published via <a shape="rect" href="http://activemq.apache.org/stomp.html">Stomp</a> which include a <code>content-length</code> header will be converted by ActiveMQ to binary messages, and will not be visible to your web clients. Beginning with ActiveMQ 5.4.0, you can resolve this problem by always setting the <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-2833"><code>amq-msg-type</code> header</a> to <code>text</code> in messages which will may be consumed by web clients.</p>
-<h3 id="Ajax-Selectorsupport">Selector support</h3>
+<h3>Selector support</h3>
-<p>By default, an ajax client will receive all messages on a topic or queue it is subscribed to. In <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-541-release.html">ActiveMQ 5.4.1</a> amq.js supports <a shape="rect" class="external-link" href="http://activemq.apache.org/selectors.html">JMS selectors</a> since it is frequently useful to receive only a subset of these messages. Selectors are supplied to an <code>amq.addListener</code> call by way of an optional 4th parameter.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-amq.addListener( myId, myDestination, myHandler.rcvMessage, { selector:"identifier='TEST'" } );
-]]></script>
-</div></div>
+<p>By default, an ajax client will receive all messages on a topic or queue it is subscribed to. In <a shape="rect" href="http://activemq.apache.org/activemq-541-release.html">ActiveMQ 5.4.1</a> amq.js supports <a shape="rect" href="http://activemq.apache.org/selectors.html">JMS selectors</a> since it is frequently useful to receive only a subset of these messages. Selectors are supplied to an <code>amq.addListener</code> call by way of an optional 4th parameter.</p>
+<structured-macro ac:macro-id="d3cf34a9-2e36-44e3-8610-62926d13eb50" ac:name="code" ac:schema-version="1"><plain-text-body>
+amq.addListener( myId, myDestination, myHandler.rcvMessage, { selector:"identifier='TEST'" } );
+</plain-text-body></structured-macro>
<p>When used in this way, the Javascript client will receive only messages containing an <code>identifier</code> header set to the value <code>TEST</code>.</p>
-<h2 id="Ajax-UsingAMQAjaxinMultipleBrowserWindows">Using AMQ Ajax in Multiple Browser Windows</h2>
+<h2>Using AMQ Ajax in Multiple Browser Windows</h2>
-<p>All windows or tabs in a single browser share the same <code>JSESSIONID</code> on the ActiveMQ server. Unless the server can distinguish listeners from multiple windows, messages which were intended for 1 window will be delivered to another one instead. Effectively, this means that amq.js could be active in only a single browser window at any given time. Beginning in <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-542-release.html">ActiveMQ 5.4.2</a>, this is resolved by allowing each call to <code>amq.init</code> to specify a unique <code>clientId</code>. When this is done, multiple windows in the same browser can happily co-exist. Each can have a separate set of message subscriptions on the broker with no interactions between them.</p>
+<p>All windows or tabs in a single browser share the same <code>JSESSIONID</code> on the ActiveMQ server. Unless the server can distinguish listeners from multiple windows, messages which were intended for 1 window will be delivered to another one instead. Effectively, this means that amq.js could be active in only a single browser window at any given time. Beginning in <a shape="rect" href="http://activemq.apache.org/activemq-542-release.html">ActiveMQ 5.4.2</a>, this is resolved by allowing each call to <code>amq.init</code> to specify a unique <code>clientId</code>. When this is done, multiple windows in the same browser can happily co-exist. Each can have a separate set of message subscriptions on the broker with no interactions between them.</p>
-<p>In this example, we use the current time (at the time the web page is loaded) as a unique identifier. This is effective as long as two browser windows are not opened within the same millisecond, and is the approach used by the example <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/chat.html">chat.html</a> included with ActiveMQ. Other schemes to ensure the uniqueness of <code>clientId</code> can easily be devised. Note that this <code>clientId</code> need only be unique within a single session. (Browser windows opened in the same millisecond in separate browsers will not interact, since they are in different sessions.)</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>In this example, we use the current time (at the time the web page is loaded) as a unique identifier. This is effective as long as two browser windows are not opened within the same millisecond, and is the approach used by the example <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/chat.html">chat.html</a> included with ActiveMQ. Other schemes to ensure the uniqueness of <code>clientId</code> can easily be devised. Note that this <code>clientId</code> need only be unique within a single session. (Browser windows opened in the same millisecond in separate browsers will not interact, since they are in different sessions.)</p>
+<structured-macro ac:macro-id="0bed7262-f3fb-4f5b-8df6-0036f4e9432c" ac:name="code" ac:schema-version="1"><plain-text-body>
org.activemq.Amq.init({
- uri: 'amq',
+ uri: 'amq',
logging: true,
timeout: 45,
clientId:(new Date()).getTime().toString()
});
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Note that this <code>clientId</code> is common to all message subscriptions in a single tab or window, and is entirely different from the <code>clientId</code> which is supplied as a first argument in <code>amq.addListener</code> calls.</p>
<ul><li>In <code>amq.init</code>, <code>clientId</code> serves to distinguish different web clients sharing the same <code>JSESSIONID</code>. All windows in a single browser need a unique <code>clientId</code> when they call <code>amq.init</code>.</li><li>In <code>amq.addListener</code>, <code>clientId</code> is used to associate a message subscription with the callback function which should be invoked when a message is received for that subscription. These <code>clientId</code> values are internal to each web page, and do not need to be unique across multiple windows or tabs.</li></ul>
-<h1 id="Ajax-Howitworks">How it works</h1>
+<h1>How it works</h1>
-<h2 id="Ajax-AjaxServletandMessageListenerServlet">AjaxServlet and MessageListenerServlet</h2>
+<h2>AjaxServlet and MessageListenerServlet</h2>
-<p>The ajax featues of amq are handled on the server side by the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web/src/main/java/org/apache/activemq/web/AjaxServlet.java">AjaxServlet</a> which extends the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web/src/main/java/org/apache/activemq/web/MessageListenerServlet.java">MessageListenerServlet</a>. This servlet is responsible for tracking the existing clients (using a HttpSesssion) and lazily creating the AMQ and javax.jms objects required by the client to send and receive messages (eg. Destination, MessageConsumer, MessageAVailableListener). This servlet should be mapped to <code>/amq/*</code> in the web application context serving the Ajax client (this can be changed, but the client javascript <code>amq.uri</code> field needs to be updated to match.)</p>
+<p>The ajax featues of amq are handled on the server side by the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web/src/main/java/org/apache/activemq/web/AjaxServlet.java">AjaxServlet</a> which extends the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web/src/main/java/org/apache/activemq/web/MessageListenerServlet.java">MessageListenerServlet</a>. This servlet is responsible for tracking the existing clients (using a HttpSesssion) and lazily creating the AMQ and javax.jms objects required by the client to send and receive messages (eg. Destination, MessageConsumer, MessageAVailableListener). This servlet should be mapped to <code>/amq/*</code> in the web application context serving the Ajax client (this can be changed, but the client javascript <code>amq.uri</code> field needs to be updated to match.)</p>
-<h2 id="Ajax-ClientSendingmessages">Client Sending messages</h2>
+<h2>Client Sending messages</h2>
-<p>When a message is sent from the client it is encoded as the content of a POST request, using the API of one of the supported connection adapters (jQuery, Prototype, or Dojo) for <a shape="rect" class="external-link" href="http://jibbering.com/2002/4/httprequest.html" rel="nofollow">XmlHttpRequest</a>. The <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/js/amq.js">amq</a> object may combine several sendMessage calls into a single POST if it can do so without adding additional delays (see polling below).</p>
+<p>When a message is sent from the client it is encoded as the content of a POST request, using the API of one of the supported connection adapters (jQuery, Prototype, or Dojo) for <a shape="rect" href="http://jibbering.com/2002/4/httprequest.html">XmlHttpRequest</a>. The <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/src/main/webapp/js/amq.js">amq</a> object may combine several sendMessage calls into a single POST if it can do so without adding additional delays (see polling below).</p>
<p>When the MessageListenerServlet receives a POST, the messages are decoded as <code>application/x-www-form-urlencoded</code> parameters with their type (in this case <code>send</code> as opposed to <code>listen</code> or <code>unlisten</code> see below) and destination. If a destination channel or topic do not exist, it is created. The message is sent to the destination as a TextMessage.</p>
-<h2 id="Ajax-Listeningformessages">Listening for messages</h2>
+<h2>Listening for messages</h2>
<p>When a client registers a listener, a message subscription request is sent from the client to the server in a POST in the same way as a message, but with a type of <code>listen</code>. When the MessageListenerServlet receives a <code>listen</code> message, it lazily creates a MessageAvailableConsumer and registers a Listener on it.</p>
-<h2 id="Ajax-WaitingPollformessages">Waiting Poll for messages</h2>
+<h2>Waiting Poll for messages</h2>
<p>When a Listener created by the MessageListenerServlet is called to indicate that a message is available, due to the limitations of the HTTP client-server model, it is not possible to send that message directly to the ajax client. Instead the client must perform a special type of <strong>Poll</strong> for messages. Polling normally means periodically making a request to see if there are messages available and there is a trade off: either the poll frequency is high and excessive load is generated when the system is idle; or the frequency is low and the latency for detecting new messages is high.</p>
@@ -140,11 +128,11 @@
<p>The client is able to asynchronously send a message to the server by creating (or using an existing) second connection to the server. However, during the processing of the poll response, normal client message sending is suspended, so that all messages to be sent are queued and sent as a single POST with the poll that will be sent (with no delay) at the end of the processing. This ensures that only two connections are required between client and server (the normal for most browsers).</p>
-<h2 id="Ajax-ThreadlessWaiting">Threadless Waiting</h2>
+<h2>Threadless Waiting</h2>
-<p>The waiting poll described above is implemented using the <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Continuations" rel="nofollow">Jetty 6 Continuations</a> mechanism. This allows the thread associated with the request to be released during the wait, so that the container does not need to have a thread per client (which may be a large number). If another servlet container is used, the Continuation mechanism falls back to use a wait and the thread is not released.</p>
+<p>The waiting poll described above is implemented using the <a shape="rect" href="http://docs.codehaus.org/display/JETTY/Continuations">Jetty 6 Continuations</a> mechanism. This allows the thread associated with the request to be released during the wait, so that the container does not need to have a thread per client (which may be a large number). If another servlet container is used, the Continuation mechanism falls back to use a wait and the thread is not released.</p>
-<h1 id="Ajax-ComparisontoPushlets">Comparison to Pushlets</h1>
+<h1>Comparison to Pushlets</h1>
<p>Firstly we could easily add support for pushlets to ActiveMQ. However we prefer the Ajax approach for various reasons</p>
<ul><li>using Ajax means that we use a distinct HTTP request for each send/receive which is much more friendly to web infrastructure (firewalls, proxies, caches and so forth) rather than having an infinitely-long GET.</li></ul>
@@ -165,5 +153,6 @@
<ul><li>pushlets assume the server knows what functions are used on the client side as the server basically writes JavaScript function calls down the scoket - it's better for us to send generic XML packets (or strings or whatever the message format is) and let the JavaScript client side be totally decoupled from the server side</li></ul>
-<ul><li>Ajax supports clean XML support allowing full XML documents to be streamed to the client for rich messages which are easy to process via standard JavaScript DOM support</li></ul></div>
+<ul><li>Ajax supports clean XML support allowing full XML documents to be streamed to the client for rich messages which are easy to process via standard JavaScript DOM support</li></ul>
+</div>
diff --git a/all-forums.xml b/all-forums.xml
index 1f979a9..9496f55 100644
--- a/all-forums.xml
+++ b/all-forums.xml
@@ -1,5 +1,5 @@
-<div class="wiki-content maincontent"><p>
-<a shape="rect" id="nabblelink" href="http://www.nabble.com/ActiveMQ-f2354.html">ActiveMQ</a>
-<script src="http://www.nabble.com/embed/f2354"></script>
-</p><p></p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="142a1ce5-7f1e-4ba8-956a-a28c34d2732a" ac:name="html" ac:schema-version="1"><plain-text-body>
+<a id="nabblelink" href="http://www.nabble.com/ActiveMQ-f2354.html">ActiveMQ</a>
+<script src="http://www.nabble.com/embed/f2354"></script>
+</plain-text-body></structured-macro></p><p></p></div>
diff --git a/amq-message-store.xml b/amq-message-store.xml
index 4ec1613..a9e7bed 100644
--- a/amq-message-store.xml
+++ b/amq-message-store.xml
@@ -1,76 +1,74 @@
-<div class="wiki-content maincontent"><h2 id="AMQMessageStore-TheBasics">The Basics</h2>
+<div class="wiki-content maincontent"><h2>The Basics</h2>
<p>This is the default storage for AcitveMQ 5 and above. The AMQ Message Store is an embeddable transactional message storage solution that is extremely fast and reliable.<br clear="none">
message commands are written to a transactional journal - which consists of rolling data logs - which means writing is extremely fast and the state of the store is easily recoverable.</p>
<p>Messages themselves are persisted in the data logs of the journal - with references to their location being held by a reference store (by default Kaha) for fast retrevial.</p>
-<div class="sectionColumnWrapper"><div class="sectionMacro">
-<div class="sectionMacroRow"><div class="columnMacro" style="width:50%;min-width:50%;max-width:50%;">
-<p><span class="confluence-embedded-file-wrapper image-left-wrapper"><img class="confluence-embedded-image image-left" src="amq-message-store.data/amqstore.png" data-image-src="/confluence/download/attachments/69705/amqstore.png?version=1&modificationDate=1193701758000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59670904" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="amqstore.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="69705" data-linked-resource-container-version="21"></span></p></div>
-<div class="columnMacro" style="width:50%;min-width:50%;max-width:50%;">
+<structured-macro ac:macro-id="7b4e09fb-98ad-415f-948f-997829c0c1e0" ac:name="section" ac:schema-version="1"><rich-text-body>
+<structured-macro ac:macro-id="0723c06c-d5db-4d8f-abc1-61861fe50ad6" ac:name="column" ac:schema-version="1"><parameter ac:name="width">50%</parameter><rich-text-body>
+<p><image ac:align="left"><attachment ri:filename="amqstore.png"></attachment></image></p></rich-text-body></structured-macro>
+<structured-macro ac:macro-id="84ca978d-31f3-486b-a66f-851f790e124e" ac:name="column" ac:schema-version="1"><parameter ac:name="width">50%</parameter><rich-text-body>
<p><br clear="none" class="atl-forced-newline">
<br clear="none" class="atl-forced-newline">
<br clear="none" class="atl-forced-newline">
References to messages are held in memory, and periodically inserted into the reference store to improve performance.
<br clear="none" class="atl-forced-newline">
<br clear="none" class="atl-forced-newline">
-The messages are stored in data logs, which are individual files, typically 32mb in size (though this is configurable, they can be larger if the size of a message is large than the file size). When all the messages in a data log have been successfully consumed, the data log file is marked as being ready to be deleted - or archived - which will happen at the next clean up period.</p></div>
-</div></div></div>
+The messages are stored in data logs, which are individual files, typically 32mb in size (though this is configurable, they can be larger if the size of a message is large than the file size). When all the messages in a data log have been successfully consumed, the data log file is marked as being ready to be deleted - or archived - which will happen at the next clean up period.</p></rich-text-body></structured-macro>
+</rich-text-body></structured-macro>
-<h2 id="AMQMessageStore-Configuration">Configuration</h2>
+<h2>Configuration</h2>
<p>By default ActiveMQ will use the the AMQ Store - and its default settings. You can configure the properties of the AMQ Store however, by explictly defining its persistence adapter (amqPersistenceAdapter):</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <broker brokerName="broker" persistent="true" useShutdownHook="false">
+<structured-macro ac:macro-id="2c5bea15-0e72-4a54-87da-44e58c3c6f55" ac:name="code" ac:schema-version="1"><plain-text-body>
+ <broker brokerName="broker" persistent="true" useShutdownHook="false">
<persistenceAdapter>
- <amqPersistenceAdapter directory="${activemq.base}/activemq-data" maxFileLength="32mb"/>
+ <amqPersistenceAdapter directory="${activemq.base}/activemq-data" maxFileLength="32mb"/>
</persistenceAdapter>
<transportConnectors>
- <transportConnector uri="tcp://localhost:61616"/>
+ <transportConnector uri="tcp://localhost:61616"/>
</transportConnectors>
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The above shows the configuration required to set the AMQ Store through its amqPersistenceAdapter - and explicity setting the directory and maxFileLength properties.</p>
-<h3 id="AMQMessageStore-AMQStoreProperties">AMQ Store Properties</h3>
+<h3>AMQ Store Properties</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>directory</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>activemq-data</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the path to the directory to use to store the message store data and log files</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useNIO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>use NIO to write messages to the data logs</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>syncOnWrite</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>sync every write to disk</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxFileLength</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>32mb</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>a hint to set the maximum size of the message data logs</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>persistentIndex</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>use a persistent index for the message logs. If this is false, an in-memory structure is maintained</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxCheckpointMessageAddSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>4kb</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the maximum number of messages to keep in a transaction before automatically committing</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>cleanupInterval</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>time (ms) before checking for a discarding/moving message data logs that are no longer used</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexBinSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1024</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>default number of bins used by the index. The bigger the bin size - the better the relative performance of the index</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexKeySize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>96</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the size of the index key - the key is the message id </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexPageSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>16kb</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the size of the index page - the bigger the page - the better the write performance of the index </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>directoryArchive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>archive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the path to the directory to use to store discarded data logs</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>archiveDataLogs</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if true data logs are moved to the archive directory instead of being deleted</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1"><p>directory</p></td><td colspan="1" rowspan="1"><p>activemq-data</p></td><td colspan="1" rowspan="1"><p>the path to the directory to use to store the message store data and log files</p></td></tr><tr><td colspan="1" rowspan="1"><p>useNIO</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>use NIO to write messages to the data logs</p></td></tr><tr><td colspan="1" rowspan="1"><p>syncOnWrite</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>sync every write to disk</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxFileLength</p></td><td colspan="1" rowspan="1"><p>32mb</p></td><td colspan="1" rowspan="1"><p>a hint to set the maximum size of the message data logs</p></td></tr><tr><td colspan="1" rowspan="1"><p>persistentIndex</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>use a persistent index for the message logs. If this is false, an in-memory structure is maintained</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxCheckpointMessageAddSize</p></td><td colspan="1" rowspan="1"><p>4kb</p></td><td colspan="1" rowspan="1"><p>the maximum number of messages to keep in a transaction before automatically committing</p></td></tr><tr><td colspan="1" rowspan="1"><p>cleanupInterval</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>time (ms) before checking for a discarding/moving message data logs that are no longer used</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexBinSize</p></td><td colspan="1" rowspan="1"><p>1024</p></td><td colspan="1" rowspan="1"><p>default number of bins used by the index. The bigger the bin size - the better the relative performance of the index</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexKeySize</p></td><td colspan="1" rowspan="1"><p>96</p></td><td colspan="1" rowspan="1"><p>the size of the index key - the key is the message id </p></td></tr><tr><td colspan="1" rowspan="1"><p>indexPageSize</p></td><td colspan="1" rowspan="1"><p>16kb</p></td><td colspan="1" rowspan="1"><p>the size of the index page - the bigger the page - the better the write performance of the index </p></td></tr><tr><td colspan="1" rowspan="1"><p>directoryArchive</p></td><td colspan="1" rowspan="1"><p>archive</p></td><td colspan="1" rowspan="1"><p>the path to the directory to use to store discarded data logs</p></td></tr><tr><td colspan="1" rowspan="1"><p>archiveDataLogs</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>if true data logs are moved to the archive directory instead of being deleted</p></td></tr></tbody></table>
-<h2 id="AMQMessageStore-DataStructure">Data Structure</h2>
+<h2>Data Structure</h2>
<p>In the data directory defined for the AMQ Store there is the following directory structure:</p>
-<div class="sectionColumnWrapper"><div class="sectionMacro">
-<div class="sectionMacroRow"><div class="columnMacro" style="width:50%;min-width:50%;max-width:50%;">
-<p><span class="confluence-embedded-file-wrapper image-left-wrapper"><img class="confluence-embedded-image image-left" src="amq-message-store.data/amqdir.png" data-image-src="/confluence/download/attachments/69705/amqdir.png?version=1&modificationDate=1193927867000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59670910" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="amqdir.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="69705" data-linked-resource-container-version="21"></span></p></div>
-<div class="columnMacro" style="width:50%;min-width:50%;max-width:50%;">
-<h3 id="AMQMessageStore-Toplevel">Top level</h3>
+<structured-macro ac:macro-id="7a6c812e-6ce6-4a10-a407-abe98d623408" ac:name="section" ac:schema-version="1"><rich-text-body>
+<structured-macro ac:macro-id="acd7fd4d-13a5-4cdb-a62e-0d91765ed0d6" ac:name="column" ac:schema-version="1"><parameter ac:name="width">50%</parameter><rich-text-body>
+<p><image ac:align="left"><attachment ri:filename="amqdir.png"></attachment></image></p></rich-text-body></structured-macro>
+<structured-macro ac:macro-id="51bcef4f-c3cf-41ad-b525-016965a64462" ac:name="column" ac:schema-version="1"><parameter ac:name="width">50%</parameter><rich-text-body>
+<h3>Top level</h3>
<p>the message broker's name is used to distinguish its directory of message data. By default, the broker name is local host.<br clear="none">
Below this top level directory are the following sub directories:</p>
-<h3 id="AMQMessageStore-archive">archive</h3>
+<h3>archive</h3>
<p>message data logs are moved here when they are discarded.<br clear="none">
n.b. this directory only exists when the property archiveDataLogs is enabled</p>
-<h3 id="AMQMessageStore-journal">journal</h3>
+<h3>journal</h3>
<p>Used to hold the message data logs</p>
-<h3 id="AMQMessageStore-kr-store">kr-store</h3>
+<h3>kr-store</h3>
<p>The directory structure of the Kaha reference store (if used)</p>
-<h5 id="AMQMessageStore-data">data</h5>
+<h5>data</h5>
<p>The indexes used to reference the message data logs in the journal for fast retrieval</p>
-<h5 id="AMQMessageStore-state">state</h5>
-<p>The state of the store - i.e. names of durable subscribers - the reason for this is described in <a shape="rect" href="#AMQMessageStore-Recovery">Recovery</a></p>
-<h3 id="AMQMessageStore-tmp-storage">tmp-storage</h3>
-<p>use to hold data files for transient messages that may be stored on disk to alleviate memory consumption - e.g. non-persistent topic messages awaiting delivery to an active, but slow subscriber.</p></div></div></div></div>
+<h5>state</h5>
+<p>The state of the store - i.e. names of durable subscribers - the reason for this is described in <link ac:anchor="Recovery"><link-body>Recovery</link-body></link></p>
+<h3>tmp-storage</h3>
+<p>use to hold data files for transient messages that may be stored on disk to alleviate memory consumption - e.g. non-persistent topic messages awaiting delivery to an active, but slow subscriber.</p></rich-text-body></structured-macro></rich-text-body></structured-macro>
-<h2 id="AMQMessageStore-Recovery">Recovery</h2>
+<h2>Recovery</h2>
<p>If the message broker does not shutdown properly, then the reference store indexes are cleaned and the message data files (which contain messages/acknowledgements and transactional boundaries) are replayed to rebuild up the message store state. It is possbile to force automatic recovery if using the Kaha reference store (the default) by deleting the kr-store/state/ directory.</p></div>
diff --git a/amqp.xml b/amqp.xml
index a3751ff..157d1e2 100644
--- a/amqp.xml
+++ b/amqp.xml
@@ -1,20 +1,8 @@
-<div class="wiki-content maincontent"><p>ActiveMQ supports the <a shape="rect" class="external-link" href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp" rel="nofollow">AMQP 1.0</a> protocol which is an OASIS standard.</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Availability</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Available from ActiveMQ version <a shape="rect" href="activemq-580-release.xml">5.8</a> onward.</p></div></div><h3 id="AMQP-EnablingtheActiveMQBrokerforAMQP">Enabling the ActiveMQ Broker for AMQP</h3><p>To enable AMQP protocol support on the broker add the following transport connector configuration referencing the <strong><code>amqp</code></strong> scheme in its URI:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnectors>
- <transportConnector name="amqp" uri="amqp://0.0.0.0:5672"/>
+<div class="wiki-content maincontent"><p>ActiveMQ supports the <a shape="rect" href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp">AMQP 1.0</a> protocol which is an OASIS standard.</p><structured-macro ac:macro-id="f7ac2108-fc07-4918-880f-69a75f359248" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Availability</parameter><rich-text-body><p>Available from ActiveMQ version <link><page ri:content-title="ActiveMQ 5.8.0 Release"></page><plain-text-link-body>5.8</plain-text-link-body></link> onward.</p></rich-text-body></structured-macro><h3>Enabling the ActiveMQ Broker for AMQP</h3><p>To enable AMQP protocol support on the broker add the following transport connector configuration referencing the <strong><code>amqp</code></strong> scheme in its URI:</p><structured-macro ac:macro-id="ef3fdf06-2ed8-4cff-8c83-850e28ce1eca" ac:name="code" ac:schema-version="1"><plain-text-body><transportConnectors>
+ <transportConnector name="amqp" uri="amqp://0.0.0.0:5672"/>
</transportConnectors>
-]]></script>
-</div></div><p>It is enabled in the default ActiveMQ server configuration. For more help see <a shape="rect" href="run-broker.xml">Run Broker</a>.</p><h3 id="AMQP-Security">Security</h3><p>The AMQP implementation fully supports an <a shape="rect" href="security.xml">ActiveMQ security</a> mechanism. This allows the broker to accept plain SASL authentication. Authorization policies are applied to a destination when it's accessed (read/write).</p><div class="confluence-information-macro confluence-information-macro-tip"><p class="title">SSL</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>For additional security AMQP can be configured to run over SSL as described in the following section.</p></div></div><h3 id="AMQP-EnablingAMQPoverNIO">Enabling AMQP over NIO</h3><p>For better scalability (and performance) the AMQP protocol should be configured to use NIO, rather than the default of TCP. To use NIO use the transport scheme <strong><code>amqp+nio</code></strong> instead of <strong><code>amqp</code></strong>.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="amqp+nio" uri="amqp+nio://localhost:5672"/>
-]]></script>
-</div></div><p>This transport uses the <a shape="rect" class="external-link" href="http://activemq.apache.org/configuring-transports.html#ConfiguringTransports-TheNIOTransport">NIO transport</a> underneath and will generally use much less threads than the standard connector. This connector can help if you want to use <a shape="rect" class="external-link" href="http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html">large number of queues</a></p><h3 id="AMQP-EnablingAMQPoverSSL">Enabling AMQP over SSL</h3><p>It's easy to configure ActiveMQ to use AMQP over a SSL connection. To use SSL use the transport scheme <strong><code>amqp+ssl</code></strong> instead of <strong><code>amqp</code></strong>.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="amqp+ssl" uri="amqp+ssl://localhost:5671"/>
-]]></script>
-</div></div><p>For more details on using SSL with ActiveMQ, see the following article (<a shape="rect" class="external-link" href="http://activemq.apache.org/how-do-i-use-ssl.html">How do I use SSL</a>).</p><h3 id="AMQP-WorkingwithDestinationswithAMQP">Working with Destinations with AMQP</h3><p>You should prefix destination address with <strong><code>queue://</code></strong> to use queue based destinations or <strong><code>topic://</code></strong> to use topic based destinations. The destination type defaults to queue when the destination prefix is omitted.</p><h3 id="AMQP-PrefetchSizeandCredit">Prefetch Size and Credit</h3><p>When AMQP receiver connects to the broker it's mapped to the JMS consumer. This JMS consumer has to have appropriate <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch size</a> set. <span style="line-height: 1.4285715;">The broker will honor the credit set by the client or use the default value of <strong><code>1000</code></strong> if client doesn't set it.</span></p><p>Example: tuning the default <strong><code>prefetch</code></strong> size:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600&amp;transport.prefetch=10"/>]]></script>
-</div></div><p class="p1">In this case, client preference will be ignored and the configured value will be used.</p><p class="p1">You can also tune broker-side <strong><code>amqp</code></strong> receiver link that handles incoming messages. It will use credit of <strong><code>1000</code></strong> messages by default, but you can override this by using <span><strong><code>producerCredit</code></strong> property, like </span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600&amp;transport.producerCredit=10000"/>]]></script>
-</div></div><h3 id="AMQP-MappingtoJMS">Mapping to JMS</h3><p>There are three basic conversion strategies that can be used with AMQP and inter-operating with the JMS API.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Strategy</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>native</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(<strong>Default</strong>) Wraps the bytes of the AMQP message into a JMS <strong><code>BytesMessage</code></strong> and maps the headers of the AMQP message to headers on the JMS message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>raw</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Wraps the bytes of the AMQP message into a JMS <strong><code>BytesMessage</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jms</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Maps headers of the AMQP message to JMS message headers and the body of the AMQP message to the JMS body.</p></td></tr></tbody></table></div><p>Set the <strong>transformer</strong> transport option on the <strong><code>transportConnector</code></strong> to the desired mapping strategy. For example, to inter-operate with JMS at the payload level, set the <strong><code>transformer</code></strong> option to <strong><code>jms</code></strong>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="amqp" uri="amqp://localhost:5672?transport.transformer=jms"/>
-]]></script>
-</div></div><h4 id="AMQP-HowAMQPMessageHeadersareMappedtoJMSHeaders">How AMQP Message Headers are Mapped to JMS Headers</h4><p>The following headers are mapped regardless of the transformer used:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>AMQP Message</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>JMS Message</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Notes</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_NATIVE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will be set to <strong><code>true</code></strong> if the transformer is <strong><code>native</code></strong> or <strong><code>raw</code></strong>, <strong><code>false</code></strong> otherwise.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>message-format</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_MESSAGE_FORMAT</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr></tbody></table></div><p>The following header mappings apply when the transformer is either <strong><code>native</code></strong> or <strong><code>jms</code></strong>:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>AMQP Message</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>JMS Message</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Notes</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>application-properties.JMSXGroupID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>application-properties.JMSXGroupSequence</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupSequence</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>application-properties.JMSXUserID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXUserID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>application-properties.<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><u><strong><code>name</code></strong></u></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>delivery-annotations.<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_DA_<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>footer.<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_FT_<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>header.deliveryCount</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXDeliveryCount</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>header.durable</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSDeliveryMode</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>javax.jms.Message.DEFAULT_DELIVERY_MODE</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>header.first-acquirer</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_FirstAcquirer</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>header.priority</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSPriority</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>javax.jms.Message.DEFAULT_PRIORITY</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>header.ttl</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSExpiration</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>javax.jms.Message.DEFAULT_TIME_TO_LIVE</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>message-annotations.<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_MA_<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>message-annotations.x-opt-jms-type</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSType</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>message-annotations.x-opt-reply-type</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Type of the <code>JMSReplyTo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Comma separated list of <strong><code>queue</code></strong>, <strong><code>topic</code></strong>, or <strong><code>temporary</code></strong>. Defaults to <strong><code>queue</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>message-annotations.x-opt-to-type</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Type of the <code>JMSDestination</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Comma separated list of <strong><code>queue</code></strong>, <strong><code>topic</code></strong>, or <strong><code>temporary</code></strong>. Defaults to <strong><code>queue</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.content-encoding</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_ContentEncoding</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.content-type</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_ContentType</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.correlation-id</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSCorrelationID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.creation-time</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSTimestamp</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.group-sequence</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupSequence</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.message-id</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSMessageID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Auto generated if not set.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.reply-to</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSReplyTo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <strong><code>JMSReplyTo</code></strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.reply-to-group-id</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_ReplyToGroupID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.subject</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMS_AMQP_Subject</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.to</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSDestination</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <strong><code>JMSDestination</code></strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>properties.user-id</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXUserID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>properties.user-id</code></strong> is decoded as a UTF-8 String.</p></td></tr></tbody></table></div><p> </p><p>AMQP property value types are converted as follows:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>AMQP Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Java Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Notes</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>binary</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Hex encoding of the binary value</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>bool</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>byte</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Byte</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>double</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Double</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>float</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Float</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Integer</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>long</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Long</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>short</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Short</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>symbol</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ubyte</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Byte</code> or <code>Short</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>Short</code></strong> is used if: <strong><code>value ></code></strong> <strong><code>Byte.MAX_VALUE</code></strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>uint</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Integer</code> or <code>Long</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>Long</code></strong> is used if: <strong><code>value ></code></strong> <strong><code>Integer.MAX_VALUE</code></strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ulong</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Long</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ushort</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Short</code> or <code>Integer</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>Integer</code></strong> is used if: <strong><code>value ></code></strong> <strong><code>Short.MAX_VALUE</code></strong></p></td></tr></tbody></table></div><h4 id="AMQP-HowaAMQPMessagesBodyisMappedtoaJMSMessage">How a AMQP Messages Body is Mapped to a JMS Message</h4><p>If the transformer is set to <strong><code>jms</code></strong> then the JMS message type will depend on the body type of the AMQP message.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Body Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>JMS Message Type</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>AmqpSequence</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>StreamMessage</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>AmqpValue</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ObjectMessage</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>AmqpValue</code> holding a <code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>AmqpValue</code> holding a <code>String</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>TextMessage</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>AmqpValue</code> holding a <code>binary</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>BytesMessage</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>AmqpValue</code> holding a <code>list</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>StreamMessage</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Data</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>BytesMessage</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Message</code></p></td></tr></tbody></table></div><h3 id="AMQP-AMQP1.0clientlibrary">AMQP 1.0 client library</h3><p>You can use <a shape="rect" class="external-link" href="http://qpid.apache.org/proton/">Apache Qpid Proton</a>.</p></div>
+</plain-text-body></structured-macro><p>It is enabled in the default ActiveMQ server configuration. For more help see <link><page ri:content-title="Run Broker"></page></link>.</p><h3>Security</h3><p>The AMQP implementation fully supports an <link><page ri:content-title="Security"></page><plain-text-link-body>ActiveMQ security</plain-text-link-body></link> mechanism. This allows the broker to accept plain SASL authentication. Authorization policies are applied to a destination when it's accessed (read/write).</p><structured-macro ac:macro-id="23a9920d-bead-4048-9614-45d166255570" ac:name="tip" ac:schema-version="1"><parameter ac:name="title">SSL</parameter><rich-text-body><p>For additional security AMQP can be configured to run over SSL as described in the following section.</p></rich-text-body></structured-macro><h3>Enabling AMQP over NIO</h3><p>For better scalability (and performance) the AMQP protocol should be configured to use NIO, rather than the default of TCP. To use NIO use the transport scheme <strong><code>amqp+nio</code></strong> instead of <strong><code>amqp</code></strong>.</p><p>Example:</p><structured-macro ac:macro-id="0ab55b1f-ee01-434f-82d9-e009f1c68625" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnector name="amqp+nio" uri="amqp+nio://localhost:5672"/>
+</plain-text-body></structured-macro><p>This transport uses the <a shape="rect" href="http://activemq.apache.org/configuring-transports.html#ConfiguringTransports-TheNIOTransport">NIO transport</a> underneath and will generally use much less threads than the standard connector. This connector can help if you want to use <a shape="rect" href="http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html">large number of queues</a></p><h3>Enabling AMQP over SSL</h3><p>It's easy to configure ActiveMQ to use AMQP over a SSL connection. To use SSL use the transport scheme <strong><code>amqp+ssl</code></strong> instead of <strong><code>amqp</code></strong>.</p><p>Example:</p><structured-macro ac:macro-id="1b2eaa95-2237-4062-85d0-8f9e9566e4ce" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnector name="amqp+ssl" uri="amqp+ssl://localhost:5671"/>
+</plain-text-body></structured-macro><p>For more details on using SSL with ActiveMQ, see the following article (<a shape="rect" href="http://activemq.apache.org/how-do-i-use-ssl.html">How do I use SSL</a>).</p><h3>Working with Destinations with AMQP</h3><p>You should prefix destination address with <strong><code>queue://</code></strong> to use queue based destinations or <strong><code>topic://</code></strong> to use topic based destinations. The destination type defaults to queue when the destination prefix is omitted.</p><h3>Prefetch Size and Credit</h3><p>When AMQP receiver connects to the broker it's mapped to the JMS consumer. This JMS consumer has to have appropriate <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>prefetch size</plain-text-link-body></link> set. <span style="line-height: 1.4285715;">The broker will honor the credit set by the client or use the default value of <strong><code>1000</code></strong> if client doesn't set it.</span></p><p>Example: tuning the default <strong><code>prefetch</code></strong> size:</p><structured-macro ac:macro-id="9a30b86c-fde9-40bc-be6b-86af0f621a5b" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600&amp;transport.prefetch=10"/></plain-text-body></structured-macro><p class="p1">In this case, client preference will be ignored and the configured value will be used.</p><p class="p1">You can also tune broker-side <strong><code>amqp</code></strong> receiver link that handles incoming messages. It will use credit of <strong><code>1000</code></strong> messages by default, but you can override this by using <span><strong><code>producerCredit</code></strong> property, like </span></p><structured-macro ac:macro-id="e342bae5-f001-43ea-aac3-191f7f4d8b81" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600&amp;transport.producerCredit=10000"/></plain-text-body></structured-macro><h3>Mapping to JMS</h3><p>There are three basic conversion strategies that can be used with AMQP and inter-operating with the JMS API.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Strategy</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>native</code></p></td><td colspan="1" rowspan="1"><p>(<strong>Default</strong>) Wraps the bytes of the AMQP message into a JMS <strong><code>BytesMessage</code></strong> and maps the headers of the AMQP message to headers on the JMS message.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>raw</code></p></td><td colspan="1" rowspan="1"><p>Wraps the bytes of the AMQP message into a JMS <strong><code>BytesMessage</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>jms</code></p></td><td colspan="1" rowspan="1"><p>Maps headers of the AMQP message to JMS message headers and the body of the AMQP message to the JMS body.</p></td></tr></tbody></table><p>Set the <strong>transformer</strong> transport option on the <strong><code>transportConnector</code></strong> to the desired mapping strategy. For example, to inter-operate with JMS at the payload level, set the <strong><code>transformer</code></strong> option to <strong><code>jms</code></strong>:</p><structured-macro ac:macro-id="92bbef4f-f76c-4b71-b56c-ee2f2afda28d" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnector name="amqp" uri="amqp://localhost:5672?transport.transformer=jms"/>
+</plain-text-body></structured-macro><h4>How AMQP Message Headers are Mapped to JMS Headers</h4><p>The following headers are mapped regardless of the transformer used:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>AMQP Message</p></th><th colspan="1" rowspan="1"><p>JMS Message</p></th><th colspan="1" rowspan="1"><p>Notes</p></th></tr><tr><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_NATIVE</code></p></td><td colspan="1" rowspan="1"><p>Will be set to <strong><code>true</code></strong> if the transformer is <strong><code>native</code></strong> or <strong><code>raw</code></strong>, <strong><code>false</code></strong> otherwise.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>message-format</code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_MESSAGE_FORMAT</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr></tbody></table><p>The following header mappings apply when the transformer is either <strong><code>native</code></strong> or <strong><code>jms</code></strong>:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>AMQP Message</p></th><th colspan="1" rowspan="1"><p>JMS Message</p></th><th colspan="1" rowspan="1"><p>Notes</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>application-properties.JMSXGroupID</code></p></td><td colspan="1" rowspan="1"><p><code>JMSXGroupID</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>application-properties.JMSXGroupSequence</code></p></td><td colspan="1" rowspan="1"><p><code>JMSXGroupSequence</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>application-properties.JMSXUserID</code></p></td><td colspan="1" rowspan="1"><p><code>JMSXUserID</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>application-properties.<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1"><p><u><strong><code>name</code></strong></u></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>delivery-annotations.<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_DA_<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>footer.<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_FT_<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>header.deliveryCount</code></p></td><td colspan="1" rowspan="1"><p><code>JMSXDeliveryCount</code></p></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><p><code>header.durable</code></p></td><td colspan="1" rowspan="1"><p><code>JMSDeliveryMode</code></p></td><td colspan="1" rowspan="1"><p><strong><code>javax.jms.Message.DEFAULT_DELIVERY_MODE</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>header.first-acquirer</code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_FirstAcquirer</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>header.priority</code></p></td><td colspan="1" rowspan="1"><p><code>JMSPriority</code></p></td><td colspan="1" rowspan="1"><p><strong><code>javax.jms.Message.DEFAULT_PRIORITY</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>header.ttl</code></p></td><td colspan="1" rowspan="1"><p><code>JMSExpiration</code></p></td><td colspan="1" rowspan="1"><p><strong><code>javax.jms.Message.DEFAULT_TIME_TO_LIVE</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>message-annotations.<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_MA_<u><strong>name</strong></u></code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>message-annotations.x-opt-jms-type</code></p></td><td colspan="1" rowspan="1"><p><code>JMSType</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>message-annotations.x-opt-reply-type</code></p></td><td colspan="1" rowspan="1"><p>Type of the <code>JMSReplyTo</code></p></td><td colspan="1" rowspan="1"><p>Comma separated list of <strong><code>queue</code></strong>, <strong><code>topic</code></strong>, or <strong><code>temporary</code></strong>. Defaults to <strong><code>queue</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>message-annotations.x-opt-to-type</code></p></td><td colspan="1" rowspan="1"><p>Type of the <code>JMSDestination</code></p></td><td colspan="1" rowspan="1"><p>Comma separated list of <strong><code>queue</code></strong>, <strong><code>topic</code></strong>, or <strong><code>temporary</code></strong>. Defaults to <strong><code>queue</code></strong> if not set.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.content-encoding</code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_ContentEncoding</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.content-type</code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_ContentType</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.correlation-id</code></p></td><td colspan="1" rowspan="1"><p><code>JMSCorrelationID</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.creation-time</code></p></td><td colspan="1" rowspan="1"><p><code>JMSTimestamp</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.group-sequence</code></p></td><td colspan="1" rowspan="1"><p><code>JMSXGroupSequence</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.message-id</code></p></td><td colspan="1" rowspan="1"><p><code>JMSMessageID</code></p></td><td colspan="1" rowspan="1"><p>Auto generated if not set.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.reply-to</code></p></td><td colspan="1" rowspan="1"><p><code>JMSReplyTo</code></p></td><td colspan="1" rowspan="1"><p>The name of the <strong><code>JMSReplyTo</code></strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.reply-to-group-id</code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_ReplyToGroupID</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.subject</code></p></td><td colspan="1" rowspan="1"><p><code>JMS_AMQP_Subject</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.to</code></p></td><td colspan="1" rowspan="1"><p><code>JMSDestination</code></p></td><td colspan="1" rowspan="1"><p>The name of the <strong><code>JMSDestination</code></strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>properties.user-id</code></p></td><td colspan="1" rowspan="1"><p><code>JMSXUserID</code></p></td><td colspan="1" rowspan="1"><p><strong><code>properties.user-id</code></strong> is decoded as a UTF-8 String.</p></td></tr></tbody></table><p> </p><p>AMQP property value types are converted as follows:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>AMQP Type</p></th><th colspan="1" rowspan="1"><p>Java Type</p></th><th colspan="1" rowspan="1"><p>Notes</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>binary</code></p></td><td colspan="1" rowspan="1"><p><code>String</code></p></td><td colspan="1" rowspan="1"><p>Hex encoding of the binary value</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>bool</code></p></td><td colspan="1" rowspan="1"><p><code>Boolean</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>byte</code></p></td><td colspan="1" rowspan="1"><p><code>Byte</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>double</code></p></td><td colspan="1" rowspan="1"><p><code>Double</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>float</code></p></td><td colspan="1" rowspan="1"><p><code>Float</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>int</code></p></td><td colspan="1" rowspan="1"><p><code>Integer</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>long</code></p></td><td colspan="1" rowspan="1"><p><code>Long</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>short</code></p></td><td colspan="1" rowspan="1"><p><code>Short</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>symbol</code></p></td><td colspan="1" rowspan="1"><p><code>String</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ubyte</code></p></td><td colspan="1" rowspan="1"><p><code>Byte</code> or <code>Short</code></p></td><td colspan="1" rowspan="1"><p><strong><code>Short</code></strong> is used if: <strong><code>value ></code></strong> <strong><code>Byte.MAX_VALUE</code></strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>uint</code></p></td><td colspan="1" rowspan="1"><p><code>Integer</code> or <code>Long</code></p></td><td colspan="1" rowspan="1"><p><strong><code>Long</code></strong> is used if: <strong><code>value ></code></strong> <strong><code>Integer.MAX_VALUE</code></strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ulong</code></p></td><td colspan="1" rowspan="1"><p><code>Long</code></p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ushort</code></p></td><td colspan="1" rowspan="1"><p><code>Short</code> or <code>Integer</code></p></td><td colspan="1" rowspan="1"><p><strong><code>Integer</code></strong> is used if: <strong><code>value ></code></strong> <strong><code>Short.MAX_VALUE</code></strong></p></td></tr></tbody></table><structured-macro ac:macro-id="1bc9267d-a4b2-4453-931f-845db9ecf314" ac:name="htmlcomment" ac:schema-version="1"><parameter ac:name="atlassian-macro-output-type">BLOCK</parameter><rich-text-body><table><tbody><tr><td colspan="1" rowspan="1"><p>char</p></td><td colspan="1" rowspan="1"><p>String</p></td></tr><tr><td colspan="1" rowspan="1"><p>timestamp</p></td><td colspan="1" rowspan="1"><p>Long</p></td></tr></tbody></table></rich-text-body></structured-macro><h4>How a AMQP Messages Body is Mapped to a JMS Message</h4><p>If the transformer is set to <strong><code>jms</code></strong> then the JMS message type will depend on the body type of the AMQP message.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Body Type</p></th><th colspan="1" rowspan="1"><p>JMS Message Type</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>AmqpSequence</code></p></td><td colspan="1" rowspan="1"><p><code>StreamMessage</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>AmqpValue</code></p></td><td colspan="1" rowspan="1"><p><code>ObjectMessage</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>AmqpValue</code> holding a <code>null</code></p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>AmqpValue</code> holding a <code>String</code></p></td><td colspan="1" rowspan="1"><p><code>TextMessage</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>AmqpValue</code> holding a <code>binary</code></p></td><td colspan="1" rowspan="1"><p><code>BytesMessage</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>AmqpValue</code> holding a <code>list</code></p></td><td colspan="1" rowspan="1"><p><code>StreamMessage</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>Data</code></p></td><td colspan="1" rowspan="1"><p><code>BytesMessage</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><code>Message</code></p></td></tr></tbody></table><h3>AMQP 1.0 client library</h3><p>You can use <a shape="rect" href="http://qpid.apache.org/proton/">Apache Qpid Proton</a>.</p></div>
diff --git a/apache-activemq-board-report-200708-august.xml b/apache-activemq-board-report-200708-august.xml
index ff38e37..cbfb247 100644
--- a/apache-activemq-board-report-200708-august.xml
+++ b/apache-activemq-board-report-200708-august.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-2007.08(August)-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[July board report was missed in part due to a change in PMC chair.
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1><structured-macro ac:macro-id="5a6c948d-f150-4690-9906-a96776c77ce9" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>July board report was missed in part due to a change in PMC chair.
Community:
* The developer and user communities remain very active.
@@ -18,6 +17,5 @@
* ActiveMQ CPP 2.0.1 - Updated to use the CMS 1.0 API
* ActiveMQ CMS 1.1 - Updated to build as a shared lib
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-200710-october.xml b/apache-activemq-board-report-200710-october.xml
index b327295..97a9bc3 100644
--- a/apache-activemq-board-report-200710-october.xml
+++ b/apache-activemq-board-report-200710-october.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-2007.10(October)-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Community:
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1><structured-macro ac:macro-id="b384dd9c-a988-487b-b276-e2abc9cda884" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>Community:
* The developer and user communities remain very active.
* The Camel project, NMS project, and recent release candidate for ActiveMQ
5.0 have generated much mailing list activity.
@@ -14,6 +13,5 @@
Releases:
* ActiveMQ Camel 1.1.0 - A routing and mediation engine
* ActiveMQ CPP 2.1 - A C++ client to ActiveMQ that implements the CMS API
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-200801-january.xml b/apache-activemq-board-report-200801-january.xml
index 6d755ed..707a058 100644
--- a/apache-activemq-board-report-200801-january.xml
+++ b/apache-activemq-board-report-200801-january.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-2008.01(January)-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Community:
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1><structured-macro ac:macro-id="0c9eddee-b43e-47c5-b6cf-90b4fc01e8d1" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>Community:
* Nicky Sandhu and Hadrian Zbarcea were voted in and accepted becoming ActiveMQ committers
* A code grant was accepted for an NMS implementation that access
Tibco EMS.
@@ -16,6 +15,5 @@
* ActiveMQ CPP 2.1.1
* ActiveMQ CPP 2.1.2
* ActiveMQ CPP 2.1.3
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-200807-july.xml b/apache-activemq-board-report-200807-july.xml
index 02c22bc..06ce4a5 100644
--- a/apache-activemq-board-report-200807-july.xml
+++ b/apache-activemq-board-report-200807-july.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-2008.07(July)-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Community:
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1><structured-macro ac:macro-id="e63d73fc-c415-4b30-b192-415e94ab6290" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>Community:
* The ActiveMQ project has had another very busy quarter. Seven new contributors were voted in and accepted becoming ActiveMQ committers:
* Gary Tully
* Gert Vanthienen
@@ -21,6 +20,5 @@
* ActiveIO 3.0.1
* ActiveMQ-CPP 2.2
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-200810-october.xml b/apache-activemq-board-report-200810-october.xml
index 80576f6..c7e8682 100644
--- a/apache-activemq-board-report-200810-october.xml
+++ b/apache-activemq-board-report-200810-october.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-2008.10(October)-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Community:
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1><structured-macro ac:macro-id="3cc0a94c-a838-4c88-85d9-75b700554bd2" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>Community:
* The ActiveMQ project has had another very busy quarter. Jonathan Anstey was voted in as an ActiveMQ committer.
* The development and user lists continue to stay vibrant.
@@ -12,6 +11,5 @@
* Camel 1.4.0
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-200901-january.xml b/apache-activemq-board-report-200901-january.xml
index 72edb4c..8740c58 100644
--- a/apache-activemq-board-report-200901-january.xml
+++ b/apache-activemq-board-report-200901-january.xml
@@ -1,8 +1,7 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-2009.01(January)-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Community:
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1><structured-macro ac:macro-id="9beca253-915a-448a-8eba-49ce980c70d0" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>Community:
* The ActiveMQ project has had another very busy quarter. William Tam has been added as an ActiveMQ committer.
* The development and user lists continue to stay vibrant.
- * The Camel sub project has been approved to become a TLP and is currently setting it's infrastructure to do so.
+ * The Camel sub project has been approved to become a TLP and is currently setting it's infrastructure to do so.
* A privacy policy page has been added to all the ActiveMQ wikis and websites.
Development:
@@ -17,6 +16,5 @@
* ActiveMQ-CPP 2.2.2
* ActiveMQ-CPP 2.2.3
* Camel 1.5.0
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-200904-april.xml b/apache-activemq-board-report-200904-april.xml
index cd2e085..af2a239 100644
--- a/apache-activemq-board-report-200904-april.xml
+++ b/apache-activemq-board-report-200904-april.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-2009.04(April)-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Community:
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1><structured-macro ac:macro-id="8750c421-9c4d-459f-9384-dccd065a1251" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>Community:
* The ActiveMQ project has had another very busy but quiet quarter.
* The development and user lists continue to stay vibrant.
* The Camel sub project has completed moving to a TLP.
@@ -14,6 +13,5 @@
Releases:
* ActiveMQ-CPP 2.2.4
* ActiveMQ-CPP 2.2.5
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-200907-july.xml b/apache-activemq-board-report-200907-july.xml
index 257a525..2fcf50f 100644
--- a/apache-activemq-board-report-200907-july.xml
+++ b/apache-activemq-board-report-200907-july.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>Community:
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="b7e799f9-4d6a-4397-900e-7eb12546bcac" ac:name="noformat" ac:schema-version="1"><plain-text-body>Community:
* The ActiveMQ project has had another very busy but quiet quarter.
* The development and user lists continue to stay vibrant.
* New PMC members: Dejan Bosanac
@@ -16,6 +15,5 @@
* ActiveMQ-CPP 3.0.0
* ActiveMQ-CPP 3.0.1
-</pre>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-200910-october.xml b/apache-activemq-board-report-200910-october.xml
index d13a6ce..5b7b245 100644
--- a/apache-activemq-board-report-200910-october.xml
+++ b/apache-activemq-board-report-200910-october.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>Community:
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="72b9438f-f3cf-4c0c-83f2-9c086cc84be4" ac:name="noformat" ac:schema-version="1"><plain-text-body>Community:
* The ActiveMQ project has had another very busy but quiet quarter.
* The development and user lists continue to stay vibrant.
@@ -17,6 +16,5 @@
* ActiveMQ Protocol Buffers 1.0
* ActiveMQ 5.3.0
-</pre>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-201001-january.xml b/apache-activemq-board-report-201001-january.xml
index 7724d88..8ebd9ca 100644
--- a/apache-activemq-board-report-201001-january.xml
+++ b/apache-activemq-board-report-201001-january.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>Community:
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="afed1d78-2444-449e-b098-7e89e02110cd" ac:name="noformat" ac:schema-version="1"><plain-text-body>Community:
* The ActiveMQ project has had another very busy but quiet quarter.
* The development and user lists continue to stay vibrant.
* Tim Bish has joined the ActiveMQ PMC
@@ -11,6 +10,5 @@
Releases:
* ActiveMQ-CPP 3.1.0
-</pre>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-201005-may.xml b/apache-activemq-board-report-201005-may.xml
index 2693fdb..d9c4e3e 100644
--- a/apache-activemq-board-report-201005-may.xml
+++ b/apache-activemq-board-report-201005-may.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-2010.05(May)-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Apologies for missing the April board report deadline.
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1><structured-macro ac:macro-id="f0c3b6cc-e3b6-400d-aaeb-47b9c61d88c4" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>Apologies for missing the April board report deadline.
Community:
* The ActiveMQ project has had another very busy but quiet quarter.
@@ -17,6 +16,5 @@
* Apache.NMS.Stomp v1.2.0
* Apache.NMS API 1.2.0
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-report-201504-april.xml b/apache-activemq-board-report-201504-april.xml
index 4d3a1cf..4fff13b 100644
--- a/apache-activemq-board-report-201504-april.xml
+++ b/apache-activemq-board-report-201504-april.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>TLP Description:<br clear="none">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4.</p><p>Community:<br clear="none">* The development and user lists continue to stay active.<br clear="none">* Several ActiveMQ based presentation were given at Apachecon NA.<br clear="none">* The ActiveMQ community has voted to name the HortnetQ code donation ActiveMQ <span style="color: rgb(34,34,34);">Artemis.</span><br clear="none"><span style="color: rgb(34,34,34);line-height: 1.4285715;">* Apache board members </span><span style="color: rgb(34,34,34);">requested<span style="line-height: 1.4285715;"> a special report to address what the plan is of the hornetq code </span>donation<span style="line-height: 1.4285715;">.  There were some specific question what were directed at the PMC:</span></span></p><p><span style="color: rgb(34,34,34);"><span style="line-height: 1.4285715;"><span style="color: rgb(34,34,34);">    Q. Red Hat has a product, called HornetQ, which includes a website;</span><br clear="none"><span style="color: rgb(34,34,34);">         branding, etc.  </span><a shape="rect" class="external-link" href="http://hornetq.jboss.org/" rel="nofollow">http://hornetq.jboss.org/</a><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">    A. ActiveMQ PMC does not intend to use the HornetQ branding in any code,</span><br clear="none"><span style="color: rgb(34,34,34);">        docs or website. <span style="color: rgb(34,34,34);">The code donation has been updated to remove such</span><br clear="none"><span style="color: rgb(34,34,34);">        references. </span>The <span style="color: rgb(34,34,34);">HornetQ open source project is now considered a legacy <br clear="none"><span style="color: rgb(34,34,34);">        </span>project and the code is no longer maintained as the open source project<br clear="none"><span style="color: rgb(34,34,34);">        </span>HornetQ.</span></span><span style="color: rgb(34,34,34);"> The ActiveMQ community is beginning to work together to <br clear="none"><span style="color: rgb(34,34,34);">        develop a plan to take the donated code base forward and to develop <br clear="none"><span style="color: rgb(34,34,34);">        </span>community <span style="color: rgb(34,34,34);">around this code base</span>. </span></span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">    Q. The ActiveMQ PMC needs to deliver a plan for:</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span>A.  Apache ActiveMQ has multiple products with multiple versions:</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">    </span> a.  ActiveMQ - (version 5.x.x)</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">    </span> b.  ActiveMQ <span style="color: rgb(34,34,34);">Artemis</span> - (version 1.x.x)</span></span></span></p><p><span style="color: rgb(34,34,34);"><span style="line-height: 1.4285715;"><span style="color: rgb(34,34,34);"> </span>          This means that we are not yet ready to declare that <span style="color: rgb(34,34,34);">ActiveMQ <span style="color: rgb(34,34,34);">Artemis</span> is the successor to ActiveMQ 5.x.  We will wait until the product matures to make that decision.</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span>Q. The current chair has been the chair for *many* years and based on the</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">     </span>current </span><span style="color: rgb(34,34,34);">status and issues in the community, I would strongly suggest having</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">     </span>a plan for potentially replacing the chair of the project.</span></span></span></p><p><span style="color: rgb(34,34,34);"><span style="line-height: 1.4285715;"><span style="color: rgb(34,34,34);">    A. The PMC agrees.</span></span></span></p><p><span style="line-height: 1.4285715;">* The PMC has voted to give the code donation a code name so that it is not referred to as HornetQ anymore within ActiveMQ.<br clear="none">* IP clearance for the code donation is almost complete: <a shape="rect" class="external-link" href="http://incubator.apache.org/ip-clearance/hornetq.html">http://incubator.apache.org/ip-clearance/hornetq.html<br clear="none"></a></span><span style="line-height: 1.4285715;">* At least one member of the PMC, as well as several members of the community, feels strongly that disagreements and concerns are not getting addressed.  They would rather have <span style="color: rgb(34,34,34);">Artemis go through the incubator.</span> <br clear="none"></span><span style="line-height: 1.4285715;">* PMC is in discussions looking for ways to increase community diversity<br clear="none"></span><span style="line-height: 1.4285715;">* PMC has voted to appoint Bruce Snyder as the ActiveMQ PMC chair.  The PMC requests that the board approve the the following resolution:</span></p><p><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">-----------------------------</span><span style="color: rgb(34,34,34);">-----------------------------</span></span></p><p><span style="color: rgb(34,34,34);">WHEREAS, the Board of Directors heretofore appointed Hiram Chirino to</span><br clear="none"><span style="color: rgb(34,34,34);">the office of Vice President, Apache ActiveMQ, and</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">WHEREAS, the Board of Directors is in receipt of the resignation</span><br clear="none"><span style="color: rgb(34,34,34);">of Hiram Chirino from the office of Vice President, Apache</span><br clear="none"><span style="color: rgb(34,34,34);">ActiveMQ, and</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">WHEREAS, the Project Management Committee of the Apache ActiveMQ</span><br clear="none"><span style="color: rgb(34,34,34);">project has chosen by vote to recommend Bruce Snyder as the Successor</span><br clear="none"><span style="color: rgb(34,34,34);">to the post;</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">NOW, THEREFORE, BE IT RESOLVED, that Hiram Chirino is</span><br clear="none"><span style="color: rgb(34,34,34);">relieved and discharged from the duties and responsibilities of</span><br clear="none"><span style="color: rgb(34,34,34);">the office of Vice President, Apache ActiveMQ, and</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">BE IT FURTHER RESOLVED, that Bruce Snyder be and hereby</span><br clear="none"><span style="color: rgb(34,34,34);">is appointed to the office of Vice President, Apache ActiveMQ, to</span><br clear="none"><span style="color: rgb(34,34,34);">serve in accordance with and subject to the direction of the</span><br clear="none"><span style="color: rgb(34,34,34);">Board of Directors and the Bylaws of the Foundation until</span><br clear="none"><span style="color: rgb(34,34,34);">death, resignation, retirement, removal or disqualification, or</span><br clear="none"><span style="color: rgb(34,34,34);">until a successor is appointed.</span></p><p><span style="color: rgb(34,34,34);">-----------------------------<span style="color: rgb(34,34,34);">-----------------------------</span></span></p><p>Development:<br clear="none">* Development on ActiveMQ 5.12 is in progress.<br clear="none">* Development on ActiveMQ <span style="color: rgb(34,34,34);">Artemis</span> is in progress.</p><p>Trademark / Branding Status:<br clear="none">* Sub-projects need to be reviewed to make sure they are also compliant /w TM policies<br clear="none">* Documentation and readme files will also be reviewed for compliance</p><p>Releases:<br clear="none"><span style="line-height: 1.4285715;">* </span><span style="color: rgb(34,34,34);">Apache ActiveMQ 5.11.1 - 2/17/15<br clear="none"></span><span style="line-height: 1.4285715;">* </span><span style="color: rgb(34,34,34);">Apache ActiveMQ 5.10.2 - 2/17/15<br clear="none">* Apache <span style="color: rgb(34,34,34);">ActiveMQ-CPP v3.8.4 - 2/19/15</span> </span></p><p><span style="color: rgb(34,34,34);"> </span></p><div><span style="color: rgb(34,34,34);"><br clear="none"></span></div><p><span style="color: rgb(34,34,34);"> </span></p><p> </p></div>
+<div class="wiki-content maincontent"><p>TLP Description:<br clear="none">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4.</p><p>Community:<br clear="none">* The development and user lists continue to stay active.<br clear="none">* Several ActiveMQ based presentation were given at Apachecon NA.<br clear="none">* The ActiveMQ community has voted to name the HortnetQ code donation ActiveMQ <span style="color: rgb(34,34,34);">Artemis.</span><br clear="none"><span style="color: rgb(34,34,34);line-height: 1.4285715;">* Apache board members </span><span style="color: rgb(34,34,34);">requested<span style="line-height: 1.4285715;"> a special report to address what the plan is of the hornetq code </span>donation<span style="line-height: 1.4285715;">.  There were some specific question what were directed at the PMC:</span></span></p><p><span style="color: rgb(34,34,34);"><span style="line-height: 1.4285715;"><span style="color: rgb(34,34,34);">    Q. Red Hat has a product, called HornetQ, which includes a website;</span><br clear="none"><span style="color: rgb(34,34,34);">         branding, etc.  </span><a shape="rect" href="http://hornetq.jboss.org/">http://hornetq.jboss.org/</a><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">    A. ActiveMQ PMC does not intend to use the HornetQ branding in any code,</span><br clear="none"><span style="color: rgb(34,34,34);">        docs or website. <span style="color: rgb(34,34,34);">The code donation has been updated to remove such</span><br clear="none"><span style="color: rgb(34,34,34);">        references. </span>The <span style="color: rgb(34,34,34);">HornetQ open source project is now considered a legacy <br clear="none"><span style="color: rgb(34,34,34);">        </span>project and the code is no longer maintained as the open source project<br clear="none"><span style="color: rgb(34,34,34);">        </span>HornetQ.</span></span><span style="color: rgb(34,34,34);"> The ActiveMQ community is beginning to work together to <br clear="none"><span style="color: rgb(34,34,34);">        develop a plan to take the donated code base forward and to develop <br clear="none"><span style="color: rgb(34,34,34);">        </span>community <span style="color: rgb(34,34,34);">around this code base</span>. </span></span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">    Q. The ActiveMQ PMC needs to deliver a plan for:</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span>A.  Apache ActiveMQ has multiple products with multiple versions:</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">    </span> a.  ActiveMQ - (version 5.x.x)</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">    </span> b.  ActiveMQ <span style="color: rgb(34,34,34);">Artemis</span> - (version 1.x.x)</span></span></span></p><p><span style="color: rgb(34,34,34);"><span style="line-height: 1.4285715;"><span style="color: rgb(34,34,34);"> </span>          This means that we are not yet ready to declare that <span style="color: rgb(34,34,34);">ActiveMQ <span style="color: rgb(34,34,34);">Artemis</span> is the successor to ActiveMQ 5.x.  We will wait until the product matures to make that decision.</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span>Q. The current chair has been the chair for *many* years and based on the</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">     </span>current </span><span style="color: rgb(34,34,34);">status and issues in the community, I would strongly suggest having</span><br clear="none"><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">    </span><span style="color: rgb(34,34,34);">     </span>a plan for potentially replacing the chair of the project.</span></span></span></p><p><span style="color: rgb(34,34,34);"><span style="line-height: 1.4285715;"><span style="color: rgb(34,34,34);">    A. The PMC agrees.</span></span></span></p><p><span style="line-height: 1.4285715;">* The PMC has voted to give the code donation a code name so that it is not referred to as HornetQ anymore within ActiveMQ.<br clear="none">* IP clearance for the code donation is almost complete: <a shape="rect" href="http://incubator.apache.org/ip-clearance/hornetq.html">http://incubator.apache.org/ip-clearance/hornetq.html<br clear="none"></a></span><span style="line-height: 1.4285715;">* At least one member of the PMC, as well as several members of the community, feels strongly that disagreements and concerns are not getting addressed.  They would rather have <span style="color: rgb(34,34,34);">Artemis go through the incubator.</span> <br clear="none"></span><span style="line-height: 1.4285715;">* PMC is in discussions looking for ways to increase community diversity<br clear="none"></span><span style="line-height: 1.4285715;">* PMC has voted to appoint Bruce Snyder as the ActiveMQ PMC chair.  The PMC requests that the board approve the the following resolution:</span></p><p><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">-----------------------------</span><span style="color: rgb(34,34,34);">-----------------------------</span></span></p><p><span style="color: rgb(34,34,34);">WHEREAS, the Board of Directors heretofore appointed Hiram Chirino to</span><br clear="none"><span style="color: rgb(34,34,34);">the office of Vice President, Apache ActiveMQ, and</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">WHEREAS, the Board of Directors is in receipt of the resignation</span><br clear="none"><span style="color: rgb(34,34,34);">of Hiram Chirino from the office of Vice President, Apache</span><br clear="none"><span style="color: rgb(34,34,34);">ActiveMQ, and</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">WHEREAS, the Project Management Committee of the Apache ActiveMQ</span><br clear="none"><span style="color: rgb(34,34,34);">project has chosen by vote to recommend Bruce Snyder as the Successor</span><br clear="none"><span style="color: rgb(34,34,34);">to the post;</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">NOW, THEREFORE, BE IT RESOLVED, that Hiram Chirino is</span><br clear="none"><span style="color: rgb(34,34,34);">relieved and discharged from the duties and responsibilities of</span><br clear="none"><span style="color: rgb(34,34,34);">the office of Vice President, Apache ActiveMQ, and</span><br clear="none"><br clear="none"><span style="color: rgb(34,34,34);">BE IT FURTHER RESOLVED, that Bruce Snyder be and hereby</span><br clear="none"><span style="color: rgb(34,34,34);">is appointed to the office of Vice President, Apache ActiveMQ, to</span><br clear="none"><span style="color: rgb(34,34,34);">serve in accordance with and subject to the direction of the</span><br clear="none"><span style="color: rgb(34,34,34);">Board of Directors and the Bylaws of the Foundation until</span><br clear="none"><span style="color: rgb(34,34,34);">death, resignation, retirement, removal or disqualification, or</span><br clear="none"><span style="color: rgb(34,34,34);">until a successor is appointed.</span></p><p><span style="color: rgb(34,34,34);">-----------------------------<span style="color: rgb(34,34,34);">-----------------------------</span></span></p><p>Development:<br clear="none">* Development on ActiveMQ 5.12 is in progress.<br clear="none">* Development on ActiveMQ <span style="color: rgb(34,34,34);">Artemis</span> is in progress.</p><p>Trademark / Branding Status:<br clear="none">* Sub-projects need to be reviewed to make sure they are also compliant /w TM policies<br clear="none">* Documentation and readme files will also be reviewed for compliance</p><p>Releases:<br clear="none"><span style="line-height: 1.4285715;">* </span><span style="color: rgb(34,34,34);">Apache ActiveMQ 5.11.1 - 2/17/15<br clear="none"></span><span style="line-height: 1.4285715;">* </span><span style="color: rgb(34,34,34);">Apache ActiveMQ 5.10.2 - 2/17/15<br clear="none">* Apache <span style="color: rgb(34,34,34);">ActiveMQ-CPP v3.8.4 - 2/19/15</span> </span></p><p><span style="color: rgb(34,34,34);"> </span></p><div><span style="color: rgb(34,34,34);"><br clear="none"></span></div><p><span style="color: rgb(34,34,34);"> </span></p><p> </p></div>
diff --git a/apache-activemq-board-report-201506-june.xml b/apache-activemq-board-report-201506-june.xml
index 20766e5..7de8fb8 100644
--- a/apache-activemq-board-report-201506-june.xml
+++ b/apache-activemq-board-report-201506-june.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><strong>The May ASF board meeting already took place this week, so we will need to publish this report in time for next month's meeting. </strong></p></div></div><p><strong style="line-height: 1.4285715;">TLP Description:</strong></p><p>Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</p><p><strong>Community: </strong></p><p>* The development and user lists continue to remain active<br clear="none">* <span style="color: rgb(34,34,34);">Two resignations from the PMC, but upon further discussion and consideration, both have suspended the request</span><br clear="none">* <span style="color: rgb(34,34,34);">New mailing list created for JIRA issues, git pull requests, etc. named <a shape="rect" class="external-link" href="mailto:issues@activemq.apache.org" rel="nofollow">issues@activemq.apache.org</a> <br clear="none">* Donated code base renamed to ActiveMQ Artemis (based on a vote)</span> <br clear="none">* <span style="color: rgb(34,34,34);">Marc Schöchlin</span> voted in as a committer on 16 May 2015<br clear="none">* <span style="color: rgb(34,34,34);">Jeff Genender</span> voted in as a committer on 16 May 2015<br clear="none"> <span style="line-height: 1.4285715;">* Developing guidelines on what it takes to become a committer on the ActiveMQ project </span> <br clear="none">* Discussions have started around some of the differences between the processes of the ActiveMQ community and the Artemis developer workflow to get them aligned with the expectations of the entire community.</p><p><strong>Development: </strong></p><p>* Development on ActiveMQ 5.12 is in progress and remains very active <br clear="none">* Development on ActiveMQ Artemis 1.0.1 is in progress and is active<span style="color: rgb(34,34,34);"> <br clear="none">* Development on ActiveMQ Apollo seems to have stalled</span></p><p><strong>Trademark / Branding Status:</strong> <span style="line-height: 1.4285715;"> </span></p><p>* Sub-projects need to be reviewed to make sure they are also compliant with trademark policies<br clear="none">* Documentation also being reviewed for compliance</p><p><strong>Releases:</strong></p><p>* ActiveMQ Artemis 1.0.0 released on May 29, 2015<br clear="none">* ActiveMQ 5.10.2 and ActiveMQ 5.11.1 released on February 17, 2015</p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="8556510b-fffc-4b9a-851e-2b1ce41784ac" ac:name="note" ac:schema-version="1"><rich-text-body><p><strong>The May ASF board meeting already took place this week, so we will need to publish this report in time for next month's meeting. </strong></p></rich-text-body></structured-macro><p><strong style="line-height: 1.4285715;">TLP Description:</strong></p><p>Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</p><p><strong>Community: </strong></p><p>* The development and user lists continue to remain active<br clear="none">* <span style="color: rgb(34,34,34);">Two resignations from the PMC, but upon further discussion and consideration, both have suspended the request</span><br clear="none">* <span style="color: rgb(34,34,34);">New mailing list created for JIRA issues, git pull requests, etc. named <a shape="rect" href="mailto:issues@activemq.apache.org">issues@activemq.apache.org</a> <br clear="none">* Donated code base renamed to ActiveMQ Artemis (based on a vote)</span> <br clear="none">* <span style="color: rgb(34,34,34);">Marc Schöchlin</span> voted in as a committer on 16 May 2015<br clear="none">* <span style="color: rgb(34,34,34);">Jeff Genender</span> voted in as a committer on 16 May 2015<br clear="none"> <span style="line-height: 1.4285715;">* Developing guidelines on what it takes to become a committer on the ActiveMQ project </span> <br clear="none">* Discussions have started around some of the differences between the processes of the ActiveMQ community and the Artemis developer workflow to get them aligned with the expectations of the entire community.</p><p><strong>Development: </strong></p><p>* Development on ActiveMQ 5.12 is in progress and remains very active <br clear="none">* Development on ActiveMQ Artemis 1.0.1 is in progress and is active<span style="color: rgb(34,34,34);"> <br clear="none">* Development on ActiveMQ Apollo seems to have stalled</span></p><p><strong>Trademark / Branding Status:</strong> <span style="line-height: 1.4285715;"> </span></p><p>* Sub-projects need to be reviewed to make sure they are also compliant with trademark policies<br clear="none">* Documentation also being reviewed for compliance</p><p><strong>Releases:</strong></p><p>* ActiveMQ Artemis 1.0.0 released on May 29, 2015<br clear="none">* ActiveMQ 5.10.2 and ActiveMQ 5.11.1 released on February 17, 2015</p></div>
diff --git a/apache-activemq-board-report-201508-august.xml b/apache-activemq-board-report-201508-august.xml
index d027b36..9bb18d9 100644
--- a/apache-activemq-board-report-201508-august.xml
+++ b/apache-activemq-board-report-201508-august.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>TLP Description:</strong></p><p>Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</p><p><strong>Report: </strong></p><ul><li>HornetQ IP clearance has been completed 100% <ul><li>HornetQ code base migrated to ActiveMQ Artemis<br clear="none"><ul><li>Eliminated all HornetQ references </li><li>The code base is now 100% an ActiveMQ project</li></ul></li></ul></li><li>Discussion around development methodology differences between the 5.x code base and the ActiveMQ Artemis <br clear="none"><ul><li>Garnered fairly active participation from many committers</li><li>It did result in a good description of the commit then review process that was agreed upon on the mailing list which was then documented at <strong style="text-align: center;"><a shape="rect" class="external-link" href="http://s.apache.org/zD7" style="text-decoration: underline;">http://s.apache.org/zD7</a></strong></li><li>There were also good discussions around code formatting setups to make working on the various codebases within ActiveMQ more consistent and easier to pull ideas and code back and forth</li></ul></li><li>ActiveMQ Artemis code base is now receiving contributions from a wider scope of people (beyond just the original HornetQ contributors)<ul><li>Long standing committers from the 5.x project are starting to contribute to ActiveMQ Artemis</li></ul></li><li>Active collaboration between 5.x development and ActiveMQ Artemis development is now taking place <ul><li>ActiveMQ 5.x features actively being migrated to Artemis <ul><li>Test framework from 5.x migrated ActiveMQ Artemis </li><li>Migration of the MQTT protocol from 5.x to ActiveMQ Artemis </li></ul></li><li>Also discussion is taking place to improve the the 5.x code base with regard multi-protocol detection on a single socket based on ideas from Artemis and Apollo</li></ul></li><li>PMC is actively working toward diversifying the community by inviting more committers to the project<ul><li>Christopher Shannon was added this month</li><li>Three others added since May 2015</li></ul></li><li>Artemis 1.0 was successfully released <ul><li>Work is on-going for the 1.0.1 release</li></ul></li><li>Back in the April report, one PMC member voiced the following concern: <br clear="none"><em>"<span class="s1">At least one member of the PMC, as well as several members of the community, feels strongly that disagreements and concerns are not getting addressed in a manner that will move the community toward consensus.</span>" </em><ul><li>While this comment is true, the community member who was raising these concerns has gone silent</li></ul></li><li>Initiated discussion to address past issues from some community members as instructed by the board<ul><li>Result so far is zero replies</li></ul></li></ul></div>
+<div class="wiki-content maincontent"><p><strong>TLP Description:</strong></p><p>Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</p><p><strong>Report: </strong></p><ul><li>HornetQ IP clearance has been completed 100% <ul><li>HornetQ code base migrated to ActiveMQ Artemis<br clear="none"><ul><li>Eliminated all HornetQ references </li><li>The code base is now 100% an ActiveMQ project</li></ul></li></ul></li><li>Discussion around development methodology differences between the 5.x code base and the ActiveMQ Artemis <br clear="none"><ul><li>Garnered fairly active participation from many committers</li><li>It did result in a good description of the commit then review process that was agreed upon on the mailing list which was then documented at <strong style="text-align: center;"><a shape="rect" href="http://s.apache.org/zD7" style="text-decoration: underline;">http://s.apache.org/zD7</a></strong></li><li>There were also good discussions around code formatting setups to make working on the various codebases within ActiveMQ more consistent and easier to pull ideas and code back and forth</li></ul></li><li>ActiveMQ Artemis code base is now receiving contributions from a wider scope of people (beyond just the original HornetQ contributors)<ul><li>Long standing committers from the 5.x project are starting to contribute to ActiveMQ Artemis</li></ul></li><li>Active collaboration between 5.x development and ActiveMQ Artemis development is now taking place <ul><li>ActiveMQ 5.x features actively being migrated to Artemis <ul><li>Test framework from 5.x migrated ActiveMQ Artemis </li><li>Migration of the MQTT protocol from 5.x to ActiveMQ Artemis </li></ul></li><li>Also discussion is taking place to improve the the 5.x code base with regard multi-protocol detection on a single socket based on ideas from Artemis and Apollo</li></ul></li><li>PMC is actively working toward diversifying the community by inviting more committers to the project<ul><li>Christopher Shannon was added this month</li><li>Three others added since May 2015</li></ul></li><li>Artemis 1.0 was successfully released <ul><li>Work is on-going for the 1.0.1 release</li></ul></li><li>Back in the April report, one PMC member voiced the following concern: <br clear="none"><em>"<span class="s1">At least one member of the PMC, as well as several members of the community, feels strongly that disagreements and concerns are not getting addressed in a manner that will move the community toward consensus.</span>" </em><ul><li>While this comment is true, the community member who was raising these concerns has gone silent</li></ul></li><li>Initiated discussion to address past issues from some community members as instructed by the board<ul><li>Result so far is zero replies</li></ul></li></ul></div>
diff --git a/apache-activemq-board-report-201510-october.xml b/apache-activemq-board-report-201510-october.xml
index 47cedf4..77c9d41 100644
--- a/apache-activemq-board-report-201510-october.xml
+++ b/apache-activemq-board-report-201510-october.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>TLP Description:</strong></p><p>Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</p><p><strong>Activity: </strong></p><ul><li>ActiveMQ 5 saw two new releases this quarter one major release and an additional bug fix release.<ul><li>ActiveMQ 5.11.2 was released on Mon Aug 10 2015</li><li>ActiveMQ 5.12.0 was released on Thu Aug 13 2015</li></ul></li><li>Some discussion on the mailing list around when to release ActiveMQ 5.12.1 and what fixes should be included. </li><li>The ActiveMQ native clients also saw some releases this quarter and continue to see active development.<ul><li>ActiveMQ-CPP 3.9.0 was released on Sat Aug 15 2015</li><li>The Apache.NMS API  v1.7.1 was released on Fri Sep 04 2015.</li><li>The Apache.NMS.ActiveMQ client library v1.7.1 was released on Mon Oct 05 2015.</li></ul></li><li>The Artemis project continues to see some very active development and discussion on the mailing lists.<ul><li>ActiveMQ Artemis 1.1.0 was released on Wed Sep 23 2015</li></ul></li></ul><p><strong>Health Report:</strong></p><ul><li><span style="color: rgb(34,34,34);">As the number and scope of the recent releases shows, there is a lot of development occurring throughout all of the ActiveMQ products </span></li><li><span style="color: rgb(34,34,34);">Many bugs are being raised, but they are being looked at fairly promptly </span></li><li><span style="color: rgb(34,34,34);">There were a couple of bugs raised that resulted in good “cross team” discussions as to whether the bug was, indeed, a bug or a desired change in behavior</span></li><li><span style="color: rgb(34,34,34);">While some of these discussions did hold up the creations of a patch release (5.12.1), it was important for the team to reach a consensus on the outcome and plans are starting to finish the release</span></li></ul><p><strong><span style="color: rgb(34,34,34);">Issues:</span></strong></p><ul><li><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">There are no issues requiring board attention at this time</span></span></li></ul><p><strong>PMC changes: </strong></p><ul><li>Currently 20 PMC members. </li><li>No new PMC members added in the last 3 months </li></ul><p><strong>LDAP changes: </strong></p><ul><li>Currently 54 committers and 20 committee group members. </li><li>No new committee group members added in the last 3 months </li><li>Christopher L. Shannon was added as a committer on Thu Jul 30 2015 </li></ul><p><strong>Releases: </strong></p><ul><li>ActiveMQ-CPP 3.9.0 was released on Fri Aug 14 2015 </li><li>ActiveMQ Artemis 1.1.0 was released on Wed Sep 23 2015 </li><li>5.11.2 was released on Mon Aug 10 2015 </li><li>activemq-cpp-3.9.0 was released on Sat Aug 15 2015 </li><li>5.12.0 was released on Wed Aug 12 2015 </li><li>Apache.NMS.ActiveMQ v1.7.1 was released on Sun Oct 04 2015 </li><li>Apache.NMS v1.7.1 was released on Thu Sep 03 2015 </li></ul><p><strong>Mailing list activity: </strong></p><ul><li>users@activemq.apache.org: <ul><li>721 subscribers (up 20 in the last 3 months): </li><li>727 emails sent to list (815 in previous quarter) </li></ul></li><li>dev@activemq.apache.org: <ul><li>336 subscribers (up 9 in the last 3 months): </li><li>777 emails sent to list (1557 in previous quarter) </li></ul></li><li>issues@activemq.apache.org: <ul><li>27 subscribers (up 6 in the last 3 months): </li><li>1807 emails sent to list (1357 in previous quarter) </li></ul></li><li>announce@activemq.apache.org: <ul><li>8 subscribers (up 0 in the last 3 months) </li></ul></li></ul><p><strong>JIRA activity: </strong></p><ul><li>248 JIRA tickets created in the last 3 months </li><li>209 JIRA tickets closed/resolved in the last 3 months</li></ul><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
+<div class="wiki-content maincontent"><p><strong>TLP Description:</strong></p><p>Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</p><p><strong>Activity: </strong></p><ul><li>ActiveMQ 5 saw two new releases this quarter one major release and an additional bug fix release.<ul><li>ActiveMQ 5.11.2 was released on Mon Aug 10 2015</li><li>ActiveMQ 5.12.0 was released on Thu Aug 13 2015</li></ul></li><li>Some discussion on the mailing list around when to release ActiveMQ 5.12.1 and what fixes should be included. </li><li>The ActiveMQ native clients also saw some releases this quarter and continue to see active development.<ul><li>ActiveMQ-CPP 3.9.0 was released on Sat Aug 15 2015</li><li>The Apache.NMS API  v1.7.1 was released on Fri Sep 04 2015.</li><li>The Apache.NMS.ActiveMQ client library v1.7.1 was released on Mon Oct 05 2015.</li></ul></li><li>The Artemis project continues to see some very active development and discussion on the mailing lists.<ul><li>ActiveMQ Artemis 1.1.0 was released on Wed Sep 23 2015</li></ul></li></ul><p><strong>Health Report:</strong></p><ul><li><span style="color: rgb(34,34,34);">As the number and scope of the recent releases shows, there is a lot of development occurring throughout all of the ActiveMQ products </span></li><li><span style="color: rgb(34,34,34);">Many bugs are being raised, but they are being looked at fairly promptly </span></li><li><span style="color: rgb(34,34,34);">There were a couple of bugs raised that resulted in good “cross team” discussions as to whether the bug was, indeed, a bug or a desired change in behavior</span></li><li><span style="color: rgb(34,34,34);">While some of these discussions did hold up the creations of a patch release (5.12.1), it was important for the team to reach a consensus on the outcome and plans are starting to finish the release</span></li></ul><p><strong><span style="color: rgb(34,34,34);">Issues:</span></strong></p><ul><li><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">There are no issues requiring board attention at this time</span></span></li></ul><p><strong>PMC changes: </strong></p><ul><li>Currently 20 PMC members. </li><li>No new PMC members added in the last 3 months </li></ul><p><strong>LDAP changes: </strong></p><ul><li>Currently 54 committers and 20 committee group members. </li><li>No new committee group members added in the last 3 months </li><li>Christopher L. Shannon was added as a committer on Thu Jul 30 2015 </li></ul><p><strong>Releases: </strong></p><ul><li>ActiveMQ-CPP 3.9.0 was released on Fri Aug 14 2015 </li><li>ActiveMQ Artemis 1.1.0 was released on Wed Sep 23 2015 </li><li>5.11.2 was released on Mon Aug 10 2015 </li><li>activemq-cpp-3.9.0 was released on Sat Aug 15 2015 </li><li>5.12.0 was released on Wed Aug 12 2015 </li><li>Apache.NMS.ActiveMQ v1.7.1 was released on Sun Oct 04 2015 </li><li>Apache.NMS v1.7.1 was released on Thu Sep 03 2015 </li></ul><p><strong>Mailing list activity: </strong></p><ul><li>users@activemq.apache.org: <ul><li>721 subscribers (up 20 in the last 3 months): </li><li>727 emails sent to list (815 in previous quarter) </li></ul></li><li>dev@activemq.apache.org: <ul><li>336 subscribers (up 9 in the last 3 months): </li><li>777 emails sent to list (1557 in previous quarter) </li></ul></li><li>issues@activemq.apache.org: <ul><li>27 subscribers (up 6 in the last 3 months): </li><li>1807 emails sent to list (1357 in previous quarter) </li></ul></li><li>announce@activemq.apache.org: <ul><li>8 subscribers (up 0 in the last 3 months) </li></ul></li></ul><p><strong>JIRA activity: </strong></p><ul><li>248 JIRA tickets created in the last 3 months </li><li>209 JIRA tickets closed/resolved in the last 3 months</li></ul><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
diff --git a/apache-activemq-board-report-201602-february.xml b/apache-activemq-board-report-201602-february.xml
index d44cbf5..6734827 100644
--- a/apache-activemq-board-report-201602-february.xml
+++ b/apache-activemq-board-report-201602-february.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><p><span style="color: rgb(0,0,0);">Apache.NMS added a new provider implementation </span><strong style="color: rgb(0,0,0);line-height: 1.42857;">Apache.NMS.XMS</strong><span style="color: rgb(0,0,0);"> for connecting to IBM WebSphere MQSeries.  This was contributed by the user community, and based on the existing Apache.NMS provider implementation for TIBCO EMS.  There are now eight NMS provider implementations.</span></p></li><li><span style="color: rgb(0,0,0);">ActiveMQ 5.x added several new features in version 5.13.0</span><ul><li><span style="color: rgb(0,0,0);">There is now support for automatic wire protocol detection (OpenWire, STOMP, MQTT, and AMQP) using the new <a shape="rect" href="auto.xml">auto transport</a>.</span></li><li><span style="color: rgb(0,0,0);">Improved metrics as the broker now keeps track of the memory size of pending messages.</span></li><li><span style="color: rgb(0,0,0);">A pure Java API for runtime configuration changes to the broker.  Previously only changes could be done in XML.</span></li><li><span style="color: rgb(0,0,0);">There is now support for <a shape="rect" href="networks-of-brokers.xml#NetworksofBrokers-virtualconsumers">dynamic network demand</a> based on the existence of Virtual Consumers.</span></li><li><span style="color: rgb(0,0,0);">Support was added for sending scheduled message using message annotations when using AMQP.</span></li><li><span style="color: rgb(0,0,0);">The ability to dynamically shrink and regrow the store size at runtime based on available disk space.</span></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li><p>Currently 20 PMC members</p></li><li><p>New PMC members </p><ul><li><p>Christopher Shannon was added to the PMC on Sun Jan 24 2016</p></li><li><p>Jeff Genender was added to the PMC on Sun Jan 24 2016</p></li></ul></li></ul><p><strong>Committer base changes</strong></p><ul><li><p>Currently 56 committers</p></li><li><p>New commmitters</p><ul><li><p>Matt Richard Hogstrom was added as a committer on Thu Jan 28 2016 (not sure why he was added, got this info from <a shape="rect" class="external-link" href="http://reporter.apache.org">reporter.apache.org</a>)</p></li><li><p>John Robert Sisson was added as a committer on Thu Jan 28 2016 (not sure why he was added, got this info from <a shape="rect" class="external-link" href="http://reporter.apache.org/">reporter.apache.org</a>)</p></li></ul></li></ul><p><strong>Releases</strong></p><ul><li><p>Activemq-CPP v3.9.1 was released on Thu Dec 03 2015</p></li><li><p>Activemq-CPP v3.9.2 was released on Thu Feb 08 2016</p></li><li><p>5.11.3 was released on Sun Nov 01 2015</p></li><li><p>5.12.1 was released on Wed Oct 14 2015</p></li><li><p>5.12.2 was released on Sun Jan 10 2016</p></li><li><p>5.13.0 was released on Wed Dec 02 2015</p></li><li>5.13.1 was released on Fri Feb 05 2016</li><li><p>ActiveMQ Artemis 1.2.0 was released on Thu Jan 07 2016</p></li></ul><p><strong>Mailing list activity</strong></p><ul><li><p><a shape="rect" class="external-link" href="mailto:users@activemq.apache.org" rel="nofollow">users@activemq.apache.org</a></p><ul><li>716 subscribers (down -5 in the last 3 months)</li><li>816 emails sent to list (712 in previous quarter)</li></ul></li><li><p><a shape="rect" class="external-link" href="mailto:dev@activemq.apache.org" rel="nofollow">dev@activemq.apache.org</a></p><ul><li>344 subscribers (up 7 in the last 3 months)</li><li>837 emails sent to list (765 in previous quarter)</li></ul></li><li><p><a shape="rect" class="external-link" href="mailto:issues@activemq.apache.org" rel="nofollow">issues@activemq.apache.org</a></p><ul><li>35 subscribers (up 4 in the last 3 months)</li><li>2045 emails sent to list (1763 in previous quarter)</li></ul></li><li><p><a shape="rect" class="external-link" href="mailto:announce@activemq.apache.org" rel="nofollow">announce@activemq.apache.org</a></p><ul><li>9 subscribers (up 1 in the last 3 months)</li></ul></li></ul><p><strong>JIRA activity</strong></p><ul><li><p>233 JIRA tickets created in the last 3 months</p></li><li><p>257 JIRA tickets closed/resolved in the last 3 months</p></li></ul><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
+<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><p><span style="color: rgb(0,0,0);">Apache.NMS added a new provider implementation </span><strong style="color: rgb(0,0,0);line-height: 1.42857;">Apache.NMS.XMS</strong><span style="color: rgb(0,0,0);"> for connecting to IBM WebSphere MQSeries.  This was contributed by the user community, and based on the existing Apache.NMS provider implementation for TIBCO EMS.  There are now eight NMS provider implementations.</span></p></li><li><span style="color: rgb(0,0,0);">ActiveMQ 5.x added several new features in version 5.13.0</span><ul><li><span style="color: rgb(0,0,0);">There is now support for automatic wire protocol detection (OpenWire, STOMP, MQTT, and AMQP) using the new <link><page ri:content-title="AUTO"></page><plain-text-link-body>auto transport</plain-text-link-body></link>.</span></li><li><span style="color: rgb(0,0,0);">Improved metrics as the broker now keeps track of the memory size of pending messages.</span></li><li><span style="color: rgb(0,0,0);">A pure Java API for runtime configuration changes to the broker.  Previously only changes could be done in XML.</span></li><li><span style="color: rgb(0,0,0);">There is now support for <link ac:anchor="virtualconsumers"><page ri:content-title="Networks of Brokers"></page><plain-text-link-body>dynamic network demand</plain-text-link-body></link> based on the existence of Virtual Consumers.</span></li><li><span style="color: rgb(0,0,0);">Support was added for sending scheduled message using message annotations when using AMQP.</span></li><li><span style="color: rgb(0,0,0);">The ability to dynamically shrink and regrow the store size at runtime based on available disk space.</span></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li><p>Currently 20 PMC members</p></li><li><p>New PMC members </p><ul><li><p>Christopher Shannon was added to the PMC on Sun Jan 24 2016</p></li><li><p>Jeff Genender was added to the PMC on Sun Jan 24 2016</p></li></ul></li></ul><p><strong>Committer base changes</strong></p><ul><li><p>Currently 56 committers</p></li><li><p>New commmitters</p><ul><li><p>Matt Richard Hogstrom was added as a committer on Thu Jan 28 2016 (not sure why he was added, got this info from <a shape="rect" href="http://reporter.apache.org">reporter.apache.org</a>)</p></li><li><p>John Robert Sisson was added as a committer on Thu Jan 28 2016 (not sure why he was added, got this info from <a shape="rect" href="http://reporter.apache.org/">reporter.apache.org</a>)</p></li></ul></li></ul><p><strong>Releases</strong></p><ul><li><p>Activemq-CPP v3.9.1 was released on Thu Dec 03 2015</p></li><li><p>Activemq-CPP v3.9.2 was released on Thu Feb 08 2016</p></li><li><p>5.11.3 was released on Sun Nov 01 2015</p></li><li><p>5.12.1 was released on Wed Oct 14 2015</p></li><li><p>5.12.2 was released on Sun Jan 10 2016</p></li><li><p>5.13.0 was released on Wed Dec 02 2015</p></li><li>5.13.1 was released on Fri Feb 05 2016</li><li><p>ActiveMQ Artemis 1.2.0 was released on Thu Jan 07 2016</p></li></ul><p><strong>Mailing list activity</strong></p><ul><li><p><a shape="rect" href="mailto:users@activemq.apache.org">users@activemq.apache.org</a></p><ul><li>716 subscribers (down -5 in the last 3 months)</li><li>816 emails sent to list (712 in previous quarter)</li></ul></li><li><p><a shape="rect" href="mailto:dev@activemq.apache.org">dev@activemq.apache.org</a></p><ul><li>344 subscribers (up 7 in the last 3 months)</li><li>837 emails sent to list (765 in previous quarter)</li></ul></li><li><p><a shape="rect" href="mailto:issues@activemq.apache.org">issues@activemq.apache.org</a></p><ul><li>35 subscribers (up 4 in the last 3 months)</li><li>2045 emails sent to list (1763 in previous quarter)</li></ul></li><li><p><a shape="rect" href="mailto:announce@activemq.apache.org">announce@activemq.apache.org</a></p><ul><li>9 subscribers (up 1 in the last 3 months)</li></ul></li></ul><p><strong>JIRA activity</strong></p><ul><li><p>233 JIRA tickets created in the last 3 months</p></li><li><p>257 JIRA tickets closed/resolved in the last 3 months</p></li></ul><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
diff --git a/apache-activemq-board-report-201604-april.xml b/apache-activemq-board-report-201604-april.xml
index 6eb722f..d3de5aa 100644
--- a/apache-activemq-board-report-201604-april.xml
+++ b/apache-activemq-board-report-201604-april.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><p>Apache ActiveMQ Artemis has been working towards adding ActiveMQ 5.x equivalent features and client compatibility improvements:</p><ul><li><p>The OpenWire protocol module has been completely refactored, improvements include:</p><ul><li><span>Improved message encoding support with increased performance</span></li><li><p><span><span>Cluster connections can now be configured using ActiveMQ 5.x style URI</span></span></p></li></ul></li><li><p><span><span><span>Equivalent implementations of all ActiveMQ 5.x JAAS modules are now available in Artemis</span></span></span></p></li><li><p>Artemis has initial support for database backed Journal.</p></li><li><span>Various improvements and bug fixes to:</span><ul><li><p>HA Replication, STOMP protocol module, File Journal Storage.</p></li></ul></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li><p>Currently 20 PMC members</p></li></ul><p><strong>Committer base changes</strong></p><ul><li><p>Currently 56 committers</p></li></ul><p><strong>Releases</strong></p><ul><li><p><strong>5.13.2 was released on </strong>Fri Mar 04 2016</p></li><li><strong>AcitveMQ-CPP v3.9.3 </strong>on Thu Mar 31 2016</li><li><strong>Apache.NMS.ActiveMQ v1.7.2</strong> on Thu Apr 7 2016</li></ul><p><strong>Mailing list activity</strong></p><ul><li><p><a shape="rect" class="external-link" href="mailto:users@activemq.apache.org" rel="nofollow">users@activemq.apache.org</a></p><ul><li>TODO</li></ul></li><li><p><a shape="rect" class="external-link" href="mailto:dev@activemq.apache.org" rel="nofollow">dev@activemq.apache.org</a></p><ul><li>TODO</li></ul></li><li><p><a shape="rect" class="external-link" href="mailto:issues@activemq.apache.org" rel="nofollow">issues@activemq.apache.org</a></p><ul><li>TODO</li></ul></li><li><p><a shape="rect" class="external-link" href="mailto:announce@activemq.apache.org" rel="nofollow">announce@activemq.apache.org</a></p><ul><li>TODO</li></ul></li></ul><p><strong>JIRA activity</strong></p><ul><li><p>TODO</p></li></ul><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
+<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><p>Apache ActiveMQ Artemis has been working towards adding ActiveMQ 5.x equivalent features and client compatibility improvements:</p><ul><li><p>The OpenWire protocol module has been completely refactored, improvements include:</p><ul><li><span>Improved message encoding support with increased performance</span></li><li><p><span><span>Cluster connections can now be configured using ActiveMQ 5.x style URI</span></span></p></li></ul></li><li><p><span><span><span>Equivalent implementations of all ActiveMQ 5.x JAAS modules are now available in Artemis</span></span></span></p></li><li><p>Artemis has initial support for database backed Journal.</p></li><li><span>Various improvements and bug fixes to:</span><ul><li><p>HA Replication, STOMP protocol module, File Journal Storage.</p></li></ul></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li><p>Currently 20 PMC members</p></li></ul><p><strong>Committer base changes</strong></p><ul><li><p>Currently 56 committers</p></li></ul><p><strong>Releases</strong></p><ul><li><p><strong>5.13.2 was released on </strong>Fri Mar 04 2016</p></li><li><strong>AcitveMQ-CPP v3.9.3 </strong>on Thu Mar 31 2016</li><li><strong>Apache.NMS.ActiveMQ v1.7.2</strong> on Thu Apr 7 2016</li></ul><p><strong>Mailing list activity</strong></p><ul><li><p><a shape="rect" href="mailto:users@activemq.apache.org">users@activemq.apache.org</a></p><ul><li>TODO</li></ul></li><li><p><a shape="rect" href="mailto:dev@activemq.apache.org">dev@activemq.apache.org</a></p><ul><li>TODO</li></ul></li><li><p><a shape="rect" href="mailto:issues@activemq.apache.org">issues@activemq.apache.org</a></p><ul><li>TODO</li></ul></li><li><p><a shape="rect" href="mailto:announce@activemq.apache.org">announce@activemq.apache.org</a></p><ul><li>TODO</li></ul></li></ul><p><strong>JIRA activity</strong></p><ul><li><p>TODO</p></li></ul><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
diff --git a/apache-activemq-board-report-201605-may.xml b/apache-activemq-board-report-201605-may.xml
index 27ebc9b..6623aae 100644
--- a/apache-activemq-board-report-201605-may.xml
+++ b/apache-activemq-board-report-201605-may.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</span></p><p><strong><span style="color: rgb(102,0,51);">Past Activity</span></strong></p><ul><li><p>This report is being filed based on a request from some board members during the April 2016 meeting. The request is to recap the results of challenges within the ActiveMQ project during the 2014-2015 time frame</p><ul><li><span style="color: rgb(34,34,34);">The <a shape="rect" class="external-link" href="https://mail-search.apache.org/members/private-arch/board/201504.mbox/%3CCAGZ-RDL96UCbTzwsLznEBQykBHNhj_usw95VjeJ8cEiF4gef=A@mail.gmail.com%3E">April 2015 ActiveMQ Board Report</a> included <span style="color: rgb(34,34,34);">the following activities:</span></span><ul><li><span style="color: rgb(34,34,34);">Bruce Snyder elected to the PMC chair position</span></li><li><span style="color: rgb(34,34,34);">HornetQ code donation accepted</span></li></ul></li><li><span style="color: rgb(34,34,34);">The <a shape="rect" href="apache-activemq-board-report-201506-june.xml" rel="nofollow">June 2015 ActiveMQ Board Report</a> included the following activities:</span><ul><li><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">Donated code base renamed to ActiveMQ Artemis (based on a vote)</span> <br clear="none"></span><ul><li><span style="color: rgb(34,34,34);">The HornetQ code donation was officially renamed to ActiveMQ Artemis</span></li></ul></li><li><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">Marc Schöchlin</span> voted in as a committer</span></li><li><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">Jeff Genender</span> voted in as a committer<br clear="none"></span></li></ul></li><li><span class="il" style="color: rgb(34,34,34);">On 7 August, 2015, </span><a shape="rect" class="external-link" href="https://mail-search.apache.org/members/private-arch/board/201508.mbox/%3C55C52714.4090400@gmail.com%3E"><span class="il" style="color: rgb(34,34,34);">Hadrian</span><span style="color: rgb(34,34,34);"> Zbarcea </span><span class="il" style="color: rgb(34,34,34);">resigned</span><span style="color: rgb(34,34,34);"> the ActiveMQ PMC</span></a><ul><li>Unfortunately this activity was not noted in the <a shape="rect" href="apache-activemq-board-report-201508-august.xml" rel="nofollow">August 2015 ActiveMQ Board Report</a></li><li>I, Bruce Snyder, was still new to the position of PMC chair and failed to add this item to the board report</li></ul></li><li>The <a shape="rect" href="apache-activemq-board-report-201508-august.xml" rel="nofollow">August 2015 ActiveMQ Board Report</a> included the following activities:<ul><li>Christopher Shannon was added to the PMC</li></ul></li><li>The <a shape="rect" href="apache-activemq-board-report-201602-february.xml" rel="nofollow">February 2016 ActiveMQ Board Report</a> included the following activities:<ul><li><p>Christopher Shannon was added to the PMC on Sun Jan 24 2016</p></li><li><p>Jeff Genender was added to the PMC on Sun Jan 24 2016</p></li></ul></li></ul></li><li>Regarding the overarching question that was asked about the turmoil within the ActiveMQ project in 2014-2015 timeframe:<ul><li>Neither were there any disagreements in the second half of 2015 nor have there been any disagreements in 2016</li></ul></li></ul><p><strong><span style="color: rgb(102,0,51);">Current Activity</span></strong></p><ul><li>CHANGE ME</li></ul><p><strong><span style="color: rgb(102,0,51);"> </span></strong></p><p><strong><span style="color: rgb(102,0,51);"><br clear="none"></span></strong></p></div>
+<div class="wiki-content maincontent"><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</span></p><p><strong><span style="color: rgb(102,0,51);">Past Activity</span></strong></p><ul><li><p>This report is being filed based on a request from some board members during the April 2016 meeting. The request is to recap the results of challenges within the ActiveMQ project during the 2014-2015 time frame</p><ul><li><span style="color: rgb(34,34,34);">The <a shape="rect" href="https://mail-search.apache.org/members/private-arch/board/201504.mbox/%3CCAGZ-RDL96UCbTzwsLznEBQykBHNhj_usw95VjeJ8cEiF4gef=A@mail.gmail.com%3E">April 2015 ActiveMQ Board Report</a> included <span style="color: rgb(34,34,34);">the following activities:</span></span><ul><li><span style="color: rgb(34,34,34);">Bruce Snyder elected to the PMC chair position</span></li><li><span style="color: rgb(34,34,34);">HornetQ code donation accepted</span></li></ul></li><li><span style="color: rgb(34,34,34);">The <a shape="rect" href="apache-activemq-board-report-201506-june.xml">June 2015 ActiveMQ Board Report</a> included the following activities:</span><ul><li><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">Donated code base renamed to ActiveMQ Artemis (based on a vote)</span> <br clear="none"></span><ul><li><span style="color: rgb(34,34,34);">The HornetQ code donation was officially renamed to ActiveMQ Artemis</span></li></ul></li><li><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">Marc Schöchlin</span> voted in as a committer</span></li><li><span style="color: rgb(34,34,34);"><span style="color: rgb(34,34,34);">Jeff Genender</span> voted in as a committer<br clear="none"></span></li></ul></li><li><span class="il" style="color: rgb(34,34,34);">On 7 August, 2015, </span><a shape="rect" href="https://mail-search.apache.org/members/private-arch/board/201508.mbox/%3C55C52714.4090400@gmail.com%3E"><span class="il" style="color: rgb(34,34,34);">Hadrian</span><span style="color: rgb(34,34,34);"> Zbarcea </span><span class="il" style="color: rgb(34,34,34);">resigned</span><span style="color: rgb(34,34,34);"> the ActiveMQ PMC</span></a><ul><li>Unfortunately this activity was not noted in the <a shape="rect" href="apache-activemq-board-report-201508-august.xml">August 2015 ActiveMQ Board Report</a></li><li>I, Bruce Snyder, was still new to the position of PMC chair and failed to add this item to the board report</li></ul></li><li>The <a shape="rect" href="apache-activemq-board-report-201508-august.xml">August 2015 ActiveMQ Board Report</a> included the following activities:<ul><li>Christopher Shannon was added to the PMC</li></ul></li><li>The <a shape="rect" href="apache-activemq-board-report-201602-february.xml">February 2016 ActiveMQ Board Report</a> included the following activities:<ul><li><p>Christopher Shannon was added to the PMC on Sun Jan 24 2016</p></li><li><p>Jeff Genender was added to the PMC on Sun Jan 24 2016</p></li></ul></li></ul></li><li>Regarding the overarching question that was asked about the turmoil within the ActiveMQ project in 2014-2015 timeframe:<ul><li>Neither were there any disagreements in the second half of 2015 nor have there been any disagreements in 2016</li></ul></li></ul><p><strong><span style="color: rgb(102,0,51);">Current Activity</span></strong></p><ul><li>CHANGE ME</li></ul><p><strong><span style="color: rgb(102,0,51);"> </span></strong></p><p><strong><span style="color: rgb(102,0,51);"><br clear="none"></span></strong></p></div>
diff --git a/apache-activemq-board-report-201607-july.xml b/apache-activemq-board-report-201607-july.xml
index cf61db8..23dd9db 100644
--- a/apache-activemq-board-report-201607-july.xml
+++ b/apache-activemq-board-report-201607-july.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">The ActiveMQ Broker continues to see continued bug fixes and feature additions</span></span></span><ul><li><span style="color: rgb(0,0,0);">Support added for AMQP over WebSockets added for inclusion in 5.14.0</span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Improvements to the KahaDB message store allowing for better store clean up.</span></span></span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Important fixes continue to be ported to the 5.13.x branch and a new 5.13.4 release is nearing release readiness.</span></span></span></li></ul></li></ul><ul><li><span style="color: rgb(0,0,0);">ActiveMQ Artemis continues working towards adding ActiveMQ 5.x equivalent features, client compatibility and improvements:</span></li></ul><ul><ul><li><p><span style="color: rgb(0,0,0);">The OpenWire protocol implementation is now feature complete</span></p></li><li><p><span style="color: rgb(0,0,0);">The Database journal has been improved and support added for</span>:</p><ul><li><p><span style="color: rgb(0,0,0);">MySQL</span></p></li><li><p><span style="color: rgb(0,0,0);">PostgreSQL</span></p></li></ul></li><li><p><span style="color: rgb(0,0,0);">Database storage for large messages has been added</span></p></li><li><p><span style="color: rgb(0,0,0);">HA using replication has been heavily tested and had several improvements</span></p></li><li><p><span style="color: rgb(0,0,0);">The AMQP protocol has had a lot of attention including many fixes and support for AMQP link drain and subscription addresses</span></p></li><li><p><span style="color: rgb(0,0,0);">MQTT protocol has been updated to support interceptors and cross protocol communication</span></p></li><li><p><span style="color: rgb(0,0,0);">Dual-authentication is now supported so SSL and non-SSL connections can be authenticated by different JAAS login modules.</span></p></li><li><p><span style="color: rgb(0,0,0);">The broker's SSL keystores can now be reloaded on demand without stopping the broker.</span></p></li><li><p><span style="color: rgb(0,0,0);">JMS topics are now auto-created by default when a producer sends a message or a client subscribes.</span></p></li><li><p><span style="color: rgb(0,0,0);">The name of the authenticated user can now be automatically added to the messages it sends.</span></p></li><li><p><span style="color: rgb(0,0,0);">STOMP clients can now have their authentication and authorization based on their SSL certificate.</span></p></li><li><p><span style="color: rgb(0,0,0);">Lots of smaller bug fixes and performance improvements</span><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><br clear="none"></span></span></span></p></li></ul></ul><div><span style="color: rgb(0,0,0);"><br clear="none"></span></div><p><strong>PMC changes</strong></p><ul><li>Currently 23 PMC members</li><li><span style="color: rgb(34,34,34);">Martyn Taylor was added to the PMC on Sun Jul 10 2016</span></li><li>Last PMC addition: <span style="color: rgb(34,34,34);">Sun Jul 10 2016 (Martyn Taylor)</span></li></ul><p><br clear="none"><strong>Committer base changes</strong></p><ul><li>Currently 56 committers</li><li>No new committers added in the last 3 months</li><li>Last committer addition was Matt Richard Hogstrom at Thu Jan 28 2016</li></ul><p><br clear="none"><strong>Releases</strong></p><ul><li>5.13.3 was released on Sun May 01 2016</li><li>ActiveMQ Artemis 1.3.0 was released on Tue Jun 14 2016</li><li>Apache.NMS.ActiveMQ v1.7.2 was released on Wed Apr 06 2016</li></ul><p><strong>Mailing list activity</strong></p><ul><li><a shape="rect" class="external-link" href="mailto:users@activemq.apache.org" rel="nofollow">users@activemq.apache.org</a><ul><li>741 subscribers (up 14 in the last 3 months)</li><li><span style="line-height: 1.42857;">638 emails sent to list (837 in previous quarter)</span></li></ul></li></ul><ul><li><a shape="rect" class="external-link" href="mailto:dev@activemq.apache.org" rel="nofollow">dev@activemq.apache.org</a><ul><li>367 subscribers (up 14 in the last 3 months)</li><li><span style="line-height: 1.42857;">909 emails sent to list (653 in previous quarter)</span></li></ul></li></ul><ul><li><a shape="rect" class="external-link" href="mailto:announce@activemq.apache.org" rel="nofollow">announce@activemq.apache.org</a><ul><li><a shape="rect" class="external-link" href="mailto:announce@activemq.apache.org" rel="nofollow"></a>9 subscribers (up 0 in the last 3 months)</li></ul></li></ul><ul><li><a shape="rect" class="external-link" href="mailto:issues@activemq.apache.org" rel="nofollow">issues@activemq.apache.org</a><ul><li>43 subscribers (up 3 in the last 3 months)</li><li>2159 emails sent to list (1698 in previous quarter)</li></ul></li></ul><p> </p><p><strong>JIRA activity</strong></p><ul><li>261 JIRA tickets created in the last 3 months</li><li>262 JIRA tickets closed/resolved in the last 3 months</li></ul><p> </p><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
+<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 1.1, J2EE 1.4, AMQP 1.0.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">The ActiveMQ Broker continues to see continued bug fixes and feature additions</span></span></span><ul><li><span style="color: rgb(0,0,0);">Support added for AMQP over WebSockets added for inclusion in 5.14.0</span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Improvements to the KahaDB message store allowing for better store clean up.</span></span></span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Important fixes continue to be ported to the 5.13.x branch and a new 5.13.4 release is nearing release readiness.</span></span></span></li></ul></li></ul><ul><li><span style="color: rgb(0,0,0);">ActiveMQ Artemis continues working towards adding ActiveMQ 5.x equivalent features, client compatibility and improvements:</span></li></ul><ul><ul><li><p><span style="color: rgb(0,0,0);">The OpenWire protocol implementation is now feature complete</span></p></li><li><p><span style="color: rgb(0,0,0);">The Database journal has been improved and support added for</span>:</p><ul><li><p><span style="color: rgb(0,0,0);">MySQL</span></p></li><li><p><span style="color: rgb(0,0,0);">PostgreSQL</span></p></li></ul></li><li><p><span style="color: rgb(0,0,0);">Database storage for large messages has been added</span></p></li><li><p><span style="color: rgb(0,0,0);">HA using replication has been heavily tested and had several improvements</span></p></li><li><p><span style="color: rgb(0,0,0);">The AMQP protocol has had a lot of attention including many fixes and support for AMQP link drain and subscription addresses</span></p></li><li><p><span style="color: rgb(0,0,0);">MQTT protocol has been updated to support interceptors and cross protocol communication</span></p></li><li><p><span style="color: rgb(0,0,0);">Dual-authentication is now supported so SSL and non-SSL connections can be authenticated by different JAAS login modules.</span></p></li><li><p><span style="color: rgb(0,0,0);">The broker's SSL keystores can now be reloaded on demand without stopping the broker.</span></p></li><li><p><span style="color: rgb(0,0,0);">JMS topics are now auto-created by default when a producer sends a message or a client subscribes.</span></p></li><li><p><span style="color: rgb(0,0,0);">The name of the authenticated user can now be automatically added to the messages it sends.</span></p></li><li><p><span style="color: rgb(0,0,0);">STOMP clients can now have their authentication and authorization based on their SSL certificate.</span></p></li><li><p><span style="color: rgb(0,0,0);">Lots of smaller bug fixes and performance improvements</span><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><br clear="none"></span></span></span></p></li></ul></ul><div><span style="color: rgb(0,0,0);"><br clear="none"></span></div><p><strong>PMC changes</strong></p><ul><li>Currently 23 PMC members</li><li><span style="color: rgb(34,34,34);">Martyn Taylor was added to the PMC on Sun Jul 10 2016</span></li><li>Last PMC addition: <span style="color: rgb(34,34,34);">Sun Jul 10 2016 (Martyn Taylor)</span></li></ul><p><br clear="none"><strong>Committer base changes</strong></p><ul><li>Currently 56 committers</li><li>No new committers added in the last 3 months</li><li>Last committer addition was Matt Richard Hogstrom at Thu Jan 28 2016</li></ul><p><br clear="none"><strong>Releases</strong></p><ul><li>5.13.3 was released on Sun May 01 2016</li><li>ActiveMQ Artemis 1.3.0 was released on Tue Jun 14 2016</li><li>Apache.NMS.ActiveMQ v1.7.2 was released on Wed Apr 06 2016</li></ul><p><strong>Mailing list activity</strong></p><ul><li><a shape="rect" href="mailto:users@activemq.apache.org">users@activemq.apache.org</a><ul><li>741 subscribers (up 14 in the last 3 months)</li><li><span style="line-height: 1.42857;">638 emails sent to list (837 in previous quarter)</span></li></ul></li></ul><ul><li><a shape="rect" href="mailto:dev@activemq.apache.org">dev@activemq.apache.org</a><ul><li>367 subscribers (up 14 in the last 3 months)</li><li><span style="line-height: 1.42857;">909 emails sent to list (653 in previous quarter)</span></li></ul></li></ul><ul><li><a shape="rect" href="mailto:announce@activemq.apache.org">announce@activemq.apache.org</a><ul><li><a shape="rect" href="mailto:announce@activemq.apache.org"></a>9 subscribers (up 0 in the last 3 months)</li></ul></li></ul><ul><li><a shape="rect" href="mailto:issues@activemq.apache.org">issues@activemq.apache.org</a><ul><li>43 subscribers (up 3 in the last 3 months)</li><li>2159 emails sent to list (1698 in previous quarter)</li></ul></li></ul><p> </p><p><strong>JIRA activity</strong></p><ul><li>261 JIRA tickets created in the last 3 months</li><li>262 JIRA tickets closed/resolved in the last 3 months</li></ul><p> </p><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
diff --git a/apache-activemq-board-report-201610-october.xml b/apache-activemq-board-report-201610-october.xml
index 921a850..950142e 100644
--- a/apache-activemq-board-report-201610-october.xml
+++ b/apache-activemq-board-report-201610-october.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li>Overall, the project health is very stable. No disgreements in the community and the folks on the project are working together on both ActiveMQ and Artemis. The ActiveMQ code base continues to grow and improve and it is pushing releases more frequently as was the plan. Activity with the Artemis code base continues its successful march toward full compatibility with ActiveMQ.</li></ul><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><br clear="none"></span></span></span><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><span style="color: rgb(34,34,34);">Active Discussions around a new web console</span></span></span></span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><span style="color: rgb(34,34,34);">The project is a little stuck on the docker issues pending infra and legal </span><span style="color: rgb(34,34,34);">resolution</span><br clear="none"></span></span></span></li></ul></li><li><p><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></p><ul><li><p><span style="color: rgb(0,0,0);">Apache Artemis 1.4.0 Released</span></p></li><li><p><span style="color: rgb(0,0,0);">AMQP 1.0 implementation improvements</span></p><ul><li><p><span style="color: rgb(0,0,0);">Local transaction support improved</span></p></li><li><p><span style="color: rgb(0,0,0);">Multi-session-per-tx and multi-tx-per-session capabilities support</span></p></li><li><p><span style="color: rgb(0,0,0);">Support for OASIS AMQP JMS mappings for JMS 1.1 over AMQP 1.0 added</span></p></li><li><p><span style="color: rgb(0,0,0);">Major refactor of the AMQP implementation making it simpler and easier to understand</span></p></li></ul></li><li><p><span style="color: rgb(34,34,34);">[</span><span class="il" style="color: rgb(34,34,34);">CVE</span><span style="color: rgb(34,34,34);">-2016-4978] Apache ActiveMQ Artemis: Deserialization of untrusted input vunerability.</span></p><ul><li><p><span style="color: rgb(34,34,34);">Fixed in Apache Artemis 1.4.0</span></p></li><li><p><span style="color: rgb(34,34,34);">Announcement made</span></p></li></ul></li><li><p><span style="color: rgb(34,34,34);">Support for setting global limits (total memory and disk utilization) added</span></p></li><li><p><span style="color: rgb(34,34,34);">Basic Java EE CDI integration added</span></p></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li>Currently 23 PMC members</li><li>No new PMC members added in the last 3 months</li><li>Last PMC addition was Martyn Taylor on Fri Jul 08 2016 </li></ul><p><strong>Committer base changes</strong></p><ul><li>Currently 57 committers</li><li>John D. Ament was added as a committer on Mon Aug 08 2016</li></ul><p><strong>Releases</strong></p><ul><li>5.13.4 was released on Mon Jul 18 2016</li><li>5.14.0 was released on Thu Aug 04 2016</li><li>5.14.1 was released on Thu Sep 29 2016</li><li>ActiveMQ Artemis 1.4.0 was released on Mon Sep 12 2016</li></ul><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
+<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li>Overall, the project health is very stable. No disgreements in the community and the folks on the project are working together on both ActiveMQ and Artemis. The ActiveMQ code base continues to grow and improve and it is pushing releases more frequently as was the plan. Activity with the Artemis code base continues its successful march toward full compatibility with ActiveMQ.</li></ul><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><br clear="none"></span></span></span><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><span style="color: rgb(34,34,34);">Active Discussions around a new web console</span></span></span></span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><span style="color: rgb(34,34,34);">The project is a little stuck on the docker issues pending infra and legal </span><span style="color: rgb(34,34,34);">resolution</span><br clear="none"></span></span></span></li></ul></li><li><p><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></p><ul><li><p><span style="color: rgb(0,0,0);">Apache Artemis 1.4.0 Released</span></p></li><li><p><span style="color: rgb(0,0,0);">AMQP 1.0 implementation improvements</span></p><ul><li><p><span style="color: rgb(0,0,0);">Local transaction support improved</span></p></li><li><p><span style="color: rgb(0,0,0);">Multi-session-per-tx and multi-tx-per-session capabilities support</span></p></li><li><p><span style="color: rgb(0,0,0);">Support for OASIS AMQP JMS mappings for JMS 1.1 over AMQP 1.0 added</span></p></li><li><p><span style="color: rgb(0,0,0);">Major refactor of the AMQP implementation making it simpler and easier to understand</span></p></li></ul></li><li><p><span style="color: rgb(34,34,34);">[</span><span class="il" style="color: rgb(34,34,34);">CVE</span><span style="color: rgb(34,34,34);">-2016-4978] Apache ActiveMQ Artemis: Deserialization of untrusted input vunerability.</span></p><ul><li><p><span style="color: rgb(34,34,34);">Fixed in Apache Artemis 1.4.0</span></p></li><li><p><span style="color: rgb(34,34,34);">Announcement made</span></p></li></ul></li><li><p><span style="color: rgb(34,34,34);">Support for setting global limits (total memory and disk utilization) added</span></p></li><li><p><span style="color: rgb(34,34,34);">Basic Java EE CDI integration added</span></p></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li>Currently 23 PMC members</li><li>No new PMC members added in the last 3 months</li><li>Last PMC addition was Martyn Taylor on Fri Jul 08 2016 </li></ul><p><strong>Committer base changes</strong></p><ul><li>Currently 57 committers</li><li>John D. Ament was added as a committer on Mon Aug 08 2016</li></ul><p><strong>Releases</strong></p><ul><li>5.13.4 was released on Mon Jul 18 2016</li><li>5.14.0 was released on Thu Aug 04 2016</li><li>5.14.1 was released on Thu Sep 29 2016</li><li>ActiveMQ Artemis 1.4.0 was released on Mon Sep 12 2016</li></ul><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
diff --git a/apache-activemq-board-report-201701-january.xml b/apache-activemq-board-report-201701-january.xml
index 55089f0..fce8778 100644
--- a/apache-activemq-board-report-201701-january.xml
+++ b/apache-activemq-board-report-201701-january.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Continued hardening of AMQP protocol support</span></span></span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Fixes to some memory leaks and deadlocks added</span></span></span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Latest release now supports Jetty releases in the 9.3.x family.</span></span></span><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><br clear="none"></span></span></span></li></ul></li><li><p><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></p></li><ul><li><p><span style="color: rgb(0,0,0);">Apache Artemis 1.5.0 released with follow up of 1.5.1 maintenance release.  Highlights:</span></p><ul><li><p><span style="color: rgb(0,0,0);">Outgoing AMQP connections supported<br clear="none"></span></p></li><li><p><span style="color: rgb(0,0,0);">The ability to broker to detect network failures was added</span></p></li><li><p><span style="color: rgb(0,0,0);">CDI Integration was added</span></p></li></ul></li><li><p><span style="color: rgb(0,0,0);">Apache Artemis 2.0.0 is planned which i</span><span style="color: rgb(0,0,0);">ncludes major overhaul of the Artemis addressing model</span></p></li><ul><li><p><span style="color: rgb(0,0,0);">New model has been proposed and implemented, highlights include:</span></p></li><ul><li><p><span style="color: rgb(0,0,0);">Better support for address naming across protocols added<br clear="none"></span></p></li><li><p><span style="color: rgb(0,0,0);">Ability to define prefixes for specifying pub/sub and point to point messaging requirements added</span></p></li><li><p><span style="color: rgb(0,0,0);">Consolidation of JMS and other protocol management/configuration</span><span style="color: rgb(0,0,0);"><br clear="none"></span></p></li></ul></ul></ul><li><span style="color: rgb(0,0,0);">Both projects are now base-lined on Java 8</span></li><li><span style="color: rgb(0,0,0);">Begin blogging about the ActiveMQ project on <a shape="rect" class="external-link" href="https://blogs.apache.org/">https://blogs.apache.org/</a></span></li></ul><p><strong>PMC changes</strong></p><ul><li>Currently 23 PMC members</li><li>Clebert Suconic was added to the PMC on Thu Oct 27 2016</li></ul><p><strong>Committer base changes</strong></p><ul><li>Currently 58 committers</li><li>Christian Schneider was added as a committer on Wed Jan 04 2017</li></ul><p><strong>Releases</strong></p><ul><li>5.13.5 was released on Mon Dec 19 2016</li><li>5.14.2 was released on Wed Dec 07 2016</li><li>5.14.3 was released on Wed Dec 21 2016</li><li>ActiveMQ Artemis 1.5.0 was released on Mon Nov 07 2016</li><li>ActiveMQ Artemis 1.5.1 was released on Thu Dec 08 2016</li></ul><pre> </pre><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
+<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Continued hardening of AMQP protocol support</span></span></span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Fixes to some memory leaks and deadlocks added</span></span></span></li><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">Latest release now supports Jetty releases in the 9.3.x family.</span></span></span><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);"><br clear="none"></span></span></span></li></ul></li><li><p><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></p></li><ul><li><p><span style="color: rgb(0,0,0);">Apache Artemis 1.5.0 released with follow up of 1.5.1 maintenance release.  Highlights:</span></p><ul><li><p><span style="color: rgb(0,0,0);">Outgoing AMQP connections supported<br clear="none"></span></p></li><li><p><span style="color: rgb(0,0,0);">The ability to broker to detect network failures was added</span></p></li><li><p><span style="color: rgb(0,0,0);">CDI Integration was added</span></p></li></ul></li><li><p><span style="color: rgb(0,0,0);">Apache Artemis 2.0.0 is planned which i</span><span style="color: rgb(0,0,0);">ncludes major overhaul of the Artemis addressing model</span></p></li><ul><li><p><span style="color: rgb(0,0,0);">New model has been proposed and implemented, highlights include:</span></p></li><ul><li><p><span style="color: rgb(0,0,0);">Better support for address naming across protocols added<br clear="none"></span></p></li><li><p><span style="color: rgb(0,0,0);">Ability to define prefixes for specifying pub/sub and point to point messaging requirements added</span></p></li><li><p><span style="color: rgb(0,0,0);">Consolidation of JMS and other protocol management/configuration</span><span style="color: rgb(0,0,0);"><br clear="none"></span></p></li></ul></ul></ul><li><span style="color: rgb(0,0,0);">Both projects are now base-lined on Java 8</span></li><li><span style="color: rgb(0,0,0);">Begin blogging about the ActiveMQ project on <a shape="rect" href="https://blogs.apache.org/">https://blogs.apache.org/</a></span></li></ul><p><strong>PMC changes</strong></p><ul><li>Currently 23 PMC members</li><li>Clebert Suconic was added to the PMC on Thu Oct 27 2016</li></ul><p><strong>Committer base changes</strong></p><ul><li>Currently 58 committers</li><li>Christian Schneider was added as a committer on Wed Jan 04 2017</li></ul><p><strong>Releases</strong></p><ul><li>5.13.5 was released on Mon Dec 19 2016</li><li>5.14.2 was released on Wed Dec 07 2016</li><li>5.14.3 was released on Wed Dec 21 2016</li><li>ActiveMQ Artemis 1.5.0 was released on Mon Nov 07 2016</li><li>ActiveMQ Artemis 1.5.1 was released on Thu Dec 08 2016</li></ul><pre> </pre><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
diff --git a/apache-activemq-board-report-201704-april.xml b/apache-activemq-board-report-201704-april.xml
index 6fbf21e..394f1db 100644
--- a/apache-activemq-board-report-201704-april.xml
+++ b/apache-activemq-board-report-201704-april.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color: rgb(0,0,0);">The 5.x broker continues to see ongoing bug fixing and stabilization work.</span><span style="color: rgb(0,0,0);"><br clear="none"></span></li></ul></li><li><p><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></p></li><ul><li><p><span style="color: rgb(0,0,0);">Continued work on broker performance especially around the AMQP protocol.</span></p></li><li><span style="color: rgb(0,0,0);">Artemis now uses Netty Epoll on platforms that support it providing improved performance at the network layer.<br clear="none"></span></li></ul><li><span style="color: rgb(0,0,0);">ActiveMQ Other</span><ul><li><span style="color: rgb(0,0,0);">A new tooling project aimed at provided a simple means of migrating data from existing ActiveMQ 5.x brokers to Artemis install has started.</span></li><li><span style="color: rgb(0,0,0);">The ActiveMQ NMS project had its SVN repositories migrated to Git to make future contributions simpler.</span><span style="color: rgb(0,0,0);"> </span></li><li><span style="color: rgb(0,0,0);">Discussion in the community around donation of work on a new ActiveMQ NMS AMQP client implementation.<br clear="none"></span></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li>Currently 24 PMC members</li><li>Clebert Suconic was added to the PMC on Thu Oct 27 2016</li></ul><p><strong>Committer base changes</strong></p><ul><li>Currently 58 committers</li><li>Christian Schneider was added as a committer on Wed Jan 04 2017</li></ul><p><strong>Releases</strong></p><ul><li><strong>ActiveMQ 5.14.4</strong><span style="color: rgb(34,34,34);"> was released on Wed Mar 01 2017</span></li><li><strong>ActiveMQ Artemis 1.5.3</strong><span style="color: rgb(34,34,34);"> was released on Sun Feb 19 2017</span></li><li><strong>ActiveMQ Artemis 1.5.4</strong><span style="color: rgb(34,34,34);"> was released on Sun Mar 12 2017</span></li><li><strong>ActiveMQ Artemis 2.0.0</strong><span style="color: rgb(34,34,34);"> was released on Sun Mar 19 2017</span></li><li><strong>ActiveMQ-CPP v3.9.4</strong><span style="color: rgb(34,34,34);"> was released on Wed Feb 22 2017</span></li></ul><pre> </pre><p>Report submitted on 11 Apr 2017</p><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
+<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color: rgb(0,0,0);">The 5.x broker continues to see ongoing bug fixing and stabilization work.</span><span style="color: rgb(0,0,0);"><br clear="none"></span></li></ul></li><li><p><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></p></li><ul><li><p><span style="color: rgb(0,0,0);">Continued work on broker performance especially around the AMQP protocol.</span></p></li><li><span style="color: rgb(0,0,0);">Artemis now uses Netty Epoll on platforms that support it providing improved performance at the network layer.<br clear="none"></span></li></ul><li><span style="color: rgb(0,0,0);">ActiveMQ Other</span><ul><li><span style="color: rgb(0,0,0);">A new tooling project aimed at provided a simple means of migrating data from existing ActiveMQ 5.x brokers to Artemis install has started.</span></li><li><span style="color: rgb(0,0,0);">The ActiveMQ NMS project had its SVN repositories migrated to Git to make future contributions simpler.</span><span style="color: rgb(0,0,0);"> </span></li><li><span style="color: rgb(0,0,0);">Discussion in the community around donation of work on a new ActiveMQ NMS AMQP client implementation.<br clear="none"></span></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li>Currently 24 PMC members</li><li>Clebert Suconic was added to the PMC on Thu Oct 27 2016</li></ul><p><strong>Committer base changes</strong></p><ul><li>Currently 58 committers</li><li>Christian Schneider was added as a committer on Wed Jan 04 2017</li></ul><p><strong>Releases</strong></p><ul><li><strong>ActiveMQ 5.14.4</strong><span style="color: rgb(34,34,34);"> was released on Wed Mar 01 2017</span></li><li><strong>ActiveMQ Artemis 1.5.3</strong><span style="color: rgb(34,34,34);"> was released on Sun Feb 19 2017</span></li><li><strong>ActiveMQ Artemis 1.5.4</strong><span style="color: rgb(34,34,34);"> was released on Sun Mar 12 2017</span></li><li><strong>ActiveMQ Artemis 2.0.0</strong><span style="color: rgb(34,34,34);"> was released on Sun Mar 19 2017</span></li><li><strong>ActiveMQ-CPP v3.9.4</strong><span style="color: rgb(34,34,34);"> was released on Wed Feb 22 2017</span></li></ul><pre> </pre><p>Report submitted on 11 Apr 2017</p><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
diff --git a/apache-activemq-board-report-201707-july.xml b/apache-activemq-board-report-201707-july.xml
index fd9f8a8..5eb21ee 100644
--- a/apache-activemq-board-report-201707-july.xml
+++ b/apache-activemq-board-report-201707-july.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color: rgb(0,0,0);">Work continues on bug fixes and hardening of the ActiveMQ 5.x broker.<br clear="none"></span></li><li><span style="color: rgb(0,0,0);">New 5.15.0 release is out which now requires Java 8 and includes the latest Camel 2.19.0 release</span></li></ul><span style="color: rgb(0,0,0);"><br clear="none"></span></li><li><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></li></ul><ul><li style="list-style-type: none;background-image: none;"><ul><li><span style="color: rgb(0,0,0);">Continued work on adding new features with several active discussions both on the mailing list and in JIRA and PR comments around the implementation of those features and their affect on existing usecases from members of the community. <br clear="none"></span></li><li><span style="color: rgb(0,0,0);">Improving AMQP support</span></li><li><span style="color: rgb(0,0,0);">Many fixes around compatibility with older clients.</span></li></ul></li></ul><ul><li><span style="color: rgb(0,0,0);">ActiveMQ Other</span><ul><li><span style="color: rgb(0,0,0);">The community has opened up a call for new Logo's for the project website, a vote to pick a winner is expected late July.<br clear="none"></span></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li>Last PMC addition: <span style="color: rgb(34,34,34);">Thu Oct 27 2016 (Clebert Suconic)</span></li><li>Currently 24 PMC members</li></ul><p><strong>Committer base changes</strong></p><ul><li>Currently 59 committers. </li><li>Francesco Nigro was added as a committer on Tue May 09 2017 </li></ul><p><strong>Releases</strong></p><ul><li>5.14.5 was released on Sun Apr 16 2017</li><li>5.15.0 was released on Thu Jun 29 2017</li><li>ActiveMQ Artemis 1.5.5 was released on Sun May 14 2017</li><li>ActiveMQ Artemis 2.1.0 was released on Sun May 14 2017</li><li>ActiveMQ CLI Tools 0.1.0 was released on Sun May 07 2017</li></ul><p>Report submitted: 11 Jul 2017</p><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
+<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color: rgb(0,0,0);">Work continues on bug fixes and hardening of the ActiveMQ 5.x broker.<br clear="none"></span></li><li><span style="color: rgb(0,0,0);">New 5.15.0 release is out which now requires Java 8 and includes the latest Camel 2.19.0 release</span></li></ul><span style="color: rgb(0,0,0);"><br clear="none"></span></li><li><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></li></ul><ul><li style="list-style-type: none;background-image: none;"><ul><li><span style="color: rgb(0,0,0);">Continued work on adding new features with several active discussions both on the mailing list and in JIRA and PR comments around the implementation of those features and their affect on existing usecases from members of the community. <br clear="none"></span></li><li><span style="color: rgb(0,0,0);">Improving AMQP support</span></li><li><span style="color: rgb(0,0,0);">Many fixes around compatibility with older clients.</span></li></ul></li></ul><ul><li><span style="color: rgb(0,0,0);">ActiveMQ Other</span><ul><li><span style="color: rgb(0,0,0);">The community has opened up a call for new Logo's for the project website, a vote to pick a winner is expected late July.<br clear="none"></span></li></ul></li></ul><p><strong>PMC changes</strong></p><ul><li>Last PMC addition: <span style="color: rgb(34,34,34);">Thu Oct 27 2016 (Clebert Suconic)</span></li><li>Currently 24 PMC members</li></ul><p><strong>Committer base changes</strong></p><ul><li>Currently 59 committers. </li><li>Francesco Nigro was added as a committer on Tue May 09 2017 </li></ul><p><strong>Releases</strong></p><ul><li>5.14.5 was released on Sun Apr 16 2017</li><li>5.15.0 was released on Thu Jun 29 2017</li><li>ActiveMQ Artemis 1.5.5 was released on Sun May 14 2017</li><li>ActiveMQ Artemis 2.1.0 was released on Sun May 14 2017</li><li>ActiveMQ CLI Tools 0.1.0 was released on Sun May 07 2017</li></ul><p>Report submitted: 11 Jul 2017</p><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p></div>
diff --git a/apache-activemq-board-report-201710-october.xml b/apache-activemq-board-report-201710-october.xml
index b674e3d..5de0cee 100644
--- a/apache-activemq-board-report-201710-october.xml
+++ b/apache-activemq-board-report-201710-october.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color: rgb(0,0,0);">ActiveMQ 5.15.1 released on Oct 2nd</span></li></ul></li><li><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></li></ul><ul><li style="list-style-type: none;background-image: none;"><ul><li>Artemis 2.3.0 was released on Sept 13th</li><li>Artemis 2.2.0 was released on July 31st</li><li>An embedded web management console was added</li><li>The download page was refreshed to improve clarity and ease future maintenance</li></ul></li></ul><ul><li><span style="color: rgb(0,0,0);">ActiveMQ Other</span><ul><li><span style="color: rgb(0,0,0);"> </span>A new logo was selected by community vote following a period of open submissions.<span style="color: rgb(0,0,0);"> </span><span style="color: rgb(0,0,0);"><span style="color: rgb(0,0,0);"> </span></span></li><li><p>The website was updated to use the new logo and slightly freshen the look.</p></li><li><p>Some release process improvements were discussed and implemented.</p></li></ul></li></ul><p><strong><span style="color: rgb(102,0,51);">Releases</span></strong></p><p> </p><ul><li><strong>5.15.1</strong><span style="color: rgb(34,34,34);"> was released on Sun Oct 01 2017</span></li><li><strong>ActiveMQ Artemis 2.2.0</strong><span style="color: rgb(34,34,34);"> was released on Sun Jul 30 2017</span></li></ul><p> </p><p>Report submitted on 10 Oct 2017</p><p>(Most of this information is pulled from <a shape="rect" class="external-link" href="https://reporter.apache.org/">reporter.apache.org</a>)</p><p> </p></div>
+<div class="wiki-content maincontent"><p><strong>Description</strong></p><p><span style="color: rgb(102,0,51);">Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and REST.</span></p><p><strong><span style="color: rgb(102,0,51);">Activity</span></strong></p><ul><li><span style="color: rgb(255,0,0);"><span style="color: rgb(0,51,102);"><span style="color: rgb(0,0,0);">ActiveMQ</span></span></span><ul><li><span style="color: rgb(0,0,0);">ActiveMQ 5.15.1 released on Oct 2nd</span></li></ul></li><li><span style="color: rgb(0,0,0);">ActiveMQ Artemis</span></li></ul><ul><li style="list-style-type: none;background-image: none;"><ul><li>Artemis 2.3.0 was released on Sept 13th</li><li>Artemis 2.2.0 was released on July 31st</li><li>An embedded web management console was added</li><li>The download page was refreshed to improve clarity and ease future maintenance</li></ul></li></ul><ul><li><span style="color: rgb(0,0,0);">ActiveMQ Other</span><ul><li><span style="color: rgb(0,0,0);"> </span>A new logo was selected by community vote following a period of open submissions.<span style="color: rgb(0,0,0);"> </span><span style="color: rgb(0,0,0);"><span style="color: rgb(0,0,0);"> </span></span></li><li><p>The website was updated to use the new logo and slightly freshen the look.</p></li><li><p>Some release process improvements were discussed and implemented.</p></li></ul></li></ul><p><strong><span style="color: rgb(102,0,51);">Releases</span></strong></p><p> </p><ul><li><strong>5.15.1</strong><span style="color: rgb(34,34,34);"> was released on Sun Oct 01 2017</span></li><li><strong>ActiveMQ Artemis 2.2.0</strong><span style="color: rgb(34,34,34);"> was released on Sun Jul 30 2017</span></li></ul><p> </p><p>Report submitted on 10 Oct 2017</p><p>(Most of this information is pulled from <a shape="rect" href="https://reporter.apache.org/">reporter.apache.org</a>)</p><p> </p></div>
diff --git a/apache-activemq-board-report-april-2008.xml b/apache-activemq-board-report-april-2008.xml
index cfdce8b..987f3d3 100644
--- a/apache-activemq-board-report-april-2008.xml
+++ b/apache-activemq-board-report-april-2008.xml
@@ -1,10 +1,9 @@
-<div class="wiki-content maincontent"><h1 id="ApacheActiveMQBoardReport-April2008-StatusreportfortheApacheActiveMQProject">Status report for the Apache ActiveMQ Project</h1>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<div class="wiki-content maincontent"><h1>Status report for the Apache ActiveMQ Project</h1>
+<structured-macro ac:macro-id="f353b1d5-8149-4612-80d5-170391ccdfe7" ac:name="code" ac:schema-version="1"><parameter ac:name="">none</parameter><plain-text-body>
Community:
The ActiveMQ community continues to stay vibrant with a very healthy amount of email traffic
- flowing through it's email lists. It has also added several new committers to it's ranks.
+ flowing through it's email lists. It has also added several new committers to it's ranks.
New Committers:
@@ -36,6 +35,5 @@
* Apache ActiveMQ
* Apache Camel
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/apache-activemq-board-reports.xml b/apache-activemq-board-reports.xml
index aa2f889..6da4828 100644
--- a/apache-activemq-board-reports.xml
+++ b/apache-activemq-board-reports.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The current ActiveMQ reporting schedule is: January, April, July, October</p><p></p><ul class="childpages-macro"><li><a shape="rect" href="apache-activemq-board-report-201710-october.xml">Apache ActiveMQ Board Report - 2017.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-201707-july.xml">Apache ActiveMQ Board Report - 2017.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-201704-april.xml">Apache ActiveMQ Board Report - 2017.04 (April)</a></li><li><a shape="rect" href="apache-activemq-board-report-201701-january.xml">Apache ActiveMQ Board Report - 2017.01 (January)</a></li><li><a shape="rect" href="apache-activemq-board-report-201610-october.xml">Apache ActiveMQ Board Report - 2016.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-201607-july.xml">Apache ActiveMQ Board Report - 2016.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-201605-may.xml">Apache ActiveMQ Board Report - 2016.05 (May)</a></li><li><a shape="rect" href="apache-activemq-board-report-201604-april.xml">Apache ActiveMQ Board Report - 2016.04 (April)</a></li><li><a shape="rect" href="apache-activemq-board-report-201602-february.xml">Apache ActiveMQ Board Report - 2016.02 (February)</a></li><li><a shape="rect" href="apache-activemq-board-report-201510-october.xml">Apache ActiveMQ Board Report - 2015.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-201508-august.xml">Apache ActiveMQ Board Report - 2015.08 (August)</a></li><li><a shape="rect" href="apache-activemq-board-report-201507-july.xml">Apache ActiveMQ Board Report - 2015.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-201506-june.xml">Apache ActiveMQ Board Report - 2015.06 (June)</a></li><li><a shape="rect" href="apache-activemq-board-report-201504-april.xml">Apache ActiveMQ Board Report - 2015.04 (April)</a></li><li><a shape="rect" href="apache-activemq-board-report-201502-february.xml">Apache ActiveMQ Board Report - 2015.02 (February)</a></li><li><a shape="rect" href="apache-activemq-board-report-201410-october.xml">Apache ActiveMQ Board Report - 2014.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-201407-july.xml">Apache ActiveMQ Board Report - 2014.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-201404-april.xml">Apache ActiveMQ Board Report - 2014.04 (April)</a></li><li><a shape="rect" href="apache-activemq-board-report-201401-january.xml">Apache ActiveMQ Board Report - 2014.01 (January)</a></li><li><a shape="rect" href="apache-activemq-board-report-201310-october.xml">Apache ActiveMQ Board Report - 2013.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-201307-july.xml">Apache ActiveMQ Board Report - 2013.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-201304-april.xml">Apache ActiveMQ Board Report - 2013.04 (April)</a></li><li><a shape="rect" href="apache-activemq-board-report-201301-january.xml">Apache ActiveMQ Board Report - 2013.01 (January)</a></li><li><a shape="rect" href="apache-activemq-board-report-201210-october.xml">Apache ActiveMQ Board Report - 2012.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-201207-july.xml">Apache ActiveMQ Board Report - 2012.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-201204-april.xml">Apache ActiveMQ Board Report - 2012.04 (April)</a></li><li><a shape="rect" href="apache-activemq-board-report-201201-january.xml">Apache ActiveMQ Board Report - 2012.01 (January)</a></li><li><a shape="rect" href="apache-activemq-board-report-201110-october.xml">Apache ActiveMQ Board Report - 2011.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-201107-july.xml">Apache ActiveMQ Board Report - 2011.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-201104-april.xml">Apache ActiveMQ Board Report - 2011.04 (April)</a></li><li><a shape="rect" href="apache-activemq-board-report-201101-january.xml">Apache ActiveMQ Board Report - 2011.01 (January)</a></li><li><a shape="rect" href="apache-activemq-board-report-201010-october.xml">Apache ActiveMQ Board Report - 2010.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-201007-july.xml">Apache ActiveMQ Board Report - 2010.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-201005-may.xml">Apache ActiveMQ Board Report - 2010.05 (May)</a></li><li><a shape="rect" href="apache-activemq-board-report-201001-january.xml">Apache ActiveMQ Board Report - 2010.01 (January)</a></li><li><a shape="rect" href="apache-activemq-board-report-200910-october.xml">Apache ActiveMQ Board Report - 2009.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-200907-july.xml">Apache ActiveMQ Board Report - 2009.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-200904-april.xml">Apache ActiveMQ Board Report - 2009.04 (April)</a></li><li><a shape="rect" href="apache-activemq-board-report-200901-january.xml">Apache ActiveMQ Board Report - 2009.01 (January)</a></li><li><a shape="rect" href="apache-activemq-board-report-200810-october.xml">Apache ActiveMQ Board Report - 2008.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-200807-july.xml">Apache ActiveMQ Board Report - 2008.07 (July)</a></li><li><a shape="rect" href="apache-activemq-board-report-200801-january.xml">Apache ActiveMQ Board Report - 2008.01 (January)</a></li><li><a shape="rect" href="apache-activemq-board-report-200710-october.xml">Apache ActiveMQ Board Report - 2007.10 (October)</a></li><li><a shape="rect" href="apache-activemq-board-report-200708-august.xml">Apache ActiveMQ Board Report - 2007.08 (August)</a></li></ul></div>
+<div class="wiki-content maincontent"><p>The current ActiveMQ reporting schedule is: January, April, July, October</p><p><structured-macro ac:macro-id="ebb67c1d-3c7d-4164-acf1-1a0b9d62908a" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="sort">title</parameter><parameter ac:name="reverse">true</parameter></structured-macro></p></div>
diff --git a/articles.xml b/articles.xml
index c1239dc..7be92ef 100644
--- a/articles.xml
+++ b/articles.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>This page captures resources and articles outside the ActiveMQ project which may assist your development. Please add any new resources that you come across by clicking the edit link at the bottom of the page. If you do this, please make sure to attach a date to the article as well so users are aware of how recent it is.</p><h3 id="Articles-InterviewsandPodcasts">Interviews and Podcasts</h3><ul><li><a shape="rect" class="external-link" href="http://feathercast.org/?p=42" rel="nofollow">ActiveMQ FeatherCast</a>, James Strachan is interviewed on the ActiveMQ project</li></ul><h3 id="Articles-Webinars,VideosandScreencasts">Webinars, Videos and Screencasts</h3><ul><li><a shape="rect" class="external-link" href="http://download.progress.com/5331/open/adobe/prc/psc/perf_tuning_activemq/index.htm" rel="nofollow">Apache ActiveMQ - Connecting Applications everywhere</a> by <em><a shape="rect" class="external-link" href="http://rajdavies.blogspot.com/" rel="nofollow">Rob Davies</a></em></li><li><a shape="rect" class="external-link" href="http://download.progress.com/5331/open/adobe/prc/psc/perf_tuning_activemq/index.htm" rel="nofollow">Performance Tuning ActiveMQ webinar </a> <em>by <a shape="rect" class="external-link" href="http://rajdavies.blogspot.com/" rel="nofollow">Rob Davies</a></em></li><li><a shape="rect" class="external-link" href="http://fusesource.com/resources/video-archived-webinars/" rel="nofollow">FuseSource Webinars</a> - Upcoming and archived webinars on Apache ActiveMQ and other related Apache products.</li><li><a shape="rect" class="external-link" href="http://fusesource.com/resources/fuse-tv/" rel="nofollow">FuseSource TV</a> - webcasts about Apache ActiveMQ and related Apache projects.</li></ul><h3 id="Articles-ArticlesonActiveMQ,MessagingandJMS">Articles on ActiveMQ, Messaging and JMS</h3><h4 id="Articles-GeneralArticles">General Articles</h4><ul><li><a shape="rect" class="external-link" href="http://blog.payara.fish/connecting-to-activemq-with-payara-server" rel="nofollow">Connecting to ActiveMQ with Payara Server</a> by Steve Millidge (December, 2015)</li><li><a shape="rect" class="external-link" href="http://de.slideshare.net/dejanb/messaging-for-web-and-mobile-with-apache-activemq" rel="nofollow">Messaging for Web and Mobile with Apache ActiveMQ</a> by <a shape="rect" class="external-link" href="http://Dejan Bosanac" rel="nofollow">Dejan Bosanac</a> (June, 2013)</li><li><a shape="rect" class="external-link" href="http://de.slideshare.net/bruce.snyder/activemq-in-action" rel="nofollow">ActiveMQ in Action: Common Problems and Solutions</a> by Bruce Snyder (July, 2011)</li><li><a shape="rect" class="external-link" href="http://blog.phatboyg.com/2009/07/12/accessing-activemq-on-mac-osx-from-a-windows-vm/" rel="nofollow">Accessing ActiveMQ on Mac OSX from a Windows VM</a></li><li><a shape="rect" class="external-link" href="http://www.theserverlabs.com/blog/2009/01/22/flex-with-jms-using-blazeds-jetty-and-activemq/" rel="nofollow">Flex with JMS using BlazeDS, Jetty and ActiveMQ</a> <em>by Kevin McCormack</em> (January, 2009)</li><li><a shape="rect" class="external-link" href="http://christopherhunt-software.blogspot.com/2009/03/mutual-ssl-authentication-and-ldap.html" rel="nofollow">Mutual SSL authentication and LDAP authorisation for ActiveMQ</a> <em>by <a shape="rect" class="external-link" href="http://christopherhunt-software.blogspot.com" rel="nofollow">Christopher Hunt</a></em> (March, 2009)</li><li><a shape="rect" class="external-link" href="http://www.slideshare.net/carsonified/dopplr-its-made-of-messages-matt-biddulph-presentation" rel="nofollow">Made of Messages</a> <em>by Matt Biddulph of <a shape="rect" class="external-link" href="http://www.dopplr.com/" rel="nofollow">Dopplr</a></em></li><li><a shape="rect" class="external-link" href="http://mmartinsoftware.blogspot.com/2008/05/simplified-blazeds-and-jms.html" rel="nofollow">Simplified BlazeDS and JMS article</a> <em>by <a shape="rect" class="external-link" href="http://mmartinsoftware.blogspot.com/" rel="nofollow">Michael Martin</a></em> (May, 2008)</li><li><a shape="rect" class="external-link" href="http://ourcraft.wordpress.com/2008/07/03/trying-out-xa/" rel="nofollow">Trying out XA</a> with ActiveMQ <em>by Daniel Meyer</em> (July, 2008)</li><li><a shape="rect" class="external-link" href="http://latrz.com/2586" rel="nofollow">Squawk (simple queues using awk)</a> <em>by <a shape="rect" class="external-link" href="http://www.nobugs.org/blog/" rel="nofollow">Andrew Birkett</a></em></li><li><a shape="rect" class="external-link" href="http://p-st.blogspot.com/2007/12/activemq-and-rest.html" rel="nofollow">Using ActiveMQ and REST</a> <em>by <a shape="rect" class="external-link" href="http://p-st.blogspot.com/" rel="nofollow">marlet</a></em> (December, 2007)</li><li><a shape="rect" class="external-link" href="http://esammer.blogspot.com/2007/09/apache-activemq-and-perl.html" rel="nofollow">Apache ActiveMQ and Perl</a> (September, 2007)</li><li><a shape="rect" class="external-link" href="http://remark.wordpress.com/articles/publish-subscribe-with-activemq-and-nms/" rel="nofollow">Publish-Subscribe with ActiveMQ and NMS</a></li><li><a shape="rect" class="external-link" href="http://note19.com/2007/06/24/activemq-masterslave-setup/" rel="nofollow">ActiveMQ Master/Slave Setup</a></li><li><a shape="rect" class="external-link" href="http://weblogs.java.net/blog/rampsarathy/archive/2007/03/glassfish_v2_an.html" rel="nofollow">GlassFish and ActiveMQ</a> <em>by Ramesh Parthasarathy</em> (March, 2007)</li><li><a shape="rect" class="external-link" href="http://jroller.com/page/sjivan?entry=asynchronous_calls_and_callbacks_using" rel="nofollow">Asynchronous calls and callbacks with Lingo and ActiveMQ</a> <em>by Sanjiv Jivan</em> (May, 2006)</li><li><a shape="rect" class="external-link" href="http://www-128.ibm.com/developerworks/opensource/library/os-ag-jmsbeans/" rel="nofollow">Magic with JMS, MDBs, and ActiveMQ in Geronimo</a> <em>by Sing Li</em> (July, 2005)</li><li><a shape="rect" class="external-link" href="http://remark.wordpress.com/articles/implementing-request-response-with-activemq-and-nms/" rel="nofollow">Implementing Request-Response with ActiveMQ and NMS</a> <em>by Mark</em></li><li><a shape="rect" class="external-link" href="http://www.christianposta.com/blog/?p=273" rel="nofollow">Understanding Memory Usage</a> <em>by Christian Posta</em> gives an overview and dive into the memory usage of the broker.</li></ul><h4 id="Articles-ActiveMQMaintenanceandMonitoring">ActiveMQ Maintenance and Monitoring</h4><ul><li><a shape="rect" class="external-link" href="http://www.bennet-schulz.com/2016/07/apache-activemq-and-hawtio.html" rel="nofollow">Running ActiveMQ and hawtio in Standalone Mode</a> by <a shape="rect" class="external-link" href="https://twitter.com/bennetelli" rel="nofollow">Bennet Schulz</a> (July, 2016)</li><li><a shape="rect" class="external-link" href="http://sensatic.net/activemq/activemq-and-hawtio.html" rel="nofollow">Management and monitoring ActiveMQ using hawtio</a> (how to install hawtio out of  the box in ActiveMQ) by Dejan Bosanac (April 2014)</li><li><a shape="rect" class="external-link" href="http://it.toolbox.com/blogs/unix-sysadmin/monitoring-activemq-from-nagios-27743" rel="nofollow">Monitoring ActiveMQ from Nagios</a> <em>by <a shape="rect" class="external-link" href="http://it.toolbox.com/people/therek/" rel="nofollow">Cezary Morga</a></em></li><li><a shape="rect" class="external-link" href="http://soatechlab.blogspot.com/2008/01/use-jconsole-with-activemq-for-quick.html" rel="nofollow">Use JConsole with ActiveMQ for a quick JMS test client</a> <em>by <a shape="rect" class="external-link" href="http://soatechlab.blogspot.com/" rel="nofollow">Rod Biresch</a></em> (January 2008)</li><li><a shape="rect" class="external-link" href="http://www.oreillynet.com/onjava/blog/2007/06/integrating_activemq_web_conso.html" rel="nofollow">Integrating ActiveMQ Web Console</a> <em>by <a shape="rect" class="external-link" href="http://www.oreillynet.com/pub/au/1763" rel="nofollow">Dejan Bosanac</a></em> (June 2007)</li><li><a shape="rect" class="external-link" href="http://hermesjms.com/demos/messagestores.html" rel="nofollow">Hermes Message Stores with ActiveMQ demo</a> <em>by Colin Crist</em></li></ul><h4 id="Articles-ActiveMQandDatabases">ActiveMQ and Databases</h4><ul><li><a shape="rect" class="external-link" href="http://barkingiguana.com/2008/12/16/high-availability-activemq-using-a-mysql-datastore" rel="nofollow">High Availability ActiveMQ using MySQL and Ruby</a> <em>by <a shape="rect" class="external-link" href="http://barkingiguana.com/" rel="nofollow">Craig R Webster</a></em> (December 2008)</li><li><a shape="rect" class="external-link" href="http://trenaman.blogspot.com/2008/09/setting-up-postgresql-database-for.html" rel="nofollow">Setting up a PostgreSQL database for ActiveMQ</a> <em>by <a shape="rect" class="external-link" href="http://trenaman.blogspot.com/" rel="nofollow">Adrian Trenaman</a></em> (September 2008)</li><li><a shape="rect" class="external-link" href="http://note19.com/2007/06/23/configure-activemq-with-mysql/" rel="nofollow">Configure ActiveMQ with MySQL</a> <em>By Shahram Javey</em> (June 2007)</li></ul><h4 id="Articles-ActiveMQandSpring">ActiveMQ and Spring</h4><ul><li><a shape="rect" class="external-link" href="https://github.com/bsnyder/spring-jms-examples" rel="nofollow">Spring JMS Examples with ActiveMQ</a> by <a shape="rect" class="external-link" href="https://bsnyderblog.blogspot.com/" rel="nofollow">Bruce Snyder</a> (June 2011)</li><li><a shape="rect" class="external-link" href="https://bsnyderblog.blogspot.com/2010/05/tuning-jms-message-consumption-in.html" rel="nofollow">Tuning JMS Message Consumption In Spring</a> by <a shape="rect" class="external-link" href="https://bsnyderblog.blogspot.com/" rel="nofollow">Bruce Snyder</a> (May 2010)</li><li><a shape="rect" class="external-link" href="http://codedependents.com/2010/03/04/synchronous-request-response-with-activemq-and-spring/" rel="nofollow">Synchronous Request Response with ActiveMQ and Spring</a> <em>by <a shape="rect" class="external-link" href="http://codedependents.com/" rel="nofollow">CodeDependents</a></em> (March 2010)</li><li><a shape="rect" class="external-link" href="https://bsnyderblog.blogspot.com/2010/02/using-spring-to-receive-jms-messages.html" rel="nofollow">Using Spring to Receive JMS Messages</a> by <a shape="rect" class="external-link" href="https://bsnyderblog.blogspot.com/" rel="nofollow">Bruce Snyder</a> (February 2010)</li><li><a shape="rect" class="external-link" href="https://bsnyderblog.blogspot.com/2010/02/using-spring-jmstemplate-to-send-jms.html" rel="nofollow">Using Spring to Send JMS Messages</a> by <a shape="rect" class="external-link" href="https://bsnyderblog.blogspot.com/" rel="nofollow">Bruce Snyder</a> (February 2010)</li><li><a shape="rect" class="external-link" href="http://codedependents.com/2009/10/16/efficient-lightweight-jms-with-spring-and-activemq/" rel="nofollow">Efficient Lightweight JMS with Spring and ActiveMQ</a> <em>by <a shape="rect" class="external-link" href="http://codedependents.com/" rel="nofollow">CodeDependents</a></em> (Octover 2009)</li><li><a shape="rect" class="external-link" href="http://javaandjava.blogspot.com/2008/10/activemq-message-consumer-in-spring.html" rel="nofollow">ActiveMQ Message Consumer in Spring</a> <em>by <a shape="rect" class="external-link" href="http://javaandjava.blogspot.com/" rel="nofollow">Saveen Kumar</a></em> (October 2008)</li><li><a shape="rect" class="external-link" href="http://www.springframework.org/node/527" rel="nofollow">Message-Driven Architectures at The Spring Experience</a> <em>by Keith Donald</em> (September 2007)</li></ul><h4 id="Articles-ActiveMQwithJRuby/Ruby,Railsand/orStomp">ActiveMQ with JRuby/Ruby, Rails and/or Stomp</h4><ul><li><a shape="rect" class="external-link" href="http://beechbonanza.blogspot.com/2007/07/jruby-jms-as-replacement-for.html" rel="nofollow">JRuby JMS as a replacement for ActiveMessaging</a></li><li><a shape="rect" class="external-link" href="http://nutrun.com/weblog/jms-with-jruby-and-activemq/" rel="nofollow">JMS with JRuby and ActiveMQ</a></li><li><a shape="rect" class="external-link" href="http://romjethoughts.blogspot.com/2007/05/first-steps-with-rubystomp-and-activemq.html" rel="nofollow">First Steps on Ruby/STOMP and ActiveMQ</a> <em>by <a shape="rect" class="external-link" href="http://romjethoughts.blogspot.com/" rel="nofollow">jerome moliere</a></em></li><li><a shape="rect" class="external-link" href="http://beechbonanza.blogspot.com/2007/06/asynchronous-messaging-with-rails.html" rel="nofollow">Asynchronous Messaging with Rails</a> <em>by <a shape="rect" class="external-link" href="http://beechbonanza.blogspot.com/" rel="nofollow">Shane Harvie</a></em></li><li><a shape="rect" class="external-link" href="http://notdennisbyrne.blogspot.com/2007/06/integrating-rails-and-activemq-with.html" rel="nofollow">Integrating Rails and ActiveMQ with ActiveMessaging/REST</a> <em>by <a shape="rect" class="external-link" href="http://notdennisbyrne.blogspot.com/" rel="nofollow">(not) Dennis Byrne</a></em></li><li><a shape="rect" class="external-link" href="http://ramesh-rubyonrails.blogspot.com/2007/09/asynchronous-messaging-using-rails.html" rel="nofollow">Asynchronous Messaging using Rails</a></li><li><a shape="rect" class="external-link" href="http://www.infoq.com/articles/intro-active-messaging-rails" rel="nofollow">Introduction to ActiveMessaging, using Rails with ActiveMQ or Stomp</a> <em>by Andrew Kuklewicz</em></li><li><a shape="rect" class="external-link" href="http://flexonrails.net/?p=83" rel="nofollow">Flex, Rails, ActiveMQ and Stomp</a> <em>by <a shape="rect" class="external-link" href="http://flexonrails.net" rel="nofollow">Flex On Rails</a></em></li><li><a shape="rect" class="external-link" href="http://just-another.net/2008/09/03/activemq-stomp-end-end-test-nagios/" rel="nofollow">ActiveMQ stomp end to end test for nagios</a> <em>by <a shape="rect" class="external-link" href="http://just-another.net/" rel="nofollow">Benjamin Smith</a></em></li><li><a shape="rect" class="external-link" href="http://www.kaazing.org/confluence/display/Doc/JavaScript+STOMP+Client+How-To" rel="nofollow">How to Create a Stomp-Driven Application in JavaScript Using Apache ActiveMQ as a Message Broker</a> <em>by <a shape="rect" class="external-link" href="http://www.kaazing.org/confluence/display/KAAZING/Home" rel="nofollow">Kaazing</a></em></li><li><a shape="rect" class="external-link" href="http://cometdaily.com/2008/10/08/scalable-real-time-web-architecture-part-1-stomp-comet-and-message-queues/" rel="nofollow">Scalable Real-Time Web Architecture, Part 1: Stomp, Comet, and Message Queues</a> <em>by <a shape="rect" class="external-link" href="http://cometdaily.com/people/michael_carter/" rel="nofollow">Michael Carter</a></em></li></ul><h4 id="Articles-ActiveMQand.NET">ActiveMQ and .NET</h4><ul><li><a shape="rect" class="external-link" href="http://remark.wordpress.com/articles/messaging-with-net-and-activemq/" rel="nofollow">Messaging with .NET and ActiveMQ</a> <em>by <a shape="rect" class="external-link" href="http://remark.wordpress.com/" rel="nofollow">Re.Mark</a></em></li><li><a shape="rect" class="external-link" href="http://remark.wordpress.com/articles/messaging-with-net-and-activemq/" rel="nofollow">Using .Net and ActiveMQ</a> <em>by <a shape="rect" class="external-link" href="http://remark.wordpress.com/" rel="nofollow">Re.Mark</a></em></li></ul><h3 id="Articles-MessageBrokerComparison">Message Broker Comparison</h3><ul><li><a shape="rect" class="external-link" href="http://bhavin.directi.com/rabbitmq-vs-apache-activemq-vs-apache-qpid/" rel="nofollow">RabbitMQ vs Apache ActiveMQ vs Apache qpid </a> <em>by Bhavin Turakhia</em> (May, 2010)</li><li><a shape="rect" class="external-link" href="http://www.nighttale.net/activemq/python-messaging-activemq-and-rabbitmq.html" rel="nofollow">Python messaging: ActiveMQ and RabbitMQ</a> <em>by Night Tale</em></li><li><a shape="rect" class="external-link" href="http://stackoverflow.com/questions/32851/multicasting-messaging-activemq-vs-msmq" rel="nofollow">Multicasting, Messaging, ActiveMQ vs. MSMQ?</a> <em>by stackoverflow.com</em></li><li><a shape="rect" class="external-link" href="http://www.fiorano.com/whitepapers/java-message-service/JMS-performance-comparison.php" rel="nofollow">JMS Performance Comparison</a> <em>by www.fiarano.com</em></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/how-does-activemq-compare-to-jbossmq.html">How does ActiveMQ compare to JBossMQ</a></li><li><a shape="rect" class="external-link" href="http://www.mail-archive.com/activemq-users@geronimo.apache.org/msg05630.html" rel="nofollow">Why use ActiveMQ over JBossMQ?</a></li><li><a shape="rect" class="external-link" href="http://www.manning-sandbox.com/thread.jspa?threadID=39270&tstart=45" rel="nofollow">Thread: ActiveMQ vs Websphere MQ </a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/how-does-activemq-compare-to-mule.html">How does ActiveMQ compare to Mule?</a></li><li><a shape="rect" class="external-link" href="http://www.roklee.com/?p=52" rel="nofollow">HornetQ 2.0GA vs ActiveMQ 5.3 – feature by feature comparison</a> <em>by www.roklee.com</em></li><li><a shape="rect" class="external-link" href="http://www.theserverside.com/discussions/thread.tss?thread_id=57192" rel="nofollow">Performance and scalability: Analysis and comparison of ActiveMQ, Websphere MQ and SonicMQ</a></li><li><a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-vs-Camel-vs-Qpid-td2355914.html" rel="nofollow">ActiveMQ vs. Camel vs. Qpid </a></li></ul><h3 id="Articles-ActiveMQtoolingandscripts">ActiveMQ tooling and scripts</h3><ul><li><a shape="rect" class="external-link" href="https://github.com/ebuzzing/bash-mq" rel="nofollow">Bash-MQ</a> - a bash/awk producer/consumer for activemq or any STOMP compatible MQ</li></ul><h3 id="Articles-BooksandReferenceGuides">Books and Reference Guides</h3><ul><li>Beside these extract of interviews, articles and videos there are also some books available. Take a look at the <a shape="rect" href="books.xml">Books</a> page.</li></ul><h3 id="Articles-AdditionalResources">Additional Resources</h3><ul><li>Many of the Commercial Providers listed on the <a shape="rect" href="support.xml">Support</a> page provide additional examples, articles, tutorials, documentation, etc...</li></ul><h3 id="Articles-ActiveMQbloggers">ActiveMQ bloggers</h3><ul><li><a shape="rect" class="external-link" href="http://rajdavies.blogspot.com/" rel="nofollow">Rob Davies</a></li><li><a shape="rect" class="external-link" href="http://hiramchirino.com/blog/" rel="nofollow">Hiram Chirino</a></li><li><a shape="rect" class="external-link" href="http://blog.garytully.com/" rel="nofollow">Gary Tully</a></li><li><a shape="rect" class="external-link" href="http://www.nighttale.net" rel="nofollow">Dejan Bosanac</a></li><li><a shape="rect" class="external-link" href="http://bruceblog.org/" rel="nofollow">Bruce Snyder</a></li><li><a shape="rect" class="external-link" href="http://www.christianposta.com/blog" rel="nofollow">Christian Posta</a></li></ul></div>
+<div class="wiki-content maincontent"><p>This page captures resources and articles outside the ActiveMQ project which may assist your development. Please add any new resources that you come across by clicking the edit link at the bottom of the page. If you do this, please make sure to attach a date to the article as well so users are aware of how recent it is.</p><h3>Interviews and Podcasts</h3><ul><li><a shape="rect" href="http://feathercast.org/?p=42">ActiveMQ FeatherCast</a>, James Strachan is interviewed on the ActiveMQ project</li></ul><h3>Webinars, Videos and Screencasts</h3><ul><li><a shape="rect" href="http://download.progress.com/5331/open/adobe/prc/psc/perf_tuning_activemq/index.htm">Apache ActiveMQ - Connecting Applications everywhere</a> by <em><a shape="rect" href="http://rajdavies.blogspot.com/">Rob Davies</a></em></li><li><a shape="rect" href="http://download.progress.com/5331/open/adobe/prc/psc/perf_tuning_activemq/index.htm">Performance Tuning ActiveMQ webinar </a> <em>by <a shape="rect" href="http://rajdavies.blogspot.com/">Rob Davies</a></em></li><li><a shape="rect" href="http://fusesource.com/resources/video-archived-webinars/">FuseSource Webinars</a> - Upcoming and archived webinars on Apache ActiveMQ and other related Apache products.</li><li><a shape="rect" href="http://fusesource.com/resources/fuse-tv/">FuseSource TV</a> - webcasts about Apache ActiveMQ and related Apache projects.</li></ul><h3>Articles on ActiveMQ, Messaging and JMS</h3><h4>General Articles</h4><ul><li><a shape="rect" href="http://blog.payara.fish/connecting-to-activemq-with-payara-server">Connecting to ActiveMQ with Payara Server</a> by Steve Millidge (December, 2015)</li><li><a shape="rect" href="http://de.slideshare.net/dejanb/messaging-for-web-and-mobile-with-apache-activemq">Messaging for Web and Mobile with Apache ActiveMQ</a> by <a shape="rect" href="http://Dejan Bosanac">Dejan Bosanac</a> (June, 2013)</li><li><a shape="rect" href="http://de.slideshare.net/bruce.snyder/activemq-in-action">ActiveMQ in Action: Common Problems and Solutions</a> by Bruce Snyder (July, 2011)</li><li><a shape="rect" href="http://blog.phatboyg.com/2009/07/12/accessing-activemq-on-mac-osx-from-a-windows-vm/">Accessing ActiveMQ on Mac OSX from a Windows VM</a></li><li><a shape="rect" href="http://www.theserverlabs.com/blog/2009/01/22/flex-with-jms-using-blazeds-jetty-and-activemq/">Flex with JMS using BlazeDS, Jetty and ActiveMQ</a> <em>by Kevin McCormack</em> (January, 2009)</li><li><a shape="rect" href="http://christopherhunt-software.blogspot.com/2009/03/mutual-ssl-authentication-and-ldap.html">Mutual SSL authentication and LDAP authorisation for ActiveMQ</a> <em>by <a shape="rect" href="http://christopherhunt-software.blogspot.com">Christopher Hunt</a></em> (March, 2009)</li><li><a shape="rect" href="http://www.slideshare.net/carsonified/dopplr-its-made-of-messages-matt-biddulph-presentation">Made of Messages</a> <em>by Matt Biddulph of <a shape="rect" href="http://www.dopplr.com/">Dopplr</a></em></li><li><a shape="rect" href="http://mmartinsoftware.blogspot.com/2008/05/simplified-blazeds-and-jms.html">Simplified BlazeDS and JMS article</a> <em>by <a shape="rect" href="http://mmartinsoftware.blogspot.com/">Michael Martin</a></em> (May, 2008)</li><li><a shape="rect" href="http://ourcraft.wordpress.com/2008/07/03/trying-out-xa/">Trying out XA</a> with ActiveMQ <em>by Daniel Meyer</em> (July, 2008)</li><li><a shape="rect" href="http://latrz.com/2586">Squawk (simple queues using awk)</a> <em>by <a shape="rect" href="http://www.nobugs.org/blog/">Andrew Birkett</a></em></li><li><a shape="rect" href="http://p-st.blogspot.com/2007/12/activemq-and-rest.html">Using ActiveMQ and REST</a> <em>by <a shape="rect" href="http://p-st.blogspot.com/">marlet</a></em> (December, 2007)</li><li><a shape="rect" href="http://esammer.blogspot.com/2007/09/apache-activemq-and-perl.html">Apache ActiveMQ and Perl</a> (September, 2007)</li><li><a shape="rect" href="http://remark.wordpress.com/articles/publish-subscribe-with-activemq-and-nms/">Publish-Subscribe with ActiveMQ and NMS</a></li><li><a shape="rect" href="http://note19.com/2007/06/24/activemq-masterslave-setup/">ActiveMQ Master/Slave Setup</a></li><li><a shape="rect" href="http://weblogs.java.net/blog/rampsarathy/archive/2007/03/glassfish_v2_an.html">GlassFish and ActiveMQ</a> <em>by Ramesh Parthasarathy</em> (March, 2007)</li><li><a shape="rect" href="http://jroller.com/page/sjivan?entry=asynchronous_calls_and_callbacks_using">Asynchronous calls and callbacks with Lingo and ActiveMQ</a> <em>by Sanjiv Jivan</em> (May, 2006)</li><li><a shape="rect" href="http://www-128.ibm.com/developerworks/opensource/library/os-ag-jmsbeans/">Magic with JMS, MDBs, and ActiveMQ in Geronimo</a> <em>by Sing Li</em> (July, 2005)</li><li><a shape="rect" href="http://remark.wordpress.com/articles/implementing-request-response-with-activemq-and-nms/">Implementing Request-Response with ActiveMQ and NMS</a> <em>by Mark</em></li><li><a shape="rect" href="http://www.christianposta.com/blog/?p=273">Understanding Memory Usage</a> <em>by Christian Posta</em> gives an overview and dive into the memory usage of the broker.</li></ul><h4>ActiveMQ Maintenance and Monitoring</h4><ul><li><a shape="rect" href="http://www.bennet-schulz.com/2016/07/apache-activemq-and-hawtio.html">Running ActiveMQ and hawtio in Standalone Mode</a> by <a shape="rect" href="https://twitter.com/bennetelli">Bennet Schulz</a> (July, 2016)</li><li><a shape="rect" href="http://sensatic.net/activemq/activemq-and-hawtio.html">Management and monitoring ActiveMQ using hawtio</a> (how to install hawtio out of  the box in ActiveMQ) by Dejan Bosanac (April 2014)</li><li><a shape="rect" href="http://it.toolbox.com/blogs/unix-sysadmin/monitoring-activemq-from-nagios-27743">Monitoring ActiveMQ from Nagios</a> <em>by <a shape="rect" href="http://it.toolbox.com/people/therek/">Cezary Morga</a></em></li><li><a shape="rect" href="http://soatechlab.blogspot.com/2008/01/use-jconsole-with-activemq-for-quick.html">Use JConsole with ActiveMQ for a quick JMS test client</a> <em>by <a shape="rect" href="http://soatechlab.blogspot.com/">Rod Biresch</a></em> (January 2008)</li><li><a shape="rect" href="http://www.oreillynet.com/onjava/blog/2007/06/integrating_activemq_web_conso.html">Integrating ActiveMQ Web Console</a> <em>by <a shape="rect" href="http://www.oreillynet.com/pub/au/1763">Dejan Bosanac</a></em> (June 2007)</li><li><a shape="rect" href="http://hermesjms.com/demos/messagestores.html">Hermes Message Stores with ActiveMQ demo</a> <em>by Colin Crist</em></li></ul><h4>ActiveMQ and Databases</h4><ul><li><a shape="rect" href="http://barkingiguana.com/2008/12/16/high-availability-activemq-using-a-mysql-datastore">High Availability ActiveMQ using MySQL and Ruby</a> <em>by <a shape="rect" href="http://barkingiguana.com/">Craig R Webster</a></em> (December 2008)</li><li><a shape="rect" href="http://trenaman.blogspot.com/2008/09/setting-up-postgresql-database-for.html">Setting up a PostgreSQL database for ActiveMQ</a> <em>by <a shape="rect" href="http://trenaman.blogspot.com/">Adrian Trenaman</a></em> (September 2008)</li><li><a shape="rect" href="http://note19.com/2007/06/23/configure-activemq-with-mysql/">Configure ActiveMQ with MySQL</a> <em>By Shahram Javey</em> (June 2007)</li></ul><h4>ActiveMQ and Spring</h4><ul><li><a shape="rect" href="https://github.com/bsnyder/spring-jms-examples">Spring JMS Examples with ActiveMQ</a> by <a shape="rect" href="https://bsnyderblog.blogspot.com/">Bruce Snyder</a> (June 2011)</li><li><a shape="rect" href="https://bsnyderblog.blogspot.com/2010/05/tuning-jms-message-consumption-in.html">Tuning JMS Message Consumption In Spring</a> by <a shape="rect" href="https://bsnyderblog.blogspot.com/">Bruce Snyder</a> (May 2010)</li><li><a shape="rect" href="http://codedependents.com/2010/03/04/synchronous-request-response-with-activemq-and-spring/">Synchronous Request Response with ActiveMQ and Spring</a> <em>by <a shape="rect" href="http://codedependents.com/">CodeDependents</a></em> (March 2010)</li><li><a shape="rect" href="https://bsnyderblog.blogspot.com/2010/02/using-spring-to-receive-jms-messages.html">Using Spring to Receive JMS Messages</a> by <a shape="rect" href="https://bsnyderblog.blogspot.com/">Bruce Snyder</a> (February 2010)</li><li><a shape="rect" href="https://bsnyderblog.blogspot.com/2010/02/using-spring-jmstemplate-to-send-jms.html">Using Spring to Send JMS Messages</a> by <a shape="rect" href="https://bsnyderblog.blogspot.com/">Bruce Snyder</a> (February 2010)</li><li><a shape="rect" href="http://codedependents.com/2009/10/16/efficient-lightweight-jms-with-spring-and-activemq/">Efficient Lightweight JMS with Spring and ActiveMQ</a> <em>by <a shape="rect" href="http://codedependents.com/">CodeDependents</a></em> (Octover 2009)</li><li><a shape="rect" href="http://javaandjava.blogspot.com/2008/10/activemq-message-consumer-in-spring.html">ActiveMQ Message Consumer in Spring</a> <em>by <a shape="rect" href="http://javaandjava.blogspot.com/">Saveen Kumar</a></em> (October 2008)</li><li><a shape="rect" href="http://www.springframework.org/node/527">Message-Driven Architectures at The Spring Experience</a> <em>by Keith Donald</em> (September 2007)</li></ul><h4>ActiveMQ with JRuby/Ruby, Rails and/or Stomp</h4><ul><li><a shape="rect" href="http://beechbonanza.blogspot.com/2007/07/jruby-jms-as-replacement-for.html">JRuby JMS as a replacement for ActiveMessaging</a></li><li><a shape="rect" href="http://nutrun.com/weblog/jms-with-jruby-and-activemq/">JMS with JRuby and ActiveMQ</a></li><li><a shape="rect" href="http://romjethoughts.blogspot.com/2007/05/first-steps-with-rubystomp-and-activemq.html">First Steps on Ruby/STOMP and ActiveMQ</a> <em>by <a shape="rect" href="http://romjethoughts.blogspot.com/">jerome moliere</a></em></li><li><a shape="rect" href="http://beechbonanza.blogspot.com/2007/06/asynchronous-messaging-with-rails.html">Asynchronous Messaging with Rails</a> <em>by <a shape="rect" href="http://beechbonanza.blogspot.com/">Shane Harvie</a></em></li><li><a shape="rect" href="http://notdennisbyrne.blogspot.com/2007/06/integrating-rails-and-activemq-with.html">Integrating Rails and ActiveMQ with ActiveMessaging/REST</a> <em>by <a shape="rect" href="http://notdennisbyrne.blogspot.com/">(not) Dennis Byrne</a></em></li><li><a shape="rect" href="http://ramesh-rubyonrails.blogspot.com/2007/09/asynchronous-messaging-using-rails.html">Asynchronous Messaging using Rails</a></li><li><a shape="rect" href="http://www.infoq.com/articles/intro-active-messaging-rails">Introduction to ActiveMessaging, using Rails with ActiveMQ or Stomp</a> <em>by Andrew Kuklewicz</em></li><li><a shape="rect" href="http://flexonrails.net/?p=83">Flex, Rails, ActiveMQ and Stomp</a> <em>by <a shape="rect" href="http://flexonrails.net">Flex On Rails</a></em></li><li><a shape="rect" href="http://just-another.net/2008/09/03/activemq-stomp-end-end-test-nagios/">ActiveMQ stomp end to end test for nagios</a> <em>by <a shape="rect" href="http://just-another.net/">Benjamin Smith</a></em></li><li><a shape="rect" href="http://www.kaazing.org/confluence/display/Doc/JavaScript+STOMP+Client+How-To">How to Create a Stomp-Driven Application in JavaScript Using Apache ActiveMQ as a Message Broker</a> <em>by <a shape="rect" href="http://www.kaazing.org/confluence/display/KAAZING/Home">Kaazing</a></em></li><li><a shape="rect" href="http://cometdaily.com/2008/10/08/scalable-real-time-web-architecture-part-1-stomp-comet-and-message-queues/">Scalable Real-Time Web Architecture, Part 1: Stomp, Comet, and Message Queues</a> <em>by <a shape="rect" href="http://cometdaily.com/people/michael_carter/">Michael Carter</a></em></li></ul><h4>ActiveMQ and .NET</h4><ul><li><a shape="rect" href="http://remark.wordpress.com/articles/messaging-with-net-and-activemq/">Messaging with .NET and ActiveMQ</a> <em>by <a shape="rect" href="http://remark.wordpress.com/">Re.Mark</a></em></li><li><a shape="rect" href="http://remark.wordpress.com/articles/messaging-with-net-and-activemq/">Using .Net and ActiveMQ</a> <em>by <a shape="rect" href="http://remark.wordpress.com/">Re.Mark</a></em></li></ul><h3>Message Broker Comparison</h3><ul><li><a shape="rect" href="http://bhavin.directi.com/rabbitmq-vs-apache-activemq-vs-apache-qpid/">RabbitMQ vs Apache ActiveMQ vs Apache qpid </a> <em>by Bhavin Turakhia</em> (May, 2010)</li><li><a shape="rect" href="http://www.nighttale.net/activemq/python-messaging-activemq-and-rabbitmq.html">Python messaging: ActiveMQ and RabbitMQ</a> <em>by Night Tale</em></li><li><a shape="rect" href="http://stackoverflow.com/questions/32851/multicasting-messaging-activemq-vs-msmq">Multicasting, Messaging, ActiveMQ vs. MSMQ?</a> <em>by stackoverflow.com</em></li><li><a shape="rect" href="http://www.fiorano.com/whitepapers/java-message-service/JMS-performance-comparison.php">JMS Performance Comparison</a> <em>by www.fiarano.com</em></li><li><a shape="rect" href="http://activemq.apache.org/how-does-activemq-compare-to-jbossmq.html">How does ActiveMQ compare to JBossMQ</a></li><li><a shape="rect" href="http://www.mail-archive.com/activemq-users@geronimo.apache.org/msg05630.html">Why use ActiveMQ over JBossMQ?</a></li><li><a shape="rect" href="http://www.manning-sandbox.com/thread.jspa?threadID=39270&tstart=45">Thread: ActiveMQ vs Websphere MQ </a></li><li><a shape="rect" href="http://activemq.apache.org/how-does-activemq-compare-to-mule.html">How does ActiveMQ compare to Mule?</a></li><li><a shape="rect" href="http://www.roklee.com/?p=52">HornetQ 2.0GA vs ActiveMQ 5.3 – feature by feature comparison</a> <em>by www.roklee.com</em></li><li><a shape="rect" href="http://www.theserverside.com/discussions/thread.tss?thread_id=57192">Performance and scalability: Analysis and comparison of ActiveMQ, Websphere MQ and SonicMQ</a></li><li><a shape="rect" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-vs-Camel-vs-Qpid-td2355914.html">ActiveMQ vs. Camel vs. Qpid </a></li></ul><h3>ActiveMQ tooling and scripts</h3><ul><li><a shape="rect" href="https://github.com/ebuzzing/bash-mq">Bash-MQ</a> - a bash/awk producer/consumer for activemq or any STOMP compatible MQ</li></ul><h3>Books and Reference Guides</h3><ul><li>Beside these extract of interviews, articles and videos there are also some books available. Take a look at the <link><page ri:content-title="Books"></page></link> page.</li></ul><h3>Additional Resources</h3><ul><li>Many of the Commercial Providers listed on the <link><page ri:content-title="Support"></page></link> page provide additional examples, articles, tutorials, documentation, etc...</li></ul><h3>ActiveMQ bloggers</h3><ul><li><a shape="rect" href="http://rajdavies.blogspot.com/">Rob Davies</a></li><li><a shape="rect" href="http://hiramchirino.com/blog/">Hiram Chirino</a></li><li><a shape="rect" href="http://blog.garytully.com/">Gary Tully</a></li><li><a shape="rect" href="http://www.nighttale.net">Dejan Bosanac</a></li><li><a shape="rect" href="http://bruceblog.org/">Bruce Snyder</a></li><li><a shape="rect" href="http://www.christianposta.com/blog">Christian Posta</a></li></ul></div>
diff --git a/async-sends.xml b/async-sends.xml
index 2dfa1a9..8e20b90 100644
--- a/async-sends.xml
+++ b/async-sends.xml
@@ -1,11 +1,5 @@
-<div class="wiki-content maincontent"><h2 id="AsyncSends-Background">Background</h2><p>ActiveMQ supports sending messages to a broker in sync or async mode. The mode used has a huge impact in the latency of the send call. Since latency is typically a huge factor in the throughput that can achieved by producer, using async sends can increase the performance of your system dramatically.</p><p>The good news is that ActiveMQ sends message in async mode by default in several cases. It is only in cases where the JMS specification required the use of sync sending that we default to sync sending. The cases that we are forced to send in sync mode are when persistent messages are being sent outside of a transaction.</p><p>If you are not using transactions and are sending persistent messages, then each send is synch and blocks until the broker has sent back an acknowledgement to the producer that the message has been safely persisted to disk. This ack provides that guarantee that the message will not be lost but it also costs a huge latency penalty since the client is blocked.</p><p>Many high performance applications are designed to be tolerate a small amount of message loss in failure scenarios. If your application has been designed in this fashion, you can enable the use of async sends to increase throughput even when using persistent messages.</p><h3 id="AsyncSends-ConfiguringAsyncSendusingaConnectionURI">Configuring Async Send using a Connection URI</h3><p>You can use the <a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a> to configure async sends as follows</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cf = new ActiveMQConnectionFactory("tcp://locahost:61616?jms.useAsyncSend=true");
-]]></script>
-</div></div><h3 id="AsyncSends-ConfiguringAsyncSendattheConnectionFactoryLevel">Configuring Async Send at the ConnectionFactory Level</h3><p>You can enable this feature on the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory </a> object using the property.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[((ActiveMQConnectionFactory)connectionFactory).setUseAsyncSend(true);
-]]></script>
-</div></div><h3 id="AsyncSends-ConfiguringAsyncSendattheConnectionLevel">Configuring Async Send at the Connection Level</h3><p>Configuring the dispatchAsync setting at this level overrides the settings at the connection factory level.</p><p>You can enable this feature on the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a> object using the property.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[((ActiveMQConnection)connection).setUseAsyncSend(true);
-]]></script>
-</div></div><h3 id="AsyncSends-Alsosee">Also see</h3><ul><li><a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a></li><li><a shape="rect" href="should-i-use-transactions.xml">Should I use transactions</a></li><li><a shape="rect" href="consumer-dispatch-async.xml">Consumer Dispatch Async</a></li></ul></div>
+<div class="wiki-content maincontent"><h2>Background</h2><p>ActiveMQ supports sending messages to a broker in sync or async mode. The mode used has a huge impact in the latency of the send call. Since latency is typically a huge factor in the throughput that can achieved by producer, using async sends can increase the performance of your system dramatically.</p><p>The good news is that ActiveMQ sends message in async mode by default in several cases. It is only in cases where the JMS specification required the use of sync sending that we default to sync sending. The cases that we are forced to send in sync mode are when persistent messages are being sent outside of a transaction.</p><p>If you are not using transactions and are sending persistent messages, then each send is synch and blocks until the broker has sent back an acknowledgement to the producer that the message has been safely persisted to disk. This ack provides that guarantee that the message will not be lost but it also costs a huge latency penalty since the client is blocked.</p><p>Many high performance applications are designed to be tolerate a small amount of message loss in failure scenarios. If your application has been designed in this fashion, you can enable the use of async sends to increase throughput even when using persistent messages.</p><h3>Configuring Async Send using a Connection URI</h3><p>You can use the <link><page ri:content-title="Connection Configuration URI"></page></link> to configure async sends as follows</p><structured-macro ac:macro-id="bc12bc02-703c-484c-910d-2e32a9a0ec5b" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>cf = new ActiveMQConnectionFactory("tcp://locahost:61616?jms.useAsyncSend=true");
+</plain-text-body></structured-macro><h3>Configuring Async Send at the ConnectionFactory Level</h3><p>You can enable this feature on the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory </a> object using the property.</p><structured-macro ac:macro-id="f193f85f-3401-4dd5-a594-dbc3128f51c4" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>((ActiveMQConnectionFactory)connectionFactory).setUseAsyncSend(true);
+</plain-text-body></structured-macro><h3>Configuring Async Send at the Connection Level</h3><p>Configuring the dispatchAsync setting at this level overrides the settings at the connection factory level.</p><p>You can enable this feature on the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a> object using the property.</p><structured-macro ac:macro-id="68830b08-1a0d-4d5a-ab6e-78cd6ef9089e" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>((ActiveMQConnection)connection).setUseAsyncSend(true);
+</plain-text-body></structured-macro><h3>Also see</h3><ul><li><link><page ri:content-title="Connection Configuration URI"></page></link></li><li><link><page ri:content-title="Should I use transactions"></page></link></li><li><link><page ri:content-title="Consumer Dispatch Async"></page></link></li></ul></div>
diff --git a/audit-logging.xml b/audit-logging.xml
index 15f7c2c..7ccd2eb 100644
--- a/audit-logging.xml
+++ b/audit-logging.xml
@@ -1,15 +1,12 @@
-<div class="wiki-content maincontent"><p>For many secured environments there's a requirement to log every user management action. For that ActiveMQ implements <em>audit logging</em>, which means that every management action made through JMX or Web Console management interface will be logged and available for later inspection.</p><p>Audit logging comes pre-configured with the distribution, so it's very easy to turn it on or off. All you have to do is to set <code>org.apache.activemq.audit</code> system property.  From 5.16.0 the value can be one of "true|entry|exit|all". When the value is all or exit, the audit captures the time the JMX operation completed. You can do that by uncommenting the following line in the startup script:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS -Dorg.apache.activemq.audit=true"
-]]></script>
-</div></div><p>The actual logs are by default stored in <code>${ACTIVEMQ_HOME}/data/audit.log</code> and for secured broker you may expect entries similar to the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[2010-12-22 12:12:07,225 | INFO | admin requested /admin/createDestination.action [JMSDestination='test' JMSDestinationType='queue'
-secret='4eb0bc3e-9d7a-4256-844c-24f40fda98f1' ] from 127.0.0.1 | qtp12205619-39
-2010-12-22 12:12:14,512 | INFO | admin requested /admin/purgeDestination.action [JMSDestination='test' JMSDestinationType='queue'
-secret='eff6a932-1b58-45da-a64a-1b30b246cfc9' ] from 127.0.0.1 | qtp12205619-36
-2010-12-22 12:12:17,802 | INFO | admin requested /admin/sendMessage.action [JMSTimeToLive='' JMSXGroupSeq='' AMQ_SCHEDULED_DELAY='' JMSType=''
-JMSMessageCountHeader='JMSXMessageCounter' JMSXGroupID='' JMSReplyTo='' JMSDestination='test' AMQ_SCHEDULED_PERIOD='' JMSText='Enter some text
-here for the message body...' JMSDestinationType='queue' AMQ_SCHEDULED_CRON='' JMSCorrelationID='' AMQ_SCHEDULED_REPEAT='' JMSMessageCount='1'
-secret='a0e1df62-14d6-4425-82a2-17aa01a16e7d' JMSPriority='' ] from 127.0.0.1 | qtp12205619-37
+<div class="wiki-content maincontent"><p>For many secured environments there's a requirement to log every user management action. For that ActiveMQ implements <em>audit logging</em>, which means that every management action made through JMX or Web Console management interface will be logged and available for later inspection.</p><p>Audit logging comes pre-configured with the distribution, so it's very easy to turn it on or off. All you have to do is to set <code>org.apache.activemq.audit</code> system property.  From 5.16.0 the value can be one of "true|entry|exit|all". When the value is all or exit, the audit captures the time the JMX operation completed. You can do that by uncommenting the following line in the startup script:</p><structured-macro ac:macro-id="133e6c51-e580-4b57-b0c7-1c109a35b72b" ac:name="code" ac:schema-version="1"><plain-text-body>ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS -Dorg.apache.activemq.audit=true"
+</plain-text-body></structured-macro><p>The actual logs are by default stored in <code>${ACTIVEMQ_HOME}/data/audit.log</code> and for secured broker you may expect entries similar to the following:</p><structured-macro ac:macro-id="d87a0230-8455-4ec7-82a5-9126c485fd82" ac:name="code" ac:schema-version="1"><plain-text-body>2010-12-22 12:12:07,225 | INFO | admin requested /admin/createDestination.action [JMSDestination='test' JMSDestinationType='queue'
+secret='4eb0bc3e-9d7a-4256-844c-24f40fda98f1' ] from 127.0.0.1 | qtp12205619-39
+2010-12-22 12:12:14,512 | INFO | admin requested /admin/purgeDestination.action [JMSDestination='test' JMSDestinationType='queue'
+secret='eff6a932-1b58-45da-a64a-1b30b246cfc9' ] from 127.0.0.1 | qtp12205619-36
+2010-12-22 12:12:17,802 | INFO | admin requested /admin/sendMessage.action [JMSTimeToLive='' JMSXGroupSeq='' AMQ_SCHEDULED_DELAY='' JMSType=''
+JMSMessageCountHeader='JMSXMessageCounter' JMSXGroupID='' JMSReplyTo='' JMSDestination='test' AMQ_SCHEDULED_PERIOD='' JMSText='Enter some text
+here for the message body...' JMSDestinationType='queue' AMQ_SCHEDULED_CRON='' JMSCorrelationID='' AMQ_SCHEDULED_REPEAT='' JMSMessageCount='1'
+secret='a0e1df62-14d6-4425-82a2-17aa01a16e7d' JMSPriority='' ] from 127.0.0.1 | qtp12205619-37
...
@@ -17,6 +14,5 @@
2010-12-22 12:13:21,976 | INFO | admin called org.apache.activemq.broker.jmx.QueueView.resetStatistics[] | RMI TCP Connection(8)-192.168.1.107
2010-12-22 12:13:32,457 | INFO | admin called org.apache.activemq.broker.jmx.QueueView.sendTextMessage[message] | RMI TCP Connection(6)-
192.168.1.107
-]]></script>
-</div></div><p>In this example you can see sample entries for actions taken both in Web Console or via JMX. Log entries contain info like:</p><ul><li>username (if available), or "anonymous" otherwise</li><li>Operation performed, which in JMX case is the method name and request URL if the operation is performed over web</li><li>Parameters used for the operation and</li><li>IP address from which call has been made</li></ul><p>A default location of the audit log can be configured in <code>${ACTIVEMQ_HOME}/conf/log4j.properties</code></p></div>
+</plain-text-body></structured-macro><p>In this example you can see sample entries for actions taken both in Web Console or via JMX. Log entries contain info like:</p><ul><li>username (if available), or "anonymous" otherwise</li><li>Operation performed, which in JMX case is the method name and request URL if the operation is performed over web</li><li>Parameters used for the operation and</li><li>IP address from which call has been made</li></ul><p>A default location of the audit log can be configured in <code>${ACTIVEMQ_HOME}/conf/log4j.properties</code></p></div>
diff --git a/auto.xml b/auto.xml
index 4845e6c..cfb1ec2 100644
--- a/auto.xml
+++ b/auto.xml
@@ -1,19 +1,3 @@
-<div class="wiki-content maincontent"><p>Starting with version 5.13.0, ActiveMQ supports wire format protocol detection.   OpenWire, STOMP, AMQP, and MQTT can be automatically detected.  This allows one transport to be shared for all 4 types of clients.</p><h3 id="AUTO-EnablingAUTOoverTCP">Enabling AUTO over TCP</h3><p>To configure ActiveMQ auto wire format detection over a TCP connection use the <code>auto</code> transport prefix. For example, add the following transport configuration in your XML file:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="auto" uri="auto://localhost:5671"/>]]></script>
-</div></div><h3 id="AUTO-EnablingAUTOoverSSL">Enabling AUTO over SSL</h3><p>To configure ActiveMQ auto wire format detection over an SSL connection use the <code>auto+ssl</code> transport prefix. For example, add the following transport configuration in your XML file:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="auto+ssl" uri="auto+ssl://localhost:5671"/>
-]]></script>
-</div></div><ul><li>For more details on using SSL with ActiveMQ, see the following article (<a shape="rect" class="external-link" href="http://activemq.apache.org/how-do-i-use-ssl.html">How do I use SSL</a>).</li></ul><h3 id="AUTO-EnablingAUTOoverNIO">Enabling AUTO over NIO</h3><p>To configure ActiveMQ auto wire format detection over an NIO TCP connection use the <code>auto+nio</code>transport prefix. For example, add the following transport configuration in your XML file:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="auto+nio" uri="auto+nio://localhost:5671"/>]]></script>
-</div></div><h3 id="AUTO-EnablingAUTOoverNIOSSL">Enabling AUTO over NIO SSL</h3><p>To configure ActiveMQ auto wire format detection over an NIO SSL connection use the <code>auto+nio+ssl</code> transport prefix. For example, add the following transport configuration in your XML file:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="auto+nio+ssl" uri="auto+nio+ssl://localhost:5671"/>]]></script>
-</div></div><h3 id="AUTO-ConfiguringAUTOTransportOptions">Configuring AUTO Transport Options</h3><p>There are some configuration options that can be set.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter Name</p></th><th colspan="1" rowspan="1" class="confluenceTh">Default Value</th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>protocolDetectionTimeOut</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The time before a connection times out in milliseconds. This is similar to maxInactivityDuration. If a client makes a connection to but doesn't send data or enough data for the protocol to be detected then the thread will sit and wait for more data to come in over the socket. This will let the broker kill the connections if they do not complete the protocol initialization after a certain period of time. The default is 30 seconds. Set a default to <= 0 to disable this.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxConnectionThreadPoolSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>MAX_INT</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>This option allows the configuration of the maximum size of the thread pool that handles connection attempts. Lowering this number can help prevent the broker from running out of threads if there are many different clients attempting to connect at the same time. By default it is turned off by setting to MAX_INT</p></td></tr></tbody></table></div><p><br clear="none">An example that configures the transport with a maximum protocol detection time of 5 seconds:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="auto" uri="auto://localhost:5671?protocolDetectionTimeOut=5000"/>]]></script>
-</div></div><h3 id="AUTO-ConfiguringWireFormats">Configuring Wire Formats</h3><p>OpenWire is the default Wire Format that ActiveMQ uses.  It provides a highly efficent binary format for high speed messaging.  OpenWire options can be configured on a JMS client's connection URI string or on a Brokers transport bind URI.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter Prefix</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Applies the option to all wire formats.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.default.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Applies the option to the default format which is OpenWire</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.stomp.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span>Applies the option to the STOMP wire format</span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span>wireFormat.amqp.</span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span>Applies the option to the AMQP<span> wire format</span></span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.mqtt.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span>Applies the option to the MQTT<span> wire format</span></span></p></td></tr></tbody></table></div><p> </p><p>An example of a property that applies to all formats:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="auto" uri="auto://localhost:5671?wireFormat.maxFrameSize=1000"/>]]></script>
-</div></div><p> </p><p>An example of a property only applied to OpenWire would be:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="auto" uri="auto://localhost:5671?wireFormat.default.maxFrameSize=1000"/>]]></script>
-</div></div><h3 id="AUTO-ConfiguringEnabledWireProtocols">Configuring Enabled Wire Protocols</h3><p>By default all wire protocols are available.  This can be configured to only enable certain formats by setting the property  auto<code>.protocols.</code> </p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>default</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables OpenWire</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>amqp</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables AMQP format</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>stomp</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables STOMP format</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>mqtt</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables MQTT format</p></td></tr></tbody></table></div><p> </p><p>An example showing only OpenWire and STOMP enabled:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="auto" uri="auto://localhost:5671?auto.protocols=default,stomp"/>]]></script>
-</div></div></div>
+<div class="wiki-content maincontent"><p>Starting with version 5.13.0, ActiveMQ supports wire format protocol detection.   OpenWire, STOMP, AMQP, and MQTT can be automatically detected.  This allows one transport to be shared for all 4 types of clients.</p><h3>Enabling AUTO over TCP</h3><p>To configure ActiveMQ auto wire format detection over a TCP connection use the <code>auto</code> transport prefix. For example, add the following transport configuration in your XML file:</p><structured-macro ac:macro-id="1b2eaa95-2237-4062-85d0-8f9e9566e4ce" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="auto" uri="auto://localhost:5671"/></plain-text-body></structured-macro><h3>Enabling AUTO over SSL</h3><p>To configure ActiveMQ auto wire format detection over an SSL connection use the <code>auto+ssl</code> transport prefix. For example, add the following transport configuration in your XML file:</p><structured-macro ac:macro-id="8fb394d9-660b-4afa-8246-ffef07fecf32" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="auto+ssl" uri="auto+ssl://localhost:5671"/>
+</plain-text-body></structured-macro><ul><li>For more details on using SSL with ActiveMQ, see the following article (<a shape="rect" href="http://activemq.apache.org/how-do-i-use-ssl.html">How do I use SSL</a>).</li></ul><h3>Enabling AUTO over NIO</h3><p>To configure ActiveMQ auto wire format detection over an NIO TCP connection use the <code>auto+nio</code>transport prefix. For example, add the following transport configuration in your XML file:</p><structured-macro ac:macro-id="d64978dd-16ac-4473-8c2d-e077b8e0e8da" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="auto+nio" uri="auto+nio://localhost:5671"/></plain-text-body></structured-macro><h3>Enabling AUTO over NIO SSL</h3><p>To configure ActiveMQ auto wire format detection over an NIO SSL connection use the <code>auto+nio+ssl</code> transport prefix. For example, add the following transport configuration in your XML file:</p><structured-macro ac:macro-id="45956eda-207b-439f-85f8-45fb5cd8b09d" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="auto+nio+ssl" uri="auto+nio+ssl://localhost:5671"/></plain-text-body></structured-macro><h3>Configuring AUTO Transport Options</h3><p>There are some configuration options that can be set.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Parameter Name</p></th><th colspan="1" rowspan="1">Default Value</th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>protocolDetectionTimeOut</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>The time before a connection times out in milliseconds. This is similar to maxInactivityDuration. If a client makes a connection to but doesn't send data or enough data for the protocol to be detected then the thread will sit and wait for more data to come in over the socket. This will let the broker kill the connections if they do not complete the protocol initialization after a certain period of time. The default is 30 seconds. Set a default to <= 0 to disable this.</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxConnectionThreadPoolSize</p></td><td colspan="1" rowspan="1"><p>MAX_INT</p></td><td colspan="1" rowspan="1"><p>This option allows the configuration of the maximum size of the thread pool that handles connection attempts. Lowering this number can help prevent the broker from running out of threads if there are many different clients attempting to connect at the same time. By default it is turned off by setting to MAX_INT</p></td></tr></tbody></table><p><br clear="none">An example that configures the transport with a maximum protocol detection time of 5 seconds:</p><structured-macro ac:macro-id="2f645d3e-dbec-42b6-b5ad-c6043c0d1d72" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="auto" uri="auto://localhost:5671?protocolDetectionTimeOut=5000"/></plain-text-body></structured-macro><h3>Configuring Wire Formats</h3><p>OpenWire is the default Wire Format that ActiveMQ uses.  It provides a highly efficent binary format for high speed messaging.  OpenWire options can be configured on a JMS client's connection URI string or on a Brokers transport bind URI.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Parameter Prefix</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.</p></td><td colspan="1" rowspan="1"><p>Applies the option to all wire formats.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.default.</p></td><td colspan="1" rowspan="1"><p>Applies the option to the default format which is OpenWire</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.stomp.</p></td><td colspan="1" rowspan="1"><p><span>Applies the option to the STOMP wire format</span></p></td></tr><tr><td colspan="1" rowspan="1"><p><span>wireFormat.amqp.</span></p></td><td colspan="1" rowspan="1"><p><span>Applies the option to the AMQP<span> wire format</span></span></p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.mqtt.</p></td><td colspan="1" rowspan="1"><p><span>Applies the option to the MQTT<span> wire format</span></span></p></td></tr></tbody></table><p> </p><p>An example of a property that applies to all formats:</p><structured-macro ac:macro-id="74a2a3a1-104d-440d-8639-b25f6efe924f" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="auto" uri="auto://localhost:5671?wireFormat.maxFrameSize=1000"/></plain-text-body></structured-macro><p> </p><p>An example of a property only applied to OpenWire would be:</p><structured-macro ac:macro-id="1098c525-7508-4399-954f-3b02ab7b1994" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="auto" uri="auto://localhost:5671?wireFormat.default.maxFrameSize=1000"/></plain-text-body></structured-macro><h3>Configuring Enabled Wire Protocols</h3><p>By default all wire protocols are available.  This can be configured to only enable certain formats by setting the property  auto<code>.protocols.</code> </p><table><tbody><tr><th colspan="1" rowspan="1"><p>Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>default</p></td><td colspan="1" rowspan="1"><p>Enables OpenWire</p></td></tr><tr><td colspan="1" rowspan="1"><p>amqp</p></td><td colspan="1" rowspan="1"><p>Enables AMQP format</p></td></tr><tr><td colspan="1" rowspan="1"><p>stomp</p></td><td colspan="1" rowspan="1"><p>Enables STOMP format</p></td></tr><tr><td colspan="1" rowspan="1"><p>mqtt</p></td><td colspan="1" rowspan="1"><p>Enables MQTT format</p></td></tr></tbody></table><p> </p><p>An example showing only OpenWire and STOMP enabled:</p><structured-macro ac:macro-id="2cc70f63-d57a-470e-848d-b8a7d05d4d06" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="auto" uri="auto://localhost:5671?auto.protocols=default,stomp"/></plain-text-body></structured-macro></div>
diff --git a/axis-and-cxf-support.xml b/axis-and-cxf-support.xml
index a7e3f56..eea2e9a 100644
--- a/axis-and-cxf-support.xml
+++ b/axis-and-cxf-support.xml
@@ -1,11 +1,11 @@
-<div class="wiki-content maincontent"><p>ActiveMQ supports both <a shape="rect" class="external-link" href="http://ws.apache.org/axis/">Apache Axis</a> and <a shape="rect" class="external-link" href="http://incubator.apache.org/cxf">Apache CXF</a> out of the box. </p>
+<div class="wiki-content maincontent"><p>ActiveMQ supports both <a shape="rect" href="http://ws.apache.org/axis/">Apache Axis</a> and <a shape="rect" href="http://incubator.apache.org/cxf">Apache CXF</a> out of the box. </p>
-<div class="confluence-information-macro confluence-information-macro-note"><p class="title">Axis support is @deprecated</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Support for Axis is deprecated, and will be removed from ActiveMQ 5.8 onwards.</p></div></div>
+<structured-macro ac:macro-id="a9d73ce4-60e3-4b4f-8fb9-0ff12c48a100" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Axis support is @deprecated</parameter><rich-text-body>
+<p>Support for Axis is deprecated, and will be removed from ActiveMQ 5.8 onwards.</p></rich-text-body></structured-macro>
-<p>Just add the <a shape="rect" href="initial-configuration.xml">required jars</a> to your classpath and you should be able to use JMS transport support inside either web service framework to send and receive messages using ActiveMQ queues or topics for reliable messaging.</p>
+<p>Just add the <link><page ri:content-title="Initial Configuration"></page><link-body>required jars</link-body></link> to your classpath and you should be able to use JMS transport support inside either web service framework to send and receive messages using ActiveMQ queues or topics for reliable messaging.</p>
-<p>For an example of using the JMS transport with Axis, consult <a shape="rect" class="external-link" href="http://ws.apache.org/axis2/1_2/jms-transport.html">JMS Transport reference</a> or try looking at the <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/webservices/axis2/branches/java/1_4/modules/samples/jms/">JMS example</a> that comes with bundled with Axis' binary and source downloads.</p>
+<p>For an example of using the JMS transport with Axis, consult <a shape="rect" href="http://ws.apache.org/axis2/1_2/jms-transport.html">JMS Transport reference</a> or try looking at the <a shape="rect" href="http://svn.apache.org/viewvc/webservices/axis2/branches/java/1_4/modules/samples/jms/">JMS example</a> that comes with bundled with Axis' binary and source downloads.</p>
-<p>For examples of using JMS transport with CXF, please see its <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jms_pubsub/">JMS publish/subscriber sample</a> and the <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jms_queue/">JMS queue sample</a> available in the CXF source and binary downloads.</p></div>
+<p>For examples of using JMS transport with CXF, please see its <a shape="rect" href="http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jms_pubsub/">JMS publish/subscriber sample</a> and the <a shape="rect" href="http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jms_queue/">JMS queue sample</a> available in the CXF source and binary downloads.</p></div>
diff --git a/banner.xml b/banner.xml
index 0ba55b7..224ccbc 100644
--- a/banner.xml
+++ b/banner.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><div id="asf_logo">
- <div id="activemq_logo">
- <a shape="rect" style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="http://activemq.apache.org" title="The most popular and powerful open source Message Broker">ActiveMQ</a>
- <a shape="rect" style="float:right; width:210px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:15px; margin-right:10px;" href="http://www.apache.org" title="The Apache Software Foundation">ASF</a>
- </div>
-</div>
-</div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="b53c059e-781d-4916-b99a-5bccad111511" ac:name="html" ac:schema-version="1"><parameter ac:name="output">html</parameter><parameter ac:name="atlassian-macro-output-type">INLINE</parameter><parameter ac:name="noPanel">true</parameter><plain-text-body><div id="asf_logo">
+ <div id="activemq_logo">
+ <a style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="http://activemq.apache.org" title="The most popular and powerful open source Message Broker">ActiveMQ</a>
+ <a style="float:right; width:210px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:15px; margin-right:10px;" href="http://www.apache.org" title="The Apache Software Foundation">ASF</a>
+ </div>
+</div>
+</plain-text-body></structured-macro></p></div>
diff --git a/becoming-a-committer.xml b/becoming-a-committer.xml
index 84ee20d..f4328d7 100644
--- a/becoming-a-committer.xml
+++ b/becoming-a-committer.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><p>This page details how to become a committer.</p><h3 id="Becomingacommitter-Howtobecomeacommitter">How to become a committer</h3><p>First of all you need to get involved and <a shape="rect" href="contributing.xml">Contribute</a> via the mail list, forums, edit the documention, work on the issue tracker and submit patches.</p><p>Once you're contributing and your work is good, one of our <a shape="rect" href="team.xml">Team</a> may invite you to be a committer (after we've called a vote). When that happens, if you accept, the following process kicks into place...</p><p>Note that becoming a committer is not just about submitting some patches; its also about helping out on the development and user <a shape="rect" href="discussion-forums.xml">Discussion Forums</a>, helping with documentation and the issue tracker.</p><h3 id="Becomingacommitter-Becomingacommittersteps">Becoming a committer steps</h3><ul><li>Download and print the Apache Contributor License Agreement from <a shape="rect" class="external-link" href="http://www.apache.org/dev/new-committers-guide.html">here</a>. You need to sign it and fax it to Apache. In the past I've found its often faster to also post it via snail mail <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></li><li>wait for your name to appear on the list of <a shape="rect" class="external-link" href="http://people.apache.org/~jim/committers.html#unlistedclas">received CLAs</a></li><li>once thats done let us know and we can apply to Apache Infrastructure to have your account created; we'll also need to know<ul><li>your full name</li><li>your preferred email address</li><li>your preferred unix account name</li></ul></li></ul><h3 id="Becomingacommitter-GettingstartedatApache">Getting started at Apache</h3><p>Firstly add yourself to the <a shape="rect" href="team.xml">Team</a> page</p><p>Now go read the instructions on the <a shape="rect" class="external-link" href="http://www.apache.org/dev/new-committers-guide.html">new committers guide</a>. Its also worth viewing <a shape="rect" class="external-link" href="http://www.apache.org/dev">http://www.apache.org/dev</a>.</p><h3 id="Becomingacommitter-EnablingyourGITaccount">Enabling your GIT account</h3><p>Once you've got your Apache account working you need to enable GIT access<strong>. </strong>Add your SSH Key at <a shape="rect" class="external-link" href="https://id.apache.org/">https://id.apache.org/</a><strong><br clear="none"></strong></p><h3 id="Becomingacommitter-ConfiguringGIT">Configuring GIT</h3><p>Configure GIT to use unix line endings.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[git config --add core.autocrlf input]]></script>
-</div></div><h3 id="Becomingacommitter-GettingKarmainJIRAandConfluence">Getting Karma in JIRA and Confluence</h3><p>Mail the dev list and ask for karma for JIRA / Confluence giving them details of your username you used to register with them both. We can then grant the necessary karma so you can start grabbing JIRA issues or editing the wiki</p></div>
+<div class="wiki-content maincontent"><p>This page details how to become a committer.</p><h3>How to become a committer</h3><p>First of all you need to get involved and <link><page ri:content-title="Contributing"></page><plain-text-link-body>Contribute</plain-text-link-body></link> via the mail list, forums, edit the documention, work on the issue tracker and submit patches.</p><p>Once you're contributing and your work is good, one of our <link><page ri:content-title="Team"></page></link> may invite you to be a committer (after we've called a vote). When that happens, if you accept, the following process kicks into place...</p><p>Note that becoming a committer is not just about submitting some patches; its also about helping out on the development and user <link><page ri:content-title="Discussion Forums"></page></link>, helping with documentation and the issue tracker.</p><h3>Becoming a committer steps</h3><ul><li>Download and print the Apache Contributor License Agreement from <a shape="rect" href="http://www.apache.org/dev/new-committers-guide.html">here</a>. You need to sign it and fax it to Apache. In the past I've found its often faster to also post it via snail mail <emoticon ac:name="smile"></emoticon></li><li>wait for your name to appear on the list of <a shape="rect" href="http://people.apache.org/~jim/committers.html#unlistedclas">received CLAs</a></li><li>once thats done let us know and we can apply to Apache Infrastructure to have your account created; we'll also need to know<ul><li>your full name</li><li>your preferred email address</li><li>your preferred unix account name</li></ul></li></ul><h3>Getting started at Apache</h3><p>Firstly add yourself to the <link><page ri:content-title="Team"></page></link> page</p><p>Now go read the instructions on the <a shape="rect" href="http://www.apache.org/dev/new-committers-guide.html">new committers guide</a>. Its also worth viewing <a shape="rect" class="external-link" href="http://www.apache.org/dev">http://www.apache.org/dev</a>.</p><h3>Enabling your GIT account</h3><p>Once you've got your Apache account working you need to enable GIT access<strong>. </strong>Add your SSH Key at <a shape="rect" href="https://id.apache.org/">https://id.apache.org/</a><strong><br clear="none"></strong></p><h3>Configuring GIT</h3><p>Configure GIT to use unix line endings.</p><structured-macro ac:macro-id="c4df4af7-2b1f-45e3-b20f-ca1ed40f7d24" ac:name="code" ac:schema-version="1"><plain-text-body>git config --add core.autocrlf input</plain-text-body></structured-macro><h3>Getting Karma in JIRA and Confluence</h3><p>Mail the dev list and ask for karma for JIRA / Confluence giving them details of your username you used to register with them both. We can then grant the necessary karma so you can start grabbing JIRA issues or editing the wiki</p></div>
diff --git a/benchmark-tests.xml b/benchmark-tests.xml
index 872a089..718448d 100644
--- a/benchmark-tests.xml
+++ b/benchmark-tests.xml
@@ -1,9 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="BenchmarkTests-ActiveMQMavenPerformancetestplugin.">ActiveMQ Maven Performance test plugin.</h2>
+<div class="wiki-content maincontent"><h2>ActiveMQ Maven Performance test plugin.</h2>
-<p>Starting with ActiveMQ 5.5 and above the plugin can be obtained from maven or if you download the src from SVN you can build it yourself. To run the following Maven goals make sure you are inside a Maven2 project directory where its POM is enabled with the Maven2 plugin. The plugin is further documented <a shape="rect" href="activemq-performance-module-users-manual.xml">here</a>.</p>
+<p>Starting with ActiveMQ 5.5 and above the plugin can be obtained from maven or if you download the src from SVN you can build it yourself. To run the following Maven goals make sure you are inside a Maven2 project directory where its POM is enabled with the Maven2 plugin. The plugin is further documented <link><page ri:content-title="ActiveMQ Performance Module Users Manual"></page><link-body>here</link-body></link>.</p>
-<h2 id="BenchmarkTests-Third-PartyJMSperformancetests">Third-Party JMS performance tests</h2>
+<h2>Third-Party JMS performance tests</h2>
<p>There are a number of third-party JMS performance test tools that can be used to measure the performance of various features of brokers and compare them.</p>
-<ul><li><a shape="rect" class="external-link" href="http://jmeter.apache.org/">Apache JMeter</a></li><li><a shape="rect" class="external-link" href="https://github.com/chirino/jms-benchmark" rel="nofollow">jms-benchmark</a></li></ul></div>
+<ul><li><a shape="rect" href="http://jmeter.apache.org/">Apache JMeter</a></li><li><a shape="rect" href="https://github.com/chirino/jms-benchmark">jms-benchmark</a></li></ul>
+</div>
diff --git a/blazeds.xml b/blazeds.xml
index e619dfe..7d1ea27 100644
--- a/blazeds.xml
+++ b/blazeds.xml
@@ -1,25 +1,24 @@
-<div class="wiki-content maincontent"><h2 id="BlazeDS-BlazeDS">BlazeDS</h2>
+<div class="wiki-content maincontent"><h2>BlazeDS</h2>
-<p>You may also want to check out the <a shape="rect" class="external-link" href="http://mmartinsoftware.blogspot.com/2008/05/simplified-blazeds-and-jms.html" rel="nofollow">Simplified BlazeDS and JMS article</a> by <a shape="rect" class="external-link" href="http://mmartinsoftware.blogspot.com/" rel="nofollow">Michael Martin</a>.</p>
+<p>You may also want to check out the <a shape="rect" href="http://mmartinsoftware.blogspot.com/2008/05/simplified-blazeds-and-jms.html">Simplified BlazeDS and JMS article</a> by <a shape="rect" href="http://mmartinsoftware.blogspot.com/">Michael Martin</a>.</p>
-<p>Using the dynamicQueues feature of the <a shape="rect" href="jndi-support.xml">JNDI Support</a> Ryan Gardner created thisworking BlazeDS messaging-config.xml file:</p>
+<p>Using the dynamicQueues feature of the <link><page ri:content-title="JNDI Support"></page></link> Ryan Gardner created thisworking BlazeDS messaging-config.xml file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<service id="message-service" class="flex.messaging.services.MessageService">
+<structured-macro ac:macro-id="b238623f-c9bb-49a6-a5c5-a5549d2610b9" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
+<service id="message-service" class="flex.messaging.services.MessageService">
<adapters>
- <adapter-definition id="actionscript" class="flex.messaging.services.messaging.adapters.ActionScriptAdapter" default="true" />
- <adapter-definition id="jms" class="flex.messaging.services.messaging.adapters.JMSAdapter"/>
+ <adapter-definition id="actionscript" class="flex.messaging.services.messaging.adapters.ActionScriptAdapter" default="true" />
+ <adapter-definition id="jms" class="flex.messaging.services.messaging.adapters.JMSAdapter"/>
</adapters>
<default-channels>
- <channel ref="my-streaming-amf"/>
- <channel ref="my-polling-amf"/>
+ <channel ref="my-streaming-amf"/>
+ <channel ref="my-polling-amf"/>
</default-channels>
- <destination id="inbound-sms-destination">
+ <destination id="inbound-sms-destination">
<properties>
<jms>
@@ -44,9 +43,8 @@
</initial-context-environment>
</jms>
</properties>
- <adapter ref="jms"/>
+ <adapter ref="jms"/>
</destination>
</service>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/blob-messages.xml b/blob-messages.xml
index 8530554..7075369 100644
--- a/blob-messages.xml
+++ b/blob-messages.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="BlobMessages-BlobMessages">Blob Messages</h2>
+<div class="wiki-content maincontent"><h2>Blob Messages</h2>
<p>A common requirement these days is to send around massive files for processing by consumers. Folks want to take advantage of the message broker's features such as reliable, transactional load balancing of queues with smart routing but still manage to deal with huge logical files.</p>
@@ -6,42 +6,35 @@
<p>There are now new createBlobMessage() methods on the ActiveMQSession that you can use for sending BLOBs. </p>
-<h3 id="BlobMessages-SendingBlobMessages">Sending BlobMessages</h3>
+<h3>Sending BlobMessages</h3>
<p>You can send a URL around the JMS network, such as a file or URL which exists on some shared file system or web server using the following code</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-BlobMessage message = session.createBlobMessage(new URL("http://some.shared.site.com");
+<structured-macro ac:macro-id="6be5c968-e508-407f-83e5-5e256a77d939" ac:name="code" ac:schema-version="1"><plain-text-body>
+BlobMessage message = session.createBlobMessage(new URL("http://some.shared.site.com");
producer.send(message);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Or if you are creating files or streams dynamically on the client you may want to upload the file to the broker or some server (Jetty, FTP, WebDav or whatever). In which case you'd use one of the following methods</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f990ea28-b4c0-4468-b9ba-5648214461d4" ac:name="code" ac:schema-version="1"><plain-text-body>
// lets use a local file
-BlobMessage message = session.createBlobMessage(new File("/foo/bar");
+BlobMessage message = session.createBlobMessage(new File("/foo/bar");
producer.send(message);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a43a4699-551e-41b2-a013-f580e8ba0894" ac:name="code" ac:schema-version="1"><plain-text-body>
// lets use a stream
InputStream in = ...;
BlobMessage message = session.createBlobMessage(in);
producer.send(message);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="BlobMessages-ReceivingBlobMessages">Receiving BlobMessages</h3>
+<h3>Receiving BlobMessages</h3>
-<p>A <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/BlobMessage.html">BlobMessage</a> is a regular JMS message so it can be received just like any other message...</p>
+<p>A <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/BlobMessage.html">BlobMessage</a> is a regular JMS message so it can be received just like any other message...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="19b81f57-789a-4d1a-882a-d0f3ebe734be" ac:name="code" ac:schema-version="1"><plain-text-body>
public class MyListener implements MessageListener {
public void onMessage(Message message) {
if (message instanceof BlobMessage) {
@@ -52,22 +45,20 @@
}
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="BlobMessages-ConfiguringtheBLOBTransferPolicy">Configuring the BLOB Transfer Policy</h3>
+<h3>Configuring the BLOB Transfer Policy</h3>
<p>You can explicitly configure the BlobTransferPolicy on an ActiveMQConnectionFactory, ActiveMQConnection or ActiveMQSession. Typically its done on the factory either via Java code or Spring.</p>
-<p>You can use the <a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a> to configure these things via a URI.</p>
+<p>You can use the <link><page ri:content-title="Connection Configuration URI"></page></link> to configure these things via a URI.</p>
<p>For example you can connect to a broker also specifying the uploadUrl to use via</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c3816021-f3f7-419b-b3d9-65a52c18ef59" ac:name="code" ac:schema-version="1"><plain-text-body>
tcp://localhost:61616?jms.blobTransferPolicy.uploadUrl=http://foo.com
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
+
</div>
diff --git a/board-reports.xml b/board-reports.xml
index 93656c6..591ed09 100644
--- a/board-reports.xml
+++ b/board-reports.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="BoardReports-BoardReports">Board Reports</h2>
+<div class="wiki-content maincontent"><h2>Board Reports</h2>
<p>The following are the Apache Software Foundation Board Reports.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="2007-april.xml">2007 April</a></li></ul></div>
+<structured-macro ac:macro-id="7dc06fda-5630-4ef7-ba59-7c2e26f9b241" ac:name="children" ac:schema-version="1"><parameter ac:name="">all</parameter></structured-macro></div>
diff --git a/books.xml b/books.xml
index 2594158..584bc3e 100644
--- a/books.xml
+++ b/books.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="Books-Books">Books</h1><p>This page lists the known books about Apache ActiveMQ. If you happen to know a book which is not listed then please contact us, for example using the <a shape="rect" href="mailing-lists.xml">Mailing Lists</a>.</p><ul><li><a shape="rect" class="external-link" href="http://bit.ly/2je6cQ" rel="nofollow">ActiveMQ in Action</a></li><li><a shape="rect" class="external-link" href="http://goo.gl/RFltj" rel="nofollow">Instant Apache ActiveMQ Messaging Application Development</a></li><li><a shape="rect" class="external-link" href="http://shop.oreilly.com/product/0636920032366.do" rel="nofollow">Mobile and Web Messaging</a></li><li><a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php" rel="nofollow">Apache ActiveMQ Reference Guide</a></li></ul><h3 id="Books-ActiveMQinAction">ActiveMQ in Action</h3><p><a shape="rect" class="external-link" href="http://bit.ly/2je6cQ" rel="nofollow">ActiveMQ in Action</a> by <a shape="rect" class="external-link" href="http://bruceblog.org/" rel="nofollow">Bruce Snyder</a>, <a shape="rect" class="external-link" href="http://www.nighttale.net/" rel="nofollow">Dejan Bosanac</a> and <a shape="rect" class="external-link" href="http://rajdavies.blogspot.com/" rel="nofollow">Rob Davies</a>. Published by <a shape="rect" class="external-link" href="http://www.manning.com" rel="nofollow">Manning</a>.</p><p><a shape="rect" class="external-link" href="http://bit.ly/2je6cQ" rel="nofollow"><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://www.manning.com/snyder/snyder_cover150.jpg" data-image-src="http://www.manning.com/snyder/snyder_cover150.jpg"></span></a></p><p>Apache ActiveMQ in Action is a thorough, practical guide to implementing message-oriented systems in Java using ActiveMQ. The book lays out the core of ActiveMQ in clear language, starting with the anatomy of a JMS message and moving quickly through connectors, message persistence, authentication and authorization. With the basics well in hand, you move into interesting examples of ActiveMQ at work, following a running Stock Portfolio application. You'll integrate ActiveMQ with containers like Geronimo and JBoss and learn to tie into popular Java-based technologies like Spring Framework.</p><p>Along the way, you'll pick up best practices forged out of the deep experience the authors bring to the book. You'll learn to integrate with non-Java technologies and explore advanced topics like broker topologies and configuration and performance tuning.</p><h3 id="Books-InstantApacheActiveMQMessagingApplicationDevelopment">Instant Apache ActiveMQ Messaging Application Development</h3><p><a shape="rect" class="external-link" href="http://goo.gl/RFltj" rel="nofollow">Instant Apache ActiveMQ Messaging Application Development</a> by <a shape="rect" class="external-link" href="http://timbish.blogspot.com/" rel="nofollow">Timothy Bish</a>. Published by <a shape="rect" class="external-link" href="http://www.packtpub.com/" rel="nofollow">Packt Publishing</a>.</p><p><a shape="rect" class="external-link" href="http://goo.gl/RFltj" rel="nofollow"><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://dgdsbygo8mp3h.cloudfront.net/sites/default/files/imagecache/productview_larger/9413OS.jpg" data-image-src="http://dgdsbygo8mp3h.cloudfront.net/sites/default/files/imagecache/productview_larger/9413OS.jpg"></span></a></p><p>Instant ActiveMQ Application Development How-to is for the developers who are new to Java Message Service application development or new to JMS development using ActiveMQ. Readers will come away ready to solve complicated messaging related problems using the JMS API and ActiveMQ.</p><p>Filled with practical, step-by-step instructions and clear explanations for the most important and useful tasks.This is a Packt Instant How-to guide, which provides concise and practical recipes to help you get started writing applications with ActiveMQ using practical examples.</p><h3 id="Books-MobileandWebMessaging">Mobile and Web Messaging</h3><p><a shape="rect" class="external-link" href="http://shop.oreilly.com/product/0636920032366.do" rel="nofollow">Messaging Protocols for Web and Mobile Devices by Jeff Mesnil. Published by OReilly.</a></p><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://akamaicovers.oreilly.com/images/0636920032366/cat.gif" data-image-src="http://akamaicovers.oreilly.com/images/0636920032366/cat.gif"></span></p><p>Learn how to use messaging technologies to build responsive and resilient applications for mobile devices and web browsers. With this hands-on guide, you’ll use the STOMP and MQTT messaging protocols to write iOS and web applications capable of sending and receiving GPS and device sensor data, text messages, and alerts.</p><h3 id="Books-ApacheActiveMQReferenceGuideKit">Apache ActiveMQ Reference Guide Kit</h3><p>The TTM's "<a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php" rel="nofollow">Apache ActiveMQ Reference Guide</a>" (PDF book) provides information to learn how to implement, deploy, administer, and tune Apache ActiveMQ. The Reference Guide includes details on how to work with ActiveMQ components, connectors, client/broker configuration, master/slave configuration, administration, logging, performance tuning and advanced features.</p></div>
+<div class="wiki-content maincontent"><h1>Books</h1><p>This page lists the known books about Apache ActiveMQ. If you happen to know a book which is not listed then please contact us, for example using the <link><page ri:content-title="Mailing Lists"></page></link>.</p><ul><li><a shape="rect" href="http://bit.ly/2je6cQ">ActiveMQ in Action</a></li><li><a shape="rect" href="http://goo.gl/RFltj">Instant Apache ActiveMQ Messaging Application Development</a></li><li><a shape="rect" href="http://shop.oreilly.com/product/0636920032366.do">Mobile and Web Messaging</a></li><li><a shape="rect" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php">Apache ActiveMQ Reference Guide</a></li></ul><h3>ActiveMQ in Action</h3><p><a shape="rect" href="http://bit.ly/2je6cQ">ActiveMQ in Action</a> by <a shape="rect" href="http://bruceblog.org/">Bruce Snyder</a>, <a shape="rect" href="http://www.nighttale.net/">Dejan Bosanac</a> and <a shape="rect" href="http://rajdavies.blogspot.com/">Rob Davies</a>. Published by <a shape="rect" href="http://www.manning.com">Manning</a>.</p><p><a shape="rect" href="http://bit.ly/2je6cQ"><image><url ri:value="http://www.manning.com/snyder/snyder_cover150.jpg"></url></image></a></p><p>Apache ActiveMQ in Action is a thorough, practical guide to implementing message-oriented systems in Java using ActiveMQ. The book lays out the core of ActiveMQ in clear language, starting with the anatomy of a JMS message and moving quickly through connectors, message persistence, authentication and authorization. With the basics well in hand, you move into interesting examples of ActiveMQ at work, following a running Stock Portfolio application. You'll integrate ActiveMQ with containers like Geronimo and JBoss and learn to tie into popular Java-based technologies like Spring Framework.</p><p>Along the way, you'll pick up best practices forged out of the deep experience the authors bring to the book. You'll learn to integrate with non-Java technologies and explore advanced topics like broker topologies and configuration and performance tuning.</p><h3>Instant Apache ActiveMQ Messaging Application Development</h3><p><a shape="rect" href="http://goo.gl/RFltj">Instant Apache ActiveMQ Messaging Application Development</a> by <a shape="rect" href="http://timbish.blogspot.com/">Timothy Bish</a>. Published by <a shape="rect" href="http://www.packtpub.com/">Packt Publishing</a>.</p><p><a shape="rect" href="http://goo.gl/RFltj"><image><url ri:value="http://dgdsbygo8mp3h.cloudfront.net/sites/default/files/imagecache/productview_larger/9413OS.jpg"></url></image></a></p><p>Instant ActiveMQ Application Development How-to is for the developers who are new to Java Message Service application development or new to JMS development using ActiveMQ. Readers will come away ready to solve complicated messaging related problems using the JMS API and ActiveMQ.</p><p>Filled with practical, step-by-step instructions and clear explanations for the most important and useful tasks.This is a Packt Instant How-to guide, which provides concise and practical recipes to help you get started writing applications with ActiveMQ using practical examples.</p><h3>Mobile and Web Messaging</h3><p><a shape="rect" href="http://shop.oreilly.com/product/0636920032366.do">Messaging Protocols for Web and Mobile Devices by Jeff Mesnil. Published by OReilly.</a></p><p><image><url ri:value="http://akamaicovers.oreilly.com/images/0636920032366/cat.gif"></url></image></p><p>Learn how to use messaging technologies to build responsive and resilient applications for mobile devices and web browsers. With this hands-on guide, you’ll use the STOMP and MQTT messaging protocols to write iOS and web applications capable of sending and receiving GPS and device sensor data, text messages, and alerts.</p><h3>Apache ActiveMQ Reference Guide Kit</h3><p>The TTM's "<a shape="rect" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php">Apache ActiveMQ Reference Guide</a>" (PDF book) provides information to learn how to implement, deploy, administer, and tune Apache ActiveMQ. The Reference Guide includes details on how to work with ActiveMQ components, connectors, client/broker configuration, master/slave configuration, administration, logging, performance tuning and advanced features.</p></div>
diff --git a/broadcasting.xml b/broadcasting.xml
index 3dcfb57..7d9c98b 100644
--- a/broadcasting.xml
+++ b/broadcasting.xml
@@ -5,8 +5,7 @@
<p>To use a BlazeChannel create one from the a factory:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f30411e7-098a-436f-aee0-aef2d1b9764d" ac:name="code" ac:schema-version="1"><plain-text-body>
import org.apache.activeblaze.*;
...
BlazeChannelFactory factory = new BlazeChannelFactory();
@@ -14,18 +13,16 @@
//start the channel and send a message
sender.start();
-String destination = "foo.bar";
-BlazeMessage msg = new BlazeMessage("test payload");
+String destination = "foo.bar";
+BlazeMessage msg = new BlazeMessage("test payload");
sender.broadcast(destination,msg);
//shutdown the sender
sender.shutDown();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>You can similarly subscribe to Topic messages by using a listener</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f52abf76-f5a1-49db-b7a5-88dcf8f9b651" ac:name="code" ac:schema-version="1"><plain-text-body>
BlazeChannel receiver = factory.createChannel();
receiver.start();
@@ -33,11 +30,10 @@
receiver.addBlazeTopicMessageListener(destination, new BlazeMessageListener() {
public void onMessage(BlazeMessage msg) {
- System.out.println("Got a msg: " + msg);
+ System.out.println("Got a msg: " + msg);
}
});
receiver.shutDown();
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/broker-camel-component.xml b/broker-camel-component.xml
index aafa00c..42e61d5 100644
--- a/broker-camel-component.xml
+++ b/broker-camel-component.xml
@@ -1,35 +1,31 @@
-<div class="wiki-content maincontent"><h2 id="BrokerCamelComponent-BrokerCamelComponent">Broker Camel Component</h2><p><strong>Available as of ActiveMQ 5.9</strong></p><p>Embedding Apache Camel inside the ActiveMQ broker provides great flexibility for extending the message broker with the integration power of Camel. Apache Camel routes also benefit in that you can avoid the serialization and network costs of connecting to ActiveMQ remotely - if you use the <a shape="rect" class="external-link" href="http://camel.apache.org/activemq.html">activemq component</a>.</p><p>If however, you want to change the behavior of messages flowing through the ActiveMQ message broker itself you will be limited to the shipped set of ActiveMQ broker <a shape="rect" class="external-link" href="http://activemq.apache.org/interceptors.html">Interceptors</a> - or develop your own <a shape="rect" class="external-link" href="http://activemq.apache.org/developing-plugins.html">Broker plugin</a> and then introduce that as a jar on to the class path for the ActiveMQ broker. The <strong><code>broker</code></strong> Camel component makes this even easier. It intercepts messages as they move through the broker itself, allowing them to be modified and manipulated before they are persisted to the message store or delivered to end consumers.</p><p>For example <a shape="rect" class="external-link" href="http://activemq.apache.org/how-should-i-package-applications-using-camel-and-activemq.html">by defining a CamelContext to run inside the broker's JVM </a>the <strong><code>broker</code></strong> component can intercept all messages published to a Topic, say, and publish them to a Queue instead, changing their priority along the way:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<route id="setPriority">
- <from uri="broker:topic:test.broker.>"/>
- <setHeader headerName="JMSPriority">
+<div class="wiki-content maincontent"><h2>Broker Camel Component</h2><p><strong>Available as of ActiveMQ 5.9</strong></p><p>Embedding Apache Camel inside the ActiveMQ broker provides great flexibility for extending the message broker with the integration power of Camel. Apache Camel routes also benefit in that you can avoid the serialization and network costs of connecting to ActiveMQ remotely - if you use the <a shape="rect" href="http://camel.apache.org/activemq.html">activemq component</a>.</p><p>If however, you want to change the behavior of messages flowing through the ActiveMQ message broker itself you will be limited to the shipped set of ActiveMQ broker <a shape="rect" href="http://activemq.apache.org/interceptors.html">Interceptors</a> - or develop your own <a shape="rect" href="http://activemq.apache.org/developing-plugins.html">Broker plugin</a> and then introduce that as a jar on to the class path for the ActiveMQ broker. The <strong><code>broker</code></strong> Camel component makes this even easier. It intercepts messages as they move through the broker itself, allowing them to be modified and manipulated before they are persisted to the message store or delivered to end consumers.</p><p>For example <a shape="rect" href="http://activemq.apache.org/how-should-i-package-applications-using-camel-and-activemq.html">by defining a CamelContext to run inside the broker's JVM </a>the <strong><code>broker</code></strong> component can intercept all messages published to a Topic, say, and publish them to a Queue instead, changing their priority along the way:</p><structured-macro ac:macro-id="46808b45-4f42-4c77-8d11-b064dc9fa99c" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><route id="setPriority">
+ <from uri="broker:topic:test.broker.>"/>
+ <setHeader headerName="JMSPriority">
<constant>9</constant>
</setHeader>
- <to uri="broker:queue:test.broker.component.queue"/>
+ <to uri="broker:queue:test.broker.component.queue"/>
</route>
-]]></script>
-</div></div><p>Notes:</p><ul><li>A broker component only adds an intercept into the broker if its started - so the broker component will not add any overhead to the running broker until its used - and then the overhead will be trivial.</li><li>Messages are intercepted by the broker component when they have been received by the broker - but before they are processed (persisted or routed to a destination).</li><li>The <strong><code>IN</code></strong> message on the Exchange is a <strong><code>CamelMessage</code></strong>, but also a JMS Message (messages routed through ActiveMQ from STOMP/MQTT/AMQP etc. are always translated into JMS messages).</li><li>W<a shape="rect" class="external-link" href="http://activemq.apache.org/wildcards.html">ildcards</a> can be used on a destination to intercept messages from destinations matching the wildcard.</li><li>After the intercept, you have to explicitly send the message back to the broker component - this allows you to either drop select messages (by not sending) - or, like in the above case - re-route the message to a different destination.<br clear="none"><br clear="none"></li></ul><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>There is one deliberate caveat though, only intercepted messages can be sent to a <strong><code>broker</code></strong> component. For example, routing a Camel message from another Component e.g. <strong><code>file</code></strong>, will result in an error.</p></div></div><p>Extra classes that have been added to the <strong><code>activemq-broker</code></strong> package to support the <strong><code>broker</code></strong> component. They allow the state of the running broker to be interrogated without using JMX. These classes are:</p><ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.9.0/apidocs/org/apache/activemq/broker/view/MessageBrokerView.html">org.apache.activemq.broker.view.MessageBrokerView</a> - provides methods to retrieve statistics on a the broker</li><li>From the <strong><code>org.apache.activemq.broker.view.MessageBrokerView</code></strong> - you can retrieve a <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.9.0/apidocs/org/apache/activemq/broker/view/BrokerDestinationView.html">org.apache.activemq.broker.view.BrokerDestinationView</a> for a particular destination.</li></ul><h3 id="BrokerCamelComponent-Example">Example</h3><p>How to route messages when a destination's queue depth has reached a certain limit:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<camelContext id="camel" trace="false" xmlns="http://camel.apache.org/schema/spring">
- <route id="routeAboveQueueLimitTest">
- <from uri="broker:queue:test.broker.queue"/>
+</plain-text-body></structured-macro><p>Notes:</p><ul><li>A broker component only adds an intercept into the broker if its started - so the broker component will not add any overhead to the running broker until its used - and then the overhead will be trivial.</li><li>Messages are intercepted by the broker component when they have been received by the broker - but before they are processed (persisted or routed to a destination).</li><li>The <strong><code>IN</code></strong> message on the Exchange is a <strong><code>CamelMessage</code></strong>, but also a JMS Message (messages routed through ActiveMQ from STOMP/MQTT/AMQP etc. are always translated into JMS messages).</li><li>W<a shape="rect" href="http://activemq.apache.org/wildcards.html">ildcards</a> can be used on a destination to intercept messages from destinations matching the wildcard.</li><li>After the intercept, you have to explicitly send the message back to the broker component - this allows you to either drop select messages (by not sending) - or, like in the above case - re-route the message to a different destination.<br clear="none"><br clear="none"></li></ul><structured-macro ac:macro-id="7fd157e0-4ac6-4027-9539-96ed3ed4828e" ac:name="warning" ac:schema-version="1"><rich-text-body><p>There is one deliberate caveat though, only intercepted messages can be sent to a <strong><code>broker</code></strong> component. For example, routing a Camel message from another Component e.g. <strong><code>file</code></strong>, will result in an error.</p></rich-text-body></structured-macro><p>Extra classes that have been added to the <strong><code>activemq-broker</code></strong> package to support the <strong><code>broker</code></strong> component. They allow the state of the running broker to be interrogated without using JMX. These classes are:</p><ul><li><a shape="rect" href="http://activemq.apache.org/maven/5.9.0/apidocs/org/apache/activemq/broker/view/MessageBrokerView.html">org.apache.activemq.broker.view.MessageBrokerView</a> - provides methods to retrieve statistics on a the broker</li><li>From the <strong><code>org.apache.activemq.broker.view.MessageBrokerView</code></strong> - you can retrieve a <a shape="rect" href="http://activemq.apache.org/maven/5.9.0/apidocs/org/apache/activemq/broker/view/BrokerDestinationView.html">org.apache.activemq.broker.view.BrokerDestinationView</a> for a particular destination.</li></ul><h3>Example</h3><p>How to route messages when a destination's queue depth has reached a certain limit:</p><structured-macro ac:macro-id="15dd6e15-edd6-4a5e-9a16-c0faf86e2c2a" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><camelContext id="camel" trace="false" xmlns="http://camel.apache.org/schema/spring">
+ <route id="routeAboveQueueLimitTest">
+ <from uri="broker:queue:test.broker.queue"/>
<choice>
<when>
<spel>#{@destinationView.queueSize >= 100}</spel>
- <to uri="broker:queue:test.broker.processLater"/>
+ <to uri="broker:queue:test.broker.processLater"/>
</when>
<otherwise>
- <to uri="broker:queue:test.broker.queue"/>
+ <to uri="broker:queue:test.broker.queue"/>
</otherwise>
</choice>
</route>
</camelContext>
-<bean id="brokerView" class="org.apache.activemq.broker.view.MessageBrokerView">
- <constructor-arg value="testBroker"/>
+<bean id="brokerView" class="org.apache.activemq.broker.view.MessageBrokerView">
+ <constructor-arg value="testBroker"/>
</bean>
-<bean id="destinationView" factory-bean="brokerView" factory-method="getDestinationView">
- <constructor-arg value="test.broker.component.route"/>
+<bean id="destinationView" factory-bean="brokerView" factory-method="getDestinationView">
+ <constructor-arg value="test.broker.component.route"/>
</bean>
-]]></script>
-</div></div><p>This is using the Camel Message Router pattern. Note the use of the Spring expression language <strong><code>spel</code></strong> in the <strong><code>when</code></strong> clause.</p><p> </p></div>
+</plain-text-body></structured-macro><p>This is using the Camel Message Router pattern. Note the use of the Spring expression language <strong><code>spel</code></strong> in the <strong><code>when</code></strong> clause.</p><p> </p></div>
diff --git a/broker-configuration-uri.xml b/broker-configuration-uri.xml
index db1e2d7..aa7d8ce 100644
--- a/broker-configuration-uri.xml
+++ b/broker-configuration-uri.xml
@@ -1,12 +1,12 @@
-<div class="wiki-content maincontent"><h3 id="BrokerConfigurationURI-Overview">Overview</h3>
+<div class="wiki-content maincontent"><h3>Overview</h3>
<p>An ActiveMQ broker can be extensivly configured using a single configuration URI. The following URI schemes are supported</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Scheme</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> xbean: </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="broker-xbean-uri.xml">Broker XBean URI</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Configures the broker using an <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> from an XML file which is on the classpath (or in 4.2 onwards can be on the file system or an external URL) which uses Spring and xbean-spring to configure the broker </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> broker: </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="broker-uri.xml">Broker URI</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Configures the broker explicitly using a URI syntax </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> properties: </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="broker-properties-uri.xml">Broker Properties URI</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Configures the broker explicitly using a URI syntax </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Scheme</p></th><th colspan="1" rowspan="1"><p>Link</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p> xbean: </p></td><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Broker XBean URI"></page></link> </p></td><td colspan="1" rowspan="1"><p> Configures the broker using an <link><page ri:content-title="Xml Configuration"></page></link> from an XML file which is on the classpath (or in 4.2 onwards can be on the file system or an external URL) which uses Spring and xbean-spring to configure the broker </p></td></tr><tr><td colspan="1" rowspan="1"><p> broker: </p></td><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Broker URI"></page></link> </p></td><td colspan="1" rowspan="1"><p> Configures the broker explicitly using a URI syntax </p></td></tr><tr><td colspan="1" rowspan="1"><p> properties: </p></td><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Broker Properties URI"></page></link> </p></td><td colspan="1" rowspan="1"><p> Configures the broker explicitly using a URI syntax </p></td></tr></tbody></table>
-<p>For the most flexible and powerful option we recommend the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> via the <a shape="rect" href="broker-xbean-uri.xml">Broker XBean URI</a> to configure AcitveMQ brokers. </p>
+<p>For the most flexible and powerful option we recommend the <link><page ri:content-title="Xml Configuration"></page></link> via the <link><page ri:content-title="Broker XBean URI"></page></link> to configure AcitveMQ brokers. </p>
-<p>If you are worried about jar dependencies then either the <a shape="rect" href="broker-uri.xml">Broker URI</a> or the <a shape="rect" href="broker-properties-uri.xml">Broker Properties URI</a> are useful as they are very simple and require no dependencies on Spring or xbean-spring and don't require any XML.</p></div>
+<p>If you are worried about jar dependencies then either the <link><page ri:content-title="Broker URI"></page></link> or the <link><page ri:content-title="Broker Properties URI"></page></link> are useful as they are very simple and require no dependencies on Spring or xbean-spring and don't require any XML.</p></div>
diff --git a/broker-properties-uri.xml b/broker-properties-uri.xml
index 13f5f95..b905668 100644
--- a/broker-properties-uri.xml
+++ b/broker-properties-uri.xml
@@ -1,10 +1,7 @@
-<div class="wiki-content maincontent"><h2 id="BrokerPropertiesURI-BrokerPropertiesURI">Broker Properties URI</h2><p>From version 4.2 of ActiveMQ onwards the Broker Properties URI allows you to <a shape="rect" href="run-broker.xml">run a configured broker</a> by referencing a properties file which could be on the classpath, a local file or a remote URL.</p><h4 id="BrokerPropertiesURI-Syntax">Syntax</h4><p><strong>properties:name</strong></p><p>Where name is some name which is resolved on the classpath, as a local file or a remote URL which points to the properties file used to configure the broker.</p><h5 id="BrokerPropertiesURI-ExampleURI">Example URI</h5><p>The following examples show variations in using the URI</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>properties:/foo/bar.properties
+<div class="wiki-content maincontent"><h2>Broker Properties URI</h2><p>From version 4.2 of ActiveMQ onwards the Broker Properties URI allows you to <link><page ri:content-title="Run Broker"></page><plain-text-link-body>run a configured broker</plain-text-link-body></link> by referencing a properties file which could be on the classpath, a local file or a remote URL.</p><h4>Syntax</h4><p><strong>properties:name</strong></p><p>Where name is some name which is resolved on the classpath, as a local file or a remote URL which points to the properties file used to configure the broker.</p><h5>Example URI</h5><p>The following examples show variations in using the URI</p><structured-macro ac:macro-id="632155fb-8fe5-43c9-bb92-058d3e71366f" ac:name="noformat" ac:schema-version="1"><plain-text-body>properties:/foo/bar.properties
properties:foo.properties
properties:http://foo.com/foo.properties
-</pre>
-</div></div><p>Here is <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/config/broker.properties">an example properties file</a></p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>## ---------------------------------------------------------------------------
+</plain-text-body></structured-macro><p>Here is <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/config/broker.properties">an example properties file</a></p><structured-macro ac:macro-id="8e337744-7484-4c40-afec-e78bdd572746" ac:name="noformat" ac:schema-version="1"><plain-text-body>## ---------------------------------------------------------------------------
## Licensed to the Apache Software Foundation (ASF) under one or more
## contributor license agreements. See the NOTICE file distributed with
## this work for additional information regarding copyright ownership.
@@ -25,6 +22,5 @@
persistent = false
brokerName = Cheese
# END SNIPPET: example
-</pre>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/broker-uri.xml b/broker-uri.xml
index 1451726..641ffb3 100644
--- a/broker-uri.xml
+++ b/broker-uri.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><h2 id="BrokerURI-BrokerURI">Broker URI</h2>
+<div class="wiki-content maincontent"><h2>Broker URI</h2>
-<p>The Broker URI allows you to <a shape="rect" href="run-broker.xml">run a configured broker</a> using a single URI for all the configuration.</p>
+<p>The Broker URI allows you to <link><page ri:content-title="Run Broker"></page><link-body>run a configured broker</link-body></link> using a single URI for all the configuration.</p>
-<h4 id="BrokerURI-Syntax">Syntax</h4>
+<h4>Syntax</h4>
<p>The URI is assumed to be a composite uri with multiple uris that are used to bind the connectors of the broker.</p>
@@ -11,23 +11,22 @@
<p>If a composite URI use the network: scheme, then the rest of the URI is bound as a network connector.</p>
-<h5 id="BrokerURI-BrokerOptions">Broker Options</h5>
+<h5>Broker 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>useJmx</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker be exposed to JMX?</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>persistent</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker use persistent storage</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>populateJMSXUserID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker populate the <a shape="rect" href="jmsxuserid.xml">JMSXUserID</a> property of messages to indicate the authenticated sender username who sent the message</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useShutdownHook</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>should the broker install a shutdown hook so that it can properly shut itself down on a JVM kill</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>brokerName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>localhost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the broker</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>deleteAllMessagesOnStartup</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should all the messages in the persistent store be deleted on broker startup</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>enableStatistics</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should statistics gathering be enabled</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>useJmx</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should the broker be exposed to JMX?</p></td></tr><tr><td colspan="1" rowspan="1"><p>persistent</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should the broker use persistent storage</p></td></tr><tr><td colspan="1" rowspan="1"><p>populateJMSXUserID</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should the broker populate the <link><page ri:content-title="JMSXUserID"></page></link> property of messages to indicate the authenticated sender username who sent the message</p></td></tr><tr><td colspan="1" rowspan="1"><p>useShutdownHook</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>should the broker install a shutdown hook so that it can properly shut itself down on a JVM kill</p></td></tr><tr><td colspan="1" rowspan="1"><p>brokerName</p></td><td colspan="1" rowspan="1"><p>localhost</p></td><td colspan="1" rowspan="1"><p>The name of the broker</p></td></tr><tr><td colspan="1" rowspan="1"><p>deleteAllMessagesOnStartup</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should all the messages in the persistent store be deleted on broker startup</p></td></tr><tr><td colspan="1" rowspan="1"><p>enableStatistics</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should statistics gathering be enabled</p></td></tr></tbody></table>
-<h5 id="BrokerURI-ExampleURI">Example URI</h5>
+<h5>Example URI</h5>
<p>The following example starts up a broker accepting connections on port 61616, and establishes a network connection to remotehost:61616 and disables persistence.</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>broker:(tcp://localhost:61616,network:static:tcp://remotehost:61616)?persistent=false&useJmx=true
-</pre>
-</div></div>
+<structured-macro ac:macro-id="35981ad4-c2b0-4fcf-bb9e-612ecd03d351" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+broker:(tcp://localhost:61616,network:static:tcp://remotehost:61616)?persistent=false&useJmx=true
+</plain-text-body></structured-macro>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">You can use the Broker URI on other transports</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>If you are using another transport - such as the <a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a> then you can refer to the above broker URI properties inside that URL. e.g. using the URL</p>
+<structured-macro ac:macro-id="b7bfcf5a-8d17-471e-a907-133785ea5950" ac:name="info" ac:schema-version="1"><parameter ac:name="title">You can use the Broker URI on other transports</parameter><rich-text-body>
+<p>If you are using another transport - such as the <link><page ri:content-title="VM Transport Reference"></page></link> then you can refer to the above broker URI properties inside that URL. e.g. using the URL</p>
-<p>vm://localhost?broker.persistent=false</p></div></div></div>
+<p>vm://localhost?broker.persistent=false</p></rich-text-body></structured-macro></div>
diff --git a/broker-xbean-uri.xml b/broker-xbean-uri.xml
index 6456dcc..5e76c8b 100644
--- a/broker-xbean-uri.xml
+++ b/broker-xbean-uri.xml
@@ -1,28 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="BrokerXBeanURI-BrokerXBeanURI">Broker XBean URI</h2>
+<div class="wiki-content maincontent"><h2>Broker XBean URI</h2>
-<p>The Broker XBean URI allows you to <a shape="rect" href="run-broker.xml">run a configured broker</a> by referencing an <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> on the classpath. The URI points to an XML document which can be parsed via XBean or Spring. This URI is typically on the classpath; though in 4.2 onwards you can point to a file or URL as well.</p>
+<p>The Broker XBean URI allows you to <link><page ri:content-title="Run Broker"></page><link-body>run a configured broker</link-body></link> by referencing an <link><page ri:content-title="Xml Configuration"></page></link> on the classpath. The URI points to an XML document which can be parsed via XBean or Spring. This URI is typically on the classpath; though in 4.2 onwards you can point to a file or URL as well.</p>
-<h4 id="BrokerXBeanURI-Syntax">Syntax</h4>
+<h4>Syntax</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Syntax </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> xbean:classPathResource </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Where classPathResource is some name which is resolved on the classpath and interpreted to be an XML document. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> xbean:</p>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Syntax </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> xbean:classPathResource </p></td><td colspan="1" rowspan="1"><p> Where classPathResource is some name which is resolved on the classpath and interpreted to be an XML document. </p></td></tr><tr><td colspan="1" rowspan="1"><p> xbean:</p>
file:filePathResource
-<p></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Where filePathResource is some name which is resolved on the file system and interpreted to be an XML document. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> xbean:urlResource </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Where urlResource is some resource which points to an XML document </p></td></tr></tbody></table></div>
+<p></p></td><td colspan="1" rowspan="1"><p> Where filePathResource is some name which is resolved on the file system and interpreted to be an XML document. </p></td></tr><tr><td colspan="1" rowspan="1"><p> xbean:urlResource </p></td><td colspan="1" rowspan="1"><p> Where urlResource is some resource which points to an XML document </p></td></tr></tbody></table>
-<h5 id="BrokerXBeanURI-ExampleURI">Example URI</h5>
+<h5>Example URI</h5>
<p>The following example starts up a broker using the activemq.xml configuration file which is on the classpath</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>xbean:activemq.xml
-</pre>
-</div></div>
+<structured-macro ac:macro-id="6e9a3e33-967a-4bd2-bc8b-e1471f52fcab" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+xbean:activemq.xml
+</plain-text-body></structured-macro>
<p>The following example starts up a broker using the activemq.xml configuration file which is in the current directory</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>xbean:file:./activemq.xml
-</pre>
-</div></div> </div>
+<structured-macro ac:macro-id="f555bed5-94eb-497b-8756-df9a749cf33b" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+xbean:file:./activemq.xml
+</plain-text-body></structured-macro> </div>
diff --git a/building-activemq-cpp.xml b/building-activemq-cpp.xml
index 9f664a1..49725ca 100644
--- a/building-activemq-cpp.xml
+++ b/building-activemq-cpp.xml
@@ -1,40 +1,36 @@
-<div class="wiki-content maincontent"><h2 id="BuildingActiveMQCPP-Dependencies">Dependencies</h2>
+<div class="wiki-content maincontent"><h2>Dependencies</h2>
-<h3 id="BuildingActiveMQCPP-libuuid">libuuid</h3>
+<h3>libuuid</h3>
-<p>The build requires the <strong>libuuid</strong> library that is part of the e2fsprogs package and is available from <a shape="rect" class="external-link" href="http://e2fsprogs.sourceforge.net/" rel="nofollow">http://e2fsprogs.sourceforge.net/</a> which is not always installed by default.</p>
+<p>The build requires the <strong>libuuid</strong> library that is part of the e2fsprogs package and is available from <a shape="rect" href="http://e2fsprogs.sourceforge.net/">http://e2fsprogs.sourceforge.net/</a> which is not always installed by default.</p>
-<h3 id="BuildingActiveMQCPP-cppunit">cppunit</h3>
+<h3>cppunit</h3>
-<p>The package contains a complete set of cppunit tests. In order for you to build an run the tests, you will need to download and install the cppunit suite. See <a shape="rect" class="external-link" href="http://cppunit.sourceforge.net/cppunit-wiki" rel="nofollow">http://cppunit.sourceforge.net/cppunit-wiki</a></p>
+<p>The package contains a complete set of cppunit tests. In order for you to build an run the tests, you will need to download and install the cppunit suite. See <a shape="rect" href="http://cppunit.sourceforge.net/cppunit-wiki">http://cppunit.sourceforge.net/cppunit-wiki</a></p>
<p>or on Fedora type the following:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e1010969-446e-40b3-8b0e-6d6fec1fe8ba" ac:name="code" ac:schema-version="1"><plain-text-body>
sudo yum install cppunit
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Make sure that the paths to the installed cppunit library and includes are visible in your current shell before you try building the tests.</p>
-<p>Windows users will need to build the cppunit library using the CPPUnit MSVC project files.  A discussion of the build process can be found on the CPPUnit wiki under <a shape="rect" class="external-link" href="http://cppunit.sourceforge.net/cppunit-wiki/BuildingCppUnit1" rel="nofollow">CPPUnit Platform build instructions</a> this covers both MSVC along with many other platforms and tool suites.</p>
+<p>Windows users will need to build the cppunit library using the CPPUnit MSVC project files.  A discussion of the build process can be found on the CPPUnit wiki under <a shape="rect" href="http://cppunit.sourceforge.net/cppunit-wiki/BuildingCppUnit1">CPPUnit Platform build instructions</a> this covers both MSVC along with many other platforms and tool suites.</p>
-<h3 id="BuildingActiveMQCPP-GNUBuildSystem(forbuildingon*nix)">GNU Build System (for building on *nix)</h3>
+<h3>GNU Build System (for building on *nix)</h3>
<p>To Generate the ./configure script use to create the Makefiles, you need the following software installed:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Tool </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Recommended Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> autoconf </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> >= 2.59 <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> automake </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> >= 1.9.6 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> libtool </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> >= 1.5.22 <br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Tool </p></th><th colspan="1" rowspan="1"><p> Recommended Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> autoconf </p></td><td colspan="1" rowspan="1"><p> >= 2.59 <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> automake </p></td><td colspan="1" rowspan="1"><p> >= 1.9.6 </p></td></tr><tr><td colspan="1" rowspan="1"><p> libtool </p></td><td colspan="1" rowspan="1"><p> >= 1.5.22 <br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table>
-<h2 id="BuildingActiveMQCPP-Buildingon*nix(Unix/Linux/OSX/Cygwin)">Building on *nix (Unix/Linux/OS X/Cygwin)</h2>
+<h2>Building on *nix (Unix/Linux/OS X/Cygwin)</h2>
<p>This assumes you have all of the project dependencies installed. We're now ready to create the configure script. To do this, run:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="73cdd5b7-0cf4-4d99-9c40-50618a8b1dfd" ac:name="code" ac:schema-version="1"><plain-text-body>
./autogen.sh
-]]></script>
-</div></div>
-<div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+</plain-text-body></structured-macro>
+<structured-macro ac:macro-id="69a5c84d-28fe-446a-8fbe-284d846c1db6" ac:name="info" ac:schema-version="1"><rich-text-body>
<p>You may see the following warnings when running this command:</p>
<p>src/test-integration/Makefile.am:44: `CXXFLAGS' is a user variable, you should not override it;<br clear="none">
@@ -42,96 +38,77 @@
src/test/Makefile.am:104: `CXXFLAGS' is a user variable, you should not override it;<br clear="none">
src/test/Makefile.am:104: use `AM_CXXFLAGS' instead.</p>
-<p>These can be ignored. We override CXXFLAGS in the makefiles for the unit and integration tests in order to suppress compiler warnings.</p></div></div>
+<p>These can be ignored. We override CXXFLAGS in the makefiles for the unit and integration tests in order to suppress compiler warnings.</p></rich-text-body></structured-macro>
<p>This should be run the first time and anytime you change configure.ac or any of the Makefile.am files.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Solaris 10 Note</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<structured-macro ac:macro-id="80a1c3af-3159-43ce-8138-6ecb3d37b68c" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Solaris 10 Note</parameter><rich-text-body>
<p>CPP_UNIT might not build until you correct the file libstdc++.la to contain the correct data, see this discussion.</p>
-<p><a shape="rect" class="external-link" href="http://forum.sun.com/jive/thread.jspa?threadID=73150" rel="nofollow">http://forum.sun.com/jive/thread.jspa?threadID=73150</a></p></div></div>
+<p><a shape="rect" href="http://forum.sun.com/jive/thread.jspa?threadID=73150">http://forum.sun.com/jive/thread.jspa?threadID=73150</a></p></rich-text-body></structured-macro>
<p>The configure script will customize the way the software is built and installed into your system along with detecting the available libraries that have been installed. To use the default configuration just run:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="205c26b2-1371-4bf8-abbc-41d2eea6f006" ac:name="code" ac:schema-version="1"><plain-text-body>
./configure
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>For more help on how to customize the build configuration, run:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9b6a11a7-08f6-4ac1-99fc-d076a7458244" ac:name="code" ac:schema-version="1"><plain-text-body>
./configure --help
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Once the configure script has run successfully, you are ready to build. Run:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f50bfe43-4a94-495e-99b0-1ab21f6212dd" ac:name="code" ac:schema-version="1"><plain-text-body>
make
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This will build all of the core ActiveMQ CPP source code. To build and install the code into the system directories, run:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="cf308ba3-9be2-47a4-8d29-ab6abe737c53" ac:name="code" ac:schema-version="1"><plain-text-body>
make install
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>You will have to become the superuser in order to be able to install the files.</p>
-<h2 id="BuildingActiveMQCPP-Doxygen">Doxygen</h2>
+<h2>Doxygen</h2>
<p>To generate the doxygen documentation for the project, just run:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="7a959d3b-8ad9-46bd-99e0-c2136169c31d" ac:name="code" ac:schema-version="1"><plain-text-body>
make doxygen-run
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="BuildingActiveMQCPP-RunningTests">Running Tests</h2>
+<h2>Running Tests</h2>
-<h3 id="BuildingActiveMQCPP-UnitTests">Unit Tests</h3>
+<h3>Unit Tests</h3>
<p>In order to build and run the suite of unit tests, run:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="355a0924-32b9-43e1-af0e-35b2c78acc6f" ac:name="code" ac:schema-version="1"><plain-text-body>
make check
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This will verify that the library is functioning correctly on the target platform. In addition, it will generate the integration tests binary.</p>
-<h3 id="BuildingActiveMQCPP-IntegrationTests">Integration Tests</h3>
+<h3>Integration Tests</h3>
<p>The library also contains a set of tests that are run against a real AMQ broker. These allow you to validate this distribution of ActiveMQ CPP against your broker. Running these without a broker will result in failed tests. The tests currently hard-code the broker url to be tcp://localhost:61613 for stomp and tcp://localhost:61616 for openwire.</p>
<p>The integration tests are built via "make check". To run them, first start a broker and then</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="84f4a992-211a-4466-b719-5932731f018a" ac:name="code" ac:schema-version="1"><plain-text-body>
cd src/test-integration
./activemq-test-integration
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This will take quite some time to complete, so be patient.</p>
-<h2 id="BuildingActiveMQCPP-Example">Example</h2>
+<h2>Example</h2>
<p>There is an example application that ships with the distribution in src/examples. The example is compiled by default with the "make" command, but can easily be compiled manually using the command:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b0fc5b8c-b49c-4a70-9cea-6b7bc430239d" ac:name="code" ac:schema-version="1"><plain-text-body>
g++ -o main -pthread -I ../main main.cpp ../../out/libactivemq-cpp-0_0_2.a -luuid
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="BuildingActiveMQCPP-NotesforWindowsusers">Notes for Windows users</h2>
+<h2>Notes for Windows users</h2>
<p>We support using the GNU compiler on Windows, using the Cygwin package. However we also support using the MSVC compiler on Windows.</p>
<p>There are a couple or things that you will need to setup to ensure that the MSVC compile succeeds.</p>
<ul><li>You need to download and install the Platform SDK if you don't have it installed already.</li><li>Ensure that the path to you MSVC install is set in the PATH env variable. You can test this by typing cl.exe at the command line, if you get an error complaining that its not found, then you'll need to fix your PATH.</li><li>Set the INCLUDE env variable to include the path to your MSVC includes, and the platform SDK includes. For example:
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1bcf5725-bbc2-4cfe-b378-7abd123ce11a" ac:name="code" ac:schema-version="1"><plain-text-body>
INCLUDE = D:\Program Files\Microsoft Visual Studio 8\VC\include;D:\Program Files\Microsoft Platform SDK\Include\*
-]]></script>
-</div></div></li><li>Set the LIB env variable to include the path to your MSVC libs, and the Platform SDK libs. For example:
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+</plain-text-body></structured-macro></li><li>Set the LIB env variable to include the path to your MSVC libs, and the Platform SDK libs. For example:
+<structured-macro ac:macro-id="9d551a9f-b5d7-4ff7-a8f7-236917531e81" ac:name="code" ac:schema-version="1"><plain-text-body>
LIB = D:\Program Files\Microsoft Visual Studio 8\VC\lib;D:\Program Files\Microsoft Platform SDK\Lib
-]]></script>
-</div></div></li><li>The Project files reference the CPPUnit libraries for the Integration and Unit tests builds.  In order for these to build correctly you must either place the CPPUnit libraries in a directory listed in the project settings, or add a new location for your install of CPPUnit. </li></ul></div>
+</plain-text-body></structured-macro></li><li>The Project files reference the CPPUnit libraries for the Integration and Unit tests builds.  In order for these to build correctly you must either place the CPPUnit libraries in a directory listed in the project settings, or add a new location for your install of CPPUnit. </li></ul>
+</div>
diff --git a/building.xml b/building.xml
index bc5a02a..5f7c835 100644
--- a/building.xml
+++ b/building.xml
@@ -1,20 +1,8 @@
-<div class="wiki-content maincontent"><h2 id="Building-BuildingActiveMQfromSource">Building ActiveMQ from Source</h2><p>ActiveMQ uses <a shape="rect" class="external-link" href="http://maven.apache.org/">Maven</a> as its build and management tool. If you don't fancy using Maven you can use your IDE directly or <a shape="rect" href="download.xml">Download</a> a distribution or JAR.</p><h3 id="Building-Prequisites">Prequisites</h3><p><strong>Required:</strong></p><ul><li>Download and <a shape="rect" class="external-link" href="http://maven.apache.org/download.html">install Maven</a>.</li><li>Get the latest <a shape="rect" href="source.xml">Source</a></li><li>JDK (1.6 for version <= 5.10, 1.7 for version > 5.10)</li></ul><h2 id="Building-UsingMaven2(ActiveMQ4.1.xandUp)">Using Maven 2 (ActiveMQ 4.1.x and Up)</h2><p>ActiveMQ 4.1.x and up use Maven 2 to Build. We recommend you download and install <a shape="rect" class="external-link" href="http://maven.apache.org/download.html">Maven 2.0.4</a>.</p><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>You should set the MAVEN_OPTS environment variable to -Xmx800m. There are portions of the ActiveMQ build that are very memory intensive. Increase the maven memory limit so that the build does not fail for you.</p></div></div><h3 id="Building-DoingaQuickBuild">Doing a Quick Build</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn -Dtest=false -DfailIfNoTests=false clean install
-]]></script>
-</div></div><h3 id="Building-UsinganIDE">Using an IDE</h3><p>If you prefer to use an IDE then you can auto-generate the IDE's project files using maven plugins. e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn eclipse:eclipse
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn idea:idea
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Importing into Eclipse</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you have not already done so, you will need to make Eclipse aware of the Maven repository so that it can build everything. In the preferences, go to Java->Build Path->Classpath and define a new Classpath Variable named M2_REPO that points to your local Maven repository (i.e., <code>~/.m2/repository</code> on Unix and <code>c:\Documents and Settings\<user>\.m2\repository</code> on Windows).</p></div></div><h3 id="Building-OtherMaven2Goals">Other Maven 2 Goals</h3><p>For more details try the <a shape="rect" href="examples.xml">Examples</a> or <a shape="rect" href="benchmark-tests.xml">Benchmark Tests</a><br clear="none"> Please refer to the <a shape="rect" class="external-link" href="http://maven.apache.org/plugins/index.html">plugin reference</a> for more details on using them.</p><h2 id="Building-UsingMaven1(ActiveMQ4.0.xandDown)">Using Maven 1 (ActiveMQ 4.0.x and Down)</h2><p>ActiveMQ 4.0.x and down use Maven 1 to Build. We recommend you download and install <a shape="rect" class="external-link" href="http://maven.apache.org/maven-1.x/start/download.html">Maven 1.0.2</a>.</p><h3 id="Building-DoingaQuickBuild.1">Doing a Quick Build</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[maven -Dmaven.test.skip.exec=true
-]]></script>
-</div></div><h3 id="Building-UsinganIDE.1">Using an IDE</h3><p>If you prefer to use an IDE then you can autogenerate the IDE's project files using maven plugins. e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[maven eclipse
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[maven idea
-]]></script>
-</div></div><p>etc.</p><h3 id="Building-OtherMaven1Goals">Other Maven 1 Goals</h3><p>For more details try the <a shape="rect" href="examples.xml">Examples</a> or <a shape="rect" href="benchmark-tests.xml">Benchmark Tests</a><br clear="none"> Please refer to the <a shape="rect" class="external-link" href="http://maven.apache.org/maven-1.x/plugins/bundled/">plugin reference</a> for more details on using them.</p></div>
+<div class="wiki-content maincontent"><h2>Building ActiveMQ from Source</h2><p>ActiveMQ uses <a shape="rect" href="http://maven.apache.org/">Maven</a> as its build and management tool. If you don't fancy using Maven you can use your IDE directly or <link><page ri:content-title="Download"></page></link> a distribution or JAR.</p><h3>Prequisites</h3><p><strong>Required:</strong></p><ul><li>Download and <a shape="rect" href="http://maven.apache.org/download.html">install Maven</a>.</li><li>Get the latest <link><page ri:content-title="Source"></page></link></li><li>JDK (1.6 for version <= 5.10, 1.7 for version > 5.10)</li></ul><h2>Using Maven 2 (ActiveMQ 4.1.x and Up)</h2><p>ActiveMQ 4.1.x and up use Maven 2 to Build. We recommend you download and install <a shape="rect" href="http://maven.apache.org/download.html">Maven 2.0.4</a>.</p><structured-macro ac:macro-id="fe89bdbf-e735-4288-8e2a-70788b5be12e" ac:name="note" ac:schema-version="1"><rich-text-body><p>You should set the MAVEN_OPTS environment variable to -Xmx800m. There are portions of the ActiveMQ build that are very memory intensive. Increase the maven memory limit so that the build does not fail for you.</p></rich-text-body></structured-macro><h3>Doing a Quick Build</h3><structured-macro ac:macro-id="97386c09-3915-4735-b982-67ff64289026" ac:name="code" ac:schema-version="1"><plain-text-body>mvn -Dtest=false -DfailIfNoTests=false clean install
+</plain-text-body></structured-macro><h3>Using an IDE</h3><p>If you prefer to use an IDE then you can auto-generate the IDE's project files using maven plugins. e.g.</p><structured-macro ac:macro-id="6a740a84-8959-4edd-b7d3-62fcc971a9e3" ac:name="code" ac:schema-version="1"><plain-text-body>mvn eclipse:eclipse
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="379bb966-063b-42b0-9cc6-adbaa22ea3a3" ac:name="code" ac:schema-version="1"><plain-text-body>mvn idea:idea
+</plain-text-body></structured-macro><structured-macro ac:macro-id="bec970c7-9d56-430f-a4d3-6071f7806eff" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Importing into Eclipse</parameter><rich-text-body><p>If you have not already done so, you will need to make Eclipse aware of the Maven repository so that it can build everything. In the preferences, go to Java->Build Path->Classpath and define a new Classpath Variable named M2_REPO that points to your local Maven repository (i.e., <code>~/.m2/repository</code> on Unix and <code>c:\Documents and Settings\<user>\.m2\repository</code> on Windows).</p></rich-text-body></structured-macro><h3>Other Maven 2 Goals</h3><p>For more details try the <link><page ri:content-title="Examples"></page></link> or <link><page ri:content-title="Benchmark Tests"></page></link><br clear="none"> Please refer to the <a shape="rect" href="http://maven.apache.org/plugins/index.html">plugin reference</a> for more details on using them.</p><h2>Using Maven 1 (ActiveMQ 4.0.x and Down)</h2><p>ActiveMQ 4.0.x and down use Maven 1 to Build. We recommend you download and install <a shape="rect" href="http://maven.apache.org/maven-1.x/start/download.html">Maven 1.0.2</a>.</p><h3>Doing a Quick Build</h3><structured-macro ac:macro-id="4d8fe143-c9c1-416f-b21f-3c0a2129f4b7" ac:name="code" ac:schema-version="1"><plain-text-body>maven -Dmaven.test.skip.exec=true
+</plain-text-body></structured-macro><h3>Using an IDE</h3><p>If you prefer to use an IDE then you can autogenerate the IDE's project files using maven plugins. e.g.</p><structured-macro ac:macro-id="7949995d-1204-4b55-b057-187381772c30" ac:name="code" ac:schema-version="1"><plain-text-body>maven eclipse
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="33270868-4ce7-4dba-ab5c-2fa84338c4f5" ac:name="code" ac:schema-version="1"><plain-text-body>maven idea
+</plain-text-body></structured-macro><p>etc.</p><h3>Other Maven 1 Goals</h3><p>For more details try the <link><page ri:content-title="Examples"></page></link> or <link><page ri:content-title="Benchmark Tests"></page></link><br clear="none"> Please refer to the <a shape="rect" href="http://maven.apache.org/maven-1.x/plugins/bundled/">plugin reference</a> for more details on using them.</p></div>
diff --git a/c-integration-scenarios.xml b/c-integration-scenarios.xml
index f73d187..898574d 100644
--- a/c-integration-scenarios.xml
+++ b/c-integration-scenarios.xml
@@ -1,11 +1,11 @@
<div class="wiki-content maincontent">
-<h2 id="Cintegrationscenarios-OnewayandRPCwithCservices">One way and RPC with C services</h2>
+<h2>One way and RPC with C services</h2>
<p>Its common for the C services to be the back end services. The 2 common use cases are</p>
<ul><li>we send a message one-way to a C service</li><li>we send a message to a C-service and wait for the result, then reply back to the originator the result</li></ul>
-<h3 id="Cintegrationscenarios-Makingone-waysreliable">Making one-ways reliable</h3>
+<h3>Making one-ways reliable</h3>
<p>If we assume that the C-service is fairly atomic, it works or it doesn't and does not partially work, then for one-way handling we just need some code to...</p>
@@ -23,7 +23,7 @@
<p>Another approach could be for the C service to say whether or not it has successfully processed the message before. This just pushes the problem inside the C code requiring that it persists when things are invoked and when things complete so that it can know when duplicate messages are delivered.</p>
-<h3 id="Cintegrationscenarios-makingRPCreliable">making RPC reliable</h3>
+<h3>making RPC reliable</h3>
<p>This scenario is as above but rather than just acknowledge the inbound message we wish to send a reply and acknowledge the inbound message. So this could be regarded as a small JMS transaction.</p>
@@ -32,7 +32,7 @@
<p>Again if the C service is capable of knowing if it has seen the message before then we can avoiid step 3.</p>
-<h3 id="Cintegrationscenarios-connectivitytoC">connectivity to C</h3>
+<h3>connectivity to C</h3>
<p>We can link C into a Java process and invoke it directly via JNI. Another option is to wrap the C code as an Apache module and perform a HTTP POST to invoke a C service and extract the results of the service.</p></div>
diff --git a/c-integration.xml b/c-integration.xml
index 372a018..1d83404 100644
--- a/c-integration.xml
+++ b/c-integration.xml
@@ -1,10 +1,11 @@
<div class="wiki-content maincontent"><p>It is very common for an organisation to have lots of legacy C code which needs integration into the message bus. The current available solutions are</p>
-<ul><li><a shape="rect" class="unresolved" href="#">CMS</a> is an easy-to-use JMS 1.1-like API for C++. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.</li><li>use the <a shape="rect" href="openwire-c-client.xml">OpenWire C Client</a> which is only available in ActiveMQ 4.x or later.</li><li>we are working on the <a shape="rect" href="openwire-cpp-client.xml">OpenWire CPP Client</a></li></ul>
+<ul><li><link><page ri:content-title="CMS"></page></link> is an easy-to-use JMS 1.1-like API for C++. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.</li><li>use the <link><page ri:content-title="OpenWire C Client"></page></link> which is only available in ActiveMQ 4.x or later.</li><li>we are working on the <link><page ri:content-title="OpenWire CPP Client"></page></link></li></ul>
-<ul><li>use the <a shape="rect" class="external-link" href="http://stomp.codehaus.org/C" rel="nofollow">Stomp C Client</a> for any version of ActiveMQ from 3.1 onwards. You can also use <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> from many other languages like .Net, Python, Ruby, Perl etc.</li></ul>
+<ul><li>use the <a shape="rect" href="http://stomp.codehaus.org/C">Stomp C Client</a> for any version of ActiveMQ from 3.1 onwards. You can also use <a shape="rect" href="http://stomp.codehaus.org/">Stomp</a> from many other languages like .Net, Python, Ruby, Perl etc.</li></ul>
<p>Other alternative mechanisms to communicate using.</p>
-<ul><li>use the <a shape="rect" href="rest.xml">REST</a> API</li><li>use <a shape="rect" class="external-link" href="http://servicemix.org/WS+Notification" rel="nofollow">WS-Notification</a> and generate C bindings to WS-Notification using a SOAP stack</li><li>use <a shape="rect" href="how-do-i-access-activemq-from-csharp-or-dotnet.xml">.Net or Mono</a> to use ActiveMQ insided .Net</li><li><a shape="rect" href="compile-activemq-with-gcj.xml">Compile ActiveMQ with GCJ</a> to get a native C/C++ library</li><li>link to the ActiveMQ Java client using JNI</li><li>Use a Jabber client to talk to the ActiveMQ broker via the <a shape="rect" href="xmpp.xml">XMPP</a> protocol</li></ul></div>
+<ul><li>use the <link><page ri:content-title="REST"></page></link> API</li><li>use <a shape="rect" href="http://servicemix.org/WS+Notification">WS-Notification</a> and generate C bindings to WS-Notification using a SOAP stack</li><li>use <link><page ri:content-title="How do I access ActiveMQ from CSharp or dotNet"></page><link-body>.Net or Mono</link-body></link> to use ActiveMQ insided .Net</li><li><link><page ri:content-title="Compile ActiveMQ with GCJ"></page></link> to get a native C/C++ library</li><li>link to the ActiveMQ Java client using JNI</li><li>Use a Jabber client to talk to the ActiveMQ broker via the <link><page ri:content-title="xmpp"></page><link-body>XMPP</link-body></link> protocol</li></ul>
+</div>
diff --git a/cache/main.pageCache b/cache/main.pageCache
index 300292a..826056c 100644
--- a/cache/main.pageCache
+++ b/cache/main.pageCache
Binary files differ
diff --git a/cache/nms.pageCache b/cache/nms.pageCache
index 477bacd..41cc4c1 100644
--- a/cache/nms.pageCache
+++ b/cache/nms.pageCache
Binary files differ
diff --git a/cached-ldap-authorization-module.xml b/cached-ldap-authorization-module.xml
index 5c60b0a..b7c5e3e 100644
--- a/cached-ldap-authorization-module.xml
+++ b/cached-ldap-authorization-module.xml
@@ -1,33 +1,25 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Available since 5.6</p></div></div><p>Cached LDAP authorization module is an implementation of an default authorization module that initializes and updates data from LDAP. It supports all standard features like defining wildcard policy entries and entry for temporary destinations.</p><h2 id="CachedLDAPAuthorizationModule-Initializing">Initializing</h2><p>We provide two ldif files for easy starting. The first one is for <a shape="rect" class="external-link" href="http://directory.apache.org/">Apache Directory Server</a> (<a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/activemq-apacheds.ldif">ldif</a>), which we use in embedded mode for testing. For an example on how to initialize the embedded ApacheDS with this ldif file take a look at <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/security/CachedLDAPSecurityTest.java">CachedLDAPSecurityTest</a></p><p>The other one is for <a shape="rect" class="external-link" href="http://www.openldap.org/" rel="nofollow">OpenLDAP</a> (<a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/activemq-openldap.ldif">ldif</a>)</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The provided ldif and examples assume <code>dc=activemq,dc=apache,dc=org</code> suffix to be used for entries, so the configuration similar to the one shown in the following snippet</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[suffix "dc=activemq,dc=apache,dc=org"
-rootdn "cn=admin,dc=activemq,dc=apache,dc=org"
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="428fbf5e-bb76-474f-9ebf-7d962d8b39f9" ac:name="info" ac:schema-version="1"><parameter ac:name="">Availability</parameter><rich-text-body><p>Available since 5.6</p></rich-text-body></structured-macro><p>Cached LDAP authorization module is an implementation of an default authorization module that initializes and updates data from LDAP. It supports all standard features like defining wildcard policy entries and entry for temporary destinations.</p><h2>Initializing</h2><p>We provide two ldif files for easy starting. The first one is for <a shape="rect" href="http://directory.apache.org/">Apache Directory Server</a> (<a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/activemq-apacheds.ldif">ldif</a>), which we use in embedded mode for testing. For an example on how to initialize the embedded ApacheDS with this ldif file take a look at <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/security/CachedLDAPSecurityTest.java">CachedLDAPSecurityTest</a></p><p>The other one is for <a shape="rect" href="http://www.openldap.org/">OpenLDAP</a> (<a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/activemq-openldap.ldif">ldif</a>)</p><structured-macro ac:macro-id="1bb9490d-a48f-437d-a0b4-864149b309f8" ac:name="info" ac:schema-version="1"><parameter ac:name=""> Configuring OpenLDAP</parameter><rich-text-body><p>The provided ldif and examples assume <code>dc=activemq,dc=apache,dc=org</code> suffix to be used for entries, so the configuration similar to the one shown in the following snippet</p><structured-macro ac:macro-id="3c8fa317-f914-445c-ae79-cf54e77d755e" ac:name="code" ac:schema-version="1"><plain-text-body>suffix "dc=activemq,dc=apache,dc=org"
+rootdn "cn=admin,dc=activemq,dc=apache,dc=org"
# Cleartext passwords, especially for the rootdn, should
# be avoid. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw {SSHA}lfAYn54xCFghgQv5B2Kqn3d3eLojqxtS
-]]></script>
-</div></div><p>should be put into your <code>slapd.conf</code></p></div></div><p>To initialize your (properly configured) OpenLDAP do something like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ldapadd -x -D "cn=admin,dc=activemq,dc=apache,dc=org" -w sunflower -f activemq-openldap.ldif]]></script>
-</div></div><h2 id="CachedLDAPAuthorizationModule-Configuring">Configuring</h2><p>Once entries are in LDAP, you can configure the module to load entries from there. A default values are adapted for embedded Apache DS server, so all you have to do in that case is add your plugin to the broker xml conf</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<authorizationPlugin>
+</plain-text-body></structured-macro><p>should be put into your <code>slapd.conf</code></p></rich-text-body></structured-macro><p>To initialize your (properly configured) OpenLDAP do something like</p><structured-macro ac:macro-id="c4fef04d-25ba-4e17-82a3-03b478d81086" ac:name="code" ac:schema-version="1"><plain-text-body>ldapadd -x -D "cn=admin,dc=activemq,dc=apache,dc=org" -w sunflower -f activemq-openldap.ldif</plain-text-body></structured-macro><h2>Configuring</h2><p>Once entries are in LDAP, you can configure the module to load entries from there. A default values are adapted for embedded Apache DS server, so all you have to do in that case is add your plugin to the broker xml conf</p><structured-macro ac:macro-id="13b9c7ce-4de5-4687-8bc0-4f99739c7add" ac:name="code" ac:schema-version="1"><plain-text-body><authorizationPlugin>
<map>
<cachedLDAPAuthorizationMap/>
</map>
-</authorizationPlugin>]]></script>
-</div></div><p>For the OpenLDAP case, you should define more parameters</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<authorizationPlugin>
+</authorizationPlugin></plain-text-body></structured-macro><p>For the OpenLDAP case, you should define more parameters</p><structured-macro ac:macro-id="569c3055-be0d-40f9-bcbd-fc7d0e0cf39e" ac:name="code" ac:schema-version="1"><plain-text-body><authorizationPlugin>
<map>
<cachedLDAPAuthorizationMap
- connectionURL="ldap://localhost:389"
- connectionUsername="cn=admin,dc=activemq,dc=apache,dc=org"
- connectionPassword="sunflower"
- queueSearchBase="ou=Queue,ou=Destination,ou=ActiveMQ,dc=activemq,dc=apache,dc=org"
- topicSearchBase="ou=Topic,ou=Destination,ou=ActiveMQ,dc=activemq,dc=apache,dc=org"
- tempSearchBase="ou=Temp,ou=Destination,ou=ActiveMQ,dc=activemq,dc=apache,dc=org"
- refreshInterval="300000"
- legacyGroupMapping="false"
+ connectionURL="ldap://localhost:389"
+ connectionUsername="cn=admin,dc=activemq,dc=apache,dc=org"
+ connectionPassword="sunflower"
+ queueSearchBase="ou=Queue,ou=Destination,ou=ActiveMQ,dc=activemq,dc=apache,dc=org"
+ topicSearchBase="ou=Topic,ou=Destination,ou=ActiveMQ,dc=activemq,dc=apache,dc=org"
+ tempSearchBase="ou=Temp,ou=Destination,ou=ActiveMQ,dc=activemq,dc=apache,dc=org"
+ refreshInterval="300000"
+ legacyGroupMapping="false"
/>
</map>
-</authorizationPlugin>]]></script>
-</div></div><p>Full examples of configurations for <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/activemq-apacheds.xml">Apache DS</a> and <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/activemq-openldap.xml">OpenLDAP</a></p><p>The list of all properties for <code>cachedLDAPAuthorizationMap</code></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property</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><td colspan="1" rowspan="1" class="confluenceTd"><p>version</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectionURL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ldap://localhost:1024</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>LDAP Server connection address</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectionUsername</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>uid=admin,ou=system</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Dn to be used for connecting to the server</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectionPassword</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>secret</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Password to be used for connecting to the server</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectionProtocol</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>s</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Connection protocol to be used for connecting to the server</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>authentication</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>simple</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Authentication method to be used when connecting to the server</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>queueSearchBase</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ou=Queue,ou=Destination,ou=ActiveMQ,ou=system</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Base dn of queue related entries</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5.7 and later</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>topicSearchBase</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ou=Topic,ou=Destination,ou=ActiveMQ,ou=system</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Base dn of topic related entries</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5.7 and later</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>tempSearchBase</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ou=Temp,ou=Destination,ou=ActiveMQ,ou=system</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Base dn of temporary destinations related entries</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5.7 and later</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>refreshInterval</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Interval (in milliseconds) of pulling changes from the server, -1 means pulling is off, see #Updates for more info</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>legacyGroupMapping</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should permission group members be configured as CN and not a full DN</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5.7 and later</p></td></tr></tbody></table></div><h2 id="CachedLDAPAuthorizationModule-Updates">Updates</h2><p>Many LDAP servers supports so called "persistent search" feature which allows applications to receive changes in LDAP in a "push" manner. By default this plugin assumes that LDAP server supports this feature and will "register" to get live updates.</p><p>For servers that doesn't support this yet (like OpenLDAP), we provide "pull" updates. In this case you need to set <code>refreshInterval</code> property, which will define the update period for the plugin (so in this case, updates will not be immediately applied)</p></div>
+</authorizationPlugin></plain-text-body></structured-macro><p>Full examples of configurations for <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/activemq-apacheds.xml">Apache DS</a> and <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/activemq-openldap.xml">OpenLDAP</a></p><p>The list of all properties for <code>cachedLDAPAuthorizationMap</code></p><table><tbody><tr><th colspan="1" rowspan="1"><p>property</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>description</p></th><td colspan="1" rowspan="1"><p>version</p></td></tr><tr><td colspan="1" rowspan="1"><p>connectionURL</p></td><td colspan="1" rowspan="1"><p>ldap://localhost:1024</p></td><td colspan="1" rowspan="1"><p>LDAP Server connection address</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>connectionUsername</p></td><td colspan="1" rowspan="1"><p>uid=admin,ou=system</p></td><td colspan="1" rowspan="1"><p>Dn to be used for connecting to the server</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>connectionPassword</p></td><td colspan="1" rowspan="1"><p>secret</p></td><td colspan="1" rowspan="1"><p>Password to be used for connecting to the server</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>connectionProtocol</p></td><td colspan="1" rowspan="1"><p>s</p></td><td colspan="1" rowspan="1"><p>Connection protocol to be used for connecting to the server</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>authentication</p></td><td colspan="1" rowspan="1"><p>simple</p></td><td colspan="1" rowspan="1"><p>Authentication method to be used when connecting to the server</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>queueSearchBase</p></td><td colspan="1" rowspan="1"><p>ou=Queue,ou=Destination,ou=ActiveMQ,ou=system</p></td><td colspan="1" rowspan="1"><p>Base dn of queue related entries</p></td><td colspan="1" rowspan="1"><p>5.7 and later</p></td></tr><tr><td colspan="1" rowspan="1"><p>topicSearchBase</p></td><td colspan="1" rowspan="1"><p>ou=Topic,ou=Destination,ou=ActiveMQ,ou=system</p></td><td colspan="1" rowspan="1"><p>Base dn of topic related entries</p></td><td colspan="1" rowspan="1"><p>5.7 and later</p></td></tr><tr><td colspan="1" rowspan="1"><p>tempSearchBase</p></td><td colspan="1" rowspan="1"><p>ou=Temp,ou=Destination,ou=ActiveMQ,ou=system</p></td><td colspan="1" rowspan="1"><p>Base dn of temporary destinations related entries</p></td><td colspan="1" rowspan="1"><p>5.7 and later</p></td></tr><tr><td colspan="1" rowspan="1"><p>refreshInterval</p></td><td colspan="1" rowspan="1"><p>-1</p></td><td colspan="1" rowspan="1"><p>Interval (in milliseconds) of pulling changes from the server, -1 means pulling is off, see #Updates for more info</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>legacyGroupMapping</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should permission group members be configured as CN and not a full DN</p></td><td colspan="1" rowspan="1"><p>5.7 and later</p></td></tr></tbody></table><h2>Updates</h2><p>Many LDAP servers supports so called "persistent search" feature which allows applications to receive changes in LDAP in a "push" manner. By default this plugin assumes that LDAP server supports this feature and will "register" to get live updates.</p><p>For servers that doesn't support this yet (like OpenLDAP), we provide "pull" updates. In this case you need to set <code>refreshInterval</code> property, which will define the update period for the plugin (so in this case, updates will not be immediately applied)</p></div>
diff --git a/can-i-get-commercial-support.xml b/can-i-get-commercial-support.xml
index 6faeb61..2eda5e6 100644
--- a/can-i-get-commercial-support.xml
+++ b/can-i-get-commercial-support.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="CanIgetcommercialsupport-CanIgetcommercialsupport?">Can I get commercial support? </h2>
+<div class="wiki-content maincontent"><h2>Can I get commercial support? </h2>
-<p>Absolutely, see our <a shape="rect" href="support.xml">Support</a> page for more details</p></div>
+<p>Absolutely, see our <link><page ri:content-title="Support"></page></link> page for more details</p></div>
diff --git a/can-i-modify-messages-on-a-queue.xml b/can-i-modify-messages-on-a-queue.xml
index 186d6ea..d956225 100644
--- a/can-i-modify-messages-on-a-queue.xml
+++ b/can-i-modify-messages-on-a-queue.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="CanImodifymessagesonaqueue-CanImodifymessagesonaqueue?">Can I modify messages on a queue?</h2>
+<div class="wiki-content maincontent"><h2>Can I modify messages on a queue?</h2>
<p>The short answer is no. In JMS messages are immutable once they have been sent. If you find you need to modify messages its recommended that you create a consumer with some selector which matches the messages you wish to update, consume them and send new modified messages, either to another queue or if you are careful, back to the original queue. (If you are using the same queue, be careful not to get into a loop where your selector matches messages you are sending yourself - you may wish to use some JMS header to avoid this loop).</p></div>
diff --git a/can-i-send-and-receive-messages-concurrently-on-one-jms-connection.xml b/can-i-send-and-receive-messages-concurrently-on-one-jms-connection.xml
index efd4cb9..5e4a60f 100644
--- a/can-i-send-and-receive-messages-concurrently-on-one-jms-connection.xml
+++ b/can-i-send-and-receive-messages-concurrently-on-one-jms-connection.xml
@@ -4,5 +4,5 @@
<p>For concurrent consumption create a session per consumer - as all messages are dispatched to a session in a single thread - but you can have as many sessions as you like per connection.</p>
-<p>To further help with concurrent consuming of JMS you can use <a shape="rect" class="external-link" href="http://jencks.codehaus.org/Message+Driven+POJOs" rel="nofollow">Message Driven POJOs</a></p></div>
+<p>To further help with concurrent consuming of JMS you can use <a shape="rect" href="http://jencks.codehaus.org/Message+Driven+POJOs">Message Driven POJOs</a></p></div>
diff --git a/can-i-send-really-large-files-over-activemq.xml b/can-i-send-really-large-files-over-activemq.xml
index d0f397d..9c4df4d 100644
--- a/can-i-send-really-large-files-over-activemq.xml
+++ b/can-i-send-really-large-files-over-activemq.xml
@@ -1,10 +1,11 @@
-<div class="wiki-content maincontent"><h2 id="CanIsendreallylargefilesoverActiveMQ-CanIsendreallylargefilesoverActiveMQ">Can I send really large files over ActiveMQ</h2>
+<div class="wiki-content maincontent"><h2>Can I send really large files over ActiveMQ</h2>
<p>The answer is yes. </p>
-<p>If you are using ActiveMQ 4.2 or later we highly recommend you use <a shape="rect" href="blob-messages.xml">Blob Messages</a> which implements an out of band transport of the messages; it allows the files to be hosted on external http/ftp sites if required and can support either direct publisher <-> subscriber communication or publisher -> broker/file server -> consumer messaging.</p>
+<p>If you are using ActiveMQ 4.2 or later we highly recommend you use <link><page ri:content-title="Blob Messages"></page></link> which implements an out of band transport of the messages; it allows the files to be hosted on external http/ftp sites if required and can support either direct publisher <-> subscriber communication or publisher -> broker/file server -> consumer messaging.</p>
-<p>For 4.1 or ealier large file transfer is achieved using <a shape="rect" href="jms-streams.xml">JMS Streams</a>. </p>
+<p>For 4.1 or ealier large file transfer is achieved using <link><page ri:content-title="JMS Streams"></page></link>. </p>
-<p>Normally the JMS API expects the entire JMS messsage to reside in the client side memory; however using <a shape="rect" href="blob-messages.xml">Blob Messages</a> or <a shape="rect" href="jms-streams.xml">JMS Streams</a> allows you to send and receive arbitrarily large files with very low RAM overhead.</p></div>
+<p>Normally the JMS API expects the entire JMS messsage to reside in the client side memory; however using <link><page ri:content-title="Blob Messages"></page></link> or <link><page ri:content-title="JMS Streams"></page></link> allows you to send and receive arbitrarily large files with very low RAM overhead.</p>
+</div>
diff --git a/can-i-use-activemq-5x-or-later-on-java-14.xml b/can-i-use-activemq-5x-or-later-on-java-14.xml
index 2bc086c..e991763 100644
--- a/can-i-use-activemq-5x-or-later-on-java-14.xml
+++ b/can-i-use-activemq-5x-or-later-on-java-14.xml
@@ -1,12 +1,13 @@
-<div class="wiki-content maincontent"><h2 id="CanIuseActiveMQ5.xorlateronJava1.4-CanIuseActiveMQ5.0orlateronJava1.4?">Can I use ActiveMQ 5.0 or later on Java 1.4?</h2>
+<div class="wiki-content maincontent"><h2>Can I use ActiveMQ 5.0 or later on Java 1.4?</h2>
<p>Apache ActiveMQ 5.x or later is developed to run on Java 5 or later to take advantage of the new language features together with the major fact that on Java 5 the new concurrency code is faster & less buggy and requires less dependencies.</p>
-<p>We may get around to creating a sepate distro of retrotranslated jars for 1.4 <a shape="rect" href="contributing.xml">particularly if someone helps</a>.</p>
+<p>We may get around to creating a sepate distro of retrotranslated jars for 1.4 <link><page ri:content-title="Contributing"></page><link-body>particularly if someone helps</link-body></link>.</p>
-<p>Until then you can just <a shape="rect" class="external-link" href="http://retrotranslator.sourceforge.net/#jit" rel="nofollow">install the retrotranslator JIT in your JVM</a> which will auto-swizzle all Java 5 bytecode to be complaint Java 1.4 bytecode using backport-util-concurrent instead of Java 5 concurrency code.</p>
+<p>Until then you can just <a shape="rect" href="http://retrotranslator.sourceforge.net/#jit">install the retrotranslator JIT in your JVM</a> which will auto-swizzle all Java 5 bytecode to be complaint Java 1.4 bytecode using backport-util-concurrent instead of Java 5 concurrency code.</p>
-<h2 id="CanIuseActiveMQ5.xorlateronJava1.4-SeeAlso">See Also</h2>
+<h2>See Also</h2>
-<ul><li><a shape="rect" href="what-platforms-does-activemq-support.xml">What platforms does ActiveMQ support</a></li></ul></div>
+<ul><li><link><page ri:content-title="What platforms does ActiveMQ support"></page></link></li></ul>
+</div>
diff --git a/can-two-brokers-share-the-same-database.xml b/can-two-brokers-share-the-same-database.xml
index 7b0c5ce..2f1da10 100644
--- a/can-two-brokers-share-the-same-database.xml
+++ b/can-two-brokers-share-the-same-database.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><h2 id="Cantwobrokerssharethesamedatabase-Cantwobrokerssharethesamedatabase">Can two brokers share the same database</h2>
+<div class="wiki-content maincontent"><h2>Can two brokers share the same database</h2>
<p>The short answer is no; 2 brokers cannot operate on the same sets of database tables concurrently. ActiveMQ is designed for high performance so we want to minimise the amount of pessimistic locking; each broker is designed to work with its own persistent database.</p>
<p>If you want to share the same physical database server across two brokers to simplify your installation & backup procedures then just create 2 different logins for each broker so that they get their own sets of database tables within the same physical database. (i.e. each broker gets its own logical database within the same physical database server).</p>
-<p>Also if you want to only have one database but many possible brokers (for HA) then just use <a shape="rect" href="jdbc-master-slave.xml">JDBC Master Slave</a></p></div>
+<p>Also if you want to only have one database but many possible brokers (for HA) then just use <link><page ri:content-title="JDBC Master Slave"></page></link></p></div>
diff --git a/can-you-browse-a-topic.xml b/can-you-browse-a-topic.xml
index 20fcf62..cbae1c0 100644
--- a/can-you-browse-a-topic.xml
+++ b/can-you-browse-a-topic.xml
@@ -4,5 +4,5 @@
<p>i.e. browsing is necessary on queues as you wanna see what messages there are without removing them. For topics, everyone who's interested gets a copy of the message so just do a regular subscribe.</p>
-<p>One nice to have feature would be to expose durable subscriptions as a logical queue, so you could browse outstanding messages on a durable subscription as if it were a queue (see <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ-25">AMQ-25</a> to track this feature request)but its not in any way standard JMS.</p></div>
+<p>One nice to have feature would be to expose durable subscriptions as a logical queue, so you could browse outstanding messages on a durable subscription as if it were a queue (see <a shape="rect" href="https://issues.apache.org/activemq/browse/AMQ-25">AMQ-25</a> to track this feature request)but its not in any way standard JMS.</p></div>
diff --git a/certificateunknown.xml b/certificateunknown.xml
index f05f240..b3184a3 100644
--- a/certificateunknown.xml
+++ b/certificateunknown.xml
@@ -1,7 +1,6 @@
<div class="wiki-content maincontent"><p>If you get an error something like this...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0708482b-8175-421f-9fe9-85a126b5b52c" ac:name="code" ac:schema-version="1"><plain-text-body>
javax.jms.JMSException: start failed: Received fatal alert: certificate_unknown
at org.activemq.transport.tcp.TcpTransportChannel.start(TcpTransportChannel.java:200)
at org.activemq.broker.impl.BrokerConnectorImpl.addClient(BrokerConnectorImpl.java:308)
@@ -17,12 +16,11 @@
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>when you are trying to use SSL to connect to ActiveMQ then the "certificate_unknown" error shows on the broker when the client doesn't trust the broker's certificate. On the client, I would see an error as well: "No trusted certificate found". </p>
-<h3 id="certificate_unknown-Fix">Fix</h3>
+<h3>Fix</h3>
-<p>Make sure that you exported the broker's certificate (step 2 in <a shape="rect" href="how-do-i-use-ssl.xml">How do I use SSL</a>) and imported it on the client into a truststore (step 4). If you did those, did you specify the javax.net.ssl.trustStore system property when you started your client VM? </p></div>
+<p>Make sure that you exported the broker's certificate (step 2 in <link><page ri:content-title="How do I use SSL"></page></link>) and imported it on the client into a truststore (step 4). If you did those, did you specify the javax.net.ssl.trustStore system property when you started your client VM? </p></div>
diff --git a/changes-in-40.xml b/changes-in-40.xml
index f71100c..25afee2 100644
--- a/changes-in-40.xml
+++ b/changes-in-40.xml
@@ -1,24 +1,23 @@
-<div class="wiki-content maincontent"><h3 id="Changesin4.0-NewFeaturesin4.0">New Features in 4.0</h3>
+<div class="wiki-content maincontent"><h3>New Features in 4.0</h3>
-<ul><li><a shape="rect" href="masterslave.xml">MasterSlave</a> provides support for continuous availability and fault tolerance of brokers to be able to handle catastrophic hardware failure and not loose a message (or get duplicates).</li><li>A new <a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a> feature allows you to pin message processing to a single consumer in a cluser of consumers.</li><li>A new <a shape="rect" href="message-groups.xml">Message Groups</a> feaure allows you load balance messages accross a set of consumers but also garantee the message order for messages within a message group.</li><li>A new <a shape="rect" href="total-ordering.xml">Total Ordering</a> feature to allow all consumers on a topic to see messages in the same order.</li><li>New <a shape="rect" href="how-can-i-monitor-activemq.xml">JMX Management</a> and monitoring capabilities. You can now see statistics for each broker, destination, connector and connection!</li><li>Improved <a shape="rect" href="security.xml">Security</a> plugin which provides JAAS support for authentication along with a pluggable strategy for authorization together with a default XML based implementation.</li><li>A new <a shape="rect" href="openwire-c-client.xml">OpenWire C Client</a> is now available. This client talks the same wire protocol that the standard java client uses so every messaging broker feature available to the java client is available to the c client.</li><li>An experimental <a shape="rect" href="nms/index.html">OpenWire dotNet</a> is available, written in pure C# along with a JMS-like API for working on the .Net platform with ActiveMQ</li><li>Queues can now be loaded up with persistent messages without locking up the broker. Persistent messages are now swapped out of memory when no consumer needs it soon.</li><li>A new <a shape="rect" href="consumer-priority.xml">Consumer Priority</a> feature allows you to build location affinity by assignin a priority to consumers. The broker can then dispatch messages to higher priority consumers before dispatching to lower priority consumers.</li><li>A configurable per <a shape="rect" href="consumer-dispatch-async.xml">Consumer Dispatch Async</a> flag which allows you to configure how messages are sent by the broker to a consumer. This controls if the broker uses <a shape="rect" href="seda.xml">SEDA</a> or <a shape="rect" class="unresolved" href="#">STP</a> style dispaching.</li><li>A new plug-able topic <a shape="rect" href="subscription-recovery-policy.xml">Subscription Recovery Policy</a> which allows you to configure how many transient messages are replayed when a <a shape="rect" href="retroactive-consumer.xml">Retroactive Consumer</a> is created.</li><li>A new <a shape="rect" href="retroactive-consumer.xml">Retroactive Consumer</a> feature allows topic consumers to "go back in time" so that it receives old messages when the subscription is activated. If the consumer is a durable consumer, he recover all the messages that are still in the persistent store.</li><li><a shape="rect" href="per-destination-policies.xml">Per Destination Policies</a> allow you configure the behavior of destinations.</li><li>The broker now supports per destination plugable <a shape="rect" href="dispatch-policies.xml">Dispatch Policies</a> so that you can choose the distribution algorithm used to send messages to a consumer.</li><li>The broker now supports two new types of connectors:
- <ul><li><a shape="rect" href="the-jms-connector.xml">The JMS Connector</a> is used to establish connection to external JMS providers so that messages can be bridged between the system.</li><li><a shape="rect" href="the-proxy-connector.xml">The Proxy Connector</a>. Is used to proxy connections to another broker.</li></ul>
- </li><li><a shape="rect" href="slow-consumer-handling.xml">Slow Consumer Handling</a> allows you to discard old messages for slow consumers on non-durable topics to avoid slowing down fast consumers</li><li>You can now specify <a shape="rect" href="destination-options.xml">Destination Options</a> that allow you to do extend configuration of consumers.</li><li>Conumsers now use <a shape="rect" href="optimized-acknowledgement.xml">Optimized Acknowledgement</a> by default to which results in increased performance.</li></ul>
+<ul><li><link><page ri:content-title="MasterSlave"></page></link> provides support for continuous availability and fault tolerance of brokers to be able to handle catastrophic hardware failure and not loose a message (or get duplicates).</li><li>A new <link><page ri:content-title="Exclusive Consumer"></page></link> feature allows you to pin message processing to a single consumer in a cluser of consumers.</li><li>A new <link><page ri:content-title="Message Groups"></page></link> feaure allows you load balance messages accross a set of consumers but also garantee the message order for messages within a message group.</li><li>A new <link><page ri:content-title="Total Ordering"></page></link> feature to allow all consumers on a topic to see messages in the same order.</li><li>New <link><page ri:content-title="How can I monitor ActiveMQ"></page><link-body>JMX Management</link-body></link> and monitoring capabilities. You can now see statistics for each broker, destination, connector and connection!</li><li>Improved <link><page ri:content-title="Security"></page></link> plugin which provides JAAS support for authentication along with a pluggable strategy for authorization together with a default XML based implementation.</li><li>A new <link><page ri:content-title="OpenWire C Client"></page></link> is now available. This client talks the same wire protocol that the standard java client uses so every messaging broker feature available to the java client is available to the c client.</li><li>An experimental <link><space ri:space-key="NMS"></space><link-body>OpenWire dotNet</link-body></link> is available, written in pure C# along with a JMS-like API for working on the .Net platform with ActiveMQ</li><li>Queues can now be loaded up with persistent messages without locking up the broker. Persistent messages are now swapped out of memory when no consumer needs it soon.</li><li>A new <link><page ri:content-title="Consumer Priority"></page></link> feature allows you to build location affinity by assignin a priority to consumers. The broker can then dispatch messages to higher priority consumers before dispatching to lower priority consumers.</li><li>A configurable per <link><page ri:content-title="Consumer Dispatch Async"></page></link> flag which allows you to configure how messages are sent by the broker to a consumer. This controls if the broker uses <link><page ri:content-title="SEDA"></page></link> or <link><page ri:content-title="STP"></page></link> style dispaching.</li><li>A new plug-able topic <link><page ri:content-title="Subscription Recovery Policy"></page></link> which allows you to configure how many transient messages are replayed when a <link><page ri:content-title="Retroactive Consumer"></page></link> is created.</li><li>A new <link><page ri:content-title="Retroactive Consumer"></page></link> feature allows topic consumers to "go back in time" so that it receives old messages when the subscription is activated. If the consumer is a durable consumer, he recover all the messages that are still in the persistent store.</li><li><link><page ri:content-title="Per Destination Policies"></page></link> allow you configure the behavior of destinations.</li><li>The broker now supports per destination plugable <link><page ri:content-title="Dispatch Policies"></page></link> so that you can choose the distribution algorithm used to send messages to a consumer.</li><li>The broker now supports two new types of connectors:
+ <ul><li><link><page ri:content-title="The JMS Connector"></page></link> is used to establish connection to external JMS providers so that messages can be bridged between the system.</li><li><link><page ri:content-title="The Proxy Connector"></page></link>. Is used to proxy connections to another broker.</li></ul>
+ </li><li><link><page ri:content-title="Slow Consumer Handling"></page></link> allows you to discard old messages for slow consumers on non-durable topics to avoid slowing down fast consumers</li><li>You can now specify <link><page ri:content-title="Destination Options"></page></link> that allow you to do extend configuration of consumers.</li><li>Conumsers now use <link><page ri:content-title="Optimized Acknowledgement"></page></link> by default to which results in increased performance.</li></ul>
-<h3 id="Changesin4.0-API/Configurationchanages">API/Configuration chanages</h3>
+<h3>API/Configuration chanages</h3>
-<ul><li>as part of the move to Apache, the package name is now <strong>org.apache.activemq</strong> and not <strong>org.activemq</strong>.</li><li>the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> has changed a little; mostly its now in the ActiveMQ namespace and has a generated XSD and documentation.</li><li>the <em>reliable</em> transport has been renamed to <em>failover</em> to make it more clear what it does; we're working on a separate DR mechanism to provide data centre resilliance. So if you wish to connect to one of a number of URIs try
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<ul><li>as part of the move to Apache, the package name is now <strong>org.apache.activemq</strong> and not <strong>org.activemq</strong>.</li><li>the <link><page ri:content-title="Xml Configuration"></page></link> has changed a little; mostly its now in the ActiveMQ namespace and has a generated XSD and documentation.</li><li>the <em>reliable</em> transport has been renamed to <em>failover</em> to make it more clear what it does; we're working on a separate DR mechanism to provide data centre resilliance. So if you wish to connect to one of a number of URIs try
+<structured-macro ac:macro-id="67446eff-165c-41df-a0ae-fbb115d9644a" ac:name="code" ac:schema-version="1"><plain-text-body>
failover:tcp://host1:port1,tcp://host2:port2
-]]></script>
-</div></div></li><li>The configuration options of transports have changed. See <a shape="rect" href="activemq-connection-uris.xml">ActiveMQ Connection URIs</a> for a detailed guide of of all the options.</li><li>The spring package has gone; we now use <a shape="rect" class="external-link" href="http://xbean.org" rel="nofollow">XBean</a> to configure ActiveMQ. See the org.activemq.xbean.BrokerFactoryBean if you want a factory bean to use in regular spring instead of the org.activemq.spring.BrokerFactoryBean. See <a shape="rect" href="configuring-brokers.xml">Configuring Brokers</a> for more information on the new XML syntax.</li><li>ActiveMQTopic and ActiveMQQueue are now in the org.activemq.command package.</li><li>If you were creating a broker in Java code, the BrokerContainer has been replaced with BrokerService which is easier to use now.</li><li>The connection URL options have changed slightly to provided more persise configuration options of the transport and wireformat and to allow validation of the options.</li><li><a shape="rect" href="message-redelivery-and-dlq-handling.xml">Message Redelivery and DLQ Handling</a> has been re-implemnted. Currently all messages sent poison messages are sent to a single DQL.</li><li>The <a shape="rect" href="jms-streams.xml">JMS Streams</a> API has changed.</li></ul>
+</plain-text-body></structured-macro></li><li>The configuration options of transports have changed. See <link><page ri:content-title="ActiveMQ Connection URIs"></page></link> for a detailed guide of of all the options.</li><li>The spring package has gone; we now use <a shape="rect" href="http://xbean.org">XBean</a> to configure ActiveMQ. See the org.activemq.xbean.BrokerFactoryBean if you want a factory bean to use in regular spring instead of the org.activemq.spring.BrokerFactoryBean. See <link><page ri:content-title="Configuring Brokers"></page></link> for more information on the new XML syntax.</li><li>ActiveMQTopic and ActiveMQQueue are now in the org.activemq.command package.</li><li>If you were creating a broker in Java code, the BrokerContainer has been replaced with BrokerService which is easier to use now.</li><li>The connection URL options have changed slightly to provided more persise configuration options of the transport and wireformat and to allow validation of the options.</li><li><link><page ri:content-title="Message Redelivery and DLQ Handling"></page></link> has been re-implemnted. Currently all messages sent poison messages are sent to a single DQL.</li><li>The <link><page ri:content-title="JMS Streams"></page></link> API has changed.</li></ul>
-<h3 id="Changesin4.0-GeneralChanges">General Changes</h3>
+<h3>General Changes</h3>
-<ul><li>The JDBC persistence adapter now uses JDBC statement batching to increase it's performance with the database. This should reduce the amount of time a checkpoint takes.</li><li>QueueBrowsers now play nicely with a queue that is currently being consumed from. It gives you a true snapshot of what the queue looked like when you created the browser and it does not affect the dispatching of messages to active consumers.</li><li>we no longer have hand-crafted marshalling code any more; its all based on <a shape="rect" href="openwire.xml">OpenWire</a> and autogenerated from the open wire commands in the org.activemq.command package</li><li>The network bridges used for broker to broker messaging now use a lower level ActiveMQ command and transport API instead of the JMS API, this allows them to use more optimizations and have a lower per bridge resource consumption while letting the JMS client API implementation reduce it's complexity.</li><li>Two types of network bridges are now supported:
+<ul><li>The JDBC persistence adapter now uses JDBC statement batching to increase it's performance with the database. This should reduce the amount of time a checkpoint takes.</li><li>QueueBrowsers now play nicely with a queue that is currently being consumed from. It gives you a true snapshot of what the queue looked like when you created the browser and it does not affect the dispatching of messages to active consumers.</li><li>we no longer have hand-crafted marshalling code any more; its all based on <link><page ri:content-title="OpenWire"></page></link> and autogenerated from the open wire commands in the org.activemq.command package</li><li>The network bridges used for broker to broker messaging now use a lower level ActiveMQ command and transport API instead of the JMS API, this allows them to use more optimizations and have a lower per bridge resource consumption while letting the JMS client API implementation reduce it's complexity.</li><li>Two types of network bridges are now supported:
<ul><li>A simple forwardng bridge - sends all messages as soon as possible to the remote broker. Great you know the usage patterns up front and allways want to do store and forward to a central broker.</li><li>A demand based forwarding bridge (same type of bridge that was using in ActiveMQ 3.x) which detects consumer demand on the remote broker and only forwards messages as needed.</li></ul>
- </li><li>The demand based forwarding bridge now take advantage of the <a shape="rect" href="consumer-priority.xml">Consumer Priority</a> to avoid forwarding messages to a remote broker if there is a local consumer consuming it's messages.</li><li>Message fragmentation is no longer done. Fragmented messages add yet another level of complexity when you introduce broker networks. Large objects/streams should be transfered using the <a shape="rect" href="jms-streams.xml">JMS Streams</a>.</li><li>JMS clients marshall fewer messages on the wire on for a rollback.</li><li>JMS clients marshall fewer messages when sessions/consumers/producers are closed.</li><li>The client and the broker make more extensive use of Thread Pools to avoid allocating idle threads that are not being used.</li></ul></div>
+ </li><li>The demand based forwarding bridge now take advantage of the <link><page ri:content-title="Consumer Priority"></page></link> to avoid forwarding messages to a remote broker if there is a local consumer consuming it's messages.</li><li>Message fragmentation is no longer done. Fragmented messages add yet another level of complexity when you introduce broker networks. Large objects/streams should be transfered using the <link><page ri:content-title="JMS Streams"></page></link>.</li><li>JMS clients marshall fewer messages on the wire on for a rollback.</li><li>JMS clients marshall fewer messages when sessions/consumers/producers are closed.</li><li>The client and the broker make more extensive use of Thread Pools to avoid allocating idle threads that are not being used.</li></ul>
+</div>
diff --git a/class-diagrams-for-activemq-40-m4-source-code.xml b/class-diagrams-for-activemq-40-m4-source-code.xml
index 92cfcc1..2ec20f9 100644
--- a/class-diagrams-for-activemq-40-m4-source-code.xml
+++ b/class-diagrams-for-activemq-40-m4-source-code.xml
@@ -3,11 +3,11 @@
<p>These diagrams cover the bulk of the source code and are in EMF format. </p>
-<p><a shape="rect" class="external-link" href="http://docs.codehaus.org/download/attachments/50288/Class+Diagrams+activemq-4.0-M4.zip" rel="nofollow">http://docs.codehaus.org/download/attachments/50288/Class+Diagrams+activemq-4.0-M4.zip</a></p>
+<p><a shape="rect" href="http://docs.codehaus.org/download/attachments/50288/Class+Diagrams+activemq-4.0-M4.zip">http://docs.codehaus.org/download/attachments/50288/Class+Diagrams+activemq-4.0-M4.zip</a></p>
-<p>Note about conversion to other formats:  Some files when converted to something like JPG or PNG will be quite large.  If your system doesn't have enough RAM you will get an error or in some cases the converting program will just scale to fit which usually will mangle the image.  For the larger file conversions you will need  1GB of RAM.  A free program I came across for converting is IrfanView (<a shape="rect" class="external-link" href="http://www.irfanview.com/" rel="nofollow">http://www.irfanview.com/</a>).  I found it much better than Windows Image Viewer, but you still need an appropriate amount of memory. </p>
+<p>Note about conversion to other formats:  Some files when converted to something like JPG or PNG will be quite large.  If your system doesn't have enough RAM you will get an error or in some cases the converting program will just scale to fit which usually will mangle the image.  For the larger file conversions you will need  1GB of RAM.  A free program I came across for converting is IrfanView (<a shape="rect" href="http://www.irfanview.com/">http://www.irfanview.com/</a>).  I found it much better than Windows Image Viewer, but you still need an appropriate amount of memory. </p>
-<p>Note about printing: Adobe In Design works well for printing if you want a large print but don't have access to an oversized/wide format ink jet (<a shape="rect" class="external-link" href="http://www.adobe.com/products/tryadobe/main.jsp#product=31" rel="nofollow">http://www.adobe.com/products/tryadobe/main.jsp#product=31</a>).  Set up the page dimensions first, for example,  normal letter size page is measured in pts, 51p0 width, 66p0 height.  So for a wider than long oversized diagram you might go to File->Document Setup... and set Page Size to "Custom" and width to 255p0 (5 8 1/2" letter pages in width), and height to 112p0 (2 11" letter pages in height).  Next go to File->Place... to import the EMF. Using the Scale tool (smaller box with an arrow pointing into larger box) size the image to fit inside the page (hold down shift key while sizing to keep proportions), and position it using the Selection tool (arrow).</p>
+<p>Note about printing: Adobe In Design works well for printing if you want a large print but don't have access to an oversized/wide format ink jet (<a shape="rect" href="http://www.adobe.com/products/tryadobe/main.jsp#product=31">http://www.adobe.com/products/tryadobe/main.jsp#product=31</a>).  Set up the page dimensions first, for example,  normal letter size page is measured in pts, 51p0 width, 66p0 height.  So for a wider than long oversized diagram you might go to File->Document Setup... and set Page Size to "Custom" and width to 255p0 (5 8 1/2" letter pages in width), and height to 112p0 (2 11" letter pages in height).  Next go to File->Place... to import the EMF. Using the Scale tool (smaller box with an arrow pointing into larger box) size the image to fit inside the page (hold down shift key while sizing to keep proportions), and position it using the Selection tool (arrow).</p>
<p>Then go to File->Print..., select "Setup" and check the "Tile" option.  The "Tile" dropdown setting should be "Auto" and Overlap 4p0.  Then set the Scale option to a percentage that maximizes the image coverage (there is a visual thumbnail that will indicate the coverage).  Then Print.  This should yield a nice large image printed out in tiled format on letter size pages.  Each page will be properly numbered so you know their positions, and there will be marks for trimming and taping the pages together.  A page cutter is neccessary.  Just trim the right and bottom overlap on each page, then align and tape.</p></div>
diff --git a/clustering.xml b/clustering.xml
index b111792..ea6155d 100644
--- a/clustering.xml
+++ b/clustering.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Clustering is a large topic and often means different things to different people. We'll try to list the various aspects of clustering and how they relate to ActiveMQ</p><h2 id="Clustering-Queueconsumerclusters">Queue consumer clusters</h2><p>ActiveMQ supports reliable high performance load balancing of messages on a queue across consumers. In enterprise integration, this scenario is known as the <a shape="rect" class="external-link" href="http://www.eaipatterns.com/CompetingConsumers.html" rel="nofollow">competing consumers</a> pattern. The following figure illustrates the concept:</p><p><span class="confluence-embedded-file-wrapper image-center-wrapper"><img class="confluence-embedded-image image-center" src="clustering.data/competing-consumers.png" data-image-src="/confluence/download/attachments/35981/competing-consumers.png?version=1&modificationDate=1410121265000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="46301416" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="competing-consumers.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35981" data-linked-resource-container-version="26"></span></p><p><span style="line-height: 1.4285715;">This solution receives the messages sent by the producers, enqueues them and distributes them between all the registered consumers. This has a number of benefits:</span></p><ul><li><span style="line-height: 1.4285715;">The load is distributed in a very dynamic fashion. Additional consumers could be provisioned and attached to the queue in high load periods, without modifying any configuration in the queue, as the new consumer would behave as just another competing consumer.</span></li><li><span style="line-height: 1.4285715;">Better availability than systems using a load balancer. Load balancers usually rely on a monitorization system to find out which real-servers are unavailable. With competing consumers, a failed consumer won't be competing for messages and therefore messages won't be delivered to it even without monitorization.</span></li><li>High reliability, if a consumer fails, any unacknowledged messages are redelivered to other consumers on the queue.</li></ul><p>On the downside, this pattern might not be ideal in systems where the order processing is required. To mitigate this problem while maintaining the benefits, the competing consumers pattern should be used in conjunction with other ActiveMQ <a shape="rect" href="features.xml">features</a> like the <a shape="rect" href="exclusive-consumer.xml">exclusive consumers</a> and the <a shape="rect" href="message-groups.xml">message groups</a> as stated in the <a shape="rect" href="how-do-i-preserve-order-of-messages.xml">ActiveMQ's FAQ</a>.</p><h2 id="Clustering-Brokerclusters">Broker clusters</h2><p>The most common mental model of clustering in a JMS context is that there is a collection of JMS brokers and a JMS client will connect to one of them; then if the JMS broker goes down, it will auto-reconnect to another broker.</p><p>We implement this using the <strong>failover://</strong> protocol in the JMS client. See the <a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a> page for details of how to configure the failover protocol. <em>Note:</em> The reliable:// protocol in ActiveMQ 3.x has now been changed to the failover:// protocol</p><p>If we just run multiple brokers on a network and tell the clients about them using either <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/static-transport-reference.html">static discovery</a> or <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/discovery-transport-reference.html">dynamic discovery</a>, then clients can easily failover from one broker to another. However, stand alone brokers don't know about consumers on other brokers; so if there are no consumers on a certain broker, messages could just pile up without being consumed. We have an outstanding <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ-816">feature request</a> to tackle this on the client side - but currently the solution to this problem is to create a Network of brokers to store and forward messages between brokers.</p><h2 id="Clustering-Discoveryofbrokers">Discovery of brokers</h2><p>We support <a shape="rect" href="discovery.xml">auto-discovery</a> of brokers using <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/static-transport-reference.html">static discovery</a> or <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/discovery-transport-reference.html">dynamic discovery</a>, so clients can automatically detect and connect to a broker out of a logical group of brokers as well for brokers to discover and connect to other brokers to form large networks.</p><h2 id="Clustering-Networksofbrokers">Networks of brokers</h2><p>If you are using <a shape="rect" href="topologies.xml">client/server or hub/spoke style topology</a> and you have many clients and many brokers, there is a chance that one broker has producers but no consumers, so that messages pile up without being processed. To avoid this, ActiveMQ supports a <a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a> which provides <em>store and forward</em> to move messages from brokers with producers to brokers with consumers which allows us to support <a shape="rect" href="how-do-distributed-queues-work.xml">distributed queues and topics</a> across a network of brokers.</p><p>This allows a client to connect to any broker - and fail over to another broker if there is a failure - providing a cluster of brokers from the clients perspective.</p><p>Networks of brokers also allows us to scale up to a massive number of clients in a network as we can run as many brokers as we need.</p><p>You can think of this as a cluster of clients connecting with a cluster of brokers with auto-failover and discovery, making a simple and easy to use messaging fabric.</p><h2 id="Clustering-MasterSlave">Master Slave</h2><p>The problem with running lots of stand alone brokers or brokers in a network is that messages are owned by a single physical broker at any point in time. If that broker goes down, you have to wait for it to be restarted before the message can be delivered. (If you are using non-persistent messaging and a broker goes down you generally lose your message).</p><p>The idea behind <a shape="rect" href="masterslave.xml">MasterSlave</a> is that messages are replicated to a slave broker so that even if you have a catastrophic hardware failure of the master's machine, file system or data centre, you get immediate failover to the slave with no message loss.</p><h2 id="Clustering-ReplicatedMessageStores">Replicated Message Stores</h2><p>An alternative to <a shape="rect" href="masterslave.xml">MasterSlave</a> is to have some way to replicate the message store; so for the disk files to be shared in some way. For example using a SAN or shared network drive you can share the files of a broker so that if it fails another broker can take over straight away.</p><p>So by supporting a <a shape="rect" href="replicated-message-store.xml">Replicated Message Store</a> you can reduce the risk of message loss to provide either a HA backup or a full <a shape="rect" href="dr.xml">DR</a> solution capable of surviving a data centre failure.</p></div>
+<div class="wiki-content maincontent"><p>Clustering is a large topic and often means different things to different people. We'll try to list the various aspects of clustering and how they relate to ActiveMQ</p><h2>Queue consumer clusters</h2><p>ActiveMQ supports reliable high performance load balancing of messages on a queue across consumers. In enterprise integration, this scenario is known as the <a shape="rect" href="http://www.eaipatterns.com/CompetingConsumers.html">competing consumers</a> pattern. The following figure illustrates the concept:</p><p><image ac:align="center"><attachment ri:filename="competing-consumers.png"></attachment></image></p><p><span style="line-height: 1.4285715;">This solution receives the messages sent by the producers, enqueues them and distributes them between all the registered consumers. This has a number of benefits:</span></p><ul><li><span style="line-height: 1.4285715;">The load is distributed in a very dynamic fashion. Additional consumers could be provisioned and attached to the queue in high load periods, without modifying any configuration in the queue, as the new consumer would behave as just another competing consumer.</span></li><li><span style="line-height: 1.4285715;">Better availability than systems using a load balancer. Load balancers usually rely on a monitorization system to find out which real-servers are unavailable. With competing consumers, a failed consumer won't be competing for messages and therefore messages won't be delivered to it even without monitorization.</span></li><li>High reliability, if a consumer fails, any unacknowledged messages are redelivered to other consumers on the queue.</li></ul><p>On the downside, this pattern might not be ideal in systems where the order processing is required. To mitigate this problem while maintaining the benefits, the competing consumers pattern should be used in conjunction with other ActiveMQ <link><page ri:content-title="Features"></page><plain-text-link-body>features</plain-text-link-body></link> like the <link><page ri:content-title="Exclusive Consumer"></page><plain-text-link-body>exclusive consumers</plain-text-link-body></link> and the <link><page ri:content-title="Message Groups"></page><plain-text-link-body>message groups</plain-text-link-body></link> as stated in the <link><page ri:content-title="How do I preserve order of messages"></page><plain-text-link-body>ActiveMQ's FAQ</plain-text-link-body></link>.</p><h2>Broker clusters</h2><p>The most common mental model of clustering in a JMS context is that there is a collection of JMS brokers and a JMS client will connect to one of them; then if the JMS broker goes down, it will auto-reconnect to another broker.</p><p>We implement this using the <strong>failover://</strong> protocol in the JMS client. See the <link><page ri:content-title="Failover Transport Reference"></page></link> page for details of how to configure the failover protocol. <em>Note:</em> The reliable:// protocol in ActiveMQ 3.x has now been changed to the failover:// protocol</p><p>If we just run multiple brokers on a network and tell the clients about them using either <a shape="rect" href="http://incubator.apache.org/activemq/static-transport-reference.html">static discovery</a> or <a shape="rect" href="http://incubator.apache.org/activemq/discovery-transport-reference.html">dynamic discovery</a>, then clients can easily failover from one broker to another. However, stand alone brokers don't know about consumers on other brokers; so if there are no consumers on a certain broker, messages could just pile up without being consumed. We have an outstanding <a shape="rect" href="http://issues.apache.org/activemq/browse/AMQ-816">feature request</a> to tackle this on the client side - but currently the solution to this problem is to create a Network of brokers to store and forward messages between brokers.</p><h2>Discovery of brokers</h2><p>We support <link><page ri:content-title="Discovery"></page><plain-text-link-body>auto-discovery</plain-text-link-body></link> of brokers using <a shape="rect" href="http://incubator.apache.org/activemq/static-transport-reference.html">static discovery</a> or <a shape="rect" href="http://incubator.apache.org/activemq/discovery-transport-reference.html">dynamic discovery</a>, so clients can automatically detect and connect to a broker out of a logical group of brokers as well for brokers to discover and connect to other brokers to form large networks.</p><h2>Networks of brokers</h2><p>If you are using <link><page ri:content-title="Topologies"></page><plain-text-link-body>client/server or hub/spoke style topology</plain-text-link-body></link> and you have many clients and many brokers, there is a chance that one broker has producers but no consumers, so that messages pile up without being processed. To avoid this, ActiveMQ supports a <link><page ri:content-title="Networks of Brokers"></page></link> which provides <em>store and forward</em> to move messages from brokers with producers to brokers with consumers which allows us to support <link><page ri:content-title="How do distributed queues work"></page><plain-text-link-body>distributed queues and topics</plain-text-link-body></link> across a network of brokers.</p><p>This allows a client to connect to any broker - and fail over to another broker if there is a failure - providing a cluster of brokers from the clients perspective.</p><p>Networks of brokers also allows us to scale up to a massive number of clients in a network as we can run as many brokers as we need.</p><p>You can think of this as a cluster of clients connecting with a cluster of brokers with auto-failover and discovery, making a simple and easy to use messaging fabric.</p><h2>Master Slave</h2><p>The problem with running lots of stand alone brokers or brokers in a network is that messages are owned by a single physical broker at any point in time. If that broker goes down, you have to wait for it to be restarted before the message can be delivered. (If you are using non-persistent messaging and a broker goes down you generally lose your message).</p><p>The idea behind <link><page ri:content-title="MasterSlave"></page></link> is that messages are replicated to a slave broker so that even if you have a catastrophic hardware failure of the master's machine, file system or data centre, you get immediate failover to the slave with no message loss.</p><h2>Replicated Message Stores</h2><p>An alternative to <link><page ri:content-title="MasterSlave"></page></link> is to have some way to replicate the message store; so for the disk files to be shared in some way. For example using a SAN or shared network drive you can share the files of a broker so that if it fails another broker can take over straight away.</p><p>So by supporting a <link><page ri:content-title="Replicated Message Store"></page></link> you can reduce the risk of message loss to provide either a HA backup or a full <link><page ri:content-title="DR"></page></link> solution capable of surviving a data centre failure.</p></div>
diff --git a/cms/2007/04/18/activemq-cpp-11-released.xml b/cms/2007/04/18/activemq-cpp-11-released.xml
index 1912286..4eb6f0c 100644
--- a/cms/2007/04/18/activemq-cpp-11-released.xml
+++ b/cms/2007/04/18/activemq-cpp-11-released.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ-CPP 1.1 release is now official! You can download the source distribution <a shape="rect" href="../../../../cms/download.xml">here</a>.</p>
+<div class="wiki-content maincontent"><p>The ActiveMQ-CPP 1.1 release is now official! You can download the source distribution <link><page ri:content-title="Download"></page><link-body>here</link-body></link>.</p>
<p>There are several bug fixes and enhancements that you might want to pick up if you're currently using 1.0. This is our last patch release before 2.0, which will have full openwire support ... and we're almost there, so stay tuned!</p></div>
diff --git a/cms/2007/04/18/activemq-cpp-20-rc1-now-available.xml b/cms/2007/04/18/activemq-cpp-20-rc1-now-available.xml
index a144be8..6cc6950 100644
--- a/cms/2007/04/18/activemq-cpp-20-rc1-now-available.xml
+++ b/cms/2007/04/18/activemq-cpp-20-rc1-now-available.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>We've finally got OpenWire 2.0 Support! Download the Release candidate <a shape="rect" href="../../../../cms/download.xml">here</a></p></div>
+<div class="wiki-content maincontent"><p>We've finally got OpenWire 2.0 Support! Download the Release candidate <link><page ri:content-title="Download"></page><link-body>here</link-body></link></p></div>
diff --git a/cms/2007/04/20/activemq-cpp-20-release.xml b/cms/2007/04/20/activemq-cpp-20-release.xml
index ddf92f7..07a9860 100644
--- a/cms/2007/04/20/activemq-cpp-20-release.xml
+++ b/cms/2007/04/20/activemq-cpp-20-release.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Version 2.0 is now official. Download it from <a shape="rect" href="../../../../cms/activemq-cpp-20-release.xml">here</a></p></div>
+<div class="wiki-content maincontent"><p>Version 2.0 is now official. Download it from <link ac:tooltip="ActiveMQ-CPP 2.0 Release"><page ri:content-title="ActiveMQ-CPP 2.0 Release"></page><link-body>here</link-body></link></p></div>
diff --git a/cms/2007/04/30/activemq-cpp-201-rc1-now-available.xml b/cms/2007/04/30/activemq-cpp-201-rc1-now-available.xml
index 4ec46a7..151fa6d 100644
--- a/cms/2007/04/30/activemq-cpp-201-rc1-now-available.xml
+++ b/cms/2007/04/30/activemq-cpp-201-rc1-now-available.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP 2.0.1 RC1 is now available. This is a bug fix release that addresses some issues that were found in the 2.0 release. Download it from  the <a shape="rect" href="../../../../cms/activemq-cpp-201-release.xml">ActiveMQ-CPP 2.0.1 Release</a> page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP 2.0.1 RC1 is now available. This is a bug fix release that addresses some issues that were found in the 2.0 release. Download it from  the <link><page ri:content-title="ActiveMQ-CPP 2.0.1 Release"></page></link> page.</p></div>
diff --git a/cms/2007/04/30/cms-api-10-release.xml b/cms/2007/04/30/cms-api-10-release.xml
index ba88587..f008493 100644
--- a/cms/2007/04/30/cms-api-10-release.xml
+++ b/cms/2007/04/30/cms-api-10-release.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>We've finally released version 1.0 of the CMS (C++ Messaging Service) API. This is the JMS-like API for C++ applications implemented by ActiveMQ-CPP. The hope is that more and more C++ application will start moving toward a common API for messaging. You can download CMS 1.0 <a shape="rect" href="../../../../cms/cms-api-10-release.xml">here</a></p></div>
+<div class="wiki-content maincontent"><p>We've finally released version 1.0 of the CMS (C++ Messaging Service) API. This is the JMS-like API for C++ applications implemented by ActiveMQ-CPP. The hope is that more and more C++ application will start moving toward a common API for messaging. You can download CMS 1.0 <link><page ri:content-title="CMS API 1.0 Release"></page><link-body>here</link-body></link></p></div>
diff --git a/cms/2007/05/09/activemq-cpp-201-release.xml b/cms/2007/05/09/activemq-cpp-201-release.xml
index 0b66a40..08f835e 100644
--- a/cms/2007/05/09/activemq-cpp-201-release.xml
+++ b/cms/2007/05/09/activemq-cpp-201-release.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Version 2.0.1 is now official. Download it from <a shape="rect" href="../../../../cms/activemq-cpp-201-release.xml">here </a></p></div>
+<div class="wiki-content maincontent"><p>Version 2.0.1 is now official. Download it from <link ac:tooltip="ActiveMQ-CPP 2.0.1 Release"><page ri:content-title="ActiveMQ-CPP 2.0.1 Release"></page><link-body>here </link-body></link></p></div>
diff --git a/cms/2007/07/24/cms-api-11-release.xml b/cms/2007/07/24/cms-api-11-release.xml
index 8274219..da48c5b 100644
--- a/cms/2007/07/24/cms-api-11-release.xml
+++ b/cms/2007/07/24/cms-api-11-release.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>In preparation for the soon-to-be-released ActiveMQ-CPP 2.1, we're releasin version 1.1 of the CMS (C++ Messaging Service) API. This has a few tweaks to decouple the API from ActiveMQ-CPP and to support exporting symbols from a shared library. You can download CMS 1.1 <a shape="rect" href="../../../../cms/cms-api-11-release.xml">here</a></p></div>
+<div class="wiki-content maincontent"><p>In preparation for the soon-to-be-released ActiveMQ-CPP 2.1, we're releasin version 1.1 of the CMS (C++ Messaging Service) API. This has a few tweaks to decouple the API from ActiveMQ-CPP and to support exporting symbols from a shared library. You can download CMS 1.1 <link><page ri:content-title="CMS API 1.1 Release"></page><link-body>here</link-body></link></p></div>
diff --git a/cms/2007/07/25/activemq-cpp-21-rc1-release.xml b/cms/2007/07/25/activemq-cpp-21-rc1-release.xml
index df125c4..d7e7ad3 100644
--- a/cms/2007/07/25/activemq-cpp-21-rc1-release.xml
+++ b/cms/2007/07/25/activemq-cpp-21-rc1-release.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP 2.1 RC1 is now available. This release features the ability to build both static and shared libraries, as well as bug fixes and performance improvements. Download it from the <a shape="rect" href="../../../../cms/activemq-cpp-21-release.xml">ActiveMQ-CPP 2.1 Release</a> page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP 2.1 RC1 is now available. This release features the ability to build both static and shared libraries, as well as bug fixes and performance improvements. Download it from the <link><page ri:content-title="ActiveMQ-CPP 2.1 Release"></page></link> page.</p></div>
diff --git a/cms/2007/07/26/activemq-cpp-21-rc1-now-available.xml b/cms/2007/07/26/activemq-cpp-21-rc1-now-available.xml
index e2a0658..eeaca66 100644
--- a/cms/2007/07/26/activemq-cpp-21-rc1-now-available.xml
+++ b/cms/2007/07/26/activemq-cpp-21-rc1-now-available.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP 2.1 RC1 is now available. This release features many bug fixes along with several performance improvements. See the <a shape="rect" href="../../../../cms/activemq-cpp-21-release.xml">ActiveMQ-CPP 2.1</a> page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP 2.1 RC1 is now available. This release features many bug fixes along with several performance improvements. See the <link><page ri:content-title="ActiveMQ-CPP 2.1 Release"></page><link-body>ActiveMQ-CPP 2.1</link-body></link> page.</p></div>
diff --git a/cms/2007/08/07/activemq-cpp-21-release.xml b/cms/2007/08/07/activemq-cpp-21-release.xml
index a05abbc..f2ffc42 100644
--- a/cms/2007/08/07/activemq-cpp-21-release.xml
+++ b/cms/2007/08/07/activemq-cpp-21-release.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.1 is now official. You can find out what was fixed and get the latest src archives on the <a shape="rect" href="../../../../cms/activemq-cpp-21-release.xml">ActiveMQ-CPP 2.1 Release</a> page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.1 is now official. You can find out what was fixed and get the latest src archives on the <link><page ri:content-title="ActiveMQ-CPP 2.1 Release"></page></link> page.</p></div>
diff --git a/cms/2007/10/28/cms-api-12-release.xml b/cms/2007/10/28/cms-api-12-release.xml
index 5fd541b..cef638d 100644
--- a/cms/2007/10/28/cms-api-12-release.xml
+++ b/cms/2007/10/28/cms-api-12-release.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>In preparation for the soon-to-be-released ActiveMQ-CPP 2.1.1, we're releasing version 1.2 of the CMS (C++ Messaging Service) API. The main change in this release is that the readXXX() methods in BytesMessage were made const so that they may be used from within the MessageListener's onMessage method. You can download CMS 1.2 <a shape="rect" href="../../../../cms/cms-api-12-release.xml">here</a></p></div>
+<div class="wiki-content maincontent"><p>In preparation for the soon-to-be-released ActiveMQ-CPP 2.1.1, we're releasing version 1.2 of the CMS (C++ Messaging Service) API. The main change in this release is that the readXXX() methods in BytesMessage were made const so that they may be used from within the MessageListener's onMessage method. You can download CMS 1.2 <link><page ri:content-title="CMS API 1.2 Release"></page><link-body>here</link-body></link></p></div>
diff --git a/cms/2007/11/05/activemq-cpp-211-released.xml b/cms/2007/11/05/activemq-cpp-211-released.xml
index 08d2eae..bce167c 100644
--- a/cms/2007/11/05/activemq-cpp-211-released.xml
+++ b/cms/2007/11/05/activemq-cpp-211-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.1.1 is now official. You can find out what was fixed and get the latest src archives on the <a shape="rect" href="../../../../cms/activemq-cpp-211-release.xml">ActiveMQ-CPP 2.1.1 Release</a> page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.1.1 is now official. You can find out what was fixed and get the latest src archives on the <link><page ri:content-title="ActiveMQ-CPP 2.1.1 Release"></page></link> page.</p></div>
diff --git a/cms/2007/11/26/solaris-platform.xml b/cms/2007/11/26/solaris-platform.xml
index eeea9b1..d54bdf8 100644
--- a/cms/2007/11/26/solaris-platform.xml
+++ b/cms/2007/11/26/solaris-platform.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="error"><span class="error">Unable to render {children}.</span> Can only find children for a page, this is a blogpost.</div></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="8ac3e1a2-e372-4fce-8fb2-facd210a99ad" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/cms/2007/11/28/activemq-cpp-212-released.xml b/cms/2007/11/28/activemq-cpp-212-released.xml
index bd140c5..3bf5603 100644
--- a/cms/2007/11/28/activemq-cpp-212-released.xml
+++ b/cms/2007/11/28/activemq-cpp-212-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.1.2 is now official. You can find out what was fixed and get the latest src archives on the <a shape="rect" href="../../../../cms/activemq-cpp-212-release.xml">ActiveMQ-CPP 2.1.2 Release</a> Release page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.1.2 is now official. You can find out what was fixed and get the latest src archives on the <link><page ri:content-title="ActiveMQ-CPP 2.1.2 Release"></page></link> Release page.</p></div>
diff --git a/cms/2007/12/10/activemq-cpp-213-released.xml b/cms/2007/12/10/activemq-cpp-213-released.xml
index bfecea5..129ebcd 100644
--- a/cms/2007/12/10/activemq-cpp-213-released.xml
+++ b/cms/2007/12/10/activemq-cpp-213-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.1.3 is now official. You can find out what was fixed and get the latest src archives on the <a shape="rect" href="../../../../cms/activemq-cpp-213-release.xml">Release</a> page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.1.3 is now official. You can find out what was fixed and get the latest src archives on the <link><page ri:content-title="ActiveMQ-CPP 2.1.3 Release"></page><link-body>Release</link-body></link> page.</p></div>
diff --git a/cms/2008/06/22/activemq-cpp-22-released.xml b/cms/2008/06/22/activemq-cpp-22-released.xml
index bc05fdb..10067b2 100644
--- a/cms/2008/06/22/activemq-cpp-22-released.xml
+++ b/cms/2008/06/22/activemq-cpp-22-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.2 is now official. You can find out what was fixed and get the latest src archives on the <a shape="rect" href="../../../../cms/activemq-cpp-22-release.xml">Release</a> page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.2 is now official. You can find out what was fixed and get the latest src archives on the <link><page ri:content-title="ActiveMQ CPP 2.2 Release"></page><link-body>Release</link-body></link> page.</p></div>
diff --git a/cms/2008/09/10/activemq-cpp-221-released.xml b/cms/2008/09/10/activemq-cpp-221-released.xml
index 064c749..6b57dbf 100644
--- a/cms/2008/09/10/activemq-cpp-221-released.xml
+++ b/cms/2008/09/10/activemq-cpp-221-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.2.1 is now official. You can find out what was fixed and get the latest src archives on the <a shape="rect" href="../../../../cms/activemq-cpp-221-release.xml">Release</a> page.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP V2.2.1 is now official. You can find out what was fixed and get the latest src archives on the <link><page ri:content-title="ActiveMQ-CPP 2.2.1 Release"></page><link-body>Release</link-body></link> page.</p></div>
diff --git a/cms/2008/11/24/activemq-cpp-222-released.xml b/cms/2008/11/24/activemq-cpp-222-released.xml
index 31f5244..8b4ee55 100644
--- a/cms/2008/11/24/activemq-cpp-222-released.xml
+++ b/cms/2008/11/24/activemq-cpp-222-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <a shape="rect" href="../../../../cms/activemq-cpp-222-release.xml">Release</a> page for more info.</p></div>
+<div class="wiki-content maincontent"><p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <link><page ri:content-title="ActiveMQ-CPP 2.2.2 Release"></page><link-body>Release</link-body></link> page for more info.</p></div>
diff --git a/cms/2009/01/12/activemq-cpp-223-released.xml b/cms/2009/01/12/activemq-cpp-223-released.xml
index 44447e9..a714086 100644
--- a/cms/2009/01/12/activemq-cpp-223-released.xml
+++ b/cms/2009/01/12/activemq-cpp-223-released.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent">
-<p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <a shape="rect" href="../../../../cms/activemq-cpp-223-release.xml">Release</a> page for more info.</p></div>
+<p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <link><page ri:content-title="ActiveMQ-CPP 2.2.3 Release"></page><link-body>Release</link-body></link> page for more info.</p></div>
diff --git a/cms/2009/02/21/activemq-cpp-224-released.xml b/cms/2009/02/21/activemq-cpp-224-released.xml
index 7355215..0770574 100644
--- a/cms/2009/02/21/activemq-cpp-224-released.xml
+++ b/cms/2009/02/21/activemq-cpp-224-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <a shape="rect" href="../../../../cms/activemq-cpp-224-release.xml">Release</a> page for more info.</p></div>
+<div class="wiki-content maincontent"><p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <link><page ri:content-title="ActiveMQ-CPP 2.2.4 Release"></page><link-body>Release</link-body></link> page for more info.</p></div>
diff --git a/cms/2009/03/25/activemq-cpp-225-released.xml b/cms/2009/03/25/activemq-cpp-225-released.xml
index cd328e5..5b73932 100644
--- a/cms/2009/03/25/activemq-cpp-225-released.xml
+++ b/cms/2009/03/25/activemq-cpp-225-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <a shape="rect" href="../../../../cms/activemq-cpp-225-release.xml">Release</a> page for more info.</p></div>
+<div class="wiki-content maincontent"><p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <link><page ri:content-title="ActiveMQ-CPP 2.2.5 Release"></page><link-body>Release</link-body></link> page for more info.</p></div>
diff --git a/cms/2009/05/17/activemq-cpp-226-released.xml b/cms/2009/05/17/activemq-cpp-226-released.xml
index 59df355..da0d39f 100644
--- a/cms/2009/05/17/activemq-cpp-226-released.xml
+++ b/cms/2009/05/17/activemq-cpp-226-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <a shape="rect" href="../../../../cms/activemq-cpp-226-release.xml">Release</a> page for more info.</p></div>
+<div class="wiki-content maincontent"><p>The newest version of the CPP library has been released, lots of good bug fixes added. See the <link><page ri:content-title="ActiveMQ-CPP 2.2.6 Release"></page><link-body>Release</link-body></link> page for more info.</p></div>
diff --git a/cms/2009/06/12/activemq-cpp-30-released.xml b/cms/2009/06/12/activemq-cpp-30-released.xml
index 2607433..538d1b5 100644
--- a/cms/2009/06/12/activemq-cpp-30-released.xml
+++ b/cms/2009/06/12/activemq-cpp-30-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP 3.0 is now officially released, check out the <a shape="rect" href="../../../../cms/activemq-cpp-30-release.xml">Release</a> page for a list of what's changed and to download the source bundle now!</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP 3.0 is now officially released, check out the <link><page ri:content-title="ActiveMQ-CPP 3.0 Release"></page><link-body>Release</link-body></link> page for a list of what's changed and to download the source bundle now!</p></div>
diff --git a/cms/2009/07/03/activemq-cpp-301-released.xml b/cms/2009/07/03/activemq-cpp-301-released.xml
index e761c84..daa4685 100644
--- a/cms/2009/07/03/activemq-cpp-301-released.xml
+++ b/cms/2009/07/03/activemq-cpp-301-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP 3.0.1 is now officially released, check out the <a shape="rect" href="../../../../cms/activemq-cpp-301-release.xml">Release page</a> for a list of what's changed and to download the source bundle now!</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP 3.0.1 is now officially released, check out the <link><page ri:content-title="ActiveMQ-CPP 3.0.1 Release"></page><link-body>Release page</link-body></link> for a list of what's changed and to download the source bundle now!</p></div>
diff --git a/cms/2009/12/20/activemq-cpp-310-officially-released.xml b/cms/2009/12/20/activemq-cpp-310-officially-released.xml
index 86d8485..75db81e 100644
--- a/cms/2009/12/20/activemq-cpp-310-officially-released.xml
+++ b/cms/2009/12/20/activemq-cpp-310-officially-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ-CPP 3.1.0 is now officially released, check out the <a shape="rect" href="../../../../cms/activemq-cpp-310-release.xml">Release</a> page for a list of what's changed and to download the source bundle now!</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ-CPP 3.1.0 is now officially released, check out the <link><page ri:content-title="ActiveMQ-CPP 3.1.0 Release"></page><link-body>Release</link-body></link> page for a list of what's changed and to download the source bundle now!</p></div>
diff --git a/cms/2010/03/27/activemq-cpp-312-released.xml b/cms/2010/03/27/activemq-cpp-312-released.xml
index 9cf61fb..b46aadb 100644
--- a/cms/2010/03/27/activemq-cpp-312-released.xml
+++ b/cms/2010/03/27/activemq-cpp-312-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Version 3.1.2 just released, fixes for a few important issues that caused segfaults have been added. Get your copy <a shape="rect" href="../../../../cms/activemq-cpp-312-release.xml">here</a>:</p></div>
+<div class="wiki-content maincontent"><p>Version 3.1.2 just released, fixes for a few important issues that caused segfaults have been added. Get your copy <link><page ri:content-title="ActiveMQ-CPP 3.1.2 Release"></page><link-body>here</link-body></link>:</p></div>
diff --git a/cms/2010/06/18/activemq-cpp-320-released.xml b/cms/2010/06/18/activemq-cpp-320-released.xml
index 3407e4c..137323d 100644
--- a/cms/2010/06/18/activemq-cpp-320-released.xml
+++ b/cms/2010/06/18/activemq-cpp-320-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Version 3.2.0 of ActiveMQ-CPP has now been officially released which include support for SSL along with QueueBrowser and Message body compression. Download the source bundle from the <a shape="rect" href="../../../../cms/activemq-cpp-320-release.xml">Release Page</a>.</p></div>
+<div class="wiki-content maincontent"><p>Version 3.2.0 of ActiveMQ-CPP has now been officially released which include support for SSL along with QueueBrowser and Message body compression. Download the source bundle from the <link><page ri:content-title="ActiveMQ-CPP 3.2.0 Release"></page><link-body>Release Page</link-body></link>.</p></div>
diff --git a/cms/2010/07/03/activemq-cpp-v321-released.xml b/cms/2010/07/03/activemq-cpp-v321-released.xml
index df55be6..194db9d 100644
--- a/cms/2010/07/03/activemq-cpp-v321-released.xml
+++ b/cms/2010/07/03/activemq-cpp-v321-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-321-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.2.1 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2010/09/16/activemq-cpp-v322-released.xml b/cms/2010/09/16/activemq-cpp-v322-released.xml
index 069d5ad..dab7a36 100644
--- a/cms/2010/09/16/activemq-cpp-v322-released.xml
+++ b/cms/2010/09/16/activemq-cpp-v322-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-322-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.2.2 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2010/09/16/activemq-cpp-v323-released.xml b/cms/2010/09/16/activemq-cpp-v323-released.xml
index 4a20797..4ed4e9a 100644
--- a/cms/2010/09/16/activemq-cpp-v323-released.xml
+++ b/cms/2010/09/16/activemq-cpp-v323-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-323-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.2.3 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2010/12/10/activemq-cpp-v324-released.xml b/cms/2010/12/10/activemq-cpp-v324-released.xml
index 9b91171..f4d3315 100644
--- a/cms/2010/12/10/activemq-cpp-v324-released.xml
+++ b/cms/2010/12/10/activemq-cpp-v324-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-324-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.2.4 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2011/03/05/activemq-cpp-v325-released.xml b/cms/2011/03/05/activemq-cpp-v325-released.xml
index 982963b..fac6b48 100644
--- a/cms/2011/03/05/activemq-cpp-v325-released.xml
+++ b/cms/2011/03/05/activemq-cpp-v325-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-325-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest patch release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.2.5 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2011/04/15/activemq-cpp-v330-released.xml b/cms/2011/04/15/activemq-cpp-v330-released.xml
index b7f1eeb..cbbbd17 100644
--- a/cms/2011/04/15/activemq-cpp-v330-released.xml
+++ b/cms/2011/04/15/activemq-cpp-v330-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-330-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.3.0 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2011/04/29/activemq-cpp-v340-released.xml b/cms/2011/04/29/activemq-cpp-v340-released.xml
index 0f8b8f8..4fa7871 100644
--- a/cms/2011/04/29/activemq-cpp-v340-released.xml
+++ b/cms/2011/04/29/activemq-cpp-v340-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-340-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.4.0 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2011/12/18/activemq-cpp-version-341-released.xml b/cms/2011/12/18/activemq-cpp-version-341-released.xml
index 7cf7919..5a81732 100644
--- a/cms/2011/12/18/activemq-cpp-version-341-released.xml
+++ b/cms/2011/12/18/activemq-cpp-version-341-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-341-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.4.1 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2012/04/27/activemq-cpp-version-342-released.xml b/cms/2012/04/27/activemq-cpp-version-342-released.xml
index 48a5f51..5875d28 100644
--- a/cms/2012/04/27/activemq-cpp-version-342-released.xml
+++ b/cms/2012/04/27/activemq-cpp-version-342-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" href="../../../../cms/index.xml">ActiveMQ-CPP</a> is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-342-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of <link><page ri:content-title="Index"></page><link-body>ActiveMQ-CPP</link-body></link> is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.4.2 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2012/06/02/activemq-cpp-version-343-released.xml b/cms/2012/06/02/activemq-cpp-version-343-released.xml
index ad3542d..296735f 100644
--- a/cms/2012/06/02/activemq-cpp-version-343-released.xml
+++ b/cms/2012/06/02/activemq-cpp-version-343-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" href="../../../../cms/index.xml">ActiveMQ-CPP</a> is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-343-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of <link><page ri:content-title="Index"></page><link-body>ActiveMQ-CPP</link-body></link> is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.4.3 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2012/06/29/activemq-cpp-version-344-released.xml b/cms/2012/06/29/activemq-cpp-version-344-released.xml
index 8482788..3c37f0b 100644
--- a/cms/2012/06/29/activemq-cpp-version-344-released.xml
+++ b/cms/2012/06/29/activemq-cpp-version-344-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of <a shape="rect" href="../../../../cms/activemq-cpp-344-release.xml">ActiveMQ-CPP</a> is out, you can download the source bundles here.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of <link><page ri:content-title="ActiveMQ-CPP 3.4.4 Release"></page><link-body>ActiveMQ-CPP</link-body></link> is out, you can download the source bundles here.</p></div>
diff --git a/cms/2012/10/12/activemq-cpp-v345-released.xml b/cms/2012/10/12/activemq-cpp-v345-released.xml
index 9cbd46f..2a99373 100644
--- a/cms/2012/10/12/activemq-cpp-v345-released.xml
+++ b/cms/2012/10/12/activemq-cpp-v345-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can <a shape="rect" href="../../../../cms/activemq-cpp-345-release.xml">download</a> the source bundles here.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can <link><page ri:content-title="ActiveMQ-CPP 3.4.5 Release"></page><link-body>download</link-body></link> the source bundles here.</p></div>
diff --git a/cms/2012/12/20/activemq-cpp-version-350-released.xml b/cms/2012/12/20/activemq-cpp-version-350-released.xml
index adb4bff..6f83d4a 100644
--- a/cms/2012/12/20/activemq-cpp-version-350-released.xml
+++ b/cms/2012/12/20/activemq-cpp-version-350-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <a shape="rect" href="../../../../cms/activemq-cpp-350-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The newest release of ActiveMQ-CPP is out, you can download the source bundles <link><page ri:content-title="ActiveMQ-CPP 3.5.0 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2013/03/08/activemq-cpp-v360-released.xml b/cms/2013/03/08/activemq-cpp-v360-released.xml
index 6f6f804..752b162 100644
--- a/cms/2013/03/08/activemq-cpp-v360-released.xml
+++ b/cms/2013/03/08/activemq-cpp-v360-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a lot of stability fixes. Download your copy from <a shape="rect" href="../../../../cms/activemq-cpp-360-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a lot of stability fixes. Download your copy from <link><page ri:content-title="ActiveMQ-CPP 3.6.0 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2013/05/19/activemq-cpp-v370-released.xml b/cms/2013/05/19/activemq-cpp-v370-released.xml
index e1c96a0..519a000 100644
--- a/cms/2013/05/19/activemq-cpp-v370-released.xml
+++ b/cms/2013/05/19/activemq-cpp-v370-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a lot of stability fixes. Download your copy from <a shape="rect" href="../../../../cms/activemq-cpp-370-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a lot of stability fixes. Download your copy from <link><page ri:content-title="ActiveMQ-CPP 3.7.0 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2013/09/07/activemq-cpp-v380-released.xml b/cms/2013/09/07/activemq-cpp-v380-released.xml
index b81da79..1d16921 100644
--- a/cms/2013/09/07/activemq-cpp-v380-released.xml
+++ b/cms/2013/09/07/activemq-cpp-v380-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a lot of stability fixes and a few new features. Download your copy from <a shape="rect" href="../../../../cms/activemq-cpp-380-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a lot of stability fixes and a few new features. Download your copy from <link><page ri:content-title="ActiveMQ-CPP 3.8.0 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2013/09/19/activemq-cpp-v381-released.xml b/cms/2013/09/19/activemq-cpp-v381-released.xml
index 13898fe..8ff3cdb 100644
--- a/cms/2013/09/19/activemq-cpp-v381-released.xml
+++ b/cms/2013/09/19/activemq-cpp-v381-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" href="../../../../cms/activemq-cpp-381-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <link><page ri:content-title="ActiveMQ-CPP 3.8.1 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2013/12/10/activemq-cpp-v382-released.xml b/cms/2013/12/10/activemq-cpp-v382-released.xml
index 98f0d46..e34b4af 100644
--- a/cms/2013/12/10/activemq-cpp-v382-released.xml
+++ b/cms/2013/12/10/activemq-cpp-v382-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" href="../../../../cms/activemq-cpp-382-release.xml">here</a>.</p></div>
+<div class="wiki-content maincontent"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <link><page ri:content-title="ActiveMQ-CPP 3.8.2 Release"></page><link-body>here</link-body></link>.</p></div>
diff --git a/cms/2015/08/16/activemq-cpp-v390-released.xml b/cms/2015/08/16/activemq-cpp-v390-released.xml
index 45a9154..c30a142 100644
--- a/cms/2015/08/16/activemq-cpp-v390-released.xml
+++ b/cms/2015/08/16/activemq-cpp-v390-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-390-release.html">here</a>.</p></div></div></div>
+<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" href="http://activemq.apache.org/cms/activemq-cpp-390-release.html">here</a>.</p></div></div></div>
diff --git a/cms/2015/12/04/activemq-cpp-v391-released.xml b/cms/2015/12/04/activemq-cpp-v391-released.xml
index 4f58f26..1da6e6c 100644
--- a/cms/2015/12/04/activemq-cpp-v391-released.xml
+++ b/cms/2015/12/04/activemq-cpp-v391-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-391-release.html">here</a>.</p></div></div></div></div>
+<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" href="http://activemq.apache.org/cms/activemq-cpp-391-release.html">here</a>.</p></div></div></div></div>
diff --git a/cms/2016/02/09/activemq-cpp-v392-released.xml b/cms/2016/02/09/activemq-cpp-v392-released.xml
index e17917a..26feb0f 100644
--- a/cms/2016/02/09/activemq-cpp-v392-released.xml
+++ b/cms/2016/02/09/activemq-cpp-v392-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small STOMP protocol fix, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-392-release.html">here</a>.</p></div></div></div></div></div>
+<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small STOMP protocol fix, grab the source bundle <a shape="rect" href="http://activemq.apache.org/cms/activemq-cpp-392-release.html">here</a>.</p></div></div></div></div></div>
diff --git a/cms/2016/04/01/activemq-cpp-v393-released.xml b/cms/2016/04/01/activemq-cpp-v393-released.xml
index c14096b..1d7f7a3 100644
--- a/cms/2016/04/01/activemq-cpp-v393-released.xml
+++ b/cms/2016/04/01/activemq-cpp-v393-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small fix to ensure failed producer create throws an exception, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-393-release.html">here</a>.</p></div></div></div></div></div></div>
+<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small fix to ensure failed producer create throws an exception, grab the source bundle <a shape="rect" href="http://activemq.apache.org/cms/activemq-cpp-393-release.html">here</a>.</p></div></div></div></div></div></div>
diff --git a/cms/2017/02/24/activemq-cpp-v394-released.xml b/cms/2017/02/24/activemq-cpp-v394-released.xml
index 6109a5e..ac32058 100644
--- a/cms/2017/02/24/activemq-cpp-v394-released.xml
+++ b/cms/2017/02/24/activemq-cpp-v394-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small fix to ensure failed producer create throws an exception, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-394-release.html">here</a>.</p></div></div></div></div></div></div></div>
+<div class="wiki-content maincontent"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small fix to ensure failed producer create throws an exception, grab the source bundle <a shape="rect" href="http://activemq.apache.org/cms/activemq-cpp-394-release.html">here</a>.</p></div></div></div></div></div></div></div>
diff --git a/cms/activemq-cpp-10-release.xml b/cms/activemq-cpp-10-release.xml
index 8be040e..6a53b06 100644
--- a/cms/activemq-cpp-10-release.xml
+++ b/cms/activemq-cpp-10-release.xml
@@ -1,31 +1,25 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP1.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is our first official release of ActiveMQ CPP. Some of the included features are:</p>
<ul><li>CMS - a JMS-like API</li><li>Implementation of the Stomp protocol (compatable with AMQ broker 4.0.2 and later)</li><li>Extensible architecture for supporting additional messaging protocols (focus on OpenWire for the next major release)</li><li>Robust, Java-like library providing streams, readers/writers, and even a synchronized macro</li><li>Build has been tested on win32, linux, solaris, and OSX</li></ul>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker version >= 4.0.2</p>
-</div></div>
+<structured-macro ac:macro-id="face4afb-579d-4e99-96b2-567d67cb49d1" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker version >= 4.0.2</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP1.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.0-src.zip">activemq-cpp-1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-1.0-src.zip.asc">activemq-cpp-1.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.0-src.tar.gz">activemq-cpp-1.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-1.0-src.tar.gz.asc">activemq-cpp-1.0-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.0-src.zip">activemq-cpp-1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-1.0-src.zip.asc">activemq-cpp-1.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.0-src.tar.gz">activemq-cpp-1.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-1.0-src.tar.gz.asc">activemq-cpp-1.0-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP1.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c09f0cd6-d916-43ea-8bb4-5a064372c881" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-1.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP1.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11803&styleName=Html&projectId=11000&Create=Create">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Unable to locate JIRA server for this macro. It may be due to Application Link configuration.
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11803&styleName=Html&projectId=11000&Create=Create">release notes</a><br clear="none">
+<structured-macro ac:macro-id="1f8ba1b4-ba3b-4934-ba70-f6dded5c4d2a" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="https://issues.apache.org/activemq/secure/IssueNavigator.jspa?view=rss&&pid=11000&fixfor=11803&sorter/field=issuekey&sorter/order=DESC&tempMax=25&reset=true&decorator=none"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-11-release.xml b/cms/activemq-cpp-11-release.xml
index 97a7928..e1c7759 100644
--- a/cms/activemq-cpp-11-release.xml
+++ b/cms/activemq-cpp-11-release.xml
@@ -1,32 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP1.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This version fixes several bugs and adds a few new features.</p>
<ul><li>Updated interface for cms::BytesMessage - more JMS-like.</li><li>Updated the MessageProducer interface to add multiple versions of the send method</li><li>Fixed several memory leaks</li><li>Now run on linux, win32, OS X, and Solaris</li><li>Persistence is fixed</li><li>Fixed deadlocks when closing a connection</li><li>Fixed message expiration</li></ul>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker version >= 4.0.2</p>
-</div></div>
+<structured-macro ac:macro-id="751ce70c-ec16-43c2-9cc3-1bc085b2811f" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker version >= 4.0.2</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP1.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.1-src.zip">activemq-cpp-1.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-1.1-src.zip.asc">activemq-cpp-1.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.1-src.tar.gz">activemq-cpp-1.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-1.1-src.tar.gz.asc">activemq-cpp-1.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.1-src.zip">activemq-cpp-1.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-1.1-src.zip.asc">activemq-cpp-1.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.1-src.tar.gz">activemq-cpp-1.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-1.1-src.tar.gz.asc">activemq-cpp-1.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP1.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5c279de2-8e3a-4059-bd0d-8a36fd206506" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-1.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP1.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11804">release notes</a></p>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11804">release notes</a></p>
-<p></p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p><structured-macro ac:macro-id="6908fa2d-b0d3-4024-8da6-8a2bbb018361" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="https://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=11000&fixfor=11804&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-20-release.xml b/cms/activemq-cpp-20-release.xml
index 311e620..5a2856f 100644
--- a/cms/activemq-cpp-20-release.xml
+++ b/cms/activemq-cpp-20-release.xml
@@ -1,31 +1,25 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This version fixes several bugs and adds a few new features.</p>
<ul><li>Full OpenWire v2 support!</li><li>You can switch between openwire and stomp via the connection URL</li><li>Temporary destinations when using OpenWire</li><li>Added support for asynchronous send</li><li>Fixed client acknowledge</li><li>Resolved some memory leaks</li><li>Sessions are now single threaded</li></ul>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker version >= 4.0.2</p>
-</div></div>
+<structured-macro ac:macro-id="dc658eb4-f767-4c44-88cb-8673bb2a3fe5" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker version >= 4.0.2</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.0-src.zip">activemq-cpp-2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.0-src.zip.asc">activemq-cpp-2.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.0-src.tar.gz">activemq-cpp-2.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.0-src.tar.gz.asc">activemq-cpp-2.0-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.0-src.zip">activemq-cpp-2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.0-src.zip.asc">activemq-cpp-2.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.0-src.tar.gz">activemq-cpp-2.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.0-src.tar.gz.asc">activemq-cpp-2.0-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="99a489ff-8129-4cef-94b2-314d477609ed" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11805">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11805">release notes</a><br clear="none">
+<structured-macro ac:macro-id="fac6a6d0-eb70-469e-9a51-c77c4fcbf9c7" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=11000&fixfor=11805&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-201-release.xml b/cms/activemq-cpp-201-release.xml
index 67e8f0b..824df64 100644
--- a/cms/activemq-cpp-201-release.xml
+++ b/cms/activemq-cpp-201-release.xml
@@ -1,33 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.0.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This version fixes several small bugs that made their way into the 2.0 release.</p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker version >= 4.0.2</p>
-</div></div>
+<structured-macro ac:macro-id="16db8a88-bafc-43da-aed1-f0a26197dd37" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker version >= 4.0.2</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.0.1Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.0.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.0.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.0.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.0.1-src.zip">activemq-cpp-2.0.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.0.1-src.zip.asc">activemq-cpp-2.0.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.0.1-src.tar.gz">activemq-cpp-2.0.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.0.1-src.tar.gz.asc">activemq-cpp-2.0.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.0.1-src.zip">activemq-cpp-2.0.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.0.1-src.zip.asc">activemq-cpp-2.0.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.0.1-src.tar.gz">activemq-cpp-2.0.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.0.1-src.tar.gz.asc">activemq-cpp-2.0.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.0.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="258be818-0486-4330-a8f9-e6d75badd8a2" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.0.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.0.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11823">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11823">release notes</a><br clear="none">
+<structured-macro ac:macro-id="07df0cb6-257b-4d1a-a3d5-527fddb745d2" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=11000&fixfor=11823&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-21-release.xml b/cms/activemq-cpp-21-release.xml
index bb8a7ed..d4bb728 100644
--- a/cms/activemq-cpp-21-release.xml
+++ b/cms/activemq-cpp-21-release.xml
@@ -1,33 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This version includes several bugfixes, as well as some new features. Also a lot of work has been done on performance and memory leaks. One new feature that has been highly anticipated is that we now build both shared and static libraries.</p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 family</p>
-</div></div>
+<structured-macro ac:macro-id="d875edd5-8b79-420c-97ab-e984d10ae133" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 family</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.1Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1-src.zip">activemq-cpp-2.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1-src.zip.asc">activemq-cpp-2.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1-src.tar.gz">activemq-cpp-2.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1-src.tar.gz.asc">activemq-cpp-2.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1-src.zip">activemq-cpp-2.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1-src.zip.asc">activemq-cpp-2.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1-src.tar.gz">activemq-cpp-2.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1-src.tar.gz.asc">activemq-cpp-2.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ff353036-1c98-4290-a897-1834730bd2df" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11812">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11812">release notes</a><br clear="none">
+<structured-macro ac:macro-id="789f096d-f614-4636-9691-d62c1df83d8b" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11812&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-211-release.xml b/cms/activemq-cpp-211-release.xml
index 49957c4..91df88b 100644
--- a/cms/activemq-cpp-211-release.xml
+++ b/cms/activemq-cpp-211-release.xml
@@ -1,33 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.1.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This version includes several bugfixes, as well as some new examples.  Also a lot of work has been done on performance and memory leaks and stability.</p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 family</p>
-</div></div>
+<structured-macro ac:macro-id="56fc63cf-c71a-480d-be27-e05b09c922f8" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 family</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.1.1Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.1.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.1-src.zip">activemq-cpp-2.1.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.1-src.zip.asc">activemq-cpp-2.1.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.1-src.tar.gz">activemq-cpp-2.1.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.1-src.tar.gz.asc">activemq-cpp-2.1.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.1-src.zip">activemq-cpp-2.1.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.1-src.zip.asc">activemq-cpp-2.1.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.1-src.tar.gz">activemq-cpp-2.1.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.1-src.tar.gz.asc">activemq-cpp-2.1.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.1.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="74b7a94a-1ef3-4df8-9247-ff1bda9eba8b" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.1.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.1.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
<p>For a more detailed view of new features and bug fixes, see the [release notes|http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11848]</p>
-<p></p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p><structured-macro ac:macro-id="7d9b80f2-bf4a-478c-a5a5-e44c6206bf7b" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11848&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-212-release.xml b/cms/activemq-cpp-212-release.xml
index fb60a19..5f1a3f8 100644
--- a/cms/activemq-cpp-212-release.xml
+++ b/cms/activemq-cpp-212-release.xml
@@ -1,34 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.1.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This version adds support for building the client code on the Solaris platform using the Sun Studio 11 compiler. Also makes some small improvements to the AutoConf scripts on various platforms.</p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 family</p>
-</div></div>
+<structured-macro ac:macro-id="71fceb0a-409a-4ff0-a07d-58e1f15b6b0f" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 family</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.1.2Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.1.2Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.2-src.zip">activemq-cpp-2.1.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.2-src.zip.asc">activemq-cpp-2.1.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.2-src.tar.gz">activemq-cpp-2.1.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.2-src.tar.gz.asc">activemq-cpp-2.1.2-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.2-src.zip">activemq-cpp-2.1.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.2-src.zip.asc">activemq-cpp-2.1.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.2-src.tar.gz">activemq-cpp-2.1.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.2-src.tar.gz.asc">activemq-cpp-2.1.2-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.1.2Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3fba3156-6056-4338-ac0f-c18ec0efbc0e" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.1.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.1.2Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11860">release notes</a></p>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11860">release notes</a></p>
-<p></p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p><structured-macro ac:macro-id="5c520ab3-1179-4590-a085-0992535c877c" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11860&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-213-release.xml b/cms/activemq-cpp-213-release.xml
index eec87b6..29705fc 100644
--- a/cms/activemq-cpp-213-release.xml
+++ b/cms/activemq-cpp-213-release.xml
@@ -1,34 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.1.3Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This version adds more support for building the client code on the Solaris platform using the Sun Studio 11 and 12 compilers as well as fixed a small OS/X configure script problem. Also makes some small improvements to the AutoConf scripts on various platforms.</p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 and 5.0 family</p>
-</div></div>
+<structured-macro ac:macro-id="d407f8cc-14b9-46fd-9a5e-1e0a277450d5" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 and 5.0 family</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.1.3Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.1.3Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.3-src.zip">activemq-cpp-2.1.3-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.3-src.zip.asc">activemq-cpp-2.1.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.3-src.tar.gz">activemq-cpp-2.1.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.3-src.tar.gz.asc">activemq-cpp-2.1.3-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.3-src.zip">activemq-cpp-2.1.3-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.3-src.zip.asc">activemq-cpp-2.1.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.1.3-src.tar.gz">activemq-cpp-2.1.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.1.3-src.tar.gz.asc">activemq-cpp-2.1.3-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.1.3Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d8e792c0-65d4-4603-9637-84ed1810b2bd" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.1.3/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.1.3Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11860">release notes</a></p>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11860">release notes</a></p>
-<p></p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p><structured-macro ac:macro-id="f0d7adc2-fd9e-447b-ad55-ab72d40dd823" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11862&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-22-release.xml b/cms/activemq-cpp-22-release.xml
index 2d7a007..77a0e20 100644
--- a/cms/activemq-cpp-22-release.xml
+++ b/cms/activemq-cpp-22-release.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQCPP2.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release has seen a large restructuring of the codebase to separate out to platform code into a new package called decaf. We are now making use of the APR and APR-Util libraries for platform independence. Also many new tests and bug fixes have made their way into this release.</p>
@@ -7,32 +7,26 @@
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 and 5.0 family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="a46f2273-1f6b-4847-87ed-ec1d40369d6e" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatable with ActiveMQ Broker versions in the 4.0 and 5.0 family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQCPP2.2Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.1.1">here</a></p>
-<h2 id="ActiveMQCPP2.2Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2-src.zip">activemq-cpp-2.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2-src.zip.asc">activemq-cpp-2.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2-src.tar.gz">activemq-cpp-2.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2-src.tar.gz.asc">activemq-cpp-2.2-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2-src.zip">activemq-cpp-2.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2-src.zip.asc">activemq-cpp-2.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2-src.tar.gz">activemq-cpp-2.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2-src.tar.gz.asc">activemq-cpp-2.2-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQCPP2.2Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="16fc7eba-15bb-4749-b4f6-a6f2afbfc155" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQCPP2.2Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11860">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11860">release notes</a><br clear="none">
+<structured-macro ac:macro-id="fbdea853-6541-4f3c-a67c-8dbea5f9e4a6" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11830&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-221-release.xml b/cms/activemq-cpp-221-release.xml
index d0c634a..ffcfa95 100644
--- a/cms/activemq-cpp-221-release.xml
+++ b/cms/activemq-cpp-221-release.xml
@@ -1,33 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.2.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor release incorporating several bug fixes that have been found since the 2.2 release.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="c4f7e07c-3052-4ef8-9193-ab0abb220d8f" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP2.2.1Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.2.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.1-src.zip">activemq-cpp-2.2.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.1-src.zip.asc">activemq-cpp-2.2.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.1-src.tar.gz">activemq-cpp-2.2.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.1-src.tar.gz.asc">activemq-cpp-2.2.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.1-src.zip">activemq-cpp-2.2.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.1-src.zip.asc">activemq-cpp-2.2.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.1-src.tar.gz">activemq-cpp-2.2.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.1-src.tar.gz.asc">activemq-cpp-2.2.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.2.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="dd421ae1-6cb0-4b76-98ec-a35cc5a2ee24" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.2.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.2.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11921">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11921">release notes</a><br clear="none">
+<structured-macro ac:macro-id="9892670c-a2d5-45e9-843c-2345863a8714" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11921&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-222-release.xml b/cms/activemq-cpp-222-release.xml
index f3b1258..7cf5cdb 100644
--- a/cms/activemq-cpp-222-release.xml
+++ b/cms/activemq-cpp-222-release.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.2.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor release that contains bugfixes that were found since the<br clear="none">
2.2.1 release. Also in this release the there have been several meory leak<br clear="none">
@@ -7,32 +7,26 @@
see the wiki for the new configuration option documentation. This version<br clear="none">
of the library now requires APR 1.3 or higher to compile.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="eba11f47-f45a-4d44-9a07-d1955bbad13a" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP2.2.2Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.2.2Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.2-src.zip">activemq-cpp-2.2.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.2-src.zip.asc">activemq-cpp-2.2.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.2-src.tar.gz">activemq-cpp-2.2.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.2-src.tar.gz.asc">activemq-cpp-2.2.2-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.2-src.zip">activemq-cpp-2.2.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.2-src.zip.asc">activemq-cpp-2.2.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.2-src.tar.gz">activemq-cpp-2.2.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.2-src.tar.gz.asc">activemq-cpp-2.2.2-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.2.2Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a4d8011d-3dee-4f67-88bb-0b488490498c" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.2.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.2.2Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11931">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11931">release notes</a><br clear="none">
+<structured-macro ac:macro-id="a7c6ff47-2fb0-4e05-af70-2a693dc7c4ec" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11931&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-223-release.xml b/cms/activemq-cpp-223-release.xml
index b56719b..030d139 100644
--- a/cms/activemq-cpp-223-release.xml
+++ b/cms/activemq-cpp-223-release.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.2.3Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor release that contains bugfixes that were found since the<br clear="none">
2.2.2 release. This version adds support for responding to KeepAlive <br clear="none">
@@ -6,32 +6,26 @@
stomp and openwire commands. Users can now delete destinations using the <br clear="none">
deleteDestination function in ActiveMQConnection.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="41459cf1-1a24-4616-9d7e-87665ae4922f" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP2.2.3Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.2.3Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.3-src.zip">activemq-cpp-2.2.3-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.3-src.zip.asc">activemq-cpp-2.2.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.3-src.tar.gz">activemq-cpp-2.2.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.3-src.tar.gz.asc">activemq-cpp-2.2.3-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.3-src.zip">activemq-cpp-2.2.3-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.3-src.zip.asc">activemq-cpp-2.2.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.3-src.tar.gz">activemq-cpp-2.2.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.3-src.tar.gz.asc">activemq-cpp-2.2.3-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.2.3Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="8296f1b9-8f50-4411-b1d7-a5e508b9d85f" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.2.3/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.2.3Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11999">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11999">release notes</a><br clear="none">
+<structured-macro ac:macro-id="7b15074d-ed4d-4379-b161-1cbc133ac0ec" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11999&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-224-release.xml b/cms/activemq-cpp-224-release.xml
index 723d9e8..cf94876 100644
--- a/cms/activemq-cpp-224-release.xml
+++ b/cms/activemq-cpp-224-release.xml
@@ -1,34 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.2.4Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor release that contains bugfixes that were found since the<br clear="none">
2.2.3 release. </p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="66b9a5db-92d7-4b1e-a431-4785615abbce" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP2.2.4Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.2.4Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.4-src.zip">activemq-cpp-2.2.4-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.4-src.zip.asc">activemq-cpp-2.2.4-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.4-src.tar.gz">activemq-cpp-2.2.4-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.4-src.tar.gz.asc">activemq-cpp-2.2.4-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.4-src.zip">activemq-cpp-2.2.4-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.4-src.zip.asc">activemq-cpp-2.2.4-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.4-src.tar.gz">activemq-cpp-2.2.4-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.4-src.tar.gz.asc">activemq-cpp-2.2.4-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.2.4Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="77d73e43-0037-42c8-bd42-cf07619cfbf6" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.2.4/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.2.4Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12000">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12000">release notes</a><br clear="none">
+<structured-macro ac:macro-id="cbd6a6bd-d72a-4b17-b27d-a9415c19b4d5" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=12000&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-225-release.xml b/cms/activemq-cpp-225-release.xml
index db8765f..6ac744b 100644
--- a/cms/activemq-cpp-225-release.xml
+++ b/cms/activemq-cpp-225-release.xml
@@ -1,34 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.2.5Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor release that contains bugfixes that were found since the<br clear="none">
2.2.4 release. </p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="c2470b9d-21a5-4610-9e4f-c8ca1595e932" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP2.2.5Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.2.5Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.5-src.zip">activemq-cpp-2.2.5-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.5-src.zip.asc">activemq-cpp-2.2.5-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.5-src.tar.gz">activemq-cpp-2.2.5-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.5-src.tar.gz.asc">activemq-cpp-2.2.5-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.5-src.zip">activemq-cpp-2.2.5-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.5-src.zip.asc">activemq-cpp-2.2.5-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.5-src.tar.gz">activemq-cpp-2.2.5-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.5-src.tar.gz.asc">activemq-cpp-2.2.5-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.2.5Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d3e69697-5aa9-4192-9470-eaacde74c922" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.2.5/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.2.5Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12060">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12060">release notes</a><br clear="none">
+<structured-macro ac:macro-id="64125340-9ef9-4164-a118-84f135fd8a28" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=12060&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-226-release.xml b/cms/activemq-cpp-226-release.xml
index 0e84c27..080f111 100644
--- a/cms/activemq-cpp-226-release.xml
+++ b/cms/activemq-cpp-226-release.xml
@@ -1,36 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP2.2.6Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor release that contains bugfixes that were found since the<br clear="none">
2.2.5 release. Most noteably the code now properly encodes the strings <br clear="none">
sent in text message's and as properties in any message as proper modified <br clear="none">
UTF-8 encoded string's. </p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="b2f97b90-0ab2-49ba-8c8b-ebc0b7fd6548" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP2.2.6Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-2.2.1">here</a></p>
-<h2 id="ActiveMQ-CPP2.2.6Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.6-src.zip">activemq-cpp-2.2.6-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.6-src.zip.asc">activemq-cpp-2.2.6-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.6-src.tar.gz">activemq-cpp-2.2.6-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.6-src.tar.gz.asc">activemq-cpp-2.2.6-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.6-src.zip">activemq-cpp-2.2.6-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.6-src.zip.asc">activemq-cpp-2.2.6-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-2.2.6-src.tar.gz">activemq-cpp-2.2.6-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-2.2.6-src.tar.gz.asc">activemq-cpp-2.2.6-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP2.2.6Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1912ddad-e337-4336-8d82-391a69897b90" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-2.2.6/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP2.2.6Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12109">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12109">release notes</a><br clear="none">
+<structured-macro ac:macro-id="a7fea867-a2d8-452c-abbb-925886276b15" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=12109&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-30-release.xml b/cms/activemq-cpp-30-release.xml
index 10c9b35..1bdc050 100644
--- a/cms/activemq-cpp-30-release.xml
+++ b/cms/activemq-cpp-30-release.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>The 3.0 release is a major update the to ActiveMQ-CPP client code, many areas have been rewritten to enhance performance and improve stability. The following are some highlights of this release:</p>
@@ -6,34 +6,28 @@
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="a39979c7-1526-4e8e-9572-aa1327fd99ed" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 1.3 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.0-src.zip">activemq-cpp-library-3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.0-src.zip.asc">activemq-cpp-library-3.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.0-src.tar.gz">activemq-cpp-library-3.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.0-src.tar.gz.asc">activemq-cpp-library-3.0-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.0-src.zip">activemq-cpp-library-3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.0-src.zip.asc">activemq-cpp-library-3.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.0-src.tar.gz">activemq-cpp-library-3.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.0-src.tar.gz.asc">activemq-cpp-library-3.0-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="260761a2-8c07-4012-adc9-dae7adcd3bc8" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11998">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=11998">release notes</a><br clear="none">
+<structured-macro ac:macro-id="ee979692-70a7-468b-9409-b1a2c39f2be8" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=11998&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-301-release.xml b/cms/activemq-cpp-301-release.xml
index c09383e..915a70a 100644
--- a/cms/activemq-cpp-301-release.xml
+++ b/cms/activemq-cpp-301-release.xml
@@ -1,35 +1,29 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.0.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a bugfix release that mainly addresses problems found in the Failover support added in the initial 3.0 release.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="006942ec-1cbc-4692-938b-649034557ba7" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.0.1Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 1.3 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.0.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.0.1-src.zip">activemq-cpp-library-3.0.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.0.1-src.zip.asc">activemq-cpp-library-3.0.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.0.1-src.tar.gz">activemq-cpp-library-3.0.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.0.1-src.tar.gz.asc">activemq-cpp-library-3.0.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.0.1-src.zip">activemq-cpp-library-3.0.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.0.1-src.zip.asc">activemq-cpp-library-3.0.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.0.1-src.tar.gz">activemq-cpp-library-3.0.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.0.1-src.tar.gz.asc">activemq-cpp-library-3.0.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.0.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2cb51d55-619b-49cb-85cd-e49d82b00329" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.0.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.0.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12141">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12141">release notes</a><br clear="none">
+<structured-macro ac:macro-id="d5bac1ae-b8c3-496f-90ff-c0dc6d71e951" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11000&fixfor=12141&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/cms/activemq-cpp-310-release.xml b/cms/activemq-cpp-310-release.xml
index 6c06bb6..26c82a5 100644
--- a/cms/activemq-cpp-310-release.xml
+++ b/cms/activemq-cpp-310-release.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.1.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a new Major release of ActiveMQ-CPP. Many new features have been added<br clear="none">
and several bugs have been fixed. The client now has an connection Inactivity<br clear="none">
@@ -7,30 +7,27 @@
memory usage, and there have been several other performance improvements added<br clear="none">
throughout the code-base.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="c850d3bf-8b71-453e-a04e-b5a42523b359" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.1.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.1 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.1.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.0-src.zip">activemq-cpp-library-3.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.0-src.zip.asc">activemq-cpp-library-3.1.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.0-src.tar.gz">activemq-cpp-library-3.1.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.0-src.tar.gz.asc">activemq-cpp-library-3.1.0-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.0-src.zip">activemq-cpp-library-3.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.0-src.zip.asc">activemq-cpp-library-3.1.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.0-src.tar.gz">activemq-cpp-library-3.1.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.0-src.tar.gz.asc">activemq-cpp-library-3.1.0-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.1.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ba2bcb1b-5f57-45b7-bac9-4dba1abce57b" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.1.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.1.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12070">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12070">release notes</a></p></div>
diff --git a/cms/activemq-cpp-311-release.xml b/cms/activemq-cpp-311-release.xml
index 3e613e5..a048b25 100644
--- a/cms/activemq-cpp-311-release.xml
+++ b/cms/activemq-cpp-311-release.xml
@@ -1,31 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.1.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a bug fix release that resolves several memory leaks found since the 3.1 release. Also a few small issues with some compilers was addressed.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="e356b887-a8b6-4319-b0b9-a4f8d322c261" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.1.1Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.1 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.1.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.1-src.zip">activemq-cpp-library-3.1.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.1-src.zip.asc">activemq-cpp-library-3.1.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.1-src.tar.gz">activemq-cpp-library-3.1.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.1-src.tar.gz.asc">activemq-cpp-library-3.1.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.1-src.zip">activemq-cpp-library-3.1.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.1-src.zip.asc">activemq-cpp-library-3.1.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.1-src.tar.gz">activemq-cpp-library-3.1.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.1-src.tar.gz.asc">activemq-cpp-library-3.1.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.1.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="515f89ec-f112-4c06-8952-2c268b9daffe" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.1.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.1.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12190">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12190">release notes</a></p></div>
diff --git a/cms/activemq-cpp-312-release.xml b/cms/activemq-cpp-312-release.xml
index 85c9fdd..7a22674 100644
--- a/cms/activemq-cpp-312-release.xml
+++ b/cms/activemq-cpp-312-release.xml
@@ -1,31 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.1.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a bug fix release that resolves several crash bugs found since the 3.1.1 release. Also a few small issues with some compilers was addressed.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="3db19e4b-4cf3-427a-81b8-4fd4ff4e0547" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.1.2Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.1 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.1.2Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.2-src.zip">activemq-cpp-library-3.1.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.2-src.zip.asc">activemq-cpp-library-3.1.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.2-src.tar.gz">activemq-cpp-library-3.1.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.2-src.tar.gz.asc">activemq-cpp-library-3.1.2-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.2-src.zip">activemq-cpp-library-3.1.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.2-src.zip.asc">activemq-cpp-library-3.1.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.2-src.tar.gz">activemq-cpp-library-3.1.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.2-src.tar.gz.asc">activemq-cpp-library-3.1.2-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.1.2Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5ee36097-dd01-44bf-9b11-6bd10b8f6e1b" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.1.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.1.2Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12260">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12260">release notes</a></p></div>
diff --git a/cms/activemq-cpp-313-release.xml b/cms/activemq-cpp-313-release.xml
index 9690df7..b1f6fe0 100644
--- a/cms/activemq-cpp-313-release.xml
+++ b/cms/activemq-cpp-313-release.xml
@@ -1,31 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.1.3Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a bug fix release that resolves an issue on Windows that could lead to deadlocks.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="765ffeda-1817-40aa-ba52-ca6f5ef04fb1" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.1.3Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.1 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.1.3Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.3-src.zip">activemq-cpp-library-3.1.3-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.3-src.zip.asc">activemq-cpp-library-3.1.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.3-src.tar.gz">activemq-cpp-library-3.1.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.3-src.tar.gz.asc">activemq-cpp-library-3.1.3-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.3-src.zip">activemq-cpp-library-3.1.3-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.3-src.zip.asc">activemq-cpp-library-3.1.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.1.3-src.tar.gz">activemq-cpp-library-3.1.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.1.3-src.tar.gz.asc">activemq-cpp-library-3.1.3-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.1.3Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="fb3d51cd-4d0b-4f69-ab2a-03453116fe6f" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.1.3/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.1.3Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12291">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12291">release notes</a></p></div>
diff --git a/cms/activemq-cpp-320-release.xml b/cms/activemq-cpp-320-release.xml
index 712a550..12fb9b0 100644
--- a/cms/activemq-cpp-320-release.xml
+++ b/cms/activemq-cpp-320-release.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.2.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a major update for the ActiveMQ-CPP library adding in support for SSL, QueueBrowser, Message compression and more. Many issues have been addressed as well as work to improve performance and prevent memory leaks. </p>
<p>The SSL support makes use of the OpenSSL libraries so you need them installed to use it. </p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="15ca9364-fb04-4409-b55a-46d178f19fd6" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.2.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.2.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.0-src.zip">activemq-cpp-library-3.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.0-src.zip.asc">activemq-cpp-library-3.2.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.0-src.tar.gz">activemq-cpp-library-3.2.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.0-src.tar.gz.asc">activemq-cpp-library-3.2.0-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.0-src.zip">activemq-cpp-library-3.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.0-src.zip.asc">activemq-cpp-library-3.2.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.0-src.tar.gz">activemq-cpp-library-3.2.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.0-src.tar.gz.asc">activemq-cpp-library-3.2.0-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.2.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1df56e26-ad59-40aa-961e-f2028ce61bcb" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.2.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.2.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12191">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12191">release notes</a></p></div>
diff --git a/cms/activemq-cpp-321-release.xml b/cms/activemq-cpp-321-release.xml
index f9322de..7d10f00 100644
--- a/cms/activemq-cpp-321-release.xml
+++ b/cms/activemq-cpp-321-release.xml
@@ -1,31 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.2.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release that addresses issues with the original 3.2.0 release for users on Windows,</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="43142ce7-f083-4efd-9ff2-2429c82c6321" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.2.1Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.2.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.1-src.zip">activemq-cpp-library-3.2.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.1-src.zip.asc">activemq-cpp-library-3.2.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.1-src.tar.gz">activemq-cpp-library-3.2.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.1-src.tar.gz.asc">activemq-cpp-library-3.2.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.1-src.zip">activemq-cpp-library-3.2.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.1-src.zip.asc">activemq-cpp-library-3.2.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.1-src.tar.gz">activemq-cpp-library-3.2.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.1-src.tar.gz.asc">activemq-cpp-library-3.2.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.2.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d74cb088-6f10-40be-af00-979be64b545d" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.2.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.2.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12333">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12333">release notes</a></p></div>
diff --git a/cms/activemq-cpp-322-release.xml b/cms/activemq-cpp-322-release.xml
index 7ce5872..d73efab 100644
--- a/cms/activemq-cpp-322-release.xml
+++ b/cms/activemq-cpp-322-release.xml
@@ -1,31 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.2.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release that addresses issues with the 3.2.1 release. Several issues that users were seeing as segfaults from APR Atomics have been addressed as well as a fix for sending and receiving empty MapMessages.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="4f5e1a37-b4e0-4998-8668-79c5c6a48ba1" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.2.2Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.2.2Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.2-src.zip">activemq-cpp-library-3.2.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.2-src.zip.asc">activemq-cpp-library-3.2.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.2-src.tar.gz">activemq-cpp-library-3.2.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.2-src.tar.gz.asc">activemq-cpp-library-3.2.2-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.2-src.zip">activemq-cpp-library-3.2.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.2-src.zip.asc">activemq-cpp-library-3.2.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.2-src.tar.gz">activemq-cpp-library-3.2.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.2-src.tar.gz.asc">activemq-cpp-library-3.2.2-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.2.2Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="36d70e14-c0b4-4585-84e4-0673dfd1f677" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.2.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.2.2Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12336">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12336">release notes</a></p></div>
diff --git a/cms/activemq-cpp-323-release.xml b/cms/activemq-cpp-323-release.xml
index 9754034..3d7efe9 100644
--- a/cms/activemq-cpp-323-release.xml
+++ b/cms/activemq-cpp-323-release.xml
@@ -1,31 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.2.3Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release that addresses issues with the 3.2.2 release. This release fixes an additional issue found in unmarshaling MapMessage objects on Windows as well as fixing a threading issue that causes invalid client Ids to be generated if two connections were created from two different threads at the same time. Also a fix to the pkg-config file that is generated for the build was added.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="922e3741-b91b-481c-8c7c-9285d8b4d882" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.2.3Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.2.3Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.3-src.zip">activemq-cpp-library-3.2.3-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.3-src.zip.asc">activemq-cpp-library-3.2.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.3-src.tar.gz">activemq-cpp-library-3.2.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.3-src.tar.gz.asc">activemq-cpp-library-3.2.3-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.3-src.zip">activemq-cpp-library-3.2.3-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.3-src.zip.asc">activemq-cpp-library-3.2.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.3-src.tar.gz">activemq-cpp-library-3.2.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.3-src.tar.gz.asc">activemq-cpp-library-3.2.3-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.2.3Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="27ee1521-47f4-46f0-950b-ad9db75cc069" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.2.3/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.2.3Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12338">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="http://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11000&styleName=Html&version=12338">release notes</a></p></div>
diff --git a/cms/activemq-cpp-324-release.xml b/cms/activemq-cpp-324-release.xml
index 539986e..7ac1e5f 100644
--- a/cms/activemq-cpp-324-release.xml
+++ b/cms/activemq-cpp-324-release.xml
@@ -1,31 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.2.4Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release that addresses issues with the 3.2.3 release. This release fixes an issue with the Stomp support as well as addressing some problems in the CMSTemplate classes.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="6a911d9f-6db7-4ab9-96a3-61f6c9b08f77" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.2.4Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.0">here</a></p>
-<h2 id="ActiveMQ-CPP3.2.4Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.4-src.zip">activemq-cpp-library-3.2.4-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.4-src.zip.asc">activemq-cpp-library-3.2.4-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.4-src.tar.gz">activemq-cpp-library-3.2.4-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.4-src.tar.gz.asc">activemq-cpp-library-3.2.4-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.4-src.zip">activemq-cpp-library-3.2.4-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.4-src.zip.asc">activemq-cpp-library-3.2.4-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.4-src.tar.gz">activemq-cpp-library-3.2.4-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.4-src.tar.gz.asc">activemq-cpp-library-3.2.4-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.2.4Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="dd07a595-d994-4acf-9971-29356b0ab0d7" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.2.4/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.2.4Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12315667">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12315667">release notes</a></p></div>
diff --git a/cms/activemq-cpp-325-release.xml b/cms/activemq-cpp-325-release.xml
index 958ff04..9fd7ead 100644
--- a/cms/activemq-cpp-325-release.xml
+++ b/cms/activemq-cpp-325-release.xml
@@ -1,31 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.2.5Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release that addresses issues with the 3.2.4 release. This release fixes a bug that was causing the client to segfault on Mac OS as well as fixing an issue with the SSL transport and X509v3 Certificates. Several small issues with URI parsing have also been fixed.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="cee29dff-51fb-4423-b691-2558e8ee2913" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.2.5Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.2.5/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.2.5/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.2.5Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.5-src.zip">activemq-cpp-library-3.2.5-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.5-src.zip.asc">activemq-cpp-library-3.2.5-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.5-src.tar.gz">activemq-cpp-library-3.2.5-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.5-src.tar.gz.asc">activemq-cpp-library-3.2.5-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.5-src.zip">activemq-cpp-library-3.2.5-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.5-src.zip.asc">activemq-cpp-library-3.2.5-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.2.5-src.tar.gz">activemq-cpp-library-3.2.5-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.2.5-src.tar.gz.asc">activemq-cpp-library-3.2.5-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.2.5Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="95657f19-8048-4820-9065-e103618627af" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.2.5/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.2.5Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12316124">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12316124">release notes</a></p></div>
diff --git a/cms/activemq-cpp-330-release.xml b/cms/activemq-cpp-330-release.xml
index 690178c..821da43 100644
--- a/cms/activemq-cpp-330-release.xml
+++ b/cms/activemq-cpp-330-release.xml
@@ -1,35 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.3.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a major release of the ActiveMQ-CPP client which includes some API changes and several new features and improvements. Some additional methods have been added to the CMS API to make it easier to use. Some highlights for this release:</p>
<ul><li>Solved some deadlock issues that could occur during failover when using asynchronous consumers.</li><li>Synchronous Consumers now get an exception if they call receive when the Connection has failed.</li><li>CMS API now provides an XA domain for linking the CMS client into XA transactions.</li><li>The Failover Transport now supports the connection rebalancing feature in ActiveMQ.</li><li>Fixes in the Stomp handling allow the client to work with ActiveMQ Apollo.</li><li>Better message redelivery processing for Transacted consumers.</li></ul>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="14a44314-e431-4e8d-ac43-efa8e1ff3ae5" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.3.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.3.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.3.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.3.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.zip">activemq-cpp-library-3.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.zip.asc">activemq-cpp-library-3.3.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.tar.gz">activemq-cpp-library-3.3.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.tar.gz.asc">activemq-cpp-library-3.3.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.tar.bz2">activemq-cpp-library-3.3.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.tar.bz2.asc">activemq-cpp-library-3.3.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.zip">activemq-cpp-library-3.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.zip.asc">activemq-cpp-library-3.3.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.tar.gz">activemq-cpp-library-3.3.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.tar.gz.asc">activemq-cpp-library-3.3.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.tar.bz2">activemq-cpp-library-3.3.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.3.0-src.tar.bz2.asc">activemq-cpp-library-3.3.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.3.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4f6fde0b-9b1b-488c-a296-2c7ca8c304ff" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.3.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.3.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12315668">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12315668">release notes</a></p></div>
diff --git a/cms/activemq-cpp-340-release.xml b/cms/activemq-cpp-340-release.xml
index 86ce853..f00a36b 100644
--- a/cms/activemq-cpp-340-release.xml
+++ b/cms/activemq-cpp-340-release.xml
@@ -1,35 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.4.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a major release of the ActiveMQ-CPP client which includes some API changes and several improvements. Some additional methods have been added to the CMS API to make it easier to use. Some highlights for this release:</p>
<ul><li>Added start and stop methods to CMS Session and MessageConsumer.</li><li>Fixed some build issues on Windows.</li><li>Resolved some issues with failover not recovering consumers correctly.</li><li>Fixed some problems with URI parsing.</li></ul>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="f7bd2097-0ac9-4cf7-a683-09a1ce5fbad9" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.4.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.4 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.4.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.zip">activemq-cpp-library-3.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.zip.asc">activemq-cpp-library-3.4.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.tar.gz">activemq-cpp-library-3.4.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.tar.gz.asc">activemq-cpp-library-3.4.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.tar.bz2">activemq-cpp-library-3.4.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.tar.bz2.asc">activemq-cpp-library-3.4.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.zip">activemq-cpp-library-3.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.zip.asc">activemq-cpp-library-3.4.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.tar.gz">activemq-cpp-library-3.4.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.tar.gz.asc">activemq-cpp-library-3.4.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.tar.bz2">activemq-cpp-library-3.4.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.0-src.tar.bz2.asc">activemq-cpp-library-3.4.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.4.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="fdc9cfd7-2cae-456b-a977-884079ac1e31" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.4.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.4.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12316372">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12316372">release notes</a></p></div>
diff --git a/cms/activemq-cpp-341-release.xml b/cms/activemq-cpp-341-release.xml
index a7f6f56..5490608 100644
--- a/cms/activemq-cpp-341-release.xml
+++ b/cms/activemq-cpp-341-release.xml
@@ -1,35 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.4.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release of the ActiveMQ-CPP client which includes some fixes for issues found since the v3.4.0 release. </p>
<ul><li>Implements the Session recover method.</li><li>Fixed some build issues on Mac with dynamic libs.</li><li>Fixed an issue with BytesMessage marshaling when compression is enabled.</li><li>Fixed an issue on Windows with some unmarshaling cases causing a crash.</li><li>A few other minor package and build fixes.</li></ul>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="1606fed1-5993-4056-81de-1eb701ba9195" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.4.1Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.4 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.4.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.zip">activemq-cpp-library-3.4.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.zip.asc">activemq-cpp-library-3.4.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.tar.gz">activemq-cpp-library-3.4.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.tar.gz.asc">activemq-cpp-library-3.4.1-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.tar.bz2">activemq-cpp-library-3.4.1-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.tar.bz2.asc">activemq-cpp-library-3.4.1-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.zip">activemq-cpp-library-3.4.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.zip.asc">activemq-cpp-library-3.4.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.tar.gz">activemq-cpp-library-3.4.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.tar.gz.asc">activemq-cpp-library-3.4.1-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.tar.bz2">activemq-cpp-library-3.4.1-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.1-src.tar.bz2.asc">activemq-cpp-library-3.4.1-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.4.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6c088493-4ee0-498f-83ef-4d689c7711d2" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.4.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.4.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12316381">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12316381">release notes</a></p></div>
diff --git a/cms/activemq-cpp-342-release.xml b/cms/activemq-cpp-342-release.xml
index fe53ef7..73e45f7 100644
--- a/cms/activemq-cpp-342-release.xml
+++ b/cms/activemq-cpp-342-release.xml
@@ -1,35 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.4.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release of the ActiveMQ-CPP client which includes some fixes for issues found since the v3.4.1 release. </p>
<ul><li>Some build issues on various platforms were resolved.</li><li>A problem with setting the username / password from the Connection Factory was fixed.</li><li>A problem with expired messages and DLQ processing was addressed.</li><li>An issue with the failover transport and hangs in Connection start() was fixed.</li><li>A couple of race conditions on Connection close() were addressed.</li></ul>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="9c75d284-e25b-4c1d-8ed6-06d35c0b2752" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.4.2Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.4 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.4.2Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.zip">activemq-cpp-library-3.4.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.zip.asc">activemq-cpp-library-3.4.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.tar.gz">activemq-cpp-library-3.4.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.tar.gz.asc">activemq-cpp-library-3.4.2-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.tar.bz2">activemq-cpp-library-3.4.2-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.tar.bz2.asc">activemq-cpp-library-3.4.2-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.zip">activemq-cpp-library-3.4.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.zip.asc">activemq-cpp-library-3.4.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.tar.gz">activemq-cpp-library-3.4.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.tar.gz.asc">activemq-cpp-library-3.4.2-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.tar.bz2">activemq-cpp-library-3.4.2-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.2-src.tar.bz2.asc">activemq-cpp-library-3.4.2-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.4.2Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b4a28b0a-97b0-4958-82e2-f7d22b60e523" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.4.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.4.2Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12319269">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12319269">release notes</a></p></div>
diff --git a/cms/activemq-cpp-343-release.xml b/cms/activemq-cpp-343-release.xml
index 661a710..eba5e5b 100644
--- a/cms/activemq-cpp-343-release.xml
+++ b/cms/activemq-cpp-343-release.xml
@@ -1,32 +1,29 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.4.3Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release of the ActiveMQ-CPP client which includes some fixes for issues found since the v3.4.2 release. This release resolves some memory leaks found in the prior 3.4.x releases in the TCP transport and in the use of Transactions for producers.</p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="05c464d4-8dcb-446f-a725-547c94be3b1e" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.4.3Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.4 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.4.3Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.zip">activemq-cpp-library-3.4.3-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.zip.asc">activemq-cpp-library-3.4.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.tar.gz">activemq-cpp-library-3.4.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.tar.gz.asc">activemq-cpp-library-3.4.3-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.tar.bz2">activemq-cpp-library-3.4.3-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.tar.bz2.asc">activemq-cpp-library-3.4.3-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.zip">activemq-cpp-library-3.4.3-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.zip.asc">activemq-cpp-library-3.4.3-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.tar.gz">activemq-cpp-library-3.4.3-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.tar.gz.asc">activemq-cpp-library-3.4.3-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.tar.bz2">activemq-cpp-library-3.4.3-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.3-src.tar.bz2.asc">activemq-cpp-library-3.4.3-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.4.3Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5028df99-e1dd-4bf4-9e96-47f9dd150adc" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.4.3/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.4.3Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12321240">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12321240">release notes</a></p></div>
diff --git a/cms/activemq-cpp-344-release.xml b/cms/activemq-cpp-344-release.xml
index 370e1cc..649be5b 100644
--- a/cms/activemq-cpp-344-release.xml
+++ b/cms/activemq-cpp-344-release.xml
@@ -1,32 +1,29 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.4.4Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release of the ActiveMQ-CPP client which includes some fixes for issues found since the v3.4.3 release. This release resolves some memory and thread leaks found in the prior 3.4.x releases having to do with Connection shutdown. Also the Windows project files are cleaned up a bit. </p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="8022618d-5a89-4e38-bda1-e28df001f7a8" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.4.4Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.4 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.4.4Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.zip">activemq-cpp-library-3.4.4-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.zip.asc">activemq-cpp-library-3.4.4-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.tar.gz">activemq-cpp-library-3.4.4-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.tar.gz.asc">activemq-cpp-library-3.4.4-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.tar.bz2">activemq-cpp-library-3.4.4-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.tar.bz2.asc">activemq-cpp-library-3.4.4-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.zip">activemq-cpp-library-3.4.4-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.zip.asc">activemq-cpp-library-3.4.4-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.tar.gz">activemq-cpp-library-3.4.4-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.tar.gz.asc">activemq-cpp-library-3.4.4-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.tar.bz2">activemq-cpp-library-3.4.4-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.4-src.tar.bz2.asc">activemq-cpp-library-3.4.4-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.4.4Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="840acb7b-d8f1-4c82-ad90-f49f9f242d8a" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.4.4/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.4.4Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12321703">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12321703">release notes</a></p></div>
diff --git a/cms/activemq-cpp-345-release.xml b/cms/activemq-cpp-345-release.xml
index 233d15c..9f43c23 100644
--- a/cms/activemq-cpp-345-release.xml
+++ b/cms/activemq-cpp-345-release.xml
@@ -1,32 +1,29 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.4.5Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a patch release of ActiveMQ-CPP that fixes several issues found since the v3.4.4 release. This release contains fixes for memory leaks that can occur when a socket connection is broken during a message marshal or unmarshal as well as fixes for some exceptions that were not being handled correctly internally in the Connection class. Also a fix the STOMP messages and correlation-id are in this release. </p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="e4ad3e7b-9426-4364-ae2a-c762996b63b0" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.4.5Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.4 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.4.5Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.zip">activemq-cpp-library-3.4.5-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.zip.asc">activemq-cpp-library-3.4.5-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.tar.gz">activemq-cpp-library-3.4.5-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.tar.gz.asc">activemq-cpp-library-3.4.5-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.tar.bz2">activemq-cpp-library-3.4.5-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.tar.bz2.asc">activemq-cpp-library-3.4.5-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.zip">activemq-cpp-library-3.4.5-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.zip.asc">activemq-cpp-library-3.4.5-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.tar.gz">activemq-cpp-library-3.4.5-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.tar.gz.asc">activemq-cpp-library-3.4.5-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.tar.bz2">activemq-cpp-library-3.4.5-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.4.5-src.tar.bz2.asc">activemq-cpp-library-3.4.5-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.4.5Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3759455c-cc45-4731-9b63-ff88974acf63" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.4.5/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.4.5Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12323248">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12323248">release notes</a></p></div>
diff --git a/cms/activemq-cpp-350-release.xml b/cms/activemq-cpp-350-release.xml
index 8f82e35..f2e5a5e 100644
--- a/cms/activemq-cpp-350-release.xml
+++ b/cms/activemq-cpp-350-release.xml
@@ -1,35 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.5.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a new Major release of ActiveMQ-CPP with several new APIs and internal changes meant to improve overall stability of the C++ client. Besides a large amount of bug fixing and memory fixing this release also features a lot of new features in the CMS API:</p>
<ul><li>Added Message Transformation capabilities for incoming and outgoing messages.</li><li>You can now query for the type of a Message property so you can choose the best getter method.</li><li>MapMessage and StreamMessage object now expose an API to find out what type a value is before you try to get a value using one of the getter methods.</li><li>Polling consumers now can set a Message available listener.</li><li>Stomp clients can configure the destination prefixes for the Destination types (Queues, Topics...).</li><li>StreamMessage now has a reset method to allow object reuse.</li><li>Added an AdvisorySupport class to make dealing with advisory topics easier.</li><li>Added support for non-blocking sends to Message Producers.</li></ul>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="b9760e39-9635-4e7e-bc0c-2d1c72332201" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.5.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 2.4 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.4.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.5.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.zip">activemq-cpp-library-3.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.zip.asc">activemq-cpp-library-3.5.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.tar.gz">activemq-cpp-library-3.5.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.tar.gz.asc">activemq-cpp-library-3.5.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.tar.bz2">activemq-cpp-library-3.5.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.tar.bz2.asc">activemq-cpp-library-3.5.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.zip">activemq-cpp-library-3.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.zip.asc">activemq-cpp-library-3.5.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.tar.gz">activemq-cpp-library-3.5.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.tar.gz.asc">activemq-cpp-library-3.5.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.tar.bz2">activemq-cpp-library-3.5.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.5.0-src.tar.bz2.asc">activemq-cpp-library-3.5.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.5.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="678985c1-2a8a-47e0-a148-4ee9a30a20a1" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.5.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.5.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12316380">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12316380">release notes</a></p></div>
diff --git a/cms/activemq-cpp-360-release.xml b/cms/activemq-cpp-360-release.xml
index 5a7ac84..5def1ca 100644
--- a/cms/activemq-cpp-360-release.xml
+++ b/cms/activemq-cpp-360-release.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.6.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a new Major release of ActiveMQ-CPP, a lot of bugs have been fixed that were found in the v3.5.0 release which should reduce memory consumption and improve overall stability. </p>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="92c7af68-d10b-4c21-bc04-8d24664d2555" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.6.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 3.1 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.6.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.zip">activemq-cpp-library-3.6.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.zip.asc">activemq-cpp-library-3.6.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.tar.gz">activemq-cpp-library-3.6.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.tar.gz.asc">activemq-cpp-library-3.6.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.tar.bz2">activemq-cpp-library-3.6.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.tar.bz2.asc">activemq-cpp-library-3.6.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.zip">activemq-cpp-library-3.6.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.zip.asc">activemq-cpp-library-3.6.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.tar.gz">activemq-cpp-library-3.6.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.tar.gz.asc">activemq-cpp-library-3.6.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.tar.bz2">activemq-cpp-library-3.6.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.6.0-src.tar.bz2.asc">activemq-cpp-library-3.6.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.6.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a5e80eca-b60f-450c-ab57-dbba4e03122c" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.6.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.6.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12323973">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12323973">release notes</a></p></div>
diff --git a/cms/activemq-cpp-370-release.xml b/cms/activemq-cpp-370-release.xml
index 1b08381..4bc153e 100644
--- a/cms/activemq-cpp-370-release.xml
+++ b/cms/activemq-cpp-370-release.xml
@@ -1,35 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.7.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a new Major release of ActiveMQ-CPP, a lot of bugs have been fixed that were found in the v3.6.0 release which should reduce memory consumption and improve overall stability. Some new features have been added as well. </p>
<ul><li>Added support of Optimized Acknowledge</li><li>Added support for Non-blocking redelivery.</li><li>Removed dependence on the APR-Util library.</li><li>Supports priority backup for Failover Transport</li><li>Supports the cluster rebalancing feature.</li><li>Message Audits to filter duplicates on Failover.</li><li>A lot of other little bug fixes and improvements.</li></ul>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="fc16e21a-a443-4421-a462-159b1ebfcf11" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.7.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 3.1 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.7.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.7.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.7.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.zip">activemq-cpp-library-3.7.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.zip.asc">activemq-cpp-library-3.7.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.tar.gz">activemq-cpp-library-3.7.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.tar.gz.asc">activemq-cpp-library-3.7.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.tar.bz2">activemq-cpp-library-3.7.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.tar.bz2.asc">activemq-cpp-library-3.7.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.zip">activemq-cpp-library-3.7.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.zip.asc">activemq-cpp-library-3.7.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.tar.gz">activemq-cpp-library-3.7.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.tar.gz.asc">activemq-cpp-library-3.7.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.tar.bz2">activemq-cpp-library-3.7.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.0-src.tar.bz2.asc">activemq-cpp-library-3.7.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.7.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f49a8eac-35df-4f38-9f87-ef0aa2dafb79" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.7.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.7.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324161">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324161">release notes</a></p></div>
diff --git a/cms/activemq-cpp-371-release.xml b/cms/activemq-cpp-371-release.xml
index 2b1d34c..c308873 100644
--- a/cms/activemq-cpp-371-release.xml
+++ b/cms/activemq-cpp-371-release.xml
@@ -1,33 +1,31 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.7.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a new patch release of ActiveMQ-CPP, a lot of bugs have been fixed that were found in the v3.7.0 release which should reduce memory consumption and improve overall stability. Several compilation fixes were made as well so things should be better on a number of platforms. Fixes of note:</p>
<ul><li>3.7.0 does not compile with gcc-4.4.7 on CentOS-6</li><li>APR-Util header include missed in latest release.</li><li>CMS FailoverTransport Leaks Socket Descriptors</li><li>closing a connection stalled in start because of failover should stop the transport safely.</li><li>Compilation Error Fix for Sun Studio under Solaris 10</li><li>Exception lifetime confusion can cause the application to crash</li><li>Connection didn't switch to the slave broker when the master broker is down</li><li>Commiting a session with a deleted consumer causes access violation</li><li>Compilation of 3.7.0 fails for Linux systems (Redhat 5.8 and SuSE SLES 10)</li><li>Cient doesn't work on Linux Red Hat 6.4 systems, fails when setting thread priority</li></ul>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="f30d409a-d3b4-4d3a-9be0-75595f2b9241" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.7.1Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 3.1 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.7.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.zip">activemq-cpp-library-3.7.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.zip.asc">activemq-cpp-library-3.7.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.tar.gz">activemq-cpp-library-3.7.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.tar.gz.asc">activemq-cpp-library-3.7.1-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.tar.bz2">activemq-cpp-library-3.7.1-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.tar.bz2.asc">activemq-cpp-library-3.7.1-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.zip">activemq-cpp-library-3.7.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.zip.asc">activemq-cpp-library-3.7.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.tar.gz">activemq-cpp-library-3.7.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.tar.gz.asc">activemq-cpp-library-3.7.1-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.tar.bz2">activemq-cpp-library-3.7.1-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.7.1-src.tar.bz2.asc">activemq-cpp-library-3.7.1-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.7.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.7.1/">https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.7.1/</a></p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="6c37c90d-b6c3-481f-ab12-70006a81046c" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.7.1/">https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/activemq-cpp-3.7.1/</a></p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.7.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324543">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324543">release notes</a></p></div>
diff --git a/cms/activemq-cpp-380-release.xml b/cms/activemq-cpp-380-release.xml
index 06b49b8..5e6ad83 100644
--- a/cms/activemq-cpp-380-release.xml
+++ b/cms/activemq-cpp-380-release.xml
@@ -1,34 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.8.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a new major release of ActiveMQ-CPP, a few bugs have been fixed that were found in the v3.7.0 and v3.7.1 releases which should reduce memory consumption and improve overall stability. Several compilation fixes were made as well so things should be better on a number of platforms. Also some new APIs were added to the CMS API to provide an event based construct to listen for addition and removal of destinations on the Broker. Fixes of note:</p>
<ul><li>3.7.0 does not compile with gcc-4.4.7 on CentOS-6</li><li>APR-Util header include missed in latest release.</li><li>CMS FailoverTransport Leaks Socket Descriptors</li><li>closing a connection stalled in start because of failover should stop the transport safely.</li><li>Compilation Error Fix for Sun Studio under Solaris 10</li><li>Exception lifetime confusion can cause the application to crash</li><li>Connection didn't switch to the slave broker when the master broker is down</li><li>Commiting a session with a deleted consumer causes access violation</li><li>Compilation of 3.7.0 fails for Linux systems (Redhat 5.8 and SuSE SLES 10)</li><li>Cient doesn't work on Linux Red Hat 6.4 systems, fails when setting thread priority</li><li>Exception "attempt to unlock read lock, not locked by current thread" when doing performance testing</li><li>For SSL connections ensure the SNI field is set.</li><li>Can't send to temporary queues created by name</li><li>Added Visual Studio 2010 project files for the project.</li><li>Added Destination Source events based listener interfaces to the CMS API.</li></ul>
-<p><br clear="none" class="atl-forced-newline"></p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<p><br clear="none" class="atl-forced-newline"><structured-macro ac:macro-id="d1d5aa7a-14d6-43ae-95b8-310cb735092e" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro></p>
-<h2 id="ActiveMQ-CPP3.8.0Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 3.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.8.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.zip">activemq-cpp-library-3.8.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.zip.asc">activemq-cpp-library-3.8.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.tar.gz">activemq-cpp-library-3.8.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.tar.gz.asc">activemq-cpp-library-3.8.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.tar.bz2">activemq-cpp-library-3.8.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.tar.bz2.asc">activemq-cpp-library-3.8.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.zip">activemq-cpp-library-3.8.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.zip.asc">activemq-cpp-library-3.8.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.tar.gz">activemq-cpp-library-3.8.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.tar.gz.asc">activemq-cpp-library-3.8.0-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.tar.bz2">activemq-cpp-library-3.8.0-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.0-src.tar.bz2.asc">activemq-cpp-library-3.8.0-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.8.0Release-GitTagCheckout">Git Tag Checkout</h2>
+<h2>Git Tag Checkout</h2>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
+<structured-macro ac:macro-id="954b8b3d-f733-4c45-8aaa-effe62c2afc2" ac:name="panel" ac:schema-version="1"><rich-text-body>
<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git</a><br clear="none">
-git checkout tags/activemq-cpp-3.8.0</p>
-</div></div>
+git checkout tags/activemq-cpp-3.8.0</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.8.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324544">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324544">release notes</a></p></div>
diff --git a/cms/activemq-cpp-381-release.xml b/cms/activemq-cpp-381-release.xml
index 209132e..7dd1ee0 100644
--- a/cms/activemq-cpp-381-release.xml
+++ b/cms/activemq-cpp-381-release.xml
@@ -1,31 +1,29 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.8.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a new patch release that resolves a memory leak issue found in the 3.8.0 and 3.7.x releases. If you are running an older release you are strongly advised to upgrade (you can work around the leak by disabling message audit in your ActiveMQConnectionFactory). </p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div>
+<structured-macro ac:macro-id="b43a6b4d-1d71-4884-9e59-4a611fcb048d" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.8.1Release-API">API</h2>
+<h2>API</h2>
<p>This release is based on the CMS 3.2 API.</p>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p>
-<h2 id="ActiveMQ-CPP3.8.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.zip">activemq-cpp-library-3.8.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.zip.asc">activemq-cpp-library-3.8.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.tar.gz">activemq-cpp-library-3.8.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.tar.gz.asc">activemq-cpp-library-3.8.1-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.tar.bz2">activemq-cpp-library-3.8.1-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.tar.bz2.asc">activemq-cpp-library-3.8.1-src.tar.bz2.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.zip">activemq-cpp-library-3.8.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.zip.asc">activemq-cpp-library-3.8.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (gzipped) </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.tar.gz">activemq-cpp-library-3.8.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.tar.gz.asc">activemq-cpp-library-3.8.1-src.tar.gz.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.tar.bz2">activemq-cpp-library-3.8.1-src.tar.bz2</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/activemq-cpp-library-3.8.1-src.tar.bz2.asc">activemq-cpp-library-3.8.1-src.tar.bz2.asc</a> </p></td></tr></tbody></table>
-<h2 id="ActiveMQ-CPP3.8.1Release-GitTagCheckout">Git Tag Checkout</h2>
+<h2>Git Tag Checkout</h2>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
+<structured-macro ac:macro-id="a1d6119f-69dd-4a4e-a9c3-df00e5992710" ac:name="panel" ac:schema-version="1"><rich-text-body>
<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git</a><br clear="none">
-git checkout tags/activemq-cpp-3.8.1</p>
-</div></div>
+git checkout tags/activemq-cpp-3.8.1</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ-CPP3.8.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324975">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324975">release notes</a></p></div>
diff --git a/cms/activemq-cpp-382-release.xml b/cms/activemq-cpp-382-release.xml
index c5f9fdd..5742e7e 100644
--- a/cms/activemq-cpp-382-release.xml
+++ b/cms/activemq-cpp-382-release.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.8.2Release-NewandNoteworthy">New and Noteworthy</h2><p>This is a new patch release that resolves some issues that have been found since the last patch release.</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div><h2 id="ActiveMQ-CPP3.8.2Release-API">API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p><h2 id="ActiveMQ-CPP3.8.2Release-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.zip">activemq-cpp-library-3.8.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.zip.asc">activemq-cpp-library-3.8.2-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.tar.gz">activemq-cpp-library-3.8.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.tar.gz.asc">activemq-cpp-library-3.8.2-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.tar.bz2">activemq-cpp-library-3.8.2-src.tar.bz2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.tar.bz2.asc">activemq-cpp-library-3.8.2-src.tar.bz2.asc</a></p></td></tr></tbody></table></div><h2 id="ActiveMQ-CPP3.8.2Release-GitTagCheckout">Git Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git</a><br clear="none"> git checkout tags/activemq-cpp-3.8.2</p>
-</div></div><h2 id="ActiveMQ-CPP3.8.2Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12325248">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a new patch release that resolves some issues that have been found since the last patch release.</p><structured-macro ac:macro-id="9c959107-12b4-4bac-8dae-a1530892aa4d" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro><h2>API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.zip">activemq-cpp-library-3.8.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.zip.asc">activemq-cpp-library-3.8.2-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.tar.gz">activemq-cpp-library-3.8.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.tar.gz.asc">activemq-cpp-library-3.8.2-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.tar.bz2">activemq-cpp-library-3.8.2-src.tar.bz2</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.2/activemq-cpp-library-3.8.2-src.tar.bz2.asc">activemq-cpp-library-3.8.2-src.tar.bz2.asc</a></p></td></tr></tbody></table><h2>Git Tag Checkout</h2><structured-macro ac:macro-id="0d53d12e-7694-47b0-a256-f80b48366f08" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git</a><br clear="none"> git checkout tags/activemq-cpp-3.8.2</p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12325248">release notes</a></p></div>
diff --git a/cms/activemq-cpp-383-release.xml b/cms/activemq-cpp-383-release.xml
index c46540c..691e8ab 100644
--- a/cms/activemq-cpp-383-release.xml
+++ b/cms/activemq-cpp-383-release.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.8.3Release-NewandNoteworthy">New and Noteworthy</h2><p>This is a new patch release that resolves some issues that have been found since the last patch release.</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div><h2 id="ActiveMQ-CPP3.8.3Release-API">API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p><h2 id="ActiveMQ-CPP3.8.3Release-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.zip">activemq-cpp-library-3.8.3-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.zip.asc">activemq-cpp-library-3.8.3-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.tar.gz">activemq-cpp-library-3.8.3-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.tar.gz.asc">activemq-cpp-library-3.8.3-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.tar.bz2">activemq-cpp-library-3.8.3-src.tar.bz2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.tar.bz2.asc">activemq-cpp-library-3.8.3-src.tar.bz2.asc</a></p></td></tr></tbody></table></div><h2 id="ActiveMQ-CPP3.8.3Release-GitTagCheckout">Git Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.8.3</span></p>
-</div></div><h2 id="ActiveMQ-CPP3.8.3Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12325744">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a new patch release that resolves some issues that have been found since the last patch release.</p><structured-macro ac:macro-id="281495e5-c964-44e5-b296-1a0291e896a3" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro><h2>API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.zip">activemq-cpp-library-3.8.3-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.zip.asc">activemq-cpp-library-3.8.3-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.tar.gz">activemq-cpp-library-3.8.3-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.tar.gz.asc">activemq-cpp-library-3.8.3-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.tar.bz2">activemq-cpp-library-3.8.3-src.tar.bz2</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.3/activemq-cpp-library-3.8.3-src.tar.bz2.asc">activemq-cpp-library-3.8.3-src.tar.bz2.asc</a></p></td></tr></tbody></table><h2>Git Tag Checkout</h2><structured-macro ac:macro-id="788a6db2-faba-4c5d-bf74-343c93803e12" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.8.3</span></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12325744">release notes</a></p></div>
diff --git a/cms/activemq-cpp-384-release.xml b/cms/activemq-cpp-384-release.xml
index 752c72a..0be8424 100644
--- a/cms/activemq-cpp-384-release.xml
+++ b/cms/activemq-cpp-384-release.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.8.4Release-NewandNoteworthy">New and Noteworthy</h2><p>This is a new patch release that resolves some issues that have been found since the last patch release.</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div><h2 id="ActiveMQ-CPP3.8.4Release-API">API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p><h2 id="ActiveMQ-CPP3.8.4Release-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.zip">activemq-cpp-library-3.8.4-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.zip.asc">activemq-cpp-library-3.8.4-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.tar.gz">activemq-cpp-library-3.8.4-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.tar.gz.asc">activemq-cpp-library-3.8.4-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.tar.bz2">activemq-cpp-library-3.8.4-src.tar.bz2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.tar.bz2.asc">activemq-cpp-library-3.8.4-src.tar.bz2.asc</a></p></td></tr></tbody></table></div><h2 id="ActiveMQ-CPP3.8.4Release-GitTagCheckout">Git Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.8.4</span></p>
-</div></div><h2 id="ActiveMQ-CPP3.8.4Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12327391">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a new patch release that resolves some issues that have been found since the last patch release.</p><structured-macro ac:macro-id="ffb0b158-d0aa-4c5f-97d2-778681956eac" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro><h2>API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html">here</a></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.zip">activemq-cpp-library-3.8.4-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.zip.asc">activemq-cpp-library-3.8.4-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.tar.gz">activemq-cpp-library-3.8.4-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.tar.gz.asc">activemq-cpp-library-3.8.4-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.tar.bz2">activemq-cpp-library-3.8.4-src.tar.bz2</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.8.4/activemq-cpp-library-3.8.4-src.tar.bz2.asc">activemq-cpp-library-3.8.4-src.tar.bz2.asc</a></p></td></tr></tbody></table><h2>Git Tag Checkout</h2><structured-macro ac:macro-id="97c66a3b-2056-4cd5-8082-0bf1d83b65dc" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.8.4</span></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12327391">release notes</a></p></div>
diff --git a/cms/activemq-cpp-390-release.xml b/cms/activemq-cpp-390-release.xml
index e701aa1..61d7f11 100644
--- a/cms/activemq-cpp-390-release.xml
+++ b/cms/activemq-cpp-390-release.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.9.0Release-NewandNoteworthy">New and Noteworthy</h2><p>This is a new major release that resolves a number of issues found since the 3.8.x series was released.  The client has been updated to include many of the same fixes that were placed into the ActiveMQ JMS client.  Additional fixes for memory leaks and segfaults have been added as well. </p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div><h2 id="ActiveMQ-CPP3.9.0Release-API">API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2 id="ActiveMQ-CPP3.9.0Release-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.zip">activemq-cpp-library-3.9.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.zip.asc">activemq-cpp-library-3.9.0-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.tar.gz">activemq-cpp-library-3.9.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.tar.gz.asc">activemq-cpp-library-3.9.0-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.tar.bz2">activemq-cpp-library-3.9.0-src.tar.bz2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.tar.bz2.asc">activemq-cpp-library-3.9.0-src.tar.bz2.asc</a></p></td></tr></tbody></table></div><h2 id="ActiveMQ-CPP3.9.0Release-GitTagCheckout">Git Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.0</span></p>
-</div></div><h2 id="ActiveMQ-CPP3.9.0Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324974">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a new major release that resolves a number of issues found since the 3.8.x series was released.  The client has been updated to include many of the same fixes that were placed into the ActiveMQ JMS client.  Additional fixes for memory leaks and segfaults have been added as well. </p><structured-macro ac:macro-id="ffb0b158-d0aa-4c5f-97d2-778681956eac" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro><h2>API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.zip">activemq-cpp-library-3.9.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.zip.asc">activemq-cpp-library-3.9.0-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.tar.gz">activemq-cpp-library-3.9.0-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.tar.gz.asc">activemq-cpp-library-3.9.0-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.tar.bz2">activemq-cpp-library-3.9.0-src.tar.bz2</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.0/activemq-cpp-library-3.9.0-src.tar.bz2.asc">activemq-cpp-library-3.9.0-src.tar.bz2.asc</a></p></td></tr></tbody></table><h2>Git Tag Checkout</h2><structured-macro ac:macro-id="97c66a3b-2056-4cd5-8082-0bf1d83b65dc" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.0</span></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12324974">release notes</a></p></div>
diff --git a/cms/activemq-cpp-391-release.xml b/cms/activemq-cpp-391-release.xml
index 0d6f0bd..a94172c 100644
--- a/cms/activemq-cpp-391-release.xml
+++ b/cms/activemq-cpp-391-release.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.9.1Release-NewandNoteworthy">New and Noteworthy</h2><p>This is a minor bugfix release of the ActiveMQ-CPP library that fixes a segfault that can occur when running against the latest ActiveMQ Artemis release along with a couple other minor fixes.</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div><h2 id="ActiveMQ-CPP3.9.1Release-API">API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2 id="ActiveMQ-CPP3.9.1Release-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.zip">activemq-cpp-library-3.9.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.zip.asc">activemq-cpp-library-3.9.1-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.tar.gz">activemq-cpp-library-3.9.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.tar.gz.asc">activemq-cpp-library-3.9.1-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.tar.bz2">activemq-cpp-library-3.9.1-src.tar.bz2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.tar.bz2.asc">activemq-cpp-library-3.9.1-src.tar.bz2.asc</a></p></td></tr></tbody></table></div><h2 id="ActiveMQ-CPP3.9.1Release-GitTagCheckout">Git Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.1</span></p>
-</div></div><h2 id="ActiveMQ-CPP3.9.1Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12333244">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a minor bugfix release of the ActiveMQ-CPP library that fixes a segfault that can occur when running against the latest ActiveMQ Artemis release along with a couple other minor fixes.</p><structured-macro ac:macro-id="ffb0b158-d0aa-4c5f-97d2-778681956eac" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro><h2>API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.zip">activemq-cpp-library-3.9.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.zip.asc">activemq-cpp-library-3.9.1-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.tar.gz">activemq-cpp-library-3.9.1-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.tar.gz.asc">activemq-cpp-library-3.9.1-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.tar.bz2">activemq-cpp-library-3.9.1-src.tar.bz2</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.1/activemq-cpp-library-3.9.1-src.tar.bz2.asc">activemq-cpp-library-3.9.1-src.tar.bz2.asc</a></p></td></tr></tbody></table><h2>Git Tag Checkout</h2><structured-macro ac:macro-id="97c66a3b-2056-4cd5-8082-0bf1d83b65dc" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.1</span></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&styleName=Html&version=12333244">release notes</a></p></div>
diff --git a/cms/activemq-cpp-392-release.xml b/cms/activemq-cpp-392-release.xml
index 8f908b5..2fd156b 100644
--- a/cms/activemq-cpp-392-release.xml
+++ b/cms/activemq-cpp-392-release.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.9.2Release-NewandNoteworthy">New and Noteworthy</h2><p>This is a minor patch release of the ActiveMQ-CPP library that fixes an issue with the way the STOMP protocol handles composite destinations.</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div><h2 id="ActiveMQ-CPP3.9.2Release-API">API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2 id="ActiveMQ-CPP3.9.2Release-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.zip">activemq-cpp-library-3.9.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.zip.asc">activemq-cpp-library-3.9.2-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.tar.gz">activemq-cpp-library-3.9.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.tar.gz.asc">activemq-cpp-library-3.9.2-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.tar.bz2">activemq-cpp-library-3.9.2-src.tar.bz2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.tar.bz2.asc">activemq-cpp-library-3.9.2-src.tar.bz2.asc</a></p></td></tr></tbody></table></div><h2 id="ActiveMQ-CPP3.9.2Release-GitTagCheckout">Git Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.2</span></p>
-</div></div><h2 id="ActiveMQ-CPP3.9.2Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&version=12334243">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a minor patch release of the ActiveMQ-CPP library that fixes an issue with the way the STOMP protocol handles composite destinations.</p><structured-macro ac:macro-id="ffb0b158-d0aa-4c5f-97d2-778681956eac" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro><h2>API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.zip">activemq-cpp-library-3.9.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.zip.asc">activemq-cpp-library-3.9.2-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.tar.gz">activemq-cpp-library-3.9.2-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.tar.gz.asc">activemq-cpp-library-3.9.2-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.tar.bz2">activemq-cpp-library-3.9.2-src.tar.bz2</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/activemq-cpp/3.9.2/activemq-cpp-library-3.9.2-src.tar.bz2.asc">activemq-cpp-library-3.9.2-src.tar.bz2.asc</a></p></td></tr></tbody></table><h2>Git Tag Checkout</h2><structured-macro ac:macro-id="97c66a3b-2056-4cd5-8082-0bf1d83b65dc" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.2</span></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&version=12334243">release notes</a></p></div>
diff --git a/cms/activemq-cpp-393-release.xml b/cms/activemq-cpp-393-release.xml
index 4b967e4..1b427fa 100644
--- a/cms/activemq-cpp-393-release.xml
+++ b/cms/activemq-cpp-393-release.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.9.3Release-NewandNoteworthy">New and Noteworthy</h2><p>This is a minor patch release of the ActiveMQ-CPP library that fixes an issue with producer create no waiting for a response from the broker before returning which can lead to missed error on create situations.</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div><h2 id="ActiveMQ-CPP3.9.3Release-API">API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2 id="ActiveMQ-CPP3.9.3Release-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.zip">activemq-cpp-library-3.9.3-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.zip.asc">activemq-cpp-library-3.9.3-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.tar.gz">activemq-cpp-library-3.9.3-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.tar.gz.asc">activemq-cpp-library-3.9.3-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.tar.bz2">activemq-cpp-library-3.9.3-src.tar.bz2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.tar.bz2.asc">activemq-cpp-library-3.9.3.src.tar.bz2.asc</a></p></td></tr></tbody></table></div><h2 id="ActiveMQ-CPP3.9.3Release-GitTagCheckout">Git Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.3</span></p>
-</div></div><h2 id="ActiveMQ-CPP3.9.3Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&version=12334845">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a minor patch release of the ActiveMQ-CPP library that fixes an issue with producer create no waiting for a response from the broker before returning which can lead to missed error on create situations.</p><structured-macro ac:macro-id="ffb0b158-d0aa-4c5f-97d2-778681956eac" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro><h2>API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.zip">activemq-cpp-library-3.9.3-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.zip.asc">activemq-cpp-library-3.9.3-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.tar.gz">activemq-cpp-library-3.9.3-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.tar.gz.asc">activemq-cpp-library-3.9.3-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.tar.bz2">activemq-cpp-library-3.9.3-src.tar.bz2</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.3/activemq-cpp-library-3.9.3-src.tar.bz2.asc">activemq-cpp-library-3.9.3.src.tar.bz2.asc</a></p></td></tr></tbody></table><h2>Git Tag Checkout</h2><structured-macro ac:macro-id="97c66a3b-2056-4cd5-8082-0bf1d83b65dc" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.3</span></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&version=12334845">release notes</a></p></div>
diff --git a/cms/activemq-cpp-394-release.xml b/cms/activemq-cpp-394-release.xml
index 42d9c57..66d9ac9 100644
--- a/cms/activemq-cpp-394-release.xml
+++ b/cms/activemq-cpp-394-release.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPP3.9.4Release-NewandNoteworthy">New and Noteworthy</h2><p>This is a minor patch release of the ActiveMQ-CPP library that fixes an issue in the Failover handling.</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p>
-</div></div><h2 id="ActiveMQ-CPP3.9.4Release-API">API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2 id="ActiveMQ-CPP3.9.4Release-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Windows</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.zip">activemq-cpp-library-3.9.4.src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.zip.asc">activemq-cpp-library-3.9.4-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.tar.gz">activemq-cpp-library-3.9.4-src.tar.gz</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.tar.gz.asc">activemq-cpp-library-3.9.4-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.tar.bz2">activemq-cpp-library-3.9.4-src.tar.bz2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.tar.bz2.asc">activemq-cpp-library-3.9.4.src.tar.bz2.asc</a></p></td></tr></tbody></table></div><h2 id="ActiveMQ-CPP3.9.4Release-GitTagCheckout">Git Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.4</span></p>
-</div></div><h2 id="ActiveMQ-CPP3.9.4Release-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&version=12335498">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a minor patch release of the ActiveMQ-CPP library that fixes an issue in the Failover handling.</p><structured-macro ac:macro-id="ffb0b158-d0aa-4c5f-97d2-778681956eac" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family</p></rich-text-body></structured-macro><h2>API</h2><p>This release is based on the CMS 3.2 API.</p><p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html">here</a></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature file of download</p></th></tr><tr><td colspan="1" rowspan="1"><p>Source code for Windows</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.zip">activemq-cpp-library-3.9.4.src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.zip.asc">activemq-cpp-library-3.9.4-src.zip.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (gzipped)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.tar.gz">activemq-cpp-library-3.9.4-src.tar.gz</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.tar.gz.asc">activemq-cpp-library-3.9.4-src.tar.gz.asc</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Source code for Unix (bz2)</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.tar.bz2">activemq-cpp-library-3.9.4-src.tar.bz2</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/3.9.4/activemq-cpp-library-3.9.4-src.tar.bz2.asc">activemq-cpp-library-3.9.4.src.tar.bz2.asc</a></p></td></tr></tbody></table><h2>Git Tag Checkout</h2><structured-macro ac:macro-id="97c66a3b-2056-4cd5-8082-0bf1d83b65dc" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git<br clear="none"></a><span style="line-height: 1.4285715;">cd activemq-cpp<br clear="none">git checkout tags/3.9.4</span></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311207&version=12335498">release notes</a></p></div>
diff --git a/cms/activemq-cpp-libtool-and-packaging-notes.xml b/cms/activemq-cpp-libtool-and-packaging-notes.xml
index dc733db..ec8d0ae 100644
--- a/cms/activemq-cpp-libtool-and-packaging-notes.xml
+++ b/cms/activemq-cpp-libtool-and-packaging-notes.xml
@@ -1,15 +1,15 @@
-<div class="wiki-content maincontent"><h1 id="ActiveMQ-CPP,libtoolandpackagingnotes-ActiveMQ-CPP,libtoolandpackagingnotes">ActiveMQ-CPP, libtool and packaging notes</h1>
+<div class="wiki-content maincontent"><h1>ActiveMQ-CPP, libtool and packaging notes</h1>
-<h3 id="ActiveMQ-CPP,libtoolandpackagingnotes-Introduction">Introduction</h3>
+<h3>Introduction</h3>
<p>This page attempts to summarise information to be considered</p>
<ul><li>when configuring libtool</li><li>when packaging ActiveMQ for distribution on Debian, Red Hat, Solaris.</li></ul>
-<h3 id="ActiveMQ-CPP,libtoolandpackagingnotes-Concepts">Concepts</h3>
+<h3>Concepts</h3>
<p>Product version numbers</p>
-<ul><li>Please see the notes on <a shape="rect" href="activemq-cpp-product-version-number.xml">ActiveMQ-CPP product version number</a></li></ul>
+<ul><li>Please see the notes on <link><page ri:content-title="ActiveMQ-CPP product version number"></page></link></li></ul>
<p>SONAME</p>
@@ -29,5 +29,6 @@
<p>Debian package name</p>
<ul><li>The package name includes the following from libtool: release number and interface number</li><li>for example, if interface version = 4, then the package name = libactivemq-cpp4</li><li>The product version number is not part of the Debian package name - it is used elsewhere in Debian's control files</li></ul>
+
</div>
diff --git a/cms/activemq-cpp-product-version-number.xml b/cms/activemq-cpp-product-version-number.xml
index 3da16c4..1aca88d 100644
--- a/cms/activemq-cpp-product-version-number.xml
+++ b/cms/activemq-cpp-product-version-number.xml
@@ -4,7 +4,7 @@
<p>In order to facilitate the correct use of libtool and the preparation of binary packages for distribution on Debian, Red Hat, etc, it is beneficial to have a written policy on version numbers.</p>
-<h3 id="ActiveMQ-CPPproductversionnumber-Productversionnumber">Product version number</h3>
+<h3>Product version number</h3>
<p>These numbers represent the release of the product. E.g. 2.1.2</p>
@@ -17,7 +17,7 @@
<ul><li>may choose to have more than one major version installed on the same system concurrently (e.g. 2.1.2 and 3.4.5)</li><li>may only have one variation of each major version installed (e.g. it is not intended to have 2.1.2 and 2.3.0 concurrently)</li></ul>
-<h3 id="ActiveMQ-CPPproductversionnumber-libtoolABIversionnumber">libtool ABI version number</h3>
+<h3>libtool ABI version number</h3>
<p>This number represents an ABI version. It is an integer, e.g., the number 5.</p>
@@ -27,5 +27,6 @@
<ul><li>any new structs, classes or function prototypes are added</li><li>the definition of any structs, classes or function prototypes are modified</li><li>any structs, classes or function prototypes are removed</li></ul>
-<p>Note that in the first case above, binary compatibility with existing applications is maintained. In the second and third case, binary compatibility is lost, and the libtool `age' variable must also be changed.</p></div>
+<p>Note that in the first case above, binary compatibility with existing applications is maintained. In the second and third case, binary compatibility is lost, and the libtool `age' variable must also be changed.</p>
+</div>
diff --git a/cms/activemq-cpp-stomp.xml b/cms/activemq-cpp-stomp.xml
index 694b5d7..d075a3d 100644
--- a/cms/activemq-cpp-stomp.xml
+++ b/cms/activemq-cpp-stomp.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ-CPPStomp-ActiveMQ-CPPStompSupport">ActiveMQ-CPP Stomp Support</h2>
+<div class="wiki-content maincontent"><h2>ActiveMQ-CPP Stomp Support</h2>
-<p>Stomp is a simple text-based protocol supported by the ActiveMQ Broker that allows communication from a variety of clients (e.g. C++, Java, .NET, Ruby, Python, etc). If you'd like to learn more about the stomp protocol, go <a shape="rect" class="external-link" href="http://stomp.codehaus.org" rel="nofollow">here</a>. Also, you can see ActiveMQ extensions <a shape="rect" class="external-link" href="http://www.activemq.org/site/stomp.html" rel="nofollow">here</a>.</p>
+<p>Stomp is a simple text-based protocol supported by the ActiveMQ Broker that allows communication from a variety of clients (e.g. C++, Java, .NET, Ruby, Python, etc). If you'd like to learn more about the stomp protocol, go <a shape="rect" href="http://stomp.codehaus.org">here</a>. Also, you can see ActiveMQ extensions <a shape="rect" href="http://www.activemq.org/site/stomp.html">here</a>.</p>
<p>The implementation of the CMS API with stomp has some quirks, as it's a simple protocol and doesn't have the full capabilities of, say, openwire. The purpose of this page is to document these quirks so that users understand any strange behaviors that they may see occasionally.</p>
-<h3 id="ActiveMQ-CPPStomp-MessagePropertiesinStompCMS">Message Properties in Stomp CMS</h3>
+<h3>Message Properties in Stomp CMS</h3>
<p>Since Stomp is strictly text-based, it does not support a way to specify the type of message properties (called "header" in stomp lingo). This means that a property sent as an integer could be read by a Stomp CMS client as any of: string, integer, short, long, etc.</p>
@@ -12,11 +12,11 @@
<p>The same goes for writing values to an outgoing message. You can call any of the methods (e.g. setIntProperty). The resulting value that goes out on the wire is still a string, however.</p>
-<h3 id="ActiveMQ-CPPStomp-TemporaryTopicsandQueues"> Temporary Topics and Queues</h3>
+<h3> Temporary Topics and Queues</h3>
<p>The Stomp Protocol does not support the concept of temporary topics or queues.  If you call the createTemporaryTopic or createTemporaryQueue methods of cms::Session an exception of type NotSupportedException is thrown.  To implement request / response type semantics you will need to use standard Topics and Queues.</p>
-<h3 id="ActiveMQ-CPPStomp-UsagenotesonSelectorswithStomp">Usage notes on Selectors with Stomp</h3>
+<h3>Usage notes on Selectors with Stomp</h3>
<p>Stomp as a general rule only allows one session per connection.  In ActiveMQ-CPP we have created a sort of virtual session that allows more than one session to be created per connection.  The one caveat is that there still can only be one selector on the main Stomp Session that we create, so whatever the first session is that is created with a selector will be the only selector that will actually have any effect as none of the newly created sessions will apply a selector even if you pass one in the creation of that Session.  </p></div>
diff --git a/cms/activemq-cpp-usage-faqs.xml b/cms/activemq-cpp-usage-faqs.xml
index fab5cc3..e8e1e96 100644
--- a/cms/activemq-cpp-usage-faqs.xml
+++ b/cms/activemq-cpp-usage-faqs.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent"><p>This section covers general questions on how to use various feature of the ActiveMQ-CPP Library</p>
-<ul class="childpages-macro"><li><a shape="rect" href="how-do-i-use-the-ssl-transport.xml">How do I use the SSL Transport</a></li></ul> </div>
+<structured-macro ac:macro-id="a7447724-ad89-4df5-b4a0-fef59223e9bb" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro> </div>
diff --git a/cms/api.xml b/cms/api.xml
index 10fe06f..216adcc 100644
--- a/cms/api.xml
+++ b/cms/api.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="API-ActiveMQ-CPPAPI">ActiveMQ-CPP API</h2><p><a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html/">ActiveMQ-CPP 3.6.x</a></p><p><a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html/">ActiveMQ-CPP 3.9.x</a></p></div>
+<div class="wiki-content maincontent"><h2>ActiveMQ-CPP API</h2><p><a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html/">ActiveMQ-CPP 3.6.x</a></p><p><a shape="rect" href="http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html/">ActiveMQ-CPP 3.9.x</a></p></div>
diff --git a/cms/are-there-more-faq-entries.xml b/cms/are-there-more-faq-entries.xml
index c0751ef..23ef201 100644
--- a/cms/are-there-more-faq-entries.xml
+++ b/cms/are-there-more-faq-entries.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="AretheremoreFAQEntries-AretheremoreFAQEntries?">Are there more FAQ Entries?</h2>
+<div class="wiki-content maincontent"><h2>Are there more FAQ Entries?</h2>
-<p>Yes, see the <a shape="rect" class="external-link" href="http://activemq.apache.org/faq.html">ActiveMQ Main FAQ</a></p></div>
+<p>Yes, see the <a shape="rect" href="http://activemq.apache.org/faq.html">ActiveMQ Main FAQ</a></p></div>
diff --git a/cms/banner.xml b/cms/banner.xml
index 2698171..5fc45ca 100644
--- a/cms/banner.xml
+++ b/cms/banner.xml
@@ -1,9 +1,9 @@
-<div class="wiki-content maincontent"><p>
- </p><div id="asf_logo">
- <div id="activemq_logo">
- <a shape="rect" style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="http://activemq.apache.org/">ActiveMQ</a>
- <a shape="rect" style="float:right; width:210px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:15px; margin-right:10px;" href="http://www.apache.org">ASF</a>
- </div>
- </div>
-<p></p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="63011488-69a4-45f4-9190-112a11eaa0e7" ac:name="html" ac:schema-version="1"><parameter ac:name="output">html</parameter><parameter ac:name="noPanel">true</parameter><plain-text-body>
+ <div id="asf_logo">
+ <div id="activemq_logo">
+ <a style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="http://activemq.apache.org/">ActiveMQ</a>
+ <a style="float:right; width:210px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:15px; margin-right:10px;" href="http://www.apache.org">ASF</a>
+ </div>
+ </div>
+</plain-text-body></structured-macro></p><p></p></div>
diff --git a/cms/building-faqs.xml b/cms/building-faqs.xml
index c9b9f8d..903ef4f 100644
--- a/cms/building-faqs.xml
+++ b/cms/building-faqs.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>These are general hints and tips on Building the Library on various platforms etc.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="general-build-issues.xml">General Build Issues</a></li><li><a shape="rect" href="openssl-support.xml">OpenSSL Support</a><ul class="childpages-macro"><li><a shape="rect" href="enable-openssl-support-with-autotools.xml">Enable OpenSSL support with autotools</a></li><li><a shape="rect" href="how-do-i-prevent-autoconf-from-enabling-openssl-support.xml">How do I prevent autoconf from enabling OpenSSL support</a></li><li><a shape="rect" href="how-to-enable-ssl-support-on-windows.xml">How to enable SSL support on Windows</a></li></ul></li><li><a shape="rect" href="solaris-platform.xml">Solaris Platform</a><ul class="childpages-macro"><li><a shape="rect" href="errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml">Errors from libstd++.la on Solaris 10 using the GNU Compiler</a></li><li><a shape="rect" href="errors-saying-no-rule-to-make-target.xml">Errors saying "no rule to make target"</a></li><li><a shape="rect" href="using-the-solaris-cc-compiler.xml">Using the Solaris CC compiler</a></li></ul></li></ul> </div>
+<structured-macro ac:macro-id="694559c3-67c0-4fe6-ada1-c8b55a3656ac" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro> </div>
diff --git a/cms/building.xml b/cms/building.xml
index 6611dd9..a85db73 100644
--- a/cms/building.xml
+++ b/cms/building.xml
@@ -1,36 +1,14 @@
-<div class="wiki-content maincontent"><h2 id="Building-Dependencies">Dependencies</h2><h3 id="Building-libuuid">libuuid</h3><p>On *nix sytems, the build requires the libuuid library that is part of the e2fsprogs package and is available from <a shape="rect" class="external-link" href="http://e2fsprogs.sourceforge.net/" rel="nofollow">http://e2fsprogs.sourceforge.net/</a> which is not always installed by default.</p><p>On Fedora/Red Hat/openSUSE, you should install the e2fsprogs and e2fsprogs-devel packages. On Debian/Ubuntu, you should install uuid and uuid-dev packages.</p><h3 id="Building-CppUnit">CppUnit</h3><p>The package contains a complete set of CppUnit tests. In order for you to build an run the tests, you will need to download and install the CppUnit library. See <a shape="rect" class="external-link" href="http://cppunit.sourceforge.net/cppunit-wiki" rel="nofollow">http://cppunit.sourceforge.net/cppunit-wiki</a></p><p>On Fedora/Red Hat/openSUSE, you should install the cppunit and cppunit-devel packages. On Debian/Ubuntu, you should install the build-essential, libcppunit and libcppunit-dev packages.</p><p>Make sure that the paths to the installed CppUnit library and includes are visible in your current shell before you try building the tests.</p><p>Windows users will need to build the CppUnit library using the CppUnit MSVC project files. A discussion of the build process can be found on the CppUnit wiki under <a shape="rect" class="external-link" href="http://cppunit.sourceforge.net/cppunit-wiki/BuildingCppUnit1" rel="nofollow">CppUnit build instructions</a> this covers both MSVC along with many other platforms and tool suites.</p><h3 id="Building-APR">APR</h3><p>With versions of ActiveMQ-CPP 2.2 and later, we have a dependency on the <a shape="rect" class="external-link" href="http://apr.apache.org">Apache Portable Runtime</a> project. You'll need to install APR on your system before you'll be able to build ActiveMQ-CPP.</p><div class="confluence-information-macro confluence-information-macro-note"><p class="title">Note to Windows Vista/MSVC++ 2008 Users</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The Vista SDK has introduced some build problems for APR. For a work-around, follow the instructions <a shape="rect" class="external-link" href="https://issues.apache.org/bugzilla/show_bug.cgi?id=40398">here</a>.</p></div></div><h2 id="Building-Buildingon*nix(Unix/Linux/OSX/Cygwin)">Building on *nix (Unix/Linux/OS X/Cygwin)</h2><h3 id="Building-GNUBuildSystem(forbuildingon*nix)">GNU Build System (for building on *nix)</h3><p>To Generate the ./configure script use to create the Makefiles, you need the following software installed:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Tool</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Recommended Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>autoconf</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>>= 2.59</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>automake</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>>= 1.9.6</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>libtool</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>>= 1.5.22</p></td></tr></tbody></table></div><p>You can also install the Doxygen and Graphviz packages if you want to generate the API documentation in HTML format.</p><h3 id="Building-Building">Building</h3><p>This assumes you have all of the project dependencies installed. We're now ready to create the configure script. To do this, run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[./autogen.sh
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>You may see the following warnings when running this command:</p><p>src/test-integration/Makefile.am:44: `CXXFLAGS' is a user variable, you should not override it;<br clear="none"> src/test-integration/Makefile.am:44: use `AM_CXXFLAGS' instead.<br clear="none"> src/test/Makefile.am:104: `CXXFLAGS' is a user variable, you should not override it;<br clear="none"> src/test/Makefile.am:104: use `AM_CXXFLAGS' instead.</p><p>These can be ignored. We override CXXFLAGS in the makefiles for the unit and integration tests in order to suppress compiler warnings.</p></div></div><p>This should be run the first time and anytime you change configure.ac or any of the Makefile.am files.</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Solaris 10 Note</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>CppUnit might not build until you correct the file libstdc++.la to contain the correct data, see this discussion.</p><p><a shape="rect" class="external-link" href="http://forum.sun.com/jive/thread.jspa?threadID=73150" rel="nofollow">http://forum.sun.com/jive/thread.jspa?threadID=73150</a></p></div></div><p>The configure script will customize the way the software is built and installed into your system along with detecting the available libraries that have been installed. To use the default configuration just run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[./configure
-]]></script>
-</div></div><p>For more help on how to customize the build configuration, run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[./configure --help
-]]></script>
-</div></div><p>Once the configure script has run successfully, you are ready to build. Run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[make
-]]></script>
-</div></div><p>This will build all of the core ActiveMQ CPP source code. To build and install the code into the system directories, run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[make install
-]]></script>
-</div></div><p>You will have to become the superuser in order to be able to install the files.</p><h3 id="Building-Doxygen">Doxygen</h3><p>To generate the doxygen documentation for the project, just run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[make doxygen-run
-]]></script>
-</div></div><h3 id="Building-RunningTests">Running Tests</h3><h3 id="Building-UnitTests">Unit Tests</h3><p>In order to build and run the suite of unit tests, run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[make check
-]]></script>
-</div></div><p>This will verify that the library is functioning correctly on the target platform. In addition, it will generate the integration tests binary.</p><h3 id="Building-IntegrationTests">Integration Tests</h3><p>The library also contains a set of tests that are run against a real AMQ broker. These allow you to validate this distribution of ActiveMQ CPP against your broker. Running these without a broker will result in failed tests. The tests currently hard-code the broker url to be tcp://localhost:61613 for stomp and tcp://localhost:61616 for openwire.</p><p>The integration tests are built via "make check". To run them, first start a broker and then</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd src/test-integration
+<div class="wiki-content maincontent"><h2>Dependencies</h2><h3>libuuid</h3><p>On *nix sytems, the build requires the libuuid library that is part of the e2fsprogs package and is available from <a shape="rect" href="http://e2fsprogs.sourceforge.net/">http://e2fsprogs.sourceforge.net/</a> which is not always installed by default.</p><p>On Fedora/Red Hat/openSUSE, you should install the e2fsprogs and e2fsprogs-devel packages. On Debian/Ubuntu, you should install uuid and uuid-dev packages.</p><h3>CppUnit</h3><p>The package contains a complete set of CppUnit tests. In order for you to build an run the tests, you will need to download and install the CppUnit library. See <a shape="rect" href="http://cppunit.sourceforge.net/cppunit-wiki">http://cppunit.sourceforge.net/cppunit-wiki</a></p><p>On Fedora/Red Hat/openSUSE, you should install the cppunit and cppunit-devel packages. On Debian/Ubuntu, you should install the build-essential, libcppunit and libcppunit-dev packages.</p><p>Make sure that the paths to the installed CppUnit library and includes are visible in your current shell before you try building the tests.</p><p>Windows users will need to build the CppUnit library using the CppUnit MSVC project files. A discussion of the build process can be found on the CppUnit wiki under <a shape="rect" href="http://cppunit.sourceforge.net/cppunit-wiki/BuildingCppUnit1">CppUnit build instructions</a> this covers both MSVC along with many other platforms and tool suites.</p><h3>APR</h3><p>With versions of ActiveMQ-CPP 2.2 and later, we have a dependency on the <a shape="rect" href="http://apr.apache.org">Apache Portable Runtime</a> project. You'll need to install APR on your system before you'll be able to build ActiveMQ-CPP.</p><structured-macro ac:macro-id="814f1ae0-dcb7-4d54-90fa-842fa65b55b2" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Note to Windows Vista/MSVC++ 2008 Users</parameter><rich-text-body><p>The Vista SDK has introduced some build problems for APR. For a work-around, follow the instructions <a shape="rect" href="https://issues.apache.org/bugzilla/show_bug.cgi?id=40398">here</a>.</p></rich-text-body></structured-macro><h2>Building on *nix (Unix/Linux/OS X/Cygwin)</h2><h3>GNU Build System (for building on *nix)</h3><p>To Generate the ./configure script use to create the Makefiles, you need the following software installed:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Tool</p></th><th colspan="1" rowspan="1"><p>Recommended Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>autoconf</p></td><td colspan="1" rowspan="1"><p>>= 2.59</p></td></tr><tr><td colspan="1" rowspan="1"><p>automake</p></td><td colspan="1" rowspan="1"><p>>= 1.9.6</p></td></tr><tr><td colspan="1" rowspan="1"><p>libtool</p></td><td colspan="1" rowspan="1"><p>>= 1.5.22</p></td></tr></tbody></table><p>You can also install the Doxygen and Graphviz packages if you want to generate the API documentation in HTML format.</p><h3>Building</h3><p>This assumes you have all of the project dependencies installed. We're now ready to create the configure script. To do this, run:</p><structured-macro ac:macro-id="dc3ca860-74f7-4801-8a45-ec866e62c8a8" ac:name="code" ac:schema-version="1"><plain-text-body>./autogen.sh
+</plain-text-body></structured-macro><structured-macro ac:macro-id="06dcee5e-557a-43a7-bb5c-12d035fc94c5" ac:name="info" ac:schema-version="1"><rich-text-body><p>You may see the following warnings when running this command:</p><p>src/test-integration/Makefile.am:44: `CXXFLAGS' is a user variable, you should not override it;<br clear="none"> src/test-integration/Makefile.am:44: use `AM_CXXFLAGS' instead.<br clear="none"> src/test/Makefile.am:104: `CXXFLAGS' is a user variable, you should not override it;<br clear="none"> src/test/Makefile.am:104: use `AM_CXXFLAGS' instead.</p><p>These can be ignored. We override CXXFLAGS in the makefiles for the unit and integration tests in order to suppress compiler warnings.</p></rich-text-body></structured-macro><p>This should be run the first time and anytime you change configure.ac or any of the Makefile.am files.</p><structured-macro ac:macro-id="fbe6fd40-060e-4e7d-aeab-cefb37d4840e" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Solaris 10 Note</parameter><rich-text-body><p>CppUnit might not build until you correct the file libstdc++.la to contain the correct data, see this discussion.</p><p><a shape="rect" href="http://forum.sun.com/jive/thread.jspa?threadID=73150">http://forum.sun.com/jive/thread.jspa?threadID=73150</a></p></rich-text-body></structured-macro><p>The configure script will customize the way the software is built and installed into your system along with detecting the available libraries that have been installed. To use the default configuration just run:</p><structured-macro ac:macro-id="8001d5f7-b487-426e-9b95-edbeba7819a2" ac:name="code" ac:schema-version="1"><plain-text-body>./configure
+</plain-text-body></structured-macro><p>For more help on how to customize the build configuration, run:</p><structured-macro ac:macro-id="2155e25a-d425-4941-a99f-6a06dda59748" ac:name="code" ac:schema-version="1"><plain-text-body>./configure --help
+</plain-text-body></structured-macro><p>Once the configure script has run successfully, you are ready to build. Run:</p><structured-macro ac:macro-id="75f2735c-fb02-4ab6-b891-129aa1e81ca4" ac:name="code" ac:schema-version="1"><plain-text-body>make
+</plain-text-body></structured-macro><p>This will build all of the core ActiveMQ CPP source code. To build and install the code into the system directories, run:</p><structured-macro ac:macro-id="22203139-efff-4381-8396-4d5b8a296c40" ac:name="code" ac:schema-version="1"><plain-text-body>make install
+</plain-text-body></structured-macro><p>You will have to become the superuser in order to be able to install the files.</p><h3>Doxygen</h3><p>To generate the doxygen documentation for the project, just run:</p><structured-macro ac:macro-id="401f3159-64a0-4175-ac69-2ced43209ca7" ac:name="code" ac:schema-version="1"><plain-text-body>make doxygen-run
+</plain-text-body></structured-macro><h3>Running Tests</h3><h3>Unit Tests</h3><p>In order to build and run the suite of unit tests, run:</p><structured-macro ac:macro-id="29f84f58-9bc9-403c-adf6-736f5496b0d7" ac:name="code" ac:schema-version="1"><plain-text-body>make check
+</plain-text-body></structured-macro><p>This will verify that the library is functioning correctly on the target platform. In addition, it will generate the integration tests binary.</p><h3>Integration Tests</h3><p>The library also contains a set of tests that are run against a real AMQ broker. These allow you to validate this distribution of ActiveMQ CPP against your broker. Running these without a broker will result in failed tests. The tests currently hard-code the broker url to be tcp://localhost:61613 for stomp and tcp://localhost:61616 for openwire.</p><p>The integration tests are built via "make check". To run them, first start a broker and then</p><structured-macro ac:macro-id="29a5ea44-45fa-4d9b-848d-4e3e828ba93e" ac:name="code" ac:schema-version="1"><plain-text-body>cd src/test-integration
./activemq-test-integration
-]]></script>
-</div></div><p>This will take quite some time to complete, so be patient.</p><h3 id="Building-Example">Example</h3><p>There is an example application that ships with the distribution in src/examples. The example is compiled by default with the "make" command, but can easily be compiled manually using the command similar to the following (varies by platform).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[g++ -o main -pthread -I ../main main.cpp ../../src/main/.libs/libactivemq-cpp.a -luuid -I /usr/include/apr-1.0/ -lssl -lcrypto -lapr-1
-]]></script>
-</div></div><h2 id="Building-BuildingonWindowswithMSVC">Building on Windows with MSVC</h2><p>We support using the GNU compiler on Windows, using the Cygwin package. However we also support using the MSVC compiler on Windows.</p><p>There are a couple or things that you will need to setup to ensure that the MSVC compile succeeds.</p><h3 id="Building-IncludingDependencies">Including Dependencies</h3><p>The Project files reference the libraries described in the <a shape="rect" href="#Building-Dependencies">#Dependencies</a> section. To build successfully, you must either place these libraries in a directory listed in the project settings, or add a new location for your library directories.</p><h3 id="Building-MSVC>=2008">MSVC >= 2008</h3><p>If you're using MSVC >= 2008, it comes with the Windows SDK (so you don't need to download it separately).</p><p>For ActiveMQ-CPP >= 2.2, you will have to follow some special instructions for building APR, duscussed <a shape="rect" href="#Building-APR">here</a>.</p><h3 id="Building-Non-Vista/MSVC<2008">Non-Vista/MSVC < 2008</h3><p>If you are using Visual C++ < 2008, you need to download and install the Platform SDK if you don't have it installed already (the Platform SDK is called the "Windows SDK" since the release of Windows Vista). Once installed, do the following:</p><ul><li>Ensure that the path to your MSVC install is set in the PATH env variable. You can test this by typing cl.exe at the command line, if you get an error complaining that it is not found, then you'll need to fix your PATH. Alternatively, you can set up the necessary environment variables by running C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars32.bat.</li><li><p>Set the INCLUDE env variable to include the path to your MSVC includes, and the platform SDK includes. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[INCLUDE = D:\Program Files\Microsoft Visual Studio 8\VC\include;D:\Program Files\Microsoft Platform SDK\Include\*
-]]></script>
-</div></div></li><li><p>Set the LIB env variable to include the path to your MSVC libs, and the Platform SDK libs. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[LIB = D:\Program Files\Microsoft Visual Studio 8\VC\lib;D:\Program Files\Microsoft Platform SDK\Lib
-]]></script>
-</div></div></li></ul></div>
+</plain-text-body></structured-macro><p>This will take quite some time to complete, so be patient.</p><h3>Example</h3><p>There is an example application that ships with the distribution in src/examples. The example is compiled by default with the "make" command, but can easily be compiled manually using the command similar to the following (varies by platform).</p><structured-macro ac:macro-id="60253d7f-40cf-4e68-aa10-6812d50198a7" ac:name="code" ac:schema-version="1"><plain-text-body>g++ -o main -pthread -I ../main main.cpp ../../src/main/.libs/libactivemq-cpp.a -luuid -I /usr/include/apr-1.0/ -lssl -lcrypto -lapr-1
+</plain-text-body></structured-macro><h2>Building on Windows with MSVC</h2><p>We support using the GNU compiler on Windows, using the Cygwin package. However we also support using the MSVC compiler on Windows.</p><p>There are a couple or things that you will need to setup to ensure that the MSVC compile succeeds.</p><h3>Including Dependencies</h3><p>The Project files reference the libraries described in the <link ac:anchor="Dependencies"><plain-text-link-body>#Dependencies</plain-text-link-body></link> section. To build successfully, you must either place these libraries in a directory listed in the project settings, or add a new location for your library directories.</p><h3>MSVC >= 2008</h3><p>If you're using MSVC >= 2008, it comes with the Windows SDK (so you don't need to download it separately).</p><p>For ActiveMQ-CPP >= 2.2, you will have to follow some special instructions for building APR, duscussed <link ac:anchor="APR"><plain-text-link-body>here</plain-text-link-body></link>.</p><h3>Non-Vista/MSVC < 2008</h3><p>If you are using Visual C++ < 2008, you need to download and install the Platform SDK if you don't have it installed already (the Platform SDK is called the "Windows SDK" since the release of Windows Vista). Once installed, do the following:</p><ul><li>Ensure that the path to your MSVC install is set in the PATH env variable. You can test this by typing cl.exe at the command line, if you get an error complaining that it is not found, then you'll need to fix your PATH. Alternatively, you can set up the necessary environment variables by running C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars32.bat.</li><li><p>Set the INCLUDE env variable to include the path to your MSVC includes, and the platform SDK includes. For example:</p><structured-macro ac:macro-id="91677a7e-17d3-4b1d-9304-a1be2b117dc0" ac:name="code" ac:schema-version="1"><plain-text-body>INCLUDE = D:\Program Files\Microsoft Visual Studio 8\VC\include;D:\Program Files\Microsoft Platform SDK\Include\*
+</plain-text-body></structured-macro></li><li><p>Set the LIB env variable to include the path to your MSVC libs, and the Platform SDK libs. For example:</p><structured-macro ac:macro-id="d6b15ce1-20b3-4d30-becc-a721b3698e86" ac:name="code" ac:schema-version="1"><plain-text-body>LIB = D:\Program Files\Microsoft Visual Studio 8\VC\lib;D:\Program Files\Microsoft Platform SDK\Lib
+</plain-text-body></structured-macro></li></ul></div>
diff --git a/cms/cms-api-10-release.xml b/cms/cms-api-10-release.xml
index 336e9da..e12a2d1 100644
--- a/cms/cms-api-10-release.xml
+++ b/cms/cms-api-10-release.xml
@@ -1,27 +1,25 @@
-<div class="wiki-content maincontent"><h2 id="CMSAPI1.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is the first official release of the C++ Messaging Service (CMS)!! CMS provides the following:</p>
<ul><li>JMS-like API (all pure-virtual classes) for messaging from C++ applications!</li><li>Fairly mature API, having grown up under activemq-cpp</li><li>Vendor-independent way of messaging in C++</li><li>Decoupled from the activemq-cpp library in order to promote more CMS implementations</li></ul>
-<h2 id="CMSAPI1.0Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/cms-1.0">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/cms-1.0">here</a></p>
-<h2 id="CMSAPI1.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.0-src.zip">cms-1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.0-src.zip.asc">cms-1.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.0-src.tar.gz">cms-1.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.0-src.tar.gz.asc">cms-1.0-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.0-src.zip">cms-1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.0-src.zip.asc">cms-1.0-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.0-src.tar.gz">cms-1.0-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.0-src.tar.gz.asc">cms-1.0-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="CMSAPI1.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f6717f64-edb4-490a-aa9f-a065bf5e0e89" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/cms-1.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="CMSAPI1.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
<p>No change log - this is the initial submission.</p></div>
diff --git a/cms/cms-api-11-release.xml b/cms/cms-api-11-release.xml
index bd700a9..aef5a5e 100644
--- a/cms/cms-api-11-release.xml
+++ b/cms/cms-api-11-release.xml
@@ -1,31 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="CMSAPI1.1Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor release of the C++ Messaging Service (CMS). This release is was done as part of releasing ActiveMQ-CPP 2.1 and contains the following updates:</p>
<ul><li>Removed dependency on the ActiveMQ-CPP Properties class</li><li>Added support for exporting CMS interface symbols from shared libraries</li></ul>
-<h2 id="CMSAPI1.1Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/cms-1.1">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/cms-1.1">here</a></p>
-<h2 id="CMSAPI1.1Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.1-src.zip">cms-1.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.1-src.zip.asc">cms-1.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.1-src.tar.gz">cms-1.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.1-src.tar.gz.asc">cms-1.1-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.1-src.zip">cms-1.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.1-src.zip.asc">cms-1.1-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.1-src.tar.gz">cms-1.1-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.1-src.tar.gz.asc">cms-1.1-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="CMSAPI1.1Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6fcc2586-bb10-4a7c-b612-a1919dee4d5a" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/cms-1.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="CMSAPI1.1Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>The following issues were resolved as part of the <a shape="rect" href="activemq-cpp-21-release.xml">ActiveMQ-CPP 2.1 Release</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>The following issues were resolved as part of the <link><page ri:content-title="ActiveMQ-CPP 2.1 Release"></page></link><br clear="none">
+<structured-macro ac:macro-id="e8c94d3a-f5d0-4ee5-b469-c8232becc14d" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="https://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&query=dynamic+libraries&summary=true&type=3&pid=11000&fixfor=11812&status=5&tempMax=1000"></url></parameter></structured-macro> </p></div>
diff --git a/cms/cms-api-12-release.xml b/cms/cms-api-12-release.xml
index 75cd2f1..1e69cc9 100644
--- a/cms/cms-api-12-release.xml
+++ b/cms/cms-api-12-release.xml
@@ -1,31 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="CMSAPI1.2Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a minor release of the C++ Messaging Service (CMS). This release is was done as part of releasing ActiveMQ-CPP 2.1.1 and contains the following updates:</p>
<ul><li>Made read methods of BytesMessage const so that asynchronous consumers (onMessage) don't have to use const_cast.</li></ul>
-<h2 id="CMSAPI1.2Release-API">API</h2>
+<h2>API</h2>
-<p>Check out the API for this release <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/api_docs/cms-1.2">here</a></p>
+<p>Check out the API for this release <a shape="rect" href="http://activemq.apache.org/cms/api_docs/cms-1.2">here</a></p>
-<h2 id="CMSAPI1.2Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Windows </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.2-src.zip">cms-1.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.2-src.zip.asc">cms-1.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Source code for Unix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.2-src.tar.gz">cms-1.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.2-src.tar.gz.asc">cms-1.2-src.tar.gz.asc</a> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature file of download </p></th></tr><tr><td colspan="1" rowspan="1"><p> Source code for Windows </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.2-src.zip">cms-1.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.2-src.zip.asc">cms-1.2-src.zip.asc</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Source code for Unix </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/cms-1.2-src.tar.gz">cms-1.2-src.tar.gz</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/activemq-cpp/source/cms-1.2-src.tar.gz.asc">cms-1.2-src.tar.gz.asc</a> </p></td></tr></tbody></table>
-<h2 id="CMSAPI1.2Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="df1960f7-5935-412f-ae2d-6938bc473fab" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/tags/cms-1.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="CMSAPI1.2Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>The following issues were resolved as part of the <a shape="rect" href="activemq-cpp-211-release.xml">ActiveMQ-CPP 2.1.1 Release</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>The following issues were resolved as part of the <link><page ri:content-title="ActiveMQ-CPP 2.1.1 Release"></page></link><br clear="none">
+<structured-macro ac:macro-id="9770f5a1-0b54-46de-ab9e-1b6cc277e812" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&query=%22BytesMessage++readXXX+methods+as+const%22&summary=true&description=true&body=true&pid=11000&fixfor=11848&tempMax=1000"></url></parameter></structured-macro> </p></div>
diff --git a/cms/cms-api-overview.xml b/cms/cms-api-overview.xml
index e0f2b19..25e06dd 100644
--- a/cms/cms-api-overview.xml
+++ b/cms/cms-api-overview.xml
@@ -1,56 +1,48 @@
-<div class="wiki-content maincontent"><h1 id="CMSAPIOverview-WhatisCMS?">What is CMS?</h1>
+<div class="wiki-content maincontent"><h1>What is CMS?</h1>
<p>The CMS API is a C++ corollary to the JMS API in Java which is used to send and receive messages from clients spread out across a network or located on the same machine.  In CMS we've made every attempt to maintain as much parity with the JMS api as possible, diverging only when a JMS feature depended strongly on features in the Java programming language itself.  Even though there are some differences most are quite minor and for the most part CMS adheres to the JMS spec, so having a firm grasp on how JMS works should make using CMS that much easier. </p>
-<p>One of the first places to start if you are already familiar with JMS is to take a look at the CMS <a shape="rect" href="api.xml">API documentation</a></p>
+<p>One of the first places to start if you are already familiar with JMS is to take a look at the CMS <link><page ri:content-title="API"></page><link-body>API documentation</link-body></link></p>
-<h1 id="CMSAPIOverview-GettingStartedwithCMS">Getting Started with CMS</h1>
+<h1>Getting Started with CMS</h1>
<p>This section covers the basics of using the CMS API. In order to aid in the discussion we assume here that you are using ActiveMQ-CPP to connect to an ActiveMQ Broker, of course with CMS you could also link to another implementation of the CMS API in your C++ application and connect to some other Message service.</p>
-<h2 id="CMSAPIOverview-TheCMSConnectionFactory">The CMS ConnectionFactory</h2>
+<h2>The CMS ConnectionFactory</h2>
<p>The first interface you will generally use in the CMS API is the ConnectionFactory. A ConnectionFactory allows you to create CMS Connection objects which maintain a connection the some Messaging service, e.g. an ActiveMQ broker.</p>
<p>The simplest way to obtain an instance of a CMS ConnectionFactory is to use the static method <strong>createCMSConnectionFactory</strong> that all CMS Provider libraries are required to implement. The code snippet below demonstrates how to obtain a new ConnectionFactory:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a Connection Factory</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9e8b1347-2997-40fb-8c11-b47f647ef70d" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a Connection Factory</parameter><plain-text-body>
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
-]]></script>
-</div></div>
-<p>As you can see the <strong>createCMSConnectionFactory</strong> takes a single string parameter which is in the form of a URI that defines where the Connection that is created is to connect to as well as the protocol that should be used, TCP/IP in the case of the above example. Additionally configuration information can be encoded in the URI. Refer to the <a shape="rect" href="configuring.xml">Configuration</a> page for more information on the configuration parameters that can be passed to ActiveMQ-CPP via the URI.</p>
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
+</plain-text-body></structured-macro>
+<p>As you can see the <strong>createCMSConnectionFactory</strong> takes a single string parameter which is in the form of a URI that defines where the Connection that is created is to connect to as well as the protocol that should be used, TCP/IP in the case of the above example. Additionally configuration information can be encoded in the URI. Refer to the <link><page ri:content-title="Configuring"></page><link-body>Configuration</link-body></link> page for more information on the configuration parameters that can be passed to ActiveMQ-CPP via the URI.</p>
<p>Once you've created a ConnectionFactory the next thing to do is to create a CMS Connection using the ConnectionFactory. A Connection is the Object that manages the client's connection to the Provider. The next section covers the use of a CMS Connection, the code to create a Connection is shown below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a Connection</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="bbc275d7-faeb-4c13-a95f-a118fc6a71b4" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a Connection</parameter><plain-text-body>
std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection() );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Upon creation the Connection object attempts to connect to the CMS Provider, if the connection fails then an CMSException is thrown with a description of the error that occurred stored in its Message property.</p>
-<h3 id="CMSAPIOverview-ConnectionsandAuthentication">Connections and Authentication</h3>
+<h3>Connections and Authentication</h3>
<p>There are a couple versions of the <strong>createConnection</strong> method that allow you to specify login parameters for the newly created Connection. The one you would use most often takes a user-name and password pair that is transmitted to the Broker for authentication. Should the credentials be invalid a CMSException would be thrown. The sample code below shows how to pass a user-name and password in when creating your Connection object.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a Connection with Authentication</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection( "<USERNAME>", "<PASSWORD>") );
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="940da753-1288-4b8b-905b-e824cca36495" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a Connection with Authentication</parameter><plain-text-body>
+std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection( "<USERNAME>", "<PASSWORD>") );
+</plain-text-body></structured-macro>
<p>If you don't want to hard code values into your source code or write code to read the login data from somewhere else there is another option for passing in the user-name and password, the URI that you pass to <strong>createConnectionFactory</strong> can be encoded so that the connectionFactory will read the values from the system environment when it parses the URI. The example below shows how to create a connection factory with the login data set in the URI.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a Connection Factory with URI values for Authentication data.</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="750d8ac2-09b4-448a-89e5-89b097e4e9b9" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a Connection Factory with URI values for Authentication data.</parameter><plain-text-body>
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616?username=${USERNAME}&password=${PASSWORD}" ) );
-]]></script>
-</div></div>
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616?username=${USERNAME}&password=${PASSWORD}" ) );
+</plain-text-body></structured-macro>
<p>As you can see it is pretty simple to have values on the URI come from the system environment. This method will work for any parameter that you can specify in the URI.</p>
-<h2 id="CMSAPIOverview-CMSConnection">CMS Connection</h2>
+<h2>CMS Connection</h2>
<p>The CMS Connection interface defines an object that is the client's active connection to the CMS provider. In most cases the client will only create one connection object since it is considered a heavyweight object.</p>
@@ -61,18 +53,16 @@
<p>A CMS Connection is created from a CMS ConnectionFactory as we saw previously. If the ConnectionFactory create call is successful then the Connection object returned is connected to the CMS Provider. The Connection object is created in a stopped state, no messages will be delivered to Message consumers that a client creates until the Connection is started. Its normal to leave a Connection in the stopped state until the client has created the initial set of Sessions, Message Producers, and Message Consumers that it intends to use. Once the setup phase of the client completes it should call the Connection's start method to begin receiving messages from the Provider. Failing to call the <strong>start</strong> method is a very common error among new users of CMS and JMS clients, if you find you aren't receiving any messages the first thing to check is that you called <strong>start</strong>.</p>
<p>After creating the Connection the client must create a CMS Session in order to create message producers and consumers. The code snippet below puts together what we've seen so far and then shows how to create a CMS Session object from our Connection instance, the section that follows will discuss the CMS Session in more detail.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a Session</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="91e4c1d5-a91e-4c52-a16b-db33cf7cd081" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a Session</parameter><plain-text-body>
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection() );
std::auto_ptr<cms::Session> session( connection->createSession() );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="CMSAPIOverview-CMSSession">CMS Session</h2>
+<h2>CMS Session</h2>
<p>Once you've successfully created a CMS Connection the next thing you would normall do is create one or more CMS Session objects using your new Connectio instance.  A Session is defined as a Single Threaded context for producing and consuming messages. </p>
@@ -83,54 +73,49 @@
<p> A session can create and service multiple message producers and consumers.</p>
<p> When a client creates a CMS session it must specify the mode in which the Session will acknowledge the messages that it receives and dispatches.  The modes supported are summarized in the table below.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Acknowledge Mode <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description <br clear="none" class="atl-forced-newline"> </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> AUTO_ACKNOWLEDGE </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> With this acknowledgement mode, the session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> CLIENT_ACKNOWLEDGE </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> With this acknowledgement mode, the client acknowledges a consumed message by calling the message's acknowledge method. Acknowledging a consumed message acknowledges all messages that the session has consumed. When client acknowledgement mode is used, a client may build up a large number of unacknowledged messages while attempting to process them. A CMS provider should provide administrators with a way to limit client overrun so that clients are not driven to resource exhaustion and ensuing failure when some resource they are using is temporarily blocked. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> DUPS_OK_ACKNOWLEDGE </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> This acknowledgement mode instructs the session to lazily acknowledge the delivery of messages. This is likely to result in the delivery of some duplicate messages if the JMS provider fails, so it should only be used by consumers that can tolerate duplicate messages. Use of this mode can reduce session overhead by minimizing the work the session does to prevent duplicates. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> SESSION_TRANSACTED </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Session is Transacted and the acknowledge of messages is handled internally. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> INDIVIDUAL_ACKNOWLEDGE<br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Acknowledges are applied to a single message only.  Unlike CLIENT_ACKNOWLEDGE where the acknowledgement applies to all messages received up to that point for the entire session, this mode applied only to a single message allowing the client to be more selective about which messages are acknowledged.  <br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Acknowledge Mode <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1"><p> Description <br clear="none" class="atl-forced-newline"> </p></th></tr><tr><td colspan="1" rowspan="1"><p> AUTO_ACKNOWLEDGE </p></td><td colspan="1" rowspan="1"><p> With this acknowledgement mode, the session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> CLIENT_ACKNOWLEDGE </p></td><td colspan="1" rowspan="1"><p> With this acknowledgement mode, the client acknowledges a consumed message by calling the message's acknowledge method. Acknowledging a consumed message acknowledges all messages that the session has consumed. When client acknowledgement mode is used, a client may build up a large number of unacknowledged messages while attempting to process them. A CMS provider should provide administrators with a way to limit client overrun so that clients are not driven to resource exhaustion and ensuing failure when some resource they are using is temporarily blocked. </p></td></tr><tr><td colspan="1" rowspan="1"><p> DUPS_OK_ACKNOWLEDGE </p></td><td colspan="1" rowspan="1"><p> This acknowledgement mode instructs the session to lazily acknowledge the delivery of messages. This is likely to result in the delivery of some duplicate messages if the JMS provider fails, so it should only be used by consumers that can tolerate duplicate messages. Use of this mode can reduce session overhead by minimizing the work the session does to prevent duplicates. </p></td></tr><tr><td colspan="1" rowspan="1"><p> SESSION_TRANSACTED </p></td><td colspan="1" rowspan="1"><p> Session is Transacted and the acknowledge of messages is handled internally. <br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> INDIVIDUAL_ACKNOWLEDGE<br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> Acknowledges are applied to a single message only.  Unlike CLIENT_ACKNOWLEDGE where the acknowledgement applies to all messages received up to that point for the entire session, this mode applied only to a single message allowing the client to be more selective about which messages are acknowledged.  <br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table>
<p>In the previous section we showed you how to create a session, lets take a look at that example again here:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a Session</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c6d7a53d-861a-43b4-819c-5137d744cf64" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a Session</parameter><plain-text-body>
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection() );
std::auto_ptr<cms::Session> session( connection->createSession() );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>In this code snippet the Session is created using the createSession with no arguments, this creates a Session that is in the AUTO_ACKNOWLEDGE mode. To create a Session with one of the modes listed above there is a second create method in the CMS Session interface that takes a single argument specifying the mode, lets take a look at an example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a Session with user specified Ack Mode</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ef257aa8-af41-45e8-9019-1b04f80cadf9" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a Session with user specified Ack Mode</parameter><plain-text-body>
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection() );
std::auto_ptr<cms::Session> session( connection->createSession(
cms::Session::CLIENT_ACKNOWLEDGE ) );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>As you can see there's not much difference here, just specify the mode you want for acknowledgement and you are ready to create your Session resources, in the next few section we will walk through the types of objects that you can create from a Session and show you the basics of using them.</p>
-<h2 id="CMSAPIOverview-ObjectscreatedfromCMSSession">Objects created from CMS Session</h2>
+<h2>Objects created from CMS Session</h2>
<p>In this section we cover the types of objects that are created from an instance of a CMS Session object.</p>
-<h3 id="CMSAPIOverview-CMSMessages">CMS Messages</h3>
+<h3>CMS Messages</h3>
-<p>As its name implies CMS exists to send and receive messages, so it makes sense to start by covering the message that you can send and receive using CMS. There are four main Message types supported by CMS at the the time of this writing, others may follow but we will stick to the ones that are fully supported right now. The table below shows the message type along with a brief description of the Message's use, for complete details on the interface and usage of a particular message type, see the <a shape="rect" href="api.xml">CMS API Documentation</a>.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Message Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Message </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The Message interface defines the simplest CMS Message. Unlike the rest of the CMS Messages the Message type has no body or payload, it can however contains properties set via a collection of property setters that encompass the basic types in C++. The Message interface is the root of all the Message types in CMS. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> TextMessage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The TextMessage class carries a payload consisting of a C++ string. The TextMessage interface extends the Message interface adding methods for setting and getting the payload text and retains the support for setting Message properties. Since Java Objects can't be sent to a CMS client from a JMS client directly the Text message is an ideal way to serialize the object to XML and send it to a JMS client. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> BytesMessage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The BytesMessage payload consists of a series of uninterrupted bytes which the receiver is responsible for interpreting. The BytesMessage adds methods for getting and setting byte array to the standard set of Message interface methods. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> MapMessage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The Map message payload is a set of Name / Value pairs. The Name is a C++ string type and the value is a C++ primitive type or string. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> StreamMessage<br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The Stream Message body consists of a list of self describing primitive types.  The StreamMessage interface provides accessor methods that can read and write the primitive types to/from the message.  The read methods allow primitive type conversion when the conversion would result in no loss of data.<br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table></div>
+<p>As its name implies CMS exists to send and receive messages, so it makes sense to start by covering the message that you can send and receive using CMS. There are four main Message types supported by CMS at the the time of this writing, others may follow but we will stick to the ones that are fully supported right now. The table below shows the message type along with a brief description of the Message's use, for complete details on the interface and usage of a particular message type, see the <link><page ri:content-title="API"></page><link-body>CMS API Documentation</link-body></link>.</p>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Message Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> Message </p></td><td colspan="1" rowspan="1"><p> The Message interface defines the simplest CMS Message. Unlike the rest of the CMS Messages the Message type has no body or payload, it can however contains properties set via a collection of property setters that encompass the basic types in C++. The Message interface is the root of all the Message types in CMS. </p></td></tr><tr><td colspan="1" rowspan="1"><p> TextMessage </p></td><td colspan="1" rowspan="1"><p> The TextMessage class carries a payload consisting of a C++ string. The TextMessage interface extends the Message interface adding methods for setting and getting the payload text and retains the support for setting Message properties. Since Java Objects can't be sent to a CMS client from a JMS client directly the Text message is an ideal way to serialize the object to XML and send it to a JMS client. </p></td></tr><tr><td colspan="1" rowspan="1"><p> BytesMessage </p></td><td colspan="1" rowspan="1"><p> The BytesMessage payload consists of a series of uninterrupted bytes which the receiver is responsible for interpreting. The BytesMessage adds methods for getting and setting byte array to the standard set of Message interface methods. </p></td></tr><tr><td colspan="1" rowspan="1"><p> MapMessage </p></td><td colspan="1" rowspan="1"><p> The Map message payload is a set of Name / Value pairs. The Name is a C++ string type and the value is a C++ primitive type or string. </p></td></tr><tr><td colspan="1" rowspan="1"><p> StreamMessage<br clear="none" class="atl-forced-newline"> </p></td><td colspan="1" rowspan="1"><p> The Stream Message body consists of a list of self describing primitive types.  The StreamMessage interface provides accessor methods that can read and write the primitive types to/from the message.  The read methods allow primitive type conversion when the conversion would result in no loss of data.<br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table>
<p>Now that we've seen the types of Message's we can create lets see how to actually create them and explore some of the operations that are available in the Message classes.</p>
-<h3 id="CMSAPIOverview-CreatingaMessage">Creating a Message</h3>
+<h3>Creating a Message</h3>
<p>As you may have already guessed, Messages are created using the CMS Session instance we created previously. The Session supplies methods for creating each of the four Message types we covered above. The Session is the Factory that create the providers implementation of the Message interfaces defined in CMS, it knows how to configure the internal data structures and prevents the client from being tied to the provider implementation directly, this is why we have to use the Session to create a Message object instead of creating them directly. Lets take a look at a code snippet that create a TextMessage instance and sets some properties on that Message.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a TextMessage using a CMS Session instance.</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="20593867-a42d-4dbe-8879-99132d2fb6fa" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a TextMessage using a CMS Session instance.</parameter><plain-text-body>
// Create the ConnectionFactory
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
// Create a Connection
std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection() );
@@ -142,31 +127,29 @@
std::auto_ptr<cms::TextMessage> textMessage( session->createTextMessage() );
// Set the payload
-textMessage->setText( "Payload Text" );
+textMessage->setText( "Payload Text" );
// Set some Properties
-textMessage->setStringProperty( "USER_NAME", "Steve" );
-textMessage->setIntProperty( "USER_CODE", 42 );
+textMessage->setStringProperty( "USER_NAME", "Steve" );
+textMessage->setIntProperty( "USER_CODE", 42 );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>As you can see from the code above creating a TextMessage is much like creating a Session or Connection instance, you just call the <strong>createTextMessage</strong> in your instance of a CMS Session and you get back a new TextMessage pointer that you can then populate with text and properties.</p>
-<h3 id="CMSAPIOverview-CMSDestinations">CMS Destinations</h3>
+<h3>CMS Destinations</h3>
<p>As its name implies the CMS Destination interface defines an object that represents an endpoint that the Messages are routed to by the Messaging broker. Clients create Destinations and send messages to them or wait for messages to be received on a destination they have subscribed to. There are two basic types of Destinations in CMS, the Topic and the Queue, there are two subtypes of these the Temporary Topic and Temporary Queue. The table below summarizes the four different Destination types.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Destination Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> In CMS a Topic implements publish and subscribe semantics. When you publish a message it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message. Only subscribers who had an active subscription at the time the broker receives the message will get a copy of the message. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A CMS Queue implements load balancer semantics. A single message will be received by exactly one consumer. If there are no consumers available at the time the message is sent it will be kept until a consumer is available that can process the message. If a consumer receives a message and does not acknowledge it before closing then the message will be redelivered to another consumer. A queue can have many consumers with messages load balanced across the available consumers. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> TemporaryTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A TemporaryTopic object is a unique Topic object created for the duration of a Connection. It is a system-defined topic that can be consumed only by the Connection that created it. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> TemporaryQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A TemporaryQueue object is a unique Queue object created for the duration of a Connection. It is a system-defined queue that can be consumed only by the Connection that created it. </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Destination Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> Topic </p></td><td colspan="1" rowspan="1"><p> In CMS a Topic implements publish and subscribe semantics. When you publish a message it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message. Only subscribers who had an active subscription at the time the broker receives the message will get a copy of the message. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Queue </p></td><td colspan="1" rowspan="1"><p> A CMS Queue implements load balancer semantics. A single message will be received by exactly one consumer. If there are no consumers available at the time the message is sent it will be kept until a consumer is available that can process the message. If a consumer receives a message and does not acknowledge it before closing then the message will be redelivered to another consumer. A queue can have many consumers with messages load balanced across the available consumers. </p></td></tr><tr><td colspan="1" rowspan="1"><p> TemporaryTopic </p></td><td colspan="1" rowspan="1"><p> A TemporaryTopic object is a unique Topic object created for the duration of a Connection. It is a system-defined topic that can be consumed only by the Connection that created it. </p></td></tr><tr><td colspan="1" rowspan="1"><p> TemporaryQueue </p></td><td colspan="1" rowspan="1"><p> A TemporaryQueue object is a unique Queue object created for the duration of a Connection. It is a system-defined queue that can be consumed only by the Connection that created it. </p></td></tr></tbody></table>
<p>Now that we've seen what the destination types are, lets look at a code snippet showing how to create a Destination object. The example below shows how to create a Topic instance using what should now be a pretty familiar pattern.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a Topic from a CMS Session object</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="82c12002-b7d4-40e2-a488-8822696f4fa6" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a Topic from a CMS Session object</parameter><plain-text-body>
// Create the ConnectionFactory
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
// Create a Connection
std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection() );
@@ -175,22 +158,20 @@
std::auto_ptr<cms::Session> session( connection->createSession();
// Now create a Topic
-std::auto_ptr<cms::Topic> myTopic( session->createTopic( "EXAMPLE-TOPIC" ) );
+std::auto_ptr<cms::Topic> myTopic( session->createTopic( "EXAMPLE-TOPIC" ) );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Creating a Topic or Queue requires passing a name for the Destination, the name is similar to an address, messages sent the the "EXAMPLE-TOPIC" destination are received by clients that have subscribed to that same Destination.</p>
-<h3 id="CMSAPIOverview-CMSMessageConsumer">CMS MessageConsumer</h3>
+<h3>CMS MessageConsumer</h3>
<p>Now that we've covered how to create messages and destinations we will look at creating a CMS MessageConsumer. The MessageConsumer allows the client application to receive messages sent by other clients to topics or queues. Before we talk about receiving Messages with the consumer lets first look at how one is created.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a MessageConsumer from a CMS Session object</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="769e2b5e-30f3-4fb3-8309-03bd18dd629f" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a MessageConsumer from a CMS Session object</parameter><plain-text-body>
// Create the ConnectionFactory
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
// Create a Connection
std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection() );
@@ -199,20 +180,18 @@
std::auto_ptr<cms::Session> session( connection->createSession();
// Now create a Topic
-std::auto_ptr<cms::Topic> myTopic( session->createTopic( "EXAMPLE-TOPIC" ) );
+std::auto_ptr<cms::Topic> myTopic( session->createTopic( "EXAMPLE-TOPIC" ) );
// Now create the Consumer
std::auto_ptr<cms::MessageConsumer> myConsumer( session->createConsumer( myTopic ) );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>As you can see the MessageConsumer is created by calling <strong>createConsumer</strong> from an instance of a CMS Session object. The MessageConsumer is given a Destination to listen for Messages on at the time you create it. Once you create a MessageConsumer its time to start using it to receive messages, the MessageConsumer two methods for receiving messages, one is synchronous and the other is asynchronous.</p>
<p>The synchronous method of receiving Messages involves a call the to the consumers receive method. A call to receive will block until a Message is received on the Destination in question if no time-out is given, or will return NULL if the time-out given elapses and no new Messages arrive. Lets take a look at a simple example of a synchronous message polling loop using CMS.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Synchronous Polling with infinite wait.</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f42099c3-9bf7-4874-9268-19bc8d62c3de" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Synchronous Polling with infinite wait.</parameter><plain-text-body>
while( !done ) {
std::auto_ptr<Message> message( myConsumer->receive() );
@@ -220,13 +199,11 @@
...Do Something with the message...
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>As you can see in the code above we called the MessageConsumer's <strong>receive</strong> method expecting that it will return a new Message object at some point. The code here will block until a new message is received. This sort of approach assumes that your program has nothing else that it needs to do until a message arrives, however there is an alternative should your application need to perform other processing. The code sample below shows a polling loop that uses the MessageConsumer's <strong>receiveNoWait</strong> method to poll and return immediately to allow for other processing to occur.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Synchronous Polling with no wait.</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ef3cc255-4b14-4bac-9f6c-ec4d00b4275f" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Synchronous Polling with no wait.</parameter><plain-text-body>
while( !done ) {
std::auto_ptr<Message> message( myConsumer->receiveNoWait() );
@@ -238,59 +215,53 @@
...Perform other application logic before checking for another message...
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The asynchronous method involves implementing the CMS MessageListener interface and passing an instance of your implementation to the MessageConsumer's <strong>setMessageListener</strong> method. When a new message arrives your listener's <strong>onMessage</strong> method will be called by the consumer in the context of another thread to allow you to process the Message received. Below is a code snippet that demonstrates implementing the MessageListener interface.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Simple MessageListener Implementation.</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="daec29b4-1dd6-4c30-b7a7-3418a030c4ea" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Simple MessageListener Implementation.</parameter><plain-text-body>
class SimpleListener : public cms::MessageListener {
virtual void onMessage( const Message* message ) {
const TextMessage* textMessage =
dynamic_cast< const TextMessage* >( message );
- string text = "";
+ string text = "";
if( textMessage != NULL ) {
text = textMessage->getText();
} else {
- text = "NOT A TEXTMESSAGE!";
+ text = "NOT A TEXTMESSAGE!";
}
- printf( "Message Received: %s\n", text.c_str() );
+ printf( "Message Received: %s\n", text.c_str() );
}
};
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>In the sample above we create a new class called SimpleListener that prints the contents of a TextMessage when received, or print an message indicating that it did not receive a TextMessage as it had expected to. Notice that the <strong>onMessage</strong> method receives a pointer to the base Message interface and we then attempt to dynamic cast to the type we think we should have received. This allows your code to process multiple message types in one method. The pointer passed is owned by the caller or onMessage so you shouldn't store it or delete it, if you need to keep a copy of the Message around you must create a copy by calling Message's <strong>clone</strong> method.</p>
<p>Now that we have a MessageListener implementation to work with its time to see how to setup asynchronous consumption using the MessageConsumer we created previously.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Setting up Async Consumption.</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="07dc9d75-a3de-4807-8d00-3700586ea8ea" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Setting up Async Consumption.</parameter><plain-text-body>
SimpleListener listener;
myConsumer->setMessageListener( &listener );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>That's it, we will now receive the messages sent to the Destination we created in the onMessage method of our SimpleListener instance.</p>
-<h3 id="CMSAPIOverview-CMSMessageProducer">CMS MessageProducer</h3>
+<h3>CMS MessageProducer</h3>
<p>We've seen how to consume Messages now how do we produce them in the first place? The answer is the CMS MessageProducer which is used to send messages to the broker for distribution to the various clients listening for Messages on the topic or queue. Creating a MessageProducer is much the same as creating a MessageConsumer, you first create your Connection, Session, and Destination objects then use the Session to create a MessageProducer. The code snippet below demonstrates how to create a MessageProducer.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating a MessageProducer from a CMS Session object</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="670ab2a6-abdd-4d93-b57a-c035973b7175" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating a MessageProducer from a CMS Session object</parameter><plain-text-body>
// Create the ConnectionFactory
std::auto_ptr<cms::ConnectionFactory> connectionFactory(
- cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
+ cms::ConnectionFactory::createCMSConnectionFactory( "tcp://127.0.0.1:61616" ) );
// Create a Connection
std::auto_ptr<cms::Connection> connection( connectionFactory->createConnection() );
@@ -299,19 +270,18 @@
std::auto_ptr<cms::Session> session( connection->createSession();
// Now create a Topic
-std::auto_ptr<cms::Topic> myTopic( session->createTopic( "EXAMPLE-TOPIC" ) );
+std::auto_ptr<cms::Topic> myTopic( session->createTopic( "EXAMPLE-TOPIC" ) );
// Now create the Consumer
std::auto_ptr<cms::MessageProducer> myProducer( session->createProducer( myTopic ) );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="CMSAPIOverview-CompleteExamples">Complete Examples</h2>
+<h2>Complete Examples</h2>
<p>Now that we've covered most of the basics of the CMS API its time to take a look at some complete examples that demonstrate how you might use the CMS API in your own application. The first example will show how to create a simple Asynchronous consumer that can receive TextMessage objects from an ActiveMQ broker, then in the second example we will look at a simple producer that publishes TextMessage objects to the destination that our consumer is listening on.</p>
-<h3 id="CMSAPIOverview-SimpleAsynchronousConsumer">Simple Asynchronous Consumer</h3>
+<h3>Simple Asynchronous Consumer</h3>
<p>In the Simple Asnychronous Consumer example we wrap the CMS API usage in a class called SimpleAsyncConsumer. This class exposes a single constructor that allows the user to create an instance of the class that connects to a particular broker and destination and whether the destination is a Queue or Topic. The user can also specify the Acknowledgement Mode shoukd be <strong>CLIENT_ACKNOWLEDGE</strong> instaned of the default <strong>AUTO_ACKNOWLEDGE</strong> mode.</p>
@@ -319,21 +289,20 @@
<p>After the <em>runConsumer</em> method returns the main method waits for user input to exit, all messages received while the application is running will be dispatched to the onMessage method of SimpleAsyncConsumer and if the message is a TextMessage its contents will be printed onscreen.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>A Simple Asynchronous Consumer example</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="dc030697-ea46-4a1d-a7b3-1272cc3aa953" ac:name="code" ac:schema-version="1"><parameter ac:name="title">A Simple Asynchronous Consumer example</parameter><plain-text-body>
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
+ * (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
+ * distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
@@ -467,19 +436,19 @@
count++;
const TextMessage* textMessage =
dynamic_cast< const TextMessage* >( message );
- string text = "";
+ string text = "";
if( textMessage != NULL ) {
text = textMessage->getText();
} else {
- text = "NOT A TEXTMESSAGE!";
+ text = "NOT A TEXTMESSAGE!";
}
if( clientAck ) {
message->acknowledge();
}
- printf( "Message #%d Received: %s\n", count, text.c_str() );
+ printf( "Message #%d Received: %s\n", count, text.c_str() );
} catch (CMSException& e) {
e.printStackTrace();
}
@@ -488,16 +457,16 @@
// If something bad happens you see it here as this class is also been
// registered as an ExceptionListener with the connection.
virtual void onException( const CMSException& ex AMQCPP_UNUSED ) {
- printf("CMS Exception occurred. Shutting down client.\n");
+ printf("CMS Exception occurred. Shutting down client.\n");
exit(1);
}
virtual void transportInterrupted() {
- std::cout << "The Connection's Transport has been Interrupted." << std::endl;
+ std::cout << "The Connection's Transport has been Interrupted." << std::endl;
}
virtual void transportResumed() {
- std::cout << "The Connection's Transport has been Restored." << std::endl;
+ std::cout << "The Connection's Transport has been Restored." << std::endl;
}
private:
@@ -524,9 +493,9 @@
activemq::library::ActiveMQCPP::initializeLibrary();
- std::cout << "=====================================================\n";
- std::cout << "Starting the example:" << std::endl;
- std::cout << "-----------------------------------------------------\n";
+ std::cout << "=====================================================\n";
+ std::cout << "Starting the example:" << std::endl;
+ std::cout << "-----------------------------------------------------\n";
// Set the URI to point to the IPAddress of your broker.
// add any optional params to the url to enable things like
@@ -536,14 +505,14 @@
// http://activemq.apache.org/cms/
//
std::string brokerURI =
- "failover:(tcp://127.0.0.1:61616)";
+ "failover:(tcp://127.0.0.1:61616)";
//============================================================
// This is the Destination Name and URI options. Use this to
// customize where the consumer listens, to have the consumer
- // use a topic or queue set the 'useTopics' flag.
+ // use a topic or queue set the 'useTopics' flag.
//============================================================
- std::string destURI = "TEST.FOO"; //?consumer.prefetchSize=1";
+ std::string destURI = "TEST.FOO"; //?consumer.prefetchSize=1";
//============================================================
// set to true to use topics instead of queues
@@ -565,41 +534,39 @@
consumer.runConsumer();
// Wait to exit.
- std::cout << "Press 'q' to quit" << std::endl;
- while( std::cin.get() != 'q') {}
+ std::cout << "Press 'q' to quit" << std::endl;
+ while( std::cin.get() != 'q') {}
// All CMS resources should be closed before the library is shutdown.
consumer.close();
- std::cout << "-----------------------------------------------------\n";
- std::cout << "Finished with the example." << std::endl;
- std::cout << "=====================================================\n";
+ std::cout << "-----------------------------------------------------\n";
+ std::cout << "Finished with the example." << std::endl;
+ std::cout << "=====================================================\n";
activemq::library::ActiveMQCPP::shutdownLibrary();
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="CMSAPIOverview-SimpleProducer">Simple Producer</h3>
+<h3>Simple Producer</h3>
<p>Much like the Simple Asynchronous Consumer example the Simple Producer example wraps up the CMS API detials needed to create a producer into a class called <strong>SimpleProducer</strong>. This class exposes a simillar interface to the consumer example, there is one constructor that allows an instance to be created with configuration options for the broker and destination as well as the number of messages to send to the configured destination. Once created the client code simply calls the SimpleProducer's <em>run</em> method to publish the specified number of messages. Once the <em>run</em> method completes the client is free to close the SimpleProducer which cleans up the allocated CMS resources, once closed the application exits.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>A Simple Message Producer Example</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0d0c2d3d-e292-4807-8c9c-feb8c733c7e5" ac:name="code" ac:schema-version="1"><parameter ac:name="title">A Simple Message Producer Example</parameter><plain-text-body>
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
+ * (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
+ * distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
@@ -714,15 +681,15 @@
string threadIdStr = Long::toString( Thread::currentThread()->getId() );
// Create a messages
- string text = (string)"Hello world! from thread " + threadIdStr;
+ string text = (string)"Hello world! from thread " + threadIdStr;
for( unsigned int ix=0; ix<numMessages; ++ix ){
TextMessage* message = session->createTextMessage( text );
- message->setIntProperty( "Integer", ix );
+ message->setIntProperty( "Integer", ix );
// Tell the producer to send the message
- printf( "Sent message #%d from thread %s\n", ix+1, threadIdStr.c_str() );
+ printf( "Sent message #%d from thread %s\n", ix+1, threadIdStr.c_str() );
producer->send( message );
delete message;
@@ -757,9 +724,9 @@
activemq::library::ActiveMQCPP::initializeLibrary();
- std::cout << "=====================================================\n";
- std::cout << "Starting the example:" << std::endl;
- std::cout << "-----------------------------------------------------\n";
+ std::cout << "=====================================================\n";
+ std::cout << "Starting the example:" << std::endl;
+ std::cout << "-----------------------------------------------------\n";
// Set the URI to point to the IPAddress of your broker.
// add any optional params to the url to enable things like
@@ -769,7 +736,7 @@
// http://activemq.apache.org/cms/
//
std::string brokerURI =
- "failover://(tcp://127.0.0.1:61616)";
+ "failover://(tcp://127.0.0.1:61616)";
//============================================================
// Total number of messages for this producer to send.
@@ -779,9 +746,9 @@
//============================================================
// This is the Destination Name and URI options. Use this to
// customize where the Producer produces, to have the producer
- // use a topic or queue set the 'useTopics' flag.
+ // use a topic or queue set the 'useTopics' flag.
//============================================================
- std::string destURI = "TEST.FOO";
+ std::string destURI = "TEST.FOO";
//============================================================
// set to true to use topics instead of queues
@@ -799,13 +766,12 @@
// Before exiting we ensure that all CMS resources are closed.
producer.close();
- std::cout << "-----------------------------------------------------\n";
- std::cout << "Finished with the example." << std::endl;
- std::cout << "=====================================================\n";
+ std::cout << "-----------------------------------------------------\n";
+ std::cout << "Finished with the example." << std::endl;
+ std::cout << "=====================================================\n";
activemq::library::ActiveMQCPP::shutdownLibrary();
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/cms/community.xml b/cms/community.xml
index dbc08cb..f854489 100644
--- a/cms/community.xml
+++ b/cms/community.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="faq.xml">FAQ</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-cpp-usage-faqs.xml">ActiveMQ-CPP Usage FAQs</a><ul class="childpages-macro"><li><a shape="rect" href="how-do-i-use-the-ssl-transport.xml">How do I use the SSL Transport</a></li></ul></li><li><a shape="rect" href="building-faqs.xml">Building FAQs</a><ul class="childpages-macro"><li><a shape="rect" href="general-build-issues.xml">General Build Issues</a></li><li><a shape="rect" href="openssl-support.xml">OpenSSL Support</a><ul class="childpages-macro"><li><a shape="rect" href="enable-openssl-support-with-autotools.xml">Enable OpenSSL support with autotools</a></li><li><a shape="rect" href="how-do-i-prevent-autoconf-from-enabling-openssl-support.xml">How do I prevent autoconf from enabling OpenSSL support</a></li><li><a shape="rect" href="how-to-enable-ssl-support-on-windows.xml">How to enable SSL support on Windows</a></li></ul></li><li><a shape="rect" href="solaris-platform.xml">Solaris Platform</a><ul class="childpages-macro"><li><a shape="rect" href="errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml">Errors from libstd++.la on Solaris 10 using the GNU Compiler</a></li><li><a shape="rect" href="errors-saying-no-rule-to-make-target.xml">Errors saying "no rule to make target"</a></li><li><a shape="rect" href="using-the-solaris-cc-compiler.xml">Using the Solaris CC compiler</a></li></ul></li></ul></li><li><a shape="rect" href="discussion-forums.xml">Discussion Forums</a><ul class="childpages-macro"><li><a shape="rect" href="mailing-lists.xml">Mailing Lists</a></li></ul></li><li><a shape="rect" href="general.xml">General</a><ul class="childpages-macro"><li><a shape="rect" href="are-there-more-faq-entries.xml">Are there more FAQ Entries</a></li><li><a shape="rect" href="what-is-activemq-cpp.xml">What is ActiveMQ CPP</a></li></ul></li></ul></li><li><a shape="rect" href="privacy-policy.xml">Privacy Policy</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="4c6961d7-0f3c-42c8-9edb-3800f09ff65b" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/cms/configuring.xml b/cms/configuring.xml
index 4811a50..c7b660a 100644
--- a/cms/configuring.xml
+++ b/cms/configuring.xml
@@ -1,96 +1,91 @@
-<div class="wiki-content maincontent"><h2 id="Configuring-ConfiguringActiveMQ-CPP">Configuring ActiveMQ-CPP</h2>
+<div class="wiki-content maincontent"><h2>Configuring ActiveMQ-CPP</h2>
<p>The configuration of ActiveMQ is so slick, we decided to take a similar approach with ActiveMQ-CPP. All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every facet of your ActiveMQ-CPP client. The tables below show the comprehensive set of parameters.</p>
-<h3 id="Configuring-ConnectionURIParameters"><strong>Connection URI Parameters</strong></h3>
+<h3><strong>Connection URI Parameters</strong></h3>
-<h5 id="Configuring-ExampleConfiguration"> Example Configuration</h5>
+<h5> Example Configuration</h5>
<p>This first example uses a standard TCP based transport.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9a908a3e-b888-4657-a1af-6db14b3832ae" ac:name="code" ac:schema-version="1"><plain-text-body>
cf = new ActiveMQConnectionFactory(
- "tcp://localhost:61616?wireFormat=openwire&wireFormat.tightEncodingEnabled=true");
-]]></script>
-</div></div>
+ "tcp://localhost:61616?wireFormat=openwire&wireFormat.tightEncodingEnabled=true");
+</plain-text-body></structured-macro>
<p>For a more reliable connection use the Failover Transport and configure in alternate locations to connect to.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ce34d2df-d2e2-402a-af17-ff1c373639a2" ac:name="code" ac:schema-version="1"><plain-text-body>
cf = new ActiveMQConnectionFactory(
- "failover://(tcp://localhost:61616,tcp://anotherhost:61616)?connection.useAsyncSend=true");
-]]></script>
-</div></div>
+ "failover://(tcp://localhost:61616,tcp://anotherhost:61616)?connection.useAsyncSend=true");
+</plain-text-body></structured-macro>
-<h3 id="Configuring-ProtocolOptions">Protocol Options</h3>
+<h3>Protocol Options</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option Name <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tcp </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses TCP/IP Sockets to connect to the broker. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ssl </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses OpenSSL to secure TCP/IP sockets. <strong>(Since v3.2.0)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> failover </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Composite of other Transports, when a Transport connection fails, the Failover Transport connects to the next Transport in the list or retries the connection to the failed broker URI. </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> tcp </p></td><td colspan="1" rowspan="1"><p> Uses TCP/IP Sockets to connect to the broker. </p></td></tr><tr><td colspan="1" rowspan="1"><p> ssl </p></td><td colspan="1" rowspan="1"><p> Uses OpenSSL to secure TCP/IP sockets. <strong>(Since v3.2.0)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> failover </p></td><td colspan="1" rowspan="1"><p> Composite of other Transports, when a Transport connection fails, the Failover Transport connects to the next Transport in the list or retries the connection to the failed broker URI. </p></td></tr></tbody></table>
-<h4 id="Configuring-SocketOptions"><strong>Socket Options</strong></h4>
+<h4><strong>Socket Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inputBufferSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 10000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The number of bytes in the buffered input stream's buffer </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outputBufferSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 10000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The number of bytes in the buffered output stream's buffer </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> soLinger </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Socket SOLinger value </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> soKeepAlive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Socket SOKeepAlive value </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> soReceiveBufferSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> -1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Socket receive buffer. If -1, use OS default. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> soSendBufferSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> -1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Socket send buffer. If -1, use OS default. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> soConnectTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> -1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Socket connection timeout in microseconds. If -1, use OS default. <strong>(Since ActiveMQ-CPP 2.2)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tcpNoDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets the Socket level TCP_NODELAY option </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> inputBufferSize </p></td><td colspan="1" rowspan="1"><p> 10000 </p></td><td colspan="1" rowspan="1"><p> The number of bytes in the buffered input stream's buffer </p></td></tr><tr><td colspan="1" rowspan="1"><p> outputBufferSize </p></td><td colspan="1" rowspan="1"><p> 10000 </p></td><td colspan="1" rowspan="1"><p> The number of bytes in the buffered output stream's buffer </p></td></tr><tr><td colspan="1" rowspan="1"><p> soLinger </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Socket SOLinger value </p></td></tr><tr><td colspan="1" rowspan="1"><p> soKeepAlive </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Socket SOKeepAlive value </p></td></tr><tr><td colspan="1" rowspan="1"><p> soReceiveBufferSize </p></td><td colspan="1" rowspan="1"><p> -1 </p></td><td colspan="1" rowspan="1"><p> Socket receive buffer. If -1, use OS default. </p></td></tr><tr><td colspan="1" rowspan="1"><p> soSendBufferSize </p></td><td colspan="1" rowspan="1"><p> -1 </p></td><td colspan="1" rowspan="1"><p> Socket send buffer. If -1, use OS default. </p></td></tr><tr><td colspan="1" rowspan="1"><p> soConnectTimeout </p></td><td colspan="1" rowspan="1"><p> -1 </p></td><td colspan="1" rowspan="1"><p> Socket connection timeout in microseconds. If -1, use OS default. <strong>(Since ActiveMQ-CPP 2.2)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> tcpNoDelay </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Sets the Socket level TCP_NODELAY option </p></td></tr></tbody></table>
-<h4 id="Configuring-GeneralTransportOptions"><strong>General Transport Options</strong></h4>
+<h4><strong>General Transport Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.commandTracingEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If true, enables tracing of incoming and outgoing transport commands </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.tcpTracingEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If true, enables tracing of raw network IO (in hex) </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.useAsyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If true, enables asynchronous sending of messages. *<strong>WARNING: Using this could result in a loss of data if messages are pending and the client is shut down or crashes.</strong>* <strong>(Deprecated Since ActiveMQ-CPP 2.2.2 has no effect as of this release, use connection.useAsyncSend instead)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.ResponseCorrelator.maxResponseWaitTime </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 3000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Milliseconds to wait for responses from the broker. <strong>(Removed as of ActiveMQ-CPP 2.2.1, use connection.sendTimeout instead)</strong> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> transport.commandTracingEnabled </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> If true, enables tracing of incoming and outgoing transport commands </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.tcpTracingEnabled </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> If true, enables tracing of raw network IO (in hex) </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.useAsyncSend </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> If true, enables asynchronous sending of messages. *<strong>WARNING: Using this could result in a loss of data if messages are pending and the client is shut down or crashes.</strong>* <strong>(Deprecated Since ActiveMQ-CPP 2.2.2 has no effect as of this release, use connection.useAsyncSend instead)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.ResponseCorrelator.maxResponseWaitTime </p></td><td colspan="1" rowspan="1"><p> 3000 </p></td><td colspan="1" rowspan="1"><p> Milliseconds to wait for responses from the broker. <strong>(Removed as of ActiveMQ-CPP 2.2.1, use connection.sendTimeout instead)</strong> </p></td></tr></tbody></table>
-<h4 id="Configuring-FailoverTransportOptions"><strong>Failover Transport Options</strong></h4>
+<h4><strong>Failover Transport Options</strong></h4>
-<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 </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 if the initial attempt to connect to the broker fails. </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> Maximum time that the transport waits before trying to connect to the Broker again. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExponentialBackOff </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the delay between connection attempt grow on each try up to the max reconnect delay </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxReconnectAttempts </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Max number of times to attempt to reconnect before failing the transport, default is forever (0). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> startupMaxReconnectAttempts </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Max number of times to attempt to reconnect before failing the transport, default is forever (0). Only applies during the initial attempt to connect, after one successful connection the <em>maxReconnectAttempts</em> flag applies from then on. <strong>(Since v3.2.0)</strong></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> Should the transport attempt to connect to the listed Broker URI's in Random order. </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> Should the Failover transport maintain hot backups. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> backupPoolSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If enabled, how many hot backup connections are made. </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> If a send is blocked waiting on a failed connection to reconnect how long should it wait before failing the send, default is forever (-1). </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> initialReconnectDelay </p></td><td colspan="1" rowspan="1"><p> 10 </p></td><td colspan="1" rowspan="1"><p> How long to wait if the initial attempt to connect to the broker fails. </p></td></tr><tr><td colspan="1" rowspan="1"><p> maxReconnectDelay </p></td><td colspan="1" rowspan="1"><p> 30000 </p></td><td colspan="1" rowspan="1"><p> Maximum time that the transport waits before trying to connect to the Broker again. </p></td></tr><tr><td colspan="1" rowspan="1"><p> useExponentialBackOff </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Should the delay between connection attempt grow on each try up to the max reconnect delay </p></td></tr><tr><td colspan="1" rowspan="1"><p> maxReconnectAttempts </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Max number of times to attempt to reconnect before failing the transport, default is forever (0). </p></td></tr><tr><td colspan="1" rowspan="1"><p> startupMaxReconnectAttempts </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Max number of times to attempt to reconnect before failing the transport, default is forever (0). Only applies during the initial attempt to connect, after one successful connection the <em>maxReconnectAttempts</em> flag applies from then on. <strong>(Since v3.2.0)</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p> randomize </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Should the transport attempt to connect to the listed Broker URI's in Random order. </p></td></tr><tr><td colspan="1" rowspan="1"><p> backup </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should the Failover transport maintain hot backups. </p></td></tr><tr><td colspan="1" rowspan="1"><p> backupPoolSize </p></td><td colspan="1" rowspan="1"><p> 1 </p></td><td colspan="1" rowspan="1"><p> If enabled, how many hot backup connections are made. </p></td></tr><tr><td colspan="1" rowspan="1"><p> timeout </p></td><td colspan="1" rowspan="1"><p> -1 </p></td><td colspan="1" rowspan="1"><p> If a send is blocked waiting on a failed connection to reconnect how long should it wait before failing the send, default is forever (-1). </p></td></tr></tbody></table>
-<h4 id="Configuring-TransactionOptions"><strong>Transaction Options</strong></h4>
+<h4><strong>Transaction Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transaction.maxRedeliveryCount </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 5 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Maximum number of redelivery attempts. <strong>(Removed in v3.2.0, see instead Connection Redelivery Policy)</strong></p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> transaction.maxRedeliveryCount </p></td><td colspan="1" rowspan="1"><p> 5 </p></td><td colspan="1" rowspan="1"><p> Maximum number of redelivery attempts. <strong>(Removed in v3.2.0, see instead Connection Redelivery Policy)</strong></p></td></tr></tbody></table>
-<h4 id="Configuring-ConnectionOptions"><strong>Connection Options</strong></h4>
+<h4><strong>Connection Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.sendTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Time to wait on Message Sends for a Response, default value of zero indicates to wait forever. Waiting forever allows the broker to have flow control over messages coming from this client if it is a fast producer or there is no consumer such that the broker would run out of memory if it did not slow down the producer. <strong>Does not affect Stomp clients as the sends are ack'd by the broker.</strong> <strong>(Since ActiveMQ-CPP 2.2.1)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.producerWindowSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The ProducerWindowSize is the maximum number of bytes in memory that a producer will transmit to a broker before waiting for acknowledgement messages from the broker that it has accepted the previously sent messages. In other words, this how you configure the producer flow control window that is used for async sends where the client is responsible for managing memory usage. The default value of 0 means no flow control at the client. See also <a shape="rect" class="external-link" href="http://activemq.apache.org/producer-flow-control.html">Producer Flow Control</a>. <strong>This option only affects Openwire clients as Stomp does not have a means of notifying the clients of accepted messages asynchronously</strong>. <strong>(Since ActiveMQ-CPP 2.2.2)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connnection.closeTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 15000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The amount of time to wait for a response from the broker when shutting down. Normally we want a response to indicate that the client has been disconnected cleanly, but we don't want to wait forever, however if you do, set this to zero. <strong>(Since ActiveMQ-CPP 2.2.1)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.useAsyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Forces the use of 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. Normally only Persistant messages that are not part of a transaction are sent synchronously, using this options forces those messages to also be async. <strong>(</strong><strong>Since ActiveMQ-CPP 2.2.2</strong><strong>)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.alwaysSyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Forces all messages that are sent to be sent synchronously overriding any usage of the useAsyncSend flag. This can reduce performance in some cases since the only messages we normally send synchronously are Persistent messages not sent in a transaction. This options guarantees that no send will return until the broker has acknowledge receipt of the message. <strong>(</strong><strong>Since ActiveMQ-CPP 2.2.2</strong><strong>)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.useCompression </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should outgoing messages have their body portion compressed using the ZLib compression algorithms <strong>(Since v3.2.0)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the broker <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the consumer, this causes all consumers from this Connection to use this setting. <strong>(Since v3.2.0)</strong> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> connection.sendTimeout </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Time to wait on Message Sends for a Response, default value of zero indicates to wait forever. Waiting forever allows the broker to have flow control over messages coming from this client if it is a fast producer or there is no consumer such that the broker would run out of memory if it did not slow down the producer. <strong>Does not affect Stomp clients as the sends are ack'd by the broker.</strong> <strong>(Since ActiveMQ-CPP 2.2.1)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.producerWindowSize </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> The ProducerWindowSize is the maximum number of bytes in memory that a producer will transmit to a broker before waiting for acknowledgement messages from the broker that it has accepted the previously sent messages. In other words, this how you configure the producer flow control window that is used for async sends where the client is responsible for managing memory usage. The default value of 0 means no flow control at the client. See also <a shape="rect" href="http://activemq.apache.org/producer-flow-control.html">Producer Flow Control</a>. <strong>This option only affects Openwire clients as Stomp does not have a means of notifying the clients of accepted messages asynchronously</strong>. <strong>(Since ActiveMQ-CPP 2.2.2)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> connnection.closeTimeout </p></td><td colspan="1" rowspan="1"><p> 15000 </p></td><td colspan="1" rowspan="1"><p> The amount of time to wait for a response from the broker when shutting down. Normally we want a response to indicate that the client has been disconnected cleanly, but we don't want to wait forever, however if you do, set this to zero. <strong>(Since ActiveMQ-CPP 2.2.1)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.useAsyncSend </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Forces the use of 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. Normally only Persistant messages that are not part of a transaction are sent synchronously, using this options forces those messages to also be async. <strong>(</strong><strong>Since ActiveMQ-CPP 2.2.2</strong><strong>)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.alwaysSyncSend </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Forces all messages that are sent to be sent synchronously overriding any usage of the useAsyncSend flag. This can reduce performance in some cases since the only messages we normally send synchronously are Persistent messages not sent in a transaction. This options guarantees that no send will return until the broker has acknowledge receipt of the message. <strong>(</strong><strong>Since ActiveMQ-CPP 2.2.2</strong><strong>)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.useCompression </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should outgoing messages have their body portion compressed using the ZLib compression algorithms <strong>(Since v3.2.0)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.dispatchAsync </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Should the broker <a shape="rect" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the consumer, this causes all consumers from this Connection to use this setting. <strong>(Since v3.2.0)</strong> </p></td></tr></tbody></table>
-<h5 id="Configuring-ConnectionPolicyOptions"><strong>Connection Policy Options</strong></h5>
+<h5><strong>Connection Policy Options</strong></h5>
<p>As of version 3.2.0 the Connection object supports policies that control various aspects its behaviour and of the Consumer objects it creates.</p>
-<h6 id="Configuring-PrefetchPolicy">Prefetch Policy</h6>
+<h6>Prefetch Policy</h6>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.PrefetchPolicy.durableTopicPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 100 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Max prefetch for Durable Topics </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.PrefetchPolicy.queueBrowserPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 500 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Max prefetch for a Queue Browser </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.PrefetchPolicy.queuePrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Max prefetch for a Queue or Temp Queue </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.PrefetchPolicy.topicPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 65535 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Max prefetch for a Topic or Temp Topic </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> cms.PrefetchPolicy.durableTopicPrefetch </p></td><td colspan="1" rowspan="1"><p> 100 </p></td><td colspan="1" rowspan="1"><p> Max prefetch for Durable Topics </p></td></tr><tr><td colspan="1" rowspan="1"><p> cms.PrefetchPolicy.queueBrowserPrefetch </p></td><td colspan="1" rowspan="1"><p> 500 </p></td><td colspan="1" rowspan="1"><p> Max prefetch for a Queue Browser </p></td></tr><tr><td colspan="1" rowspan="1"><p> cms.PrefetchPolicy.queuePrefetch </p></td><td colspan="1" rowspan="1"><p> 1000 </p></td><td colspan="1" rowspan="1"><p> Max prefetch for a Queue or Temp Queue </p></td></tr><tr><td colspan="1" rowspan="1"><p> cms.PrefetchPolicy.topicPrefetch </p></td><td colspan="1" rowspan="1"><p> 65535 </p></td><td colspan="1" rowspan="1"><p> Max prefetch for a Topic or Temp Topic </p></td></tr></tbody></table>
-<h6 id="Configuring-RedeliveryPolicy">Redelivery Policy</h6>
+<h6>Redelivery Policy</h6>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.RedeliveryPolicy.backOffMultiplier </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 5.0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Used to extend the redelivery window when the _useExponentialBackOff option is enabled. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.RedeliveryPolicy.collisionAvoidancePercent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 15 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Percentage of randomness to add to redelivery backoff to keep multiple consumers in a rollback from redelivering at the same time. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.RedeliveryPolicy.initialRedeliveryDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Amount of time to wait before starting redeliveries, in milliseconds. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.RedeliveryPolicy.maximumRedeliveries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 6 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Maximum number of time to attempt a redelivery before giving up and NAck'ing the message. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.RedeliveryPolicy.useCollisionAvoidance </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the Random avoidance percentage be added into the redelivery delay. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cms.RedeliveryPolicy.useExponentialBackOff </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should redeliveries be slowed on each cycle. </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> cms.RedeliveryPolicy.backOffMultiplier </p></td><td colspan="1" rowspan="1"><p> 5.0 </p></td><td colspan="1" rowspan="1"><p> Used to extend the redelivery window when the _useExponentialBackOff option is enabled. </p></td></tr><tr><td colspan="1" rowspan="1"><p> cms.RedeliveryPolicy.collisionAvoidancePercent </p></td><td colspan="1" rowspan="1"><p> 15 </p></td><td colspan="1" rowspan="1"><p> Percentage of randomness to add to redelivery backoff to keep multiple consumers in a rollback from redelivering at the same time. </p></td></tr><tr><td colspan="1" rowspan="1"><p> cms.RedeliveryPolicy.initialRedeliveryDelay </p></td><td colspan="1" rowspan="1"><p> 1000 </p></td><td colspan="1" rowspan="1"><p> Amount of time to wait before starting redeliveries, in milliseconds. </p></td></tr><tr><td colspan="1" rowspan="1"><p> cms.RedeliveryPolicy.maximumRedeliveries </p></td><td colspan="1" rowspan="1"><p> 6 </p></td><td colspan="1" rowspan="1"><p> Maximum number of time to attempt a redelivery before giving up and NAck'ing the message. </p></td></tr><tr><td colspan="1" rowspan="1"><p> cms.RedeliveryPolicy.useCollisionAvoidance </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should the Random avoidance percentage be added into the redelivery delay. </p></td></tr><tr><td colspan="1" rowspan="1"><p> cms.RedeliveryPolicy.useExponentialBackOff </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should redeliveries be slowed on each cycle. </p></td></tr></tbody></table>
-<h4 id="Configuring-WireFormatProtocolOptions"><strong>Wire Format Protocol Options</strong></h4>
+<h4><strong>Wire Format Protocol Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> openwire </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Selects the wire format to use. Out of the box, can be either stomp or openwire. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.stackTraceEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the stack trace of exception that occur on the broker be sent to the client? Only used by openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.cacheEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should commonly repeated values be cached so that less marshalling occurs? Only used by openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.tcpNoDelayEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Does not affect the wire format, but provides a hint to the peer that TCP nodelay should be enabled on the communications Socket. Only used by openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.sizePrefixDisabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should serialized messages include a payload length prefix? Only used by openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.tightEncodingEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should wire size be optimized over CPU usage? Only used by the openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.maxInactivityDuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 30000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum inactivity duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to appear to die, so we allow the broker to kill connections if they are inactive for a period of time. Use by some transports to enable a keep alive heart beat feature. Set to a value <= 0 to disable inactivity monitoring. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxInactivityDurationInitalDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 10000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The initial delay in starting the maximum inactivity checks (and, yes, the word 'Inital' is supposed to be misspelled like that) </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> wireFormat </p></td><td colspan="1" rowspan="1"><p> openwire </p></td><td colspan="1" rowspan="1"><p> Selects the wire format to use. Out of the box, can be either stomp or openwire. </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.stackTraceEnabled </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should the stack trace of exception that occur on the broker be sent to the client? Only used by openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.cacheEnabled </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should commonly repeated values be cached so that less marshalling occurs? Only used by openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.tcpNoDelayEnabled </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Does not affect the wire format, but provides a hint to the peer that TCP nodelay should be enabled on the communications Socket. Only used by openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.sizePrefixDisabled </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should serialized messages include a payload length prefix? Only used by openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.tightEncodingEnabled </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should wire size be optimized over CPU usage? Only used by the openwire protocol. </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.maxInactivityDuration </p></td><td colspan="1" rowspan="1"><p> 30000 </p></td><td colspan="1" rowspan="1"><p> The maximum inactivity duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to appear to die, so we allow the broker to kill connections if they are inactive for a period of time. Use by some transports to enable a keep alive heart beat feature. Set to a value <= 0 to disable inactivity monitoring. </p></td></tr><tr><td colspan="1" rowspan="1"><p> maxInactivityDurationInitalDelay </p></td><td colspan="1" rowspan="1"><p> 10000 </p></td><td colspan="1" rowspan="1"><p> The initial delay in starting the maximum inactivity checks (and, yes, the word 'Inital' is supposed to be misspelled like that) </p></td></tr></tbody></table>
-<h3 id="Configuring-DestinationURIParameters"><strong>Destination URI Parameters</strong></h3>
+<h3><strong>Destination URI Parameters</strong></h3>
-<h5 id="Configuring-ExampleConfiguration.1">Example Configuration</h5>
+<h5>Example Configuration</h5>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-d = session->createTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="f6141dc2-cae3-47c9-9a43-87c6b026a5ea" ac:name="code" ac:schema-version="1"><plain-text-body>
+d = session->createTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
+</plain-text-body></structured-macro>
-<h4 id="Configuring-GeneralOptions"><strong>General Options</strong></h4>
+<h4><strong>General Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The number of message the consumer will <a shape="rect" class="external-link" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.maximumPendingMessageLimit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use to control if messages are dropped if a <a shape="rect" class="external-link" href="http://activemq.apache.org/slow-consumer-handling.html">slow consumer</a> situation exists. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.noLocal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the broker <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the consumer. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.retroactive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Is this a <a shape="rect" class="external-link" href="http://activemq.apache.org/retroactive-consumer.html">Retroactive Consumer</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> JMS Selector used with the consumer. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.exclusive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Is this an <a shape="rect" class="external-link" href="http://activemq.apache.org/exclusive-consumer.html">Exclusive Consumer</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.priority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Allows you to configure a <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-priority.html">Consumer Priority</a>. </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer.prefetchSize </p></td><td colspan="1" rowspan="1"><p> 1000 </p></td><td colspan="1" rowspan="1"><p> The number of message the consumer will <a shape="rect" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch</a>. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.maximumPendingMessageLimit </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Use to control if messages are dropped if a <a shape="rect" href="http://activemq.apache.org/slow-consumer-handling.html">slow consumer</a> situation exists. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.noLocal </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.dispatchAsync </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should the broker <a shape="rect" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the consumer. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.retroactive </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Is this a <a shape="rect" href="http://activemq.apache.org/retroactive-consumer.html">Retroactive Consumer</a>. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.selector </p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> JMS Selector used with the consumer. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.exclusive </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Is this an <a shape="rect" href="http://activemq.apache.org/exclusive-consumer.html">Exclusive Consumer</a>. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.priority </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Allows you to configure a <a shape="rect" href="http://activemq.apache.org/consumer-priority.html">Consumer Priority</a>. </p></td></tr></tbody></table>
-<h4 id="Configuring-OpenWire-onlyOptions"><strong>OpenWire-only Options</strong></h4>
+<h4><strong>OpenWire-only Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.browser </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.networkSubscription </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.optimizedAcknowledge </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Enables an optimised acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode for the consumers which can often be faster. <strong>WARNING</strong> enabling this issue could cause some issues with auto-acknowledgement on reconnection </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.noRangeAcks </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.retroactive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started. </p></td></tr></tbody></table></div></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer.browser </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.networkSubscription </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.optimizedAcknowledge </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Enables an optimised acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode for the consumers which can often be faster. <strong>WARNING</strong> enabling this issue could cause some issues with auto-acknowledgement on reconnection </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.noRangeAcks </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.retroactive </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started. </p></td></tr></tbody></table>
+</div>
diff --git a/cms/connectivity.xml b/cms/connectivity.xml
index 24cc369..f88b162 100644
--- a/cms/connectivity.xml
+++ b/cms/connectivity.xml
@@ -1,4 +1,5 @@
<div class="wiki-content maincontent"><p>ActiveMQ-CPP has been designed to have a pluggable connector architecture. Out of the box, it comes with support for the following protocols:</p>
-<ul class="alternate"><li><a shape="rect" href="stomp-support.xml">Stomp</a></li><li><a shape="rect" href="openwire-support.xml">OpenWire</a></li></ul></div>
+<ul class="alternate"><li><link><page ri:content-title="Stomp Support"></page><link-body>Stomp</link-body></link></li><li><link><page ri:content-title="OpenWire Support"></page><link-body>OpenWire</link-body></link></li></ul>
+</div>
diff --git a/cms/creating-distributions.xml b/cms/creating-distributions.xml
index c1c4f30..e9010de 100644
--- a/cms/creating-distributions.xml
+++ b/cms/creating-distributions.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><h2 id="CreatingDistributions-CreatingaDistributionofActiveMQ-CPP">Creating a Distribution of ActiveMQ-CPP</h2>
+<div class="wiki-content maincontent"><h2>Creating a Distribution of ActiveMQ-CPP</h2>
<p>This should give you an idea of the steps involved with creating a new distribution of ActiveMQ-CPP. This content was extracted from <a shape="rect" class="external-link" href="http://www.apache.org/dev/mirror-guide-bodewig.html">http://www.apache.org/dev/mirror-guide-bodewig.html</a>, so you may want to reference that for more information.</p>
-<h3 id="CreatingDistributions-ALittleBackgroundInfo...">A Little Background Info ...</h3>
+<h3>A Little Background Info ...</h3>
<p>Apache mirrors everything under /www.www.apache.org/dist. We have had the infrastructure team add a directory under there for activemq. All you need in order to write to this directory is to be a member of the activemq group. If you're not, you'll have to create an infrastructure issue to get yourself added. Under the dir activemq, there is a directory activemq-cpp/source for the source distributions of ActiveMQ-CPP.</p>
<p>Under the source dir, we just drop the archive files (*.zip, *.tar.gz, *.zip.asc, *.tar.gz.asc) for the release versions. (NOTE: After you add files here, you should wait about 24 hours before notifying the lists since it takes a while for all the mirrors to pick up the files).</p>
@@ -17,61 +17,58 @@
<p>... and click on one of the archives. You'll be taken to a generic-looking download page.</p>
-<p>Like I said, this is a quick and dirty for now, but it works! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>Like I said, this is a quick and dirty for now, but it works! <emoticon ac:name="smile"></emoticon></p>
-<h3 id="CreatingDistributions-Productversion,interfaceversionandpackagename">Product version, interface version and package name</h3>
+<h3>Product version, interface version and package name</h3>
-<p>The page <a shape="rect" href="activemq-cpp-product-version-number.xml">ActiveMQ-CPP product version number</a> has been created to specify the way version numbers are used in the project, with some examples.</p>
+<p>The page <link><page ri:content-title="ActiveMQ-CPP product version number"></page></link> has been created to specify the way version numbers are used in the project, with some examples.</p>
-<p><a shape="rect" href="activemq-cpp-libtool-and-packaging-notes.xml">ActiveMQ-CPP, libtool and packaging notes</a> discusses the way version numbers impact libtool and packaging, and make some recommendations for this project.</p>
+<p><link><page ri:content-title="ActiveMQ-CPP, libtool and packaging notes"></page></link> discusses the way version numbers impact libtool and packaging, and make some recommendations for this project.</p>
-<h3 id="CreatingDistributions-CreatingaDistribution(step-by-step)">Creating a Distribution (step-by-step)</h3>
+<h3>Creating a Distribution (step-by-step)</h3>
<ul><li>Create a pre-release download page for your distribution. This should have a disclaimer that the release is not yet official and should have a temporary link to a pre-release distribution. For the pre-release, you do not need to have both zip and tar.gz, but a detached signature file (.asc) file should accompany any distribution. Below is an example of the disclaimer that should appear at the top of the download page:</li></ul>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">The Release is still in progress</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<structured-macro ac:macro-id="dff08b99-9f5f-48f8-97b2-e641c7c4aeb0" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">The Release is still in progress</parameter><rich-text-body>
<p> You are previewing the release page for unreleased version of yadda. The download links on the page below may not work until it is officially released.</p>
<p> Until the release is approved you could try the current source bundle:<br clear="none">
- <a shape="rect" class="external-link" href="http://people.apache.org/~myaccount/yadda.zip">http://people.apache.org/~myaccount/yadda.zip</a></p></div></div>
+ <a shape="rect" href="http://people.apache.org/~myaccount/yadda.zip">http://people.apache.org/~myaccount/yadda.zip</a></p></rich-text-body></structured-macro>
<p>Here is the Wiki Test for the above:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>{warning:title=The Release is still in progress}
+<structured-macro ac:macro-id="d1a0132f-2605-47fd-8dfb-8f025c1033e5" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+{warning:title=The Release is still in progress}
You are previewing the release page for unreleased version of yadda. The download links on the page below may not work until it is officially released.
Until the release is approved you could try the current source bundle:
[http://people.apache.org/~myaccount/yadda.zip]
{warning}
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
-<ul><li>Call a vote on the release of the distribution. This email typically has <p>[VOTE]</p> in the subject line and should provide a link to the download page and the pre-release distribution.</li><li>Wait 3 days. If there >= 3 +1's and no -1's, you can proceed with the release.</li><li>Create all of the distributions of the source (*.zip, *.tar.gz). Make sure that you remove the .svn directories from the directory before you create the archives. On *nix, this can be done with the command:</li></ul>
+<ul><li>Call a vote on the release of the distribution. This email typically has <p><structured-macro ac:macro-id="a3ebd840-af2e-420f-b8f4-66e95fa1dbb9" ac:name="html" ac:schema-version="1"><parameter ac:name="nopanel">true</parameter><plain-text-body>[VOTE]</plain-text-body></structured-macro></p> in the subject line and should provide a link to the download page and the pre-release distribution.</li><li>Wait 3 days. If there >= 3 +1's and no -1's, you can proceed with the release.</li><li>Create all of the distributions of the source (*.zip, *.tar.gz). Make sure that you remove the .svn directories from the directory before you create the archives. On *nix, this can be done with the command:</li></ul>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>rm -rf `find . -type d -name .svn`
-</pre>
-</div></div>
+<structured-macro ac:macro-id="6fbc2b45-33bf-4edb-9e16-e9e3d73045f7" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+rm -rf `find . -type d -name .svn`
+</plain-text-body></structured-macro>
<ul><li>Sign your distribution files, creating an asc file for both the tar and zip files, see this page <a shape="rect" class="external-link" href="http://www.apache.org/dev/release-signing.html">http://www.apache.org/dev/release-signing.html</a> for more information on release signing.</li></ul>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>gpg --armor --output foo.tar.gz.asc --detach-sig foo.tar.gz
+<structured-macro ac:macro-id="ca3a314e-73c2-4310-af92-69f282dc9041" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+gpg --armor --output foo.tar.gz.asc --detach-sig foo.tar.gz
gpg --armor --output foo.zip.asc --detach-sig foo.zip
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
<ul><li>Copy the distribution files to <strong>/www/www.apache.org/dist/activemq/activemq-cpp/source</strong> on minotaur.</li><li>Wait 24 hours for the mirrors to be updated with the distribution.</li><li>Update the links on the download page to reference your distribution through the CGI script. This simply means that you precede the file names with the path <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/">http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/</a>.</li></ul>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>i.e. http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.1-src.zip
-</pre>
-</div></div>
+<structured-macro ac:macro-id="425298a1-5ba0-4668-80c3-b6a5148fbf77" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+i.e. http://www.apache.org/dyn/closer.cgi/activemq/activemq-cpp/source/activemq-cpp-1.1-src.zip
+</plain-text-body></structured-macro>
-<ul><li>Generate the Doxygen API and place it under /www/activemq.apache.org/cms/api_docs.</li><li>Add the link to the release API to the <a shape="rect" href="api.xml">API</a> page.</li><li>Add a news item under the CMS space on the wiki about the release.</li><li>Send out an e-mail on both the dev and users list about the release.</li></ul>
+<ul><li>Generate the Doxygen API and place it under /www/activemq.apache.org/cms/api_docs.</li><li>Add the link to the release API to the <link><page ri:content-title="API"></page></link> page.</li><li>Add a news item under the CMS space on the wiki about the release.</li><li>Send out an e-mail on both the dev and users list about the release.</li></ul>
+
</div>
diff --git a/cms/developers.xml b/cms/developers.xml
index 39dc126..aa29589 100644
--- a/cms/developers.xml
+++ b/cms/developers.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="creating-distributions.xml">Creating Distributions</a></li><li><a shape="rect" href="source.xml">Source</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="ffdbf83a-e3c0-4a31-b22a-128b580da75e" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/cms/discussion-forums.xml b/cms/discussion-forums.xml
index 63253ca..d5bb77a 100644
--- a/cms/discussion-forums.xml
+++ b/cms/discussion-forums.xml
@@ -1,13 +1,13 @@
-<div class="wiki-content maincontent"><p>Before posting you might want to read the <a shape="rect" class="unresolved" href="#">Tips for getting help</a>.</p>
+<div class="wiki-content maincontent"><p>Before posting you might want to read the <link><page ri:content-title="Tips for getting help"></page></link>.</p>
-<p>Many users prefer to use online forums rather than joining a mail list which can lead to lots more email traffic so we use the online forums at <a shape="rect" class="external-link" href="http://www.nabble.com/ActiveMQ-f2354.html" rel="nofollow">Nabble forums</a> which also work with our <a shape="rect" href="mailing-lists.xml">Mailing Lists</a> so that both stay completely in sync. Use either the mailing lists or online forums, its completely up to you.</p>
+<p>Many users prefer to use online forums rather than joining a mail list which can lead to lots more email traffic so we use the online forums at <a shape="rect" href="http://www.nabble.com/ActiveMQ-f2354.html">Nabble forums</a> which also work with our <link><page ri:content-title="Mailing Lists"></page></link> so that both stay completely in sync. Use either the mailing lists or online forums, its completely up to you.</p>
-<h3 id="DiscussionForums-ActiveMQForums"><a shape="rect" class="external-link" href="http://www.nabble.com/ActiveMQ-f2354.html" rel="nofollow">ActiveMQ Forums</a></h3>
+<h3><a shape="rect" href="http://www.nabble.com/ActiveMQ-f2354.html">ActiveMQ Forums</a></h3>
-<ul><li><a shape="rect" class="external-link" href="http://www.nabble.com/ActiveMQ---User-f2356.html" rel="nofollow">ActiveMQ User Forum</a></li><li><a shape="rect" class="external-link" href="http://www.nabble.com/ActiveMQ---Dev-f2355.html" rel="nofollow">ActiveMQ Developer Forum</a></li></ul>
+<ul><li><a shape="rect" href="http://www.nabble.com/ActiveMQ---User-f2356.html">ActiveMQ User Forum</a></li><li><a shape="rect" href="http://www.nabble.com/ActiveMQ---Dev-f2355.html">ActiveMQ Developer Forum</a></li></ul>
-<h3 id="DiscussionForums-MailingLists">Mailing Lists</h3>
+<h3>Mailing Lists</h3>
-<p>If you prefer to use a mailing list instead then check out our <a shape="rect" href="mailing-lists.xml">Mailing Lists</a>. Note that the Forums and <a shape="rect" href="mailing-lists.xml">Mailing Lists</a> are kept in sync so its your choice which you use.</p></div>
+<p>If you prefer to use a mailing list instead then check out our <link><page ri:content-title="Mailing Lists"></page></link>. Note that the Forums and <link><page ri:content-title="Mailing Lists"></page></link> are kept in sync so its your choice which you use.</p></div>
diff --git a/cms/download.xml b/cms/download.xml
index 1c41b8a..083b4fa 100644
--- a/cms/download.xml
+++ b/cms/download.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Download-DownloadActiveMQ-CPP">Download ActiveMQ-CPP</h2><h3 id="Download-LatestReleases">Latest Releases</h3><p>The current stable release of the code is the <span class="confluence-link"><a shape="rect" href="activemq-cpp-394-release.xml">ActiveMQ-CPP 3.9.4</a> Release</span>.</p><h3 id="Download-AllReleases">All Releases</h3><p></p><ul class="childpages-macro"><li><a shape="rect" href="activemq-cpp-394-release.xml">ActiveMQ-CPP 3.9.4 Release</a></li><li><a shape="rect" href="activemq-cpp-393-release.xml">ActiveMQ-CPP 3.9.3 Release</a></li><li><a shape="rect" href="activemq-cpp-392-release.xml">ActiveMQ-CPP 3.9.2 Release</a></li><li><a shape="rect" href="activemq-cpp-391-release.xml">ActiveMQ-CPP 3.9.1 Release</a></li><li><a shape="rect" href="activemq-cpp-390-release.xml">ActiveMQ-CPP 3.9.0 Release</a></li><li><a shape="rect" href="activemq-cpp-384-release.xml">ActiveMQ-CPP 3.8.4 Release</a></li><li><a shape="rect" href="activemq-cpp-383-release.xml">ActiveMQ-CPP 3.8.3 Release</a></li><li><a shape="rect" href="activemq-cpp-382-release.xml">ActiveMQ-CPP 3.8.2 Release</a></li><li><a shape="rect" href="activemq-cpp-381-release.xml">ActiveMQ-CPP 3.8.1 Release</a></li><li><a shape="rect" href="activemq-cpp-380-release.xml">ActiveMQ-CPP 3.8.0 Release</a></li><li><a shape="rect" href="activemq-cpp-371-release.xml">ActiveMQ-CPP 3.7.1 Release</a></li><li><a shape="rect" href="activemq-cpp-370-release.xml">ActiveMQ-CPP 3.7.0 Release</a></li><li><a shape="rect" href="activemq-cpp-360-release.xml">ActiveMQ-CPP 3.6.0 Release</a></li><li><a shape="rect" href="activemq-cpp-350-release.xml">ActiveMQ-CPP 3.5.0 Release</a></li><li><a shape="rect" href="activemq-cpp-345-release.xml">ActiveMQ-CPP 3.4.5 Release</a></li><li><a shape="rect" href="activemq-cpp-344-release.xml">ActiveMQ-CPP 3.4.4 Release</a></li><li><a shape="rect" href="activemq-cpp-343-release.xml">ActiveMQ-CPP 3.4.3 Release</a></li><li><a shape="rect" href="activemq-cpp-342-release.xml">ActiveMQ-CPP 3.4.2 Release</a></li><li><a shape="rect" href="activemq-cpp-341-release.xml">ActiveMQ-CPP 3.4.1 Release</a></li><li><a shape="rect" href="activemq-cpp-340-release.xml">ActiveMQ-CPP 3.4.0 Release</a></li><li><a shape="rect" href="activemq-cpp-330-release.xml">ActiveMQ-CPP 3.3.0 Release</a></li><li><a shape="rect" href="activemq-cpp-325-release.xml">ActiveMQ-CPP 3.2.5 Release</a></li><li><a shape="rect" href="activemq-cpp-324-release.xml">ActiveMQ-CPP 3.2.4 Release</a></li><li><a shape="rect" href="activemq-cpp-323-release.xml">ActiveMQ-CPP 3.2.3 Release</a></li><li><a shape="rect" href="activemq-cpp-322-release.xml">ActiveMQ-CPP 3.2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-321-release.xml">ActiveMQ-CPP 3.2.1 Release</a></li><li><a shape="rect" href="activemq-cpp-320-release.xml">ActiveMQ-CPP 3.2.0 Release</a></li><li><a shape="rect" href="activemq-cpp-313-release.xml">ActiveMQ-CPP 3.1.3 Release</a></li><li><a shape="rect" href="activemq-cpp-312-release.xml">ActiveMQ-CPP 3.1.2 Release</a></li><li><a shape="rect" href="activemq-cpp-311-release.xml">ActiveMQ-CPP 3.1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-310-release.xml">ActiveMQ-CPP 3.1.0 Release</a></li><li><a shape="rect" href="activemq-cpp-301-release.xml">ActiveMQ-CPP 3.0.1 Release</a></li><li><a shape="rect" href="activemq-cpp-30-release.xml">ActiveMQ-CPP 3.0 Release</a></li><li><a shape="rect" href="activemq-cpp-226-release.xml">ActiveMQ-CPP 2.2.6 Release</a></li><li><a shape="rect" href="activemq-cpp-225-release.xml">ActiveMQ-CPP 2.2.5 Release</a></li><li><a shape="rect" href="activemq-cpp-224-release.xml">ActiveMQ-CPP 2.2.4 Release</a></li><li><a shape="rect" href="activemq-cpp-223-release.xml">ActiveMQ-CPP 2.2.3 Release</a></li><li><a shape="rect" href="activemq-cpp-222-release.xml">ActiveMQ-CPP 2.2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-221-release.xml">ActiveMQ-CPP 2.2.1 Release</a></li><li><a shape="rect" href="activemq-cpp-22-release.xml">ActiveMQ CPP 2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-213-release.xml">ActiveMQ-CPP 2.1.3 Release</a></li><li><a shape="rect" href="activemq-cpp-libtool-and-packaging-notes.xml">ActiveMQ-CPP, libtool and packaging notes</a></li><li><a shape="rect" href="activemq-cpp-212-release.xml">ActiveMQ-CPP 2.1.2 Release</a></li><li><a shape="rect" href="activemq-cpp-211-release.xml">ActiveMQ-CPP 2.1.1 Release</a></li><li><a shape="rect" href="cms-api-12-release.xml">CMS API 1.2 Release</a></li><li><a shape="rect" href="activemq-cpp-21-release.xml">ActiveMQ-CPP 2.1 Release</a></li><li><a shape="rect" href="cms-api-11-release.xml">CMS API 1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-201-release.xml">ActiveMQ-CPP 2.0.1 Release</a></li><li><a shape="rect" href="cms-api-10-release.xml">CMS API 1.0 Release</a></li><li><a shape="rect" href="activemq-cpp-20-release.xml">ActiveMQ-CPP 2.0 Release</a></li><li><a shape="rect" href="activemq-cpp-11-release.xml">ActiveMQ-CPP 1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-10-release.xml">ActiveMQ-CPP 1.0 Release</a></li></ul></div>
+<div class="wiki-content maincontent"><h2>Download ActiveMQ-CPP</h2><h3>Latest Releases</h3><p>The current stable release of the code is the <span class="confluence-link"><link><page ri:content-title="ActiveMQ-CPP 3.9.4 Release"></page><plain-text-link-body>ActiveMQ-CPP 3.9.4</plain-text-link-body></link> Release</span>.</p><h3>All Releases</h3><p><structured-macro ac:macro-id="dfb6a07d-17da-4bb0-a5a9-7c68c32bccb1" ac:name="children" ac:schema-version="1"><parameter ac:name="sort">creation</parameter><parameter ac:name="reverse">true</parameter></structured-macro></p></div>
diff --git a/cms/enable-openssl-support-with-autotools.xml b/cms/enable-openssl-support-with-autotools.xml
index dedcd25..dba82d4 100644
--- a/cms/enable-openssl-support-with-autotools.xml
+++ b/cms/enable-openssl-support-with-autotools.xml
@@ -1,7 +1,6 @@
<div class="wiki-content maincontent"><p>When you build the ActiveMQ-CPP library using the GNU AutoTools the Configure script will automatically search for OpenSSL on your system and enable support for it in the code if its found. The search might fail if you have installed OpenSSL in a non-standard location in which case you can tell the configure script where to look using the <em>with-openssl</em> option, see below for an example.</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>./configure --with-openssl=/opt/special/openssl
-</pre>
-</div></div></div>
+<structured-macro ac:macro-id="eb19df99-c256-49b9-ad5f-de3e5b67ccbf" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+./configure --with-openssl=/opt/special/openssl
+</plain-text-body></structured-macro></div>
diff --git a/cms/errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml b/cms/errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml
index 36f5ac9..46f02c3 100644
--- a/cms/errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml
+++ b/cms/errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml
@@ -1,10 +1,9 @@
<div class="wiki-content maincontent"><p>On Solaris 10 the libstdc++.la file is empty which causes the build to fail. In order to fix this you must fill in the libstdc++.la file with the correct information. There are two versions, one for 32 bit and one for 64 bit. The following listings show the correct contents of these files respectively. </p>
-<p>From <a shape="rect" class="external-link" href="http://forum.java.sun.com/thread.jspa?threadID=5073150" rel="nofollow">Sun Forums</a></p>
+<p>From <a shape="rect" href="http://forum.java.sun.com/thread.jspa?threadID=5073150">Sun Forums</a></p>
<p>/usr/sfw/lib/libstdc++.la</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>
+<structured-macro ac:macro-id="40d128d2-ef20-4e2d-9b0e-d8dd6753686c" ac:name="noformat" ac:schema-version="1"><plain-text-body>
# libstdc++.la - a libtool library file
# Generated by ltmain.sh - GNU libtool 1.4a-GCC3.0 (1.641.2.256 2001/05/28 20:09:07 with GCC-local changes)
#
@@ -37,12 +36,10 @@
# Directory that this library needs to be installed in:
libdir='/usr/sfw/lib'
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
<p>/usr/sfw/lib/64/libstdc++.la</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>
+<structured-macro ac:macro-id="1ba95c70-1934-4802-ade9-885ed7966585" ac:name="noformat" ac:schema-version="1"><plain-text-body>
# libstdc++.la - a libtool library file
# Generated by ltmain.sh - GNU libtool 1.4a-GCC3.0 (1.641.2.256 2001/05/28 20:09:07 with GCC-local changes)
#
@@ -75,14 +72,11 @@
# Directory that this library needs to be installed in:
libdir='/usr/sfw/lib/64'
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
<p>Note that this doesn't seem to get us all the way. For some reason the shared library dependencies can't seem to all be resolved so you must build only static libraries. This can be accomplished by passing the following to the configure script.</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>
+<structured-macro ac:macro-id="fc32c26c-e2fe-4eaa-8bf5-365e451ec2dd" ac:name="noformat" ac:schema-version="1"><plain-text-body>
./configure --enable-shared=no
-</pre>
-</div></div> </div>
+</plain-text-body></structured-macro> </div>
diff --git a/cms/example.xml b/cms/example.xml
index 76bdaa8..e15fc3e 100644
--- a/cms/example.xml
+++ b/cms/example.xml
@@ -1,23 +1,22 @@
-<div class="wiki-content maincontent"><h2 id="Example-ActiveMQ-CPPinAction">ActiveMQ-CPP in Action</h2>
+<div class="wiki-content maincontent"><h2>ActiveMQ-CPP in Action</h2>
<p>In the example below we create two classes <strong>HolloWorldConsumer</strong> and <strong>HelloWorldProducer</strong> each of which runs in its own thread. The Producer sends TextMessage objects via a <strong>MessageProducer</strong> instance to the ActiveMQ broker. The Consumer receives messages asynchronously from the broker on the same Topic or Queue as the Producer looking for a set number of TextMessages to arrive. </p>
<p>The following example is taken from the source code and shows a basic usage scenario of ActiveMQ-CPP, you can find other examples in the examples folder that ships with the source distribution of ActiveMQ-CPP:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>main.cpp</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6137a35b-c89a-4c44-89d0-d0ac7ebd9d8c" ac:name="code" ac:schema-version="1"><parameter ac:name="title">main.cpp</parameter><plain-text-body>
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
+ * (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
+ * distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
@@ -112,9 +111,9 @@
// Create the destination (Topic or Queue)
if (useTopic) {
- destination = session->createTopic("TEST.FOO");
+ destination = session->createTopic("TEST.FOO");
} else {
- destination = session->createQueue("TEST.FOO");
+ destination = session->createQueue("TEST.FOO");
}
// Create a MessageProducer from the Session to the Topic or Queue
@@ -125,12 +124,12 @@
string threadIdStr = Long::toString(Thread::currentThread()->getId());
// Create a messages
- string text = (string) "Hello world! from thread " + threadIdStr;
+ string text = (string) "Hello world! from thread " + threadIdStr;
for (int ix = 0; ix < numMessages; ++ix) {
std::auto_ptr<TextMessage> message(session->createTextMessage(text));
- message->setIntProperty("Integer", ix);
- printf("Sent message #%d from thread %s\n", ix + 1, threadIdStr.c_str());
+ message->setIntProperty("Integer", ix);
+ printf("Sent message #%d from thread %s\n", ix + 1, threadIdStr.c_str());
producer->send(message.get());
}
@@ -238,9 +237,9 @@
// Create the destination (Topic or Queue)
if (useTopic) {
- destination = session->createTopic("TEST.FOO");
+ destination = session->createTopic("TEST.FOO");
} else {
- destination = session->createQueue("TEST.FOO");
+ destination = session->createQueue("TEST.FOO");
}
// Create a MessageConsumer from the Session to the Topic or Queue
@@ -272,15 +271,15 @@
try {
count++;
const TextMessage* textMessage = dynamic_cast<const TextMessage*> (message);
- string text = "";
+ string text = "";
if (textMessage != NULL) {
text = textMessage->getText();
} else {
- text = "NOT A TEXTMESSAGE!";
+ text = "NOT A TEXTMESSAGE!";
}
- printf("Message #%d Received: %s\n", count, text.c_str());
+ printf("Message #%d Received: %s\n", count, text.c_str());
} catch (CMSException& e) {
e.printStackTrace();
@@ -298,7 +297,7 @@
// If something bad happens you see it here as this class is also been
// registered as an ExceptionListener with the connection.
virtual void onException(const CMSException& ex AMQCPP_UNUSED) {
- printf("CMS Exception occurred. Shutting down client.\n");
+ printf("CMS Exception occurred. Shutting down client.\n");
ex.printStackTrace();
exit(1);
}
@@ -334,9 +333,9 @@
activemq::library::ActiveMQCPP::initializeLibrary();
{
- std::cout << "=====================================================\n";
- std::cout << "Starting the example:" << std::endl;
- std::cout << "-----------------------------------------------------\n";
+ std::cout << "=====================================================\n";
+ std::cout << "Starting the example:" << std::endl;
+ std::cout << "-----------------------------------------------------\n";
// Set the URI to point to the IP Address of your broker.
@@ -362,16 +361,16 @@
// the trusted root. If using client authentication you also need to specify
// the location of the client Certificate.
//
- // System::setProperty( "decaf.net.ssl.keyStore", "<path>/client.pem" );
- // System::setProperty( "decaf.net.ssl.keyStorePassword", "password" );
- // System::setProperty( "decaf.net.ssl.trustStore", "<path>/rootCA.pem" );
+ // System::setProperty( "decaf.net.ssl.keyStore", "<path>/client.pem" );
+ // System::setProperty( "decaf.net.ssl.keyStorePassword", "password" );
+ // System::setProperty( "decaf.net.ssl.trustStore", "<path>/rootCA.pem" );
//
// The you just specify the ssl transport in the URI, for example:
//
// ssl://localhost:61617
//
std::string brokerURI =
- "failover:(tcp://localhost:61616)";
+ "failover:(tcp://localhost:61616)";
//============================================================
// set to true to use topics instead of queues
@@ -408,10 +407,10 @@
consumer.close();
producer.close();
- std::cout << "Time to completion = " << totalTime << " seconds." << std::endl;
- std::cout << "-----------------------------------------------------\n";
- std::cout << "Finished with the example." << std::endl;
- std::cout << "=====================================================\n";
+ std::cout << "Time to completion = " << totalTime << " seconds." << std::endl;
+ std::cout << "-----------------------------------------------------\n";
+ std::cout << "Finished with the example." << std::endl;
+ std::cout << "=====================================================\n";
}
activemq::library::ActiveMQCPP::shutdownLibrary();
@@ -419,6 +418,5 @@
// END SNIPPET: demo
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/cms/faq.xml b/cms/faq.xml
index 380a4a2..e09f76d 100644
--- a/cms/faq.xml
+++ b/cms/faq.xml
@@ -1,23 +1,18 @@
-<div class="wiki-content maincontent"><h2 id="FAQ-FAQ">FAQ</h2>
+<div class="wiki-content maincontent"><h2>FAQ</h2>
-<p>Here are a list of commonly asked questions and answers. If you have any questions which are not on this list, please talk to us on the <a shape="rect" href="discussion-forums.xml">forums</a>.</p>
+<p>Here are a list of commonly asked questions and answers. If you have any questions which are not on this list, please talk to us on the <link><page ri:content-title="Discussion Forums"></page><link-body>forums</link-body></link>.</p>
-<p>We <a shape="rect" href="../contributing.xml">welcome contributions</a> and this entire website is a <a shape="rect" href="../how-does-the-website-work.xml">wiki that you can edit</a> so please join in and help us make the documentation better! If you have a suggestion for more topics you can open a new Jira Issue or post on the forums, and if you provide a complete FAQ entry we'll put it up right away.</p>
+<p>We <link><page ri:content-title="Contributing" ri:space-key="ACTIVEMQ"></page><link-body>welcome contributions</link-body></link> and this entire website is a <link><page ri:content-title="How does the website work" ri:space-key="ACTIVEMQ"></page><link-body>wiki that you can edit</link-body></link> so please join in and help us make the documentation better! If you have a suggestion for more topics you can open a new Jira Issue or post on the forums, and if you provide a complete FAQ entry we'll put it up right away.</p>
-<h3 id="FAQ-General"><a shape="rect" href="general.xml">General</a></h3>
+<h3><link><page ri:content-title="General"></page></link></h3>
-General Questions about ActiveMQ's CMS client.
+<structured-macro ac:macro-id="b3c8a23b-ed63-4ca6-b3fe-de78b0f5a7b1" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="General"></page></link></parameter></structured-macro>
-<ul class="childpages-macro"><li><a shape="rect" href="are-there-more-faq-entries.xml">Are there more FAQ Entries</a></li><li><a shape="rect" href="what-is-activemq-cpp.xml">What is ActiveMQ CPP</a></li></ul>
+<h3><link><page ri:content-title="ActiveMQ-CPP Usage FAQs"></page></link></h3>
-<h3 id="FAQ-ActiveMQ-CPPUsageFAQs"><a shape="rect" href="activemq-cpp-usage-faqs.xml">ActiveMQ-CPP Usage FAQs</a></h3>
+<structured-macro ac:macro-id="d38d330a-55b2-4532-908c-c0b8a64112b1" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="ActiveMQ-CPP Usage FAQs"></page></link></parameter></structured-macro>
-This section covers general questions on how to use various feature of the ActiveMQ-CPP Library
-<ul class="childpages-macro"><li><a shape="rect" href="how-do-i-use-the-ssl-transport.xml">How do I use the SSL Transport</a></li></ul>
+<h3><link><page ri:content-title="Building FAQs"></page></link></h3>
-<h3 id="FAQ-BuildingFAQs"><a shape="rect" href="building-faqs.xml">Building FAQs</a></h3>
-
-These are general hints and tips on Building the Library on various platforms etc.
-
-<ul class="childpages-macro"><li><a shape="rect" href="general-build-issues.xml">General Build Issues</a></li><li><a shape="rect" href="openssl-support.xml">OpenSSL Support</a><ul class="childpages-macro"><li><a shape="rect" href="enable-openssl-support-with-autotools.xml">Enable OpenSSL support with autotools</a></li><li><a shape="rect" href="how-do-i-prevent-autoconf-from-enabling-openssl-support.xml">How do I prevent autoconf from enabling OpenSSL support</a></li><li><a shape="rect" href="how-to-enable-ssl-support-on-windows.xml">How to enable SSL support on Windows</a></li></ul></li><li><a shape="rect" href="solaris-platform.xml">Solaris Platform</a><ul class="childpages-macro"><li><a shape="rect" href="errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml">Errors from libstd++.la on Solaris 10 using the GNU Compiler</a></li><li><a shape="rect" href="errors-saying-no-rule-to-make-target.xml">Errors saying "no rule to make target"</a></li><li><a shape="rect" href="using-the-solaris-cc-compiler.xml">Using the Solaris CC compiler</a></li></ul></li></ul> </div>
+<structured-macro ac:macro-id="398000a2-61a1-4d8a-a932-ca44d2228dbc" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Building FAQs"></page></link></parameter></structured-macro></div>
diff --git a/cms/general-build-issues.xml b/cms/general-build-issues.xml
index f6427fe..6d6367c 100644
--- a/cms/general-build-issues.xml
+++ b/cms/general-build-issues.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h6 id="GeneralBuildIssues-Errorduringconfigure:"error:libpthreadnotfound!"">Error during configure: "error: libpthread not found!"</h6>
+<div class="wiki-content maincontent"><h6>Error during configure: "error: libpthread not found!"</h6>
<p>Getting an error about libpthread not found even though its installed, in many cases indicates that the tool chain required to build the library isn't fully installed.  One good place to start checking is to ensure that both 'gcc' and 'g+<span style="text-decoration: underline;">' are installed as the M4 configure macros that check for pthread related features uses 'g</span>+'.   </p></div>
diff --git a/cms/general.xml b/cms/general.xml
index 7892dfa..3e017ad 100644
--- a/cms/general.xml
+++ b/cms/general.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>General Questions about ActiveMQ's CMS client.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="are-there-more-faq-entries.xml">Are there more FAQ Entries</a></li><li><a shape="rect" href="what-is-activemq-cpp.xml">What is ActiveMQ CPP</a></li></ul></div>
+<structured-macro ac:macro-id="35a0132d-8bbc-4b99-9ccd-bbcf5bdf58e0" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/cms/getting-started.xml b/cms/getting-started.xml
index 7ab5040..15f8f9a 100644
--- a/cms/getting-started.xml
+++ b/cms/getting-started.xml
@@ -1,4 +1,5 @@
-<div class="wiki-content maincontent"><h2 id="GettingStarted-GettingStartedGuide">Getting Started Guide</h2>
+<div class="wiki-content maincontent"><h2>Getting Started Guide</h2>
-<p>Start off by getting a <a shape="rect" href="download.xml">Download</a> or by grabbing the <a shape="rect" href="source.xml">Source</a> and <a shape="rect" href="building.xml">Building</a> it.</p></div>
+<p>Start off by getting a <link><page ri:content-title="Download"></page></link> or by grabbing the <link><page ri:content-title="Source"></page></link> and <link><page ri:content-title="Building"></page></link> it.</p>
+</div>
diff --git a/cms/handling-advisory-messages.xml b/cms/handling-advisory-messages.xml
index 1af52cf..a54b259 100644
--- a/cms/handling-advisory-messages.xml
+++ b/cms/handling-advisory-messages.xml
@@ -3,83 +3,76 @@
<ul><li>See consumers, producers and connections starting and stopping</li><li>See temporary destinations being created and destroyed</li><li>Get notified messages expiring on topics and queues</li><li>Observe brokers sending messages to destinations with no consumers.</li><li>See connections starting and stopping</li></ul>
-<p>Advisory messages can be thought as some kind of administrative channel where you receive information regarding what is happening on your JMS provider along with what's happening with producers, consumers and destinations. To learn more about the broker's advisory message support see this <a shape="rect" href="../advisory-message.xml">article</a>.</p>
+<p>Advisory messages can be thought as some kind of administrative channel where you receive information regarding what is happening on your JMS provider along with what's happening with producers, consumers and destinations. To learn more about the broker's advisory message support see this <link><page ri:content-title="Advisory Message" ri:space-key="ActiveMQ"></page><link-body>article</link-body></link>.</p>
-<h3 id="HandlingAdvisoryMessages-BeforeYouBegin"><strong>Before You Begin</strong></h3>
+<h3><strong>Before You Begin</strong></h3>
-<p>This tutorial assumes that the reader has a working knowledge of the CMS API and knows how to build basic applications using the ActiveMQ-CPP Library. If you aren't sure how to use the CMS API then you should first read the <a shape="rect" href="cms-api-overview.xml">CMS API Overview</a>. The tutorial is written against the ActiveMQ-CPP 3.0 release API and while it is possible to handle advisory messages using the older ActiveMQ-CPP 2.x clients there may be some code differences which are not shown in this article. </p>
+<p>This tutorial assumes that the reader has a working knowledge of the CMS API and knows how to build basic applications using the ActiveMQ-CPP Library. If you aren't sure how to use the CMS API then you should first read the <link><page ri:content-title="CMS API Overview"></page><link-body>CMS API Overview</link-body></link>. The tutorial is written against the ActiveMQ-CPP 3.0 release API and while it is possible to handle advisory messages using the older ActiveMQ-CPP 2.x clients there may be some code differences which are not shown in this article. </p>
-<h3 id="HandlingAdvisoryMessages-SubscribingtoAdvisoryTopics"><strong>Subscribing to Advisory Topics</strong></h3>
+<h3><strong>Subscribing to Advisory Topics</strong></h3>
<p>To receive advisory message's you first need to subscribe to the Topic that supplies the advisory message you want. You subscribe to these Topics like you would any other destination, the trick is to use the correct name for the Topic that you want to use. Lets first take a look at a couple of the types available for use (this is not a complete set).</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Advisory Topics</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>properties</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Data Structure</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ActiveMQ.Advisory.Connection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Connection start & stop messages </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ActiveMQ.Advisory.Producer.Queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Producer start & stop messages on a Queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String='producerCount' - the number of producers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> ProducerInfo</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ActiveMQ.Advisory.Producer.Topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Producer start & stop messages on a Topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String='producerCount' - the number of producers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ProducerInfo</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ActiveMQ.Advisory.Consumer.Queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Consumer start & stop messages on a Queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String='consumerCount' - the number of Consumers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ConsumerInfo</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ActiveMQ.Advisory.Consumer.Topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Consumer start & stop messages on a Topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String='consumerCount' - the number of Consumers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ConsumerInfo</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Advisory Topics</p></th><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>properties</p></th><th colspan="1" rowspan="1"><p>Data Structure</p></th></tr><tr><td colspan="1" rowspan="1"><p> ActiveMQ.Advisory.Connection </p></td><td colspan="1" rowspan="1"><p> Connection start & stop messages </p></td></tr><tr><td colspan="1" rowspan="1"><p> ActiveMQ.Advisory.Producer.Queue </p></td><td colspan="1" rowspan="1"><p> Producer start & stop messages on a Queue </p></td><td colspan="1" rowspan="1"><p>String='producerCount' - the number of producers</p></td><td colspan="1" rowspan="1"><p> ProducerInfo</p></td></tr><tr><td colspan="1" rowspan="1"><p> ActiveMQ.Advisory.Producer.Topic </p></td><td colspan="1" rowspan="1"><p> Producer start & stop messages on a Topic </p></td><td colspan="1" rowspan="1"><p>String='producerCount' - the number of producers</p></td><td colspan="1" rowspan="1"><p>ProducerInfo</p></td></tr><tr><td colspan="1" rowspan="1"><p> ActiveMQ.Advisory.Consumer.Queue </p></td><td colspan="1" rowspan="1"><p> Consumer start & stop messages on a Queue </p></td><td colspan="1" rowspan="1"><p>String='consumerCount' - the number of Consumers</p></td><td colspan="1" rowspan="1"><p>ConsumerInfo</p></td></tr><tr><td colspan="1" rowspan="1"><p> ActiveMQ.Advisory.Consumer.Topic </p></td><td colspan="1" rowspan="1"><p> Consumer start & stop messages on a Topic </p></td><td colspan="1" rowspan="1"><p>String='consumerCount' - the number of Consumers</p></td><td colspan="1" rowspan="1"><p>ConsumerInfo</p></td></tr></tbody></table>
<p>Now, looking at the above list lets pick one of the Topics and figure out how we would create the CMS Topic to subscribe to in order to receive the advisory messages. Using the Java client we could create the Destination using the utility class <strong>AdvisorySupport</strong> but for now ActiveMQ-CPP doesn't provide such a utility class, hopefully we will see this added in a future release (Contributions are of course always welcomed!).</p>
<p>If we had a Topic named TOPIC.FOO and we wanted to know when a producer subscribed to that Topic we would need to create a Topic object whose name is <strong>ActiveMQ.Advisory.Producer.Topic.TOPIC.FOO</strong> in order to receive the advisory message we are interested in. We know this because we can look at the above table and see that the <strong>ActiveMQ.Advisory.Producer.Topic</strong> is informed whenever a Producer starts or stops publishing messages on a Topic and we also know that our Topic is named TOPIC.FOO, so adding them together gets us the name of our Advisory Topic, we also know this because we peaked at the AdvisorySupport.java class, and no, that's not cheating. Below is a code snippet showing the creation of the Topic using a CMS Session:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating an Advisory Topic for Producers on TOPIC.FOO</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ac0429a2-01b4-421a-8e3a-5abbe4840c4f" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating an Advisory Topic for Producers on TOPIC.FOO</parameter><plain-text-body>
std::auto_ptr<cms::Topic> advisories( session->createTopic(
- "ActiveMQ.Advisory.Producer.Topic.TOPIC.FOO" ) );
+ "ActiveMQ.Advisory.Producer.Topic.TOPIC.FOO" ) );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Once we create the Topic for the advisory messages we want to listen for we just need to create a consumer to listen for them, the code snippet below demonstrates this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Creating an Consumer for an Advisory Topic.</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="59084ef4-8042-4829-8a92-5ee78351e123" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Creating an Consumer for an Advisory Topic.</parameter><plain-text-body>
std::auto_ptr<cms::MessageConsumer> consumer;
consumer.reset( session->createConsumer( advisories.get() ) );
consumer->setMessageListener( this );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>As you can see there is no difference between subscriptions to advisory topics that subscriptions to any other Destination in CMS. In the above example we registered as an asynchronous listener, you can also use the normal blocking <strong>receive</strong> method but we prefer this method.</p>
-<h3 id="HandlingAdvisoryMessages-DealingwithincomingAdvisoryMessages"><strong>Dealing with incoming Advisory Messages</strong></h3>
+<h3><strong>Dealing with incoming Advisory Messages</strong></h3>
<p>Every Advisory has the message type 'Advisory' and some predefined message properties, to check a CMS Message for this type you would call the <strong>getCMSType</strong> method on a Message object. In some cases you will know that the only message you are going to receive are advisory messages because your client only subscribes to advisory topics, other times you might have wired multiple MessageConsumers to the same MessageListener in which case you will have to check the message tppe. Once you know you are dealing with an advisory message then you can start to inspect it to determine what sort of message it is and extract the data that is meaningful to your application.</p>
<p>Many of the advisory messages store meaningful data in the Message properties, for instance the Consumer Start / Stop advisory message contains an element with the key <strong>consumerCount</strong> which is populated with the current number of active consumers on the Topic or Queue in question. Lets take a look at a code snippet now that checks the messages received in an onMessage callback to see if its an advisory message and acts on it if it is:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Using the CMS Type to determine if a Message is an Advisory</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c025c6dd-e89f-4115-a690-58e22829e2f8" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Using the CMS Type to determine if a Message is an Advisory</parameter><plain-text-body>
void AdvisoryProducer::onMessage( const cms::Message* message ) {
- if( message->getCMSType() == "Advisory" ) {
+ if( message->getCMSType() == "Advisory" ) {
- std::cout << "Received an Advisory Message!" << std::endl;
+ std::cout << "Received an Advisory Message!" << std::endl;
- if( message->propertyExists( "consumerCount" ) ) {
+ if( message->propertyExists( "consumerCount" ) ) {
- std::string consumerCount = message->getStringProperty( "consumerCount" );
- std::cout << "Number of Consumers = " << consumerCount << std::endl;
+ std::string consumerCount = message->getStringProperty( "consumerCount" );
+ std::cout << "Number of Consumers = " << consumerCount << std::endl;
// Do Something Meaningful here....
}
} else {
- std::cout << "Received a Non-Advisory Message!" << std::endl;
+ std::cout << "Received a Non-Advisory Message!" << std::endl;
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="HandlingAdvisoryMessages-CompleteExample:ProducerthatonlyProduceswhenthereisaConsumer"><strong>Complete Example: Producer that only Produces when there is a Consumer</strong></h3>
+<h3><strong>Complete Example: Producer that only Produces when there is a Consumer</strong></h3>
<p>Now that you've seen the basics of advisory message processing its time to show you a complete example that demonstrates what you can do with advisory messages. The following code shows a class header and source file that implements a basic CMS Producer that will send heart beat message to a Topic called <strong>HEART-BEAT-CHANNEL</strong> only when there are active consumers, otherwise it sits idle.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>AdvisoryProducer Header file</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d44fac8d-a18d-433f-99fb-bb8af9d942f8" ac:name="code" ac:schema-version="1"><parameter ac:name="title">AdvisoryProducer Header file</parameter><plain-text-body>
#ifndef _ACTIVEMQCPP_EXAMPLES_ADVISORIES_ADVISORYPRODUCER_H_
#define _ACTIVEMQCPP_EXAMPLES_ADVISORIES_ADVISORYPRODUCER_H_
@@ -145,13 +138,11 @@
#endif /* _ACTIVEMQCPP_EXAMPLES_ADVISORIES_ADVISORYPRODUCER_H_ */
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>AdvisoryProducer Source file</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f39527c7-13c5-47cc-b854-cd091268e6b0" ac:name="code" ac:schema-version="1"><parameter ac:name="title">AdvisoryProducer Source file</parameter><plain-text-body>
-#include "AdvisoryProducer.h"
+#include "AdvisoryProducer.h"
#include <cms/Topic.h>
#include <cms/Message.h>
@@ -172,13 +163,13 @@
if( session == NULL ) {
throw NullPointerException(
- __FILE__, __LINE__, "Session Object passed was Null." );
+ __FILE__, __LINE__, "Session Object passed was Null." );
}
std::auto_ptr<cms::Topic> destination( session->createTopic(
- "HEART-BEAT-CHANNEL" ) );
+ "HEART-BEAT-CHANNEL" ) );
std::auto_ptr<cms::Topic> advisories( session->createTopic(
- "ActiveMQ.Advisory.Consumer.Topic.HEART-BEAT-CHANNEL" ) );
+ "ActiveMQ.Advisory.Consumer.Topic.HEART-BEAT-CHANNEL" ) );
this->shutdown = false;
this->consumerOnline = false;
@@ -207,7 +198,7 @@
if( this->consumerOnline ) {
std::auto_ptr<cms::TextMessage> message(
- this->session->createTextMessage( "Alive" ) );
+ this->session->createTextMessage( "Alive" ) );
this->producer->send( message.get() );
@@ -221,63 +212,59 @@
////////////////////////////////////////////////////////////////////////////////
void AdvisoryProducer::onMessage( const cms::Message* message ) {
- if( message->getCMSType() == "Advisory" ) {
+ if( message->getCMSType() == "Advisory" ) {
- std::cout << "Received an Advisory Message!" << std::endl;
+ std::cout << "Received an Advisory Message!" << std::endl;
- if( message->propertyExists( "consumerCount" ) ) {
+ if( message->propertyExists( "consumerCount" ) ) {
- std::string consumerCount = message->getStringProperty( "consumerCount" );
- std::cout << "Number of Consumers = " << consumerCount << std::endl;
+ std::string consumerCount = message->getStringProperty( "consumerCount" );
+ std::cout << "Number of Consumers = " << consumerCount << std::endl;
this->consumerOnline = Integer::parseInt( consumerCount ) > 0 ? true : false;
}
} else {
- std::cout << "Received a Non-Advisory Message!" << std::endl;
+ std::cout << "Received a Non-Advisory Message!" << std::endl;
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="HandlingAdvisoryMessages-*AdvancedTopic*DealingwithCommandObjectsinAdvisories">*<strong>Advanced Topic</strong>* Dealing with Command Objects in Advisories </h3>
+<h3>*<strong>Advanced Topic</strong>* Dealing with Command Objects in Advisories </h3>
-<p>If you read the ActiveMQ Advisory Message <a shape="rect" href="../advisory-message.xml">article</a> mentioned at the start of this tutorial then you know that certain advisory messages can contain an embedded command object. If you didn't read that <a shape="rect" href="../advisory-message.xml">article</a> then this section is going to be very confusing, so go read it. We can access those command object in CMS with a little work which means we can take full advantage of the Advisory Message feature.</p>
+<p>If you read the ActiveMQ Advisory Message <link><page ri:content-title="Advisory Message" ri:space-key="ActiveMQ"></page><link-body>article</link-body></link> mentioned at the start of this tutorial then you know that certain advisory messages can contain an embedded command object. If you didn't read that <link><page ri:content-title="Advisory Message" ri:space-key="ActiveMQ"></page><link-body>article</link-body></link> then this section is going to be very confusing, so go read it. We can access those command object in CMS with a little work which means we can take full advantage of the Advisory Message feature.</p>
-<p>All Advisory Messages are sent as a basic ActiveMQMessage to your client. The underlying type hierarchy in ActiveMQ-CPP is the same as that of ActiveMQ so the names of the embedded command objects you saw in the Advisory <a shape="rect" href="../advisory-message.xml">article</a> are the same and they contain mostly the same information, although sometimes the information is encoded in a more C++ friendly or unfriendly way depending on your point of view. </p>
+<p>All Advisory Messages are sent as a basic ActiveMQMessage to your client. The underlying type hierarchy in ActiveMQ-CPP is the same as that of ActiveMQ so the names of the embedded command objects you saw in the Advisory <link><page ri:content-title="Advisory Message" ri:space-key="ActiveMQ"></page><link-body>article</link-body></link> are the same and they contain mostly the same information, although sometimes the information is encoded in a more C++ friendly or unfriendly way depending on your point of view. </p>
<p>To demonstrate how we can access the command objects lets try and create a client application that listens to the Broker for advisories that indicate that Temporary Destinations have either been created or destroyed. The Broker will publish advisory messages to the "ActiveMQ.Advisory.TempTopic" and "ActiveMQ.Advisory.TempQueue" Topics whenever the corresponding Temporary Destination is created or destroyed and the command object will be of type DestinationInfo. The DestinationInfo object contains a Destination object describing the Destination in question and an Operation Type value telling whether the command is a create or destroy command. First lets look at how we subscribe to this Advisory Topic:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Subscribing to a Composite Advisory Topic</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f9da7b3c-4eca-4a1b-809e-4775cc6a1abb" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Subscribing to a Composite Advisory Topic</parameter><plain-text-body>
std::auto_ptr<cms::Topic> advisories( session->createTopic(
- "ActiveMQ.Advisory.TempTopic,ActiveMQ.Advisory.TempQueue" ) );
+ "ActiveMQ.Advisory.TempTopic,ActiveMQ.Advisory.TempQueue" ) );
std::auto_ptr<cms::MessageConsumer> consumer;
consumer.reset( session->createConsumer( advisories.get() ) );
consumer->setMessageListener( this );
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>As you can see in the above code snippet we just create a new Topic object whose name is a composite of the two Topics we want to subscribe on, this will allow our single <strong>MessageConsumer</strong> instance to receive both Temporary Topic and Temporary Queue advisories. As before we also create a <strong>MessageConsumer</strong> and register our class' instance as the asynchronous listener. Now all that's left is to implement the <strong>onMessage</strong> method of the <strong>MessageListener</strong> interface, lets take a look at that code now:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Processing an Advisory message with an embedded command object</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="dd78c039-6792-46b6-abf3-1a4163c4b4da" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Processing an Advisory message with an embedded command object</parameter><plain-text-body>
////////////////////////////////////////////////////////////////////////////////
void TempDestinationAdvisoryConsumer::onMessage( const cms::Message* message ) {
- if( message->getCMSType() == "Advisory" ) {
+ if( message->getCMSType() == "Advisory" ) {
- std::cout << "Received an Advisory Message!" << std::endl;
+ std::cout << "Received an Advisory Message!" << std::endl;
const ActiveMQMessage* amqMessage =
dynamic_cast<const ActiveMQMessage*>( message );
if( amqMessage != NULL && amqMessage->getDataStructure() != NULL ) {
- std::cout << "Advisory Message contains a Command Object!" << std::endl;
+ std::cout << "Advisory Message contains a Command Object!" << std::endl;
try {
@@ -287,43 +274,41 @@
unsigned char operationType = info->getOperationType();
if( operationType == ActiveMQConstants::DESTINATION_REMOVE_OPERATION ) {
- std::cout << "Temporary Destination {"
+ std::cout << "Temporary Destination {"
<< info->getDestination()->getPhysicalName()
- << "} Removed."
+ << "} Removed."
<< std::endl;
} else if( operationType == ActiveMQConstants::DESTINATION_ADD_OPERATION ) {
- std::cout << "Temporary Destination {"
+ std::cout << "Temporary Destination {"
<< info->getDestination()->getPhysicalName()
- << "} Added."
+ << "} Added."
<< std::endl;
} else {
- std::cout << "ERROR: I have no Idea what just happened!"
+ std::cout << "ERROR: I have no Idea what just happened!"
<< std::endl;
}
} catch( ClassCastException& ex ) {
- std::cout << "ERROR: Expected the Command to be a DestinationInfo, "
- << "it wasn't so PANIC!!"
+ std::cout << "ERROR: Expected the Command to be a DestinationInfo, "
+ << "it wasn't so PANIC!!"
<< std::endl;
}
}
} else {
- std::cout << "Received a Non-Advisory Message!" << std::endl;
+ std::cout << "Received a Non-Advisory Message!" << std::endl;
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Fortunately for use the code above looks more complicated than it really is, lets walk through it a bit more slowly now to understand what is going on:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Getting to the ActiveMQMessage object</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="acb1797e-d657-4a65-8b8a-54144ec26fa3" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Getting to the ActiveMQMessage object</parameter><plain-text-body>
-if( message->getCMSType() == "Advisory" ) {
+if( message->getCMSType() == "Advisory" ) {
- std::cout << "Received an Advisory Message!" << std::endl;
+ std::cout << "Received an Advisory Message!" << std::endl;
const ActiveMQMessage* amqMessage =
dynamic_cast<const ActiveMQMessage*>( message );
@@ -331,26 +316,22 @@
... Other scary code comes next...
else {
- std::cout << "Received a Non-Advisory Message!" << std::endl;
+ std::cout << "Received a Non-Advisory Message!" << std::endl;
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The first thing we need to do is check that we received an advisory message, ActiveMQ encodes the Message Type as "Advisory" so that's easy enough. We don't technically need to do this here since our consumer only listens on an advisory Topic but its not a bad idea to check. Once we know its an advisory message we know that the message pointer should be of type ActiveMQMessage under that generic cms::Message disguise its wearing so we use a <strong>dynamic_cast</strong> to convert it. Now that we've converted to an ActiveMQMessage what's next, well lets take a look:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Checking for an embedded command object</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e2c6ec28-d857-4f19-bdfa-58b3b4d1ec3d" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Checking for an embedded command object</parameter><plain-text-body>
if( amqMessage != NULL && amqMessage->getDataStructure() != NULL ) {
- std::cout << "Advisory Message contains a Command Object!" << std::endl;
+ std::cout << "Advisory Message contains a Command Object!" << std::endl;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Every ActiveMQMessage derived object has a method called <strong>getDataStructure</strong> which can be used for all sorts of useful things, here we are trying to see if there is a command object contained in this message, and you guessed it, the getDataStructure method will tell us if there is one. If there is then we can move onto checking for a DestinationInfo object:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Getting to the DestinationInfo object</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="63c3b5de-08b6-4727-a368-2e9ae4602a8a" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Getting to the DestinationInfo object</parameter><plain-text-body>
try{
@@ -360,37 +341,35 @@
unsigned char operationType = info->getOperationType();
if( operationType == ActiveMQConstants::DESTINATION_REMOVE_OPERATION ) {
- std::cout << "Temporary Destination {"
+ std::cout << "Temporary Destination {"
<< info->getDestination()->getPhysicalName()
- << "} Removed."
+ << "} Removed."
<< std::endl;
} else if( operationType == ActiveMQConstants::DESTINATION_ADD_OPERATION ) {
- std::cout << "Temporary Destination {"
+ std::cout << "Temporary Destination {"
<< info->getDestination()->getPhysicalName()
- << "} Added."
+ << "} Added."
<< std::endl;
} else {
- std::cout << "ERROR: I have no Idea what just happened!"
+ std::cout << "ERROR: I have no Idea what just happened!"
<< std::endl;
}
} catch( ClassCastException& ex ) {
- std::cout << "ERROR: Expected the Command to be a DestinationInfo, "
- << "it wasn't so PANIC!!"
+ std::cout << "ERROR: Expected the Command to be a DestinationInfo, "
+ << "it wasn't so PANIC!!"
<< std::endl;
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>First thing you are probably asking about this code snippet is "what is that Pointer thing?", that is a thread safe smart pointer that is used internally by ActiveMQ-CPP to manage all the pointers that make up the cms::Message objects among other things. We create an instance of a Pointer<DestinationInfo> type which will pointer to our DestinationInfo command if the dynamicCast method is able to make that conversion, if not a ClassCastException is thrown. Once we have the DestinationInfo pointer we can retrieve the Operation Type of the command and then compare it to the constants in ActiveMQConstants to see what is being done to the Destination. There are only two operation types, add and remove, but since the DestinationInfo object encodes the operation type value as an unsigned char we provide a fall-back case to alert us to that error. We are almost done now, all that remains is to output what happened, and also let the user know what the name of the Destination is, the <strong>getPhysicalName</strong> method in the Destination class tells us that. You could also find out whether the Destination is a Topic or a Queue using the Destination object, we leave that as an exercise to the reader.</p>
-<h3 id="HandlingAdvisoryMessages-CompleteExample:ConsumerthatlistensforCreationandDestructionofTemporaryDestinations"><strong>Complete Example: Consumer that listens for Creation and Destruction of Temporary Destinations</strong></h3>
+<h3><strong>Complete Example: Consumer that listens for Creation and Destruction of Temporary Destinations</strong></h3>
<p>The complete code of our client application is shown below, you can also find this code as well as a simple client that creates both a Temporary Topic and a Temporary Queue in the examples folder in the source distribution.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>TempDestinationAdvisoryConsumer Header File</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2068fff3-c58c-4fa8-86b4-98f4a0c68521" ac:name="code" ac:schema-version="1"><parameter ac:name="title">TempDestinationAdvisoryConsumer Header File</parameter><plain-text-body>
#ifndef _ACTIVEMQCPP_EXAMPLES_ADVISORIES_TEMPDESTINATIONADVISORYCONSUMER_H_
#define _ACTIVEMQCPP_EXAMPLES_ADVISORIES_TEMPDESTINATIONADVISORYCONSUMER_H_
@@ -436,13 +415,11 @@
#endif /* _ACTIVEMQCPP_EXAMPLES_ADVISORIES_TEMPDESTINATIONADVISORYCONSUMER_H_ */
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>TempDestinationAdvisoryConsumer Source File</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0270a8c8-0536-45aa-af59-f5e69fbdcd5b" ac:name="code" ac:schema-version="1"><parameter ac:name="title">TempDestinationAdvisoryConsumer Source File</parameter><plain-text-body>
-#include "TempDestinationAdvisoryConsumer.h"
+#include "TempDestinationAdvisoryConsumer.h"
#include <cms/Topic.h>
#include <cms/Message.h>
@@ -470,11 +447,11 @@
if( session == NULL ) {
throw NullPointerException(
- __FILE__, __LINE__, "Session Object passed was Null." );
+ __FILE__, __LINE__, "Session Object passed was Null." );
}
std::auto_ptr<cms::Topic> advisories( session->createTopic(
- "ActiveMQ.Advisory.TempTopic,ActiveMQ.Advisory.TempQueue" ) );
+ "ActiveMQ.Advisory.TempTopic,ActiveMQ.Advisory.TempQueue" ) );
this->session = session;
this->consumer.reset( session->createConsumer( advisories.get() ) );
@@ -488,15 +465,15 @@
////////////////////////////////////////////////////////////////////////////////
void TempDestinationAdvisoryConsumer::onMessage( const cms::Message* message ) {
- if( message->getCMSType() == "Advisory" ) {
+ if( message->getCMSType() == "Advisory" ) {
- std::cout << "Received an Advisory Message!" << std::endl;
+ std::cout << "Received an Advisory Message!" << std::endl;
const ActiveMQMessage* amqMessage =
dynamic_cast<const ActiveMQMessage*>( message );
if( amqMessage != NULL && amqMessage->getDataStructure() != NULL ) {
- std::cout << "Advisory Message contains a Command Object!" << std::endl;
+ std::cout << "Advisory Message contains a Command Object!" << std::endl;
try {
@@ -506,32 +483,31 @@
unsigned char operationType = info->getOperationType();
if( operationType == ActiveMQConstants::DESTINATION_REMOVE_OPERATION ) {
- std::cout << "Temporary Destination {"
+ std::cout << "Temporary Destination {"
<< info->getDestination()->getPhysicalName()
- << "} Removed."
+ << "} Removed."
<< std::endl;
} else if( operationType == ActiveMQConstants::DESTINATION_ADD_OPERATION ) {
- std::cout << "Temporary Destination {"
+ std::cout << "Temporary Destination {"
<< info->getDestination()->getPhysicalName()
- << "} Added."
+ << "} Added."
<< std::endl;
} else {
- std::cout << "ERROR: I have no Idea what just happened!"
+ std::cout << "ERROR: I have no Idea what just happened!"
<< std::endl;
}
} catch( ClassCastException& ex ) {
- std::cout << "ERROR: Expected the Command to be a DestinationInfo, "
- << "it wasn't so PANIC!!"
+ std::cout << "ERROR: Expected the Command to be a DestinationInfo, "
+ << "it wasn't so PANIC!!"
<< std::endl;
}
}
} else {
- std::cout << "Received a Non-Advisory Message!" << std::endl;
+ std::cout << "Received a Non-Advisory Message!" << std::endl;
}
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/cms/how-do-i-prevent-autoconf-from-enabling-openssl-support.xml b/cms/how-do-i-prevent-autoconf-from-enabling-openssl-support.xml
index 99c203f..d490535 100644
--- a/cms/how-do-i-prevent-autoconf-from-enabling-openssl-support.xml
+++ b/cms/how-do-i-prevent-autoconf-from-enabling-openssl-support.xml
@@ -1,7 +1,6 @@
<div class="wiki-content maincontent"><p>In some cases you may not want to build in support for OpenSSL, since the Autotools script do this automatically we have provided a means to disable this, just add the <em>disable-ssl</em> options to your configure and no SSL support will be added:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>./configure --disable-ssl
-</pre>
-</div></div></div>
+<structured-macro ac:macro-id="b274ecb8-c81f-4c58-93c0-7c845fe29265" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+./configure --disable-ssl
+</plain-text-body></structured-macro></div>
diff --git a/cms/how-do-i-use-the-ssl-transport.xml b/cms/how-do-i-use-the-ssl-transport.xml
index b32da0f..0e0054f 100644
--- a/cms/how-do-i-use-the-ssl-transport.xml
+++ b/cms/how-do-i-use-the-ssl-transport.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><p>The first thing you need to do in order to use the SSL Transport in ActiveMQ-CPP is to build the library with SSL support enabled, for that see the <a shape="rect" href="building-faqs.xml">Build FAQs</a>.</p>
+<div class="wiki-content maincontent"><p>The first thing you need to do in order to use the SSL Transport in ActiveMQ-CPP is to build the library with SSL support enabled, for that see the <link><page ri:content-title="Building FAQs"></page><link-body>Build FAQs</link-body></link>.</p>
<p>Once you have a build that supports the SSL protocol then its pretty simple, just replace the use of the <em>TCP</em> Transport in your connection URI with SSL, for example: </p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>tcp://broker1:61616
-</pre>
-</div></div>
+<structured-macro ac:macro-id="52f589ed-9f33-48fd-967b-efabc07ffa0c" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+tcp://broker1:61616
+</plain-text-body></structured-macro>
<p>becomes:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>ssl://broker1:61616
-</pre>
-</div></div>
+<structured-macro ac:macro-id="859b73ed-9e01-48b7-86ce-19bcdab4acb2" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ssl://broker1:61616
+</plain-text-body></structured-macro>
<p>You should note that in order to validate that the certificate that the broker sends is the one we want we must validate the "Common Name (CN)" field from the certificate against the host-name in the URI. If you have trouble connecting to the broker one of the first things to check it if your host-name matches the broker certificate common name.</p>
<p>That's almost it, there's just a couple other things you need might need to do. The SSL transport needs to know whether or not to trust the certificate that the Broker sends to it, for this you need to set a property in the Decaf library (this is the native library ActiveMQ-CPP uses for cross platform support). The property you set tells the library where to find either the Broker's Certificate or the Certificate of the Authority that signed the broker's certificate. If you are using the Failover Transport (which you should be) in conjunction with the SSL Transport then its best to set the property to point to the certificate that signed all your broker's certificates. Here's what the code looks like:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>
+<structured-macro ac:macro-id="f9f78a4d-7595-4914-843a-687c8868dfd4" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+
#include <decaf/lang/System.h>
...
decaf::lang::System::setProperty( "decaf.net.ssl.trustStore", "<path to Certificate file>/certificate.pem" );
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
<p>One thing to note here is that since we are using OpenSSL as our SSL Engine the Certificate needs to be in PEM format.</p></div>
diff --git a/cms/index.xml b/cms/index.xml
index 7407747..3df83c7 100644
--- a/cms/index.xml
+++ b/cms/index.xml
@@ -1,84 +1,2 @@
-<div class="wiki-content maincontent"><p>CMS (stands for C++ Messaging Service) is a JMS-like API for C++ for interfacing with Message Brokers such as <a shape="rect" class="external-link" href="http://activemq.apache.org">Apache ActiveMQ</a>. CMS helps to make your C++ client code much neater and easier to follow. To get a better feel for CMS try the <a shape="rect" href="api.xml">API</a> Reference. ActiveMQ-CPP is a client only library, a message broker such as <a shape="rect" class="external-link" href="http://activemq.apache.org">Apache ActiveMQ</a> is still needed for your clients to communicate.</p><p>Our implementation of CMS is called ActiveMQ-CPP, which has an architecture that allows for pluggable transports and wire formats. Currently we support the <a shape="rect" href="openwire-support.xml">OpenWire</a> and <a shape="rect" href="stomp-support.xml">Stomp</a> protocols, both over TCP and SSL, we also now support a Failover Transport for more reliable client operation. In addition to CMS, ActiveMQ-CPP also provides a robust set of classes that support platform independent constructs such as threading, I/O, sockets, etc. You may find many of these utilities very useful, such as a Java like Thread class or the "synchronized" macro that let's you use a Java-like synchronization on any object that implements the activemq::concurrent::Synchronizable interface. ActiveMQ-CPP is released under the <a shape="rect" class="external-link" href="http://www.apache.org/">Apache</a> <a shape="rect" class="external-link" href="http://www.apache.org/licenses/LICENSE-2.0.html">2.0 License</a></p><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="index.data/ActiveMQ-CPP.png" data-image-src="/confluence/download/attachments/45919/ActiveMQ-CPP.png?version=3&modificationDate=1176898417000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="4180" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="ActiveMQ-CPP.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="45919" data-linked-resource-container-version="55"></span></p><h3 id="Index-LatestNewsItems.">Latest News Items.</h3><p>
-
-
-
-</p><div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/02/24/activemq-cpp-v394-released.xml">ActiveMQ-CPP v3.9.4 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Feb 24, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small fix to ensure failed producer create throws an exception, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-394-release.html">here</a>.</p></div></div></div></div></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/04/01/activemq-cpp-v393-released.xml">ActiveMQ-CPP v3.9.3 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Apr 01, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small fix to ensure failed producer create throws an exception, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-393-release.html">here</a>.</p></div></div></div></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/02/09/activemq-cpp-v392-released.xml">ActiveMQ-CPP v3.9.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Feb 09, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small STOMP protocol fix, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-392-release.html">here</a>.</p></div></div></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2015/12/04/activemq-cpp-v391-released.xml">ActiveMQ-CPP v3.9.1 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Dec 04, 2015</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-391-release.html">here</a>.</p></div></div></div>
- </div>
-
-
- </div>
- <h3 id="Index-ToseeolderNewspostings.">To see older News postings.</h3><ul><li><a shape="rect" href="news.xml">Get all the Apache ActiveMQ-CPP News Here!</a></li></ul></div>
+<div class="wiki-content maincontent"><p>CMS (stands for C++ Messaging Service) is a JMS-like API for C++ for interfacing with Message Brokers such as <a shape="rect" href="http://activemq.apache.org">Apache ActiveMQ</a>. CMS helps to make your C++ client code much neater and easier to follow. To get a better feel for CMS try the <link><page ri:content-title="API"></page></link> Reference. ActiveMQ-CPP is a client only library, a message broker such as <a shape="rect" href="http://activemq.apache.org">Apache ActiveMQ</a> is still needed for your clients to communicate.</p><p>Our implementation of CMS is called ActiveMQ-CPP, which has an architecture that allows for pluggable transports and wire formats. Currently we support the <link><page ri:content-title="OpenWire Support"></page><plain-text-link-body>OpenWire</plain-text-link-body></link> and <link><page ri:content-title="Stomp Support"></page><plain-text-link-body>Stomp</plain-text-link-body></link> protocols, both over TCP and SSL, we also now support a Failover Transport for more reliable client operation. In addition to CMS, ActiveMQ-CPP also provides a robust set of classes that support platform independent constructs such as threading, I/O, sockets, etc. You may find many of these utilities very useful, such as a Java like Thread class or the "synchronized" macro that let's you use a Java-like synchronization on any object that implements the activemq::concurrent::Synchronizable interface. ActiveMQ-CPP is released under the <a shape="rect" href="http://www.apache.org/">Apache</a> <a shape="rect" href="http://www.apache.org/licenses/LICENSE-2.0.html">2.0 License</a></p><p><image><attachment ri:filename="ActiveMQ-CPP.png"></attachment></image></p><h3>Latest News Items.</h3><p><structured-macro ac:macro-id="6bca84f5-0f2c-4d7e-b7b6-b55e56478097" ac:name="blog-posts" ac:schema-version="1"><parameter ac:name="">4</parameter></structured-macro></p><h3>To see older News postings.</h3><ul><li><link><page ri:content-title="News"></page><plain-text-link-body>Get all the Apache ActiveMQ-CPP News Here!</plain-text-link-body></link></li></ul></div>
diff --git a/cms/mailing-lists.xml b/cms/mailing-lists.xml
index 240f33b..075cb46 100644
--- a/cms/mailing-lists.xml
+++ b/cms/mailing-lists.xml
@@ -1,11 +1,11 @@
-<div class="wiki-content maincontent"><p>The following mailing lists are available. Before posting you might want to read the <a shape="rect" class="unresolved" href="#">Tips for getting help</a>.</p>
+<div class="wiki-content maincontent"><p>The following mailing lists are available. Before posting you might want to read the <link><page ri:content-title="Tips for getting help"></page></link>.</p>
-<h2 id="MailingLists-ApacheMailingLists">Apache Mailing Lists</h2>
+<h2>Apache Mailing Lists</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> List Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Subscribe </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Unsubscribe </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Archive </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Nabble (Online Forums) </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> activemq User List </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="mailto:users-subscribe@activemq.apache.org" rel="nofollow">Subscribe</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="mailto:users-unsubscribe@activemq.apache.org" rel="nofollow">Unsubscribe</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://mail-archives.apache.org/mod_mbox/activemq-users/">Archive</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.nabble.com/ActiveMQ---User-f2356.html" rel="nofollow">Nabble</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> activemq Developer List </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="mailto:dev-subscribe@activemq.apache.org" rel="nofollow">Subscribe</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="mailto:dev-unsubscribe@activemq.apache.org" rel="nofollow">Unsubscribe</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://mail-archives.apache.org/mod_mbox/activemq-dev/">Archive</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.nabble.com/ActiveMQ---Dev-f2355.html" rel="nofollow">Nabble</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> activemq SCM List </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="mailto:commits-subscribe@activemq.apache.org" rel="nofollow">Subscribe</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="mailto:commits-unsubscribe@activemq.apache.org" rel="nofollow">Unsubscribe</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://mail-archives.apache.org/mod_mbox/activemq-commits/">Archive</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> List Name </p></th><th colspan="1" rowspan="1"><p> Subscribe </p></th><th colspan="1" rowspan="1"><p> Unsubscribe </p></th><th colspan="1" rowspan="1"><p> Archive </p></th><th colspan="1" rowspan="1"><p> Nabble (Online Forums) </p></th></tr><tr><td colspan="1" rowspan="1"><p> activemq User List </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="mailto:users-subscribe@activemq.apache.org">Subscribe</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="mailto:users-unsubscribe@activemq.apache.org">Unsubscribe</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://mail-archives.apache.org/mod_mbox/activemq-users/">Archive</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.nabble.com/ActiveMQ---User-f2356.html">Nabble</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> activemq Developer List </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="mailto:dev-subscribe@activemq.apache.org">Subscribe</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="mailto:dev-unsubscribe@activemq.apache.org">Unsubscribe</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://mail-archives.apache.org/mod_mbox/activemq-dev/">Archive</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.nabble.com/ActiveMQ---Dev-f2355.html">Nabble</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> activemq SCM List </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="mailto:commits-subscribe@activemq.apache.org">Subscribe</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="mailto:commits-unsubscribe@activemq.apache.org">Unsubscribe</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://mail-archives.apache.org/mod_mbox/activemq-commits/">Archive</a> </p></td><td colspan="1" rowspan="1"><p> </p></td></tr></tbody></table>
-<h3 id="MailingLists-DiscussionForums">Discussion Forums</h3>
+<h3>Discussion Forums</h3>
-<p>If you prefer you could use our <a shape="rect" href="discussion-forums.xml">Discussion Forums</a> which are sync'd with the above mailing lists.</p></div>
+<p>If you prefer you could use our <link><page ri:content-title="Discussion Forums"></page></link> which are sync'd with the above mailing lists.</p></div>
diff --git a/cms/navigation.xml b/cms/navigation.xml
index 20c7883..2a377e9 100644
--- a/cms/navigation.xml
+++ b/cms/navigation.xml
@@ -1,40 +1,41 @@
-<div class="wiki-content maincontent"><h3 id="Navigation-Overview"><a shape="rect" href="index.xml">Overview</a></h3>
+<div class="wiki-content maincontent"><h3><link><page ri:content-title="Index"></page><link-body>Overview</link-body></link></h3>
-<ul class="alternate"><li><a shape="rect" href="index.xml">Index</a></li><li><a shape="rect" href="news.xml">News</a></li><li><a shape="rect" href="getting-started.xml">Getting Started</a></li><li><a shape="rect" href="tutorials.xml">Tutorials</a></li><li><a shape="rect" href="api.xml">API</a></li><li><a shape="rect" href="faq.xml">FAQ</a></li><li><a shape="rect" href="download.xml">Download</a></li></ul>
+<ul class="alternate"><li><link><page ri:content-title="Index"></page></link></li><li><link><page ri:content-title="News"></page></link></li><li><link><page ri:content-title="Getting Started"></page></link></li><li><link><page ri:content-title="Tutorials"></page></link></li><li><link><page ri:content-title="API"></page></link></li><li><link><page ri:content-title="FAQ"></page></link></li><li><link><page ri:content-title="Download"></page></link></li></ul>
-<h3 id="Navigation-Connectivity"><a shape="rect" href="connectivity.xml">Connectivity</a></h3>
+<h3><link><page ri:content-title="Connectivity"></page></link></h3>
-<ul class="alternate"><li><a shape="rect" href="stomp-support.xml">Stomp</a></li><li><a shape="rect" href="openwire-support.xml">OpenWire</a></li></ul>
+<ul class="alternate"><li><link><page ri:content-title="Stomp Support"></page><link-body>Stomp</link-body></link></li><li><link><page ri:content-title="OpenWire Support"></page><link-body>OpenWire</link-body></link></li></ul>
-<h3 id="Navigation-UsingActiveMQ-CPP"><a shape="rect" href="using-activemq-cpp.xml">Using ActiveMQ-CPP</a></h3>
+<h3><link><page ri:content-title="Using ActiveMQ-CPP"></page></link></h3>
-<ul class="alternate"><li><a shape="rect" href="getting-started.xml">Getting Started</a></li><li><a shape="rect" href="cms-api-overview.xml">CMS API Overview</a></li><li><a shape="rect" href="example.xml">Example</a></li><li><a shape="rect" href="configuring.xml">Configuring</a></li></ul>
+<ul class="alternate"><li><link><page ri:content-title="Getting Started"></page></link></li><li><link><page ri:content-title="CMS API Overview"></page></link></li><li><link><page ri:content-title="Example"></page></link></li><li><link><page ri:content-title="Configuring"></page></link></li></ul>
-<h3 id="Navigation-Search">Search</h3>
+<h3>Search</h3>
-<p></p><p>
-</p><div>
-<form enctype="application/x-www-form-urlencoded" method="get" action="http://www.google.com/search" style="font-size: 10px;">
-<input type="hidden" name="ie" value="UTF-8">
-<input type="hidden" name="oe" value="UTF-8">
- <input maxlength="255" type="text" name="q" size="15" value="value"><br clear="none">
- <input type="submit" name="btnG" value="Search">
- <input type="hidden" name="domains" value="activemq.apache.org">
- <input type="hidden" name="sitesearch" value="activemq.apache.org">
-</form>
+<p></p><p><structured-macro ac:macro-id="a6958b0d-f81f-414e-a092-9833bafc9aea" ac:name="html" ac:schema-version="1"><plain-text-body>
+<DIV>
+<FORM action="http://www.google.com/search" method="get" style="font-size: 10px;">
+<INPUT name="ie" type="hidden" value="UTF-8"></INPUT>
+<INPUT name="oe" type="hidden" value="UTF-8"></INPUT>
+ <INPUT maxlength="255" name="q" size="15" type="text" value></INPUT><BR></BR>
+ <INPUT name="btnG" type="submit" value="Search"></INPUT>
+ <INPUT name="domains" type="hidden" value="activemq.apache.org"></INPUT>
+ <INPUT name="sitesearch" type="hidden" value="activemq.apache.org"></INPUT>
+</FORM>
+</DIV>
+</plain-text-body></structured-macro></p><p></p>
+
+<h3><link><page ri:content-title="Community"></page></link></h3>
+
+<ul class="alternate"><li><link><page ri:content-title="Support"></page></link></li><li><a shape="rect" href="http://activemq.apache.org/contributing.html">Contributing</a></li><li><a shape="rect" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a></li><li><a shape="rect" href="irc://irc.codehaus.org/activemq">IRC</a></li><li><a shape="rect" href="http://servlet.uwyn.com/drone/log/hausbot/activemq">IRC Log</a></li><li><link><page ri:content-title="Site"></page></link></li><li><a shape="rect" href="http://activemq.apache.org/team.html">Team</a></li></ul>
+
+
+
+<h3><link><page ri:content-title="Developers"></page></link></h3>
+
+<ul class="alternate"><li><link><page ri:content-title="Source"></page></link></li><li><link><page ri:content-title="Building"></page></link></li><li><link><page ri:content-title="Creating Distributions"></page></link></li></ul>
</div>
-<p></p>
-
-<h3 id="Navigation-Community"><a shape="rect" href="community.xml">Community</a></h3>
-
-<ul class="alternate"><li><a shape="rect" href="support.xml">Support</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/contributing.html">Contributing</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="irc://irc.codehaus.org/activemq" rel="nofollow">IRC</a></li><li><a shape="rect" class="external-link" href="http://servlet.uwyn.com/drone/log/hausbot/activemq" rel="nofollow">IRC Log</a></li><li><a shape="rect" href="site.xml">Site</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/team.html">Team</a></li></ul>
-
-
-
-<h3 id="Navigation-Developers"><a shape="rect" href="developers.xml">Developers</a></h3>
-
-<ul class="alternate"><li><a shape="rect" href="source.xml">Source</a></li><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="creating-distributions.xml">Creating Distributions</a></li></ul></div>
diff --git a/cms/news.xml b/cms/news.xml
index 60beb7f..e9dd923 100644
--- a/cms/news.xml
+++ b/cms/news.xml
@@ -1,206 +1,4 @@
-<div class="wiki-content maincontent"><h3 id="News-ActiveMQ-CPPNews">ActiveMQ-CPP News</h3>
+<div class="wiki-content maincontent"><h3>ActiveMQ-CPP News</h3>
-
-
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/02/24/activemq-cpp-v394-released.xml">ActiveMQ-CPP v3.9.4 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Feb 24, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small fix to ensure failed producer create throws an exception, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-394-release.html">here</a>.</p></div></div></div></div></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/04/01/activemq-cpp-v393-released.xml">ActiveMQ-CPP v3.9.3 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Apr 01, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small fix to ensure failed producer create throws an exception, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-393-release.html">here</a>.</p></div></div></div></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/02/09/activemq-cpp-v392-released.xml">ActiveMQ-CPP v3.9.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Feb 09, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a small STOMP protocol fix, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-392-release.html">here</a>.</p></div></div></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2015/12/04/activemq-cpp-v391-released.xml">ActiveMQ-CPP v3.9.1 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Dec 04, 2015</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-391-release.html">here</a>.</p></div></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2015/08/16/activemq-cpp-v390-released.xml">ActiveMQ-CPP v3.9.0 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Aug 16, 2015</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" class="external-link" href="http://activemq.apache.org/cms/activemq-cpp-390-release.html">here</a>.</p></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2014/07/18/activemq-cpp-v383-released.xml">ActiveMQ-CPP v3.8.3 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Jul 18, 2014</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.8.3+Release">here</a>.</p></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2013/12/10/activemq-cpp-v382-released.xml">ActiveMQ-CPP v3.8.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Dec 10, 2013</div>
-
- </div>
-
- <div class="wiki-content">
- <p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" href="activemq-cpp-382-release.xml">here</a>.</p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2013/09/19/activemq-cpp-v381-released.xml">ActiveMQ-CPP v3.8.1 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Sep 19, 2013</div>
-
- </div>
-
- <div class="wiki-content">
- <p>The next release of ActiveMQ-CPP is out featuring a critical memory leak fix, grab the source bundle <a shape="rect" href="activemq-cpp-381-release.xml">here</a>.</p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="/confluence/pages/viewpage.action?pageId=34019221">ActiveMQ-CPP v3.8.0 Released.</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Sep 07, 2013</div>
-
- </div>
-
- <div class="wiki-content">
- <p>The next release of ActiveMQ-CPP is out featuring a lot of stability fixes and a few new features. Download your copy from <a shape="rect" href="activemq-cpp-380-release.xml">here</a>.</p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2013/05/19/activemq-cpp-v370-released.xml">ActiveMQ-CPP v3.7.0 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on May 19, 2013</div>
-
- </div>
-
- <div class="wiki-content">
- <p>The next release of ActiveMQ-CPP is out featuring a lot of stability fixes. Download your copy from <a shape="rect" href="activemq-cpp-370-release.xml">here</a>.</p>
- </div>
-
-
- </div>
- </div>
+<structured-macro ac:macro-id="e56c7a5a-74fb-481b-8683-b438708ab851" ac:name="blog-posts" ac:schema-version="1"><parameter ac:name="">10</parameter></structured-macro></div>
diff --git a/cms/openssl-support.xml b/cms/openssl-support.xml
index 5240f0f..efe67f2 100644
--- a/cms/openssl-support.xml
+++ b/cms/openssl-support.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent"><p>This section covers building the ActiveMQ-CPP Library with support for SSL using the OpenSSL library</p>
-<ul class="childpages-macro"><li><a shape="rect" href="enable-openssl-support-with-autotools.xml">Enable OpenSSL support with autotools</a></li><li><a shape="rect" href="how-do-i-prevent-autoconf-from-enabling-openssl-support.xml">How do I prevent autoconf from enabling OpenSSL support</a></li><li><a shape="rect" href="how-to-enable-ssl-support-on-windows.xml">How to enable SSL support on Windows</a></li></ul></div>
+<structured-macro ac:macro-id="91699896-dbbe-43e4-b0fe-3ca45b430706" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/cms/openwire-support.xml b/cms/openwire-support.xml
index 4fe5ea4..e99adf5 100644
--- a/cms/openwire-support.xml
+++ b/cms/openwire-support.xml
@@ -1,5 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="OpenWireSupport-ActiveMQ-CPPOpenWireSupport">ActiveMQ-CPP OpenWire Support</h2>
+<div class="wiki-content maincontent"><h2>ActiveMQ-CPP OpenWire Support</h2>
-<p><a shape="rect" class="external-link" href="http://activemq.apache.org/openwire.html">OpenWire</a> is the native protocol used by the <a shape="rect" class="external-link" href="http://activemq.apache.org/">ActiveMQ</a>. As of version 2.0, ActiveMQ-CPP supports the OpenWire protocol, with a few exceptions.</p>
-<ul><li>ObjectMessage - We cannot reconstruct the object(s) contained in an ObjectMessage in C++, so if your application is subscribed to a queue or topic that has an ObjectMessage sent to it, you will receive the message but will not be able to extract an Object from it.</li></ul></div>
+<p><a shape="rect" href="http://activemq.apache.org/openwire.html">OpenWire</a> is the native protocol used by the <a shape="rect" href="http://activemq.apache.org/">ActiveMQ</a>. As of version 2.0, ActiveMQ-CPP supports the OpenWire protocol, with a few exceptions.</p>
+<ul><li>ObjectMessage - We cannot reconstruct the object(s) contained in an ObjectMessage in C++, so if your application is subscribed to a queue or topic that has an ObjectMessage sent to it, you will receive the message but will not be able to extract an Object from it.</li></ul>
+</div>
diff --git a/cms/overview.xml b/cms/overview.xml
index ab2fc3c..2ad050f 100644
--- a/cms/overview.xml
+++ b/cms/overview.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="Overview-OverviewofActiveMQ-CPP"><strong>Overview of ActiveMQ-CPP</strong></h2>
+<div class="wiki-content maincontent"><h2><strong>Overview of ActiveMQ-CPP</strong></h2>
<p>ActiveMQ CPP ships with a JMS 1.1-like API, called CMS. This helps to make your C++ client code much neater and easier to follow. In addition to CMS, ActiveMQ-CPP also provides a robust set of classes that support things such as threading, I/O, sockets, etc. You may find many of these classes useful, such as the "synchronized" macro that let's you use a Java-like synchronization on any object that implements the activemq::concurrent::Synchronizable interface.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="cms-api-overview.xml">CMS API Overview</a></li><li><a shape="rect" href="download.xml">Download</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-cpp-22-release.xml">ActiveMQ CPP 2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-10-release.xml">ActiveMQ-CPP 1.0 Release</a></li><li><a shape="rect" href="activemq-cpp-11-release.xml">ActiveMQ-CPP 1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-201-release.xml">ActiveMQ-CPP 2.0.1 Release</a></li><li><a shape="rect" href="activemq-cpp-20-release.xml">ActiveMQ-CPP 2.0 Release</a></li><li><a shape="rect" href="activemq-cpp-211-release.xml">ActiveMQ-CPP 2.1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-212-release.xml">ActiveMQ-CPP 2.1.2 Release</a></li><li><a shape="rect" href="activemq-cpp-213-release.xml">ActiveMQ-CPP 2.1.3 Release</a></li><li><a shape="rect" href="activemq-cpp-21-release.xml">ActiveMQ-CPP 2.1 Release</a></li><li><a shape="rect" href="activemq-cpp-221-release.xml">ActiveMQ-CPP 2.2.1 Release</a></li><li><a shape="rect" href="activemq-cpp-222-release.xml">ActiveMQ-CPP 2.2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-223-release.xml">ActiveMQ-CPP 2.2.3 Release</a></li><li><a shape="rect" href="activemq-cpp-224-release.xml">ActiveMQ-CPP 2.2.4 Release</a></li><li><a shape="rect" href="activemq-cpp-225-release.xml">ActiveMQ-CPP 2.2.5 Release</a></li><li><a shape="rect" href="activemq-cpp-226-release.xml">ActiveMQ-CPP 2.2.6 Release</a></li><li><a shape="rect" href="activemq-cpp-301-release.xml">ActiveMQ-CPP 3.0.1 Release</a></li><li><a shape="rect" href="activemq-cpp-30-release.xml">ActiveMQ-CPP 3.0 Release</a></li><li><a shape="rect" href="activemq-cpp-310-release.xml">ActiveMQ-CPP 3.1.0 Release</a></li><li><a shape="rect" href="activemq-cpp-311-release.xml">ActiveMQ-CPP 3.1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-312-release.xml">ActiveMQ-CPP 3.1.2 Release</a></li><li><a shape="rect" href="activemq-cpp-313-release.xml">ActiveMQ-CPP 3.1.3 Release</a></li><li><a shape="rect" href="activemq-cpp-320-release.xml">ActiveMQ-CPP 3.2.0 Release</a></li><li><a shape="rect" href="activemq-cpp-321-release.xml">ActiveMQ-CPP 3.2.1 Release</a></li><li><a shape="rect" href="activemq-cpp-322-release.xml">ActiveMQ-CPP 3.2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-323-release.xml">ActiveMQ-CPP 3.2.3 Release</a></li><li><a shape="rect" href="activemq-cpp-324-release.xml">ActiveMQ-CPP 3.2.4 Release</a></li><li><a shape="rect" href="activemq-cpp-325-release.xml">ActiveMQ-CPP 3.2.5 Release</a></li><li><a shape="rect" href="activemq-cpp-330-release.xml">ActiveMQ-CPP 3.3.0 Release</a></li><li><a shape="rect" href="activemq-cpp-340-release.xml">ActiveMQ-CPP 3.4.0 Release</a></li><li><a shape="rect" href="activemq-cpp-341-release.xml">ActiveMQ-CPP 3.4.1 Release</a></li><li><a shape="rect" href="activemq-cpp-342-release.xml">ActiveMQ-CPP 3.4.2 Release</a></li><li><a shape="rect" href="activemq-cpp-343-release.xml">ActiveMQ-CPP 3.4.3 Release</a></li><li><a shape="rect" href="activemq-cpp-344-release.xml">ActiveMQ-CPP 3.4.4 Release</a></li><li><a shape="rect" href="activemq-cpp-345-release.xml">ActiveMQ-CPP 3.4.5 Release</a></li><li><a shape="rect" href="activemq-cpp-350-release.xml">ActiveMQ-CPP 3.5.0 Release</a></li><li><a shape="rect" href="activemq-cpp-360-release.xml">ActiveMQ-CPP 3.6.0 Release</a></li><li><a shape="rect" href="activemq-cpp-370-release.xml">ActiveMQ-CPP 3.7.0 Release</a></li><li><a shape="rect" href="activemq-cpp-371-release.xml">ActiveMQ-CPP 3.7.1 Release</a></li><li><a shape="rect" href="activemq-cpp-380-release.xml">ActiveMQ-CPP 3.8.0 Release</a></li><li><a shape="rect" href="activemq-cpp-381-release.xml">ActiveMQ-CPP 3.8.1 Release</a></li><li><a shape="rect" href="activemq-cpp-382-release.xml">ActiveMQ-CPP 3.8.2 Release</a></li><li><a shape="rect" href="activemq-cpp-383-release.xml">ActiveMQ-CPP 3.8.3 Release</a></li><li><a shape="rect" href="activemq-cpp-384-release.xml">ActiveMQ-CPP 3.8.4 Release</a></li><li><a shape="rect" href="activemq-cpp-390-release.xml">ActiveMQ-CPP 3.9.0 Release</a></li><li><a shape="rect" href="activemq-cpp-391-release.xml">ActiveMQ-CPP 3.9.1 Release</a></li><li><a shape="rect" href="activemq-cpp-392-release.xml">ActiveMQ-CPP 3.9.2 Release</a></li><li><a shape="rect" href="activemq-cpp-393-release.xml">ActiveMQ-CPP 3.9.3 Release</a></li><li><a shape="rect" href="activemq-cpp-394-release.xml">ActiveMQ-CPP 3.9.4 Release</a></li><li><a shape="rect" href="activemq-cpp-libtool-and-packaging-notes.xml">ActiveMQ-CPP, libtool and packaging notes</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-cpp-product-version-number.xml">ActiveMQ-CPP product version number</a></li></ul></li><li><a shape="rect" href="cms-api-10-release.xml">CMS API 1.0 Release</a></li><li><a shape="rect" href="cms-api-11-release.xml">CMS API 1.1 Release</a></li><li><a shape="rect" href="cms-api-12-release.xml">CMS API 1.2 Release</a></li></ul></li><li><a shape="rect" href="getting-started.xml">Getting Started</a></li><li><a shape="rect" href="tutorials.xml">Tutorials</a><ul class="childpages-macro"><li><a shape="rect" href="handling-advisory-messages.xml">Handling Advisory Messages</a></li></ul></li></ul></div>
+<structured-macro ac:macro-id="822d0745-229f-433f-9c2d-e8e99ca5e74c" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/cms/privacy-policy.xml b/cms/privacy-policy.xml
index b6db1d7..e37a397 100644
--- a/cms/privacy-policy.xml
+++ b/cms/privacy-policy.xml
@@ -3,7 +3,7 @@
<ol><li>The IP address from which you access the website;</li><li>The type of browser and operating system you use to access our site;</li><li>The date and time you access our site;</li><li>The pages you visit; and</li><li>The addresses of pages from where you followed a link to our site.</li></ol>
-<p>Part of this information is gathered using a tracking cookie set by the <a shape="rect" class="external-link" href="http://www.google.com/analytics/" rel="nofollow">Google Analytics</a> service and handled by Google as described in their <a shape="rect" class="external-link" href="http://www.google.com/privacy.html" rel="nofollow">privacy policy</a>. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.</p>
+<p>Part of this information is gathered using a tracking cookie set by the <a shape="rect" href="http://www.google.com/analytics/">Google Analytics</a> service and handled by Google as described in their <a shape="rect" href="http://www.google.com/privacy.html">privacy policy</a>. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.</p>
<p>We use the gathered information to help us make our site more useful to visitors and to better understand how and when our site is used. We do not track or collect personally identifiable information or associate gathered data with any personally identifying information from other sources.</p>
diff --git a/cms/quicklinks.xml b/cms/quicklinks.xml
index b2afa0b..cb12a42 100644
--- a/cms/quicklinks.xml
+++ b/cms/quicklinks.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><a shape="rect" href="download.xml">Download</a> | <a shape="rect" href="api.xml">API</a> | <a shape="rect" href="source.xml">Source</a> | <a shape="rect" class="external-link" href="http://activemq.apache.org/discussion-forums.html">Forums</a> | <a shape="rect" href="support.xml">Support</a></p></div>
+<div class="wiki-content maincontent"><p><link><page ri:content-title="Download"></page></link> | <link><page ri:content-title="API"></page></link> | <link><page ri:content-title="Source"></page></link> | <a shape="rect" href="http://activemq.apache.org/discussion-forums.html">Forums</a> | <link><page ri:content-title="Support"></page></link></p></div>
diff --git a/cms/site.xml b/cms/site.xml
index b668a62..cbb9d5c 100644
--- a/cms/site.xml
+++ b/cms/site.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="banner.xml">Banner</a></li><li><a shape="rect" href="navigation.xml">Navigation</a><ul class="childpages-macro"><li><a shape="rect" href="api.xml">API</a></li><li><a shape="rect" href="connectivity.xml">Connectivity</a></li><li><a shape="rect" href="news.xml">News</a></li><li><a shape="rect" href="openwire-support.xml">OpenWire Support</a></li><li><a shape="rect" href="stomp-support.xml">Stomp Support</a></li><li><a shape="rect" href="support.xml">Support</a></li><li><a shape="rect" href="using-activemq-cpp.xml">Using ActiveMQ-CPP</a></li></ul></li><li><a shape="rect" href="quicklinks.xml">QuickLinks</a></li><li><a shape="rect" href="siteindex.xml">SiteIndex</a></li><li><a shape="rect" href="sitemap.xml">SiteMap</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="2c573859-3be9-461d-87eb-ad1dc060eb4b" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/cms/siteindex.xml b/cms/siteindex.xml
index 7fbad88..ad3584d 100644
--- a/cms/siteindex.xml
+++ b/cms/siteindex.xml
@@ -1,337 +1,3 @@
<div class="wiki-content maincontent">
-<h2>Space Index</h2>
-
-<p>
-<table class="grid" width="99%" cellspacing="0"><tr><td colspan="2" rowspan="1">
- <table width="100%"><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-0-9">0-9</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-A">A</a> ... 54</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-B">B</a> ... 3</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-C">C</a> ... 8</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-D">D</a> ... 3</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-E">E</a> ... 4</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-F">F</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-G">G</a> ... 3</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-H">H</a> ... 4</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-I">I</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-J">J</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-K">K</a> ... 0</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-L">L</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-M">M</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-N">N</a> ... 2</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-O">O</a> ... 3</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-P">P</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Q">Q</a> ... 1</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-R">R</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-S">S</a> ... 7</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-T">T</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-U">U</a> ... 2</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-V">V</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-W">W</a> ... 1</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-X">X</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Y">Y</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Z">Z</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-%21@%23%24">!@#$</a> ... 0</td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1"> </td></tr></table>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-0-9"></a>0-9</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-A"></a>A</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ+CPP+2.2+Release">ActiveMQ CPP 2.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release has seen a large restructuring of the codebase to separate out to platform code into a new package called decaf. We are now making use of the APR and APR-Util libraries for platform independence. Also many new tests and bug</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+1.0+Release">ActiveMQ-CPP 1.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is our first official release of ActiveMQ CPP. Some of the included features are: CMS - a JMS-like API Implementation of the Stomp protocol (compatable with AMQ broker 4.0.2 and later) Extensible architecture for supporting additio</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+1.1+Release">ActiveMQ-CPP 1.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This version fixes several bugs and adds a few new features. Updated interface for cms::BytesMessage - more JMS-like. Updated the MessageProducer interface to add multiple versions of the send method Fixed several memory leaks Now run o</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.0+Release">ActiveMQ-CPP 2.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This version fixes several bugs and adds a few new features. Full OpenWire v2 support! You can switch between openwire and stomp via the connection URL Temporary destinations when using OpenWire Added support for asynchronous send Fixed</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.0.1+Release">ActiveMQ-CPP 2.0.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This version fixes several small bugs that made their way into the 2.0 release. NOTE: Compatable with ActiveMQ Broker version >= 4.0.2 API Check out the API for this release here http://activemq.apache.org/cms/api_docs/activemqcpp-2.0.1</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.1+Release">ActiveMQ-CPP 2.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This version includes several bugfixes, as well as some new features. Also a lot of work has been done on performance and memory leaks. One new feature that has been highly anticipated is that we now build both shared and static librari</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.1.1+Release">ActiveMQ-CPP 2.1.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This version includes several bugfixes, as well as some new examples. Also a lot of work has been done on performance and memory leaks and stability. NOTE: Compatable with ActiveMQ Broker versions in the 4.0 family API Check out the AP</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.1.2+Release">ActiveMQ-CPP 2.1.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This version adds support for building the client code on the Solaris platform using the Sun Studio 11 compiler. Also makes some small improvements to the AutoConf scripts on various platforms. NOTE: Compatable with ActiveMQ Broker vers</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.1.3+Release">ActiveMQ-CPP 2.1.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This version adds more support for building the client code on the Solaris platform using the Sun Studio 11 and 12 compilers as well as fixed a small OS/X configure script problem. Also makes some small improvements to the AutoConf scri</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.2.1+Release">ActiveMQ-CPP 2.2.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor release incorporating several bug fixes that have been found since the 2.2 release. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API Check out the API for this release here http://activemq.apa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.2.2+Release">ActiveMQ-CPP 2.2.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor release that contains bugfixes that were found since the 2.2.1 release. Also in this release the there have been several meory leak fixes and threading issues resolved. The connection URI options have changed to reflect </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.2.3+Release">ActiveMQ-CPP 2.2.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor release that contains bugfixes that were found since the 2.2.2 release. This version adds support for responding to KeepAlive requests from the broker, and it now properly sets JMSX properties on both stomp and openwire </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.2.4+Release">ActiveMQ-CPP 2.2.4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor release that contains bugfixes that were found since the 2.2.3 release. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API Check out the API for this release here http://activemq.apache.org/cms/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.2.5+Release">ActiveMQ-CPP 2.2.5 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor release that contains bugfixes that were found since the 2.2.4 release. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API Check out the API for this release here http://activemq.apache.org/cms/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+2.2.6+Release">ActiveMQ-CPP 2.2.6 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor release that contains bugfixes that were found since the 2.2.5 release. Most noteably the code now properly encodes the strings sent in text message's and as properties in any message as proper modified UTF-8 encoded str</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.0+Release">ActiveMQ-CPP 3.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The 3.0 release is a major update the to ActiveMQ-CPP client code, many areas have been rewritten to enhance performance and improve stability. The following are some highlights of this release: Newly added Failover Transport CMS API ha</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.0.1+Release">ActiveMQ-CPP 3.0.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bugfix release that mainly addresses problems found in the Failover support added in the initial 3.0 release. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This release is based on the CMS 1.3 AP</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.1.0+Release">ActiveMQ-CPP 3.1.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new Major release of ActiveMQ-CPP. Many new features have been added and several bugs have been fixed. The client now has an connection Inactivity Monitor which allows it to more quickly detect when a TCP connection has been b</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.1.1+Release">ActiveMQ-CPP 3.1.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bug fix release that resolves several memory leaks found since the 3.1 release. Also a few small issues with some compilers was addressed. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This relea</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.1.2+Release">ActiveMQ-CPP 3.1.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bug fix release that resolves several crash bugs found since the 3.1.1 release. Also a few small issues with some compilers was addressed. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This relea</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.1.3+Release">ActiveMQ-CPP 3.1.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bug fix release that resolves an issue on Windows that could lead to deadlocks. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This release is based on the CMS 2.1 API. Check out the API for this </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.2.0+Release">ActiveMQ-CPP 3.2.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a major update for the ActiveMQ-CPP library adding in support for SSL, QueueBrowser, Message compression and more. Many issues have been addressed as well as work to improve performance and prevent memory leaks. The SSL support </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.2.1+Release">ActiveMQ-CPP 3.2.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release that addresses issues with the original 3.2.0 release for users on Windows, NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This release is based on the CMS 2.2 API. Check out the API</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.2.2+Release">ActiveMQ-CPP 3.2.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release that addresses issues with the 3.2.1 release. Several issues that users were seeing as segfaults from APR Atomics have been addressed as well as a fix for sending and receiving empty MapMessages. NOTE: Compatible</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.2.3+Release">ActiveMQ-CPP 3.2.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release that addresses issues with the 3.2.2 release. This release fixes an additional issue found in unmarshaling MapMessage objects on Windows as well as fixing a threading issue that causes invalid client Ids to be ge</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.2.4+Release">ActiveMQ-CPP 3.2.4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release that addresses issues with the 3.2.3 release. This release fixes an issue with the Stomp support as well as addressing some problems in the CMSTemplate classes. NOTE: Compatible with ActiveMQ Broker versions in t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.2.5+Release">ActiveMQ-CPP 3.2.5 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release that addresses issues with the 3.2.4 release. This release fixes a bug that was causing the client to segfault on Mac OS as well as fixing an issue with the SSL transport and X509v3 Certificates. Several small is</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.3.0+Release">ActiveMQ-CPP 3.3.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a major release of the ActiveMQ-CPP client which includes some API changes and several new features and improvements. Some additional methods have been added to the CMS API to make it easier to use. Some highlights for this rele</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.4.0+Release">ActiveMQ-CPP 3.4.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a major release of the ActiveMQ-CPP client which includes some API changes and several improvements. Some additional methods have been added to the CMS API to make it easier to use. Some highlights for this release: Added start </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.4.1+Release">ActiveMQ-CPP 3.4.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release of the ActiveMQ-CPP client which includes some fixes for issues found since the v3.4.0 release. Implements the Session recover method. Fixed some build issues on Mac with dynamic libs. Fixed an issue with BytesMe</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.4.2+Release">ActiveMQ-CPP 3.4.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release of the ActiveMQ-CPP client which includes some fixes for issues found since the v3.4.1 release. Some build issues on various platforms were resolved. A problem with setting the username / password from the Connec</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.4.3+Release">ActiveMQ-CPP 3.4.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release of the ActiveMQ-CPP client which includes some fixes for issues found since the v3.4.2 release. This release resolves some memory leaks found in the prior 3.4.x releases in the TCP transport and in the use of Tra</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.4.4+Release">ActiveMQ-CPP 3.4.4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release of the ActiveMQ-CPP client which includes some fixes for issues found since the v3.4.3 release. This release resolves some memory and thread leaks found in the prior 3.4.x releases having to do with Connection sh</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.4.5+Release">ActiveMQ-CPP 3.4.5 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a patch release of ActiveMQ-CPP that fixes several issues found since the v3.4.4 release. This release contains fixes for memory leaks that can occur when a socket connection is broken during a message marshal or unmarshal as we</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.5.0+Release">ActiveMQ-CPP 3.5.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new Major release of ActiveMQ-CPP with several new APIs and internal changes meant to improve overall stability of the C++ client. Besides a large amount of bug fixing and memory fixing this release also features a lot of new </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.6.0+Release">ActiveMQ-CPP 3.6.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new Major release of ActiveMQ-CPP, a lot of bugs have been fixed that were found in the v3.5.0 release which should reduce memory consumption and improve overall stability. NOTE: Compatible with ActiveMQ Broker versions in the</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.7.0+Release">ActiveMQ-CPP 3.7.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new Major release of ActiveMQ-CPP, a lot of bugs have been fixed that were found in the v3.6.0 release which should reduce memory consumption and improve overall stability. Some new features have been added as well. Added supp</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.7.1+Release">ActiveMQ-CPP 3.7.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new patch release of ActiveMQ-CPP, a lot of bugs have been fixed that were found in the v3.7.0 release which should reduce memory consumption and improve overall stability. Several compilation fixes were made as well so things</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.8.0+Release">ActiveMQ-CPP 3.8.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new major release of ActiveMQ-CPP, a few bugs have been fixed that were found in the v3.7.0 and v3.7.1 releases which should reduce memory consumption and improve overall stability. Several compilation fixes were made as well </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.8.1+Release">ActiveMQ-CPP 3.8.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new patch release that resolves a memory leak issue found in the 3.8.0 and 3.7.x releases. If you are running an older release you are strongly advised to upgrade (you can work around the leak by disabling message audit in you</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.8.2+Release">ActiveMQ-CPP 3.8.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new patch release that resolves some issues that have been found since the last patch release. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This release is based on the CMS 3.2 API. Check out th</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.8.3+Release">ActiveMQ-CPP 3.8.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new patch release that resolves some issues that have been found since the last patch release. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This release is based on the CMS 3.2 API. Check out th</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.8.4+Release">ActiveMQ-CPP 3.8.4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new patch release that resolves some issues that have been found since the last patch release. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This release is based on the CMS 3.2 API. Check out th</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.9.0+Release">ActiveMQ-CPP 3.9.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a new major release that resolves a number of issues found since the 3.8.x series was released. The client has been updated to include many of the same fixes that were placed into the ActiveMQ JMS client. Additional fixes for </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.9.1+Release">ActiveMQ-CPP 3.9.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor bugfix release of the ActiveMQ-CPP library that fixes a segfault that can occur when running against the latest ActiveMQ Artemis release along with a couple other minor fixes. NOTE: Compatible with ActiveMQ Broker versio</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.9.2+Release">ActiveMQ-CPP 3.9.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor patch release of the ActiveMQ-CPP library that fixes an issue with the way the STOMP protocol handles composite destinations. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This release is b</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.9.3+Release">ActiveMQ-CPP 3.9.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor patch release of the ActiveMQ-CPP library that fixes an issue with producer create no waiting for a response from the broker before returning which can lead to missed error on create situations. NOTE: Compatible with Act</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+3.9.4+Release">ActiveMQ-CPP 3.9.4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor patch release of the ActiveMQ-CPP library that fixes an issue in the Failover handling. NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family API This release is based on the CMS 3.2 API. Check out the</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+product+version+number">ActiveMQ-CPP product version number</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This is a DRAFT proposal and has not been adopted as official policy by this project. In order to facilitate the correct use of libtool and the preparation of binary packages for distribution on Debian, Red Hat, etc, it is beneficial to have a written pol</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+Stomp">ActiveMQ-CPP Stomp</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ-CPP Stomp Support Stomp is a simple text-based protocol supported by the ActiveMQ Broker that allows communication from a variety of clients (e.g. C++, Java, .NET, Ruby, Python, etc). If you'd like to learn more about the stomp protocol, go here </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP+Usage+FAQs">ActiveMQ-CPP Usage FAQs</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This section covers general questions on how to use various feature of the ActiveMQ-CPP Library</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/ActiveMQ-CPP%2C+libtool+and+packaging+notes">ActiveMQ-CPP, libtool and packaging notes</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ-CPP, libtool and packaging notes Introduction This page attempts to summarise information to be considered when configuring libtool when packaging ActiveMQ for distribution on Debian, Red Hat, Solaris. Concepts Product version numbers Please see </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/API">API</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ-CPP API ActiveMQ-CPP 3.6.x http://activemq.apache.org/cms/api_docs/activemqcpp-3.6.0/html/ ActiveMQ-CPP 3.9.x http://activemq.apache.org/cms/api_docs/activemqcpp-3.9.0/html/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Are+there+more+FAQ+Entries">Are there more FAQ Entries</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Are there more FAQ Entries? Yes, see the ActiveMQ Main FAQ http://activemq.apache.org/faq.html</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-B"></a>B</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Banner">Banner</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"><div id="asf_logo"> <div id="activemq_logo"> <a style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="http://activemq.apache.org/">ActiveMQ</a> <a style="float:ri</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Building">Building</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Dependencies libuuid On *nix sytems, the build requires the libuuid library that is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net/ http://e2fsprogs.sourceforge.net/ which is not always installed by default. On Fedora</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Building+FAQs">Building FAQs</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">These are general hints and tips on Building the Library on various platforms etc.</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-C"></a>C</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/CMS+API+1.0+Release">CMS API 1.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is the first official release of the C++ Messaging Service (CMS)!! CMS provides the following: JMS-like API (all pure-virtual classes) for messaging from C++ applications! Fairly mature API, having grown up under activemq-cpp Vendo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/CMS+API+1.1+Release">CMS API 1.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor release of the C++ Messaging Service (CMS). This release is was done as part of releasing ActiveMQ-CPP 2.1 and contains the following updates: Removed dependency on the ActiveMQ-CPP Properties class Added support for exp</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/CMS+API+1.2+Release">CMS API 1.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor release of the C++ Messaging Service (CMS). This release is was done as part of releasing ActiveMQ-CPP 2.1.1 and contains the following updates: Made read methods of BytesMessage const so that asynchronous consumers (onM</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/CMS+API+Overview">CMS API Overview</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What is CMS? The CMS API is a C++ corollary to the JMS API in Java which is used to send and receive messages from clients spread out across a network or located on the same machine. In CMS we've made every attempt to maintain as much parity with the JMS</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Community">Community</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Configuring">Configuring</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring ActiveMQ-CPP The configuration of ActiveMQ is so slick, we decided to take a similar approach with ActiveMQ-CPP. All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can conf</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Connectivity">Connectivity</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ-CPP has been designed to have a pluggable connector architecture. Out of the box, it comes with support for the following protocols: Stomp OpenWire</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Creating+Distributions">Creating Distributions</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Creating a Distribution of ActiveMQ-CPP This should give you an idea of the steps involved with creating a new distribution of ActiveMQ-CPP. This content was extracted from http://www.apache.org/dev/mirror-guide-bodewig.html http://www.apache.org/dev/mirr</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-D"></a>D</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Developers">Developers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Discussion+Forums">Discussion Forums</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Before posting you might want to read the Tips for getting help. Many users prefer to use online forums rather than joining a mail list which can lead to lots more email traffic so we use the online forums at Nabble forums http://www.nabble.com/ActiveMQ-f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Download">Download</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Download ActiveMQ-CPP Latest Releases The current stable release of the code is the ActiveMQ-CPP 3.9.4 Release. All Releases</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-E"></a>E</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Enable+OpenSSL+support+with+autotools">Enable OpenSSL support with autotools</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">When you build the ActiveMQ-CPP library using the GNU AutoTools the Configure script will automatically search for OpenSSL on your system and enable support for it in the code if its found. The search might fail if you have installed OpenSSL in a non-stan</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml">Errors from libstd++.la on Solaris 10 using the GNU Compiler</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">On Solaris 10 the libstdc++.la file is empty which causes the build to fail. In order to fix this you must fill in the libstdc++.la file with the correct information. There are two versions, one for 32 bit and one for 64 bit. The following listings show t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="errors-saying-no-rule-to-make-target.xml">Errors saying "no rule to make target"</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you get errors when building on solaris that indicate that there is no rule to make a target file one thing to check is if the file is really in your build tree. If you extracted the source archive with the sun Tar command then you may be missing files</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Example">Example</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ-CPP in Action In the example below we create two classes HolloWorldConsumer and HelloWorldProducer each of which runs in its own thread. The Producer sends TextMessage objects via a MessageProducer instance to the ActiveMQ broker. The Consumer re</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-F"></a>F</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/FAQ">FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">FAQ Here are a list of commonly asked questions and answers. If you have any questions which are not on this list, please talk to us on the forums. We welcome contributions and this entire website is a wiki that you can edit so please join in and help us </div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-G"></a>G</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/General">General</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">General Questions about ActiveMQ's CMS client.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/General+Build+Issues">General Build Issues</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Error during configure: "error: libpthread not found!" Getting an error about libpthread not found even though its installed, in many cases indicates that the tool chain required to build the library isn't fully installed. One good place to start checkin</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Getting+Started">Getting Started</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Getting Started Guide Start off by getting a Download or by grabbing the Source and Building it.</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-H"></a>H</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Handling+Advisory+Messages">Handling Advisory Messages</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ supports advisory messages which allows you to watch the system using regular CMS messages. A few things that you can currently do with advisory messages are: See consumers, producers and connections starting and stopping See temporary destinatio</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/How+do+I+prevent+autoconf+from+enabling+OpenSSL+support">How do I prevent autoconf from enabling OpenSSL support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">In some cases you may not want to build in support for OpenSSL, since the Autotools script do this automatically we have provided a means to disable this, just add the disable-ssl options to your configure and no SSL support will be added: ./configure --d</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/How+do+I+use+the+SSL+Transport">How do I use the SSL Transport</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The first thing you need to do in order to use the SSL Transport in ActiveMQ-CPP is to build the library with SSL support enabled, for that see the Build FAQs. Once you have a build that supports the SSL protocol then its pretty simple, just replace the u</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/How+to+enable+SSL+support+on+Windows">How to enable SSL support on Windows</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">To enable support for SSL on Windows you first need to obtain a build of the OpenSSL libraries for Windows (See the OpenSSL site for details). Once you have the OpenSSL package for Windows installed you need to add the HAVE_OPENSSL preprocessor directive </div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-I"></a>I</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-homepage" title="Home page">Home page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Index">Index</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">CMS (stands for C++ Messaging Service) is a JMS-like API for C++ for interfacing with Message Brokers such as Apache ActiveMQ http://activemq.apache.org. CMS helps to make your C++ client code much neater and easier to follow. To get a better feel for CMS</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-J"></a>J</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-K"></a>K</h4>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-L"></a>L</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-M"></a>M</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Mailing+Lists">Mailing Lists</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The following mailing lists are available. Before posting you might want to read the Tips for getting help. Apache Mailing Lists List Name Subscribe Unsubscribe Archive Nabble (Online Forums) activemq User List Subscribe mailto:users-subscribe@activemq.ap</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-N"></a>N</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Navigation">Navigation</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview Index News Getting Started Tutorials API FAQ Download Connectivity Stomp OpenWire Using ActiveMQ-CPP Getting Started CMS API Overview Example Configuring Search <DIV> <FORM action="http://www.google.com/search" method="get" style="font-size: 10px</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/News">News</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ-CPP News</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-O"></a>O</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/OpenSSL+Support">OpenSSL Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This section covers building the ActiveMQ-CPP Library with support for SSL using the OpenSSL library</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/OpenWire+Support">OpenWire Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ-CPP OpenWire Support OpenWire http://activemq.apache.org/openwire.html is the native protocol used by the ActiveMQ http://activemq.apache.org/. As of version 2.0, ActiveMQ-CPP supports the OpenWire protocol, with a few exceptions. ObjectMessage -</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Overview">Overview</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview of ActiveMQ-CPP ActiveMQ CPP ships with a JMS 1.1-like API, called CMS. This helps to make your C++ client code much neater and easier to follow. In addition to CMS, ActiveMQ-CPP also provides a robust set of classes that support things such as t</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-P"></a>P</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Privacy+Policy">Privacy Policy</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Information about your use of this website is collected using server access logs and a tracking cookie. The collected information consists of the following: The IP address from which you access the website; The type of browser and operating system you use</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Q"></a>Q</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/QuickLinks">QuickLinks</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Download | API | Source | Forums http://activemq.apache.org/discussion-forums.html | Support</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-R"></a>R</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-S"></a>S</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Site">Site</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/SiteIndex">SiteIndex</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">{index}{index}</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/SiteMap">SiteMap</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Index</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Solaris+Platform">Solaris Platform</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Information specific to builds on Solaris</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Source">Source</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The ActiveMQ-CPP client code is maintained in a Git repository. Web Browsing of Git To browse via the web: https://git-wip-us.apache.org/repos/asf?p=activemq-cpp.git https://git-wip-us.apache.org/repos/asf?p=activemq-cpp.git Checking out from Git git clon</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Stomp+Support">Stomp Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ-CPP Stomp Support Stomp http://stomp.codehaus.org is a simple text-based protocol supported by the ActiveMQ Broker that allows communication from a variety of clients (e.g. C++, Java, .NET, Ruby, Python, etc). If you'd like to learn more about th</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Support">Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Getting Help If you are experiencing problems using ActiveMQ then please first try the FAQ. If you cannot find your issue then report your problem to our Issue Tracker http://issues.apache.org/activemq/browse/AMQCPP You may also find it useful to discuss </div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-T"></a>T</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Tutorials">Tutorials</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Tutorials This section lists the various tutorials and articles that cover how to use the ActiveMQ-CPP client. Handling Advisory Messages</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-U"></a>U</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Using+ActiveMQ-CPP">Using ActiveMQ-CPP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Using ActiveMQ-CPP Getting Started CMS API Overview Example Configuring</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/Using+the+Solaris+CC+compiler">Using the Solaris CC compiler</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This Entry only applies to the Sun Studio 11 and above compiler. The Sun Workshop compiler does not seem to support building this library. In order to use the Solaris compiler you must set some environment variables and then run the autogen.sh and configu</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-V"></a>V</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-W"></a>W</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/AMQCPP/What+is+ActiveMQ+CPP">What is ActiveMQ CPP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What is Apache ActiveMQ CPP? Apache ActiveMQ CPP is the C++ client for accessing the ActiveMQ http://activemq.apache.org/ message broker.</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-X"></a>X</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Y"></a>Y</h4>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Z"></a>Z</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-%21@%23%24"></a>!@#$</h4>
- </td></tr></table>
-</p></div>
+<structured-macro ac:macro-id="84416491-aa9f-4fb6-8f22-ed119beb626a" ac:name="unmigrated-inline-wiki-markup" ac:schema-version="1"><plain-text-body>{index}{index}</plain-text-body></structured-macro></div>
diff --git a/cms/sitemap.xml b/cms/sitemap.xml
index 2738b44..6a812b5 100644
--- a/cms/sitemap.xml
+++ b/cms/sitemap.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="activemq-cpp-stomp.xml">ActiveMQ-CPP Stomp</a></li><li><a shape="rect" href="community.xml">Community</a><ul class="childpages-macro"><li><a shape="rect" href="faq.xml">FAQ</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-cpp-usage-faqs.xml">ActiveMQ-CPP Usage FAQs</a><ul class="childpages-macro"><li><a shape="rect" href="how-do-i-use-the-ssl-transport.xml">How do I use the SSL Transport</a></li></ul></li><li><a shape="rect" href="building-faqs.xml">Building FAQs</a><ul class="childpages-macro"><li><a shape="rect" href="general-build-issues.xml">General Build Issues</a></li><li><a shape="rect" href="openssl-support.xml">OpenSSL Support</a><ul class="childpages-macro"><li><a shape="rect" href="enable-openssl-support-with-autotools.xml">Enable OpenSSL support with autotools</a></li><li><a shape="rect" href="how-do-i-prevent-autoconf-from-enabling-openssl-support.xml">How do I prevent autoconf from enabling OpenSSL support</a></li><li><a shape="rect" href="how-to-enable-ssl-support-on-windows.xml">How to enable SSL support on Windows</a></li></ul></li><li><a shape="rect" href="solaris-platform.xml">Solaris Platform</a><ul class="childpages-macro"><li><a shape="rect" href="errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml">Errors from libstd++.la on Solaris 10 using the GNU Compiler</a></li><li><a shape="rect" href="errors-saying-no-rule-to-make-target.xml">Errors saying "no rule to make target"</a></li><li><a shape="rect" href="using-the-solaris-cc-compiler.xml">Using the Solaris CC compiler</a></li></ul></li></ul></li><li><a shape="rect" href="discussion-forums.xml">Discussion Forums</a><ul class="childpages-macro"><li><a shape="rect" href="mailing-lists.xml">Mailing Lists</a></li></ul></li><li><a shape="rect" href="general.xml">General</a><ul class="childpages-macro"><li><a shape="rect" href="are-there-more-faq-entries.xml">Are there more FAQ Entries</a></li><li><a shape="rect" href="what-is-activemq-cpp.xml">What is ActiveMQ CPP</a></li></ul></li></ul></li><li><a shape="rect" href="privacy-policy.xml">Privacy Policy</a></li></ul></li><li><a shape="rect" href="configuring.xml">Configuring</a></li><li><a shape="rect" href="developers.xml">Developers</a><ul class="childpages-macro"><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="creating-distributions.xml">Creating Distributions</a></li><li><a shape="rect" href="source.xml">Source</a></li></ul></li><li><a shape="rect" href="example.xml">Example</a></li><li><a shape="rect" href="overview.xml">Overview</a><ul class="childpages-macro"><li><a shape="rect" href="cms-api-overview.xml">CMS API Overview</a></li><li><a shape="rect" href="download.xml">Download</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-cpp-22-release.xml">ActiveMQ CPP 2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-10-release.xml">ActiveMQ-CPP 1.0 Release</a></li><li><a shape="rect" href="activemq-cpp-11-release.xml">ActiveMQ-CPP 1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-201-release.xml">ActiveMQ-CPP 2.0.1 Release</a></li><li><a shape="rect" href="activemq-cpp-20-release.xml">ActiveMQ-CPP 2.0 Release</a></li><li><a shape="rect" href="activemq-cpp-211-release.xml">ActiveMQ-CPP 2.1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-212-release.xml">ActiveMQ-CPP 2.1.2 Release</a></li><li><a shape="rect" href="activemq-cpp-213-release.xml">ActiveMQ-CPP 2.1.3 Release</a></li><li><a shape="rect" href="activemq-cpp-21-release.xml">ActiveMQ-CPP 2.1 Release</a></li><li><a shape="rect" href="activemq-cpp-221-release.xml">ActiveMQ-CPP 2.2.1 Release</a></li><li><a shape="rect" href="activemq-cpp-222-release.xml">ActiveMQ-CPP 2.2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-223-release.xml">ActiveMQ-CPP 2.2.3 Release</a></li><li><a shape="rect" href="activemq-cpp-224-release.xml">ActiveMQ-CPP 2.2.4 Release</a></li><li><a shape="rect" href="activemq-cpp-225-release.xml">ActiveMQ-CPP 2.2.5 Release</a></li><li><a shape="rect" href="activemq-cpp-226-release.xml">ActiveMQ-CPP 2.2.6 Release</a></li><li><a shape="rect" href="activemq-cpp-301-release.xml">ActiveMQ-CPP 3.0.1 Release</a></li><li><a shape="rect" href="activemq-cpp-30-release.xml">ActiveMQ-CPP 3.0 Release</a></li><li><a shape="rect" href="activemq-cpp-310-release.xml">ActiveMQ-CPP 3.1.0 Release</a></li><li><a shape="rect" href="activemq-cpp-311-release.xml">ActiveMQ-CPP 3.1.1 Release</a></li><li><a shape="rect" href="activemq-cpp-312-release.xml">ActiveMQ-CPP 3.1.2 Release</a></li><li><a shape="rect" href="activemq-cpp-313-release.xml">ActiveMQ-CPP 3.1.3 Release</a></li><li><a shape="rect" href="activemq-cpp-320-release.xml">ActiveMQ-CPP 3.2.0 Release</a></li><li><a shape="rect" href="activemq-cpp-321-release.xml">ActiveMQ-CPP 3.2.1 Release</a></li><li><a shape="rect" href="activemq-cpp-322-release.xml">ActiveMQ-CPP 3.2.2 Release</a></li><li><a shape="rect" href="activemq-cpp-323-release.xml">ActiveMQ-CPP 3.2.3 Release</a></li><li><a shape="rect" href="activemq-cpp-324-release.xml">ActiveMQ-CPP 3.2.4 Release</a></li><li><a shape="rect" href="activemq-cpp-325-release.xml">ActiveMQ-CPP 3.2.5 Release</a></li><li><a shape="rect" href="activemq-cpp-330-release.xml">ActiveMQ-CPP 3.3.0 Release</a></li><li><a shape="rect" href="activemq-cpp-340-release.xml">ActiveMQ-CPP 3.4.0 Release</a></li><li><a shape="rect" href="activemq-cpp-341-release.xml">ActiveMQ-CPP 3.4.1 Release</a></li><li><a shape="rect" href="activemq-cpp-342-release.xml">ActiveMQ-CPP 3.4.2 Release</a></li><li><a shape="rect" href="activemq-cpp-343-release.xml">ActiveMQ-CPP 3.4.3 Release</a></li><li><a shape="rect" href="activemq-cpp-344-release.xml">ActiveMQ-CPP 3.4.4 Release</a></li><li><a shape="rect" href="activemq-cpp-345-release.xml">ActiveMQ-CPP 3.4.5 Release</a></li><li><a shape="rect" href="activemq-cpp-350-release.xml">ActiveMQ-CPP 3.5.0 Release</a></li><li><a shape="rect" href="activemq-cpp-360-release.xml">ActiveMQ-CPP 3.6.0 Release</a></li><li><a shape="rect" href="activemq-cpp-370-release.xml">ActiveMQ-CPP 3.7.0 Release</a></li><li><a shape="rect" href="activemq-cpp-371-release.xml">ActiveMQ-CPP 3.7.1 Release</a></li><li><a shape="rect" href="activemq-cpp-380-release.xml">ActiveMQ-CPP 3.8.0 Release</a></li><li><a shape="rect" href="activemq-cpp-381-release.xml">ActiveMQ-CPP 3.8.1 Release</a></li><li><a shape="rect" href="activemq-cpp-382-release.xml">ActiveMQ-CPP 3.8.2 Release</a></li><li><a shape="rect" href="activemq-cpp-383-release.xml">ActiveMQ-CPP 3.8.3 Release</a></li><li><a shape="rect" href="activemq-cpp-384-release.xml">ActiveMQ-CPP 3.8.4 Release</a></li><li><a shape="rect" href="activemq-cpp-390-release.xml">ActiveMQ-CPP 3.9.0 Release</a></li><li><a shape="rect" href="activemq-cpp-391-release.xml">ActiveMQ-CPP 3.9.1 Release</a></li><li><a shape="rect" href="activemq-cpp-392-release.xml">ActiveMQ-CPP 3.9.2 Release</a></li><li><a shape="rect" href="activemq-cpp-393-release.xml">ActiveMQ-CPP 3.9.3 Release</a></li><li><a shape="rect" href="activemq-cpp-394-release.xml">ActiveMQ-CPP 3.9.4 Release</a></li><li><a shape="rect" href="activemq-cpp-libtool-and-packaging-notes.xml">ActiveMQ-CPP, libtool and packaging notes</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-cpp-product-version-number.xml">ActiveMQ-CPP product version number</a></li></ul></li><li><a shape="rect" href="cms-api-10-release.xml">CMS API 1.0 Release</a></li><li><a shape="rect" href="cms-api-11-release.xml">CMS API 1.1 Release</a></li><li><a shape="rect" href="cms-api-12-release.xml">CMS API 1.2 Release</a></li></ul></li><li><a shape="rect" href="getting-started.xml">Getting Started</a></li><li><a shape="rect" href="tutorials.xml">Tutorials</a><ul class="childpages-macro"><li><a shape="rect" href="handling-advisory-messages.xml">Handling Advisory Messages</a></li></ul></li></ul></li><li><a shape="rect" href="site.xml">Site</a><ul class="childpages-macro"><li><a shape="rect" href="banner.xml">Banner</a></li><li><a shape="rect" href="navigation.xml">Navigation</a><ul class="childpages-macro"><li><a shape="rect" href="api.xml">API</a></li><li><a shape="rect" href="connectivity.xml">Connectivity</a></li><li><a shape="rect" href="news.xml">News</a></li><li><a shape="rect" href="openwire-support.xml">OpenWire Support</a></li><li><a shape="rect" href="stomp-support.xml">Stomp Support</a></li><li><a shape="rect" href="support.xml">Support</a></li><li><a shape="rect" href="using-activemq-cpp.xml">Using ActiveMQ-CPP</a></li></ul></li><li><a shape="rect" href="quicklinks.xml">QuickLinks</a></li><li><a shape="rect" href="siteindex.xml">SiteIndex</a></li><li><a shape="rect" href="sitemap.xml">SiteMap</a></li></ul></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="402b6cdf-a16e-41b8-9406-a92393c21df8" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Index"></page></link></parameter></structured-macro></div>
diff --git a/cms/solaris-platform.xml b/cms/solaris-platform.xml
index 8719c09..5b2092e 100644
--- a/cms/solaris-platform.xml
+++ b/cms/solaris-platform.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent"><p>Information specific to builds on Solaris</p>
-<ul class="childpages-macro"><li><a shape="rect" href="errors-from-libstdla-on-solaris-10-using-the-gnu-compiler.xml">Errors from libstd++.la on Solaris 10 using the GNU Compiler</a></li><li><a shape="rect" href="errors-saying-no-rule-to-make-target.xml">Errors saying "no rule to make target"</a></li><li><a shape="rect" href="using-the-solaris-cc-compiler.xml">Using the Solaris CC compiler</a></li></ul></div>
+<structured-macro ac:macro-id="95832b65-f0ee-4342-afe7-4cd88d8f0dde" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/cms/source.xml b/cms/source.xml
index 6ab40e4..10d6ac1 100644
--- a/cms/source.xml
+++ b/cms/source.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ-CPP client code is maintained in a Git repository.</p><h2 id="Source-WebBrowsingofGit">Web Browsing of Git</h2><p>To browse via the web:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq-cpp.git">https://git-wip-us.apache.org/repos/asf?p=activemq-cpp.git</a></p>
-</div></div><h2 id="Source-CheckingoutfromGit">Checking out from Git</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git</a></p>
-</div></div><p>Only project developers can commit to the Git tree via this method.</p><h3 id="Source-Branches">Branches</h3><p>We use the master for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at a specific branch in Git.</p><h2 id="Source-Buildingthecode">Building the code</h2><p>To then build the code see <a shape="rect" href="building.xml">Building</a>.</p><p> </p></div>
+<div class="wiki-content maincontent"><p>The ActiveMQ-CPP client code is maintained in a Git repository.</p><h2>Web Browsing of Git</h2><p>To browse via the web:</p><structured-macro ac:macro-id="1b43b591-29a9-491b-92b9-5597664298ce" ac:name="panel" ac:schema-version="1"><rich-text-body><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq-cpp.git">https://git-wip-us.apache.org/repos/asf?p=activemq-cpp.git</a></p></rich-text-body></structured-macro><h2>Checking out from Git</h2><structured-macro ac:macro-id="54ada66d-3766-48f1-a812-ced14197f814" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq-cpp.git">https://git-wip-us.apache.org/repos/asf/activemq-cpp.git</a></p></rich-text-body></structured-macro><p>Only project developers can commit to the Git tree via this method.</p><h3>Branches</h3><p>We use the master for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at a specific branch in Git.</p><h2>Building the code</h2><p>To then build the code see <link><page ri:content-title="Building"></page></link>.</p><p> </p></div>
diff --git a/cms/stomp-support.xml b/cms/stomp-support.xml
index 2dfa32b..20d7ad3 100644
--- a/cms/stomp-support.xml
+++ b/cms/stomp-support.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="StompSupport-ActiveMQ-CPPStompSupport">ActiveMQ-CPP Stomp Support</h2>
+<div class="wiki-content maincontent"><h2>ActiveMQ-CPP Stomp Support</h2>
-<p><a shape="rect" class="external-link" href="http://stomp.codehaus.org" rel="nofollow">Stomp</a> is a simple text-based protocol supported by the ActiveMQ Broker that allows communication from a variety of clients (e.g. C++, Java, .NET, Ruby, Python, etc). If you'd like to learn more about the stomp protocol, checkout <a shape="rect" class="external-link" href="http://stomp.codehaus.org" rel="nofollow">http://stomp.codehaus.org</a>. Also, you can see ActiveMQ extensions <a shape="rect" class="external-link" href="http://www.activemq.org/site/stomp.html" rel="nofollow">here</a>.</p>
+<p><a shape="rect" href="http://stomp.codehaus.org">Stomp</a> is a simple text-based protocol supported by the ActiveMQ Broker that allows communication from a variety of clients (e.g. C++, Java, .NET, Ruby, Python, etc). If you'd like to learn more about the stomp protocol, checkout <a shape="rect" href="http://stomp.codehaus.org">http://stomp.codehaus.org</a>. Also, you can see ActiveMQ extensions <a shape="rect" href="http://www.activemq.org/site/stomp.html">here</a>.</p>
-<p>The ActiveMQ-CPP implementation of the CMS API with stomp has some quirks, as it's a simple protocol and doesn't have the full capabilities of, say, <a shape="rect" href="openwire-support.xml">OpenWire</a>. The purpose of this page is to document these quirks so that users understand any strange behaviors that they may see occasionally.</p>
+<p>The ActiveMQ-CPP implementation of the CMS API with stomp has some quirks, as it's a simple protocol and doesn't have the full capabilities of, say, <link><page ri:content-title="OpenWire Support"></page><link-body>OpenWire</link-body></link>. The purpose of this page is to document these quirks so that users understand any strange behaviors that they may see occasionally.</p>
-<h3 id="StompSupport-MessagePropertiesinStompCMS">Message Properties in Stomp CMS</h3>
+<h3>Message Properties in Stomp CMS</h3>
<p>Since Stomp is strictly text-based, it does not support a way to specify the type of message properties (called "header" in stomp lingo). This means that a property sent as an integer could be read by a Stomp CMS client as any of: string, integer, short, long, etc.</p>
@@ -12,15 +12,15 @@
<p>The same goes for writing values to an outgoing message. You can call any of the methods (e.g. setIntProperty). The resulting value that goes out on the wire is still a string, however.</p>
-<h3 id="StompSupport-TemporaryTopicsandQueues"> Temporary Topics and Queues</h3>
+<h3> Temporary Topics and Queues</h3>
<p>The Stomp Protocol does not support the concept of temporary topics or queues.  If you call the createTemporaryTopic or createTemporaryQueue methods of cms::Session an exception of type NotSupportedException is thrown.  To implement request / response type semantics you will need to use standard Topics and Queues.</p>
-<h3 id="StompSupport-UsagenotesonSelectorswithStomp">Usage notes on Selectors with Stomp</h3>
+<h3>Usage notes on Selectors with Stomp</h3>
<p>Stomp as a general rule only allows one session per connection.  In ActiveMQ-CPP we have created a sort of virtual session that allows more than one session to be created per connection.  The one caveat is that there still can only be one selector on the main Stomp Session that we create, so whatever the first session is that is created with a selector will be the only selector that will actually have any effect as none of the newly created sessions will apply a selector even if you pass one in the creation of that Session.  </p>
-<h3 id="StompSupport-StompandFailover">Stomp and Failover</h3>
+<h3>Stomp and Failover</h3>
<p>Currently the Stomp protocol is at V1.0 and doesn't supply the necessary features in the protocol to allow the use of Failover with a Stomp based Transport. The draft version of Stomp v1.1 is under way and includes provisions for keep alive monitoring between broker and client which will allow for detection of dropped connections. Even with that support though there will be limitations on what can be accomplished on Failover of a Stomp client, transactions will not be able to be restored and message recovery will not be possible. A Stomp Failover would need to behave almost as a new Stomp connection to the Broker with automatic re-subscription for active consumers, all currently prefetched messages would be purged from the active consumers. Until the Stomp v1.1 spec is ratified and the ActiveMQ-CPP client code is updated to support this it is not recommended that you combine the Stomp transport and Failover transport.</p></div>
diff --git a/cms/support.xml b/cms/support.xml
index 76e2610..191544e 100644
--- a/cms/support.xml
+++ b/cms/support.xml
@@ -1,15 +1,15 @@
-<div class="wiki-content maincontent"><h2 id="Support-GettingHelp">Getting Help</h2>
+<div class="wiki-content maincontent"><h2>Getting Help</h2>
-<p>If you are experiencing problems using ActiveMQ then please first try the <a shape="rect" href="faq.xml">FAQ</a>. If you cannot find your issue then report your problem to our <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQCPP">Issue Tracker</a></p>
+<p>If you are experiencing problems using ActiveMQ then please first try the <link><page ri:content-title="FAQ"></page></link>. If you cannot find your issue then report your problem to our <a shape="rect" href="http://issues.apache.org/activemq/browse/AMQCPP">Issue Tracker</a></p>
-<p>You may also find it useful to discuss your issues with the community on the <a shape="rect" class="external-link" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a> or join one of our <a shape="rect" class="external-link" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a>.</p>
+<p>You may also find it useful to discuss your issues with the community on the <a shape="rect" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a> or join one of our <a shape="rect" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a>.</p>
-<h3 id="Support-Links">Links</h3>
+<h3>Links</h3>
-<ul><li><a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQCPP">Issue Tracker</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a></li><li><a shape="rect" href="faq.xml">FAQ</a></li></ul>
+<ul><li><a shape="rect" href="http://issues.apache.org/activemq/browse/AMQCPP">Issue Tracker</a></li><li><a shape="rect" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a></li><li><link><page ri:content-title="FAQ"></page></link></li></ul>
-<h3 id="Support-Gettingmorehelp">Getting more help</h3>
+<h3>Getting more help</h3>
-<p>For more details on how to get more help such as commercial support see the <a shape="rect" class="external-link" href="http://activemq.apache.org/support.html">main ActiveMQ Support page</a></p></div>
+<p>For more details on how to get more help such as commercial support see the <a shape="rect" href="http://activemq.apache.org/support.html">main ActiveMQ Support page</a></p></div>
diff --git a/cms/tutorials.xml b/cms/tutorials.xml
index 21ff6d6..f2c630d 100644
--- a/cms/tutorials.xml
+++ b/cms/tutorials.xml
@@ -1,6 +1,7 @@
-<div class="wiki-content maincontent"><h1 id="Tutorials-Tutorials">Tutorials</h1>
+<div class="wiki-content maincontent"><h1>Tutorials</h1>
<p>This section lists the various tutorials and articles that cover how to use the ActiveMQ-CPP client.</p>
-<ul><li> <a shape="rect" href="handling-advisory-messages.xml">Handling Advisory Messages</a></li></ul></div>
+<ul><li> <link><page ri:content-title="Handling Advisory Messages"></page></link></li></ul>
+</div>
diff --git a/cms/using-activemq-cpp.xml b/cms/using-activemq-cpp.xml
index 6cb2350..64e31a8 100644
--- a/cms/using-activemq-cpp.xml
+++ b/cms/using-activemq-cpp.xml
@@ -1,4 +1,5 @@
-<div class="wiki-content maincontent"><h2 id="UsingActiveMQ-CPP-UsingActiveMQ-CPP">Using ActiveMQ-CPP</h2>
+<div class="wiki-content maincontent"><h2>Using ActiveMQ-CPP</h2>
-<ul class="alternate"><li><a shape="rect" href="getting-started.xml">Getting Started</a></li><li><a shape="rect" href="cms-api-overview.xml">CMS API Overview</a></li><li><a shape="rect" href="example.xml">Example</a></li><li><a shape="rect" href="configuring.xml">Configuring</a></li></ul></div>
+<ul class="alternate"><li><link><page ri:content-title="Getting Started"></page></link></li><li><link><page ri:content-title="CMS API Overview"></page></link></li><li><link><page ri:content-title="Example"></page></link></li><li><link><page ri:content-title="Configuring"></page></link></li></ul>
+</div>
diff --git a/cms/using-the-solaris-cc-compiler.xml b/cms/using-the-solaris-cc-compiler.xml
index 6fbe8ba..88d7974 100644
--- a/cms/using-the-solaris-cc-compiler.xml
+++ b/cms/using-the-solaris-cc-compiler.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Use the Correct Compiler</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This Entry only applies to the Sun Studio 11 and above compiler. The Sun Workshop compiler does not seem to support building this library.</p></div></div><p>In order to use the Solaris compiler you must set some environment variables and then run the autogen.sh and configure scripts.</p><p>The following variable need to be set</p><ul><li>CC = cc</li><li>CXX = CC</li></ul><p>Underneath the configure script will append -library=stlport4 to the CC command so that the Sun Compiler will use STLPort instead of the broken version of STL that they link in by default and ActiveMQ-CPP uses features that it does not support. By using the STLPort library you get access to the features we need, but you must compile your application with STLPort as well to insure compatibility with our library.</p><p>So in you own makefiles you must pass -library=stlport4 to CC when you build and link.</p><p>You can find out more from Sun on this at <a shape="rect" class="external-link" href="http://www.oracle.com/technetwork/server-storage/solaris/cmp-stlport-libcstd-142559.html" rel="nofollow">STL Library Comparison</a></p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="e46d64c6-643d-4c72-9b67-1a85207ca018" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Use the Correct Compiler</parameter><rich-text-body><p>This Entry only applies to the Sun Studio 11 and above compiler. The Sun Workshop compiler does not seem to support building this library.</p></rich-text-body></structured-macro><p>In order to use the Solaris compiler you must set some environment variables and then run the autogen.sh and configure scripts.</p><p>The following variable need to be set</p><ul><li>CC = cc</li><li>CXX = CC</li></ul><p>Underneath the configure script will append -library=stlport4 to the CC command so that the Sun Compiler will use STLPort instead of the broken version of STL that they link in by default and ActiveMQ-CPP uses features that it does not support. By using the STLPort library you get access to the features we need, but you must compile your application with STLPort as well to insure compatibility with our library.</p><p>So in you own makefiles you must pass -library=stlport4 to CC when you build and link.</p><p>You can find out more from Sun on this at <a shape="rect" href="http://www.oracle.com/technetwork/server-storage/solaris/cmp-stlport-libcstd-142559.html">STL Library Comparison</a></p></div>
diff --git a/cms/what-is-activemq-cpp.xml b/cms/what-is-activemq-cpp.xml
index 0871e00..334e674 100644
--- a/cms/what-is-activemq-cpp.xml
+++ b/cms/what-is-activemq-cpp.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="WhatisActiveMQCPP-WhatisApacheActiveMQCPP?">What is Apache ActiveMQ CPP?</h2>
+<div class="wiki-content maincontent"><h2>What is Apache ActiveMQ CPP?</h2>
-<p>Apache ActiveMQ CPP is the C++ client for accessing the <a shape="rect" class="external-link" href="http://activemq.apache.org/">ActiveMQ</a> message broker.</p></div>
+<p>Apache ActiveMQ CPP is the C++ client for accessing the <a shape="rect" href="http://activemq.apache.org/">ActiveMQ</a> message broker.</p></div>
diff --git a/code-overview.xml b/code-overview.xml
index 8be68fb..b9132af 100644
--- a/code-overview.xml
+++ b/code-overview.xml
@@ -1,20 +1,20 @@
-<div class="wiki-content maincontent"><h1 id="CodeOverview-Architecture">Architecture</h1>
+<div class="wiki-content maincontent"><h1>Architecture</h1>
<p>The following section walks through the main parts of Apache ActiveMQ and links to the code to help you understand the layout</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.apache.org/images/BrokerDiagram.png" data-image-src="http://activemq.apache.org/images/BrokerDiagram.png"></span></p>
+<p><image><url ri:value="http://activemq.apache.org/images/BrokerDiagram.png"></url></image></p>
-<h2 id="CodeOverview-JMSClient">JMS Client</h2>
+<h2>JMS Client</h2>
-<p>The <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/package-summary.html">org.apache.activemq</a> package defines the core JMS client.</p>
+<p>The <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/package-summary.html">org.apache.activemq</a> package defines the core JMS client.</p>
-<h2 id="CodeOverview-Transport">Transport</h2>
+<h2>Transport</h2>
-<p>The JMS client and the message broker use the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/transport/Transport.html">Transport</a> abstraction for sending around command objects (like a distributed <em>Command Pattern</em>). A TransportChannel typically deals with some kind of networking mechanism (TCP sockets using BIO, using NIO, UDP / multicast, SSL over sockets, JXTA, EmberIO etc). See the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/transport/package-summary.html">org.apache.activemq.transport</a> package for more details</p>
+<p>The JMS client and the message broker use the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/transport/Transport.html">Transport</a> abstraction for sending around command objects (like a distributed <em>Command Pattern</em>). A TransportChannel typically deals with some kind of networking mechanism (TCP sockets using BIO, using NIO, UDP / multicast, SSL over sockets, JXTA, EmberIO etc). See the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/transport/package-summary.html">org.apache.activemq.transport</a> package for more details</p>
-<p>So the TransportChannel is basically concerned with sending and receiving <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/Command.html">Command</a> objects (each instance represents some kind of <em>command</em>). Packet is defined in the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">org.apache.activemq.command</a> package which defines all the JMS Message implementations classes (which are Commands) along with a number of other kinds of packets, like subsciptions, message acknowledgements, transactions and so forth.</p>
+<p>So the TransportChannel is basically concerned with sending and receiving <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/Command.html">Command</a> objects (each instance represents some kind of <em>command</em>). Packet is defined in the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">org.apache.activemq.command</a> package which defines all the JMS Message implementations classes (which are Commands) along with a number of other kinds of packets, like subsciptions, message acknowledgements, transactions and so forth.</p>
-<h2 id="CodeOverview-WireFormat">WireFormat</h2>
+<h2>WireFormat</h2>
<p>There are various possible ways of encoding messages onto a stream. We may wish to adapt to various different encoding mechanisms - such as to provide simpler wire formats for talking to C / JavaScript or to make a C# friendly encoding.</p>
@@ -22,79 +22,79 @@
<p>So if you wish to provide your own binary, <em>on the wire</em> protocol then we just need a WireFormat implementation of your protocol, then we can use this with any transport (TCP BIO, NIO, JXTA etc).</p>
-<p>We use <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/openwire/OpenWireFormat.html">OpenWireFormat</a> by default which is the most efficient & easiest format to use from Java code - so if both ends of the wire are Java then its highly recommended. Though other WireFormats are most welcome.</p>
+<p>We use <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/openwire/OpenWireFormat.html">OpenWireFormat</a> by default which is the most efficient & easiest format to use from Java code - so if both ends of the wire are Java then its highly recommended. Though other WireFormats are most welcome.</p>
-<h2 id="CodeOverview-DefaultWireFormat">Default Wire Format</h2>
+<h2>Default Wire Format</h2>
-<p>The default wire format writes a byte which indicates the kind of Command which is being sent (see the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.5.0/activemq-core/apidocs/org/apache/activemq/command/CommandTypes.html">CommandTypes</a> interface which defines all the int constants for each type of command.</p>
+<p>The default wire format writes a byte which indicates the kind of Command which is being sent (see the <a shape="rect" href="http://activemq.apache.org/maven/5.5.0/activemq-core/apidocs/org/apache/activemq/command/CommandTypes.html">CommandTypes</a> interface which defines all the int constants for each type of command.</p>
<p>The core JMS Message types each have a unique byte ID for</p>
<ul><li>Message</li><li>ObjectMessage</li><li>TextMessage</li><li>MapMessage</li><li>BytesMessage</li><li>StreamMessage</li></ul>
-<p>Then in addition there are various other <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">types of command</a> such as</p>
-<ul><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/ConnectionInfo.html">ConnectionInfo </a> for when a new connection is established with a message broker</li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/ConsumerInfo.html">ConsumerInfo</a> when a new consumer is created on a connection</li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/MessageAck.html">MessageAck</a> to acknowledge a message ID</li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/TransactionInfo.html">TransactionInfo</a> to denote a transaction</li></ul>
+<p>Then in addition there are various other <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">types of command</a> such as</p>
+<ul><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/ConnectionInfo.html">ConnectionInfo </a> for when a new connection is established with a message broker</li><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/ConsumerInfo.html">ConsumerInfo</a> when a new consumer is created on a connection</li><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/MessageAck.html">MessageAck</a> to acknowledge a message ID</li><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/TransactionInfo.html">TransactionInfo</a> to denote a transaction</li></ul>
-<p>There are a few others; the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">org.apache.activemq.command</a> package describes them in their gory detail.</p>
+<p>There are a few others; the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/command/package-summary.html">org.apache.activemq.command</a> package describes them in their gory detail.</p>
<p>Basically the DefaultWireFormat has a default encoding of each of these commands. So after the first byte which indicates the type of packet is written, there is a specific wire format per packet type.</p>
<p>For new wire formats it may be that you only need to support a small subset of these types. e.g. you might just have a simple publish message, consume message & message ack.</p>
-<h1 id="CodeOverview-MessageBroker">Message Broker</h1>
+<h1>Message Broker</h1>
-<p>The APIs for the message broker (server side of the JMS client) are defined in the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/package-summary.html">org.apache.activemq.broker</a>. There are various other packages which define different parts, from the message stores to the message routing and so forth. </p>
+<p>The APIs for the message broker (server side of the JMS client) are defined in the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/package-summary.html">org.apache.activemq.broker</a>. There are various other packages which define different parts, from the message stores to the message routing and so forth. </p>
-<p>To see an overview of these packages try the <a shape="rect" href="javadocs.xml">JavaDocs</a></p>
+<p>To see an overview of these packages try the <link><page ri:content-title="JavaDocs"></page></link></p>
<hr>
-<p></p><p>
-</p><h1>ActiveMQ System Overview</h1>
+<p></p><p><structured-macro ac:macro-id="80c4987f-5dd0-4292-8a02-226cf9e5c410" ac:name="html" ac:schema-version="1"><plain-text-body>
+<h1>ActiveMQ System Overview</h1>
-<h2>Introduction</h2>
+<h2>Introduction</h2>
-<p>ActiveMQ is the system responsible for creating and managing network connections used for communication between clients and the broker. This document hopes to outline the inner workings of this system with in order to make it easier to understand for future developers. It will give a high-level overview of the system and outline the major players. We will also cover a few other interesting classes that may be useful to others working on the system. Most of this document is written with the server side code in mind. This is because the client-side communication systems are architecturally simple and understanding the server will make understanding clients trivial by comparison.</p>
+<p>ActiveMQ is the system responsible for creating and managing network connections used for communication between clients and the broker. This document hopes to outline the inner workings of this system with in order to make it easier to understand for future developers. It will give a high-level overview of the system and outline the major players. We will also cover a few other interesting classes that may be useful to others working on the system. Most of this document is written with the server side code in mind. This is because the client-side communication systems are architecturally simple and understanding the server will make understanding clients trivial by comparison.</p>
-<p>We assume the reader has basic understanding of JMS. Refer to the official Java docs for more information.</p>
+<p>We assume the reader has basic understanding of JMS. Refer to the official Java docs for more information.</p>
-<h2>Overview: The Big Players</h2>
+<h2>Overview: The Big Players</h2>
-<p>The core classes involved in the ActiveMQ communication system are Transports. These include the <code>Transport</code>, <code>TransportServer</code>, and <code>TransportFactory</code> hierarchies. <code>Transport</code>s and <code>TransportServer</code>s are wrappers around sockets and server sockets respectively. <code>TransportFactory</code>s (as you may have guessed) are factories that create <code>Transport</code>s and <code>TransportServers</code>. <code>Transport</code>s are connected to <code>Broker</code>s and transmit <code>Command</code>s, which represent all major actions to be taken by ActiveMQ (more on this later). The following example illustrates how these pieces fit together.</p>
+<p>The core classes involved in the ActiveMQ communication system are Transports. These include the <code>Transport</code>, <code>TransportServer</code>, and <code>TransportFactory</code> hierarchies. <code>Transport</code>s and <code>TransportServer</code>s are wrappers around sockets and server sockets respectively. <code>TransportFactory</code>s (as you may have guessed) are factories that create <code>Transport</code>s and <code>TransportServers</code>. <code>Transport</code>s are connected to <code>Broker</code>s and transmit <code>Command</code>s, which represent all major actions to be taken by ActiveMQ (more on this later). The following example illustrates how these pieces fit together.</p>
-<p>The primary class needed to create a JMS "provider" application is the <code>Broker</code> class. The default ActiveMQ binary will use a <code>BrokerService</code> class to wrap around <code>Broker</code>s. When the application is started, it instantiates a <code>BrokerService</code> and instructs it to bind to a specific (local) address, say "tcp://localhost:61616". The <code>Broker</code> will use the scheme in the given address and find the proper <code>TransportFactory</code>, <code>TcpTransportFactory</code> in this example. This factory will then be used to create a <code>TcpTransportServer</code> that will be bound to "localhost:61616". Once the <code>TransportServer</code> is started, it will continually pole its socket for incoming connections. Successfully connected incoming sockets will be wrapped in a <code>TcpTransport</code> instance and passed back (indirectly) to the <code>Broker</code>. The <code>Broker</code> will then start polling the new <code>Transport</code> for incoming <code>Command</code>s to process.</p>
+<p>The primary class needed to create a JMS &quot;provider&quot; application is the <code>Broker</code> class. The default ActiveMQ binary will use a <code>BrokerService</code> class to wrap around <code>Broker</code>s. When the application is started, it instantiates a <code>BrokerService</code> and instructs it to bind to a specific (local) address, say &quot;tcp://localhost:61616&quot;. The <code>Broker</code> will use the scheme in the given address and find the proper <code>TransportFactory</code>, <code>TcpTransportFactory</code> in this example. This factory will then be used to create a <code>TcpTransportServer</code> that will be bound to &quot;localhost:61616&quot;. Once the <code>TransportServer</code> is started, it will continually pole its socket for incoming connections. Successfully connected incoming sockets will be wrapped in a <code>TcpTransport</code> instance and passed back (indirectly) to the <code>Broker</code>. The <code>Broker</code> will then start polling the new <code>Transport</code> for incoming <code>Command</code>s to process.</p>
-<p>The final pieces missing from the above example are the <code>TransportConnection</code> and <code>TransportConnector</code> classes. These classes are used to connect <code>Broker</code>s to <code>Transport</code>s and <code>TransportServer</code>s respectively.</p>
+<p>The final pieces missing from the above example are the <code>TransportConnection</code> and <code>TransportConnector</code> classes. These classes are used to connect <code>Broker</code>s to <code>Transport</code>s and <code>TransportServer</code>s respectively.</p>
-<h2>Class Details</h2>
+<h2>Class Details</h2>
-<p>This section will explain some of the more interesting details of the mentioned classes separately.
+<p>This section will explain some of the more interesting details of the mentioned classes separately.
-</p><h3>Transports, TransportServers, and TransportFactories</h3>
+<h3>Transports, TransportServers, and TransportFactories</h3>
-<p>The basic principles of how these classes operate are very simple: <code>Transport</code>s and <code>TransportServer</code>s are wrappers around sockets and server sockets used to hide implementation, and <code>TransportFactory</code>s are factory classes for the mentioned classes. The only caveats are how <code>TransportFactory</code>s are chosen and configured based on URIs they are supplied.</p>
+<p>The basic principles of how these classes operate are very simple: <code>Transport</code>s and <code>TransportServer</code>s are wrappers around sockets and server sockets used to hide implementation, and <code>TransportFactory</code>s are factory classes for the mentioned classes. The only caveats are how <code>TransportFactory</code>s are chosen and configured based on URIs they are supplied.</p>
-<p>The <code>TransportFactory</code> class is abstract and incapable of creating <code>Transport</code> or <code>TransportServer</code> classes directly. It, nevertheless, is the class used to create <code>Transport</code>s and <code>TransportServer</code>s. <code>TransportFactory</code> delegates its responsibilities to its subclasses based on the choice of subclass provided by the <code>FactoryFinder</code> class, which uses the URI's scheme to find a matching factory classes based on text files stored under the META-INF directory.</p>
+<p>The <code>TransportFactory</code> class is abstract and incapable of creating <code>Transport</code> or <code>TransportServer</code> classes directly. It, nevertheless, is the class used to create <code>Transport</code>s and <code>TransportServer</code>s. <code>TransportFactory</code> delegates its responsibilities to its subclasses based on the choice of subclass provided by the <code>FactoryFinder</code> class, which uses the URI's scheme to find a matching factory classes based on text files stored under the META-INF directory.</p>
-<p>Configuration of the created <code>Transport</code>s is done entirely to reflection. <code>Transport</code>s are configured through calls to <code>compositeConfigure</code>, which are made by the factory at the time of the <code>Transport</code>'s creation. <code>compositeConfigure</code> uses the <code>IntrospectionSupport</code> class to call setters for parameters passed in through the URI. For example, creating a <code>Transport</code> using the URI "ssl://localhost:61616/?needClientAuth=true" would result in the creation of an <code>SslTransport</code> object whose <code>setNeedClientAuth</code> method (if it exists) is called with the value of <code>true</code> immediately after its creation. <code>TransportServer</code>s operate in a similar fashion. The only difference is that the call to <code>IntrospectionSupport</code> is made from the <code>doBind</code> method of the <code>TransportFactory</code>.</p>
+<p>Configuration of the created <code>Transport</code>s is done entirely to reflection. <code>Transport</code>s are configured through calls to <code>compositeConfigure</code>, which are made by the factory at the time of the <code>Transport</code>'s creation. <code>compositeConfigure</code> uses the <code>IntrospectionSupport</code> class to call setters for parameters passed in through the URI. For example, creating a <code>Transport</code> using the URI &quot;ssl://localhost:61616/?needClientAuth=true&quot; would result in the creation of an <code>SslTransport</code> object whose <code>setNeedClientAuth</code> method (if it exists) is called with the value of <code>true</code> immediately after its creation. <code>TransportServer</code>s operate in a similar fashion. The only difference is that the call to <code>IntrospectionSupport</code> is made from the <code>doBind</code> method of the <code>TransportFactory</code>.</p>
-<h3>Commands</h3>
+<h3>Commands</h3>
-<p><code>Command</code>s are the main means for communication within <code>Broker</code>s. Each <code>Command</code> represents an action to be taken. <code>Command</code> subclasses include <code>ConnectionInfo</code>, <code>KeepAliveInfo</code>, and <code>Message</code>, which result in processing of new connections, maintenance of old connections, and processing of user messages respectively. These classes are de-serialized from <code>Transport</code>s using Marshalers. Whenever new data is found in a socket, the first byte is read to determine what type of <code>Command</code> being received. The proper Marshaller is then selected to de-serialize the <code>Command</code> (e.g. to de-serialize a <code>ConnectionInfo</code>, the <code>ConnectionInfoMarshaller</code> is used).</p>
+<p><code>Command</code>s are the main means for communication within <code>Broker</code>s. Each <code>Command</code> represents an action to be taken. <code>Command</code> subclasses include <code>ConnectionInfo</code>, <code>KeepAliveInfo</code>, and <code>Message</code>, which result in processing of new connections, maintenance of old connections, and processing of user messages respectively. These classes are de-serialized from <code>Transport</code>s using Marshalers. Whenever new data is found in a socket, the first byte is read to determine what type of <code>Command</code> being received. The proper Marshaller is then selected to de-serialize the <code>Command</code> (e.g. to de-serialize a <code>ConnectionInfo</code>, the <code>ConnectionInfoMarshaller</code> is used).</p>
-<h3>TransportConnections and TransportConnectors</h3>
+<h3>TransportConnections and TransportConnectors</h3>
-<p>Every <code>TransportServer</code> is connected to a <code>Broker</code> using a <code>TransportConnector</code>. The server's accept listener (which is called when a new <code>Transport</code> is constructed) is set to call the given <code>TransportConnector</code>'s <code>createConnection</code> method with the new <code>Transport</code>. When called, <code>createConnection</code> creates a new <code>TransportConnection</code> that links the given <code>Transport</code> and the supporting <code>Broker</code> together; the <code>Transport</code>'s transport listener is set to the <code>TransportConnection</code>'s <code>onCommand</code> method, which is then called whenever a new <code>Command</code> is received.</p>
+<p>Every <code>TransportServer</code> is connected to a <code>Broker</code> using a <code>TransportConnector</code>. The server's accept listener (which is called when a new <code>Transport</code> is constructed) is set to call the given <code>TransportConnector</code>'s <code>createConnection</code> method with the new <code>Transport</code>. When called, <code>createConnection</code> creates a new <code>TransportConnection</code> that links the given <code>Transport</code> and the supporting <code>Broker</code> together; the <code>Transport</code>'s transport listener is set to the <code>TransportConnection</code>'s <code>onCommand</code> method, which is then called whenever a new <code>Command</code> is received.</p>
-<p><code>Command</code>s and <code>AbstractConnection</code> (the superclass of <code>TransportConnection</code>) form a visitor pattern. <code>onCommand</code> will call <code>AbstractConnection</code>'s service method which will make a series of calls in line with the visitor patter and eventually, the proper <code>Command</code> subclass to be passed to the corresponding method of the <code>Broker</code> for processing.</p>
+<p><code>Command</code>s and <code>AbstractConnection</code> (the superclass of <code>TransportConnection</code>) form a visitor pattern. <code>onCommand</code> will call <code>AbstractConnection</code>'s service method which will make a series of calls in line with the visitor patter and eventually, the proper <code>Command</code> subclass to be passed to the corresponding method of the <code>Broker</code> for processing.</p>
-<h3>BrokerFilters and BrokerPlugins</h3>
+<h3>BrokerFilters and BrokerPlugins</h3>
-<p>While not used directly by the communication system, <code>BrokerFilter</code>s and <code>BrokerPlugin</code>s provide an effective and easy to use way of modifying Broker behavior. <code>BrokerFilter</code>s allow for one to modify a few <code>Broker</code> methods without touching the rest (as the name suggests). The <code>BrokerFilter</code> passes on all of its responsibilities to a <code>Broker</code> it receives in its constructor. Subclassing <code>BrokerFilter</code> allows us to perform additional actions before passing the work down to the underlying <code>Broker</code>.</p>
+<p>While not used directly by the communication system, <code>BrokerFilter</code>s and <code>BrokerPlugin</code>s provide an effective and easy to use way of modifying Broker behavior. <code>BrokerFilter</code>s allow for one to modify a few <code>Broker</code> methods without touching the rest (as the name suggests). The <code>BrokerFilter</code> passes on all of its responsibilities to a <code>Broker</code> it receives in its constructor. Subclassing <code>BrokerFilter</code> allows us to perform additional actions before passing the work down to the underlying <code>Broker</code>.</p>
-<p>The power of the <code>BrokerFilter</code> class comes from the fact that multiple filters can be cascaded to create different functional combinations. As an example, the <code>JaasAuthenticationBroker</code> is a subclass of <code>BrokerFilter</code> that modifies the methods used for adding and removing connections to allow for JAAS authentication. <code>AuthorizationBroker</code> is another subclass of <code>BrokerFilter</code>. This class modifies the destination regulation methods to enforce access levels. With this architecture, one can create a <code>JaasAuthenticationBroker</code> and have it use an <code>AuthorizationBroker</code> as its underlying broker (which would use another broker itself, etc.).</p>
+<p>The power of the <code>BrokerFilter</code> class comes from the fact that multiple filters can be cascaded to create different functional combinations. As an example, the <code>JaasAuthenticationBroker</code> is a subclass of <code>BrokerFilter</code> that modifies the methods used for adding and removing connections to allow for JAAS authentication. <code>AuthorizationBroker</code> is another subclass of <code>BrokerFilter</code>. This class modifies the destination regulation methods to enforce access levels. With this architecture, one can create a <code>JaasAuthenticationBroker</code> and have it use an <code>AuthorizationBroker</code> as its underlying broker (which would use another broker itself, etc.).</p>
-<p><code>BrokerPlugin</code>s are simple classes that will wrap their corresponding <code>Brokers</code> around the one they are given. i.e. "installing" an <code>AuthorizationPlugin</code> on an existing <code>Broker</code> will create an <code>AuthorizationBroker</code> that uses the original <code>Broker</code> internally. The main reason for the existence of <code>BrokerPlugin</code>s is to allow for one to configure the <code>Broker</code> used by the <code>BrokerService</code> class (either through code or XML configuration and spring).</p>
-<p></p></div>
+<p><code>BrokerPlugin</code>s are simple classes that will wrap their corresponding <code>Brokers</code> around the one they are given. i.e. &quot;installing&quot; an <code>AuthorizationPlugin</code> on an existing <code>Broker</code> will create an <code>AuthorizationBroker</code> that uses the original <code>Broker</code> internally. The main reason for the existence of <code>BrokerPlugin</code>s is to allow for one to configure the <code>Broker</code> used by the <code>BrokerService</code> class (either through code or XML configuration and spring).</p>
+</plain-text-body></structured-macro></p><p></p></div>
diff --git a/command-agent.xml b/command-agent.xml
index 2672f5a..cd299b2 100644
--- a/command-agent.xml
+++ b/command-agent.xml
@@ -1,41 +1,39 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Removed in 5.9</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><ul class="alternate"><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4406">https://issues.apache.org/jira/browse/AMQ-4406</a></li></ul>
-</div></div>
-<h2 id="CommandAgent-CommandAgent">Command Agent</h2>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="333621b0-0930-4059-9eeb-3ca28a0e2e4b" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Removed in 5.9</parameter><rich-text-body><ul class="alternate"><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4406">https://issues.apache.org/jira/browse/AMQ-4406</a></li></ul>
+</rich-text-body></structured-macro>
+<h2>Command Agent</h2>
<p>From 4.2 onwards Apache ActiveMQ allows you to communicate with a broker Command Agent to be able to perform administration queries and commands. This allows you to use the message bus itself to communicate with the message broker to list available queues, topics, subscriptions, to view metadata, browse queues and so forth.</p>
-<h3 id="CommandAgent-EnablingtheCommandAgent">Enabling the Command Agent</h3>
+<h3>Enabling the Command Agent</h3>
<p>To enable the command agent, in the activemq.xml (or your spring.xml you use to configure the broker) add the following</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b0bfb924-553e-4cc7-9cbf-d469cb1fa83f" ac:name="code" ac:schema-version="1"><plain-text-body>
<beans>
- <broker useJmx="true" xmlns="http://activemq.apache.org/schema/core">
+ <broker useJmx="true" xmlns="http://activemq.apache.org/schema/core">
...
<managementContext>
- <managementContext createConnector="true"/>
+ <managementContext createConnector="true"/>
</managementContext>
...
</broker>
- <commandAgent xmlns="http://activemq.apache.org/schema/core"/>
+ <commandAgent xmlns="http://activemq.apache.org/schema/core"/>
...
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The broker will then have a command agent connected which will listen on the topic <strong>ActiveMQ.Agent</strong>.</p>
-<h3 id="CommandAgent-UsingJabber(XMPP)totalktotheBroker">Using Jabber (XMPP) to talk to the Broker</h3>
+<h3>Using Jabber (XMPP) to talk to the Broker</h3>
-<p>You can use the <a shape="rect" href="xmpp.xml">XMPP</a> support to talk with the broker. For example follow the instructions in <a shape="rect" href="xmpp.xml">XMPP</a> to connect via a Jabber client, then just join the room <strong>ActiveMQ.Agent</strong> and talk to the broker!</p>
+<p>You can use the <link><page ri:content-title="XMPP"></page></link> support to talk with the broker. For example follow the instructions in <link><page ri:content-title="XMPP"></page></link> to connect via a Jabber client, then just join the room <strong>ActiveMQ.Agent</strong> and talk to the broker!</p>
-<p>The following image shows the <a shape="rect" class="external-link" href="http://jivesoftware.com/products/spark/" rel="nofollow">Spark</a> client in action talking to the broker</p>
+<p>The following image shows the <a shape="rect" href="http://jivesoftware.com/products/spark/">Spark</a> client in action talking to the broker</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="command-agent.data/help.png" data-image-src="/confluence/download/attachments/35957/help.png?version=1&modificationDate=1164085283000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3231" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="help.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35957" data-linked-resource-container-version="10"></span></p>
+<p><image><attachment ri:filename="help.png"></attachment></image></p>
-<h3 id="CommandAgent-Usingtheinteractiveconsole">Using the interactive console</h3>
+<h3>Using the interactive console</h3>
<p>The activemq-core module has a simple Java class called SimpleConsole which you can run in your IDE to get an interactive console for communicating with a broker over JMS. Type in the various commands (or help to get more help) and the results are returned on the console.</p></div>
diff --git a/community.xml b/community.xml
index aa5c720..a7d575a 100644
--- a/community.xml
+++ b/community.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="articles.xml">Articles</a></li><li><a shape="rect" href="books.xml">Books</a></li><li><a shape="rect" href="contributing.xml">Contributing</a></li><li><a shape="rect" href="discussion-forums.xml">Discussion Forums</a></li><li><a shape="rect" href="faq.xml">FAQ</a><ul class="childpages-macro"><li><a shape="rect" href="configuration.xml">Configuration</a></li><li><a shape="rect" href="developing-activemq.xml">Developing ActiveMQ</a></li><li><a shape="rect" href="errors.xml">Errors</a></li><li><a shape="rect" href="general.xml">General</a></li><li><a shape="rect" href="jms.xml">JMS</a></li><li><a shape="rect" href="persistence-questions.xml">Persistence Questions</a></li><li><a shape="rect" href="terminology.xml">Terminology</a></li><li><a shape="rect" href="using-apache-activemq.xml">Using Apache ActiveMQ</a></li></ul></li><li><a shape="rect" href="mailing-lists.xml">Mailing Lists</a><ul class="childpages-macro"><li><a shape="rect" href="all-forums.xml">All Forums</a></li><li><a shape="rect" href="developer-forum.xml">Developer Forum</a></li><li><a shape="rect" href="user-forum.xml">User Forum</a></li></ul></li><li><a shape="rect" href="pmc-templates.xml">PMC Templates</a></li><li><a shape="rect" href="privacy-policy.xml">Privacy Policy</a></li><li><a shape="rect" href="projects-using-activemq.xml">Projects Using ActiveMQ</a></li><li><a shape="rect" href="security-advisories.xml">Security Advisories</a></li><li><a shape="rect" href="sponsorship.xml">Sponsorship</a></li><li><a shape="rect" href="support.xml">Support</a></li><li><a shape="rect" href="team.xml">Team</a></li><li><a shape="rect" href="tips-for-getting-help.xml">Tips for getting help</a></li><li><a shape="rect" href="users.xml">Users</a></li></ul> </div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="ec681140-ace7-4fe2-9a89-04db683a3be3" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">2</parameter></structured-macro> </p></div>
diff --git a/compile-activemq-with-gcj.xml b/compile-activemq-with-gcj.xml
index f4ecd95..679c78a 100644
--- a/compile-activemq-with-gcj.xml
+++ b/compile-activemq-with-gcj.xml
@@ -1,38 +1,35 @@
<div class="wiki-content maincontent">
-<p>You can use <a shape="rect" class="external-link" href="http://gcc.gnu.org/java/" rel="nofollow">GCJ</a> to build ActiveMQ as a shared library you can reuse from C++.</p>
+<p>You can use <a shape="rect" href="http://gcc.gnu.org/java/">GCJ</a> to build ActiveMQ as a shared library you can reuse from C++.</p>
-<h3 id="CompileActiveMQwithGCJ-NativecompileActiveMQHOWTO">Native compile ActiveMQ HOWTO</h3>
+<h3>Native compile ActiveMQ HOWTO</h3>
-<h4 id="CompileActiveMQwithGCJ-Abstract">Abstract</h4>
+<h4>Abstract</h4>
<p>This document describes how to native compile ActiveMQ for use in a C++ environment. The version of ActiveMQ used is 3.2 in this howto. To compile you'll need GCC 4.0.2, or later, with both Java, and C/C++ support.</p>
-<h4 id="CompileActiveMQwithGCJ-ToolsSetup">Tools Setup</h4>
+<h4>Tools Setup</h4>
<p>If you don't already have GCC 4.0.2 installed you need to download and build it. See GCC manuals for complete instructions on how to build GCC but below is a short descriptions of the steps involved. The GCC build steps assumes that you already have an older GCC compiler installed.</p>
<ul><li>Unpack GCC into an arbitrary directory, for example /opt/gccbuild, and then create a separate output directory. Your directory structure should look similar to this;
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> /opt/gccbuild/gcc-4.0.2
+<structured-macro ac:macro-id="93a6eb11-be7b-4c05-8174-292ba8661d7f" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ /opt/gccbuild/gcc-4.0.2
/opt/gccbuild/output
-</pre>
-</div></div></li><li>Go to the output directory and run configure.
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> cd /opt/gccbuild/output
+</plain-text-body></structured-macro></li><li>Go to the output directory and run configure.
+<structured-macro ac:macro-id="3c50361b-035c-4d89-8c23-36ca3362dd3a" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ cd /opt/gccbuild/output
../gcc-4.0.2/configure --prefix=/opt/gcc402
--enable-shared
--enable-threads=posix
--enable-languages=c,c++,java
-</pre>
-</div></div></li><li>Run make.
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> make bootstrap
+</plain-text-body></structured-macro></li><li>Run make.
+<structured-macro ac:macro-id="d567ed56-a7ef-4dd5-97ea-ce0d50cdda52" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ make bootstrap
make install
-</pre>
-</div></div></li></ul>
+</plain-text-body></structured-macro></li></ul>
<ul><li>Download ActiveMQ and copy the JARs to a new empty directory /opt/app, including
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> activeio-1.1.jar
+<structured-macro ac:macro-id="0f658903-01d0-4f47-b9b5-96a68be84721" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ activeio-1.1.jar
activemq-core-3.2.jar
commons-logging-1.0.3.jar
concurrent-1.3.4.jar
@@ -41,18 +38,17 @@
geronimo-spec-jms-1.1-rc4.jar
geronimo-spec-jta-1.0.1B-rc4.jar
log4j-1.2.8.jar
-</pre>
-</div></div></li></ul>
+</plain-text-body></structured-macro></li></ul>
-<h4 id="CompileActiveMQwithGCJ-WritetheGlueCode">Write the Glue Code</h4>
+<h4>Write the Glue Code</h4>
<p>Either access the ActiveMQ classes directly from C++ or write a facade object in Java that handles all startup and shutdown logic of ActiveMQ. Save the glue files in the same directory as for the ActiveMQ jars.</p>
<p>An CNI example using a Java object starting the MQ.</p>
-<h5 id="CompileActiveMQwithGCJ-Bootstrap.cpp">Bootstrap.cpp</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>#include <gcj/cni.h>
+<h5>Bootstrap.cpp</h5>
+<structured-macro ac:macro-id="74a1f7b3-5e16-4ec2-a7bf-10b5c5130735" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+#include <gcj/cni.h>
#include <iostream>
#include <java/lang/System.h>
#include <java/lang/Throwable.h>
@@ -92,11 +88,10 @@
t->printStackTrace() ;
}
}
-</pre>
-</div></div>
-<h5 id="CompileActiveMQwithGCJ-MQAdapter.java">MQAdapter.java</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>import org.activemq.*;
+</plain-text-body></structured-macro>
+<h5>MQAdapter.java</h5>
+<structured-macro ac:macro-id="2fefcabc-d370-4e1e-b1a7-94883d3d3591" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+import org.activemq.*;
import java.util.Hashtable ;
import javax.jms.*;
import javax.naming.*;
@@ -180,17 +175,16 @@
}
}
}
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="CompileActiveMQwithGCJ-CompiletheJavaandC++Code">Compile the Java and C++ Code</h4>
+<h4>Compile the Java and C++ Code</h4>
<p>The Java code must be BC compiled to be able to dynamically link required classes as needed, see reference for more information on BC compilation. Use the suggested script to compile all ActiveMQ JARs and create a class map database.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Note</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Using -Bsymbolic does not seem to work, use -symbolic instead.</p></div></div>
+<structured-macro ac:macro-id="fa02f16f-d456-4563-950b-2c2b97495410" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Note</parameter><rich-text-body>
+<p>Using -Bsymbolic does not seem to work, use -symbolic instead.</p></rich-text-body></structured-macro>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> compile.sh:
+<structured-macro ac:macro-id="cc0d4ed4-9457-4de6-a80d-20aab110eddd" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ compile.sh:
#!/bin/sh
@@ -203,69 +197,61 @@
gcj -shared -findirect-dispatch -fjni -fPIC -Wl,-symbolic -o ${JAR_FILE}.so ${JAR_FILE}
gcj-dbtool -a classmap.db ${JAR_FILE} ${JAR_FILE}.so
done
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
<ul><li>Run the above script and set environment property GCJ_PROPERTIES.
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> ./compile.sh
+<structured-macro ac:macro-id="769e79ed-10bc-4951-99dd-ff9bb4786940" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ ./compile.sh
export GCJ_PROPERTIES="gnu.gcj.precompiled.db.path=/opt/app/classmap.db"
-</pre>
-</div></div></li></ul>
+</plain-text-body></structured-macro></li></ul>
<ul><li>Java compile MQAdapter.java
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> gcj --classpath=./geronimo-spec-jms-1.1-rc4.jar:./activemq-core-3.2.jar -C MQAdapter.java
-</pre>
-</div></div></li></ul>
+<structured-macro ac:macro-id="829b8d71-c144-4232-890b-1cc6b89514a6" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ gcj --classpath=./geronimo-spec-jms-1.1-rc4.jar:./activemq-core-3.2.jar -C MQAdapter.java
+</plain-text-body></structured-macro></li></ul>
<ul><li>Generate CNI header for MQAdapter.class
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> gcjh MQAdapter
-</pre>
-</div></div></li></ul>
+<structured-macro ac:macro-id="0c9263bc-06f4-4058-b810-168ce4bc66e9" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ gcjh MQAdapter
+</plain-text-body></structured-macro></li></ul>
<ul><li>JAR the Java glue code
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> fastjar cf MQAdapter.jar MQAdapter.class
-</pre>
-</div></div></li></ul>
+<structured-macro ac:macro-id="97d07144-63e6-4fcc-92da-bad27355c062" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ fastjar cf MQAdapter.jar MQAdapter.class
+</plain-text-body></structured-macro></li></ul>
<ul><li>Native compile the Java JAR into a shared library, add output directory to LD_LIBRARY_PATH.
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> gcj -shared -findirect-dispatch -fjni -fPIC -Wl,-symbolic -o MQAdapter.so MQAdapter.jar
+<structured-macro ac:macro-id="1d7dd7b5-cc71-4188-94a8-b06eff1d1889" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ gcj -shared -findirect-dispatch -fjni -fPIC -Wl,-symbolic -o MQAdapter.so MQAdapter.jar
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/app
-</pre>
-</div></div></li></ul>
+</plain-text-body></structured-macro></li></ul>
<ul><li>Compile the C++ code
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> g++ -c Bootstrap.cpp
-</pre>
-</div></div></li></ul>
+<structured-macro ac:macro-id="53b7d6ad-6df6-41ac-9966-78ee51ade665" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ g++ -c Bootstrap.cpp
+</plain-text-body></structured-macro></li></ul>
<ul><li>Link Bootstrap with the Java code
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> gcj -o Bootstrap Bootstrap.o -L /opt/app -lgcj -lstdc++ activeio-1.1.jar.so activemq-core-3.2.jar.so
+<structured-macro ac:macro-id="0f038e48-ac55-469e-8193-0f587d4e46bc" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ gcj -o Bootstrap Bootstrap.o -L /opt/app -lgcj -lstdc++ activeio-1.1.jar.so activemq-core-3.2.jar.so
commons-logging-1.0.3.jar.so concurrent-1.3.4.jar.so geronimo-spec-jms-1.1-rc4.jar.so
geronimo-spec-j2ee-management-1.0-rc4.jar.so geronimo-spec-j2ee-jacc-1.0-rc4.jar.so
geronimo-spec-jta-1.0.1B-rc4.jar.so log4j-1.2.8.jar.so MQAdapter.so
-</pre>
-</div></div></li></ul>
+</plain-text-body></structured-macro></li></ul>
<p>Now, if everything went ok you should be able to run the app. with ./Bootstrap.</p>
-<h4 id="CompileActiveMQwithGCJ-References">References</h4>
+<h4>References</h4>
-<p><a shape="rect" class="external-link" href="http://gcc.gnu.org/wiki/How%20to%20BC%20compile%20with%20GCJ" rel="nofollow">How to BC compile with GCJ</a></p>
+<p><a shape="rect" href="http://gcc.gnu.org/wiki/How%20to%20BC%20compile%20with%20GCJ">How to BC compile with GCJ</a></p>
-<p><a shape="rect" class="external-link" href="http://www.redhat.com/magazine/012oct05/features/java/" rel="nofollow">The state of Java on Linux</a></p></div>
+<p><a shape="rect" href="http://www.redhat.com/magazine/012oct05/features/java/">The state of Java on Linux</a></p></div>
diff --git a/complex-single-broker-configuration-stomp-only.xml b/complex-single-broker-configuration-stomp-only.xml
index 0586bab..a690a3b 100644
--- a/complex-single-broker-configuration-stomp-only.xml
+++ b/complex-single-broker-configuration-stomp-only.xml
@@ -3,8 +3,7 @@
<p>While this is a fairly detailed configuration, it locks down every ActiveMQ service. It would be ideal if ActiveMQ shipped with a default closed configuration like this.</p>
<p>ActiveMQ is assumed to be installed in /usr/local/activemq/ in this example.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="55aa3dea-f2f2-432e-8402-ecd4d24e69fd" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<!--
ActiveMQ activemq.xml configuration file (/usr/local/activemq/conf/activemq.xml)
@@ -13,8 +12,8 @@
* Uses the Sun JMX connector for remote management. Point jconsole at:
service:jmx:rmi:///jndi/rmi://myserver.domain.net:61616/jmxrmi
- * Uses Kaha persistence storage, stored in the "activemq-data" directory.
- "activemq-data" and "logs" sub-directories must be writable by the
+ * Uses Kaha persistence storage, stored in the "activemq-data" directory.
+ "activemq-data" and "logs" sub-directories must be writable by the
ActiveMQ user.
* Also see conf/log4j.properties for logging configuration
@@ -22,47 +21,47 @@
<beans>
<!-- Enables system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker xmlns="http://activemq.org/config/1.0" brokerName="SERVER1"
- populateJMSXUserID="true" useJmx="true" persistent="true">
+ <broker xmlns="http://activemq.org/config/1.0" brokerName="SERVER1"
+ populateJMSXUserID="true" useJmx="true" persistent="true">
<!-- Queue setup. Queues can be created on the fly by any user with
admin rights, but it is not good to give every user admin rights. -->
<destinations>
- <queue physicalName="widgets" />
- <queue physicalName="spacecontrol" />
- <queue physicalName="displays" />
+ <queue physicalName="widgets" />
+ <queue physicalName="spacecontrol" />
+ <queue physicalName="displays" />
</destinations>
<!-- We only allow Stomp clients -->
<transportConnectors>
- <transportConnector name="stomp" uri="stomp://localhost:61613"/>
+ <transportConnector name="stomp" uri="stomp://localhost:61613"/>
</transportConnectors>
- <!-- We don't have any other brokers to connect to -->
+ <!-- We don't have any other brokers to connect to -->
<networkConnectors>
</networkConnectors>
<!-- Do not create an ActiveMQ JMX connector. Use the Sun JMX connector
instead, and hook ActiveMQ to it. -->
<managementContext>
- <managementContext createConnector="false" />
+ <managementContext createConnector="false" />
</managementContext>
<plugins>
<simpleAuthenticationPlugin>
<users>
- <authenticationUser username="sa" password="manager" groups="producers,consumers,admins" />
- <authenticationUser username="frontend" password="manager" groups="producers,consumers" />
- <authenticationUser username="backend" password="manager" groups="consumers" />
+ <authenticationUser username="sa" password="manager" groups="producers,consumers,admins" />
+ <authenticationUser username="frontend" password="manager" groups="producers,consumers" />
+ <authenticationUser username="backend" password="manager" groups="consumers" />
</users>
</simpleAuthenticationPlugin>
<authorizationPlugin>
<map>
<authorizationMap>
<authorizationEntries>
- <authorizationEntry queue=">" write="producers" read="consumers" admin="admins" />
+ <authorizationEntry queue=">" write="producers" read="consumers" admin="admins" />
</authorizationEntries>
</authorizationMap>
</map>
@@ -73,7 +72,7 @@
<!-- Do not create ActiveMQ.Agent topic, as it does not work if
destination security is enabled -->
- <!-- <commandAgent xmlns="http://activemq.org/config/1.0"/> -->
+ <!-- <commandAgent xmlns="http://activemq.org/config/1.0"/> -->
<!-- Web Console. Auth is via JAAS. Beware: jetty-plus-6.1.4.jar contains the
JAAS classes, and is not included with ActiveMQ. You need to download
@@ -81,27 +80,25 @@
to browse the queue, and that requires a password.
-->
- <jetty xmlns="http://mortbay.com/schemas/jetty/1.0">
+ <jetty xmlns="http://mortbay.com/schemas/jetty/1.0">
<connectors>
- <nioConnector port="8161" />
+ <nioConnector port="8161" />
</connectors>
<userRealms>
- <!-- "name" must match the realm in web.xml, and "loginModuleName" must be defined in login.conf -->
- <jaasUserRealm name="ActiveMQ" loginModuleName="ActiveMQ"
- callbackHandlerClass="org.mortbay.jetty.plus.jaas.callback.DefaultCallbackHandler" />
+ <!-- "name" must match the realm in web.xml, and "loginModuleName" must be defined in login.conf -->
+ <jaasUserRealm name="ActiveMQ" loginModuleName="ActiveMQ"
+ callbackHandlerClass="org.mortbay.jetty.plus.jaas.callback.DefaultCallbackHandler" />
</userRealms>
<handlers>
- <webAppContext contextPath="/admin" resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true" />
+ <webAppContext contextPath="/admin" resourceBase="${activemq.base}/webapps/admin" logUrlOnStart="true" />
</handlers>
</jetty>
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Add this XML snippet to the web.xml for the /admin/ app, in order to enable HTTP Authentication to match the activemq.xml configuration above.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="205793d6-8b74-4d5b-a880-25b0c46d7ebe" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<security-constraint>
<web-resource-collection>
<web-resource-name>Web Console</web-resource-name>
@@ -116,6 +113,5 @@
<auth-method>BASIC</auth-method>
<realm-name>ActiveMQ</realm-name>
</login-config>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/composite-destinations.xml b/composite-destinations.xml
index 88524f7..bd18796 100644
--- a/composite-destinations.xml
+++ b/composite-destinations.xml
@@ -6,31 +6,26 @@
<p>We do this using a simple separator of "," allowing a number of destinations to be specified when creating a destintation, or registering destinations in JNDI. e.g. the destination</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6277290e-e1c1-41c9-8626-0903661ac49b" ac:name="code" ac:schema-version="1"><plain-text-body>
FOO.A,FOO.B,FOO.C
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Represents 3 different destinations. This could be used with a queue or topic to represent a set of 3 destinations. e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="40832b73-bda0-4200-b10c-cd1aa311a70d" ac:name="code" ac:schema-version="1"><plain-text-body>
// send to 3 queues as one logical operation
-Queue queue = new ActiveMQQueue("FOO.A,FOO.B,FOO.C");
+Queue queue = new ActiveMQQueue("FOO.A,FOO.B,FOO.C");
producer.send(queue, someMessage);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>If you wish to mix and match the types of destination, you can use a prefix of <strong>queue://</strong> or <strong>topic://</strong> to differentiate the type of destination. e.g. to publish on a queue but also make a notification on a topic as well you could use</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ae96f102-2093-47a3-8507-ed585b7c2636" ac:name="code" ac:schema-version="1"><plain-text-body>
// send to queues and topic one logical operation
-Queue queue = new ActiveMQQueue("FOO.A,topic://NOTIFY.FOO.A");
+Queue queue = new ActiveMQQueue("FOO.A,topic://NOTIFY.FOO.A");
producer.send(queue, someMessage);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>Composite destinations can also be configured on the <a shape="rect" href="virtual-destinations.xml#VirtualDestinations-CompositeDestinations">broker side</a>, such that messages sent to a single destination by the client will be transparently copied to multiple physical destinations.</p></div>
+<p>Composite destinations can also be configured on the <link ac:anchor="Composite Destinations"><page ri:content-title="Virtual Destinations"></page><link-body>broker side</link-body></link>, such that messages sent to a single destination by the client will be transparently copied to multiple physical destinations.</p>
+</div>
diff --git a/configurable-ioexception-handling.xml b/configurable-ioexception-handling.xml
index 259577a..fda6c6c 100644
--- a/configurable-ioexception-handling.xml
+++ b/configurable-ioexception-handling.xml
@@ -1,20 +1,16 @@
-<div class="wiki-content maincontent"><p>Starting with 5.3.1, ActiveMQ provides configurable IOException handling for its file-based message stores. From version 5.5 the handler is also invoked when the JDBC persistence adapter gets a failure on <code>getConnection()</code>.</p><h2 id="ConfigurableIOExceptionHandling-DefaultIOExceptionhandler">Default IOException handler</h2><p>ActiveMQ comes with a default IOException handler, which does the following. When some of the file-based message stores encounter IOException it can be one of the two things: either the disk is unavailable of there's no more space on the disk.</p><p>The first case is usually encountered when disk fails or network disk is disconnected. These errors are not "recoverable" and we usually want to shutdown the broker until problems with the disk are solved.</p><p>When there's no more space on the disk, we usually want to wait that some space is reclaimed and continue what we have been doing before (exchanging messages). All file-based persistent stores are capable of surviving these kind of errors.</p><h3 id="ConfigurableIOExceptionHandling-ConfiguringDefaultIOExceptionhandler">Configuring Default IOException handler</h3><p>There are a couple of properties you can use to tune the behavior of the <code>DefaultIOExceptionHandler</code>. First, instantiate the exception handler as a bean. Then configure the broker to use the exception handler by setting the broker's <code>ioExceptionHandler</code> property.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <bean id="ioExceptionHandler" class="org.apache.activemq.util.DefaultIOExceptionHandler">
- <property name="ignoreAllErrors"><value>true</value></property>
+<div class="wiki-content maincontent"><p>Starting with 5.3.1, ActiveMQ provides configurable IOException handling for its file-based message stores. From version 5.5 the handler is also invoked when the JDBC persistence adapter gets a failure on <code>getConnection()</code>.</p><h2>Default IOException handler</h2><p>ActiveMQ comes with a default IOException handler, which does the following. When some of the file-based message stores encounter IOException it can be one of the two things: either the disk is unavailable of there's no more space on the disk.</p><p>The first case is usually encountered when disk fails or network disk is disconnected. These errors are not "recoverable" and we usually want to shutdown the broker until problems with the disk are solved.</p><p>When there's no more space on the disk, we usually want to wait that some space is reclaimed and continue what we have been doing before (exchanging messages). All file-based persistent stores are capable of surviving these kind of errors.</p><h3>Configuring Default IOException handler</h3><p>There are a couple of properties you can use to tune the behavior of the <code>DefaultIOExceptionHandler</code>. First, instantiate the exception handler as a bean. Then configure the broker to use the exception handler by setting the broker's <code>ioExceptionHandler</code> property.</p><p>Example:</p><structured-macro ac:macro-id="225b34f9-76e5-47c3-8046-3b66e7ace910" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body> <bean id="ioExceptionHandler" class="org.apache.activemq.util.DefaultIOExceptionHandler">
+ <property name="ignoreAllErrors"><value>true</value></property>
</bean>
- <broker xmlns="http://activemq.apache.org/schema/core" ioExceptionHandler="#ioExceptionHandler">
+ <broker xmlns="http://activemq.apache.org/schema/core" ioExceptionHandler="#ioExceptionHandler">
...
</broker>
-]]></script>
-</div></div><p>Handler configuration properties:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property</p></th><th colspan="1" rowspan="1" class="confluenceTh">Since</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><code>ignoreAllErrors</code></p></td><td colspan="1" rowspan="1" class="confluenceTd">5.4</td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <code>true</code> all errors are ignored and the broker remains running.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ignoreNoSpaceErrors</code></p></td><td colspan="1" rowspan="1" class="confluenceTd">5.4</td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <code>false</code> 'no disk space' errors are treated the same as other errors causing the broker to be stopped.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>noSpaceMessage</code></p></td><td colspan="1" rowspan="1" class="confluenceTd">5.4</td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>space</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The string used to match against the exception's message. When matched a 'no disk space' error results.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);"><code>ignoreSQLExceptions</code></span></p></td><td colspan="1" rowspan="1" class="confluenceTd">5.5</td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <code>true</code> all SQLExceptions are ignored by the handler allowing them to be handled by the persistence adapter's locker. When <code>false</code> the exception handler processes the exception.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);"><code>sqlExceptionMessage</code></span></p></td><td colspan="1" rowspan="1" class="confluenceTd">5.5</td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>""</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The SQLException phrase to match when ignoring SQLExceptions. Only matched exceptions are ignored. All SQLExceptions match the default empty string.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);"><code>stopStartConnectors</code></span></p></td><td colspan="1" rowspan="1" class="confluenceTd">5.5</td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <code>true</code> transport connectors are stopped (client connections are refused), however, the broker will remain running. The transport connectors will be restarted following a successful persistence adapter checkpoint. All exceptions are ignored whilst the transport connectors are stopped. This option ensures that the broker does not need to be manually restarted in the event of a DB restart, for example.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);"><code>resumeCheckSleepPeriod</code></span></p></td><td colspan="1" rowspan="1" class="confluenceTd">5.5</td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5sec</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The interval between persistence adapter checkpoints. Typically used in conjunction with <code>stopStartConnectors</code>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);">systemExitOnShutdown</span></p></td><td colspan="1" rowspan="1" class="confluenceTd">5.13</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd"><span style="color: rgb(0,0,0);">before stopping the broker, set the broker attribute <span style="line-height: 1.42857;">systemExitOnShutdown to this value to potentially force a jvm exit. </span></span></td></tr></tbody></table></div><p><span style="color: rgb(0,0,0);">The default configuration will try to find a specified string in the exception message to determine whether it is a 'no disk space' error. On most platforms (at least those we have tested), you'll find the word 'space' in it. Of course, you can customize this to your platform by using <code style="line-height: 1.42857;">noSpaceMessage</code> property.</span></p><p>Note: as of ActiveMQ 5.11 the <code>JDBCIOExceptionHandler</code> has been deprecated. It has been replaced by the <code>org.apache.activemq.util.LeaseLockerIOExceptionHandler</code> that will work with any persistence adapter that supports pluggable storage lockers whether or not a locker is in use.</p><p><span style="color: rgb(102,0,51);">Writing your own handler</span></p><p>In case this handler doesn't work for you, you can write your own. For example you might want to change the way how you detect full disk and execute some external command, like <code>df</code> on Linux to be sure.</p><p>All you have to do is implement the <code>org.apache.activemq.util.IOExceptionHandler</code> interface then configure the broker to use it:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <bean id="ioExceptionHandler" class="com.mycompany.MyIOExceptionHandler">
- <property name="ignoreAllErrors"><value>true</value></property>
+</plain-text-body></structured-macro><p>Handler configuration properties:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Property</p></th><th colspan="1" rowspan="1">Since</th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>ignoreAllErrors</code></p></td><td colspan="1" rowspan="1">5.4</td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>When <code>true</code> all errors are ignored and the broker remains running.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ignoreNoSpaceErrors</code></p></td><td colspan="1" rowspan="1">5.4</td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>When <code>false</code> 'no disk space' errors are treated the same as other errors causing the broker to be stopped.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>noSpaceMessage</code></p></td><td colspan="1" rowspan="1">5.4</td><td colspan="1" rowspan="1"><p><code>space</code></p></td><td colspan="1" rowspan="1"><p>The string used to match against the exception's message. When matched a 'no disk space' error results.</p></td></tr><tr><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);"><code>ignoreSQLExceptions</code></span></p></td><td colspan="1" rowspan="1">5.5</td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>If <code>true</code> all SQLExceptions are ignored by the handler allowing them to be handled by the persistence adapter's locker. When <code>false</code> the exception handler processes the exception.</p></td></tr><tr><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);"><code>sqlExceptionMessage</code></span></p></td><td colspan="1" rowspan="1">5.5</td><td colspan="1" rowspan="1"><p><code>""</code></p></td><td colspan="1" rowspan="1"><p>The SQLException phrase to match when ignoring SQLExceptions. Only matched exceptions are ignored. All SQLExceptions match the default empty string.</p></td></tr><tr><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);"><code>stopStartConnectors</code></span></p></td><td colspan="1" rowspan="1">5.5</td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>When <code>true</code> transport connectors are stopped (client connections are refused), however, the broker will remain running. The transport connectors will be restarted following a successful persistence adapter checkpoint. All exceptions are ignored whilst the transport connectors are stopped. This option ensures that the broker does not need to be manually restarted in the event of a DB restart, for example.</p></td></tr><tr><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);"><code>resumeCheckSleepPeriod</code></span></p></td><td colspan="1" rowspan="1">5.5</td><td colspan="1" rowspan="1"><p><code>5sec</code></p></td><td colspan="1" rowspan="1"><p>The interval between persistence adapter checkpoints. Typically used in conjunction with <code>stopStartConnectors</code>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);">systemExitOnShutdown</span></p></td><td colspan="1" rowspan="1">5.13</td><td colspan="1" rowspan="1">false</td><td colspan="1" rowspan="1"><span style="color: rgb(0,0,0);">before stopping the broker, set the broker attribute <span style="line-height: 1.42857;">systemExitOnShutdown to this value to potentially force a jvm exit. </span></span></td></tr></tbody></table><p><span style="color: rgb(0,0,0);">The default configuration will try to find a specified string in the exception message to determine whether it is a 'no disk space' error. On most platforms (at least those we have tested), you'll find the word 'space' in it. Of course, you can customize this to your platform by using <code style="line-height: 1.42857;">noSpaceMessage</code> property.</span></p><p>Note: as of ActiveMQ 5.11 the <code>JDBCIOExceptionHandler</code> has been deprecated. It has been replaced by the <code>org.apache.activemq.util.LeaseLockerIOExceptionHandler</code> that will work with any persistence adapter that supports pluggable storage lockers whether or not a locker is in use.</p><p><span style="color: rgb(102,0,51);">Writing your own handler</span></p><p>In case this handler doesn't work for you, you can write your own. For example you might want to change the way how you detect full disk and execute some external command, like <code>df</code> on Linux to be sure.</p><p>All you have to do is implement the <code>org.apache.activemq.util.IOExceptionHandler</code> interface then configure the broker to use it:</p><structured-macro ac:macro-id="dc77904e-f88b-45af-a7ba-f3356f7f0c7c" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body> <bean id="ioExceptionHandler" class="com.mycompany.MyIOExceptionHandler">
+ <property name="ignoreAllErrors"><value>true</value></property>
</bean>
- <broker xmlns="http://activemq.apache.org/schema/core" ioExceptionHandler="#ioExceptionHandler">
+ <broker xmlns="http://activemq.apache.org/schema/core" ioExceptionHandler="#ioExceptionHandler">
...
</broker>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/configuration.xml b/configuration.xml
index eb26111..4fe0acb 100644
--- a/configuration.xml
+++ b/configuration.xml
@@ -3,5 +3,5 @@
<p>Questions on configuring ActiveMQ's JMS client or the Message Broker</p>
-<ul class="childpages-macro"><li><a shape="rect" href="how-can-i-enable-detailed-logging.xml">How can I enable detailed logging</a></li><li><a shape="rect" href="how-does-xbean-compare-to-spring-2.xml">How does XBean compare to Spring 2</a></li><li><a shape="rect" href="how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker.xml">How do I configure 10s of 1000s of Queues in a single broker</a></li><li><a shape="rect" href="how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages.xml">How do I configure ActiveMQ to hold 100s of millions of Queue Messages</a></li><li><a shape="rect" href="how-do-i-configure-activemq-to-use-aio-server-transport.xml">How do I configure ActiveMQ to use AIO server transport</a></li><li><a shape="rect" href="how-do-i-configure-automatic-reconnection.xml">How do I configure automatic reconnection</a></li><li><a shape="rect" href="how-do-i-configure-distributed-queues-or-topics.xml">How do I configure distributed queues or topics</a></li><li><a shape="rect" href="how-do-i-configure-the-queues-i-want.xml">How do I configure the queues I want</a></li><li><a shape="rect" href="how-do-i-define-a-local-address-and-local-port-for-tcp-or-ssl.xml">How do I define a local address and local port for TCP or SSL</a></li><li><a shape="rect" href="how-do-i-disable-persistence.xml">How do I disable persistence</a></li><li><a shape="rect" href="how-do-i-run-activemq-under-the-kaffe-jvm.xml">How do I run ActiveMQ under the Kaffe JVM</a></li><li><a shape="rect" href="how-to-configure-a-new-database.xml">How to configure a new database</a></li><li><a shape="rect" href="how-to-deploy-activemq-ra-versionrar-to-weblogic.xml">How to deploy activemq-ra-version.rar to weblogic</a></li><li><a shape="rect" href="how-to-disable-multicast-discovery.xml">How to disable multicast discovery</a></li></ul></div>
+<structured-macro ac:macro-id="4be0647a-0a3a-460c-b754-4e9757b58610" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/configure-startup-destinations.xml b/configure-startup-destinations.xml
index dcd4263..de224c8 100644
--- a/configure-startup-destinations.xml
+++ b/configure-startup-destinations.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>Typically in Apache ActiveMQ we <a shape="rect" href="how-do-i-create-new-destinations.xml">create destinations on demand</a> as clients start to use them. However sometimes users want to be able to configure which destinations are available on startup explicitly in the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>.</p><parameter ac:name="title">4.1 Feature</parameter><rich-text-body><p>Note this feature is available from 4.1 onwards. If you try this XML on older versions of ActiveMQ you will get an exception about the 'destinations' property not being writable.</p></rich-text-body><h3 id="ConfigureStartupDestinations-Example">Example</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/broker/destinations-on-start.xml">example</a> shows how you can configure a number of destinations to be available at startup.<plain-text-body>
+<div class="wiki-content maincontent"><p>Typically in Apache ActiveMQ we <link><page ri:content-title="How do I create new destinations"></page><plain-text-link-body>create destinations on demand</plain-text-link-body></link> as clients start to use them. However sometimes users want to be able to configure which destinations are available on startup explicitly in the <link><page ri:content-title="Xml Configuration"></page></link>.</p><parameter ac:name="title">4.1 Feature</parameter><rich-text-body><p>Note this feature is available from 4.1 onwards. If you try this XML on older versions of ActiveMQ you will get an exception about the 'destinations' property not being writable.</p></rich-text-body><h3>Example</h3><p>The following <a shape="rect" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/broker/destinations-on-start.xml">example</a> shows how you can configure a number of destinations to be available at startup.<plain-text-body>
<broker xmlns="http://activemq.apache.org/schema/core">
<destinations>
diff --git a/configure-version-5-brokers.xml b/configure-version-5-brokers.xml
index 2db2822..39437a9 100644
--- a/configure-version-5-brokers.xml
+++ b/configure-version-5-brokers.xml
@@ -1,28 +1,27 @@
-<div class="wiki-content maincontent"><h3 id="Configureversion5Brokers-Overview">Overview</h3><p>There is an updates XML syntax for configuring message brokers - <a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.0-SNAPSHOT.xsd">see here</a></p><p>So we decided that using XML would make this configuration much easier. we use <a shape="rect" class="external-link" href="http://xbean.org/" rel="nofollow">XBean</a> to perform the XML configuration.</p><p>For details of the XML see the <a shape="rect" href="xml-reference.xml">Xml Reference</a></p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Be careful with broker names and URIs</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Make sure you do not use any strange characters in the names of brokers as they are converted to URIs which <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html" rel="nofollow">do not allow things like underscores</a> in them etc.</p></div></div><h2 id="Configureversion5Brokers-Examples">Examples</h2><p>The default ActiveMQ configuration: <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">current default config</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans
- xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
+<div class="wiki-content maincontent"><h3>Overview</h3><p>There is an updates XML syntax for configuring message brokers - <a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.0-SNAPSHOT.xsd">see here</a></p><p>So we decided that using XML would make this configuration much easier. we use <a shape="rect" href="http://xbean.org/">XBean</a> to perform the XML configuration.</p><p>For details of the XML see the <link><page ri:content-title="Xml Reference"></page></link></p><structured-macro ac:macro-id="8bc30f12-46ab-4d0b-b5a7-c915427e4b4b" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Be careful with broker names and URIs</parameter><rich-text-body><p>Make sure you do not use any strange characters in the names of brokers as they are converted to URIs which <a shape="rect" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html">do not allow things like underscores</a> in them etc.</p></rich-text-body></structured-macro><h2>Examples</h2><p>The default ActiveMQ configuration: <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">current default config</a>.</p><structured-macro ac:macro-id="79ddd82e-0753-4eaf-87e4-2f3d0904296c" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><beans
+ xmlns="http://www.springframework.org/schema/beans"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
+ http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
- <property name="locations">
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
+ <property name="locations">
<value>file:${activemq.conf}/credentials.properties</value>
</property>
</bean>
<!-- Allows accessing the server log -->
- <bean id="logQuery" class="io.fabric8.insight.log.log4j.Log4jLogQuery"
- lazy-init="false" scope="singleton"
- init-method="start" destroy-method="stop">
+ <bean id="logQuery" class="io.fabric8.insight.log.log4j.Log4jLogQuery"
+ lazy-init="false" scope="singleton"
+ init-method="start" destroy-method="stop">
</bean>
<!--
The <broker> element is used to configure the ActiveMQ broker.
-->
- <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}">
+ <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}">
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry topic=">" >
+ <policyEntry topic=">" >
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
@@ -30,7 +29,7 @@
http://activemq.apache.org/slow-consumer-handling.html
-->
<pendingMessageLimitStrategy>
- <constantPendingMessageLimitStrategy limit="1000"/>
+ <constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>
</policyEntries>
@@ -44,7 +43,7 @@
http://activemq.apache.org/jmx.html
-->
<managementContext>
- <managementContext createConnector="false"/>
+ <managementContext createConnector="false"/>
</managementContext>
<!--
Configure message persistence for the broker. The default persistence
@@ -53,7 +52,7 @@
http://activemq.apache.org/persistence.html
-->
<persistenceAdapter>
- <kahaDB directory="${activemq.data}/kahadb"/>
+ <kahaDB directory="${activemq.data}/kahadb"/>
</persistenceAdapter>
<!--
@@ -64,13 +63,13 @@
<systemUsage>
<systemUsage>
<memoryUsage>
- <memoryUsage percentOfJvmHeap="70" />
+ <memoryUsage percentOfJvmHeap="70" />
</memoryUsage>
<storeUsage>
- <storeUsage limit="100 gb"/>
+ <storeUsage limit="100 gb"/>
</storeUsage>
<tempUsage>
- <tempUsage limit="50 gb"/>
+ <tempUsage limit="50 gb"/>
</tempUsage>
</systemUsage>
</systemUsage>
@@ -81,15 +80,15 @@
-->
<transportConnectors>
<!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
- <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
- <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
- <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
- <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
- <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
+ <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
+ <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
+ <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
+ <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
+ <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
</transportConnectors>
<!-- destroy the spring context on shutdown to stop jetty -->
<shutdownHooks>
- <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
+ <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
</shutdownHooks>
</broker>
<!--
@@ -97,9 +96,8 @@
The web consoles requires by default login, you can disable this in the jetty.xml file
Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
-->
- <import resource="jetty.xml"/>
+ <import resource="jetty.xml"/>
</beans>
-]]></script>
-</div></div><p>From the binary distributionthere is an <em>activemq</em> script allowing you to run a Message Broker as a stand alone process from the command line easily providing the $ACTIVEMQ_HOME/bin directory is on your PATH.</p></div>
+</plain-text-body></structured-macro><p>From the binary distributionthere is an <em>activemq</em> script allowing you to run a Message Broker as a stand alone process from the command line easily providing the $ACTIVEMQ_HOME/bin directory is on your PATH.</p></div>
diff --git a/configuring-activemq-cpp.xml b/configuring-activemq-cpp.xml
index 5c4127b..8d4cf8b 100644
--- a/configuring-activemq-cpp.xml
+++ b/configuring-activemq-cpp.xml
@@ -1,49 +1,46 @@
<div class="wiki-content maincontent"><p>The configuration of ActiveMQ is so slick, we decided to take a similar approach with ActiveMQ-CPP. All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every facet of your ActiveMQ-CPP client. The tables below show the comprehensive set of parameters.</p>
-<h2 id="ConfiguringActiveMQCPP-ConnectionURIParameters"><strong>Connection URI Parameters</strong></h2>
+<h2><strong>Connection URI Parameters</strong></h2>
-<h4 id="ConfiguringActiveMQCPP-ExampleConfiguration">Example Configuration</h4>
+<h4>Example Configuration</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f8ac92f6-d75e-4a5f-8c13-6ae42fd8a7c3" ac:name="code" ac:schema-version="1"><plain-text-body>
cf = new ActiveMQConnectionFactory(
- "tcp://localhost:61616?wireFormat=openwire&wireFormat.tightEncodingEnabled=true");
-]]></script>
-</div></div>
+ "tcp://localhost:61616?wireFormat=openwire&wireFormat.tightEncodingEnabled=true");
+</plain-text-body></structured-macro>
-<h3 id="ConfiguringActiveMQCPP-SocketOptions"><strong>Socket Options</strong></h3>
-<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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>inputBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of bytes in the buffered input stream's buffer</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outputBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of bytes in the buffered output stream's buffer</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>soLinger</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Socket SOLinger value</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>soKeepAlive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Socket SOKeepAlive value</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>soReceiveBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Socket receive buffer. If -1, use OS default.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>soSendBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Socket send buffer. If -1, use OS default.</p></td></tr></tbody></table></div>
+<h3><strong>Socket Options</strong></h3>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>inputBufferSize</p></td><td colspan="1" rowspan="1"><p>10000</p></td><td colspan="1" rowspan="1"><p>The number of bytes in the buffered input stream's buffer</p></td></tr><tr><td colspan="1" rowspan="1"><p>outputBufferSize</p></td><td colspan="1" rowspan="1"><p>10000</p></td><td colspan="1" rowspan="1"><p>The number of bytes in the buffered output stream's buffer</p></td></tr><tr><td colspan="1" rowspan="1"><p>soLinger</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Socket SOLinger value</p></td></tr><tr><td colspan="1" rowspan="1"><p>soKeepAlive</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Socket SOKeepAlive value</p></td></tr><tr><td colspan="1" rowspan="1"><p>soReceiveBufferSize</p></td><td colspan="1" rowspan="1"><p>-1</p></td><td colspan="1" rowspan="1"><p>Socket receive buffer. If -1, use OS default.</p></td></tr><tr><td colspan="1" rowspan="1"><p>soSendBufferSize</p></td><td colspan="1" rowspan="1"><p>-1</p></td><td colspan="1" rowspan="1"><p>Socket send buffer. If -1, use OS default.</p></td></tr></tbody></table>
-<h3 id="ConfiguringActiveMQCPP-TransportOptions"><strong>Transport Options</strong></h3>
-<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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>commandTracingEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, enables tracing of incoming and outgoing transport commands</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>tcpTracingEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, enables tracing of raw network IO (in hex)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useAsyncSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, enables asynchronous sending of messages.</p></td></tr></tbody></table></div>
+<h3><strong>Transport Options</strong></h3>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>commandTracingEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, enables tracing of incoming and outgoing transport commands</p></td></tr><tr><td colspan="1" rowspan="1"><p>tcpTracingEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, enables tracing of raw network IO (in hex)</p></td></tr><tr><td colspan="1" rowspan="1"><p>useAsyncSend</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, enables asynchronous sending of messages.</p></td></tr></tbody></table>
-<h3 id="ConfiguringActiveMQCPP-TransactionOptions"><strong>Transaction Options</strong></h3>
-<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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transaction.maxRedeliveryCount</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>5</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Maximum number of redelivery attempts.</p></td></tr></tbody></table></div>
+<h3><strong>Transaction Options</strong></h3>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>transaction.maxRedeliveryCount</p></td><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>Maximum number of redelivery attempts.</p></td></tr></tbody></table>
-<h3 id="ConfiguringActiveMQCPP-WireFormatProtocolOptions"><strong>Wire Format Protocol Options</strong></h3>
-<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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>openwire</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Selects the wire format to use. Out of the box, can be either stomp or openwire.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.stackTraceEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the stack trace of exception that occur on the broker be sent to the client? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.cacheEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should commonly repeated values be cached so that less marshalling occurs? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.tcpNoDelayEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Does not affect the wire format, but provides a hint to the peer that TCP nodelay should be enabled on the communications Socket. Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.sizePrefixDisabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should serialized messages include a payload length prefix? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.tightEncodingEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should wire size be optimized over CPU usage? Only used by the openwire protocol.</p></td></tr></tbody></table></div>
+<h3><strong>Wire Format Protocol Options</strong></h3>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>wireFormat</p></td><td colspan="1" rowspan="1"><p>openwire</p></td><td colspan="1" rowspan="1"><p>Selects the wire format to use. Out of the box, can be either stomp or openwire.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.stackTraceEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should the stack trace of exception that occur on the broker be sent to the client? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.cacheEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should commonly repeated values be cached so that less marshalling occurs? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.tcpNoDelayEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Does not affect the wire format, but provides a hint to the peer that TCP nodelay should be enabled on the communications Socket. Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.sizePrefixDisabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should serialized messages include a payload length prefix? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.tightEncodingEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should wire size be optimized over CPU usage? Only used by the openwire protocol.</p></td></tr></tbody></table>
-<h2 id="ConfiguringActiveMQCPP-DestinationURIParameters"><strong>Destination URI Parameters</strong></h2>
+<h2><strong>Destination URI Parameters</strong></h2>
-<h4 id="ConfiguringActiveMQCPP-ExampleConfiguration.1">Example Configuration</h4>
+<h4>Example Configuration</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-d = session->createTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="60e75886-3975-4e30-af58-247e9b0a740f" ac:name="code" ac:schema-version="1"><plain-text-body>
+d = session->createTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
+</plain-text-body></structured-macro>
-<h3 id="ConfiguringActiveMQCPP-GeneralOptions"><strong>General Options</strong></h3>
-<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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.prefetchSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The number of message the consumer will <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.maximumPendingMessageLimit</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use to control if messages are dropped if a <a shape="rect" href="slow-consumer-handling.xml">slow consumer</a> situation exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.noLocal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the broker <a shape="rect" href="consumer-dispatch-async.xml">dispatch messages asynchronously</a> to the consumer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Is this a <a shape="rect" href="retroactive-consumer.xml">Retroactive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.selector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> JMS Selector used with the consumer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.exclusive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Is this an <a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.priority</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Allows you to configure a <a shape="rect" href="consumer-priority.xml">Consumer Priority</a>.</p></td></tr></tbody></table></div>
+<h3><strong>General Options</strong></h3>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>consumer.prefetchSize</p></td><td colspan="1" rowspan="1"><p> 1000 </p></td><td colspan="1" rowspan="1"><p> The number of message the consumer will <link><page ri:content-title="What is the Prefetch Limit For?"></page><link-body>prefetch</link-body></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.maximumPendingMessageLimit</p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Use to control if messages are dropped if a <link><page ri:content-title="Slow Consumer Handling"></page><link-body>slow consumer</link-body></link> situation exists.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.noLocal </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.dispatchAsync </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should the broker <link><page ri:content-title="Consumer Dispatch Async"></page><link-body>dispatch messages asynchronously</link-body></link> to the consumer.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1"><p> false</p></td><td colspan="1" rowspan="1"><p> Is this a <link><page ri:content-title="Retroactive Consumer"></page></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.selector</p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> JMS Selector used with the consumer.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.exclusive</p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Is this an <link><page ri:content-title="Exclusive Consumer"></page></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.priority</p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Allows you to configure a <link><page ri:content-title="Consumer Priority"></page></link>.</p></td></tr></tbody></table>
-<h3 id="ConfiguringActiveMQCPP-OpenWire-onlyOptions"><strong>OpenWire-only Options</strong></h3>
-<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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.browser</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.networkSubscription</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.optimizedAcknowledge</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Enables an optimised acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode for the consumers which can often be faster. <strong>WARNING</strong> enabling this issue could cause some issues with auto-acknowledgement on reconnection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.noRangeAcks</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>producer.dispatchAsyc</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr></tbody></table></div>
+<h3><strong>OpenWire-only Options</strong></h3>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>consumer.browser</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.networkSubscription</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.optimizedAcknowledge</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p> Enables an optimised acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode for the consumers which can often be faster. <strong>WARNING</strong> enabling this issue could cause some issues with auto-acknowledgement on reconnection</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.noRangeAcks</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started.</p></td></tr><tr><td colspan="1" rowspan="1"><p>producer.dispatchAsyc</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p> </p></td></tr></tbody></table>
+
</div>
diff --git a/configuring-brokers.xml b/configuring-brokers.xml
index 5744e7e..dc656cd 100644
--- a/configuring-brokers.xml
+++ b/configuring-brokers.xml
@@ -1,42 +1,40 @@
<div class="wiki-content maincontent">
-<h3 id="ConfiguringBrokers-Overview">Overview</h3>
+<h3>Overview</h3>
<p>In ActiveMQ 4, we are using a new xml format to configure the broker.</p>
-<h3 id="ConfiguringBrokers-Syntax">Syntax</h3>
+<h3>Syntax</h3>
<p>The following xsd describes the syntax of the broker configuration file.</p>
-<p><a shape="rect" href="configuring-brokers.data/activemq-4.0.xsd?version=1&modificationDate=1133701454000&api=v2" data-linked-resource-id="3253" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="activemq-4.0.xsd" data-linked-resource-content-type="application/octet-stream" data-linked-resource-container-id="36158" data-linked-resource-container-version="6">activemq-4.0.xsd</a></p>
+<p><link><attachment ri:filename="activemq-4.0.xsd"></attachment></link></p>
<p>And here is the reference documentation for that xsd file.</p>
-<p><a shape="rect" href="configuring-brokers.data/activemq-4.0.xsd.html?version=1&modificationDate=1133701442000&api=v2" data-linked-resource-id="3286" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="activemq-4.0.xsd.html" data-nice-type="HTML Document" data-linked-resource-content-type="text/html" data-linked-resource-container-id="36158" data-linked-resource-container-version="6">activemq-4.0.xsd.html</a></p>
+<p><link><attachment ri:filename="activemq-4.0.xsd.html"></attachment></link></p>
-<h3 id="ConfiguringBrokers-Example">Example</h3>
+<h3>Example</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<beans xmlns="http://activemq.org/config/1.0">
+<structured-macro ac:macro-id="678b9187-119f-47cf-ada5-eb85cee61646" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<beans xmlns="http://activemq.org/config/1.0">
- <broker useJmx="true">
+ <broker useJmx="true">
<persistenceAdapter>
- <journaledJDBC journalLogFiles="5" dataDirectory="../data"/>
+ <journaledJDBC journalLogFiles="5" dataDirectory="../data"/>
</persistenceAdapter>
<transportConnectors>
- <transportConnector uri="discovery:tcp://localhost:61616"/>
+ <transportConnector uri="discovery:tcp://localhost:61616"/>
</transportConnectors>
<networkConnectors>
- <networkConnector uri="multicast"/>
+ <networkConnector uri="multicast"/>
</networkConnectors>
</broker>
</beans>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/configuring-transports.xml b/configuring-transports.xml
index 3f9e271..07e83cb 100644
--- a/configuring-transports.xml
+++ b/configuring-transports.xml
@@ -1,30 +1,24 @@
-<div class="wiki-content maincontent"><h2 id="ConfiguringTransports-Transportconfigurationoptions">Transport configuration options</h2><p>One of the first kinds of URI you are likely to use is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All of the following URI configurations are based on the java.net.URI class which does not allow whitespace to be used. So if you are using <strong><code>failover:</code></strong> or <strong><code>static:</code></strong> URIs, do not put any whitespace around the <strong><code>','</code> </strong>symbol.</p></div></div><h3 id="ConfiguringTransports-TheAUTOTransport">The AUTO Transport</h3><p>Starting with 5.13.0 ActiveMQ has support for automatic wire protocol detection over TCP, SSL, NIO, and NIO SSL.  OpenWire, STOMP, AMQP, and MQTT are supported.  For details see the <a shape="rect" href="auto.xml">AUTO </a>Transport Reference.</p><h3 id="ConfiguringTransports-TheVMTransport">The VM Transport</h3><p>The VM transport allows clients to connect to each other inside the VM without the overhead of the network communication. The connection used is not that of a socket connection but instead uses direct method invocations to enable a high performance embedded messaging system.</p><p>The first client to use the VM connection will boot an embedded broker. Subsequent connections will attach that the same broker. Once all VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For more information see the <a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a></p><h3 id="ConfiguringTransports-TheAMQPTransport">The AMQP Transport</h3><p>As of 5.8.0 ActiveMQ has support for AMQP. For details see the <a shape="rect" href="amqp.xml">AMQP</a> Transport Reference.</p><h3 id="ConfiguringTransports-TheMQTTTransport">The MQTT Transport</h3><p>Starting with 5.6.0 ActiveMQ also supports <a shape="rect" class="external-link" href="http://mqtt.org/" rel="nofollow">MQTT</a>. Its a light weight publish/subscribe messaging transport. See the <a shape="rect" href="mqtt.xml">MQTT</a> Transport Reference for details.</p><h3 id="ConfiguringTransports-TheTCPTransport">The TCP Transport</h3><p>The TCP transport allows clients to connect a remote ActiveMQ using a a TCP socket.</p><p>For more information see the <a shape="rect" href="tcp-transport-reference.xml">TCP Transport Reference</a></p><h3 id="ConfiguringTransports-TheNIOTransport">The NIO Transport</h3><p>Same as the TCP transport, except that the <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/New_I/O" rel="nofollow">New I/O (NIO)</a> package is used, which may provide better performance. The Java NIO package should not be confused with IBM's <a shape="rect" class="external-link" href="http://java.sys-con.com/read/46658.htm" rel="nofollow">AIO4J </a> package.</p><p>To switch from TCP to NIO, simply change the scheme portion of the URI. Here's an example as defined within a broker's XML configuration file.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
+<div class="wiki-content maincontent"><h2>Transport configuration options</h2><p>One of the first kinds of URI you are likely to use is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are the first transports you'll use.</p><structured-macro ac:macro-id="0f5649b8-41ab-477a-8bd2-7060071af7bd" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Be careful about whitespace</parameter><rich-text-body><p>All of the following URI configurations are based on the java.net.URI class which does not allow whitespace to be used. So if you are using <strong><code>failover:</code></strong> or <strong><code>static:</code></strong> URIs, do not put any whitespace around the <strong><code>','</code> </strong>symbol.</p></rich-text-body></structured-macro><h3>The AUTO Transport</h3><p>Starting with 5.13.0 ActiveMQ has support for automatic wire protocol detection over TCP, SSL, NIO, and NIO SSL.  OpenWire, STOMP, AMQP, and MQTT are supported.  For details see the <link><page ri:content-title="AUTO"></page><plain-text-link-body>AUTO </plain-text-link-body></link>Transport Reference.</p><h3>The VM Transport</h3><p>The VM transport allows clients to connect to each other inside the VM without the overhead of the network communication. The connection used is not that of a socket connection but instead uses direct method invocations to enable a high performance embedded messaging system.</p><p>The first client to use the VM connection will boot an embedded broker. Subsequent connections will attach that the same broker. Once all VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For more information see the <link><page ri:content-title="VM Transport Reference"></page></link></p><h3>The AMQP Transport</h3><p>As of 5.8.0 ActiveMQ has support for AMQP. For details see the <link><page ri:content-title="AMQP"></page></link> Transport Reference.</p><h3>The MQTT Transport</h3><p>Starting with 5.6.0 ActiveMQ also supports <a shape="rect" href="http://mqtt.org/">MQTT</a>. Its a light weight publish/subscribe messaging transport. See the <link><page ri:content-title="MQTT"></page></link> Transport Reference for details.</p><h3>The TCP Transport</h3><p>The TCP transport allows clients to connect a remote ActiveMQ using a a TCP socket.</p><p>For more information see the <link><page ri:content-title="TCP Transport Reference"></page></link></p><h3>The NIO Transport</h3><p>Same as the TCP transport, except that the <a shape="rect" href="http://en.wikipedia.org/wiki/New_I/O">New I/O (NIO)</a> package is used, which may provide better performance. The Java NIO package should not be confused with IBM's <a shape="rect" href="http://java.sys-con.com/read/46658.htm">AIO4J </a> package.</p><p>To switch from TCP to NIO, simply change the scheme portion of the URI. Here's an example as defined within a broker's XML configuration file.</p><structured-macro ac:macro-id="b963ed56-8d6d-409a-baee-d4a2ad19b668" ac:name="code" ac:schema-version="1"><plain-text-body><broker>
...
<transportConnectors>
- <transportConnector name="nio" uri="nio://0.0.0.0:61616"/>
+ <transportConnector name="nio" uri="nio://0.0.0.0:61616"/>
</<transportConnectors>
...
</broker>
-]]></script>
-</div></div><p>Trying to use nio transport url on the client side will instantiate the regular TCP transport. For more information see the <a shape="rect" href="nio-transport-reference.xml">NIO Transport Reference</a></p><h3 id="ConfiguringTransports-TheSSLTransport">The SSL Transport</h3><p>This allows you to talk over TCP using SSL. For more information see the <a shape="rect" href="ssl-transport-reference.xml">SSL Transport Reference</a></p><h3 id="ConfiguringTransports-TheNIOSSLTransport">The NIO SSL Transport</h3><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Availability</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Available since 5.6</p></div></div><p>Implementing SSL transport over NIO. This allows you to connect large number of SSL clients to a single broker instance. It's server side transport-option only</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
+</plain-text-body></structured-macro><p>Trying to use nio transport url on the client side will instantiate the regular TCP transport. For more information see the <link><page ri:content-title="NIO Transport Reference"></page></link></p><h3>The SSL Transport</h3><p>This allows you to talk over TCP using SSL. For more information see the <link><page ri:content-title="SSL Transport Reference"></page></link></p><h3>The NIO SSL Transport</h3><structured-macro ac:macro-id="2aa11976-d3d9-4a7a-98ff-b7ea8fb7f1f3" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Availability</parameter><rich-text-body><p>Available since 5.6</p></rich-text-body></structured-macro><p>Implementing SSL transport over NIO. This allows you to connect large number of SSL clients to a single broker instance. It's server side transport-option only</p><structured-macro ac:macro-id="65251e10-4456-410d-8bc8-a74670275b2d" ac:name="code" ac:schema-version="1"><plain-text-body><broker>
...
<transportConnectors>
- <transportConnector name="nio+ssl" uri="nio+ssl://0.0.0.0:61616"/>
+ <transportConnector name="nio+ssl" uri="nio+ssl://0.0.0.0:61616"/>
</<transportConnectors>
...
</broker>
-]]></script>
-</div></div><p>Trying to use <code>nio+ssl</code> transport url on the client side will instantiate the regular SSL transport.</p><h3 id="ConfiguringTransports-ThePeerTransport">The Peer Transport</h3><p>The Peer transport provides a peer-to-peer network with ActiveMQ. What actually happens is the peer transport uses the VM transport to create and connect to a local embedded broker but which configures the embedded broker to establish network connections to other peer embedded brokers.</p><p>For more information see the <a shape="rect" href="peer-transport-reference.xml">Peer Transport Reference</a></p><h3 id="ConfiguringTransports-TheUDPTransport">The UDP Transport</h3><p>This allows you to talk over UDP.</p><p>For more information see the <a shape="rect" href="udp-transport-reference.xml">UDP Transport Reference</a></p><h3 id="ConfiguringTransports-TheMulticastTransport">The Multicast Transport</h3><p>This allows you to talk over Multicast.</p><p>For more information see the <a shape="rect" href="multicast-transport-reference.xml">Multicast Transport Reference</a></p><h3 id="ConfiguringTransports-TheHTTPandHTTPSTransport">The HTTP and HTTPS Transport</h3><p>This allows the ActiveMQ client and broker to tunnel over HTTP. If the client is not JMS you might want to look at <a shape="rect" href="rest.xml">REST</a> or <a shape="rect" href="ajax.xml">Ajax</a> support instead.</p><p>For more information see the <a shape="rect" href="http-and-https-transports-reference.xml">HTTP and HTTPs Transports Reference</a></p><h3 id="ConfiguringTransports-TheWebSocketsTransport">The WebSockets Transport</h3><p>This transport uses the new HTML5 WebSockets to exchange messages with the broker. For more information see the <a shape="rect" href="websockets.xml">WebSockets</a> Transport Reference</p><h3 id="ConfiguringTransports-TheStompTransport">The Stomp Transport</h3><p>A plain text transport that can be used with many languages. See <a shape="rect" href="stomp.xml">Stomp</a> for more details.</p><h2 id="ConfiguringTransports-GeneralPurposeURIs">General Purpose URIs</h2><p>You can configure other features via the URI syntax as follows...</p><h3 id="ConfiguringTransports-ConnectionConfigurationURI">Connection Configuration URI</h3><p>Any Apache ActiveMQ JMS connection can be configured using the URL or explicitly setting properties on the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a> or <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> objects themselves.</p><p>For more information see <a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a></p><h3 id="ConfiguringTransports-DestinationOptions">Destination Options</h3><p>You can configure various consumer related options using <a shape="rect" href="destination-options.xml">Destination Options</a> which allow you to configure destinations using URI syntax.</p><h3 id="ConfiguringTransports-BrokerConfigurationURI">Broker Configuration URI</h3><p>You can use a <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a> to configure an embedded broker, either using the BrokerFactory helper class from Java or using the activemq shell script. For more details see <a shape="rect" href="run-broker.xml">How to Run a Broker</a></p><h3 id="ConfiguringTransports-ConfiguringWireFormats">Configuring Wire Formats</h3><p>Any transport which involves marshalling messages onto some kind of network transport like TCP or UDP will typically use the <a shape="rect" href="openwire.xml">OpenWire</a> format. This is configurable to customize how things appear on the wire.</p><p>For more information see <a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a></p><h2 id="ConfiguringTransports-HighLevelProtocolURIs">High Level Protocol URIs</h2><p>The following higher level protocols can be configured via URI</p><h3 id="ConfiguringTransports-TheFailoverTransport">The Failover Transport</h3><p>The Failover transport layers reconnect logic on top of any of the other transports. This is what used to be the Reliable transport in ActiveMQ 3. Its configuration syntax allows you to specify any number of composite URIs. The Failover transport randomly chooses one of the composite URIs 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><p>For more information see the <a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></p><h3 id="ConfiguringTransports-TheFanoutTransport">The Fanout Transport</h3><p>The Fanout transport layers reconnect and replicate logic on top of any of the other transports. It is used replicate commands to multiple brokers.</p><p>For more information see the <a shape="rect" href="fanout-transport-reference.xml">Fanout Transport Reference</a></p><h2 id="ConfiguringTransports-UsingDiscovery">Using Discovery</h2><p>Often when using transports like TCP you want to use <a shape="rect" href="discovery.xml">Discovery</a> to locate the available brokers. This is different from using, say, <a shape="rect" href="multicast-transport-reference.xml">Multicast</a> - as the actual main communication is over TCP but multicast is purely used to discover the location of brokers.</p><h3 id="ConfiguringTransports-TheDiscoveryTransport">The Discovery Transport</h3><p>The Discovery transport works just like the reliable transport, except that it uses a discovery agent to locate the list of URIs to connect to.</p><p>For more information see the <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport Reference</a></p><h3 id="ConfiguringTransports-TheZeroConfTransport">The ZeroConf Transport</h3><p>The ZeroConf transport provides <a shape="rect" href="discovery.xml">Discovery</a> and it works like the <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport</a> but rather than using our own multicast based discovery mechanism (which allows you to configure the exact multicast address and port, etc.), the <a shape="rect" href="zeroconf.xml">ZeroConf</a> transport is used instead.</p><p>For more information see the <a shape="rect" href="zeroconf-transport-reference.xml">ZeroConf Transport Reference</a></p><h3 id="ConfiguringTransports-Serversideoptions">Server side options</h3><p>There are a number of options that can be used for changing behavior on the server for the <strong><code>TransportConnector</code></strong> in the ActiveMQ broker configuration. These are:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: red;"> <code>allowLinkStealing</code><br clear="none"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>This is enabled for default for MQTT transport.</p><p>Link Stealing is where the last of two or more connections with the same id (clientID for JMS) is deemed the valid connection and the older one is closed by the broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>discoveryURI</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If set, the multicast discovery address for client connections to find the broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>enableStatusMonitor</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will monitor connections to determine if they are blocked.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>name</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <strong><code>TransportConnector</code></strong> instance.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>rebalanceClusterClients</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will automatically re-balance clients across the cluster on changes of topology.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterClients</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If enabled, will update client connections (if they use the <strong><code>failover://</code></strong> transport) of changes to the broker cluster.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterClientsOnRemove</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will update clients if a broker is removed from the cluster.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterFilter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Comma separated list of regular expressions. Brokers with a name matching the pattern will be included for client updates.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>uri</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The bind address for the transport.</p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><strong>Note</strong>: properties in <span style="color: rgb(255,0,0);">red</span> are version 5.10 (and higher) options only.</p></div></div><p>Example configuration:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
- <!-- ... -->
+</plain-text-body></structured-macro><p>Trying to use <code>nio+ssl</code> transport url on the client side will instantiate the regular SSL transport.</p><h3>The Peer Transport</h3><p>The Peer transport provides a peer-to-peer network with ActiveMQ. What actually happens is the peer transport uses the VM transport to create and connect to a local embedded broker but which configures the embedded broker to establish network connections to other peer embedded brokers.</p><p>For more information see the <link><page ri:content-title="Peer Transport Reference"></page></link></p><h3>The UDP Transport</h3><p>This allows you to talk over UDP.</p><p>For more information see the <link><page ri:content-title="UDP Transport Reference"></page></link></p><h3>The Multicast Transport</h3><p>This allows you to talk over Multicast.</p><p>For more information see the <link><page ri:content-title="Multicast Transport Reference"></page></link></p><h3>The HTTP and HTTPS Transport</h3><p>This allows the ActiveMQ client and broker to tunnel over HTTP. If the client is not JMS you might want to look at <link><page ri:content-title="REST"></page></link> or <link><page ri:content-title="Ajax"></page></link> support instead.</p><p>For more information see the <link><page ri:content-title="HTTP and HTTPs Transports Reference"></page></link></p><h3>The WebSockets Transport</h3><p>This transport uses the new HTML5 WebSockets to exchange messages with the broker. For more information see the <link><page ri:content-title="WebSockets"></page></link> Transport Reference</p><h3>The Stomp Transport</h3><p>A plain text transport that can be used with many languages. See <link><page ri:content-title="Stomp"></page></link> for more details.</p><h2>General Purpose URIs</h2><p>You can configure other features via the URI syntax as follows...</p><h3>Connection Configuration URI</h3><p>Any Apache ActiveMQ JMS connection can be configured using the URL or explicitly setting properties on the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a> or <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> objects themselves.</p><p>For more information see <link><page ri:content-title="Connection Configuration URI"></page></link></p><h3>Destination Options</h3><p>You can configure various consumer related options using <link><page ri:content-title="Destination Options"></page></link> which allow you to configure destinations using URI syntax.</p><h3>Broker Configuration URI</h3><p>You can use a <link><page ri:content-title="Broker Configuration URI"></page></link> to configure an embedded broker, either using the BrokerFactory helper class from Java or using the activemq shell script. For more details see <link><page ri:content-title="Run Broker"></page><plain-text-link-body>How to Run a Broker</plain-text-link-body></link></p><h3>Configuring Wire Formats</h3><p>Any transport which involves marshalling messages onto some kind of network transport like TCP or UDP will typically use the <link><page ri:content-title="OpenWire"></page></link> format. This is configurable to customize how things appear on the wire.</p><p>For more information see <link><page ri:content-title="Configuring Wire Formats"></page></link></p><h2>High Level Protocol URIs</h2><p>The following higher level protocols can be configured via URI</p><h3>The Failover Transport</h3><p>The Failover transport layers reconnect logic on top of any of the other transports. This is what used to be the Reliable transport in ActiveMQ 3. Its configuration syntax allows you to specify any number of composite URIs. The Failover transport randomly chooses one of the composite URIs 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><p>For more information see the <link><page ri:content-title="Failover Transport Reference"></page></link></p><h3>The Fanout Transport</h3><p>The Fanout transport layers reconnect and replicate logic on top of any of the other transports. It is used replicate commands to multiple brokers.</p><p>For more information see the <link><page ri:content-title="Fanout Transport Reference"></page></link></p><h2>Using Discovery</h2><p>Often when using transports like TCP you want to use <link><page ri:content-title="Discovery"></page></link> to locate the available brokers. This is different from using, say, <link><page ri:content-title="Multicast Transport Reference"></page><plain-text-link-body>Multicast</plain-text-link-body></link> - as the actual main communication is over TCP but multicast is purely used to discover the location of brokers.</p><h3>The Discovery Transport</h3><p>The Discovery transport works just like the reliable transport, except that it uses a discovery agent to locate the list of URIs to connect to.</p><p>For more information see the <link><page ri:content-title="Discovery Transport Reference"></page></link></p><h3>The ZeroConf Transport</h3><p>The ZeroConf transport provides <link><page ri:content-title="Discovery"></page></link> and it works like the <link><page ri:content-title="Discovery Transport Reference"></page><plain-text-link-body>Discovery Transport</plain-text-link-body></link> but rather than using our own multicast based discovery mechanism (which allows you to configure the exact multicast address and port, etc.), the <link><page ri:content-title="ZeroConf"></page></link> transport is used instead.</p><p>For more information see the <link><page ri:content-title="ZeroConf Transport Reference"></page></link></p><h3>Server side options</h3><p>There are a number of options that can be used for changing behavior on the server for the <strong><code>TransportConnector</code></strong> in the ActiveMQ broker configuration. These are:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p><span style="color: red;"> <code>allowLinkStealing</code><br clear="none"></span></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>This is enabled for default for MQTT transport.</p><p>Link Stealing is where the last of two or more connections with the same id (clientID for JMS) is deemed the valid connection and the older one is closed by the broker.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>discoveryURI</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>If set, the multicast discovery address for client connections to find the broker.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>enableStatusMonitor</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Will monitor connections to determine if they are blocked.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>name</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>The name of the <strong><code>TransportConnector</code></strong> instance.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>rebalanceClusterClients</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Will automatically re-balance clients across the cluster on changes of topology.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>updateClusterClients</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If enabled, will update client connections (if they use the <strong><code>failover://</code></strong> transport) of changes to the broker cluster.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>updateClusterClientsOnRemove</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Will update clients if a broker is removed from the cluster.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>updateClusterFilter</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>Comma separated list of regular expressions. Brokers with a name matching the pattern will be included for client updates.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>uri</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>The bind address for the transport.</p></td></tr></tbody></table><structured-macro ac:macro-id="cc529423-17f8-4ab2-9dcb-305406ab27d0" ac:name="info" ac:schema-version="1"><rich-text-body><p><strong>Note</strong>: properties in <span style="color: rgb(255,0,0);">red</span> are version 5.10 (and higher) options only.</p></rich-text-body></structured-macro><p>Example configuration:</p><structured-macro ac:macro-id="7fbeb1d3-9c38-479d-b367-c1d8231f6bf8" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><broker>
+   <!-- ... -->
- <transportConnectors>
- <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" enableStatusMonitor="true"/>
- </<transportConnectors>
+   <transportConnectors>
+     <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" enableStatusMonitor="true"/>
+   </<transportConnectors>
- <!-- ... -->
-</broker>]]></script>
-</div></div></div>
+   <!-- ... -->
+</broker></plain-text-body></structured-macro></div>
diff --git a/configuring-version-5-transports.xml b/configuring-version-5-transports.xml
index 3af73cc..41c05a0 100644
--- a/configuring-version-5-transports.xml
+++ b/configuring-version-5-transports.xml
@@ -1,30 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ConfiguringVersion5Transports-Transportconfigurationoptions">Transport configuration options</h2><p>One of the first kinds of URI you are likely to use is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All of the following URI configurations are based on the java.net.URI class which does not allow whitespace to be used. So if you are using <strong><code>failover:</code></strong> or <strong><code>static:</code></strong> URIs, do not put any whitespace around the <strong><code>','</code> </strong>symbol.</p></div></div><h3 id="ConfiguringVersion5Transports-TheAUTOTransport">The AUTO Transport</h3><p>Starting with 5.13.0 ActiveMQ has support for automatic wire protocol detection over TCP, SSL, NIO, and NIO SSL.  OpenWire, STOMP, AMQP, and MQTT are supported.  For details see the <a shape="rect" href="auto.xml">AUTO </a>Transport Reference.</p><h3 id="ConfiguringVersion5Transports-TheVMTransport">The VM Transport</h3><p>The VM transport allows clients to connect to each other inside the VM without the overhead of the network communication. The connection used is not that of a socket connection but instead uses direct method invocations to enable a high performance embedded messaging system.</p><p>The first client to use the VM connection will boot an embedded broker. Subsequent connections will attach that the same broker. Once all VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For more information see the <a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheAMQPTransport">The AMQP Transport</h3><p>As of 5.8.0 ActiveMQ has support for AMQP. For details see the <a shape="rect" href="amqp.xml">AMQP</a> Transport Reference.</p><h3 id="ConfiguringVersion5Transports-TheMQTTTransport">The MQTT Transport</h3><p>Starting with 5.6.0 ActiveMQ also supports <a shape="rect" class="external-link" href="http://mqtt.org/" rel="nofollow">MQTT</a>. Its a light weight publish/subscribe messaging transport. See the <a shape="rect" href="mqtt.xml">MQTT</a> Transport Reference for details.</p><h3 id="ConfiguringVersion5Transports-TheTCPTransport">The TCP Transport</h3><p>The TCP transport allows clients to connect a remote ActiveMQ using a a TCP socket.</p><p>For more information see the <a shape="rect" href="tcp-transport-reference.xml">TCP Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheNIOTransport">The NIO Transport</h3><p>Same as the TCP transport, except that the <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/New_I/O" rel="nofollow">New I/O (NIO)</a> package is used, which may provide better performance. The Java NIO package should not be confused with IBM's <a shape="rect" class="external-link" href="http://java.sys-con.com/read/46658.htm" rel="nofollow">AIO4J </a> package.</p><p>To switch from TCP to NIO, simply change the scheme portion of the URI. Here's an example as defined within a broker's XML configuration file.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
- ...
- <transportConnectors>
- <transportConnector name="nio" uri="nio://0.0.0.0:61616"/>
- </<transportConnectors>
- ...
-</broker>
-]]></script>
-</div></div><p>Trying to use nio transport url on the client side will instantiate the regular TCP transport. For more information see the <a shape="rect" href="nio-transport-reference.xml">NIO Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheSSLTransport">The SSL Transport</h3><p>This allows you to talk over TCP using SSL. For more information see the <a shape="rect" href="ssl-transport-reference.xml">SSL Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheNIOSSLTransport">The NIO SSL Transport</h3><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Availability</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Available since 5.6</p></div></div><p>Implementing SSL transport over NIO. This allows you to connect large number of SSL clients to a single broker instance. It's server side transport-option only</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
- ...
- <transportConnectors>
- <transportConnector name="nio+ssl" uri="nio+ssl://0.0.0.0:61616"/>
- </<transportConnectors>
- ...
-</broker>
-]]></script>
-</div></div><p>Trying to use <code>nio+ssl</code> transport url on the client side will instantiate the regular SSL transport.</p><h3 id="ConfiguringVersion5Transports-ThePeerTransport">The Peer Transport</h3><p>The Peer transport provides a peer-to-peer network with ActiveMQ. What actually happens is the peer transport uses the VM transport to create and connect to a local embedded broker but which configures the embedded broker to establish network connections to other peer embedded brokers.</p><p>For more information see the <a shape="rect" href="peer-transport-reference.xml">Peer Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheUDPTransport">The UDP Transport</h3><p>This allows you to talk over UDP.</p><p>For more information see the <a shape="rect" href="udp-transport-reference.xml">UDP Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheMulticastTransport">The Multicast Transport</h3><p>This allows you to talk over Multicast.</p><p>For more information see the <a shape="rect" href="multicast-transport-reference.xml">Multicast Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheHTTPandHTTPSTransport">The HTTP and HTTPS Transport</h3><p>This allows the ActiveMQ client and broker to tunnel over HTTP. If the client is not JMS you might want to look at <a shape="rect" href="rest.xml">REST</a> or <a shape="rect" href="ajax.xml">Ajax</a> support instead.</p><p>For more information see the <a shape="rect" href="http-and-https-transports-reference.xml">HTTP and HTTPs Transports Reference</a></p><h3 id="ConfiguringVersion5Transports-TheWebSocketsTransport">The WebSockets Transport</h3><p>This transport uses the new HTML5 WebSockets to exchange messages with the broker. For more information see the <a shape="rect" href="websockets.xml">WebSockets</a> Transport Reference</p><h3 id="ConfiguringVersion5Transports-TheStompTransport">The Stomp Transport</h3><p>A plain text transport that can be used with many languages. See <a shape="rect" href="stomp.xml">Stomp</a> for more details.</p><h2 id="ConfiguringVersion5Transports-GeneralPurposeURIs">General Purpose URIs</h2><p>You can configure other features via the URI syntax as follows...</p><h3 id="ConfiguringVersion5Transports-ConnectionConfigurationURI">Connection Configuration URI</h3><p>Any Apache ActiveMQ JMS connection can be configured using the URL or explicitly setting properties on the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a> or <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> objects themselves.</p><p>For more information see <a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a></p><h3 id="ConfiguringVersion5Transports-DestinationOptions">Destination Options</h3><p>You can configure various consumer related options using <a shape="rect" href="destination-options.xml">Destination Options</a> which allow you to configure destinations using URI syntax.</p><h3 id="ConfiguringVersion5Transports-BrokerConfigurationURI">Broker Configuration URI</h3><p>You can use a <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a> to configure an embedded broker, either using the BrokerFactory helper class from Java or using the activemq shell script. For more details see <a shape="rect" href="run-broker.xml">How to Run a Broker</a></p><h3 id="ConfiguringVersion5Transports-ConfiguringWireFormats">Configuring Wire Formats</h3><p>Any transport which involves marshalling messages onto some kind of network transport like TCP or UDP will typically use the <a shape="rect" href="openwire.xml">OpenWire</a> format. This is configurable to customize how things appear on the wire.</p><p>For more information see <a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a></p><h2 id="ConfiguringVersion5Transports-HighLevelProtocolURIs">High Level Protocol URIs</h2><p>The following higher level protocols can be configured via URI</p><h3 id="ConfiguringVersion5Transports-TheFailoverTransport">The Failover Transport</h3><p>The Failover transport layers reconnect logic on top of any of the other transports. This is what used to be the Reliable transport in ActiveMQ 3. Its configuration syntax allows you to specify any number of composite URIs. The Failover transport randomly chooses one of the composite URIs 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><p>For more information see the <a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheFanoutTransport">The Fanout Transport</h3><p>The Fanout transport layers reconnect and replicate logic on top of any of the other transports. It is used replicate commands to multiple brokers.</p><p>For more information see the <a shape="rect" href="fanout-transport-reference.xml">Fanout Transport Reference</a></p><h2 id="ConfiguringVersion5Transports-UsingDiscovery">Using Discovery</h2><p>Often when using transports like TCP you want to use <a shape="rect" href="discovery.xml">Discovery</a> to locate the available brokers. This is different from using, say, <a shape="rect" href="multicast-transport-reference.xml">Multicast</a> - as the actual main communication is over TCP but multicast is purely used to discover the location of brokers.</p><h3 id="ConfiguringVersion5Transports-TheDiscoveryTransport">The Discovery Transport</h3><p>The Discovery transport works just like the reliable transport, except that it uses a discovery agent to locate the list of URIs to connect to.</p><p>For more information see the <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheZeroConfTransport">The ZeroConf Transport</h3><p>The ZeroConf transport provides <a shape="rect" href="discovery.xml">Discovery</a> and it works like the <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport</a> but rather than using our own multicast based discovery mechanism (which allows you to configure the exact multicast address and port, etc.), the <a shape="rect" href="zeroconf.xml">ZeroConf</a> transport is used instead.</p><p>For more information see the <a shape="rect" href="zeroconf-transport-reference.xml">ZeroConf Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-Serversideoptions">Server side options</h3><p>There are a number of options that can be used for changing behavior on the server for the <strong><code>TransportConnector</code></strong> in the ActiveMQ broker configuration. These are:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: red;"> <code>allowLinkStealing</code><br clear="none"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>This is enabled for default for MQTT transport.</p><p>Link Stealing is where the last of two or more connections with the same id (clientID for JMS) is deemed the valid connection and the older one is closed by the broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>discoveryURI</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If set, the multicast discovery address for client connections to find the broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>enableStatusMonitor</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will monitor connections to determine if they are blocked.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>name</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <strong><code>TransportConnector</code></strong> instance.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>rebalanceClusterClients</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will automatically re-balance clients across the cluster on changes of topology.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterClients</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If enabled, will update client connections (if they use the <strong><code>failover://</code></strong> transport) of changes to the broker cluster.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterClientsOnRemove</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Will update clients if a broker is removed from the cluster.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterFilter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Comma separated list of regular expressions. Brokers with a name matching the pattern will be included for client updates.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>uri</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The bind address for the transport.</p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><strong>Note</strong>: properties in <span style="color: rgb(255,0,0);">red</span> are version 5.10 (and higher) options only.</p></div></div><p>Example configuration:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
- <!-- ... -->
-
- <transportConnectors>
- <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" enableStatusMonitor="true"/>
- </<transportConnectors>
-
- <!-- ... -->
-</broker>]]></script>
-</div></div></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="19b708b7-5a5a-4415-a812-e6f67dcf36ef" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Configuring Transports"></page></link></parameter></structured-macro></div>
diff --git a/configuring-wire-formats.xml b/configuring-wire-formats.xml
index c73854b..4e25b9d 100644
--- a/configuring-wire-formats.xml
+++ b/configuring-wire-formats.xml
@@ -1,9 +1,5 @@
-<div class="wiki-content maincontent"><h3 id="ConfiguringWireFormats-TheOpenWireWireFormat">The OpenWire Wire Format</h3><p>OpenWire is the default wire format used by ActiveMQ.  It provides a highly efficient binary format for high speed messaging.  OpenWire options can be configured on a JMS client's connection URI or on a broker's transport bind URI.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cacheEnabled</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should commonly repeated values be cached so that less marshaling occurs?</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cacheSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1024</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>cacheEnabled=true</code></strong> then this parameter is used to specify the number of values to be cached.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxInactivityDuration</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum <a shape="rect" href="activemq-inactivitymonitor.xml">inactivity</a> duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to die. Therefore allow the broker to kill connections when they have been inactive for the configured period of time. Used by some transports to enable a keep alive heart beat feature.</p><p>Inactivity monitoring is disabled when set to a value <strong><code><= 0</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxInactivityDurationInitalDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The initial delay before starting <a shape="rect" href="activemq-inactivitymonitor.xml">inactivity</a> checks.</p><p>Yes, the word <strong><code>'Inital'</code></strong> is supposed to be misspelled like that.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxFrameSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>MAX_LONG</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Maximum allowed frame size. Can help help prevent OOM DOS attacks.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>sizePrefixDisabled</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the size of the packet be prefixed before each packet is marshaled?</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>stackTraceEnabled</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the stack trace of exception that occur on the broker be sent to the client?</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>tcpNoDelayEnabled</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Does not affect the wire format, but provides a hint to the peer that <strong><code>TCP_NODELAY</code></strong> should be enabled on the communications Socket.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>tightEncodingEnabled</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should wire size be optimized over CPU usage?</p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Use the Correct Prefix!</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Wire format options must have the prefix <strong><code>wireFormat.</code></strong> to take effect, e.g., <strong><code>wireFormat.maxInactivityDuration=10000</code></strong>. Options missing this prefix will be ignored.</p></div></div><h4 id="ConfiguringWireFormats-ExampleConfigurations">Example Configurations</h4><p><strong>Java:</strong></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory("tcp://localhost:61616?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false");]]></script>
-</div></div><p><strong><br clear="none"></strong></p><p> </p><p><strong>Spring:</strong></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="failover:(tcp://localhost:61616?jms.optimizeAcknowledge=false&wireFormat.maxInactivityDuration=30000)"/>
+<div class="wiki-content maincontent"><h3>The OpenWire Wire Format</h3><p>OpenWire is the default wire format used by ActiveMQ.  It provides a highly efficient binary format for high speed messaging.  OpenWire options can be configured on a JMS client's connection URI or on a broker's transport bind URI.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>cacheEnabled</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Should commonly repeated values be cached so that less marshaling occurs?</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>cacheSize</code></p></td><td colspan="1" rowspan="1"><p><code>1024</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>cacheEnabled=true</code></strong> then this parameter is used to specify the number of values to be cached.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxInactivityDuration</code></p></td><td colspan="1" rowspan="1"><p><code>30000</code></p></td><td colspan="1" rowspan="1"><p>The maximum <link><page ri:content-title="ActiveMQ InactivityMonitor"></page><plain-text-link-body>inactivity</plain-text-link-body></link> duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to die. Therefore allow the broker to kill connections when they have been inactive for the configured period of time. Used by some transports to enable a keep alive heart beat feature.</p><p>Inactivity monitoring is disabled when set to a value <strong><code><= 0</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxInactivityDurationInitalDelay</code></p></td><td colspan="1" rowspan="1"><p><code>10000</code></p></td><td colspan="1" rowspan="1"><p>The initial delay before starting <link><page ri:content-title="ActiveMQ InactivityMonitor"></page><plain-text-link-body>inactivity</plain-text-link-body></link> checks.</p><p>Yes, the word <strong><code>'Inital'</code></strong> is supposed to be misspelled like that.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxFrameSize</code></p></td><td colspan="1" rowspan="1"><p><code>MAX_LONG</code></p></td><td colspan="1" rowspan="1"><p>Maximum allowed frame size. Can help help prevent OOM DOS attacks.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>sizePrefixDisabled</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Should the size of the packet be prefixed before each packet is marshaled?</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>stackTraceEnabled</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Should the stack trace of exception that occur on the broker be sent to the client?</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>tcpNoDelayEnabled</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Does not affect the wire format, but provides a hint to the peer that <strong><code>TCP_NODELAY</code></strong> should be enabled on the communications Socket.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>tightEncodingEnabled</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Should wire size be optimized over CPU usage?</p></td></tr></tbody></table><structured-macro ac:macro-id="5f63c58b-03ae-42b4-acb9-5129da2b15db" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Use the Correct Prefix!</parameter><rich-text-body><p>Wire format options must have the prefix <strong><code>wireFormat.</code></strong> to take effect, e.g., <strong><code>wireFormat.maxInactivityDuration=10000</code></strong>. Options missing this prefix will be ignored.</p></rich-text-body></structured-macro><h4>Example Configurations</h4><p><strong>Java:</strong></p><structured-macro ac:macro-id="82d9cc9e-c50c-4ac4-9e27-ae3d5cc4a5ac" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><plain-text-body>ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory("tcp://localhost:61616?wireFormat.cacheEnabled=false&wireFormat.tightEncodingEnabled=false");</plain-text-body></structured-macro><p><strong><br clear="none"></strong></p><p> </p><p><strong>Spring:</strong></p><structured-macro ac:macro-id="554a55c5-5f0b-489e-ab16-f3d317658e94" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><bean class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="failover:(tcp://localhost:61616?jms.optimizeAcknowledge=false&wireFormat.maxInactivityDuration=30000)"/>
<!-- other options... -->
-</bean>]]></script>
-</div></div><p> </p><p> </p><p><strong><br clear="none"></strong></p><p> </p></div>
+</bean></plain-text-body></structured-macro><p> </p><p> </p><p><strong><br clear="none"></strong></p><p> </p></div>
diff --git a/connection-configuration-uri.xml b/connection-configuration-uri.xml
index 25b0f20..6648827 100644
--- a/connection-configuration-uri.xml
+++ b/connection-configuration-uri.xml
@@ -1,8 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="ConnectionConfigurationURI-ConnectionConfigurationURI">Connection Configuration URI</h2><p>An Apache ActiveMQ connection can be configured by explicitly setting properties on the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a> or <a shape="rect" class="external-link" 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><h3 id="ConnectionConfigurationURI-Example">Example</h3><p>You set the property called <strong><code>jms.$PROPERTY</code></strong> on a regular connection URI. For example you can set the <strong><code>brokerURL</code></strong> on your <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> to the following value to enable <a shape="rect" href="async-sends.xml">Async Sends</a></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tcp://localhost:61616?jms.useAsyncSend=true
-]]></script>
-</div></div><h3 id="ConnectionConfigurationURI-ConnectionOptions">Connection Options</h3><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Use the Correct Prefix!</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The following options should be prefixed with <strong><code>jms.</code></strong> when used on a <strong><code>brokerURL</code></strong> or a broker's transport connector.</p></div></div><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><code>alwaysSessionAsync</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong> a separate thread is used for dispatching messages for each Session in the Connection.</p><p>A separate thread is always used when there's more than one session, or the session isn't in <strong><code>Session.AUTO_ACKNOWLEDGE</code></strong> or <strong><code>Session.DUPS_OK_ACKNOWLEDGE</code></strong> mode.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>alwaysSyncSend</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong> a <strong><code>MessageProducer</code></strong> will always use Sync sends when sending a Message even if it is not required for the Delivery Mode.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>auditDepth</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>2048</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The size of the message window that will be audited for duplicates and out of order messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>auditMaximumProducerNumber</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>64</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Maximum number of producers that will be audited.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>checkForDuplicates</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong> the consumer will check for duplicate messages and properly handle the message to make sure that it is not processed twice inadvertently.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>clientID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the JMS clientID to use for the connection.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>closeTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>15000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the timeout, in milliseconds, before a close is considered complete. Normally a <strong><code>close()</code></strong> on a connection waits for confirmation from the broker.</p><p>This allows the close operation to timeout preventing the client from hanging when no broker is available.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumerExpiryCheckEnabled</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Controls whether message expiration checking is done in each <strong><code>MessageConsumer</code></strong> prior to dispatching a message. Disabling this check can lead to consumption of expired messages. (since 5.11).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>copyMessageOnSend</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should a JMS message be copied to a new JMS Message object as part of the <strong><code>send()</code></strong> method in JMS. This is enabled by default to be compliant with the JMS specification.</p><p>For a performance boost set to <strong><code>false</code></strong> if you do not mutate JMS messages after they are sent.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>disableTimeStampsByDefault</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets whether or not timestamps on messages should be disabled or not.</p><p>For a small performance boost set to <strong><code>false</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>dispatchAsync</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker <a shape="rect" href="consumer-dispatch-async.xml">dispatch messages asynchronously</a> to the consumer?</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>nestedMapAndListEnabled</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Controls whether <a shape="rect" href="structured-message-properties-and-mapmessages.xml">Structured Message Properties and MapMessages</a> are supported so that Message properties and <strong><code>MapMessage</code></strong> entries can contain nested Map and List objects. Available from version 4.1.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>objectMessageSerializationDefered</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When an object is set on an <strong><code>ObjectMessage</code></strong> the JMS spec requires the object be serialized by that set method.</p><p>When <strong><code>true</code></strong> the object will not be serialized. The object may subsequently be serialized if the message needs to be sent over a socket or stored to disk.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>optimizeAcknowledge</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables an optimized acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use <strong><code>Session.DUPS_OK_ACKNOWLEDGE</code></strong> acknowledgement mode for the consumers which can often be faster.</p><p><strong>WARNING</strong>: enabling this issue could cause some issues with auto-acknowledgement on reconnection.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>optimizeAcknowledgeTimeOut</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>300</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If > 0, specifies the max time, in milliseconds, between batch acknowledgements when <strong><code>optimizeAcknowledge</code></strong> is enabled. (since 5.6).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>optimizedAckScheduledAckInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If > 0, specifies a <span style="line-height: 1.4285715;">time interval upon which all the outstanding ACKs are delivered when optimized acknowledge is used so that a long running consumer that doesn't receive any more messages will eventually ACK the last few un-ACK'ed messages (since 5.7).</span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>optimizedMessageDispatch</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> a larger prefetch limit is used - only applicable for durable topic subscribers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useAsyncSend</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Forces the use of <a shape="rect" href="async-sends.xml">Async Sends</a> which adds a massive performance boost; but means that the <strong><code>send()</code></strong> method will return immediately whether the message has been sent or not which could lead to message loss.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useCompression</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables the use of compression on the message's body.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useRetroactiveConsumer</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>warnAboutUnstartedConnectionTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The timeout, in milliseconds, from the time of connection creation to when a warning is generated if the connection is not properly started via <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#start()" rel="nofollow">Connection.start()</a> and a message is received by a consumer. It is a very common gotcha to forget to <a shape="rect" href="i-am-not-receiving-any-messages-what-is-wrong.xml">start the connection and then wonder why no messages are delivered</a> so this option makes the default case to create a warning if the user forgets.</p><p>To disable the warning just set the value to <strong><code>< 0</code></strong>.</p></td></tr></tbody></table></div><h3 id="ConnectionConfigurationURI-NestedOptions">Nested Options</h3><p>You can also configure nested objects on the connection object using the given prefixes. See the javadoc for a breakdown of each individual property.</p><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>Object configured</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>See Also</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jms.blobTransferPolicy.*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/blob/BlobTransferPolicy.html">BlobTransferPolicy</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="unresolved" href="#">Blob Message</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jms.prefetchPolicy.*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://http//activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html" rel="nofollow">ActiveMQPrefetchPolicy</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="what-is-the-prefetch-limit-for.xml">What is the Prefetch Limit For?</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jms.redeliveryPolicy.*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/RedeliveryPolicy.html">RedeliveryPolicy</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="redelivery-policy.xml">Redelivery Policy</a></p></td></tr></tbody></table></div><p>For example you could set</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tcp://localhost:61616?jms.prefetchPolicy.all=100&jms.redeliveryPolicy.maximumRedeliveries=5
-]]></script>
-</div></div></div>
+<div class="wiki-content maincontent"><h2>Connection Configuration URI</h2><p>An Apache ActiveMQ connection can be configured by explicitly setting properties on the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a> or <a shape="rect" 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><h3>Example</h3><p>You set the property called <strong><code>jms.$PROPERTY</code></strong> on a regular connection URI. For example you can set the <strong><code>brokerURL</code></strong> on your <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> to the following value to enable <link><page ri:content-title="Async Sends"></page></link></p><structured-macro ac:macro-id="cdb20bb5-233a-4d06-a1d6-95b6a9d4082e" ac:name="code" ac:schema-version="1"><plain-text-body>tcp://localhost:61616?jms.useAsyncSend=true
+</plain-text-body></structured-macro><h3>Connection Options</h3><structured-macro ac:macro-id="677dbbcf-a4ab-498d-b67a-2360c5dec022" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Use the Correct Prefix!</parameter><rich-text-body><p>The following options should be prefixed with <strong><code>jms.</code></strong> when used on a <strong><code>brokerURL</code></strong> or a broker's transport connector.</p></rich-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>alwaysSessionAsync</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code></strong> a separate thread is used for dispatching messages for each Session in the Connection.</p><p>A separate thread is always used when there's more than one session, or the session isn't in <strong><code>Session.AUTO_ACKNOWLEDGE</code></strong> or <strong><code>Session.DUPS_OK_ACKNOWLEDGE</code></strong> mode.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>alwaysSyncSend</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code></strong> a <strong><code>MessageProducer</code></strong> will always use Sync sends when sending a Message even if it is not required for the Delivery Mode.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>auditDepth</code></p></td><td colspan="1" rowspan="1"><p><code>2048</code></p></td><td colspan="1" rowspan="1"><p>The size of the message window that will be audited for duplicates and out of order messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>auditMaximumProducerNumber</code></p></td><td colspan="1" rowspan="1"><p><code>64</code></p></td><td colspan="1" rowspan="1"><p>Maximum number of producers that will be audited.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>checkForDuplicates</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code></strong> the consumer will check for duplicate messages and properly handle the message to make sure that it is not processed twice inadvertently.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>clientID</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>Sets the JMS clientID to use for the connection.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>closeTimeout</code></p></td><td colspan="1" rowspan="1"><p><code>15000</code></p></td><td colspan="1" rowspan="1"><p>Sets the timeout, in milliseconds, before a close is considered complete. Normally a <strong><code>close()</code></strong> on a connection waits for confirmation from the broker.</p><p>This allows the close operation to timeout preventing the client from hanging when no broker is available.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumerExpiryCheckEnabled</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Controls whether message expiration checking is done in each <strong><code>MessageConsumer</code></strong> prior to dispatching a message. Disabling this check can lead to consumption of expired messages. (since 5.11).</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>copyMessageOnSend</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Should a JMS message be copied to a new JMS Message object as part of the <strong><code>send()</code></strong> method in JMS. This is enabled by default to be compliant with the JMS specification.</p><p>For a performance boost set to <strong><code>false</code></strong> if you do not mutate JMS messages after they are sent.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>disableTimeStampsByDefault</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Sets whether or not timestamps on messages should be disabled or not.</p><p>For a small performance boost set to <strong><code>false</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>dispatchAsync</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Should the broker <link><page ri:content-title="Consumer Dispatch Async"></page><plain-text-link-body>dispatch messages asynchronously</plain-text-link-body></link> to the consumer?</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>nestedMapAndListEnabled</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Controls whether <link><page ri:content-title="Structured Message Properties and MapMessages"></page></link> are supported so that Message properties and <strong><code>MapMessage</code></strong> entries can contain nested Map and List objects. Available from version 4.1.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>objectMessageSerializationDefered</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>When an object is set on an <strong><code>ObjectMessage</code></strong> the JMS spec requires the object be serialized by that set method.</p><p>When <strong><code>true</code></strong> the object will not be serialized. The object may subsequently be serialized if the message needs to be sent over a socket or stored to disk.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>optimizeAcknowledge</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Enables an optimized acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use <strong><code>Session.DUPS_OK_ACKNOWLEDGE</code></strong> acknowledgement mode for the consumers which can often be faster.</p><p><strong>WARNING</strong>: enabling this issue could cause some issues with auto-acknowledgement on reconnection.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>optimizeAcknowledgeTimeOut</code></p></td><td colspan="1" rowspan="1"><p><code>300</code></p></td><td colspan="1" rowspan="1"><p>If > 0, specifies the max time, in milliseconds, between batch acknowledgements when <strong><code>optimizeAcknowledge</code></strong> is enabled. (since 5.6).</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>optimizedAckScheduledAckInterval</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>If > 0, specifies a <span style="line-height: 1.4285715;">time interval upon which all the outstanding ACKs are delivered when optimized acknowledge is used so that a long running consumer that doesn't receive any more messages will eventually ACK the last few un-ACK'ed messages (since 5.7).</span></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>optimizedMessageDispatch</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> a larger prefetch limit is used - only applicable for durable topic subscribers.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useAsyncSend</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Forces the use of <link><page ri:content-title="Async Sends"></page></link> which adds a massive performance boost; but means that the <strong><code>send()</code></strong> method will return immediately whether the message has been sent or not which could lead to message loss.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useCompression</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Enables the use of compression on the message's body.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useRetroactiveConsumer</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>warnAboutUnstartedConnectionTimeout</code></p></td><td colspan="1" rowspan="1"><p><code>500</code></p></td><td colspan="1" rowspan="1"><p>The timeout, in milliseconds, from the time of connection creation to when a warning is generated if the connection is not properly started via <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#start()">Connection.start()</a> and a message is received by a consumer. It is a very common gotcha to forget to <link><page ri:content-title="I am not receiving any messages, what is wrong"></page><plain-text-link-body>start the connection and then wonder why no messages are delivered</plain-text-link-body></link> so this option makes the default case to create a warning if the user forgets.</p><p>To disable the warning just set the value to <strong><code>< 0</code></strong>.</p></td></tr></tbody></table><h3>Nested Options</h3><p>You can also configure nested objects on the connection object using the given prefixes. See the javadoc for a breakdown of each individual property.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Object configured</p></th><th colspan="1" rowspan="1"><p>See Also</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>jms.blobTransferPolicy.*</code></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/blob/BlobTransferPolicy.html">BlobTransferPolicy</a></p></td><td colspan="1" rowspan="1"><p><link><page ri:content-title="Blob Message"></page><plain-text-link-body>Blob Message</plain-text-link-body></link></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>jms.prefetchPolicy.*</code></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://http//activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html">ActiveMQPrefetchPolicy</a></p></td><td colspan="1" rowspan="1"><p><link><page ri:content-title="What is the Prefetch Limit For?"></page></link></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>jms.redeliveryPolicy.*</code></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/RedeliveryPolicy.html">RedeliveryPolicy</a></p></td><td colspan="1" rowspan="1"><p><link><page ri:content-title="Redelivery Policy"></page></link></p></td></tr></tbody></table><p>For example you could set</p><structured-macro ac:macro-id="0255c160-beb2-4274-9d9c-5c9fcf102482" ac:name="code" ac:schema-version="1"><plain-text-body>tcp://localhost:61616?jms.prefetchPolicy.all=100&jms.redeliveryPolicy.maximumRedeliveries=5
+</plain-text-body></structured-macro></div>
diff --git a/connection-factory-properties.xml b/connection-factory-properties.xml
index 0439247..3cc7b8f 100644
--- a/connection-factory-properties.xml
+++ b/connection-factory-properties.xml
@@ -3,27 +3,27 @@
<p>The Connection Factory properties that can be configured are:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Required</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>ServerUrl</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set in resource adapter</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>UserName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set in resource adapter</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Clientid</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set in resource adapter</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Password</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set in resource adapter</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>UseInboundSession</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set in resource adapter</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Required</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>ServerUrl</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>set in resource adapter</p></td></tr><tr><td colspan="1" rowspan="1"><p>UserName</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>set in resource adapter</p></td></tr><tr><td colspan="1" rowspan="1"><p>Clientid</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>set in resource adapter</p></td></tr><tr><td colspan="1" rowspan="1"><p>Password</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>set in resource adapter</p></td></tr><tr><td colspan="1" rowspan="1"><p>UseInboundSession</p></td><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p>set in resource adapter</p></td></tr></tbody></table>
-<h4 id="ConnectionFactoryProperties-ServerUrl">ServerUrl </h4>
+<h4>ServerUrl </h4>
<p>The URL to the ActiveMQ server that you want this connection to connect to. If using an embedded broker, this value should be 'vm://localhost'.</p>
-<h4 id="ConnectionFactoryProperties-UserName">UserName</h4>
+<h4>UserName</h4>
<p>The default user name that will be used to establish connections to the ActiveMQ server.</p>
-<h4 id="ConnectionFactoryProperties-Password">Password</h4>
+<h4>Password</h4>
<p>The default password that will be used to log the default user into the ActiveMQ server.</p>
-<h4 id="ConnectionFactoryProperties-Clientid">Clientid</h4>
+<h4>Clientid</h4>
<p>The client id that will be set on the connection that is established to the ActiveMQ server.</p>
-<h4 id="ConnectionFactoryProperties-UseInboundSession">UseInboundSession</h4>
+<h4>UseInboundSession</h4>
<p>Boolean to configure if outbound connections should reuse the inbound connection's session for sending messages.</p></div>
diff --git a/connectivity.xml b/connectivity.xml
index 2bccfb1..a63dfff 100644
--- a/connectivity.xml
+++ b/connectivity.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>Apache ActiveMQ is designed to support a large number if <a shape="rect" href="cross-language-clients.xml">Cross Language Clients</a>, speak a wide range of <a shape="rect" href="protocols.xml">Protocols</a> and be usable in a wide variety of <a shape="rect" href="containers.xml">Containers</a> in addition to being usable in a stand alone Java SE platform.</p>
+<div class="wiki-content maincontent"><p>Apache ActiveMQ is designed to support a large number if <link><page ri:content-title="Cross Language Clients"></page></link>, speak a wide range of <link><page ri:content-title="Protocols"></page></link> and be usable in a wide variety of <link><page ri:content-title="Containers"></page></link> in addition to being usable in a stand alone Java SE platform.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="ajax.xml">Ajax</a></li><li><a shape="rect" href="containers.xml">Containers</a><ul class="childpages-macro"><li><a shape="rect" href="axis-and-cxf-support.xml">Axis and CXF Support</a></li><li><a shape="rect" href="blazeds.xml">BlazeDS</a></li><li><a shape="rect" href="geronimo.xml">Geronimo</a></li><li><a shape="rect" href="integrating-apache-activemq-with-glassfish.xml">Integrating Apache ActiveMQ with Glassfish</a></li><li><a shape="rect" href="integrating-apache-activemq-with-jboss.xml">Integrating Apache ActiveMQ with JBoss</a></li><li><a shape="rect" href="j2ee.xml">J2EE</a></li><li><a shape="rect" href="jboss-integration.xml">JBoss Integration</a></li><li><a shape="rect" href="jca-container.xml">JCA Container</a></li><li><a shape="rect" href="jndi-support.xml">JNDI Support</a></li><li><a shape="rect" href="old-osgi-integration.xml">Old OSGi Integration</a></li><li><a shape="rect" href="osgi-integration.xml">OSGi Integration</a></li><li><a shape="rect" href="resource-adapter.xml">Resource Adapter</a></li><li><a shape="rect" href="sjsas-with-genericjmsra.xml">SJSAS with GenericJMSRA</a></li><li><a shape="rect" href="spring-support.xml">Spring Support</a></li><li><a shape="rect" href="sun-jndi.xml">Sun JNDI</a></li><li><a shape="rect" href="tomcat.xml">Tomcat</a></li><li><a shape="rect" href="weblogic-integration.xml">WebLogic Integration</a></li><li><a shape="rect" href="zos.xml">zOS</a></li></ul></li><li><a shape="rect" href="cross-language-clients.xml">Cross Language Clients</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-c-clients.xml">ActiveMQ C++ Clients</a></li><li><a shape="rect" href="c-integration.xml">C Integration</a></li><li><a shape="rect" href="delphi-and-freepascal.xml">Delphi and FreePascal</a></li></ul></li><li><a shape="rect" href="jms-to-jms-bridge.xml">JMS to JMS Bridge</a></li><li><a shape="rect" href="protocols.xml">Protocols</a><ul class="childpages-macro"><li><a shape="rect" href="amqp.xml">AMQP</a></li><li><a shape="rect" href="auto.xml">AUTO</a></li><li><a shape="rect" href="mqtt.xml">MQTT</a></li><li><a shape="rect" href="openwire.xml">OpenWire</a></li><li><a shape="rect" href="rest.xml">REST</a></li><li><a shape="rect" href="rss-and-atom.xml">RSS and Atom</a></li><li><a shape="rect" href="stomp.xml">Stomp</a></li><li><a shape="rect" href="wsif.xml">WSIF</a></li><li><a shape="rect" href="ws-notification.xml">WS Notification</a></li><li><a shape="rect" href="xmpp.xml">XMPP</a></li></ul></li><li><a shape="rect" href="websockets.xml">WebSockets</a></li></ul> </div>
+<structured-macro ac:macro-id="e62fc540-f05e-466a-bda3-36de08652244" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">2</parameter></structured-macro> </div>
diff --git a/consumer-dispatch-async.xml b/consumer-dispatch-async.xml
index bf3557e..33ef563 100644
--- a/consumer-dispatch-async.xml
+++ b/consumer-dispatch-async.xml
@@ -1,12 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="ConsumerDispatchAsync-Overview">Overview</h2><p>From ActiveMQ v4: the choice of a broker performing synchronous or asynchronous dispatch to a consumer has become more configurable. It is now configured as a default value on the <a shape="rect" href="connection-configuration-uri.xml">connection URI, Connection and ConnectionFactory</a> as well as with being customizable on a per consumer basis via the <a shape="rect" href="destination-options.xml">Destination Options</a> instead previously just being a transport server setting.</p><p>This makes more sense since you want to do asynchronous message delivery to slower consumers, but synchronous message delivery for faster consumers (to avoid the synchronization and context switching costs of adding another SEDA queue). The downside to using synchronous message delivery is that the producer is more likely to block if there is a slow consumer that he is dispatching messages to.</p><p>The default setting is <strong><code>dispatchAsync=true</code></strong> which is the best setting for high performance. If you want to deal better with slow consumers you will want to enable this setting. If you want better throughput and the chances of having a slow consumer are low, you may want to change this to <strong><code>dispatchAsync=false</code></strong>.</p><h3 id="ConsumerDispatchAsync-ConfiguringAsyncDispatchattheConnectionFactoryLevel">Configuring Async Dispatch at the ConnectionFactory Level</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[((ActiveMQConnectionFactory)connectionFactory).setDispatchAsync(false);
-]]></script>
-</div></div><h3 id="ConsumerDispatchAsync-ConfiguringDispatchAsyncattheConnectionLevel">Configuring Dispatch Async at the Connection Level</h3><p>Configuring the <strong><code>dispatchAsync</code></strong> setting at this level overrides the settings at the connection factory level.</p><h3 id="ConsumerDispatchAsync-ConfiguringDispatchAsyncattheConsumerLevelusingtheDestinationURI">Configuring Dispatch Async at the Consumer Level using the Destination URI</h3><p>Configuring the <strong><code>dispatchAsync</code></strong> using <a shape="rect" href="destination-options.xml">Destination Options</a> overrides the settings at the connection and connection factory level.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[queue = new ActiveMQQueue("TEST.QUEUE?consumer.dispatchAsync=false");
+<div class="wiki-content maincontent"><h2>Overview</h2><p>From ActiveMQ v4: the choice of a broker performing synchronous or asynchronous dispatch to a consumer has become more configurable. It is now configured as a default value on the <link><page ri:content-title="Connection Configuration URI"></page><plain-text-link-body>connection URI, Connection and ConnectionFactory</plain-text-link-body></link> as well as with being customizable on a per consumer basis via the <link><page ri:content-title="Destination Options"></page></link> instead previously just being a transport server setting.</p><p>This makes more sense since you want to do asynchronous message delivery to slower consumers, but synchronous message delivery for faster consumers (to avoid the synchronization and context switching costs of adding another SEDA queue). The downside to using synchronous message delivery is that the producer is more likely to block if there is a slow consumer that he is dispatching messages to.</p><p>The default setting is <strong><code>dispatchAsync=true</code></strong> which is the best setting for high performance. If you want to deal better with slow consumers you will want to enable this setting. If you want better throughput and the chances of having a slow consumer are low, you may want to change this to <strong><code>dispatchAsync=false</code></strong>.</p><h3>Configuring Async Dispatch at the ConnectionFactory Level</h3><structured-macro ac:macro-id="b6c7c4b9-0a3b-4d23-9106-5b97ec057de0" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>((ActiveMQConnectionFactory)connectionFactory).setDispatchAsync(false);
+</plain-text-body></structured-macro><h3>Configuring Dispatch Async at the Connection Level</h3><p>Configuring the <strong><code>dispatchAsync</code></strong> setting at this level overrides the settings at the connection factory level.</p><h3>Configuring Dispatch Async at the Consumer Level using the Destination URI</h3><p>Configuring the <strong><code>dispatchAsync</code></strong> using <link><page ri:content-title="Destination Options"></page></link> overrides the settings at the connection and connection factory level.</p><structured-macro ac:macro-id="1c757d6c-8c52-4ae7-bb24-8a4c1d6d3f47" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>queue = new ActiveMQQueue("TEST.QUEUE?consumer.dispatchAsync=false");
consumer = session.createConsumer(queue);
-]]></script>
-</div></div><h3 id="ConsumerDispatchAsync-DisablingAsyncDispatchonBroker'sTransportConnector">Disabling Async Dispatch on Broker's Transport Connector</h3><p>It is possible to disable async dispatch on a specific transport connector via the <strong><code>disableAsyncDispatch</code></strong> property. Once disabled for this transport, it cannot be enabled by individual clients.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="openwire" uri="tcp://0.0.0.0:61616" disableAsyncDispatch="true"/>
-]]></script>
-</div></div><p> </p><p> </p><p> </p></div>
+</plain-text-body></structured-macro><h3>Disabling Async Dispatch on Broker's Transport Connector</h3><p>It is possible to disable async dispatch on a specific transport connector via the <strong><code>disableAsyncDispatch</code></strong> property. Once disabled for this transport, it cannot be enabled by individual clients.</p><structured-macro ac:macro-id="c0d99739-d154-47e1-b5e2-06cf41a2c071" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><transportConnector name="openwire" uri="tcp://0.0.0.0:61616" disableAsyncDispatch="true"/>
+</plain-text-body></structured-macro><p> </p><p> </p><p> </p></div>
diff --git a/consumer-features.xml b/consumer-features.xml
index 2747bc7..0a963a9 100644
--- a/consumer-features.xml
+++ b/consumer-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="consumer-dispatch-async.xml">Consumer Dispatch Async</a></li><li><a shape="rect" href="consumer-priority.xml">Consumer Priority</a></li><li><a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a></li><li><a shape="rect" href="manage-durable-subscribers.xml">Manage Durable Subscribers</a></li><li><a shape="rect" href="message-groups.xml">Message Groups</a></li><li><a shape="rect" href="redelivery-policy.xml">Redelivery Policy</a></li><li><a shape="rect" href="retroactive-consumer.xml">Retroactive Consumer</a></li><li><a shape="rect" href="selectors.xml">Selectors</a></li><li><a shape="rect" href="slow-consumer-handling.xml">Slow Consumer Handling</a></li><li><a shape="rect" href="subscription-recovery-policy.xml">Subscription Recovery Policy</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="2f85a176-f68a-4245-977e-4dcc32605717" ac:name="children" ac:schema-version="1"><parameter ac:name="">all</parameter></structured-macro></div>
diff --git a/consumer-priority.xml b/consumer-priority.xml
index 23e5c3c..5898aec 100644
--- a/consumer-priority.xml
+++ b/consumer-priority.xml
@@ -1,6 +1,4 @@
-<div class="wiki-content maincontent"><h3 id="ConsumerPriority-Background">Background</h3><p>As well as having a pluggable dispatch policy e.g. round robin, ActiveMQ also supports consumer priorities. This allows us to weight consumers to optimize network hops. For example, you typically want a broker to send messages to regular JMS consumers rather than to other brokers; there's no need to make unnecessary broker-to-broker hops if there are available consumers.</p><h3 id="ConsumerPriority-Example">Example</h3><p>The priority for a consumer is set using <a shape="rect" href="destination-options.xml">Destination Options</a> as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[queue = new ActiveMQQueue("TEST.QUEUE?consumer.priority=10");
+<div class="wiki-content maincontent"><h3>Background</h3><p>As well as having a pluggable dispatch policy e.g. round robin, ActiveMQ also supports consumer priorities. This allows us to weight consumers to optimize network hops. For example, you typically want a broker to send messages to regular JMS consumers rather than to other brokers; there's no need to make unnecessary broker-to-broker hops if there are available consumers.</p><h3>Example</h3><p>The priority for a consumer is set using <link><page ri:content-title="Destination Options"></page></link> as follows:</p><structured-macro ac:macro-id="2191e679-8788-42a2-9961-a7799dc2a7e2" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>queue = new ActiveMQQueue("TEST.QUEUE?consumer.priority=10");
consumer = session.createConsumer(queue);
-]]></script>
-</div></div><p>The range of priority values is: <strong><code>0</code></strong> to <strong><code>127</code></strong>. The highest priority is <strong><code>127</code></strong>. The default priority is <strong><code>0</code></strong>.</p><p>The broker orders a queue's consumers according to their priorities, dispatching messages to the highest priority consumers first. Once a particular consumer's prefetch buffer is full the broker will start dispatching messages to the consumer with the next lowest priority whose prefetch buffer is not full.</p></div>
+</plain-text-body></structured-macro><p>The range of priority values is: <strong><code>0</code></strong> to <strong><code>127</code></strong>. The highest priority is <strong><code>127</code></strong>. The default priority is <strong><code>0</code></strong>.</p><p>The broker orders a queue's consumers according to their priorities, dispatching messages to the highest priority consumers first. Once a particular consumer's prefetch buffer is full the broker will start dispatching messages to the consumer with the next lowest priority whose prefetch buffer is not full.</p></div>
diff --git a/containers.xml b/containers.xml
index 79c96e7..ce61a36 100644
--- a/containers.xml
+++ b/containers.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>This page lists the various containers that Apache ActiveMQ works inside</p>
-<ul class="childpages-macro"><li><a shape="rect" href="axis-and-cxf-support.xml">Axis and CXF Support</a></li><li><a shape="rect" href="blazeds.xml">BlazeDS</a></li><li><a shape="rect" href="geronimo.xml">Geronimo</a></li><li><a shape="rect" href="integrating-apache-activemq-with-glassfish.xml">Integrating Apache ActiveMQ with Glassfish</a></li><li><a shape="rect" href="integrating-apache-activemq-with-jboss.xml">Integrating Apache ActiveMQ with JBoss</a></li><li><a shape="rect" href="j2ee.xml">J2EE</a></li><li><a shape="rect" href="jboss-integration.xml">JBoss Integration</a></li><li><a shape="rect" href="jca-container.xml">JCA Container</a></li><li><a shape="rect" href="jndi-support.xml">JNDI Support</a></li><li><a shape="rect" href="old-osgi-integration.xml">Old OSGi Integration</a></li><li><a shape="rect" href="osgi-integration.xml">OSGi Integration</a></li><li><a shape="rect" href="resource-adapter.xml">Resource Adapter</a></li><li><a shape="rect" href="sjsas-with-genericjmsra.xml">SJSAS with GenericJMSRA</a></li><li><a shape="rect" href="spring-support.xml">Spring Support</a></li><li><a shape="rect" href="sun-jndi.xml">Sun JNDI</a></li><li><a shape="rect" href="tomcat.xml">Tomcat</a></li><li><a shape="rect" href="weblogic-integration.xml">WebLogic Integration</a></li><li><a shape="rect" href="zos.xml">zOS</a></li></ul></div>
+<structured-macro ac:macro-id="8cb45622-a2f2-4d5d-b847-53c07d4def3e" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/contributing.xml b/contributing.xml
index 49575e4..13587c1 100644
--- a/contributing.xml
+++ b/contributing.xml
@@ -1,15 +1,7 @@
-<div class="wiki-content maincontent"><p>There are many ways you can help make ActiveMQ a better piece of software - please dive in and help!</p><p>Try surf the documentation - if somethings confusing or not clear, let us know. Download the code & try it out and see what you think. Browse the source code. Got an itch to scratch, want to tune some operation or add some feature?</p><p>Want to do some hacking on ActiveMQ? Try surfing to our <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/AMQ">issue tracker</a> for open issues or features that need to be implemented, take ownership of an issue and try fix it.</p><h2 id="Contributing-Gettingintouch">Getting in touch</h2><p>There are various ways of communicating with the ActiveMQ community.</p><ul class="alternate"><li>join us on the <a shape="rect" href="discussion-forums.xml">Discussion Forums</a> or subscribe to the <a shape="rect" href="mailing-lists.xml">Mailing Lists</a> and take part in any conversations</li><li><p>pop by on <span>in <a shape="rect" href="irc.xml">irc</a> and say hi</span></p></li><li>add some comments to the <a shape="rect" href="navigation.xml">wiki</a></li></ul><h2 id="Contributing-Ifyoufindabugorproblem">If you find a bug or problem</h2><p>Please raise a new issue in our <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ">issue tracker</a></p><p>If you can create a JUnit test case then your issue is more likely to be resolved quicker.<br clear="none"> e.g. take a look at some of the existing <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tree;f=activemq-unit-tests/src/test;h=185a655c5200ed30fd2964bc236c18c5bde534c4;hb=refs/heads/master">unit tests cases</a></p><p>Then we can add your issue to the test suite and then we'll know when its really fixed and we can ensure that the problem <strong>stays fixed</strong> in future releases.</p><h2 id="Contributing-Ifyouwanttohelpoutwiththedocumentation">If you want to help out with the documentation</h2><p>If you want to contribute to the ActiveMQ documentation you should first subscribe our <a shape="rect" class="external-link" href="mailto:dev-subscribe@activemq.apache.org" rel="nofollow">dev@</a> where ActiveMQ developers interact with each other. If you want edit rights on the ActiveMQ site, create an account in the <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ">ActiveMQ wiki</a> and fill in and submit an ICLA to the ASF (see the <a shape="rect" href="becoming-a-committer.xml">Committer Guide</a>). Then ask on the dev@ list to be granted edit rights and an admin will do so fairly quickly. If you want to just contribute the content, please submit the content on the dev@ list or create an issue and attach it there. <strong>All</strong> contributions are highly appreciated.</p><h2 id="Contributing-Workingonthecode">Working on the code</h2><p>Grab the <a shape="rect" href="source.xml">Source</a> from git</p><p>Build the project.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=128M"
+<div class="wiki-content maincontent"><p>There are many ways you can help make ActiveMQ a better piece of software - please dive in and help!</p><p>Try surf the documentation - if somethings confusing or not clear, let us know. Download the code & try it out and see what you think. Browse the source code. Got an itch to scratch, want to tune some operation or add some feature?</p><p>Want to do some hacking on ActiveMQ? Try surfing to our <a shape="rect" href="http://issues.apache.org/jira/browse/AMQ">issue tracker</a> for open issues or features that need to be implemented, take ownership of an issue and try fix it.</p><h2>Getting in touch</h2><p>There are various ways of communicating with the ActiveMQ community.</p><ul class="alternate"><li>join us on the <link><page ri:content-title="Discussion Forums"></page></link> or subscribe to the <link><page ri:content-title="Mailing Lists"></page></link> and take part in any conversations</li><li><p>pop by on <span>in <link><page ri:content-title="IRC"></page><plain-text-link-body>irc</plain-text-link-body></link> and say hi</span></p></li><li>add some comments to the <link><page ri:content-title="Navigation"></page><plain-text-link-body>wiki</plain-text-link-body></link></li></ul><h2>If you find a bug or problem</h2><p>Please raise a new issue in our <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ">issue tracker</a></p><p>If you can create a JUnit test case then your issue is more likely to be resolved quicker.<br clear="none"> e.g. take a look at some of the existing <a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tree;f=activemq-unit-tests/src/test;h=185a655c5200ed30fd2964bc236c18c5bde534c4;hb=refs/heads/master">unit tests cases</a></p><p>Then we can add your issue to the test suite and then we'll know when its really fixed and we can ensure that the problem <strong>stays fixed</strong> in future releases.</p><h2>If you want to help out with the documentation</h2><p>If you want to contribute to the ActiveMQ documentation you should first subscribe our <a shape="rect" href="mailto:dev-subscribe@activemq.apache.org">dev@</a> where ActiveMQ developers interact with each other. If you want edit rights on the ActiveMQ site, create an account in the <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ">ActiveMQ wiki</a> and fill in and submit an ICLA to the ASF (see the <link><page ri:content-title="Becoming a committer"></page><plain-text-link-body>Committer Guide</plain-text-link-body></link>). Then ask on the dev@ list to be granted edit rights and an admin will do so fairly quickly. If you want to just contribute the content, please submit the content on the dev@ list or create an issue and attach it there. <strong>All</strong> contributions are highly appreciated.</p><h2>Working on the code</h2><p>Grab the <link><page ri:content-title="Source"></page></link> from git</p><p>Build the project.</p><structured-macro ac:macro-id="25d641b3-f919-4efd-a2ce-8623d0c25cc4" ac:name="code" ac:schema-version="1"><plain-text-body>export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=128M"
mvn -Dtest=false install
-]]></script>
-</div></div><p>PS: You might need to build multiple times (if you get a build error) because sometimes maven fails to download all the files.</p><p>Create a project in your IDE. e.g. if you are using Eclipse the following should do the trick.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn eclipse:eclipse
-]]></script>
-</div></div><p>Then import the projects into your workspace.</p><h2 id="Contributing-Creatingpatches">Creating patches</h2><p>We gladly accept patches if you can find ways to improve, tune or fix ActiveMQ in some way.</p><p>Most IDEs can create nice patches now very easily. e.g. in Eclipse just right click on a file/directory and select Team -> Create Patch. Then just save the patch as a file and then submit it. (You may have to click on Team -> Share... first to enable the Subversion options).</p><p>If you're a command line person try the following to create the patch</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[diff -u Main.java.orig Main.java >> patchfile.txt
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[git diff Main.java >> patchfile.txt
-]]></script>
-</div></div><h2 id="Contributing-Submittingpatches">Submitting patches</h2><p>The easiest way to submit a patch is to create a new JIRA issue, attach the patch and tick the ASF license grant check box, tick the Patch Attached button on the issue then fire off an email to the <a shape="rect" href="mailing-lists.xml">Mailing Lists</a> or <a shape="rect" href="discussion-forums.xml">Discussion Forums</a>.</p><h2 id="Contributing-Becomingacommmitter">Becoming a commmitter</h2><p>Once you've got involved as above, we may well invite you to be a committer. See <a shape="rect" href="becoming-a-committer.xml">Becoming a committer</a> for more details.</p><h2 id="Contributing-Usingtheissuetracker">Using the issue tracker</h2><p>Before you can raise an issue in the issue tracker you need to register with it. This is quick & painless.</p><p>If you want to have a go at fixing an issue you need to be in the list of activemq-developers on the issue tracker. To join the group, please mail the <a shape="rect" class="external-link" href="mailto:dev@activemq.apache.org" rel="nofollow">dev@activemq.apache.org</a> mail list with the email address you used to register with the issue tracker and we'll add you to the group.</p><p>Why not dive in the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ">issue tracker</a>, and try tackle some of our outstanding issues?</p><h2 id="Contributing-Becomingacommitter">Becoming a committer</h2><p>The first step is contributing to the project; if you want to take that a step forward and become a fellow committer on the project then see the <a shape="rect" href="becoming-a-committer.xml">Committer Guide</a></p></div>
+</plain-text-body></structured-macro><p>PS: You might need to build multiple times (if you get a build error) because sometimes maven fails to download all the files.</p><p>Create a project in your IDE. e.g. if you are using Eclipse the following should do the trick.</p><structured-macro ac:macro-id="e56c51bd-0335-411a-af24-ad8f058f506e" ac:name="code" ac:schema-version="1"><plain-text-body>mvn eclipse:eclipse
+</plain-text-body></structured-macro><p>Then import the projects into your workspace.</p><h2>Creating patches</h2><p>We gladly accept patches if you can find ways to improve, tune or fix ActiveMQ in some way.</p><p>Most IDEs can create nice patches now very easily. e.g. in Eclipse just right click on a file/directory and select Team -> Create Patch. Then just save the patch as a file and then submit it. (You may have to click on Team -> Share... first to enable the Subversion options).</p><p>If you're a command line person try the following to create the patch</p><structured-macro ac:macro-id="2d0a96df-60e0-465e-9fd4-f4ad65c58016" ac:name="code" ac:schema-version="1"><plain-text-body>diff -u Main.java.orig Main.java >> patchfile.txt
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="c70274da-13ad-4f5e-9cd5-b777ce4af0d0" ac:name="code" ac:schema-version="1"><plain-text-body>git diff Main.java >> patchfile.txt
+</plain-text-body></structured-macro><h2>Submitting patches</h2><p>The easiest way to submit a patch is to create a new JIRA issue, attach the patch and tick the ASF license grant check box, tick the Patch Attached button on the issue then fire off an email to the <link><page ri:content-title="Mailing Lists"></page></link> or <link><page ri:content-title="Discussion Forums"></page></link>.</p><h2>Becoming a commmitter</h2><p>Once you've got involved as above, we may well invite you to be a committer. See <link><page ri:content-title="Becoming a committer"></page></link> for more details.</p><h2>Using the issue tracker</h2><p>Before you can raise an issue in the issue tracker you need to register with it. This is quick & painless.</p><p>If you want to have a go at fixing an issue you need to be in the list of activemq-developers on the issue tracker. To join the group, please mail the <a shape="rect" href="mailto:dev@activemq.apache.org">dev@activemq.apache.org</a> mail list with the email address you used to register with the issue tracker and we'll add you to the group.</p><p>Why not dive in the <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ">issue tracker</a>, and try tackle some of our outstanding issues?</p><h2>Becoming a committer</h2><p>The first step is contributing to the project; if you want to take that a step forward and become a fellow committer on the project then see the <link><page ri:content-title="Becoming a committer"></page><plain-text-link-body>Committer Guide</plain-text-link-body></link></p></div>
diff --git a/could-not-find-packetreader-for-packet-type-unknown-packet-type.xml b/could-not-find-packetreader-for-packet-type-unknown-packet-type.xml
index f078dae..b25bfc8 100644
--- a/could-not-find-packetreader-for-packet-type-unknown-packet-type.xml
+++ b/could-not-find-packetreader-for-packet-type-unknown-packet-type.xml
@@ -1,12 +1,10 @@
-<div class="wiki-content maincontent"><h3 id="CouldnotfindPacketReaderforpackettype-UNKNOWNPACKETTYPE-Error">Error</h3>
+<div class="wiki-content maincontent"><h3>Error</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d1a91181-524f-47f6-9389-3bb5a7ef5e6c" ac:name="code" ac:schema-version="1"><plain-text-body>
Could not find PacketReader for packet type: UNKNOWN PACKET TYPE: -102
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="CouldnotfindPacketReaderforpackettype-UNKNOWNPACKETTYPE-Reason">Reason</h3>
+<h3>Reason</h3>
<p>You are probably using different versions of ActiveMQ jars on the client and the broker. Try using the same jars on each node and the problem should go away.</p>
diff --git a/cross-language-clients.xml b/cross-language-clients.xml
index 4ace01e..311eef4 100644
--- a/cross-language-clients.xml
+++ b/cross-language-clients.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Apache ActiveMQ is a message broker written in Java with JMS, <a shape="rect" href="rest.xml">REST</a> and <a shape="rect" href="websockets.xml">WebSocket</a> interfaces, however it supports protocols like <a shape="rect" href="amqp.xml">AMQP</a>, <a shape="rect" href="mqtt.xml">MQTT</a>, <a shape="rect" href="openwire.xml">OpenWire</a> and <a shape="rect" href="stomp.xml">STOMP</a> that can be used by applications in different languages.</p><h2 id="CrossLanguageClients-Libraries">Libraries</h2><ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/">.NET</a></li><li><a shape="rect" class="external-link" href="http://docs.codehaus.org/display/STOMP/C" rel="nofollow">C</a><span> (defunct)</span></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/cms/">C++</a></li><li><a shape="rect" class="external-link" href="https://github.com/igb/Erlang-STOMP-Client" rel="nofollow">Erlang</a></li><li><a shape="rect" class="external-link" href="https://github.com/go-stomp/stomp" rel="nofollow">Go</a></li><li><a shape="rect" class="external-link" href="https://github.com/toschoo/mom" rel="nofollow">Haskell</a></li><li><a shape="rect" class="external-link" href="https://code.google.com/p/hxstomp" rel="nofollow">Haxe</a> (defunct)</li><li><a shape="rect" class="external-link" href="https://github.com/fribeiro1/jekpro-activemq-library" rel="nofollow">Jekejeke Prolog</a></li><li><a shape="rect" class="external-link" href="https://github.com/fribeiro1/ActiveMQ-Extension" rel="nofollow">NetLogo</a></li><li><a shape="rect" class="external-link" href="https://github.com/gdaws/node-stomp" rel="nofollow">Node.js</a></li><li><a shape="rect" class="external-link" href="http://search.cpan.org/%7Elcons/Net-STOMP-Client/" rel="nofollow">Perl 5</a></li><li><a shape="rect" class="external-link" href="https://github.com/hww3/pike_modules-public_protocols_stomp" rel="nofollow">Pike</a></li><li><a shape="rect" class="external-link" href="https://github.com/jasonrbriggs/stomp.py" rel="nofollow">Python</a></li><li><a shape="rect" class="external-link" href="https://github.com/tonyg/racket-stomp" rel="nofollow">Racket</a></li><li><a shape="rect" class="external-link" href="https://github.com/kookster/activemessaging" rel="nofollow">Ruby on Rails</a></li><li><a shape="rect" class="external-link" href="https://github.com/siemens/tstomp" rel="nofollow">Tcl/Tk</a></li></ul><h2 id="CrossLanguageClients-CodeSamples">Code Samples</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Language</th><th colspan="1" rowspan="1" class="confluenceTh">Variant</th><th colspan="1" rowspan="1" class="confluenceTh">Interface</th><th colspan="1" rowspan="1" class="confluenceTh">Protocol</th><th colspan="1" rowspan="1" class="confluenceTh">Links</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Awk</td><td colspan="1" rowspan="1" class="confluenceTd">Gawk</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/06/how-to-send-a-message-to-an-apache-activemq-queue-with-gawk/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/06/how-to-send-a-message-to-an-apache-activemq-topic-with-gawk/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-gawk/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-gawk/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">C/C++</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd"><span>Library</span></td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/23/how-to-send-a-message-to-an-apache-activemq-queue-with-cc/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/23/how-to-send-a-message-to-an-apache-activemq-topic-with-cc/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/23/how-to-receive-a-message-from-an-apache-activemq-queue-with-cc/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/23/how-to-receive-a-message-from-an-apache-activemq-topic-with-cc/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">COBOL</td><td colspan="1" rowspan="1" class="confluenceTd">GNU COBOL</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/15/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-cobol/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/15/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-cobol/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/17/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-cobol/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/17/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-cobol/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">COBOL</td><td colspan="1" rowspan="1" class="confluenceTd">Visual COBOL</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/12/how-to-send-a-message-to-an-apache-activemq-queue-with-visual-cobol/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/12/how-to-send-a-message-to-an-apache-activemq-topic-with-visual-cobol/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/13/how-to-receive-a-message-from-an-apache-activemq-queue-with-visual-cobol/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/13/how-to-receive-a-message-from-an-apache-activemq-topic-with-visual-cobol/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ceylon</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/28/how-to-send-a-message-to-an-apache-activemq-queue-with-ceylon/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/28/how-to-send-a-message-to-an-apache-activemq-topic-with-ceylon/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/28/how-to-receive-a-message-from-an-apache-activemq-queue-with-ceylon/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/28/how-to-receive-a-message-from-an-apache-activemq-topic-with-ceylon/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Clojure</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-clojure/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-clojure/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-clojure/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-clojure/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">D</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/02/how-to-send-a-message-to-an-apache-activemq-queue-with-d/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/02/how-to-send-a-message-to-an-apache-activemq-topic-with-d/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/03/how-to-receive-a-message-from-an-apache-activemq-queue-with-d/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/03/how-to-receive-a-message-from-an-apache-activemq-topic-with-d/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Dylan</td><td colspan="1" rowspan="1" class="confluenceTd">Open Dylan</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/02/06/how-to-send-a-message-to-an-apache-activemq-queue-with-open-dylan/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/02/06/how-to-send-a-message-to-an-apache-activemq-topic-with-open-dylan/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/02/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-open-dylan/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/02/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-open-dylan/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Efene</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/11/how-to-send-a-message-to-an-apache-activemq-queue-with-efene/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/11/how-to-send-a-message-to-an-apache-activemq-topic-with-efene/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/11/how-to-receive-a-message-from-an-apache-activemq-queue-with-efene/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/11/how-to-receive-a-message-from-an-apache-activemq-topic-with-efene/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Eiffel</td><td colspan="1" rowspan="1" class="confluenceTd">EiffelStudio</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/24/how-to-send-a-message-to-an-apache-activemq-queue-with-eiffelstudio/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/24/how-to-send-a-message-to-an-apache-activemq-topic-with-eiffelstudio/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/24/how-to-receive-a-message-from-an-apache-activemq-queue-with-eiffelstudio/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/24/how-to-receive-a-message-from-an-apache-activemq-queue-with-eiffelstudio/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Eiffel</td><td colspan="1" rowspan="1" class="confluenceTd">GNU Eiffel</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/25/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-eiffel/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/25/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-eiffel/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/25/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-eiffel/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/25/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-eiffel/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Elixir</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/09/how-to-send-a-message-to-an-apache-activemq-queue-with-elixir/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/09/how-to-send-a-message-to-an-apache-activemq-topic-with-elixir/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/09/how-to-receive-a-message-from-an-apache-activemq-queue-with-elixir/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/09/how-to-receive-a-message-from-an-apache-activemq-topic-with-elixir/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Erlang</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/06/how-to-send-a-message-to-an-apache-activemq-queue-with-erlang/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/06/how-to-send-a-message-to-an-apache-activemq-topic-with-erlang/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/07/how-to-receive-a-message-from-an-apache-activemq-queue-with-erlang/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/07/how-to-receive-a-message-from-an-apache-activemq-topic-with-erlang/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Factor</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/13/how-to-send-a-message-to-an-apache-activemq-queue-with-factor/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/13/how-to-send-a-message-to-an-apache-activemq-topic-with-factor/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/13/how-to-receive-a-message-from-an-apache-activemq-queue-with-factor/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/13/how-to-receive-a-message-from-an-apache-activemq-topic-with-factor/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Fantom</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/11/how-to-send-a-message-to-an-apache-activemq-queue-with-fantom/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/11/how-to-send-a-message-to-an-apache-activemq-topic-with-fantom/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/11/how-to-receive-a-message-from-an-apache-activemq-queue-with-fantom/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/11/how-to-receive-a-message-from-an-apache-activemq-topic-with-fantom/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Frege</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/06/how-to-send-a-message-to-an-apache-activemq-queue-with-frege/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/06/how-to-send-a-message-to-an-apache-activemq-topic-with-frege/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-frege/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-frege/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Go</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/16/how-to-send-a-message-to-an-apache-activemq-queue-with-go/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/16/how-to-send-a-message-to-an-apache-activemq-topic-with-go/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/16/how-to-receive-a-message-from-an-apache-activemq-queue-with-go/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/16/how-to-receive-a-message-from-an-apache-activemq-topic-with-go/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Golo</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/10/how-to-send-a-message-to-an-apache-activemq-queue-with-golo/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/10/how-to-send-a-message-to-an-apache-activemq-topic-with-golo/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-golo/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-golo/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Gosu</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-gosu/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-gosu/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-gosu/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-gosu/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Groovy</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/01/how-to-send-a-message-to-an-apache-activemq-queue-with-groovy/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/01/how-to-send-a-message-to-an-apache-activemq-topic-with-groovy/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/01/how-to-receive-a-message-from-an-apache-activemq-queue-with-groovy/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/01/how-to-receive-a-message-from-an-apache-activemq-topic-with-groovy/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Haxe</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/12/how-to-send-a-message-to-an-apache-activemq-queue-with-haxe/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/12/how-to-send-a-message-to-an-apache-activemq-topic-with-haxe/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/12/how-to-receive-a-message-from-an-apache-activemq-queue-with-haxe/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/12/how-to-receive-a-message-from-an-apache-activemq-topic-with-haxe/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Haskell</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/14/how-to-send-a-message-to-an-apache-activemq-queue-with-haskell/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/14/how-to-send-a-message-to-an-apache-activemq-topic-with-haskell/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/14/how-to-receive-a-message-from-an-apache-activemq-queue-with-haskell/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/14/how-to-receive-a-message-from-an-apache-activemq-topic-with-haskell/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Interfix</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/12/how-to-send-a-message-to-an-apache-activemq-queue-with-interfix/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/12/how-to-send-a-message-to-an-apache-activemq-topic-with-interfix/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/12/how-to-receive-a-message-from-an-apache-activemq-queue-with-interfix/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/12/how-to-receive-a-message-from-an-apache-activemq-topic-with-interfix/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ioke</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/10/how-to-send-a-message-to-an-apache-activemq-queue-with-ioke/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/10/how-to-send-a-message-to-an-apache-activemq-topic-with-ioke/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-ioke/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-ioke/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Java</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd"><span>JMS</span></td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/19/how-to-send-a-message-to-an-apache-activemq-queue-with-java/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/19/how-to-send-a-message-to-an-apache-activemq-topic-with-java/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-java/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-java/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Java</td><td colspan="1" rowspan="1" class="confluenceTd">Apache Camel</td><td colspan="1" rowspan="1" class="confluenceTd"><span>JMS</span></td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/21/how-to-send-a-message-to-an-apache-activemq-queue-with-apache-camel/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/21/how-to-send-a-message-to-an-apache-activemq-topic-with-apache-camel/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/21/how-to-receive-a-message-from-an-apache-activemq-queue-with-apache-camel/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/21/how-to-receive-a-message-from-an-apache-activemq-topic-with-apache-camel/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Java</td><td colspan="1" rowspan="1" class="confluenceTd">JAX-RS</td><td colspan="1" rowspan="1" class="confluenceTd">REST</td><td colspan="1" rowspan="1" class="confluenceTd">REST</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/07/how-to-send-a-message-to-an-apache-activemq-queue-with-jax-rs/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/07/how-to-send-a-message-to-an-apache-activemq-topic-with-jax-rs/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/07/how-to-receive-a-message-from-an-apache-activemq-queue-with-jax-rs/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/11/07/how-to-receive-a-message-from-an-apache-activemq-topic-with-jax-rs/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Java</td><td colspan="1" rowspan="1" class="confluenceTd">Java API for WebSocket</td><td colspan="1" rowspan="1" class="confluenceTd">WebSocket</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/23/how-to-send-a-message-to-an-apache-activemq-queue-with-the-java-api-for-websocket/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/23/how-to-send-a-message-to-an-apache-activemq-topic-with-the-java-api-for-websocket/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/23/how-to-receive-a-message-from-an-apache-activemq-queue-with-the-java-api-for-websocket/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/23/how-to-receive-a-message-from-an-apache-activemq-topic-with-the-java-api-for-websocket/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">JavaScript</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">WebSocket</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/02/02/how-to-send-a-message-to-an-apache-activemq-queue-with-javascript/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/02/02/how-to-send-a-message-to-an-apache-activemq-topic-with-javascript/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/02/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-javascript/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/02/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-javascript/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">JavaScript</td><td colspan="1" rowspan="1" class="confluenceTd">DynJS</td><td colspan="1" rowspan="1" class="confluenceTd"><span>JMS</span></td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/02/how-to-send-a-message-to-an-apache-activemq-queue-with-dynjs/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/02/how-to-send-a-message-to-an-apache-activemq-topic-with-dynjs/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-dynjs/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-dynjs/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">JavaScript</td><td colspan="1" rowspan="1" class="confluenceTd">Rhino</td><td colspan="1" rowspan="1" class="confluenceTd"><span>JMS</span></td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-rhino/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-rhino/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-rhino/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-rhino/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">JavaScript</td><td colspan="1" rowspan="1" class="confluenceTd">Nashorn</td><td colspan="1" rowspan="1" class="confluenceTd"><span>JMS</span></td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-nashorn/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-nashorn/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-nashorn/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-nashorn/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">JavaScript</td><td colspan="1" rowspan="1" class="confluenceTd">Node.js</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/03/13/how-to-send-a-message-to-an-apache-activemq-queue-with-node-js/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/03/13/how-to-send-a-message-to-an-apache-activemq-topic-with-node-js/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/03/13/how-to-receive-a-message-from-an-apache-activemq-queue-with-node-js/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/03/13/how-to-receive-a-message-from-an-apache-activemq-topic-with-node-js/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">JudoScript</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/10/how-to-send-a-message-to-an-apache-activemq-queue-with-judoscript/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/10/how-to-send-a-message-to-an-apache-activemq-topic-with-judoscript/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-judoscript/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-judoscript/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Julia</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/02/how-to-send-a-message-to-an-apache-activemq-queue-with-julia/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/02/how-to-send-a-message-to-an-apache-activemq-topic-with-julia/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-julia/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2016/01/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-julia/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Kotlin</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/10/how-to-send-a-message-to-an-apache-activemq-queue-with-kotlin/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/10/how-to-send-a-message-to-an-apache-activemq-topic-with-kotlin/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-kotlin/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-kotlin/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">ABCL</td><td colspan="1" rowspan="1" class="confluenceTd"><span>JMS</span></td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/02/how-to-send-a-message-to-an-apache-activemq-queue-with-abcl/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/02/how-to-send-a-message-to-an-apache-activemq-topic-with-abcl/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-abcl/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-abcl/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">Allegro CL</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/05/how-to-send-a-message-to-an-apache-activemq-queue-with-allegro-cl/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/05/how-to-send-a-message-to-an-apache-activemq-topic-with-allegro-cl/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/05/how-to-receive-a-message-from-an-apache-activemq-queue-with-allegro-cl/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/05/how-to-receive-a-message-from-an-apache-activemq-topic-with-allegro-cl/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">Bigloo</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/02/how-to-send-a-message-to-an-apache-activemq-queue-with-bigloo/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/02/how-to-send-a-message-to-an-apache-activemq-topic-with-bigloo/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-bigloo/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-bigloo/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">GNU CLISP</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/17/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-clisp/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/17/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-clisp/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/17/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-clisp/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/17/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-clisp/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">JScheme</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/30/how-to-send-a-message-to-an-apache-activemq-queue-with-jscheme/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/30/how-to-send-a-message-to-an-apache-activemq-topic-with-jscheme/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-jscheme/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-jscheme/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">Joxa</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/11/how-to-send-a-message-to-an-apache-activemq-queue-with-joxa/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/11/how-to-send-a-message-to-an-apache-activemq-topic-with-joxa/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/11/how-to-receive-a-message-from-an-apache-activemq-queue-with-joxa/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/11/how-to-receive-a-message-from-an-apache-activemq-topic-with-joxa/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">Kawa</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/17/how-to-send-a-message-to-an-apache-activemq-queue-with-kawa/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/17/how-to-send-a-message-to-an-apache-activemq-topic-with-kawa/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/17/how-to-receive-a-message-from-an-apache-activemq-queue-with-kawa/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/17/how-to-receive-a-message-from-an-apache-activemq-topic-with-kawa/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">LFE</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/11/how-to-send-a-message-to-an-apache-activemq-queue-with-lfe/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/11/how-to-send-a-message-to-an-apache-activemq-topic-with-lfe/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/11/how-to-receive-a-message-from-an-apache-activemq-queue-with-lfe/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/11/how-to-receive-a-message-from-an-apache-activemq-topic-with-lfe/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">MIT/GNU Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/24/how-to-send-a-message-to-an-apache-activemq-queue-with-mitgnu-scheme/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/24/how-to-send-a-message-to-an-apache-activemq-topic-with-mitgnu-scheme/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/25/how-to-receive-a-message-from-an-apache-activemq-queue-with-mitgnu-scheme/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/25/how-to-receive-a-message-from-an-apache-activemq-topic-with-mitgnu-scheme/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">Racket</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/29/how-to-send-a-message-to-an-apache-activemq-queue-with-racket/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/29/how-to-send-a-message-to-an-apache-activemq-topic-with-racket/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/29/how-to-receive-a-message-from-an-apache-activemq-queue-with-racket/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/29/how-to-receive-a-message-from-an-apache-activemq-topic-with-racket/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lisp/Scheme</td><td colspan="1" rowspan="1" class="confluenceTd">SISC</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/06/how-to-send-a-message-to-an-apache-activemq-queue-with-sisc/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/06/how-to-send-a-message-to-an-apache-activemq-topic-with-sisc/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-sisc/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/04/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-sisc/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Logo</td><td colspan="1" rowspan="1" class="confluenceTd">NetLogo</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/06/how-to-send-a-message-to-an-apache-activemq-queue-with-netlogo/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/06/how-to-send-a-message-to-an-apache-activemq-topic-with-netlogo/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-netlogo/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/12/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-netlogo/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lua</td><td colspan="1" rowspan="1" class="confluenceTd">Lua</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/13/how-to-send-a-message-to-an-apache-activemq-queue-with-lua/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/13/how-to-send-a-message-to-an-apache-activemq-topic-with-lua/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/13/how-to-receive-a-message-from-an-apache-activemq-queue-with-lua/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/13/how-to-receive-a-message-from-an-apache-activemq-topic-with-lua/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Lua</td><td colspan="1" rowspan="1" class="confluenceTd">Luaj</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/25/how-to-send-a-message-to-an-apache-activemq-queue-with-luaj/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/25/how-to-send-a-message-to-an-apache-activemq-topic-with-luaj/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/25/how-to-receive-a-message-from-an-apache-activemq-queue-with-luaj/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/25/how-to-receive-a-message-from-an-apache-activemq-topic-with-luaj/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">ML</td><td colspan="1" rowspan="1" class="confluenceTd">OCaml</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/02/21/how-to-send-a-message-to-an-apache-activemq-queue-with-ocaml/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/02/22/how-to-send-a-message-to-an-apache-activemq-topic-with-ocaml/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/02/22/how-to-receive-a-message-from-an-apache-activemq-queue-with-ocaml/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/02/22/how-to-receive-a-message-from-an-apache-activemq-topic-with-ocaml/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">ML</td><td colspan="1" rowspan="1" class="confluenceTd">OCaml-Java</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/02/15/how-to-send-a-message-to-an-apache-activemq-queue-with-ocaml-java/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/02/15/how-to-send-a-message-to-an-apache-activemq-topic-with-ocaml-java/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/02/15/how-to-receive-a-message-from-an-apache-activemq-queue-with-ocaml-java/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/02/15/how-to-receive-a-message-from-an-apache-activemq-topic-with-ocaml-java/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Mirah</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/30/how-to-send-a-message-to-an-apache-activemq-queue-with-mirah/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/30/how-to-send-a-message-to-an-apache-activemq-topic-with-mirah/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-mirah/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-mirah/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Perl</td><td colspan="1" rowspan="1" class="confluenceTd"><span>Perl 5</span></td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/08/how-to-send-a-message-to-an-apache-activemq-queue-with-perl-5/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/08/how-to-send-a-message-to-an-apache-activemq-topic-with-perl-5/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/08/how-to-receive-a-message-from-an-apache-activemq-queue-with-perl-5/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/08/how-to-receive-a-message-from-an-apache-activemq-topic-with-perl-5/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Pike</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/16/how-to-send-a-message-to-an-apache-activemq-queue-with-pike/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/16/how-to-send-a-message-to-an-apache-activemq-topic-with-pike/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/16/how-to-receive-a-message-from-an-apache-activemq-queue-with-pike/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/16/how-to-receive-a-message-from-an-apache-activemq-topic-with-pike/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Prolog</td><td colspan="1" rowspan="1" class="confluenceTd">JIProlog</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/14/how-to-send-a-message-to-an-apache-activemq-queue-with-jiprolog/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/14/how-to-send-a-message-to-an-apache-activemq-topic-with-jiprolog/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/14/how-to-receive-a-message-from-an-apache-activemq-queue-with-jiprolog/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/14/how-to-receive-a-message-from-an-apache-activemq-topic-with-jiprolog/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Prolog</td><td colspan="1" rowspan="1" class="confluenceTd">Jekejeke Prolog</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/26/how-to-send-a-message-to-an-apache-activemq-queue-with-jekejeke-prolog/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/26/how-to-send-a-message-to-an-apache-activemq-topic-with-jekejeke-prolog/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/26/how-to-receive-a-message-from-an-apache-activemq-queue-with-jekejeke-prolog/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/26/how-to-receive-a-message-from-an-apache-activemq-topic-with-jekejeke-prolog/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Prolog</td><td colspan="1" rowspan="1" class="confluenceTd">tuProlog</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/21/how-to-send-a-message-to-an-apache-activemq-queue-with-tuprolog/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/21/how-to-send-a-message-to-an-apache-activemq-topic-with-tuprolog/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/21/how-to-receive-a-message-from-an-apache-activemq-queue-with-tuprolog/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/21/how-to-receive-a-message-from-an-apache-activemq-topic-with-tuprolog/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Python</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/14/how-to-send-a-message-to-an-apache-activemq-queue-with-python/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/14/how-to-send-a-message-to-an-apache-activemq-topic-with-python/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/14/how-to-receive-a-message-from-an-apache-activemq-queue-with-python/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/14/how-to-receive-a-message-from-an-apache-activemq-topic-with-python/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Python</td><td colspan="1" rowspan="1" class="confluenceTd">Jython</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/30/how-to-send-a-message-to-an-apache-activemq-queue-with-jython/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/30/how-to-send-a-message-to-an-apache-activemq-topic-with-jython/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-jython/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-jython/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">R</td><td colspan="1" rowspan="1" class="confluenceTd">GNU R</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/19/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-r/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/19/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-r/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/19/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-r/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/19/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-r/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">R</td><td colspan="1" rowspan="1" class="confluenceTd">Renjin</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-renjin/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-renjin/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-renjin/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-renjin/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Rebol</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/11/28/how-to-send-a-message-to-an-apache-activemq-queue-with-rebol/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/11/28/how-to-send-a-message-to-an-apache-activemq-topic-with-rebol/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/11/28/how-to-receive-a-message-from-an-apache-activemq-queue-with-rebol/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/11/28/how-to-receive-a-message-from-an-apache-activemq-topic-with-rebol/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Rexx</td><td colspan="1" rowspan="1" class="confluenceTd">BSF4ooRexx</td><td colspan="1" rowspan="1" class="confluenceTd"><span>JMS</span></td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/21/how-to-send-a-message-to-an-apache-activemq-queue-with-bsf4oorexx/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/21/how-to-send-a-message-to-an-apache-activemq-topic-with-bsf4oorexx/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/22/how-to-receive-a-message-from-an-apache-activemq-queue-with-bsf4oorexx/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/22/how-to-receive-a-message-from-an-apache-activemq-topic-with-bsf4oorexx/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Rexx</td><td colspan="1" rowspan="1" class="confluenceTd">NetRexx</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/17/how-to-send-a-message-to-an-apache-activemq-queue-with-netrexx/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/17/how-to-send-a-message-to-an-apache-activemq-topic-with-netrexx/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/17/how-to-receive-a-message-from-an-apache-activemq-queue-with-netrexx/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/17/how-to-receive-a-message-from-an-apache-activemq-topic-with-netrexx/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Rexx</td><td colspan="1" rowspan="1" class="confluenceTd">ooRexx</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/21/how-to-send-a-message-to-an-apache-activemq-queue-with-oorexx/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/21/how-to-send-a-message-to-an-apache-activemq-topic-with-oorexx/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/21/how-to-receive-a-message-from-an-apache-activemq-queue-with-oorexx/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/21/how-to-receive-a-message-from-an-apache-activemq-topic-with-oorexx/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ruby</td><td colspan="1" rowspan="1" class="confluenceTd">None</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/02/how-to-send-a-message-to-an-apache-activemq-queue-with-ruby/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/03/how-to-send-a-message-to-an-apache-activemq-topic-with-ruby/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/03/how-to-receive-a-message-from-an-apache-activemq-queue-with-ruby/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/03/how-to-receive-a-message-from-an-apache-activemq-topic-with-ruby/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ruby</td><td colspan="1" rowspan="1" class="confluenceTd">Ruby on Rails</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/27/how-to-send-a-message-to-an-apache-activemq-queue-with-ruby-on-rails/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/27/how-to-send-a-message-to-an-apache-activemq-topic-with-ruby-on-rails/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/27/how-to-receive-a-message-from-an-apache-activemq-queue-with-ruby-on-rails/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/27/how-to-receive-a-message-from-an-apache-activemq-topic-with-ruby-on-rails/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ruby</td><td colspan="1" rowspan="1" class="confluenceTd">JRuby</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/30/how-to-send-a-message-to-an-apache-activemq-queue-with-jruby/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/30/how-to-send-a-message-to-an-apache-activemq-topic-with-jruby/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-jruby/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-jruby/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Rust</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/16/how-to-send-a-message-to-an-apache-activemq-queue-with-rust/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/16/how-to-send-a-message-to-an-apache-activemq-topic-with-rust/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/16/how-to-receive-a-message-from-an-apache-activemq-queue-with-rust/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2015/01/16/how-to-receive-a-message-from-an-apache-activemq-topic-with-rust/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Scala</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-scala/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-scala/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-scala/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-scala/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Smalltalk</td><td colspan="1" rowspan="1" class="confluenceTd">GNU Smalltalk</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/28/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-smalltalk/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/28/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-smalltalk/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/28/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-smalltalk/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/28/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-smalltalk/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Smalltalk</td><td colspan="1" rowspan="1" class="confluenceTd">Squeak</td><td colspan="1" rowspan="1" class="confluenceTd">Sockets</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/30/how-to-send-a-message-to-an-apache-activemq-queue-with-squeak/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/30/how-to-send-a-message-to-an-apache-activemq-topic-with-squeak/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-squeak/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/03/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-squeak/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Tcl</td><td colspan="1" rowspan="1" class="confluenceTd">Tcl/Tk</td><td colspan="1" rowspan="1" class="confluenceTd">Library</td><td colspan="1" rowspan="1" class="confluenceTd">STOMP</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/27/how-to-send-a-message-to-an-apache-activemq-queue-with-tcltk/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/27/how-to-send-a-message-to-an-apache-activemq-topic-with-tcltk/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/27/how-to-receive-a-message-from-an-apache-activemq-queue-with-tcltk/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/02/27/how-to-receive-a-message-from-an-apache-activemq-topic-with-tcltk/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Tcl</td><td colspan="1" rowspan="1" class="confluenceTd">Tcl/Java</td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/24/how-to-send-a-message-to-an-apache-activemq-queue-with-tcljava/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/24/how-to-send-a-message-to-an-apache-activemq-topic-with-tcljava/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/24/how-to-receive-a-message-from-an-apache-activemq-queue-with-tcljava/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/08/24/how-to-receive-a-message-from-an-apache-activemq-topic-with-tcljava/" rel="nofollow">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Xtend</td><td colspan="1" rowspan="1" class="confluenceTd"><span>None</span></td><td colspan="1" rowspan="1" class="confluenceTd">JMS</td><td colspan="1" rowspan="1" class="confluenceTd">OpenWire</td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/01/how-to-send-a-message-to-an-apache-activemq-queue-with-xtend/" rel="nofollow">Send to Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/01/how-to-send-a-message-to-an-apache-activemq-topic-with-xtend/" rel="nofollow">Send to Topic</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/01/how-to-receive-a-message-from-an-apache-activemq-queue-with-xtend/" rel="nofollow">Receive from Queue</a></li><li><a shape="rect" class="external-link" href="https://simplesassim.wordpress.com/2014/01/01/how-to-receive-a-message-from-an-apache-activemq-topic-with-xtend/" rel="nofollow">Receive from Topic</a></li></ul></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><p>Apache ActiveMQ is a message broker written in Java with JMS, <link><page ri:content-title="REST"></page></link> and <link><page ri:content-title="WebSockets"></page><plain-text-link-body>WebSocket</plain-text-link-body></link> interfaces, however it supports protocols like <link><page ri:content-title="AMQP"></page></link>, <link><page ri:content-title="MQTT"></page></link>, <link><page ri:content-title="OpenWire"></page></link> and <link><page ri:content-title="Stomp"></page><plain-text-link-body>STOMP</plain-text-link-body></link> that can be used by applications in different languages.</p><h2>Libraries</h2><ul><li><a shape="rect" href="http://activemq.apache.org/nms/">.NET</a></li><li><a shape="rect" href="http://docs.codehaus.org/display/STOMP/C">C</a><span> (defunct)</span></li><li><a shape="rect" href="http://activemq.apache.org/cms/">C++</a></li><li><a shape="rect" href="https://github.com/igb/Erlang-STOMP-Client">Erlang</a></li><li><a shape="rect" href="https://github.com/go-stomp/stomp">Go</a></li><li><a shape="rect" href="https://github.com/toschoo/mom">Haskell</a></li><li><a shape="rect" href="https://code.google.com/p/hxstomp">Haxe</a> (defunct)</li><li><a shape="rect" href="https://github.com/fribeiro1/jekpro-activemq-library">Jekejeke Prolog</a></li><li><a shape="rect" href="https://github.com/fribeiro1/ActiveMQ-Extension">NetLogo</a></li><li><a shape="rect" href="https://github.com/gdaws/node-stomp">Node.js</a></li><li><a shape="rect" href="http://search.cpan.org/%7Elcons/Net-STOMP-Client/">Perl 5</a></li><li><a shape="rect" href="https://github.com/hww3/pike_modules-public_protocols_stomp">Pike</a></li><li><a shape="rect" href="https://github.com/jasonrbriggs/stomp.py">Python</a></li><li><a shape="rect" href="https://github.com/tonyg/racket-stomp">Racket</a></li><li><a shape="rect" href="https://github.com/kookster/activemessaging">Ruby on Rails</a></li><li><a shape="rect" href="https://github.com/siemens/tstomp">Tcl/Tk</a></li></ul><h2>Code Samples</h2><table><tbody><tr><th colspan="1" rowspan="1">Language</th><th colspan="1" rowspan="1">Variant</th><th colspan="1" rowspan="1">Interface</th><th colspan="1" rowspan="1">Protocol</th><th colspan="1" rowspan="1">Links</th></tr><tr><td colspan="1" rowspan="1">Awk</td><td colspan="1" rowspan="1">Gawk</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/06/how-to-send-a-message-to-an-apache-activemq-queue-with-gawk/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/06/how-to-send-a-message-to-an-apache-activemq-topic-with-gawk/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-gawk/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-gawk/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">C/C++</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1"><span>Library</span></td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/23/how-to-send-a-message-to-an-apache-activemq-queue-with-cc/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/23/how-to-send-a-message-to-an-apache-activemq-topic-with-cc/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/23/how-to-receive-a-message-from-an-apache-activemq-queue-with-cc/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/23/how-to-receive-a-message-from-an-apache-activemq-topic-with-cc/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">COBOL</td><td colspan="1" rowspan="1">GNU COBOL</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/15/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-cobol/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/15/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-cobol/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/17/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-cobol/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/17/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-cobol/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">COBOL</td><td colspan="1" rowspan="1">Visual COBOL</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/12/how-to-send-a-message-to-an-apache-activemq-queue-with-visual-cobol/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/12/how-to-send-a-message-to-an-apache-activemq-topic-with-visual-cobol/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/13/how-to-receive-a-message-from-an-apache-activemq-queue-with-visual-cobol/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/13/how-to-receive-a-message-from-an-apache-activemq-topic-with-visual-cobol/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Ceylon</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/28/how-to-send-a-message-to-an-apache-activemq-queue-with-ceylon/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/28/how-to-send-a-message-to-an-apache-activemq-topic-with-ceylon/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/28/how-to-receive-a-message-from-an-apache-activemq-queue-with-ceylon/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/28/how-to-receive-a-message-from-an-apache-activemq-topic-with-ceylon/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Clojure</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-clojure/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-clojure/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-clojure/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-clojure/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">D</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/02/how-to-send-a-message-to-an-apache-activemq-queue-with-d/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/02/how-to-send-a-message-to-an-apache-activemq-topic-with-d/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/03/how-to-receive-a-message-from-an-apache-activemq-queue-with-d/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/03/how-to-receive-a-message-from-an-apache-activemq-topic-with-d/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Dylan</td><td colspan="1" rowspan="1">Open Dylan</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/02/06/how-to-send-a-message-to-an-apache-activemq-queue-with-open-dylan/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/02/06/how-to-send-a-message-to-an-apache-activemq-topic-with-open-dylan/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/02/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-open-dylan/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/02/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-open-dylan/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Efene</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/11/how-to-send-a-message-to-an-apache-activemq-queue-with-efene/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/11/how-to-send-a-message-to-an-apache-activemq-topic-with-efene/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/11/how-to-receive-a-message-from-an-apache-activemq-queue-with-efene/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/11/how-to-receive-a-message-from-an-apache-activemq-topic-with-efene/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Eiffel</td><td colspan="1" rowspan="1">EiffelStudio</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/24/how-to-send-a-message-to-an-apache-activemq-queue-with-eiffelstudio/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/24/how-to-send-a-message-to-an-apache-activemq-topic-with-eiffelstudio/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/24/how-to-receive-a-message-from-an-apache-activemq-queue-with-eiffelstudio/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/24/how-to-receive-a-message-from-an-apache-activemq-queue-with-eiffelstudio/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Eiffel</td><td colspan="1" rowspan="1">GNU Eiffel</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/25/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-eiffel/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/25/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-eiffel/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/25/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-eiffel/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/25/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-eiffel/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Elixir</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/09/how-to-send-a-message-to-an-apache-activemq-queue-with-elixir/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/09/how-to-send-a-message-to-an-apache-activemq-topic-with-elixir/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/09/how-to-receive-a-message-from-an-apache-activemq-queue-with-elixir/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/09/how-to-receive-a-message-from-an-apache-activemq-topic-with-elixir/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Erlang</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/06/how-to-send-a-message-to-an-apache-activemq-queue-with-erlang/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/06/how-to-send-a-message-to-an-apache-activemq-topic-with-erlang/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/07/how-to-receive-a-message-from-an-apache-activemq-queue-with-erlang/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/07/how-to-receive-a-message-from-an-apache-activemq-topic-with-erlang/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Factor</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/13/how-to-send-a-message-to-an-apache-activemq-queue-with-factor/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/13/how-to-send-a-message-to-an-apache-activemq-topic-with-factor/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/13/how-to-receive-a-message-from-an-apache-activemq-queue-with-factor/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/13/how-to-receive-a-message-from-an-apache-activemq-topic-with-factor/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Fantom</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/11/how-to-send-a-message-to-an-apache-activemq-queue-with-fantom/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/11/how-to-send-a-message-to-an-apache-activemq-topic-with-fantom/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/11/how-to-receive-a-message-from-an-apache-activemq-queue-with-fantom/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/11/how-to-receive-a-message-from-an-apache-activemq-topic-with-fantom/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Frege</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/06/how-to-send-a-message-to-an-apache-activemq-queue-with-frege/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/06/how-to-send-a-message-to-an-apache-activemq-topic-with-frege/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-frege/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-frege/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Go</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/16/how-to-send-a-message-to-an-apache-activemq-queue-with-go/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/16/how-to-send-a-message-to-an-apache-activemq-topic-with-go/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/16/how-to-receive-a-message-from-an-apache-activemq-queue-with-go/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/16/how-to-receive-a-message-from-an-apache-activemq-topic-with-go/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Golo</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/10/how-to-send-a-message-to-an-apache-activemq-queue-with-golo/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/10/how-to-send-a-message-to-an-apache-activemq-topic-with-golo/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-golo/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-golo/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Gosu</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-gosu/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-gosu/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-gosu/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-gosu/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Groovy</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/01/how-to-send-a-message-to-an-apache-activemq-queue-with-groovy/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/01/how-to-send-a-message-to-an-apache-activemq-topic-with-groovy/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/01/how-to-receive-a-message-from-an-apache-activemq-queue-with-groovy/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/01/how-to-receive-a-message-from-an-apache-activemq-topic-with-groovy/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Haxe</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/12/how-to-send-a-message-to-an-apache-activemq-queue-with-haxe/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/12/how-to-send-a-message-to-an-apache-activemq-topic-with-haxe/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/12/how-to-receive-a-message-from-an-apache-activemq-queue-with-haxe/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/12/how-to-receive-a-message-from-an-apache-activemq-topic-with-haxe/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Haskell</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/14/how-to-send-a-message-to-an-apache-activemq-queue-with-haskell/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/14/how-to-send-a-message-to-an-apache-activemq-topic-with-haskell/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/14/how-to-receive-a-message-from-an-apache-activemq-queue-with-haskell/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/14/how-to-receive-a-message-from-an-apache-activemq-topic-with-haskell/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Interfix</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/12/how-to-send-a-message-to-an-apache-activemq-queue-with-interfix/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/12/how-to-send-a-message-to-an-apache-activemq-topic-with-interfix/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/12/how-to-receive-a-message-from-an-apache-activemq-queue-with-interfix/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/12/how-to-receive-a-message-from-an-apache-activemq-topic-with-interfix/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Ioke</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/10/how-to-send-a-message-to-an-apache-activemq-queue-with-ioke/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/10/how-to-send-a-message-to-an-apache-activemq-topic-with-ioke/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-ioke/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-ioke/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Java</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1"><span>JMS</span></td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/19/how-to-send-a-message-to-an-apache-activemq-queue-with-java/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/19/how-to-send-a-message-to-an-apache-activemq-topic-with-java/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-java/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-java/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Java</td><td colspan="1" rowspan="1">Apache Camel</td><td colspan="1" rowspan="1"><span>JMS</span></td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/21/how-to-send-a-message-to-an-apache-activemq-queue-with-apache-camel/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/21/how-to-send-a-message-to-an-apache-activemq-topic-with-apache-camel/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/21/how-to-receive-a-message-from-an-apache-activemq-queue-with-apache-camel/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/21/how-to-receive-a-message-from-an-apache-activemq-topic-with-apache-camel/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Java</td><td colspan="1" rowspan="1">JAX-RS</td><td colspan="1" rowspan="1">REST</td><td colspan="1" rowspan="1">REST</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/07/how-to-send-a-message-to-an-apache-activemq-queue-with-jax-rs/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/07/how-to-send-a-message-to-an-apache-activemq-topic-with-jax-rs/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/07/how-to-receive-a-message-from-an-apache-activemq-queue-with-jax-rs/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/11/07/how-to-receive-a-message-from-an-apache-activemq-topic-with-jax-rs/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Java</td><td colspan="1" rowspan="1">Java API for WebSocket</td><td colspan="1" rowspan="1">WebSocket</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/23/how-to-send-a-message-to-an-apache-activemq-queue-with-the-java-api-for-websocket/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/23/how-to-send-a-message-to-an-apache-activemq-topic-with-the-java-api-for-websocket/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/23/how-to-receive-a-message-from-an-apache-activemq-queue-with-the-java-api-for-websocket/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/23/how-to-receive-a-message-from-an-apache-activemq-topic-with-the-java-api-for-websocket/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">JavaScript</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">WebSocket</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/02/02/how-to-send-a-message-to-an-apache-activemq-queue-with-javascript/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/02/02/how-to-send-a-message-to-an-apache-activemq-topic-with-javascript/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/02/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-javascript/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/02/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-javascript/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">JavaScript</td><td colspan="1" rowspan="1">DynJS</td><td colspan="1" rowspan="1"><span>JMS</span></td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/02/how-to-send-a-message-to-an-apache-activemq-queue-with-dynjs/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/02/how-to-send-a-message-to-an-apache-activemq-topic-with-dynjs/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-dynjs/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-dynjs/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">JavaScript</td><td colspan="1" rowspan="1">Rhino</td><td colspan="1" rowspan="1"><span>JMS</span></td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-rhino/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-rhino/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-rhino/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-rhino/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">JavaScript</td><td colspan="1" rowspan="1">Nashorn</td><td colspan="1" rowspan="1"><span>JMS</span></td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-nashorn/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-nashorn/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-nashorn/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-nashorn/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">JavaScript</td><td colspan="1" rowspan="1">Node.js</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/03/13/how-to-send-a-message-to-an-apache-activemq-queue-with-node-js/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/03/13/how-to-send-a-message-to-an-apache-activemq-topic-with-node-js/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/03/13/how-to-receive-a-message-from-an-apache-activemq-queue-with-node-js/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/03/13/how-to-receive-a-message-from-an-apache-activemq-topic-with-node-js/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">JudoScript</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/10/how-to-send-a-message-to-an-apache-activemq-queue-with-judoscript/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/10/how-to-send-a-message-to-an-apache-activemq-topic-with-judoscript/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-judoscript/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-judoscript/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Julia</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/02/how-to-send-a-message-to-an-apache-activemq-queue-with-julia/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/02/how-to-send-a-message-to-an-apache-activemq-topic-with-julia/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-julia/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2016/01/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-julia/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Kotlin</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/10/how-to-send-a-message-to-an-apache-activemq-queue-with-kotlin/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/10/how-to-send-a-message-to-an-apache-activemq-topic-with-kotlin/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/10/how-to-receive-a-message-from-an-apache-activemq-queue-with-kotlin/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/10/how-to-receive-a-message-from-an-apache-activemq-topic-with-kotlin/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">ABCL</td><td colspan="1" rowspan="1"><span>JMS</span></td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/02/how-to-send-a-message-to-an-apache-activemq-queue-with-abcl/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/02/how-to-send-a-message-to-an-apache-activemq-topic-with-abcl/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-abcl/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-abcl/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">Allegro CL</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/05/how-to-send-a-message-to-an-apache-activemq-queue-with-allegro-cl/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/05/how-to-send-a-message-to-an-apache-activemq-topic-with-allegro-cl/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/05/how-to-receive-a-message-from-an-apache-activemq-queue-with-allegro-cl/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/05/how-to-receive-a-message-from-an-apache-activemq-topic-with-allegro-cl/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">Bigloo</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/02/how-to-send-a-message-to-an-apache-activemq-queue-with-bigloo/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/02/how-to-send-a-message-to-an-apache-activemq-topic-with-bigloo/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/02/how-to-receive-a-message-from-an-apache-activemq-queue-with-bigloo/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/02/how-to-receive-a-message-from-an-apache-activemq-topic-with-bigloo/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">GNU CLISP</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/17/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-clisp/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/17/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-clisp/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/17/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-clisp/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/17/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-clisp/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">JScheme</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/30/how-to-send-a-message-to-an-apache-activemq-queue-with-jscheme/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/30/how-to-send-a-message-to-an-apache-activemq-topic-with-jscheme/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-jscheme/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-jscheme/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">Joxa</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/11/how-to-send-a-message-to-an-apache-activemq-queue-with-joxa/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/11/how-to-send-a-message-to-an-apache-activemq-topic-with-joxa/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/11/how-to-receive-a-message-from-an-apache-activemq-queue-with-joxa/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/11/how-to-receive-a-message-from-an-apache-activemq-topic-with-joxa/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">Kawa</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/17/how-to-send-a-message-to-an-apache-activemq-queue-with-kawa/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/17/how-to-send-a-message-to-an-apache-activemq-topic-with-kawa/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/17/how-to-receive-a-message-from-an-apache-activemq-queue-with-kawa/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/17/how-to-receive-a-message-from-an-apache-activemq-topic-with-kawa/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">LFE</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/11/how-to-send-a-message-to-an-apache-activemq-queue-with-lfe/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/11/how-to-send-a-message-to-an-apache-activemq-topic-with-lfe/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/11/how-to-receive-a-message-from-an-apache-activemq-queue-with-lfe/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/11/how-to-receive-a-message-from-an-apache-activemq-topic-with-lfe/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">MIT/GNU Scheme</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/24/how-to-send-a-message-to-an-apache-activemq-queue-with-mitgnu-scheme/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/24/how-to-send-a-message-to-an-apache-activemq-topic-with-mitgnu-scheme/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/25/how-to-receive-a-message-from-an-apache-activemq-queue-with-mitgnu-scheme/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/25/how-to-receive-a-message-from-an-apache-activemq-topic-with-mitgnu-scheme/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">Racket</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/29/how-to-send-a-message-to-an-apache-activemq-queue-with-racket/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/29/how-to-send-a-message-to-an-apache-activemq-topic-with-racket/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/29/how-to-receive-a-message-from-an-apache-activemq-queue-with-racket/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/29/how-to-receive-a-message-from-an-apache-activemq-topic-with-racket/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lisp/Scheme</td><td colspan="1" rowspan="1">SISC</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/06/how-to-send-a-message-to-an-apache-activemq-queue-with-sisc/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/06/how-to-send-a-message-to-an-apache-activemq-topic-with-sisc/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-sisc/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/04/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-sisc/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Logo</td><td colspan="1" rowspan="1">NetLogo</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/06/how-to-send-a-message-to-an-apache-activemq-queue-with-netlogo/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/06/how-to-send-a-message-to-an-apache-activemq-topic-with-netlogo/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/06/how-to-receive-a-message-from-an-apache-activemq-queue-with-netlogo/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/12/06/how-to-receive-a-message-from-an-apache-activemq-topic-with-netlogo/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lua</td><td colspan="1" rowspan="1">Lua</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/13/how-to-send-a-message-to-an-apache-activemq-queue-with-lua/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/13/how-to-send-a-message-to-an-apache-activemq-topic-with-lua/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/13/how-to-receive-a-message-from-an-apache-activemq-queue-with-lua/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/13/how-to-receive-a-message-from-an-apache-activemq-topic-with-lua/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Lua</td><td colspan="1" rowspan="1">Luaj</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/25/how-to-send-a-message-to-an-apache-activemq-queue-with-luaj/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/25/how-to-send-a-message-to-an-apache-activemq-topic-with-luaj/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/25/how-to-receive-a-message-from-an-apache-activemq-queue-with-luaj/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/25/how-to-receive-a-message-from-an-apache-activemq-topic-with-luaj/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">ML</td><td colspan="1" rowspan="1">OCaml</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/02/21/how-to-send-a-message-to-an-apache-activemq-queue-with-ocaml/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/02/22/how-to-send-a-message-to-an-apache-activemq-topic-with-ocaml/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/02/22/how-to-receive-a-message-from-an-apache-activemq-queue-with-ocaml/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/02/22/how-to-receive-a-message-from-an-apache-activemq-topic-with-ocaml/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">ML</td><td colspan="1" rowspan="1">OCaml-Java</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/02/15/how-to-send-a-message-to-an-apache-activemq-queue-with-ocaml-java/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/02/15/how-to-send-a-message-to-an-apache-activemq-topic-with-ocaml-java/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/02/15/how-to-receive-a-message-from-an-apache-activemq-queue-with-ocaml-java/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/02/15/how-to-receive-a-message-from-an-apache-activemq-topic-with-ocaml-java/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Mirah</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/30/how-to-send-a-message-to-an-apache-activemq-queue-with-mirah/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/30/how-to-send-a-message-to-an-apache-activemq-topic-with-mirah/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-mirah/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-mirah/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Perl</td><td colspan="1" rowspan="1"><span>Perl 5</span></td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/08/how-to-send-a-message-to-an-apache-activemq-queue-with-perl-5/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/08/how-to-send-a-message-to-an-apache-activemq-topic-with-perl-5/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/08/how-to-receive-a-message-from-an-apache-activemq-queue-with-perl-5/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/08/how-to-receive-a-message-from-an-apache-activemq-topic-with-perl-5/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Pike</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/16/how-to-send-a-message-to-an-apache-activemq-queue-with-pike/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/16/how-to-send-a-message-to-an-apache-activemq-topic-with-pike/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/16/how-to-receive-a-message-from-an-apache-activemq-queue-with-pike/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/16/how-to-receive-a-message-from-an-apache-activemq-topic-with-pike/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Prolog</td><td colspan="1" rowspan="1">JIProlog</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/14/how-to-send-a-message-to-an-apache-activemq-queue-with-jiprolog/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/14/how-to-send-a-message-to-an-apache-activemq-topic-with-jiprolog/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/14/how-to-receive-a-message-from-an-apache-activemq-queue-with-jiprolog/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/14/how-to-receive-a-message-from-an-apache-activemq-topic-with-jiprolog/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Prolog</td><td colspan="1" rowspan="1">Jekejeke Prolog</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/26/how-to-send-a-message-to-an-apache-activemq-queue-with-jekejeke-prolog/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/26/how-to-send-a-message-to-an-apache-activemq-topic-with-jekejeke-prolog/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/26/how-to-receive-a-message-from-an-apache-activemq-queue-with-jekejeke-prolog/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/26/how-to-receive-a-message-from-an-apache-activemq-topic-with-jekejeke-prolog/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Prolog</td><td colspan="1" rowspan="1">tuProlog</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/21/how-to-send-a-message-to-an-apache-activemq-queue-with-tuprolog/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/21/how-to-send-a-message-to-an-apache-activemq-topic-with-tuprolog/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/21/how-to-receive-a-message-from-an-apache-activemq-queue-with-tuprolog/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/21/how-to-receive-a-message-from-an-apache-activemq-topic-with-tuprolog/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Python</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/14/how-to-send-a-message-to-an-apache-activemq-queue-with-python/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/14/how-to-send-a-message-to-an-apache-activemq-topic-with-python/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/14/how-to-receive-a-message-from-an-apache-activemq-queue-with-python/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/14/how-to-receive-a-message-from-an-apache-activemq-topic-with-python/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Python</td><td colspan="1" rowspan="1">Jython</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/30/how-to-send-a-message-to-an-apache-activemq-queue-with-jython/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/30/how-to-send-a-message-to-an-apache-activemq-topic-with-jython/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-jython/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-jython/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">R</td><td colspan="1" rowspan="1">GNU R</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/19/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-r/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/19/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-r/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/19/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-r/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/19/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-r/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">R</td><td colspan="1" rowspan="1">Renjin</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-renjin/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-renjin/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-renjin/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-renjin/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Rebol</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/11/28/how-to-send-a-message-to-an-apache-activemq-queue-with-rebol/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/11/28/how-to-send-a-message-to-an-apache-activemq-topic-with-rebol/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/11/28/how-to-receive-a-message-from-an-apache-activemq-queue-with-rebol/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/11/28/how-to-receive-a-message-from-an-apache-activemq-topic-with-rebol/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Rexx</td><td colspan="1" rowspan="1">BSF4ooRexx</td><td colspan="1" rowspan="1"><span>JMS</span></td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/21/how-to-send-a-message-to-an-apache-activemq-queue-with-bsf4oorexx/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/21/how-to-send-a-message-to-an-apache-activemq-topic-with-bsf4oorexx/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/22/how-to-receive-a-message-from-an-apache-activemq-queue-with-bsf4oorexx/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/22/how-to-receive-a-message-from-an-apache-activemq-topic-with-bsf4oorexx/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Rexx</td><td colspan="1" rowspan="1">NetRexx</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/17/how-to-send-a-message-to-an-apache-activemq-queue-with-netrexx/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/17/how-to-send-a-message-to-an-apache-activemq-topic-with-netrexx/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/17/how-to-receive-a-message-from-an-apache-activemq-queue-with-netrexx/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/17/how-to-receive-a-message-from-an-apache-activemq-topic-with-netrexx/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Rexx</td><td colspan="1" rowspan="1">ooRexx</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/21/how-to-send-a-message-to-an-apache-activemq-queue-with-oorexx/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/21/how-to-send-a-message-to-an-apache-activemq-topic-with-oorexx/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/21/how-to-receive-a-message-from-an-apache-activemq-queue-with-oorexx/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/21/how-to-receive-a-message-from-an-apache-activemq-topic-with-oorexx/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Ruby</td><td colspan="1" rowspan="1">None</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/02/how-to-send-a-message-to-an-apache-activemq-queue-with-ruby/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/03/how-to-send-a-message-to-an-apache-activemq-topic-with-ruby/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/03/how-to-receive-a-message-from-an-apache-activemq-queue-with-ruby/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/03/how-to-receive-a-message-from-an-apache-activemq-topic-with-ruby/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Ruby</td><td colspan="1" rowspan="1">Ruby on Rails</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/27/how-to-send-a-message-to-an-apache-activemq-queue-with-ruby-on-rails/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/27/how-to-send-a-message-to-an-apache-activemq-topic-with-ruby-on-rails/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/27/how-to-receive-a-message-from-an-apache-activemq-queue-with-ruby-on-rails/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/27/how-to-receive-a-message-from-an-apache-activemq-topic-with-ruby-on-rails/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Ruby</td><td colspan="1" rowspan="1">JRuby</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/30/how-to-send-a-message-to-an-apache-activemq-queue-with-jruby/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/30/how-to-send-a-message-to-an-apache-activemq-topic-with-jruby/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-jruby/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-jruby/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Rust</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/16/how-to-send-a-message-to-an-apache-activemq-queue-with-rust/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/16/how-to-send-a-message-to-an-apache-activemq-topic-with-rust/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/16/how-to-receive-a-message-from-an-apache-activemq-queue-with-rust/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2015/01/16/how-to-receive-a-message-from-an-apache-activemq-topic-with-rust/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Scala</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-queue-with-scala/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-send-a-message-to-an-apache-activemq-topic-with-scala/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-queue-with-scala/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2013/12/31/how-to-receive-a-message-from-an-apache-activemq-topic-with-scala/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Smalltalk</td><td colspan="1" rowspan="1">GNU Smalltalk</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/28/how-to-send-a-message-to-an-apache-activemq-queue-with-gnu-smalltalk/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/28/how-to-send-a-message-to-an-apache-activemq-topic-with-gnu-smalltalk/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/28/how-to-receive-a-message-from-an-apache-activemq-queue-with-gnu-smalltalk/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/28/how-to-receive-a-message-from-an-apache-activemq-topic-with-gnu-smalltalk/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Smalltalk</td><td colspan="1" rowspan="1">Squeak</td><td colspan="1" rowspan="1">Sockets</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/30/how-to-send-a-message-to-an-apache-activemq-queue-with-squeak/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/30/how-to-send-a-message-to-an-apache-activemq-topic-with-squeak/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/30/how-to-receive-a-message-from-an-apache-activemq-queue-with-squeak/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/03/30/how-to-receive-a-message-from-an-apache-activemq-topic-with-squeak/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Tcl</td><td colspan="1" rowspan="1">Tcl/Tk</td><td colspan="1" rowspan="1">Library</td><td colspan="1" rowspan="1">STOMP</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/27/how-to-send-a-message-to-an-apache-activemq-queue-with-tcltk/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/27/how-to-send-a-message-to-an-apache-activemq-topic-with-tcltk/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/27/how-to-receive-a-message-from-an-apache-activemq-queue-with-tcltk/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/02/27/how-to-receive-a-message-from-an-apache-activemq-topic-with-tcltk/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Tcl</td><td colspan="1" rowspan="1">Tcl/Java</td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/24/how-to-send-a-message-to-an-apache-activemq-queue-with-tcljava/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/24/how-to-send-a-message-to-an-apache-activemq-topic-with-tcljava/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/24/how-to-receive-a-message-from-an-apache-activemq-queue-with-tcljava/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/08/24/how-to-receive-a-message-from-an-apache-activemq-topic-with-tcljava/">Receive from Topic</a></li></ul></td></tr><tr><td colspan="1" rowspan="1">Xtend</td><td colspan="1" rowspan="1"><span>None</span></td><td colspan="1" rowspan="1">JMS</td><td colspan="1" rowspan="1">OpenWire</td><td colspan="1" rowspan="1"><ul><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/01/how-to-send-a-message-to-an-apache-activemq-queue-with-xtend/">Send to Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/01/how-to-send-a-message-to-an-apache-activemq-topic-with-xtend/">Send to Topic</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/01/how-to-receive-a-message-from-an-apache-activemq-queue-with-xtend/">Receive from Queue</a></li><li><a shape="rect" href="https://simplesassim.wordpress.com/2014/01/01/how-to-receive-a-message-from-an-apache-activemq-topic-with-xtend/">Receive from Topic</a></li></ul></td></tr></tbody></table></div>
diff --git a/delay-and-schedule-message-delivery.xml b/delay-and-schedule-message-delivery.xml
index d6885a6..5c8e1ad 100644
--- a/delay-and-schedule-message-delivery.xml
+++ b/delay-and-schedule-message-delivery.xml
@@ -1,13 +1,10 @@
-<div class="wiki-content maincontent"><p>ActiveMQ from version <strong>5.4</strong> has an optional persistent scheduler built into the ActiveMQ message broker. It is enabled by setting the broker <strong>schedulerSupport</strong> attribute to true in the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. <br clear="none"> An ActiveMQ client can take advantage of a delayed delivery by using the following message properties:</p><div class="confluence-information-macro confluence-information-macro-note"><p class="title">Check your Message Properties</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The message property <code>scheduledJobId </code>is reserved for use by the Job Scheduler. If this property is set before sending, the message will be sent immediately and not scheduled. Also, <span>after a scheduled message is received, the property </span><span><code>scheduledJobId</code> will be set on the received message so </span>keep this in mind if using something like a Camel Route which might automatically copy properties over when re-sending a message.</p></div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_DELAY</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>long</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The time in milliseconds that a message will wait before being scheduled to be delivered by the broker</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_PERIOD</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>long</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The time in milliseconds to wait after the start time to wait before scheduling the message again</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_REPEAT</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>int</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of times to repeat scheduling a message for delivery</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_CRON</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use a Cron entry to set the schedule</p></td></tr></tbody></table></div><p>For the connivence of Java JMS clients - there's an interface with the property names used for scheduling at <em><strong>org.apache.activemq.ScheduledMessage</strong></em>.</p><p>For example, to have a message scheduled for delivery in 60 seconds - you would need to set the <em>AMQ_SCHEDULED_DELAY</em> property:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ MessageProducer producer = session.createProducer(destination);
- TextMessage message = session.createTextMessage("test msg");
+<div class="wiki-content maincontent"><p>ActiveMQ from version <strong>5.4</strong> has an optional persistent scheduler built into the ActiveMQ message broker. It is enabled by setting the broker <strong>schedulerSupport</strong> attribute to true in the <link><page ri:content-title="Xml Configuration"></page></link>. <br clear="none"> An ActiveMQ client can take advantage of a delayed delivery by using the following message properties:</p><structured-macro ac:macro-id="9d386966-fbbb-49f5-afcd-e4fc705a19ed" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Check your Message Properties</parameter><rich-text-body><p>The message property <code>scheduledJobId </code>is reserved for use by the Job Scheduler. If this property is set before sending, the message will be sent immediately and not scheduled. Also, <span>after a scheduled message is received, the property </span><span><code>scheduledJobId</code> will be set on the received message so </span>keep this in mind if using something like a Camel Route which might automatically copy properties over when re-sending a message.</p></rich-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Property name</p></th><th colspan="1" rowspan="1"><p>type</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>AMQ_SCHEDULED_DELAY</p></td><td colspan="1" rowspan="1"><p>long</p></td><td colspan="1" rowspan="1"><p>The time in milliseconds that a message will wait before being scheduled to be delivered by the broker</p></td></tr><tr><td colspan="1" rowspan="1"><p>AMQ_SCHEDULED_PERIOD</p></td><td colspan="1" rowspan="1"><p>long</p></td><td colspan="1" rowspan="1"><p>The time in milliseconds to wait after the start time to wait before scheduling the message again</p></td></tr><tr><td colspan="1" rowspan="1"><p>AMQ_SCHEDULED_REPEAT</p></td><td colspan="1" rowspan="1"><p>int</p></td><td colspan="1" rowspan="1"><p>The number of times to repeat scheduling a message for delivery</p></td></tr><tr><td colspan="1" rowspan="1"><p>AMQ_SCHEDULED_CRON</p></td><td colspan="1" rowspan="1"><p>String</p></td><td colspan="1" rowspan="1"><p>Use a Cron entry to set the schedule</p></td></tr></tbody></table><p>For the connivence of Java JMS clients - there's an interface with the property names used for scheduling at <em><strong>org.apache.activemq.ScheduledMessage</strong></em>.</p><p>For example, to have a message scheduled for delivery in 60 seconds - you would need to set the <em>AMQ_SCHEDULED_DELAY</em> property:</p><structured-macro ac:macro-id="c68d7805-8bf6-4833-b600-9a20ee84ca98" ac:name="code" ac:schema-version="1"><plain-text-body> MessageProducer producer = session.createProducer(destination);
+ TextMessage message = session.createTextMessage("test msg");
long time = 60 * 1000;
message.setLongProperty(ScheduledMessage.AMQ_SCHEDULED_DELAY, time);
producer.send(message);
-]]></script>
-</div></div><p>You can set a message to wait with an initial delay, and the repeat delivery 10 times, waiting 10 seconds between each re-delivery:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ MessageProducer producer = session.createProducer(destination);
- TextMessage message = session.createTextMessage("test msg");
+</plain-text-body></structured-macro><p>You can set a message to wait with an initial delay, and the repeat delivery 10 times, waiting 10 seconds between each re-delivery:</p><structured-macro ac:macro-id="912377b9-7446-4d59-ab20-80cea8490783" ac:name="code" ac:schema-version="1"><plain-text-body> MessageProducer producer = session.createProducer(destination);
+ TextMessage message = session.createTextMessage("test msg");
long delay = 30 * 1000;
long period = 10 * 1000;
int repeat = 9;
@@ -15,22 +12,17 @@
message.setLongProperty(ScheduledMessage.AMQ_SCHEDULED_PERIOD, period);
message.setIntProperty(ScheduledMessage.AMQ_SCHEDULED_REPEAT, repeat);
producer.send(message);
-]]></script>
-</div></div><p>You can also use <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Cron" rel="nofollow">CRON</a> to schedule a message, for example, if you want a message scheduled to be delivered every hour, you would need to set the CRON entry to be - <em>0 * * * *</em> - e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ MessageProducer producer = session.createProducer(destination);
- TextMessage message = session.createTextMessage("test msg");
- message.setStringProperty(ScheduledMessage.AMQ_SCHEDULED_CRON, "0 * * * *");
+</plain-text-body></structured-macro><p>You can also use <a shape="rect" href="http://en.wikipedia.org/wiki/Cron">CRON</a> to schedule a message, for example, if you want a message scheduled to be delivered every hour, you would need to set the CRON entry to be - <em>0 * * * *</em> - e.g.</p><structured-macro ac:macro-id="a4d4b451-b5a5-4c05-b608-6034275960a5" ac:name="code" ac:schema-version="1"><plain-text-body> MessageProducer producer = session.createProducer(destination);
+ TextMessage message = session.createTextMessage("test msg");
+ message.setStringProperty(ScheduledMessage.AMQ_SCHEDULED_CRON, "0 * * * *");
producer.send(message);
-]]></script>
-</div></div><p>CRON scheduling takes priority over using message delay - however, if a repeat and period is set with a CRON entry, the ActiveMQ scheduler will schedule delivery of the message for every time the CRON entry fires. Easier to explain with an example. Supposing that you want a message to be delivered 10 times, with a one second delay between each message - and you wanted this to happen every hour - you'd do this:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ MessageProducer producer = session.createProducer(destination);
- TextMessage message = session.createTextMessage("test msg");
- message.setStringProperty(ScheduledMessage.AMQ_SCHEDULED_CRON, "0 * * * *");
+</plain-text-body></structured-macro><p>CRON scheduling takes priority over using message delay - however, if a repeat and period is set with a CRON entry, the ActiveMQ scheduler will schedule delivery of the message for every time the CRON entry fires. Easier to explain with an example. Supposing that you want a message to be delivered 10 times, with a one second delay between each message - and you wanted this to happen every hour - you'd do this:</p><structured-macro ac:macro-id="6a9d7e73-9d13-44b2-80e0-63ca1b8130b3" ac:name="code" ac:schema-version="1"><plain-text-body> MessageProducer producer = session.createProducer(destination);
+ TextMessage message = session.createTextMessage("test msg");
+ message.setStringProperty(ScheduledMessage.AMQ_SCHEDULED_CRON, "0 * * * *");
message.setLongProperty(ScheduledMessage.AMQ_SCHEDULED_DELAY, 1000);
message.setLongProperty(ScheduledMessage.AMQ_SCHEDULED_PERIOD, 1000);
message.setIntProperty(ScheduledMessage.AMQ_SCHEDULED_REPEAT, 9);
producer.send(message);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/delete-inactive-destinations.xml b/delete-inactive-destinations.xml
index 6273c34..14bff40 100644
--- a/delete-inactive-destinations.xml
+++ b/delete-inactive-destinations.xml
@@ -1,16 +1,12 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Inactive Destination</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">An 'inactive' destination is one that has had no messages pending and no consumers connected for some configured period of time.</div></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">By default the broker does <em>not</em> check for inactive destinations. This as governed by the default values for the following options: <strong><code>schedulePeriodForDestinationPurge="0"</code></strong> and <strong><code>gcInactiveDestinations="false"</code></strong>.</div></div><p>However, the broker can be configured to purge inactive destinations. To do so requires using specially configured destination policy entries in combination with the broker attribute: <strong><code>schedulePeriodForDestinationPurge > 0</code></strong>.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker xmlns="http://activemq.apache.org/schema/core" schedulePeriodForDestinationPurge="10000">
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="fcf7d983-a1c8-45c4-97f5-e84d80c6cb5e" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Inactive Destination</parameter><rich-text-body>An 'inactive' destination is one that has had no messages pending and no consumers connected for some configured period of time.</rich-text-body></structured-macro><structured-macro ac:macro-id="44b9356b-6be3-4fbf-87d6-7c0840678f48" ac:name="info" ac:schema-version="1"><rich-text-body>By default the broker does <em>not</em> check for inactive destinations. This as governed by the default values for the following options: <strong><code>schedulePeriodForDestinationPurge="0"</code></strong> and <strong><code>gcInactiveDestinations="false"</code></strong>.</rich-text-body></structured-macro><p>However, the broker can be configured to purge inactive destinations. To do so requires using specially configured destination policy entries in combination with the broker attribute: <strong><code>schedulePeriodForDestinationPurge > 0</code></strong>.</p><p>Example:</p><structured-macro ac:macro-id="6500de46-5edd-41a6-8032-baf0dc981af5" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><broker xmlns="http://activemq.apache.org/schema/core" schedulePeriodForDestinationPurge="10000">
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue=">" gcInactiveDestinations="true" inactiveTimoutBeforeGC="30000"/>
+ <policyEntry queue=">" gcInactiveDestinations="true" inactiveTimoutBeforeGC="30000"/>
</policyEntries>
</policyMap>
</destinationPolicy>
-</broker>]]></script>
-</div></div><p>In this example the broker will check for inactive destinations every <strong><code>10</code></strong> seconds, as determined by <strong><code>schedulePeriodForDestinationPurge="10000"</code></strong>. When a destination purge is triggered the broker will delete any queue that has been empty for longer than <strong><code>inactiveTimoutBeforeGC="30000"</code></strong> milliseconds (default: <strong><code>60000</code></strong> milliseconds) and for which <strong><code>gcInactiveDestinations="true"</code></strong> is set on its corresponding destination policy entry.</p><p>When a destination is removed the broker will log a message like:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[INFO Queue - TEST.QUEUE Inactive for longer than 30000 ms - removing ...]]></script>
-</div></div><p> </p><p> </p></div>
+</broker></plain-text-body></structured-macro><p>In this example the broker will check for inactive destinations every <strong><code>10</code></strong> seconds, as determined by <strong><code>schedulePeriodForDestinationPurge="10000"</code></strong>. When a destination purge is triggered the broker will delete any queue that has been empty for longer than <strong><code>inactiveTimoutBeforeGC="30000"</code></strong> milliseconds (default: <strong><code>60000</code></strong> milliseconds) and for which <strong><code>gcInactiveDestinations="true"</code></strong> is set on its corresponding destination policy entry.</p><p>When a destination is removed the broker will log a message like:</p><structured-macro ac:macro-id="af51b539-e8e4-4614-88fb-8c56e9030c99" ac:name="code" ac:schema-version="1"><plain-text-body>INFO Queue - TEST.QUEUE Inactive for longer than 30000 ms - removing ...</plain-text-body></structured-macro><p> </p><p> </p></div>
diff --git a/delphi-and-freepascal.xml b/delphi-and-freepascal.xml
index 2741618..5b991fc 100644
--- a/delphi-and-freepascal.xml
+++ b/delphi-and-freepascal.xml
@@ -1,14 +1,14 @@
-<div class="wiki-content maincontent"><h1 id="DelphiandFreePascal-DelphiandFreePascalClient">Delphi and FreePascal Client</h1>
+<div class="wiki-content maincontent"><h1>Delphi and FreePascal Client</h1>
<p>Habari ActiveMQ Client is a library for Delphi(tm) and Free Pascal. With Habari, applications can connect to Apache ActiveMQ servers, subscribe to queues and topics, send and receive messages and objects, and work with transactions.</p>
-<h3 id="DelphiandFreePascal-SupportedCommunicationLibraries">Supported Communication Libraries</h3>
+<h3>Supported Communication Libraries</h3>
<ul><li>Internet Direct (Indy) 10.2</li><li>Synapse</li><li>OverByte ICS V6 (limited feature set)</li><li>TClientSocket (limited feature set)</li></ul>
-<h3 id="DelphiandFreePascal-ProjectStatus">Project Status</h3>
+<h3>Project Status</h3>
<p>Habari ActiveMQ Client 1.0 has been released on March 5, 2008. Demo applications, API documentation and source code examples are available for download. <br clear="none">
-The API documentation is available at <a shape="rect" class="external-link" href="http://www.mikejustin.com/habari/docs/html/index.html" rel="nofollow">http://www.mikejustin.com/habari/docs/html/index.html</a></p>
+The API documentation is available at <a shape="rect" href="http://www.mikejustin.com/habari/docs/html/index.html">http://www.mikejustin.com/habari/docs/html/index.html</a></p>
-<h3 id="DelphiandFreePascal-ProjectHomePage">Project Home Page</h3>
-<p><a shape="rect" class="external-link" href="http://www.mikejustin.com/" rel="nofollow">http://www.mikejustin.com/</a></p></div>
+<h3>Project Home Page</h3>
+<p><a shape="rect" href="http://www.mikejustin.com/">http://www.mikejustin.com/</a></p></div>
diff --git a/design-documents.xml b/design-documents.xml
index 1b2e0c5..e15f1ca 100644
--- a/design-documents.xml
+++ b/design-documents.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><ul><li><a shape="rect" href="slow-consumers.xml">Slow Consumers</a></li><li><a shape="rect" href="durable-queue-memory-management.xml">Durable Queue Memory Management</a></li><li><a shape="rect" href="supporting-io-streams.xml">Supporting IO Streams</a></li><li><a shape="rect" href="message-redelivery-and-dlq-handling.xml">Message Redelivery and DLQ Handling</a></li><li><a shape="rect" href="multicast-transport.xml">Multicast Transport</a></li><li><a shape="rect" href="proposed-c-client-architecture.xml">Proposed C Client Architecture</a></li><li><a shape="rect" href="rest-protocols.xml">REST protocols</a></li></ul></div>
+<div class="wiki-content maincontent"><ul><li><link><page ri:content-title="Slow Consumers"></page></link></li><li><link><page ri:content-title="Durable Queue Memory Management"></page></link></li><li><link><page ri:content-title="Supporting IO Streams"></page></link></li><li><link><page ri:content-title="Message Redelivery and DLQ Handling"></page></link></li><li><link><page ri:content-title="Multicast Transport"></page></link></li><li><link><page ri:content-title="Proposed C Client Architecture"></page></link></li><li><link><page ri:content-title="REST protocols"></page></link></li></ul>
+</div>
diff --git a/destination-features.xml b/destination-features.xml
index d9996a7..d7e7e4f 100644
--- a/destination-features.xml
+++ b/destination-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="composite-destinations.xml">Composite Destinations</a></li><li><a shape="rect" href="configure-startup-destinations.xml">Configure Startup Destinations</a></li><li><a shape="rect" href="delete-inactive-destinations.xml">Delete Inactive Destinations</a></li><li><a shape="rect" href="destination-options.xml">Destination Options</a></li><li><a shape="rect" href="mirrored-queues.xml">Mirrored Queues</a></li><li><a shape="rect" href="per-destination-policies.xml">Per Destination Policies</a></li><li><a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a></li><li><a shape="rect" href="wildcards.xml">Wildcards</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="9c003b57-9b0d-42d5-b9a7-84b09f429720" ac:name="children" ac:schema-version="1"><parameter ac:name="">all</parameter></structured-macro></div>
diff --git a/destination-options.xml b/destination-options.xml
index ec098d5..5eaba8a 100644
--- a/destination-options.xml
+++ b/destination-options.xml
@@ -1,6 +1,4 @@
-<div class="wiki-content maincontent"><h3 id="DestinationOptions-Background">Background</h3><p>Destination Options are a way to provide extended configuration options to a JMS consumer without having to extend the JMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on.</p><h3 id="DestinationOptions-ConsumerOptions">Consumer Options</h3><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><code>consumer.dispatchAsync</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker <a shape="rect" href="consumer-dispatch-async.xml">dispatch messages asynchronously</a> to the consumer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumer.exclusive</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Is this an <a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumer.maximumPendingMessageLimit</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use to control if messages for non-durable topics are dropped if a <a shape="rect" href="slow-consumer-handling.xml">slow consumer</a> situation exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumer.noLocal</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Same as the <strong><code>noLocal</code></strong> flag on a Topic consumer. Exposed here so that it can be used with a queue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumer.prefetchSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>n/a</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of message the consumer will <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumer.priority</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows you to configure a <a shape="rect" href="consumer-priority.xml">Consumer Priority</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumer.retroactive</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Is this a <a shape="rect" href="retroactive-consumer.xml">Retroactive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumer.selector</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>JMS Selector used with the consumer.</p></td></tr></tbody></table></div><h3 id="DestinationOptions-Example">Example</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[queue = new ActiveMQQueue("TEST.QUEUE?consumer.dispatchAsync=false&consumer.prefetchSize=10");
+<div class="wiki-content maincontent"><h3>Background</h3><p>Destination Options are a way to provide extended configuration options to a JMS consumer without having to extend the JMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on.</p><h3>Consumer Options</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>consumer.dispatchAsync</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Should the broker <link><page ri:content-title="Consumer Dispatch Async"></page><plain-text-link-body>dispatch messages asynchronously</plain-text-link-body></link> to the consumer.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumer.exclusive</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Is this an <link><page ri:content-title="Exclusive Consumer"></page></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumer.maximumPendingMessageLimit</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Use to control if messages for non-durable topics are dropped if a <link><page ri:content-title="Slow Consumer Handling"></page><plain-text-link-body>slow consumer</plain-text-link-body></link> situation exists.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumer.noLocal</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Same as the <strong><code>noLocal</code></strong> flag on a Topic consumer. Exposed here so that it can be used with a queue.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumer.prefetchSize</code></p></td><td colspan="1" rowspan="1"><p><code>n/a</code></p></td><td colspan="1" rowspan="1"><p>The number of message the consumer will <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>prefetch</plain-text-link-body></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumer.priority</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Allows you to configure a <link><page ri:content-title="Consumer Priority"></page></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumer.retroactive</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Is this a <link><page ri:content-title="Retroactive Consumer"></page></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumer.selector</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>JMS Selector used with the consumer.</p></td></tr></tbody></table><h3>Example</h3><structured-macro ac:macro-id="3ee1935a-0d33-41b2-b125-7b032eae301b" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>queue = new ActiveMQQueue("TEST.QUEUE?consumer.dispatchAsync=false&consumer.prefetchSize=10");
consumer = session.createConsumer(queue);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/destinations-plugin.xml b/destinations-plugin.xml
index 04d03eb..8018c9f 100644
--- a/destinations-plugin.xml
+++ b/destinations-plugin.xml
@@ -1,6 +1,4 @@
-<div class="wiki-content maincontent"><p>In some environments clients can't create destinations and only administrators are allowed to do that using management consoles or APIs. This plugin allows users to export destinations created during the runtime of the broker and replicate that state on another broker.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <plugins>
- <destinationsPlugin location="/workspace/destinations"/>
- </plugins>]]></script>
-</div></div><p> </p><p>The plugin saves all destinations to the file defined by the location property when it stops. If the property is not specified, broker data directory will be used and the file will be named <code>destinations</code> (<code>${ACTIVEMQ_HOME}/data/localhost/destinations</code> by default). If this file is present on the broker start, destinations listed in the file will be pre-created. The future improvements can include periodic export or on demand via management API.</p></div>
+<div class="wiki-content maincontent"><p>In some environments clients can't create destinations and only administrators are allowed to do that using management consoles or APIs. This plugin allows users to export destinations created during the runtime of the broker and replicate that state on another broker.</p><structured-macro ac:macro-id="3fd8e4f9-55b1-482d-a0d5-506278d29dee" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body> <plugins>
+ <destinationsPlugin location="/workspace/destinations"/>
+ </plugins></plain-text-body></structured-macro><p> </p><p>The plugin saves all destinations to the file defined by the location property when it stops. If the property is not specified, broker data directory will be used and the file will be named <code>destinations</code> (<code>${ACTIVEMQ_HOME}/data/localhost/destinations</code> by default). If this file is present on the broker start, destinations listed in the file will be pre-created. The future improvements can include periodic export or on demand via management API.</p></div>
diff --git a/developer-forum.xml b/developer-forum.xml
index e1b0bd3..d2fa78b 100644
--- a/developer-forum.xml
+++ b/developer-forum.xml
@@ -1,5 +1,5 @@
-<div class="wiki-content maincontent"><p>
-<a shape="rect" id="nabblelink" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html">ActiveMQ - Dev</a>
-<script src="http://activemq.2283324.n4.nabble.com/embed/f2368404"></script>
-</p><p></p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="979c14ec-231e-4310-b1c9-4f97fd543ff8" ac:name="html" ac:schema-version="1"><plain-text-body>
+<a id="nabblelink" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html">ActiveMQ - Dev</a>
+<script src="http://activemq.2283324.n4.nabble.com/embed/f2368404"></script>
+</plain-text-body></structured-macro></p><p></p></div>
diff --git a/developer-guide.xml b/developer-guide.xml
index c194982..3008545 100644
--- a/developer-guide.xml
+++ b/developer-guide.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The following documents might be interesting</p><ul><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="release-plans.xml">Release Plans</a></li><li><a shape="rect" href="release-guide.xml">Release Guide</a></li><li><a shape="rect" href="design-documents.xml">Design Documents</a></li><li><a shape="rect" href="changes-in-40.xml">Changes in 4.0</a></li><li><a shape="rect" href="apache-activemq-board-reports.xml">Apache ActiveMQ Board Reports</a></li><li><a shape="rect" href="maven-snapshot-repository-in-your-pom.xml">Maven SNAPSHOT Repository in your POM</a></li></ul><h3 id="DeveloperGuide-Codewalkthrough">Code walkthrough</h3><ul class="alternate"><li><a shape="rect" href="code-overview.xml">Code Overview</a></li><li><a shape="rect" href="wire-protocol.xml">Wire Protocol</a></li><li><a shape="rect" href="developing-plugins.xml">Developing Plugins</a></li></ul></div>
+<div class="wiki-content maincontent"><p>The following documents might be interesting</p><ul><li><link><page ri:content-title="Building"></page></link></li><li><link><page ri:content-title="Release Plans"></page></link></li><li><link><page ri:content-title="Release Guide"></page></link></li><li><link><page ri:content-title="Design Documents"></page></link></li><li><link><page ri:content-title="Changes in 4.0"></page></link></li><li><link><page ri:content-title="Apache ActiveMQ Board Reports"></page></link></li><li><link><page ri:content-title="Maven SNAPSHOT Repository in your POM"></page></link></li></ul><h3>Code walkthrough</h3><ul class="alternate"><li><link><page ri:content-title="Code Overview"></page></link></li><li><link><page ri:content-title="Wire Protocol"></page></link></li><li><link><page ri:content-title="Developing Plugins"></page></link></li></ul></div>
diff --git a/developers.xml b/developers.xml
index afe7f55..6daa975 100644
--- a/developers.xml
+++ b/developers.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="becoming-a-committer.xml">Becoming a committer</a></li><li><a shape="rect" href="benchmark-tests.xml">Benchmark Tests</a></li><li><a shape="rect" href="board-reports.xml">Board Reports</a><ul class="childpages-macro"><li><a shape="rect" href="2007-april.xml">2007 April</a></li></ul></li><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="code-overview.xml">Code Overview</a></li><li><a shape="rect" href="developer-guide.xml">Developer Guide</a><ul class="childpages-macro"><li><a shape="rect" href="design-documents.xml">Design Documents</a><ul class="childpages-macro"><li><a shape="rect" href="class-diagrams-for-activemq-40-m4-source-code.xml">Class Diagrams for activemq-4.0-M4 source code</a></li><li><a shape="rect" href="durable-queue-memory-management.xml">Durable Queue Memory Management</a></li><li><a shape="rect" href="message-redelivery-and-dlq-handling.xml">Message Redelivery and DLQ Handling</a></li><li><a shape="rect" href="multicast-transport.xml">Multicast Transport</a></li><li><a shape="rect" href="proposed-c-client-architecture.xml">Proposed C Client Architecture</a></li><li><a shape="rect" href="rest-protocols.xml">REST protocols</a></li><li><a shape="rect" href="slow-consumers.xml">Slow Consumers</a></li><li><a shape="rect" href="supporting-io-streams.xml">Supporting IO Streams</a></li></ul></li><li><a shape="rect" href="developing-plugins.xml">Developing Plugins</a></li><li><a shape="rect" href="maven-snapshot-repository-in-your-pom.xml">Maven SNAPSHOT Repository in your POM</a></li><li><a shape="rect" href="release-plans.xml">Release Plans</a><ul class="childpages-macro"><li><a shape="rect" href="40-rc-1-guide.xml">4.0 RC 1 Guide</a></li><li><a shape="rect" href="how-you-can-help-release.xml">How you can help release</a></li><li><a shape="rect" href="release-info.xml">Release Info</a></li></ul></li></ul></li><li><a shape="rect" href="ideas.xml">Ideas</a><ul class="childpages-macro"><li><a shape="rect" href="restful-queue.xml">RESTful Queue</a></li></ul></li><li><a shape="rect" href="integration-tests.xml">Integration Tests</a><ul class="childpages-macro"><li><a shape="rect" href="example-testing-scenario.xml">Example Testing Scenario</a></li></ul></li><li><a shape="rect" href="jmeter-performance-tests.xml">JMeter Performance Tests</a></li><li><a shape="rect" href="jmeter-system-tests.xml">JMeter System Tests</a></li><li><a shape="rect" href="junit-reports.xml">JUnit Reports</a></li><li><a shape="rect" href="release-guide.xml">Release Guide</a></li><li><a shape="rect" href="sandbox.xml">Sandbox</a></li><li><a shape="rect" href="source.xml">Source</a></li><li><a shape="rect" href="source-xref.xml">Source XRef</a></li><li><a shape="rect" href="svn.xml">SVN</a></li><li><a shape="rect" href="test-source-xref.xml">Test Source XRef</a></li><li><a shape="rect" href="wire-protocol.xml">Wire Protocol</a></li></ul> </div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="deb1db17-86c2-4189-adb5-f9ba39674adb" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro> </div>
diff --git a/developing-activemq.xml b/developing-activemq.xml
index f551956..505bc26 100644
--- a/developing-activemq.xml
+++ b/developing-activemq.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>Questions for developers wishing to extend or enhance Apache ActiveMQ</p>
-<ul class="childpages-macro"><li><a shape="rect" href="how-can-i-add-a-new-type-of-transport.xml">How can I add a new type of transport</a></li><li><a shape="rect" href="how-can-i-contribute.xml">How can I contribute</a></li><li><a shape="rect" href="how-do-i-add-my-own-plugins.xml">How do I add my own plugins</a></li><li><a shape="rect" href="how-do-i-debug-activemq-from-my-ide.xml">How do I debug ActiveMQ from my IDE</a></li></ul></div>
+<structured-macro ac:macro-id="f2073f3c-4db5-47be-ae49-cba901b84bce" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/developing-plugins.xml b/developing-plugins.xml
index b2e0216..125e78a 100644
--- a/developing-plugins.xml
+++ b/developing-plugins.xml
@@ -1,37 +1,31 @@
-<div class="wiki-content maincontent"><p>Apache ActiveMQ is based on the model of POJOs and <em>Dependency Injection</em>. If you are developing <a shape="rect" href="interceptors.xml">Interceptors</a> or additional components or plugins for ActiveMQ then the first thing you should do is develop the code as if you are writing any other Spring component, using dependency injection.</p><h3 id="DevelopingPlugins-DependencyInjection">Dependency Injection</h3><p>Some folks favour using constructor based injection as it removes the need to have a separate lifecycle <em>start()</em> method - others find using property based injection is a little more flexible and easier to map to XML configuration files. We'll leave that choice up to you. For complex to create objects you could consider writing a FactoryBean. For more details on writing POJOs with Spring see their <a shape="rect" class="external-link" href="http://www.springframework.org/documentation" rel="nofollow">documentation</a>.</p><h3 id="DevelopingPlugins-CustomXML">Custom XML</h3><p>With ActiveMQ you can use regular Spring.xml syntax to configure things. However to produce neater XML that is easier to read and edit we use <a shape="rect" class="external-link" href="http://geronimo.apache.org/xbean/">XBean</a> to autogenerate support for <a shape="rect" class="external-link" href="http://geronimo.apache.org/xbean/custom-xml.html">Custom XML</a>.</p><p>If you wish your POJO to have its own custom XML you may wish to follow the following source examples for working nicely with XBean. Basically you add an XBean annotation in the javadoc comments to tell XBean how to map the POJO to custom XML. This should look something like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[/**
- * @org.apache.xbean.XBean element="foo"
+<div class="wiki-content maincontent"><p>Apache ActiveMQ is based on the model of POJOs and <em>Dependency Injection</em>. If you are developing <link><page ri:content-title="Interceptors"></page></link> or additional components or plugins for ActiveMQ then the first thing you should do is develop the code as if you are writing any other Spring component, using dependency injection.</p><h3>Dependency Injection</h3><p>Some folks favour using constructor based injection as it removes the need to have a separate lifecycle <em>start()</em> method - others find using property based injection is a little more flexible and easier to map to XML configuration files. We'll leave that choice up to you. For complex to create objects you could consider writing a FactoryBean. For more details on writing POJOs with Spring see their <a shape="rect" href="http://www.springframework.org/documentation">documentation</a>.</p><h3>Custom XML</h3><p>With ActiveMQ you can use regular Spring.xml syntax to configure things. However to produce neater XML that is easier to read and edit we use <a shape="rect" href="http://geronimo.apache.org/xbean/">XBean</a> to autogenerate support for <a shape="rect" href="http://geronimo.apache.org/xbean/custom-xml.html">Custom XML</a>.</p><p>If you wish your POJO to have its own custom XML you may wish to follow the following source examples for working nicely with XBean. Basically you add an XBean annotation in the javadoc comments to tell XBean how to map the POJO to custom XML. This should look something like</p><structured-macro ac:macro-id="18ed826e-ea03-4094-8041-ea885c64973f" ac:name="code" ac:schema-version="1"><plain-text-body>/**
+ * @org.apache.xbean.XBean element="foo"
*/
public class MyExtension {
...
}
-]]></script>
-</div></div><p>You can omit the element configuration. For more details on the available annotation options see <a shape="rect" class="external-link" href="http://geronimo.apache.org/xbean/xbean-ant-task.html">here</a></p><p>If you are submitting your plugin to the ActiveMQ project then it will end up being included in the maven build step to create the XBean artifacts as part of the jar (in the META-INF/services area).</p><p>However if you are writing an external plugin to ActiveMQ then you will need to add the maven-xbean-plugin to your Maven 2 build. Refer to the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-spring/pom.xml">activemq-spring/pom.xml</a> as an example of using this plugin.</p><h3 id="DevelopingPlugins-ConfiguringpluginswithoutcustomXML">Configuring plugins without custom XML</h3><p>If you want to configure plugins that does not implement custom XML, you can define plugins as "regular" Spring beans and reference them in broker's <code>plugins</code> attribute. For example,</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker useJmx="true" xmlns="http://activemq.apache.org/schema/core" plugins="#loggingPlugin">
+</plain-text-body></structured-macro><p>You can omit the element configuration. For more details on the available annotation options see <a shape="rect" href="http://geronimo.apache.org/xbean/xbean-ant-task.html">here</a></p><p>If you are submitting your plugin to the ActiveMQ project then it will end up being included in the maven build step to create the XBean artifacts as part of the jar (in the META-INF/services area).</p><p>However if you are writing an external plugin to ActiveMQ then you will need to add the maven-xbean-plugin to your Maven 2 build. Refer to the <a shape="rect" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-spring/pom.xml">activemq-spring/pom.xml</a> as an example of using this plugin.</p><h3>Configuring plugins without custom XML</h3><p>If you want to configure plugins that does not implement custom XML, you can define plugins as "regular" Spring beans and reference them in broker's <code>plugins</code> attribute. For example,</p><structured-macro ac:macro-id="1dd35da6-a1b9-41af-ab9b-43fe546563b6" ac:name="code" ac:schema-version="1"><plain-text-body><broker useJmx="true" xmlns="http://activemq.apache.org/schema/core" plugins="#loggingPlugin">
...
</broker>
-<bean id="loggingPlugin"
- class="org.apache.activemq.broker.util.LoggingBrokerPlugin"
+<bean id="loggingPlugin"
+ class="org.apache.activemq.broker.util.LoggingBrokerPlugin"
/>
-]]></script>
-</div></div><p>Not that this mechanism will not work in case that you have some XBean plugins configured inside the <code><plugins/></code> tag. In that case you must define the plugin inside that tag as well (with the appropriate schema definition). For example,</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<plugins>
+</plain-text-body></structured-macro><p>Not that this mechanism will not work in case that you have some XBean plugins configured inside the <code><plugins/></code> tag. In that case you must define the plugin inside that tag as well (with the appropriate schema definition). For example,</p><structured-macro ac:macro-id="8a2615a4-df89-4e27-9b6b-523392c4aad0" ac:name="code" ac:schema-version="1"><plain-text-body><plugins>
<simpleAuthenticationPlugin>
<users>
- <authenticationUser username="system" password="manager"
- groups="users,admins"/>
- <authenticationUser username="user" password="password"
- groups="users"/>
- <authenticationUser username="guest" password="password" groups="guests"/>
+ <authenticationUser username="system" password="manager"
+ groups="users,admins"/>
+ <authenticationUser username="user" password="password"
+ groups="users"/>
+ <authenticationUser username="guest" password="password" groups="guests"/>
</users>
</simpleAuthenticationPlugin>
- <bean xmlns="http://www.springframework.org/schema/beans"
- id="loggingPlugin"
- class="org.apache.activemq.broker.util.LoggingBrokerPlugin"
+ <bean xmlns="http://www.springframework.org/schema/beans"
+ id="loggingPlugin"
+ class="org.apache.activemq.broker.util.LoggingBrokerPlugin"
/>
</plugins>
-]]></script>
-</div></div><h3 id="DevelopingPlugins-Examples">Examples</h3><p>The easiest way to get a feel for how to extend ActiveMQ is maybe to look at some concrete examples of features and how those are implemented and configured. Here are some examples</p><ul><li><a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-spring/src/main/java/org/apache/activemq/xbean/XBeanBrokerService.java">XBeanBrokerService</a> deals with most of the core configuration of the <broker> tag in the XML</li><li><a shape="rect" href="security.xml">Security</a> has an <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/jaas-broker.xml">example</a> XML configuration file using the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/security/AuthorizationPlugin.java">AuthorizationPlugin</a></li><li>The <a shape="rect" href="message-redelivery-and-dlq-handling.xml#MessageRedeliveryandDLQHandling-TheDiscardingDLQPlugin">Discarding DLQ Plugin</a> is used to discard messages from the DLQ.</li></ul></div>
+</plain-text-body></structured-macro><h3>Examples</h3><p>The easiest way to get a feel for how to extend ActiveMQ is maybe to look at some concrete examples of features and how those are implemented and configured. Here are some examples</p><ul><li><a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-spring/src/main/java/org/apache/activemq/xbean/XBeanBrokerService.java">XBeanBrokerService</a> deals with most of the core configuration of the <broker> tag in the XML</li><li><link><page ri:content-title="Security"></page></link> has an <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/jaas-broker.xml">example</a> XML configuration file using the <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/security/AuthorizationPlugin.java">AuthorizationPlugin</a></li><li>The <link ac:anchor="The Discarding DLQ Plugin"><page ri:content-title="Message Redelivery and DLQ Handling"></page><plain-text-link-body>Discarding DLQ Plugin</plain-text-link-body></link> is used to discard messages from the DLQ.</li></ul></div>
diff --git a/discovery-transport-reference.xml b/discovery-transport-reference.xml
index 04533fd..7a5ed9a 100644
--- a/discovery-transport-reference.xml
+++ b/discovery-transport-reference.xml
@@ -1,42 +1,39 @@
-<div class="wiki-content maincontent"><h3 id="DiscoveryTransportReference-TheDiscoveryTransport">The Discovery Transport</h3>
+<div class="wiki-content maincontent"><h3>The Discovery Transport</h3>
-<p>The Discovery transport works just like the <a shape="rect" href="failover-transport-reference.xml">Failover</a> transport, except that it uses a discovery agent to locate the list of uri to connect to. The Discovery transport is also used by the <a shape="rect" href="fanout-transport-reference.xml">Fanout</a> transport for discovering brokers to send a fanout message to.</p>
+<p>The Discovery transport works just like the <link><page ri:content-title="Failover Transport Reference"></page><link-body>Failover</link-body></link> transport, except that it uses a discovery agent to locate the list of uri to connect to. The Discovery transport is also used by the <link><page ri:content-title="Fanout Transport Reference"></page><link-body>Fanout</link-body></link> transport for discovering brokers to send a fanout message to.</p>
-<h4 id="DiscoveryTransportReference-ConfigurationSyntax">Configuration Syntax</h4>
+<h4>Configuration Syntax</h4>
<p><strong>discovery:(discoveryAgentURI)?transportOptions</strong><br clear="none">
or<br clear="none">
<strong>discovery:discoveryAgentURI</strong></p>
-<p>Note that to be able to use <a shape="rect" href="discovery.xml">Discovery</a> to find brokers, the brokers need to have the multicast discovery agent enabled on the broker. </p>
+<p>Note that to be able to use <link><page ri:content-title="Discovery"></page></link> to find brokers, the brokers need to have the multicast discovery agent enabled on the broker. </p>
-<p>To configure discovery in a Broker you should use the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. Here is an <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/usecases/receiver-discovery.xml?view=co">example</a> of using discovery. Its basically something like the following (see the <strong>discoveryUri</strong>)</p>
+<p>To configure discovery in a Broker you should use the <link><page ri:content-title="Xml Configuration"></page></link>. Here is an <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/usecases/receiver-discovery.xml?view=co">example</a> of using discovery. Its basically something like the following (see the <strong>discoveryUri</strong>)</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker name="foo">
+<structured-macro ac:macro-id="aaf47c6c-4495-4851-b8a2-4d450e232d07" ac:name="code" ac:schema-version="1"><plain-text-body>
+<broker name="foo">
<transportConnectors>
- <transportConnector uri="tcp://localhost:0" discoveryUri="multicast://default"/>
+ <transportConnector uri="tcp://localhost:0" discoveryUri="multicast://default"/>
</transportConnectors>
...
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h5 id="DiscoveryTransportReference-TransportOptions">Transport Options</h5>
+<h5>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>reconnectDelay</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 for discovery</p></td></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 to a discovered url</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</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useExponentialBackOff</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>backOffMultiplier</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>2</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>0</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</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>group</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>default</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 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></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>reconnectDelay</p></td><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>How long to wait for discovery</p></td></tr><tr><td colspan="1" rowspan="1"><p>initialReconnectDelay</p></td><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>How long to wait before the first reconnect attempt to a discovered url</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxReconnectDelay</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>The maximum amount of time we ever wait between reconnect attempts</p></td></tr><tr><td colspan="1" rowspan="1"><p>useExponentialBackOff</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should an exponential backoff be used btween reconnect attempts</p></td></tr><tr><td colspan="1" rowspan="1"><p>backOffMultiplier</p></td><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>The exponent used in the exponential backoff attempts</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxReconnectAttempts</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>If not 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"><p>group</p></td><td colspan="1" rowspan="1"><p>default</p></td><td colspan="1" rowspan="1"><p> 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></td></tr></tbody></table>
-<h5 id="DiscoveryTransportReference-ExampleURI">Example URI</h5>
+<h5>Example URI</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>discovery:(multicast://default)?initialReconnectDelay=100
-</pre>
-</div></div>
+<structured-macro ac:macro-id="9b5b8676-087a-4fb5-a1a5-b5fa176682fc" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+discovery:(multicast://default)?initialReconnectDelay=100
+</plain-text-body></structured-macro>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Applying parameters to discovered transports</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>From 5.4, transport parameters in the URI will also be applied to discovered transports if they are prefixed with <code>discovered.</code>; For example, adding the <code>discovered.connectionTimeout</code> parameter to the URI will apply the parameter to every discovered <a shape="rect" href="tcp-transport-reference.xml">TCP</a> transport, even though this parameter is not a Discovery transport option.</p></div></div></div>
+<structured-macro ac:macro-id="a04821a9-8498-4d06-a5e0-f047d1b800e3" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Applying parameters to discovered transports</parameter><rich-text-body>
+<p>From 5.4, transport parameters in the URI will also be applied to discovered transports if they are prefixed with <code>discovered.</code>; For example, adding the <code>discovered.connectionTimeout</code> parameter to the URI will apply the parameter to every discovered <link><page ri:content-title="TCP Transport Reference"></page><link-body>TCP</link-body></link> transport, even though this parameter is not a Discovery transport option.</p></rich-text-body></structured-macro></div>
diff --git a/discovery.xml b/discovery.xml
index 042a018..e393f9f 100644
--- a/discovery.xml
+++ b/discovery.xml
@@ -1,18 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="Discovery-DiscoveryAgents">Discovery Agents</h2><p>ActiveMQ uses an abstraction called a <a shape="rect" class="external-link" href="http://actievmq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/transport/discovery/DiscoveryAgent.html">Discovery Agent</a> to detect remote services such as remote brokers. We can use discovery for JMS clients to auto-detect a Message Broker to connect to, or to provide <a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a></p><p>There are currently two kinds of discovery agent.</p><h3 id="Discovery-Multicast">Multicast</h3><p>The Discovery transport uses our own Multicast based discovery agent to locate the list of URIs to connect to.</p><p>For more information see the <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport Reference</a>.</p><h3 id="Discovery-Zeroconf">Zeroconf</h3><p><a shape="rect" href="zeroconf.xml">ZeroConf</a> is a standard discovery specification that uses UDP / multicast to discovery devices. Its used by Apple's Rendezvous services.<br clear="none"> We use the <a shape="rect" class="external-link" href="http://jmdns.sf.net/" rel="nofollow">jmDNS</a> project to implement the Zeroconf specification to detect services. This means other Zeroconf<br clear="none"> based tools can be used in conjunction with this discovery agent.</p><p>To configure discovery in a Broker you should use the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. Here is an <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/usecases/receiver-zeroconf.xml?view=co">example</a> of using discovery to create <a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a>.</p><p>If you have one or more brokers running with Zeroconf discovery enabled you can connect to a broker using the brokerURL</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[zeroconf:_activemq_development.
-]]></script>
-</div></div><p>This will use Zeroconf to find an available broker and one will be randomly chosen & things will auto-failover on disconnect if there are several brokers running.</p><h3 id="Discovery-LDAPDiscovery">LDAP Discovery</h3><p>ActiveMQ supports the use of LDAP for discovery of brokers.</p><p>Please see <a shape="rect" href="ldap-broker-discovery-mechanism.xml">LDAP Broker Discovery Mechanism</a> for more details.</p><h2 id="Discovery-Tryingoutdiscovery">Trying out discovery</h2><p>If you run the following commands in separate shells you'll have 2 brokers auto-discovering themselves and 2 clients using fixed-URLs</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[maven -o server -Dconfig=src/test/org/activemq/usecases/receiver-zeroconf.xml
+<div class="wiki-content maincontent"><h2>Discovery Agents</h2><p>ActiveMQ uses an abstraction called a <a shape="rect" href="http://actievmq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/transport/discovery/DiscoveryAgent.html">Discovery Agent</a> to detect remote services such as remote brokers. We can use discovery for JMS clients to auto-detect a Message Broker to connect to, or to provide <link><page ri:content-title="Networks of Brokers"></page></link></p><p>There are currently two kinds of discovery agent.</p><h3>Multicast</h3><p>The Discovery transport uses our own Multicast based discovery agent to locate the list of URIs to connect to.</p><p>For more information see the <link><page ri:content-title="Discovery Transport Reference"></page></link>.</p><h3>Zeroconf</h3><p><link><page ri:content-title="ZeroConf"></page></link> is a standard discovery specification that uses UDP / multicast to discovery devices. Its used by Apple's Rendezvous services.<br clear="none"> We use the <a shape="rect" href="http://jmdns.sf.net/">jmDNS</a> project to implement the Zeroconf specification to detect services. This means other Zeroconf<br clear="none"> based tools can be used in conjunction with this discovery agent.</p><p>To configure discovery in a Broker you should use the <link><page ri:content-title="Xml Configuration"></page></link>. Here is an <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/usecases/receiver-zeroconf.xml?view=co">example</a> of using discovery to create <link><page ri:content-title="Networks of Brokers"></page></link>.</p><p>If you have one or more brokers running with Zeroconf discovery enabled you can connect to a broker using the brokerURL</p><structured-macro ac:macro-id="f1747328-7dfc-4d75-beaa-110c0513fbed" ac:name="code" ac:schema-version="1"><plain-text-body>zeroconf:_activemq_development.
+</plain-text-body></structured-macro><p>This will use Zeroconf to find an available broker and one will be randomly chosen & things will auto-failover on disconnect if there are several brokers running.</p><h3>LDAP Discovery</h3><p>ActiveMQ supports the use of LDAP for discovery of brokers.</p><p>Please see <link><page ri:content-title="LDAP Broker Discovery Mechanism"></page></link> for more details.</p><h2>Trying out discovery</h2><p>If you run the following commands in separate shells you'll have 2 brokers auto-discovering themselves and 2 clients using fixed-URLs</p><structured-macro ac:macro-id="11d9cbdf-33c7-4f54-b9b6-ebb80e6fdcc8" ac:name="code" ac:schema-version="1"><plain-text-body>maven -o server -Dconfig=src/test/org/activemq/usecases/receiver-zeroconf.xml
maven -o server -Dconfig=src/test/org/activemq/usecases/sender-zeroconf.xml
maven -o consumer -Durl=tcp://localhost:62002
maven -o producer -Durl=tcp://localhost:62001
-]]></script>
-</div></div><p>If you want the clients to use discovery to find brokers, run either of the two 'server' statements above (or both) then run the producer/consumer as follows</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[maven -o consumer -Durl=zeroconf:_activemq.broker.development.
+</plain-text-body></structured-macro><p>If you want the clients to use discovery to find brokers, run either of the two 'server' statements above (or both) then run the producer/consumer as follows</p><structured-macro ac:macro-id="d61f046e-320e-45b1-8e46-119e1e612211" ac:name="code" ac:schema-version="1"><plain-text-body>maven -o consumer -Durl=zeroconf:_activemq.broker.development.
maven -o producer -Durl=zeroconf:_activemq.broker.development.
-]]></script>
-</div></div><p>The transport URL is of the format</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ zeroconf:<serviceName>
-]]></script>
-</div></div><p>where <em><serviceName></em> is the Zeroconf service name; which seems to start with an underscore (_) and must end with a dot (.). So we can use this service name to distinguish development, UAT & production brokers - or group them into domains etc.</p><h2 id="Discovery-DiscoveryandSecurity">Discovery and Security</h2><p>When using auto discovery of brokers an attacker may be able to present itself as a legitimate broker and by this way catch and / or manipulate all messages that run over it.</p><p>Are there security settings in auto discovery to avoid this?</p></div>
+</plain-text-body></structured-macro><p>The transport URL is of the format</p><structured-macro ac:macro-id="fae97634-2d5e-41b9-9ae6-ed05d453676d" ac:name="code" ac:schema-version="1"><plain-text-body> zeroconf:<serviceName>
+</plain-text-body></structured-macro><p>where <em><serviceName></em> is the Zeroconf service name; which seems to start with an underscore (_) and must end with a dot (.). So we can use this service name to distinguish development, UAT & production brokers - or group them into domains etc.</p><h2>Discovery and Security</h2><p>When using auto discovery of brokers an attacker may be able to present itself as a legitimate broker and by this way catch and / or manipulate all messages that run over it.</p><p>Are there security settings in auto discovery to avoid this?</p></div>
diff --git a/discussion-forums.xml b/discussion-forums.xml
index 2c8ebdb..adb6a94 100644
--- a/discussion-forums.xml
+++ b/discussion-forums.xml
@@ -1,13 +1,13 @@
-<div class="wiki-content maincontent"><p>Before posting you might want to read the <a shape="rect" href="tips-for-getting-help.xml">Tips for getting help</a>.</p>
+<div class="wiki-content maincontent"><p>Before posting you might want to read the <link><page ri:content-title="Tips for getting help"></page></link>.</p>
-<p>Many users prefer to use online forums rather than joining a mail list which can lead to lots more email traffic so we use the online forums at <a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/" rel="nofollow">Nabble forums</a> which also work with our <a shape="rect" href="mailing-lists.xml">Mailing Lists</a> so that both stay completely in sync. Use either the mailing lists or online forums, its completely up to you.</p>
+<p>Many users prefer to use online forums rather than joining a mail list which can lead to lots more email traffic so we use the online forums at <a shape="rect" href="http://activemq.2283324.n4.nabble.com/">Nabble forums</a> which also work with our <link><page ri:content-title="Mailing Lists"></page></link> so that both stay completely in sync. Use either the mailing lists or online forums, its completely up to you.</p>
-<h3 id="DiscussionForums-ActiveMQForums"><a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/" rel="nofollow">ActiveMQ Forums</a></h3>
+<h3><a shape="rect" href="http://activemq.2283324.n4.nabble.com/">ActiveMQ Forums</a></h3>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html" rel="nofollow">ActiveMQ User Forum</a></li><li><a shape="rect" class="external-link" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html" rel="nofollow">ActiveMQ Developer Forum</a></li></ul>
+<ul><li><a shape="rect" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html">ActiveMQ User Forum</a></li><li><a shape="rect" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html">ActiveMQ Developer Forum</a></li></ul>
-<h3 id="DiscussionForums-MailingLists">Mailing Lists</h3>
+<h3>Mailing Lists</h3>
-<p>If you prefer to use a mailing list instead then check out our <a shape="rect" href="mailing-lists.xml">Mailing Lists</a>. Note that the Forums and <a shape="rect" href="mailing-lists.xml">Mailing Lists</a> are kept in sync so its your choice which you use.</p></div>
+<p>If you prefer to use a mailing list instead then check out our <link><page ri:content-title="Mailing Lists"></page></link>. Note that the Forums and <link><page ri:content-title="Mailing Lists"></page></link> are kept in sync so its your choice which you use.</p></div>
diff --git a/dispatch-policies.xml b/dispatch-policies.xml
index c2adcfd..9b425d2 100644
--- a/dispatch-policies.xml
+++ b/dispatch-policies.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="DispatchPolicies-DispatchPolicies">Dispatch Policies</h1><h2 id="DispatchPolicies-Dispatchpoliciesforqueues">Dispatch policies for queues</h2><p>Plug-able dispatch policies only apply to topics. For Queues, dispatch is more static, you can choose round robin (the default) or strict order. Before discussing dispatch policies its worth first understanding <a shape="rect" href="what-is-the-prefetch-limit-for.xml">the purpose of the prefetch value</a>.</p><p>The out of the box configuration of ActiveMQ is designed for high performance and high throughput messaging where there are lots of messages that need to be dispatched to consumers as quickly as possible. So the default prefetch values are fairly large and the default dispatch policy will try and fill the prefetch buffers as quickly as possible.</p><p>However with messaging there are many use cases and sometimes the default configuration is not ideal to your use case; when you send a small number of messages, they tend to all go to one consumer unless you've lots of messages. If you have a large number of consumers and a relatively high <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch value</a> and you have a small number of messages that each message takes quite a while to process then the default dispatch policy might result in increasing the amount of time it takes to process all the messages (since the load balancing is not fair for small numbers of messages).</p><p>For queues, you can define whether the dispatch will occur in a round-robin fashion (default behaviour) or if one consumer's prefetch buffer will be exhausted before the dispatch process selects the next consumer along (strictOrderDispatch).<br clear="none"> The latter behaviour is enabled by setting the "strictOrderDispatch" attribute on the <policyEntry /> element. E.g.:</p><plain-text-body><policyEntry queue=">" strictOrderDispatch="false" /> </plain-text-body><p>Consumer priorities are observed, so if you have several consumers with different <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-priority.html">priorities</a>, the one with the highest priority will be flooded first until it can take no more, then the next one along, etc.</p><p>From version 5.14.0 - the strictOrderDispatch=true option will ensure strict order for redispatched messages when there is a single consumer. </p><h2 id="DispatchPolicies-DispatchpoliciesforTopics">Dispatch policies for Topics</h2><p>There are more options for topics because the dispatch policy is plug-able. Any implementation of org.apache.activemq.broker.region.policy.DispatchPolicy will work.<br clear="none"> The default org.apache.activemq.broker.region.policy.SimpleDispatchPolicy does what one would expect and delivers messages to all subscribers. An example of a more advanced implementation is the org.apache.activemq.broker.region.policy.PriorityNetworkDispatchPolicy which will only dispatch to the highest priority network consumer. This is useful in a loop network topology where there is more than route to a consumer.</p><p>Here is an <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/xbean/activemq-policy.xml">example of destination policy configuration</a>.</p><parameter ac:name="">xml</parameter><plain-text-body><destinationPolicy>
+<div class="wiki-content maincontent"><h1>Dispatch Policies</h1><h2>Dispatch policies for queues</h2><p>Plug-able dispatch policies only apply to topics. For Queues, dispatch is more static, you can choose round robin (the default) or strict order. Before discussing dispatch policies its worth first understanding <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>the purpose of the prefetch value</plain-text-link-body></link>.</p><p>The out of the box configuration of ActiveMQ is designed for high performance and high throughput messaging where there are lots of messages that need to be dispatched to consumers as quickly as possible. So the default prefetch values are fairly large and the default dispatch policy will try and fill the prefetch buffers as quickly as possible.</p><p>However with messaging there are many use cases and sometimes the default configuration is not ideal to your use case; when you send a small number of messages, they tend to all go to one consumer unless you've lots of messages. If you have a large number of consumers and a relatively high <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>prefetch value</plain-text-link-body></link> and you have a small number of messages that each message takes quite a while to process then the default dispatch policy might result in increasing the amount of time it takes to process all the messages (since the load balancing is not fair for small numbers of messages).</p><p>For queues, you can define whether the dispatch will occur in a round-robin fashion (default behaviour) or if one consumer's prefetch buffer will be exhausted before the dispatch process selects the next consumer along (strictOrderDispatch).<br clear="none"> The latter behaviour is enabled by setting the "strictOrderDispatch" attribute on the <policyEntry /> element. E.g.:</p><plain-text-body><policyEntry queue=">" strictOrderDispatch="false" /> </plain-text-body><p>Consumer priorities are observed, so if you have several consumers with different <a shape="rect" href="http://activemq.apache.org/consumer-priority.html">priorities</a>, the one with the highest priority will be flooded first until it can take no more, then the next one along, etc.</p><p>From version 5.14.0 - the strictOrderDispatch=true option will ensure strict order for redispatched messages when there is a single consumer. </p><h2>Dispatch policies for Topics</h2><p>There are more options for topics because the dispatch policy is plug-able. Any implementation of org.apache.activemq.broker.region.policy.DispatchPolicy will work.<br clear="none"> The default org.apache.activemq.broker.region.policy.SimpleDispatchPolicy does what one would expect and delivers messages to all subscribers. An example of a more advanced implementation is the org.apache.activemq.broker.region.policy.PriorityNetworkDispatchPolicy which will only dispatch to the highest priority network consumer. This is useful in a loop network topology where there is more than route to a consumer.</p><p>Here is an <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/xbean/activemq-policy.xml">example of destination policy configuration</a>.</p><parameter ac:name="">xml</parameter><plain-text-body><destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic="FOO.>">
diff --git a/does-activemq-support-clustering.xml b/does-activemq-support-clustering.xml
index a2de10a..693fef9 100644
--- a/does-activemq-support-clustering.xml
+++ b/does-activemq-support-clustering.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>Yes, though there are various kinds of clustering. See <a shape="rect" href="clustering.xml">this page on details</a></p></div>
+<p>Yes, though there are various kinds of clustering. See <link><page ri:content-title="Clustering"></page><link-body>this page on details</link-body></link></p></div>
diff --git a/does-activemq-support-my-sql-database.xml b/does-activemq-support-my-sql-database.xml
index 4eae899..26312be 100644
--- a/does-activemq-support-my-sql-database.xml
+++ b/does-activemq-support-my-sql-database.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent">
-<p>Quite possibly <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">. See the <a shape="rect" href="jdbc-support.xml">JDBC Support</a> page for details of how to configure for your database or how to let us know of a database which does not work. Also see <a shape="rect" href="persistence.xml">Persistence</a></p></div>
+<p>Quite possibly <emoticon ac:name="smile"></emoticon>. See the <link><page ri:content-title="JDBC Support"></page></link> page for details of how to configure for your database or how to let us know of a database which does not work. Also see <link><page ri:content-title="Persistence"></page></link></p></div>
diff --git a/download-archives.xml b/download-archives.xml
index 20974c9..7bfdd10 100644
--- a/download-archives.xml
+++ b/download-archives.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="DownloadArchives-Downloadarchives">Download archives</h2><p>You can use the Apache Archives to download all the ActiveMQ releases.</p><ul class="alternate"><li><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/">http://archive.apache.org/dist/activemq/</a> - ActiveMQ releases</li><li><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-activemq/">http://archive.apache.org/dist/activemq/apache-activemq/</a> - Even older ActiveMQ releases</li></ul><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Downloading</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The links below contains the release notes for all the ActiveMQ release. However if you want to download the release, you <strong>must</strong> use the download archives, which is the two links above.</p></div></div><p>All time Apache ActiveMQ releases notes:</p><p></p><ul class="childpages-macro"><li><a shape="rect" href="activemq-11-release.xml">ActiveMQ 1.1 Release</a></li><li><a shape="rect" href="activemq-12-release.xml">ActiveMQ 1.2 Release</a></li><li><a shape="rect" href="activemq-13-release.xml">ActiveMQ 1.3 Release</a></li><li><a shape="rect" href="activemq-14-release.xml">ActiveMQ 1.4 Release</a></li><li><a shape="rect" href="activemq-15-release.xml">ActiveMQ 1.5 Release</a></li><li><a shape="rect" href="activemq-20-release.xml">ActiveMQ 2.0 Release</a></li><li><a shape="rect" href="activemq-21-release.xml">ActiveMQ 2.1 Release</a></li><li><a shape="rect" href="activemq-30-release.xml">ActiveMQ 3.0 Release</a></li><li><a shape="rect" href="activemq-31-release.xml">ActiveMQ 3.1 Release</a></li><li><a shape="rect" href="activemq-321-release.xml">ActiveMQ 3.2.1 Release</a></li><li><a shape="rect" href="activemq-322-release.xml">ActiveMQ 3.2.2 Release</a></li><li><a shape="rect" href="activemq-32-release.xml">ActiveMQ 3.2 Release</a></li><li><a shape="rect" href="activemq-401-release.xml">ActiveMQ 4.0.1 Release</a></li><li><a shape="rect" href="activemq-402-release.xml">ActiveMQ 4.0.2 Release</a></li><li><a shape="rect" href="activemq-40-m4-release.xml">ActiveMQ 4.0 M4 Release</a></li><li><a shape="rect" href="activemq-40-rc2-release.xml">ActiveMQ 4.0 RC2 Release</a></li><li><a shape="rect" href="activemq-40-release.xml">ActiveMQ 4.0 Release</a></li><li><a shape="rect" href="activemq-410-release.xml">ActiveMQ 4.1.0 Release</a></li><li><a shape="rect" href="activemq-411-release.xml">ActiveMQ 4.1.1 Release</a></li><li><a shape="rect" href="activemq-412-release.xml">ActiveMQ 4.1.2 Release</a></li><li><a shape="rect" href="activemq-500-release.xml">ActiveMQ 5.0.0 Release</a></li><li><a shape="rect" href="activemq-510-release.xml">ActiveMQ 5.1.0 Release</a></li><li><a shape="rect" href="activemq-5100-release.xml">ActiveMQ 5.10.0 Release</a></li><li><a shape="rect" href="activemq-5101-release.xml">ActiveMQ 5.10.1 Release</a></li><li><a shape="rect" href="activemq-5102-release.xml">ActiveMQ 5.10.2 Release</a></li><li><a shape="rect" href="activemq-5110-release.xml">ActiveMQ 5.11.0 Release</a></li><li><a shape="rect" href="activemq-5111-release.xml">ActiveMQ 5.11.1 Release</a></li><li><a shape="rect" href="activemq-5112-release.xml">ActiveMQ 5.11.2 Release</a></li><li><a shape="rect" href="activemq-5113-release.xml">ActiveMQ 5.11.3 Release</a></li><li><a shape="rect" href="activemq-5120-release.xml">ActiveMQ 5.12.0 Release</a></li><li><a shape="rect" href="activemq-5121-release.xml">ActiveMQ 5.12.1 Release</a></li><li><a shape="rect" href="activemq-5122-release.xml">ActiveMQ 5.12.2 Release</a></li><li><a shape="rect" href="activemq-5130-release.xml">ActiveMQ 5.13.0 Release</a></li><li><a shape="rect" href="activemq-5131-release.xml">ActiveMQ 5.13.1 Release</a></li><li><a shape="rect" href="activemq-5132-release.xml">ActiveMQ 5.13.2 Release</a></li><li><a shape="rect" href="activemq-5133-release.xml">ActiveMQ 5.13.3 Release</a></li><li><a shape="rect" href="activemq-5134-release.xml">ActiveMQ 5.13.4 Release</a></li><li><a shape="rect" href="activemq-5140-release.xml">ActiveMQ 5.14.0 Release</a></li><li><a shape="rect" href="activemq-5141-release.xml">ActiveMQ 5.14.1 Release</a></li><li><a shape="rect" href="activemq-5142-release.xml">ActiveMQ 5.14.2 Release</a></li><li><a shape="rect" href="activemq-5143-release.xml">ActiveMQ 5.14.3 Release</a></li><li><a shape="rect" href="activemq-5144-release.xml">ActiveMQ 5.14.4 Release</a></li><li><a shape="rect" href="activemq-5145-release.xml">ActiveMQ 5.14.5 Release</a></li><li><a shape="rect" href="activemq-5150-release.xml">ActiveMQ 5.15.0 Release</a></li><li><a shape="rect" href="activemq-5151-release.xml">ActiveMQ 5.15.1 Release</a></li><li><a shape="rect" href="activemq-5152-release.xml">ActiveMQ 5.15.2 Release</a></li><li><a shape="rect" href="activemq-520-release.xml">ActiveMQ 5.2.0 Release</a></li><li><a shape="rect" href="activemq-530-release.xml">ActiveMQ 5.3.0 Release</a></li><li><a shape="rect" href="activemq-531-release.xml">ActiveMQ 5.3.1 Release</a></li><li><a shape="rect" href="activemq-532-release.xml">ActiveMQ 5.3.2 Release</a></li><li><a shape="rect" href="activemq-540-release.xml">ActiveMQ 5.4.0 Release</a></li><li><a shape="rect" href="activemq-541-release.xml">ActiveMQ 5.4.1 Release</a></li><li><a shape="rect" href="activemq-542-release.xml">ActiveMQ 5.4.2 Release</a></li><li><a shape="rect" href="activemq-543-release.xml">ActiveMQ 5.4.3 Release</a></li><li><a shape="rect" href="activemq-550-release.xml">ActiveMQ 5.5.0 Release</a></li><li><a shape="rect" href="activemq-551-release.xml">ActiveMQ 5.5.1 Release</a></li><li><a shape="rect" href="activemq-560-release.xml">ActiveMQ 5.6.0 Release</a></li><li><a shape="rect" href="activemq-570-release.xml">ActiveMQ 5.7.0 Release</a></li><li><a shape="rect" href="activemq-580-release.xml">ActiveMQ 5.8.0 Release</a></li><li><a shape="rect" href="activemq-590-release.xml">ActiveMQ 5.9.0 Release</a></li><li><a shape="rect" href="activemq-591-release.xml">ActiveMQ 5.9.1 Release</a></li><li><a shape="rect" href="in-progress.xml">In Progress</a></li></ul></div>
+<div class="wiki-content maincontent"><h2>Download archives</h2><p>You can use the Apache Archives to download all the ActiveMQ releases.</p><ul class="alternate"><li><a shape="rect" href="http://archive.apache.org/dist/activemq/">http://archive.apache.org/dist/activemq/</a> - ActiveMQ releases</li><li><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-activemq/">http://archive.apache.org/dist/activemq/apache-activemq/</a> - Even older ActiveMQ releases</li></ul><structured-macro ac:macro-id="32ec292d-4810-4e71-b56f-53b4642d6eb3" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Downloading</parameter><rich-text-body><p>The links below contains the release notes for all the ActiveMQ release. However if you want to download the release, you <strong>must</strong> use the download archives, which is the two links above.</p></rich-text-body></structured-macro><p>All time Apache ActiveMQ releases notes:</p><p><structured-macro ac:macro-id="3fb4e86e-9b48-453e-b111-88ec01910c7a" ac:name="children" ac:schema-version="1"><parameter ac:name="page"><link><page ri:content-title="Download"></page></link></parameter><parameter ac:name="sort">title</parameter></structured-macro></p></div>
diff --git a/download.xml b/download.xml
index 1967eb5..a2b15fa 100644
--- a/download.xml
+++ b/download.xml
@@ -1,11 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Download-LatestReleases">Latest Releases</h2><div class="sectionColumnWrapper"><div class="sectionMacro"><div class="sectionMacroRow"><div class="columnMacro" style="width:20%;min-width:20%;max-width:20%;"><div style="padding-right:20px;float:left;"><p> </p></div>
-
-
-</div><div class="columnMacro" style="width:80%;min-width:80%;max-width:80%;"><div style="min-height:200px"><p>The latest stable release is the <a shape="rect" href="activemq-5152-release.xml">ActiveMQ 5.15.2 Release</a></p></div>
-
-
-</div></div></div></div><h2 id="Download-Gettingpastreleases">Getting past releases</h2><p>See the <a shape="rect" href="download-archives.xml">Download Archives</a> for all time releases.</p><p></p><h2 id="Download-ReleasesInProgress">Releases In Progress</h2>
-
-<p>The following releases are currently in progress</p>
-<h2 id="Download-MavenRepositories">Maven Repositories</h2><p>All ActiveMQ releases are available from the <a shape="rect" class="external-link" href="https://repository.apache.org/content/repositories/releases/org/apache/activemq/">Maven central repository</a>.</p><p> </p></div>
+<div class="wiki-content maincontent"><h2>Latest Releases</h2><structured-macro ac:macro-id="1cafbdbf-a2ac-46ef-af1e-3c5603c896b9" ac:name="section" ac:schema-version="1"><rich-text-body><structured-macro ac:macro-id="b12d1a16-bf7f-4e71-8a63-67e33d2b2579" ac:name="column" ac:schema-version="1"><parameter ac:name="width">20%</parameter><rich-text-body><structured-macro ac:macro-id="6b90137d-36ce-42e9-9b97-797a38374053" ac:name="div" ac:schema-version="1"><parameter ac:name="style">padding-right:20px;float:left;</parameter><rich-text-body><p> </p></rich-text-body></structured-macro></rich-text-body></structured-macro><structured-macro ac:macro-id="b08e84a5-b461-4325-afd8-c82570122d65" ac:name="column" ac:schema-version="1"><parameter ac:name="width">80%</parameter><rich-text-body><structured-macro ac:macro-id="c8e895e7-88d5-48aa-b0f8-b09da5f8983f" ac:name="div" ac:schema-version="1"><parameter ac:name="style">min-height:200px</parameter><rich-text-body><p>The latest stable release is the <link><page ri:content-title="ActiveMQ 5.15.2 Release"></page></link></p></rich-text-body></structured-macro></rich-text-body></structured-macro></rich-text-body></structured-macro><h2>Getting past releases</h2><p>See the <link><page ri:content-title="Download Archives"></page></link> for all time releases.</p><p><structured-macro ac:macro-id="35f66c4e-eeb1-47b0-bf37-fa3c8c6dcfc2" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="In Progress"></page></link></parameter></structured-macro></p><h2>Maven Repositories</h2><p>All ActiveMQ releases are available from the <a shape="rect" href="https://repository.apache.org/content/repositories/releases/org/apache/activemq/">Maven central repository</a>.</p><p> </p></div>
diff --git a/downloading-activemq-cpp.xml b/downloading-activemq-cpp.xml
index 1f83ef7..051c039 100644
--- a/downloading-activemq-cpp.xml
+++ b/downloading-activemq-cpp.xml
@@ -1,20 +1,18 @@
-<div class="wiki-content maincontent"><p>ActiveMQ CPP distributions are source-only. To get the source bundle for a particular release, go <a shape="rect" href="download.xml">here</a>. Follow the instructions here only if you want the bleeding edge from trunk.</p>
+<div class="wiki-content maincontent"><p>ActiveMQ CPP distributions are source-only. To get the source bundle for a particular release, go <link><page ri:content-title="Download"></page><link-body>here</link-body></link>. Follow the instructions here only if you want the bleeding edge from trunk.</p>
-<h2 id="DownloadingActiveMQCPP-WebBrowsingofSVN">Web Browsing of SVN</h2>
+<h2>Web Browsing of SVN</h2>
<p>To browse via the web use the ViewVC interface:</p>
-<p><a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/activemq-cpp/trunk/activemq-cpp">http://svn.apache.org/viewvc/activemq/activemq-cpp/trunk/activemq-cpp</a></p>
+<p><a shape="rect" href="http://svn.apache.org/viewvc/activemq/activemq-cpp/trunk/activemq-cpp">http://svn.apache.org/viewvc/activemq/activemq-cpp/trunk/activemq-cpp</a></p>
<p>Or to browse the source tree directly:</p>
-<p><a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-cpp/trunk/activemq-cpp">https://svn.apache.org/repos/asf/activemq/activemq-cpp/trunk/activemq-cpp</a></p>
+<p><a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-cpp/trunk/activemq-cpp">https://svn.apache.org/repos/asf/activemq/activemq-cpp/trunk/activemq-cpp</a></p>
-<h2 id="DownloadingActiveMQCPP-CheckingoutfromSVN">Checking out from SVN </h2>
+<h2>Checking out from SVN </h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="fc547fb7-41b2-4d66-963b-e98964f12385" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-cpp/trunk/
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/durable-queue-memory-management.xml b/durable-queue-memory-management.xml
index ea57e74..afde918 100644
--- a/durable-queue-memory-management.xml
+++ b/durable-queue-memory-management.xml
@@ -3,31 +3,31 @@
<p>This page outlines design the design proposal.</p>
-<h2 id="DurableQueueMemoryManagement-TargetArea">TargetArea</h2>
+<h2>TargetArea</h2>
<p>Maintains TargetLists for each consumer (the messages that have matched one or more consumers's selectors and are gonna be used to try dispatch stuff to the consumer DispatchArea). TargetEntry objects are added to the TargetList as messages arrive from the Queue. </p>
<p>A TargetEntry can have either a direct Message reference or a CacheReference to an entry in a cache. </p>
-<h3 id="DurableQueueMemoryManagement-Eagerloading">Eager loading</h3>
+<h3>Eager loading</h3>
<p>Each TargetList has a watermark to indicate the first TargetEntry which is a CacheReference. The idea is that under ideal scenarios, each TargetList has the watermark equal to the high water mark (i.e. that there are enough direct message references in RAM).</p>
<p>So we can have a background thread increasing the watermark up to the ideal level - which means it starts at the current watermark and directly loads the objects; de-referencing the CacheReference and replacing with direct references. </p>
-<h3 id="DurableQueueMemoryManagement-PendingCache">PendingCache</h3>
+<h3>PendingCache</h3>
<p>TargetEntry objects added to the TargetList which are above the high watermark have their Message objects evicted from direct references into the PendingCache.</p>
<p>The Target eager loader will move objects from this cache to the TargetList when they are available. If they are not in the PendingCache, they are loaded from the QueueArea.</p>
-<h3 id="DurableQueueMemoryManagement-QueueArea">QueueArea</h3>
+<h3>QueueArea</h3>
<p>This represents the actual queue messages. There's also a matching HeadQueueCache which is a simple memory bound queue. FIFO so newer stuff is evicted from the end.</p>
<p>Back </p>
-<h3 id="DurableQueueMemoryManagement-LinkingtheCaches">Linking the Caches</h3>
+<h3>Linking the Caches</h3>
<p>The PendingCache and HeadQueueCache are linked together, along with the TargetArea/DispatchArea so that there is a fixed amount of RAM used in all the caches.</p>
diff --git a/encrypted-passwords.xml b/encrypted-passwords.xml
index 26aa92b..346c10b 100644
--- a/encrypted-passwords.xml
+++ b/encrypted-passwords.xml
@@ -1,61 +1,41 @@
-<div class="wiki-content maincontent"><p>As of ActiveMQ 5.4.1 you can encrypt your passwords and safely store them in configuration files. To encrypt the password, you can use the newly added <code>encrypt</code> command like:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ bin/activemq encrypt --password activemq --input mypassword
+<div class="wiki-content maincontent"><p>As of ActiveMQ 5.4.1 you can encrypt your passwords and safely store them in configuration files. To encrypt the password, you can use the newly added <code>encrypt</code> command like:</p><structured-macro ac:macro-id="a4cfbc62-bc63-4654-8acd-24413d0aa390" ac:name="code" ac:schema-version="1"><plain-text-body>$ bin/activemq encrypt --password activemq --input mypassword
...
-Encrypted text: eeWjNyX6FY8Fjp3E+F6qTytV11bZItDp]]></script>
-</div></div><p>Where the password you want to encrypt is passed with the <code>input</code> argument, while the <code>password</code> argument is a secret used by the encryptor. In a similar fashion you can test-out your passwords like:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ bin/activemq decrypt --password activemq --input eeWjNyX6FY8Fjp3E+F6qTytV11bZItDp
+Encrypted text: eeWjNyX6FY8Fjp3E+F6qTytV11bZItDp</plain-text-body></structured-macro><p>Where the password you want to encrypt is passed with the <code>input</code> argument, while the <code>password</code> argument is a secret used by the encryptor. In a similar fashion you can test-out your passwords like:</p><structured-macro ac:macro-id="c62647f7-a774-4f0c-ace3-f26dc2e9ebc9" ac:name="code" ac:schema-version="1"><plain-text-body>$ bin/activemq decrypt --password activemq --input eeWjNyX6FY8Fjp3E+F6qTytV11bZItDp
...
-Decrypted text: mypassword]]></script>
-</div></div><p><strong>Note:</strong> It is recommended that you use only alphanumeric characters for the password. Special characters, such as <code>$/^&</code>, are not supported.</p><p>The next step is to add the password to the appropriate configuration file, <code>$ACTIVEMQ_HOME/conf/credentials-enc.properties</code> by default.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[activemq.username=system
+Decrypted text: mypassword</plain-text-body></structured-macro><p><strong>Note:</strong> It is recommended that you use only alphanumeric characters for the password. Special characters, such as <code>$/^&</code>, are not supported.</p><p>The next step is to add the password to the appropriate configuration file, <code>$ACTIVEMQ_HOME/conf/credentials-enc.properties</code> by default.</p><structured-macro ac:macro-id="ee57e0c3-7e0c-4121-ba74-e8b2dc5b7b16" ac:name="code" ac:schema-version="1"><plain-text-body>activemq.username=system
activemq.password=ENC(mYRkg+4Q4hua1kvpCCI2hg==)
guest.password=ENC(Cf3Jf3tM+UrSOoaKU50od5CuBa8rxjoL)
...
jdbc.password=ENC(eeWjNyX6FY8Fjp3E+F6qTytV11bZItDp)
-]]></script>
-</div></div><p>Note that we used <code>ENC()</code> to wrap our encrypted passwords. You can mix plain and encrypted passwords in your properties files, so encrypted ones must be wrapped this way.</p><p>Finally, you need to instruct your property loader to encrypt variables when it loads properties to the memory. Instead of standard property loader we'll use the special one (see <code>\$ACTIVEMQ_HOME/conf/activemq-security.xml</code>) to achieve this.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="environmentVariablesConfiguration" class="org.jasypt.encryption.pbe.config.EnvironmentStringPBEConfig">
- <property name="algorithm" value="PBEWithMD5AndDES" />
- <property name="passwordEnvName" value="ACTIVEMQ_ENCRYPTION_PASSWORD" />
+</plain-text-body></structured-macro><p>Note that we used <code>ENC()</code> to wrap our encrypted passwords. You can mix plain and encrypted passwords in your properties files, so encrypted ones must be wrapped this way.</p><p>Finally, you need to instruct your property loader to encrypt variables when it loads properties to the memory. Instead of standard property loader we'll use the special one (see <code>\$ACTIVEMQ_HOME/conf/activemq-security.xml</code>) to achieve this.</p><structured-macro ac:macro-id="d8068f39-1db7-41d5-8520-5716dfa54be5" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="environmentVariablesConfiguration" class="org.jasypt.encryption.pbe.config.EnvironmentStringPBEConfig">
+ <property name="algorithm" value="PBEWithMD5AndDES" />
+ <property name="passwordEnvName" value="ACTIVEMQ_ENCRYPTION_PASSWORD" />
</bean>
-<bean id="configurationEncryptor" class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
- <property name="config" ref="environmentVariablesConfiguration" />
+<bean id="configurationEncryptor" class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
+ <property name="config" ref="environmentVariablesConfiguration" />
</bean>
-<bean id="propertyConfigurer" class="org.jasypt.spring31.properties.EncryptablePropertyPlaceholderConfigurer">
- <constructor-arg ref="configurationEncryptor" />
- <property name="location" value="file:${activemq.base}/conf/credentials-enc.properties"/>
-</bean>]]></script>
-</div></div><p>With this configuration ActiveMQ will try to load your encryptor password from the <code>ACTIVEMQ_ENCRYPTION_PASSWORD</code> environment variable and then use it to decrypt passwords from <code>credential-enc.properties</code> file.</p><p>Alternative is to use a simple variant and store encryptor password in the xml file, like this</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="configurationEncryptor" class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
- <property name="algorithm" value="PBEWithMD5AndDES"/>
- <property name="password" value="activemq"/>
-</bean>]]></script>
-</div></div><p>but with that you'll lose the secrecy of the encryptor's secret. You may also consult <a shape="rect" class="external-link" href="http://www.jasypt.org/advancedconfiguration.html" rel="nofollow">http://www.jasypt.org/advancedconfiguration.html</a> for more ideas on how to configure Jasypt.</p><p>Finally, we can use properties like we'd normally do</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<simpleAuthenticationPlugin>
+<bean id="propertyConfigurer" class="org.jasypt.spring31.properties.EncryptablePropertyPlaceholderConfigurer">
+ <constructor-arg ref="configurationEncryptor" />
+ <property name="location" value="file:${activemq.base}/conf/credentials-enc.properties"/>
+</bean></plain-text-body></structured-macro><p>With this configuration ActiveMQ will try to load your encryptor password from the <code>ACTIVEMQ_ENCRYPTION_PASSWORD</code> environment variable and then use it to decrypt passwords from <code>credential-enc.properties</code> file.</p><p>Alternative is to use a simple variant and store encryptor password in the xml file, like this</p><structured-macro ac:macro-id="ed075f5b-2bb9-4b47-b0a2-6f7374fa0824" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="configurationEncryptor" class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
+ <property name="algorithm" value="PBEWithMD5AndDES"/>
+ <property name="password" value="activemq"/>
+</bean></plain-text-body></structured-macro><p>but with that you'll lose the secrecy of the encryptor's secret. You may also consult <a shape="rect" href="http://www.jasypt.org/advancedconfiguration.html">http://www.jasypt.org/advancedconfiguration.html</a> for more ideas on how to configure Jasypt.</p><p>Finally, we can use properties like we'd normally do</p><structured-macro ac:macro-id="bc584b96-e1c6-4a03-bb9e-3a9b1a29a870" ac:name="code" ac:schema-version="1"><plain-text-body><simpleAuthenticationPlugin>
<users>
- <authenticationUser username="system" password="${activemq.password}"
- groups="users,admins"/>
- <authenticationUser username="user" password="${guest.password}"
- groups="users"/>
- <authenticationUser username="guest" password="${guest.password}" groups="guests"/>
+ <authenticationUser username="system" password="${activemq.password}"
+ groups="users,admins"/>
+ <authenticationUser username="user" password="${guest.password}"
+ groups="users"/>
+ <authenticationUser username="guest" password="${guest.password}" groups="guests"/>
</users>
-</simpleAuthenticationPlugin>]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
- <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
- <property name="url" value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
- <property name="username" value="activemq"/>
- <property name="password" value="${jdbc.password}"/>
- <property name="maxActive" value="200"/>
- <property name="poolPreparedStatements" value="true"/>
-</bean>]]></script>
-</div></div><p>If you want to run the broker with this configuration, you need to do the following:</p><ul><li><p>Set environment variable:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ export ACTIVEMQ_ENCRYPTION_PASSWORD=activemq]]></script>
-</div></div></li><li><p>Start the broker:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ bin/activemq start xbean:conf/activemq-security.xml]]></script>
-</div></div></li><li><p>Unset the environment variable:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ unset ACTIVEMQ_ENCRYPTION_PASSWORD]]></script>
-</div></div></li></ul><p>In this way your encryptor secret is never saved on your system and your encrypted passwords are safely stored in the configuration files.</p></div>
+</simpleAuthenticationPlugin></plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="2a8d90c3-6bb9-480f-9fb8-164c7d94761f" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
+ <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
+ <property name="url" value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
+ <property name="username" value="activemq"/>
+ <property name="password" value="${jdbc.password}"/>
+ <property name="maxActive" value="200"/>
+ <property name="poolPreparedStatements" value="true"/>
+</bean></plain-text-body></structured-macro><p>If you want to run the broker with this configuration, you need to do the following:</p><ul><li><p>Set environment variable:</p><structured-macro ac:macro-id="1ca2acff-d7df-4c4c-b8e9-4a4424beb0f1" ac:name="code" ac:schema-version="1"><plain-text-body>$ export ACTIVEMQ_ENCRYPTION_PASSWORD=activemq</plain-text-body></structured-macro></li><li><p>Start the broker:</p><structured-macro ac:macro-id="e3f2412b-28b1-4ecb-8821-0d369beb278b" ac:name="code" ac:schema-version="1"><plain-text-body>$ bin/activemq start xbean:conf/activemq-security.xml</plain-text-body></structured-macro></li><li><p>Unset the environment variable:</p><structured-macro ac:macro-id="4c104818-b20f-4a2f-80bc-f80afc233850" ac:name="code" ac:schema-version="1"><plain-text-body>$ unset ACTIVEMQ_ENCRYPTION_PASSWORD</plain-text-body></structured-macro></li></ul><p>In this way your encryptor secret is never saved on your system and your encrypted passwords are safely stored in the configuration files.</p></div>
diff --git a/enterprise-integration-patterns.xml b/enterprise-integration-patterns.xml
index 67c2f24..a7cec7d 100644
--- a/enterprise-integration-patterns.xml
+++ b/enterprise-integration-patterns.xml
@@ -1,55 +1,52 @@
-<div class="wiki-content maincontent"><h2 id="EnterpriseIntegrationPatterns-EnterpriseIntegrationPatterns">Enterprise Integration Patterns</h2>
+<div class="wiki-content maincontent"><h2>Enterprise Integration Patterns</h2>
-<p>Version 5.0 onwards of Apache ActiveMQ comes complete with full support for the <a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/toc.html" rel="nofollow">Enterprise Integration Patterns</a> (from the excellent book by <a shape="rect" class="external-link" href="http://www.amazon.com/exec/obidos/search-handle-url/105-9796798-8100401?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Gregor%20Hohpe" rel="nofollow">Gregor Hohpe</a> and <a shape="rect" class="external-link" href="http://www.amazon.com/exec/obidos/search-handle-url/105-9796798-8100401?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Bobby%20Woolf" rel="nofollow">Bobby Woolf</a>) via the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Apache Camel library</a>. </p>
+<p>Version 5.0 onwards of Apache ActiveMQ comes complete with full support for the <a shape="rect" href="http://www.enterpriseintegrationpatterns.com/toc.html">Enterprise Integration Patterns</a> (from the excellent book by <a shape="rect" href="http://www.amazon.com/exec/obidos/search-handle-url/105-9796798-8100401?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Gregor%20Hohpe">Gregor Hohpe</a> and <a shape="rect" href="http://www.amazon.com/exec/obidos/search-handle-url/105-9796798-8100401?%5Fencoding=UTF8&search-type=ss&index=books&field-author=Bobby%20Woolf">Bobby Woolf</a>) via the <a shape="rect" href="http://activemq.apache.org/camel/">Apache Camel library</a>. </p>
-<p>You can easily add any of the supported <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/enterprise-integration-patterns.html">Enterprise Integration Patterns</a> into ActiveMQ (either on the JMS client or in the broker process) to support smart routing, transformation and a whole host of other powerful patterns. You can of course just embed <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Camel library</a> directly into your application, such as via <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/spring.html">Spring</a> as well..</p>
+<p>You can easily add any of the supported <a shape="rect" href="http://activemq.apache.org/camel/enterprise-integration-patterns.html">Enterprise Integration Patterns</a> into ActiveMQ (either on the JMS client or in the broker process) to support smart routing, transformation and a whole host of other powerful patterns. You can of course just embed <a shape="rect" href="http://activemq.apache.org/camel/">Camel library</a> directly into your application, such as via <a shape="rect" href="http://activemq.apache.org/camel/spring.html">Spring</a> as well..</p>
-<p>This also means you can cleanly integrate all of the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/components.html">Camel Components</a> into ActiveMQ so you can easily integrate with <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/cxf.html">CXF</a>, <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/file.html">Files</a>, <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/jbi.html">JBI</a>, <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/jpa.html">JPA</a>, <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/mail.html">Mail</a>, <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/mina.html">MINA</a>, <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/quartz.html">Quartz</a>, <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/xmpp.html">XMPP</a> and <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/components.html">many other protocols and transports!</a></p>
+<p>This also means you can cleanly integrate all of the <a shape="rect" href="http://activemq.apache.org/camel/components.html">Camel Components</a> into ActiveMQ so you can easily integrate with <a shape="rect" href="http://activemq.apache.org/camel/cxf.html">CXF</a>, <a shape="rect" href="http://activemq.apache.org/camel/file.html">Files</a>, <a shape="rect" href="http://activemq.apache.org/camel/jbi.html">JBI</a>, <a shape="rect" href="http://activemq.apache.org/camel/jpa.html">JPA</a>, <a shape="rect" href="http://activemq.apache.org/camel/mail.html">Mail</a>, <a shape="rect" href="http://activemq.apache.org/camel/mina.html">MINA</a>, <a shape="rect" href="http://activemq.apache.org/camel/quartz.html">Quartz</a>, <a shape="rect" href="http://activemq.apache.org/camel/xmpp.html">XMPP</a> and <a shape="rect" href="http://activemq.apache.org/camel/components.html">many other protocols and transports!</a></p>
-<h3 id="EnterpriseIntegrationPatterns-UsingEIPintheActiveMQBroker">Using EIP in the ActiveMQ Broker</h3>
+<h3>Using EIP in the ActiveMQ Broker</h3>
<p>The broker's <strong>activemq.xml</strong> file comes already configured to support Camel; you just need to customize the routing rules.</p>
-<h4 id="EnterpriseIntegrationPatterns-WritingEIPrulesusingJavacode">Writing EIP rules using Java code</h4>
+<h4>Writing EIP rules using Java code</h4>
-<p>To use <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/dsl.html">Java code to write EIP routing rules</a>, just put your classes on the classpath (such as in activemq/lib/myroutes/foo.jar). Then to get Camel to find your routes you need to edit the activemq.xml so that the <strong>packages</strong> attribute points to the package name (or a parent package name) to look for.</p>
+<p>To use <a shape="rect" href="http://activemq.apache.org/camel/dsl.html">Java code to write EIP routing rules</a>, just put your classes on the classpath (such as in activemq/lib/myroutes/foo.jar). Then to get Camel to find your routes you need to edit the activemq.xml so that the <strong>packages</strong> attribute points to the package name (or a parent package name) to look for.</p>
<p>For example if all your routes are in the package org.acme.cheese; such as org.acme.cheese.whatnot.MyRouter then you could edit the XML to be...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<camelContext xmlns="http://activemq.apache.org/camel/schema/spring">
+<structured-macro ac:macro-id="08391332-f1a6-460a-bfe5-58a3b1d4cc39" ac:name="code" ac:schema-version="1"><plain-text-body>
+<camelContext xmlns="http://activemq.apache.org/camel/schema/spring">
<package>org.acme.cheese</package>
</camelContext>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="EnterpriseIntegrationPatterns-WritingEIPrulesusingXML">Writing EIP rules using XML</h4>
+<h4>Writing EIP rules using XML</h4>
-<p>To use XML its even easier, as you can just embed whatever routing rules inside the <camelContext> element using Camel's <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/xml-configuration.html">Spring XML format</a>. Note that the XML is way more verbose than the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/dsl.html">Java DSL</a> but it is a bit simpler to deploy. e.g. for a trivial route...</p>
+<p>To use XML its even easier, as you can just embed whatever routing rules inside the <camelContext> element using Camel's <a shape="rect" href="http://activemq.apache.org/camel/xml-configuration.html">Spring XML format</a>. Note that the XML is way more verbose than the <a shape="rect" href="http://activemq.apache.org/camel/dsl.html">Java DSL</a> but it is a bit simpler to deploy. e.g. for a trivial route...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<camelContext xmlns="http://activemq.apache.org/camel/schema/spring">
+<structured-macro ac:macro-id="a14e2d08-d3c4-484d-8b0c-71443cb4ef06" ac:name="code" ac:schema-version="1"><plain-text-body>
+<camelContext xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
- <from uri="activemq:com.acme.MyQueue"/>
- <to uri="activemq:com.acme.SomeOtherQueue"/>
+ <from uri="activemq:com.acme.MyQueue"/>
+ <to uri="activemq:com.acme.SomeOtherQueue"/>
</route>
</camelContext>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="EnterpriseIntegrationPatterns-UsingEIPintheJMSclient">Using EIP in the JMS client</h3>
+<h3>Using EIP in the JMS client</h3>
-<p>You can use <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Camel</a> <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/endpoint.html">Endpoints</a> directly from your JMS client one of the following JMS destinations, depending on what JMS API you want it to use</p>
+<p>You can use <a shape="rect" href="http://activemq.apache.org/camel/">Camel</a> <a shape="rect" href="http://activemq.apache.org/camel/endpoint.html">Endpoints</a> directly from your JMS client one of the following JMS destinations, depending on what JMS API you want it to use</p>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/camel/CamelDestination.html">CamelDestination</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/camel/CamelQueue.html">CamelQueue</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/camel/CamelTopic.html">CamelTopic</a></li></ul>
+<ul><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/camel/CamelDestination.html">CamelDestination</a></li><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/camel/CamelQueue.html">CamelQueue</a></li><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/camel/CamelTopic.html">CamelTopic</a></li></ul>
-<p>You can then use this destination like any other JMS destination when sending or receiving messages! This means you can use any of the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/components.html">large number of Camel components</a> from your JMS code, by just changing the Destination object!</p>
+<p>You can then use this destination like any other JMS destination when sending or receiving messages! This means you can use any of the <a shape="rect" href="http://activemq.apache.org/camel/components.html">large number of Camel components</a> from your JMS code, by just changing the Destination object!</p>
-<h3 id="EnterpriseIntegrationPatterns-SeeAlso">See Also</h3>
+<h3>See Also</h3>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/camel/enterprise-integration-patterns.html">Enterprise Integration Patterns</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/camel/components.html">Camel Components</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/camel/xml-reference.html">Camel XML Reference</a></li></ul></div>
+<ul><li><a shape="rect" href="http://activemq.apache.org/camel/enterprise-integration-patterns.html">Enterprise Integration Patterns</a></li><li><a shape="rect" href="http://activemq.apache.org/camel/components.html">Camel Components</a></li><li><a shape="rect" href="http://activemq.apache.org/camel/xml-reference.html">Camel XML Reference</a></li></ul>
+</div>
diff --git a/errors.xml b/errors.xml
index 32219c4..c24ff71 100644
--- a/errors.xml
+++ b/errors.xml
@@ -1,6 +1,6 @@
<div class="wiki-content maincontent">
-<p>Questions on specific kinds of errors. If you have seen a specific exception then check the <a shape="rect" href="exceptions.xml">Exceptions</a></p>
+<p>Questions on specific kinds of errors. If you have seen a specific exception then check the <link><page ri:content-title="Exceptions"></page></link></p>
-<ul class="childpages-macro"><li><a shape="rect" href="could-not-find-packetreader-for-packet-type-unknown-packet-type.xml">Could not find PacketReader for packet type - UNKNOWN PACKET TYPE</a></li><li><a shape="rect" href="exceptions.xml">Exceptions</a><ul class="childpages-macro"><li><a shape="rect" href="certificateunknown.xml">certificate_unknown</a></li><li><a shape="rect" href="ioexception-could-not-find-class-for-resource.xml">IOException - could not find class for resource</a></li><li><a shape="rect" href="javaiointerruptedioexception.xml">java.io.InterruptedIOException</a></li><li><a shape="rect" href="javaioioexception-failed-to-create-database-derbydb-see-the-next-exception-for-details.xml">java.io.IOException Failed to create database 'derbydb', see the next exception for details</a></li><li><a shape="rect" href="javalangnosuchmethoderror.xml">java.lang.NoSuchMethodError</a></li><li><a shape="rect" href="javalangnosuchmethodexception-orgactivemqraactivemqresourceadaptersetuseembeddedbroker.xml">java.lang.NoSuchMethodException org.activemq.ra.ActiveMQResourceAdapter.setUseEmbeddedBroker</a></li><li><a shape="rect" href="javalangoutofmemory.xml">java.lang.OutOfMemory</a></li><li><a shape="rect" href="javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml">javax.jms.JMSException - Wire format negociation timeout - peer did not send his wire format.</a></li><li><a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI () needs 2.1 API.</a></li><li><a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-xxx-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (xxx) needs 2.1 API</a></li><li><a shape="rect" href="journal-is-already-opened-by-this-application.xml">Journal is already opened by this application</a></li><li><a shape="rect" href="noclassdeffounderror-orgspringframeworkcoreioresource.xml">NoClassDefFoundError - org.springframework.core.io.Resource</a></li><li><a shape="rect" href="no-suitable-driver.xml">No suitable driver</a></li></ul></li><li><a shape="rect" href="i-am-having-problems-with-the-spring-jmstemplate.xml">I am having problems with the Spring JmsTemplate</a></li><li><a shape="rect" href="i-am-not-receiving-any-messages-what-is-wrong.xml">I am not receiving any messages, what is wrong</a></li><li><a shape="rect" href="i-cannot-connect-to-activemq-from-jconsole.xml">I cannot connect to ActiveMQ from JConsole</a></li><li><a shape="rect" href="i-do-not-receive-messages-in-my-second-consumer.xml">I do not receive messages in my second consumer</a></li><li><a shape="rect" href="i-get-errors-building-the-code-whats-wrong.xml">I get errors building the code whats wrong</a></li><li><a shape="rect" href="log4j-warn-no-appenders-could-be-found-for-logger.xml">log4j-WARN No appenders could be found for logger</a></li><li><a shape="rect" href="multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.xml">Multicast - Watch out for IPV6 vs IPV4 support on your operating system or distribution or network</a></li><li><a shape="rect" href="my-producer-blocks.xml">My producer blocks</a></li><li><a shape="rect" href="onmessage-method-of-messagelistener-is-never-called.xml">onMessage method of MessageListener is never called</a></li><li><a shape="rect" href="resource-adapter-does-not-seem-to-pool-connections.xml">Resource Adapter does not seem to pool connections</a></li><li><a shape="rect" href="slow-networks-drop-large-messages.xml">Slow networks drop large messages</a></li><li><a shape="rect" href="the-broker-will-not-start.xml">The Broker will not start</a></li><li><a shape="rect" href="the-vm-transport-starts-a-broker-before-my-configured-broker-starts.xml">The vm transport starts a broker before my configured broker starts</a></li><li><a shape="rect" href="why-do-i-not-get-all-of-the-messages-i-sent.xml">Why do I not get all of the messages I sent</a></li><li><a shape="rect" href="why-do-i-not-receive-messages-on-my-durable-topic-subscription.xml">Why do I not receive messages on my durable topic subscription</a></li><li><a shape="rect" href="why-do-kahadb-log-files-remain-after-cleanup.xml">Why do KahaDB log files remain after cleanup</a></li></ul></div>
+<structured-macro ac:macro-id="973fda2c-e36b-4969-941e-e4322b544111" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/example-testing-scenario.xml b/example-testing-scenario.xml
index 8993c80..da4b748 100644
--- a/example-testing-scenario.xml
+++ b/example-testing-scenario.xml
@@ -1,9 +1,9 @@
-<div class="wiki-content maincontent"><h2 id="ExampleTestingScenario-ActiveMQPerformanceModule">ActiveMQ Performance Module</h2>
+<div class="wiki-content maincontent"><h2>ActiveMQ Performance Module</h2>
-<ul><li><a shape="rect" href="activemq-performance-module-users-manual.xml">Users Manual</a></li></ul>
+<ul><li><link><page ri:content-title="ActiveMQ Performance Module Users Manual"></page><link-body>Users Manual</link-body></link></li></ul>
-<h2 id="ExampleTestingScenario-ExampleTestingScenario">Example Testing Scenario</h2>
+<h2>Example Testing Scenario</h2>
<p>This page gives a simple example of the kinds of thing we wanna do.</p>
@@ -11,62 +11,58 @@
<p>We'll try describe the different ways this could work and give each implementation style a name so we can start revving different ways to solve this...</p>
-<h3 id="ExampleTestingScenario-Headlessbuild">Headless build</h3>
+<h3>Headless build</h3>
<p>In this version there is no 'controller'; each build is considered to be a totally separate build.</p>
<p>Each build knows what to do; each test case generates an XML file which becomes a named deployment artifact.</p>
<p>e.g. imagine the following builds (which are really just running Java executables within a POM for classpath)</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Box </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Command line </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> hostB </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Broker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> java org.apache.activemq.broker.console.Main tcp://$hostA:61616 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> hostC </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> java org.apache.activemq.test.ConsumerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> hostD </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Producer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> java org.apache.activemq.test.ProducerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Box </p></th><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Command line </p></th></tr><tr><td colspan="1" rowspan="1"><p> hostB </p></td><td colspan="1" rowspan="1"><p> Broker </p></td><td colspan="1" rowspan="1"><p> java org.apache.activemq.broker.console.Main tcp://$hostA:61616 </p></td></tr><tr><td colspan="1" rowspan="1"><p> hostC </p></td><td colspan="1" rowspan="1"><p> Consumer </p></td><td colspan="1" rowspan="1"><p> java org.apache.activemq.test.ConsumerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616 </p></td></tr><tr><td colspan="1" rowspan="1"><p> hostD </p></td><td colspan="1" rowspan="1"><p> Producer </p></td><td colspan="1" rowspan="1"><p> java org.apache.activemq.test.ProducerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616 </p></td></tr></tbody></table>
<p>In the above example - each build has to kinda wait for other things to start up to some time period. e.g. the producer and consumer wanna keep around for say 5 minutes trying to connect to the broker as they can be started in any order.</p>
<p>Ideally we might wanna run this as 3 maven commands as follows...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="38e63ecb-031a-4d14-af75-5f75f99487f0" ac:name="code" ac:schema-version="1"><plain-text-body>
mvn activemq:broker
mvn activemq:perf-producer -Dmessage-count=5000 -Dqueue=true -Ddestination=org.foo.bar -Durl=tcp://$hostA:61616
mvn activemq:perf-consumer -Dmessage-count=5000 -Dqueue=true -Ddestination=org.foo.bar -Durl=tcp://$hostA:61616
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="ExampleTestingScenario-Controllerbuild">Controller build</h3>
+<h3>Controller build</h3>
<p>The idea with the controller version is one of the tests (which is spun off first to try help) tries to coordinate among the test nodes.</p>
<p>e.g. we could spin the controller first...</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Box </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Command line </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> hostA </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Controller </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> mvn test </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Box </p></th><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Command line </p></th></tr><tr><td colspan="1" rowspan="1"><p> hostA </p></td><td colspan="1" rowspan="1"><p> Controller </p></td><td colspan="1" rowspan="1"><p> mvn test </p></td></tr></tbody></table>
<p>Then the test case fires off these processes while communicating with them...</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Box </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Command line </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> hostB </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Broker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> java org.apache.activemq.broker.console.Main tcp://$hostA:61616 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> hostC </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> java org.apache.activemq.test.ConsumerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> hostD </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Producer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> java org.apache.activemq.test.ProducerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Box </p></th><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Command line </p></th></tr><tr><td colspan="1" rowspan="1"><p> hostB </p></td><td colspan="1" rowspan="1"><p> Broker </p></td><td colspan="1" rowspan="1"><p> java org.apache.activemq.broker.console.Main tcp://$hostA:61616 </p></td></tr><tr><td colspan="1" rowspan="1"><p> hostC </p></td><td colspan="1" rowspan="1"><p> Consumer </p></td><td colspan="1" rowspan="1"><p> java org.apache.activemq.test.ConsumerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616 </p></td></tr><tr><td colspan="1" rowspan="1"><p> hostD </p></td><td colspan="1" rowspan="1"><p> Producer </p></td><td colspan="1" rowspan="1"><p> java org.apache.activemq.test.ProducerMain --message-count=5000 --queue=true --destination=org.foo.bar tcp://$hostA:61616 </p></td></tr></tbody></table>
-<h3 id="ExampleTestingScenario-Controllerfactorybuild">Controller factory build</h3>
+<h3>Controller factory build</h3>
<p>Fairly soon we're gonna have tons of builds firing off. We may want a single project to build with a raft of different test suites. Each single distributed integration/system/performance test might have many sub-builds (processes) to run.</p>
<p>So we might want to run a single JUnit test case which fires off different remote builds/processes.</p>
<p>e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e913d0b3-10e0-47da-bfd9-a0e44571b677" ac:name="code" ac:schema-version="1"><plain-text-body>
public class PerformanceTestSuite {
public void testSmallMessages() {
- buildQueue.start("broker", "");
- buildQueue.start("consumer", "--messageCount=1000");
- buildQueue.start("producer", "--messageCount=1000");
+ buildQueue.start("broker", "");
+ buildQueue.start("consumer", "--messageCount=1000");
+ buildQueue.start("producer", "--messageCount=1000");
buildQueue.join(5 * MINUTES);
}
public void testLargeMessages() {
- buildQueue.start("broker", "");
- buildQueue.start("consumer", "--messageCount=1000 --messageSize=1M");
- buildQueue.start("producer", "--messageCount=1000 --messageSize=1M");
+ buildQueue.start("broker", "");
+ buildQueue.start("consumer", "--messageCount=1000 --messageSize=1M");
+ buildQueue.start("producer", "--messageCount=1000 --messageSize=1M");
buildQueue.join(10 * MINUTES);
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>So these 2 test cases in JUnit in the controller build will each start 3 separate remote builds on the queue and wait for them to complete - or terminate them </p></div>
diff --git a/examples.xml b/examples.xml
index 2dec1c9..ab6d915 100644
--- a/examples.xml
+++ b/examples.xml
@@ -1,34 +1,2 @@
-<div class="wiki-content maincontent"><p>Since version<strong> 5.12.0</strong>, Apache ActiveMQ comes with the new tool that can be used to produce and consume messages from the broker.</p><h2 id="Examples-Prerequisites"><span style="color: rgb(34,34,34);">Prerequisites</span></h2><p><span style="color: rgb(34,34,34);"> </span></p><p>Before running the examples you should try <a shape="rect" href="run-broker.xml">running a JMS broker</a> on your machine. Follow the <a shape="rect" href="installation.xml">Installation</a> instructions to use a binary distribution of ActiveMQ. To run the broker in a command shell, type:</p><p><span style="color: rgb(34,34,34);"> </span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console
-]]></script>
-</div></div><p><span style="color: rgb(34,34,34);"> </span></p><p>This starts up ActiveMQ.</p><h2 id="Examples-Running">Running</h2><p>From the<a shape="rect" href="unix-shell-script.xml"> command line</a> you can run</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[${ACTIVEMQ_HOME}/bin/activemq producer
-${ACTIVEMQ_HOME}/bin/activemq consumer]]></script>
-</div></div><p> </p><p>If you have <code>activemq-all</code> jar available you can achieve the same with</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[java -jar activemq-all-5.x.x.jar producer
-java -jar activemq-all-5.x.x.jar consumer]]></script>
-</div></div><p>If you run inside <a shape="rect" href="osgi-integration.xml">Karaf</a>, you can run the commands as</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[activemq:producer
-activemq:consumer]]></script>
-</div></div><p> </p><h2 id="Examples-Options">Options</h2><p>For all options on the commands, run them with <code>--help</code> parameter. The up to date, options for <a shape="rect" class="external-link" href="https://github.com/apache/activemq/blob/master/activemq-console/src/main/resources/org/apache/activemq/console/command/producer.txt" rel="nofollow">producer</a> and <a shape="rect" class="external-link" href="https://github.com/apache/activemq/blob/master/activemq-console/src/main/resources/org/apache/activemq/console/command/consumer.txt" rel="nofollow">consumer</a> can be found in the source.</p><h2 id="Examples-Examples">Examples</h2><p>Here are a couple of examples of more advanced features.</p><p>To send a text message with custom text use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq producer --message "My message" --messageCount 1
-]]></script>
-</div></div><p>To send byte message of custom length use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq producer --messageSize 100 --messageCount 1
-]]></script>
-</div></div><p>To send a text message with content obtained from an url</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq producer --payloadUrl http://activemq.apache.org/schema/core/activemq-core.xsd --messageCount 1]]></script>
-</div></div><p>To consume in transaction use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq consumer --transacted true
-]]></script>
-</div></div><p>To use client acknowledgment use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq consumer --ackMode CLIENT_ACKNOWLEDGE
-]]></script>
-</div></div><p>To use durable topic subscribers use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq consumer --durable true --clientId example --destination topic://TEST
-]]></script>
-</div></div><h2 id="Examples-Oldexamples">Old examples</h2><p>In older versions of ActiveMQ, the corresponding examples were located in <code>examples/</code> or <code>examples/openwire/swissarmy/</code> directories, where you can do the similar tasks with an ant script.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ant producer
-ant consumer]]></script>
-</div></div><h2 id="Examples-Otherexamples">Other examples</h2><p>In <code>examples/</code> directory (depending on the version) you can find more examples of using the broker with variety of protocols (mqtt, amqp, ...) and clients (Java, Ruby, JavaScript, ...), so it's the good place to start learning. Also, <code>examples/conf/</code> directory contains a lot of different configuration examples that you can use as a starting point for your deployment.</p><h2 id="Examples-SeeAlso">See Also</h2><ul><li><a shape="rect" href="web-samples.xml">Web Samples</a></li><li><a shape="rect" href="web-console.xml">Web Console</a></li><li><a shape="rect" href="jmx.xml">JMX</a></li></ul></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="0968c863-7ab1-4077-92f7-e8476aa32b06" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Version 5 Examples"></page></link></parameter></structured-macro></p></div>
diff --git a/exceptions.xml b/exceptions.xml
index 9cc4439..8d7059d 100644
--- a/exceptions.xml
+++ b/exceptions.xml
@@ -2,5 +2,5 @@
<p>Questions Java Exceptions (when you get a nasty stack trace while working with ActiveMQ)</p>
-<ul class="childpages-macro"><li><a shape="rect" href="certificateunknown.xml">certificate_unknown</a></li><li><a shape="rect" href="ioexception-could-not-find-class-for-resource.xml">IOException - could not find class for resource</a></li><li><a shape="rect" href="javaiointerruptedioexception.xml">java.io.InterruptedIOException</a></li><li><a shape="rect" href="javaioioexception-failed-to-create-database-derbydb-see-the-next-exception-for-details.xml">java.io.IOException Failed to create database 'derbydb', see the next exception for details</a></li><li><a shape="rect" href="javalangnosuchmethoderror.xml">java.lang.NoSuchMethodError</a></li><li><a shape="rect" href="javalangnosuchmethodexception-orgactivemqraactivemqresourceadaptersetuseembeddedbroker.xml">java.lang.NoSuchMethodException org.activemq.ra.ActiveMQResourceAdapter.setUseEmbeddedBroker</a></li><li><a shape="rect" href="javalangoutofmemory.xml">java.lang.OutOfMemory</a></li><li><a shape="rect" href="javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml">javax.jms.JMSException - Wire format negociation timeout - peer did not send his wire format.</a></li><li><a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI () needs 2.1 API.</a></li><li><a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-xxx-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (xxx) needs 2.1 API</a></li><li><a shape="rect" href="journal-is-already-opened-by-this-application.xml">Journal is already opened by this application</a></li><li><a shape="rect" href="noclassdeffounderror-orgspringframeworkcoreioresource.xml">NoClassDefFoundError - org.springframework.core.io.Resource</a></li><li><a shape="rect" href="no-suitable-driver.xml">No suitable driver</a></li></ul></div>
+<structured-macro ac:macro-id="7157e88d-4129-4eae-8f4e-8e19923d3fa8" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/exclusive-consumer.xml b/exclusive-consumer.xml
index c14435d..6ffdc68 100644
--- a/exclusive-consumer.xml
+++ b/exclusive-consumer.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h3 id="ExclusiveConsumer-Background">Background</h3>
+<div class="wiki-content maincontent"><h3>Background</h3>
<p>We maintain the order of messages in queues and dispatch them to consumers in order. However if you have multiple JMS Sessions and MessageConsumer instances consuming from the same queue (whether in the same JVM or not), you will loose the guarantee of processing the messages in order; since the messages with be processed concurrently in different threads.</p>
@@ -6,7 +6,7 @@
<p>So what folks have to do in J2EE clusters is often to <em>pin</em> one particular JVM in the cluster to have <em>one</em> consumer on the queue to avoid loosing ordering. The problem with this is that if the particular pinned JVM goes down, no one is processing the queue any more, which can be problem.</p>
-<h3 id="ExclusiveConsumer-ExclusiveConsumer">Exclusive Consumer</h3>
+<h3>Exclusive Consumer</h3>
<p>We have a new feature in 4.x called Exclusive Consumer or Exclusive Queues which avoids the end user having to <em>pin</em> anything. The broker will pick a single MessageConsumer to get all the messages for a queue to ensure ordering. If that consumer fails, the broker will auto failover and choose another consumer.</p>
@@ -14,14 +14,12 @@
<p>For those who've struggled with pinning JMS consumers in J2EE clusters you'll immediately realize how useful this is to making clustered, high available distributed services.</p>
-<h3 id="ExclusiveConsumer-Example">Example</h3>
+<h3>Example</h3>
-<p>An Exclusive Consumer is created using <a shape="rect" href="destination-options.xml">Destination Options</a> as follows:</p>
+<p>An Exclusive Consumer is created using <link><page ri:content-title="Destination Options"></page></link> as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-queue = new ActiveMQQueue("TEST.QUEUE?consumer.exclusive=true");
+<structured-macro ac:macro-id="d264c935-8140-47cb-beee-f71ddae49a5a" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
+queue = new ActiveMQQueue("TEST.QUEUE?consumer.exclusive=true");
consumer = session.createConsumer(queue);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/failover-transport-reference.xml b/failover-transport-reference.xml
index 45204b4..a5ac212 100644
--- a/failover-transport-reference.xml
+++ b/failover-transport-reference.xml
@@ -1,31 +1,13 @@
-<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. The configuration syntax allows you to specify any number of composite URIs. The Failover transport randomly chooses one of the composite URIs and attempts to establish a connection to it. If it does not succeed, or if it subsequently fails, a new connection is established choosing one of the other URIs randomly from the list.</p><p> </p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Configuration Syntax</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><code><strong>failover:(uri1,...,uriN)?transportOptions&nestedURIOptions</strong></code></p><p>or</p><p><code><strong>failover:uri1,...,uriN</strong></code></p></div></div><p> </p><p>Example:<strong><br clear="none"></strong></p><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><h4 id="FailoverTransportReference-TransportOptions">Transport Options</h4><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><code>backup</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></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><code>initialReconnectDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The delay (in ms) before the <em>first</em> reconnect attempt.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxCacheSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>131072</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Size in bytes for the cache of tracked messages.</p><p>Applicable only if <strong><code>trackMessages</code></strong> is <strong><code>true</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxReconnectAttempts</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1 | 0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>From ActiveMQ 5.6</strong>: default is <strong><code>-1</code></strong>, retry forever. <strong><code>0</code></strong> means disables re-connection, e.g: just try to connect once.<br clear="none" class="atl-forced-newline"> <strong>Before ActiveMQ 5.6</strong>: default is <strong><code>0</code></strong>, retry forever. <br clear="none" class="atl-forced-newline"> <strong>All ActiveMQ versions</strong>: a value <strong><code>>0</code></strong> denotes 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><code>maxReconnectDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum delay (in ms) between the <em>second and subsequent</em> reconnect attempts.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>nested.*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>From ActiveMQ 5.9:</strong> common URI options that will be applied to each URI in the list<strong>.</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>randomize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, choose a URI at random from the list to use for reconnect.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>reconnectDelayExponent</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>2.0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The exponent used during exponential back-off attempts.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>reconnectSupported</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Determines whether the client should respond to broker <strong><code>ConnectionControl</code></strong> events with a reconnect (see: <strong><code>rebalanceClusterClients</code>).</strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>startupMaxReconnectAttempts</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A value of <strong><code>-1</code></strong> denotes that the number of connection attempts at startup should be unlimited.</p><p>A value of  <strong><code>>=0 </code></strong>denotes the number of reconnect attempts at startup that will be made after which an error is sent back to the client when the client makes a subsequent reconnect attempt.</p><p><strong>Note</strong>: once successfully connected the <code><strong>maxReconnectAttempts</strong></code> option prevails.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>From ActiveMQ 5.3</strong>: set the timeout on send operations (in ms) without interruption of re-connection process. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trackMessages</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></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><code>updateURIsSupported</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>From</strong><strong> ActiveMQ 5.4:</strong> determines whether the client should accept updates from the broker to its list of known URIs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateURIsURL</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>From ActiveMQ 5.4:</strong> 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. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useExponentialBackOff</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> an exponential back-off is used between reconnect attempts.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>warnAfterReconnectAttempts</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>From ActiveMQ 5.10:</strong> a value <strong><code>>0</code></strong> specifies the number of reconnect attempts before a warning is logged. A logged warning indicates that there is no current connection but re-connection is being attempted.</p><p>A value of <strong><code><=0</code></strong> disables the logging of warnings about reconnect attempts. </p></td></tr></tbody></table></div><p> </p><h4 id="FailoverTransportReference-UsingRandomize">Using Randomize</h4><p>The Failover transport chooses a URI at random by default. This effectively load-balances clients over multiple brokers. However, to have a client connect to a primary first and only connect to a secondary backup broker when the primary is unavailable, set <strong><code>randomize=false</code></strong>.</p><p>Example:</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-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 shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/transport/TransportListener.html">TransportListener</a> directly on the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a>, so that it is in place before any request that may require a network hop or second, set the <strong><code>timeout</code></strong> option. The <strong><code>timeout</code></strong> option causes the current send operation to fail after the specified timeout.</p><p>Example:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>failover:(tcp://primary:61616)?timeout=3000
-</pre>
-</div></div><p>In this example if the connection isn't established the send operation will timeout after 3 seconds. It is important to note that the connection <em>is not killed</em> when a timeout occurs. It is possible, therefore, to resend the affected message(s) later using the <em>same</em> connection once a broker becomes available.</p><h5 id="FailoverTransportReference-Transactions">Transactions</h5><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 can interfere with newly delivered messages. This can lead to unacknowledged messages.</p><p><strong>From ActiveMQ 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 <strong><code>javax.jms.</code><code>TransactionRolledBackException</code></strong> 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 not possible to know the exact point of failure. Did failure happen because the transaction commit message was not delivered or was the commit reply lost? In either case, it becomes necessary to rollback the transaction so that the application can get an indication of the failure and deal with any potential problem.</p><h5 id="FailoverTransportReference-Broker-sideOptionsforFailover">Broker-side Options for Failover</h5><p><strong>From ActiveMQ 5.4</strong>: the <strong><code>TransportConnector</code></strong> 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><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><code>updateClusterClients</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, pass information to connected clients about changes in the topology of the broker cluster.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>rebalanceClusterClients</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, connected clients will be asked to re-balance across a cluster of brokers when a new broker joins the network of brokers (note: <strong><code>priorityBackup=true</code></strong> can override).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterClientsOnRemove</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, will update clients when a cluster is removed from the network. Having this as separate option enables clients to be updated when new brokers join, but <em>not</em> when brokers leave.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>updateClusterFilter</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Comma separated list of regular expression filters used to match broker names of brokers to designate as being part of the failover cluster for the clients.</p></td></tr></tbody></table></div><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Confluence" type="syntaxhighlighter"><![CDATA[<broker>
+<div class="wiki-content maincontent"><h3>The Failover Transport</h3><p>The Failover transport layers reconnect logic on top of any of the other transports. The configuration syntax allows you to specify any number of composite URIs. The Failover transport randomly chooses one of the composite URIs and attempts to establish a connection to it. If it does not succeed, or if it subsequently fails, a new connection is established choosing one of the other URIs randomly from the list.</p><p> </p><structured-macro ac:macro-id="d39731b4-a16a-40b6-929b-c69f97aec3f2" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Configuration Syntax</parameter><rich-text-body><p><code><strong>failover:(uri1,...,uriN)?transportOptions&nestedURIOptions</strong></code></p><p>or</p><p><code><strong>failover:uri1,...,uriN</strong></code></p></rich-text-body></structured-macro><p> </p><p>Example:<strong><br clear="none"></strong></p><structured-macro ac:macro-id="bc1fc833-6442-4c03-99ba-18b2e895565f" ac:name="noformat" ac:schema-version="1"><plain-text-body>failover:(tcp://localhost:61616,tcp://remotehost:61616)?initialReconnectDelay=100
+</plain-text-body></structured-macro><h4>Transport Options</h4><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>backup</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Initialize and hold a second transport connection - to enable fast failover.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>initialReconnectDelay</code></p></td><td colspan="1" rowspan="1"><p><code>10</code></p></td><td colspan="1" rowspan="1"><p>The delay (in ms) before the <em>first</em> reconnect attempt.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxCacheSize</code></p></td><td colspan="1" rowspan="1"><p><code>131072</code></p></td><td colspan="1" rowspan="1"><p>Size in bytes for the cache of tracked messages.</p><p>Applicable only if <strong><code>trackMessages</code></strong> is <strong><code>true</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxReconnectAttempts</code></p></td><td colspan="1" rowspan="1"><p><code>-1 | 0</code></p></td><td colspan="1" rowspan="1"><p><strong>From ActiveMQ 5.6</strong>: default is <strong><code>-1</code></strong>, retry forever. <strong><code>0</code></strong> means disables re-connection, e.g: just try to connect once.<br clear="none" class="atl-forced-newline"> <strong>Before ActiveMQ 5.6</strong>: default is <strong><code>0</code></strong>, retry forever. <br clear="none" class="atl-forced-newline"> <strong>All ActiveMQ versions</strong>: a value <strong><code>>0</code></strong> denotes the maximum number of reconnect attempts before an error is sent back to the client.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxReconnectDelay</code></p></td><td colspan="1" rowspan="1"><p><code>30000</code></p></td><td colspan="1" rowspan="1"><p>The maximum delay (in ms) between the <em>second and subsequent</em> reconnect attempts.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>nested.*</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><strong>From ActiveMQ 5.9:</strong> common URI options that will be applied to each URI in the list<strong>.</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>randomize</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, choose a URI at random from the list to use for reconnect.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>reconnectDelayExponent</code></p></td><td colspan="1" rowspan="1"><p><code>2.0</code></p></td><td colspan="1" rowspan="1"><p>The exponent used during exponential back-off attempts.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>reconnectSupported</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Determines whether the client should respond to broker <strong><code>ConnectionControl</code></strong> events with a reconnect (see: <strong><code>rebalanceClusterClients</code>).</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>startupMaxReconnectAttempts</code></p></td><td colspan="1" rowspan="1"><p><code>-1</code></p></td><td colspan="1" rowspan="1"><p>A value of <strong><code>-1</code></strong> denotes that the number of connection attempts at startup should be unlimited.</p><p>A value of  <strong><code>>=0 </code></strong>denotes the number of reconnect attempts at startup that will be made after which an error is sent back to the client when the client makes a subsequent reconnect attempt.</p><p><strong>Note</strong>: once successfully connected the <code><strong>maxReconnectAttempts</strong></code> option prevails.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>timeout</code></p></td><td colspan="1" rowspan="1"><p><code>-1</code></p></td><td colspan="1" rowspan="1"><p><strong>From ActiveMQ 5.3</strong>: set the timeout on send operations (in ms) without interruption of re-connection process. </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>trackMessages</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><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"><p><code>updateURIsSupported</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><strong>From</strong><strong> ActiveMQ 5.4:</strong> determines whether the client should accept updates from the broker to its list of known URIs.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>updateURIsURL</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p><strong>From ActiveMQ 5.4:</strong> 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. </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useExponentialBackOff</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> an exponential back-off is used between reconnect attempts.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>warnAfterReconnectAttempts</code></p></td><td colspan="1" rowspan="1"><p><code>10</code></p></td><td colspan="1" rowspan="1"><p><strong>From ActiveMQ 5.10:</strong> a value <strong><code>>0</code></strong> specifies the number of reconnect attempts before a warning is logged. A logged warning indicates that there is no current connection but re-connection is being attempted.</p><p>A value of <strong><code><=0</code></strong> disables the logging of warnings about reconnect attempts. </p></td></tr></tbody></table><p> </p><h4>Using Randomize</h4><p>The Failover transport chooses a URI at random by default. This effectively load-balances clients over multiple brokers. However, to have a client connect to a primary first and only connect to a secondary backup broker when the primary is unavailable, set <strong><code>randomize=false</code></strong>.</p><p>Example:</p><structured-macro ac:macro-id="c9a3b254-4e38-4aff-b023-15778e60ef4b" ac:name="noformat" ac:schema-version="1"><plain-text-body>failover:(tcp://primary:61616,tcp://secondary:61616)?randomize=false
+</plain-text-body></structured-macro><h5>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 shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/transport/TransportListener.html">TransportListener</a> directly on the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a>, so that it is in place before any request that may require a network hop or second, set the <strong><code>timeout</code></strong> option. The <strong><code>timeout</code></strong> option causes the current send operation to fail after the specified timeout.</p><p>Example:</p><structured-macro ac:macro-id="54687531-328b-49c5-802c-658731fa1711" ac:name="noformat" ac:schema-version="1"><plain-text-body>failover:(tcp://primary:61616)?timeout=3000
+</plain-text-body></structured-macro><p>In this example if the connection isn't established the send operation will timeout after 3 seconds. It is important to note that the connection <em>is not killed</em> when a timeout occurs. It is possible, therefore, to resend the affected message(s) later using the <em>same</em> connection once a broker becomes available.</p><h5>Transactions</h5><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 can interfere with newly delivered messages. This can lead to unacknowledged messages.</p><p><strong>From ActiveMQ 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 <strong><code>javax.jms.</code><code>TransactionRolledBackException</code></strong> 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 not possible to know the exact point of failure. Did failure happen because the transaction commit message was not delivered or was the commit reply lost? In either case, it becomes necessary to rollback the transaction so that the application can get an indication of the failure and deal with any potential problem.</p><h5>Broker-side Options for Failover</h5><p><strong>From ActiveMQ 5.4</strong>: the <strong><code>TransportConnector</code></strong> 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><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>updateClusterClients</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, pass information to connected clients about changes in the topology of the broker cluster.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>rebalanceClusterClients</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, connected clients will be asked to re-balance across a cluster of brokers when a new broker joins the network of brokers (note: <strong><code>priorityBackup=true</code></strong> can override).</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>updateClusterClientsOnRemove</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, will update clients when a cluster is removed from the network. Having this as separate option enables clients to be updated when new brokers join, but <em>not</em> when brokers leave.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>updateClusterFilter</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>Comma separated list of regular expression filters used to match broker names of brokers to designate as being part of the failover cluster for the clients.</p></td></tr></tbody></table><p>Example:</p><structured-macro ac:macro-id="591e8d97-f040-4870-8ac8-9f0577e9b0a2" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="theme">Confluence</parameter><plain-text-body><broker>
...
<transportConnectors>
- <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" updateClusterClients="true" updateClusterFilter=".*A.*,.*B.*"/>
+ <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" updateClusterClients="true" updateClusterFilter=".*A.*,.*B.*"/>
</<transportConnectors>
...
</broker>
-]]></script>
-</div></div><p>When <strong><code>updateClusterClients=true</code></strong> clients need only be configured with the details of one broker in a cluster in order to connect.</p><p>Example:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>failover:(tcp://primary:61616)
-</pre>
-</div></div><p>When new brokers join the cluster the client is automatically informed of the new broker's URI. The new URI is then available for failover when one of the other known brokers becomes unavailable.</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Additional Information</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">See the following blog entry about using the cluster client updates and re-balancing features titled <a shape="rect" class="external-link" href="http://bsnyderblog.blogspot.com/2010/10/new-features-in-activemq-54-automatic.html" rel="nofollow">New Features in ActiveMQ 5.4: Automatic Cluster Update and Rebalance</a>.</div></div><h5 id="FailoverTransportReference-PriorityBackup">Priority Backup</h5><p><strong>From ActiveMQ 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 <strong><code>priorityBackup</code></strong> and <strong><code>priorityURIs</code></strong> options.</p><p>Consider the following URL:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>failover:(tcp://local:61616,tcp://remote:61616)?randomize=false&priorityBackup=true</pre>
-</div></div><p>Given this URL a client will try to connect and stay connected to the <strong><code>local</code></strong> broker. If <strong><code>local</code></strong> broker fails, it will of course fail over to <strong><code>remote</code></strong>. However, as <strong><code>priorityBackup</code></strong> parameter is used, the client will constantly try to reconnect to <strong><code> local</code></strong>. Once the client can do so, the client will re-connect to it without any need for manual intervention.</p><p>By default, only the first URI in the list is considered prioritized (<strong><code>local</code></strong>). In most cases this will suffice. However, in some cases it may be necessary to have multiple "local" URIs. The <strong><code>priorityURIs</code></strong> option can be used to specify which URIs are considered prioritized.</p><p>Example:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>failover:(tcp://local1:61616,tcp://local2:61616,tcp://remote:61616)?randomize=false&priorityBackup=true&priorityURIs=tcp://local1:61616,tcp://local2:61616</pre>
-</div></div><p>In this case the client will prioritize either <strong><code>local1</code></strong> or <strong><code>local2</code></strong> brokers and (re-)connect to them if they are available.</p><h5 id="FailoverTransportReference-ConfiguringNestedURIOptions.">Configuring Nested URI Options.</h5><p><span style="color: rgb(255,0,0);"><span style="color: rgb(0,0,0);"><strong>From ActiveMQ 5.9</strong></span></span>: 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: <strong><code>nested.</code></strong> </p><p>Example - instead of doing this:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>failover:(tcp://broker1:61616?wireFormat.maxInactivityDuration=1000,tcp://broker2:61616?wireFormat.maxInactivityDuration=1000,tcp://broker3:61616?wireFormat.maxInactivityDuration=1000) </pre>
-</div></div><p>do this:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>failover:(tcp://broker1:61616,tcp://broker2:61616,tcp://broker3:61616)?nested.wireFormat.maxInactivityDuration=1000</pre>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">Any option that can applied to the query string of an individual URI is a candidate for use with the <strong><code>nested</code></strong> option.</div></div><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Option Precedence</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">If the same option is specified as both an individual URI option <em>and</em> as a nested option, the nested option definition will take precedence.</div></div><p> </p><p> </p><p> </p><p> </p></div>
+</plain-text-body></structured-macro><p>When <strong><code>updateClusterClients=true</code></strong> clients need only be configured with the details of one broker in a cluster in order to connect.</p><p>Example:</p><structured-macro ac:macro-id="99da95ca-95f9-4ecc-827e-61a16fab74e9" ac:name="noformat" ac:schema-version="1"><plain-text-body>failover:(tcp://primary:61616)
+</plain-text-body></structured-macro><p>When new brokers join the cluster the client is automatically informed of the new broker's URI. The new URI is then available for failover when one of the other known brokers becomes unavailable.</p><structured-macro ac:macro-id="0462312a-5b88-4989-aeb3-50ea736dce4e" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Additional Information</parameter><rich-text-body>See the following blog entry about using the cluster client updates and re-balancing features titled <a shape="rect" href="http://bsnyderblog.blogspot.com/2010/10/new-features-in-activemq-54-automatic.html">New Features in ActiveMQ 5.4: Automatic Cluster Update and Rebalance</a>.</rich-text-body></structured-macro><h5>Priority Backup</h5><p><strong>From ActiveMQ 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 <strong><code>priorityBackup</code></strong> and <strong><code>priorityURIs</code></strong> options.</p><p>Consider the following URL:</p><structured-macro ac:macro-id="90acedcc-f375-42b7-9768-744527d3cd9b" ac:name="noformat" ac:schema-version="1"><plain-text-body>failover:(tcp://local:61616,tcp://remote:61616)?randomize=false&priorityBackup=true</plain-text-body></structured-macro><p>Given this URL a client will try to connect and stay connected to the <strong><code>local</code></strong> broker. If <strong><code>local</code></strong> broker fails, it will of course fail over to <strong><code>remote</code></strong>. However, as <strong><code>priorityBackup</code></strong> parameter is used, the client will constantly try to reconnect to <strong><code> local</code></strong>. Once the client can do so, the client will re-connect to it without any need for manual intervention.</p><p>By default, only the first URI in the list is considered prioritized (<strong><code>local</code></strong>). In most cases this will suffice. However, in some cases it may be necessary to have multiple "local" URIs. The <strong><code>priorityURIs</code></strong> option can be used to specify which URIs are considered prioritized.</p><p>Example:</p><structured-macro ac:macro-id="e7114c68-8a0d-467e-af8f-f0cd720513ed" ac:name="noformat" ac:schema-version="1"><plain-text-body>failover:(tcp://local1:61616,tcp://local2:61616,tcp://remote:61616)?randomize=false&priorityBackup=true&priorityURIs=tcp://local1:61616,tcp://local2:61616</plain-text-body></structured-macro><p>In this case the client will prioritize either <strong><code>local1</code></strong> or <strong><code>local2</code></strong> brokers and (re-)connect to them if they are available.</p><h5>Configuring Nested URI Options.</h5><p><span style="color: rgb(255,0,0);"><span style="color: rgb(0,0,0);"><strong>From ActiveMQ 5.9</strong></span></span>: 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: <strong><code>nested.</code></strong> </p><p>Example - instead of doing this:</p><structured-macro ac:macro-id="bb73f89c-526b-4c8b-8c13-740e6921273c" ac:name="noformat" ac:schema-version="1"><plain-text-body>failover:(tcp://broker1:61616?wireFormat.maxInactivityDuration=1000,tcp://broker2:61616?wireFormat.maxInactivityDuration=1000,tcp://broker3:61616?wireFormat.maxInactivityDuration=1000) </plain-text-body></structured-macro><p>do this:</p><structured-macro ac:macro-id="e4f99a01-55da-44f7-8af7-743e32eb9107" ac:name="noformat" ac:schema-version="1"><plain-text-body>failover:(tcp://broker1:61616,tcp://broker2:61616,tcp://broker3:61616)?nested.wireFormat.maxInactivityDuration=1000</plain-text-body></structured-macro><structured-macro ac:macro-id="9c23d901-5052-481c-aeac-02971ab370cf" ac:name="info" ac:schema-version="1"><rich-text-body>Any option that can applied to the query string of an individual URI is a candidate for use with the <strong><code>nested</code></strong> option.</rich-text-body></structured-macro><structured-macro ac:macro-id="49f2ce50-8238-4833-a982-e54504803684" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Option Precedence</parameter><rich-text-body>If the same option is specified as both an individual URI option <em>and</em> as a nested option, the nested option definition will take precedence.</rich-text-body></structured-macro><p> </p><p> </p><p> </p><p> </p></div>
diff --git a/fanout-transport-reference.xml b/fanout-transport-reference.xml
index bf5154e..08422ae 100644
--- a/fanout-transport-reference.xml
+++ b/fanout-transport-reference.xml
@@ -1,51 +1,44 @@
-<div class="wiki-content maincontent"><h3 id="FanoutTransportReference-TheFanoutTransport">The Fanout Transport</h3>
+<div class="wiki-content maincontent"><h3>The Fanout Transport</h3>
-<p>The Fanout transport layers reconnect and replication logic on top of any of the other transports. It utilizes the <a shape="rect" href="discovery-transport-reference.xml">Discovery</a> transport to discover brokers and replicates commands to those brokers.</p>
+<p>The Fanout transport layers reconnect and replication logic on top of any of the other transports. It utilizes the <link><page ri:content-title="Discovery Transport Reference"></page><link-body>Discovery</link-body></link> transport to discover brokers and replicates commands to those brokers.</p>
-<h4 id="FanoutTransportReference-ConfigurationSyntax">Configuration Syntax</h4>
+<h4>Configuration Syntax</h4>
<p><strong>fanout:(discoveryURI)?transportOptions</strong><br clear="none">
or<br clear="none">
<strong>fanout:discoveryURI</strong></p>
-<h5 id="FanoutTransportReference-TransportOptions">Transport Options</h5>
+<h5>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</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</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useExponentialBackOff</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>backOffMultiplier</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>2</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>0</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</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>fanOutQueues</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If set to 'true', commands are replicated to queues as well as topics</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>minAckCount</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The minimum number of brokers to which connections must be established</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>initialReconnectDelay</p></td><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>How long to wait before the first reconnect attempt</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxReconnectDelay</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>The maximum amount of time we ever wait between reconnect attempts</p></td></tr><tr><td colspan="1" rowspan="1"><p>useExponentialBackOff</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should an exponential backoff be used btween reconnect attempts</p></td></tr><tr><td colspan="1" rowspan="1"><p>backOffMultiplier</p></td><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>The exponent used in the exponential backoff attempts</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxReconnectAttempts</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>If not 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"><p>fanOutQueues</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If set to 'true', commands are replicated to queues as well as topics</p></td></tr><tr><td colspan="1" rowspan="1"><p>minAckCount</p></td><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>The minimum number of brokers to which connections must be established</p></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>
<p>By default, a client's fanout transport waits for connections to be established to 2 brokers, or the number of static TCP URIs configured (if more than 2). Until this number of connections is established, the client's call to Connection.createSession() does not return. For example, a producer that uses the fanout connector listed below will wait until 2 brokers are running, and connections are established to those two brokers. </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="14dfe3e4-da24-4f67-ae01-1c3435c1ada2" ac:name="code" ac:schema-version="1"><plain-text-body>
fanout:(multicast://default)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Another example would be a producer using the following fanout connector. </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6ab706dc-d1f3-409b-a0cc-e7dd193f7f09" ac:name="code" ac:schema-version="1"><plain-text-body>
fanout:(static:(tcp://localhost:61629,tcp://localhost:61639,tcp://localhost:61649))
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>In this case, three broker connections are needed. However, this required number of connections can be overridden by using the minAckCount transport option. For example, this fanout connector allows the producer to run after connecting to just one broker.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="015aa0e2-b6a4-445d-ba33-ebad5395e4be" ac:name="code" ac:schema-version="1"><plain-text-body>
fanout:(multicast://default)?minAckCount=1
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>It is not recommended that you use the fanout URI for consumers. Also, if a producer fans out across multiple brokers, who happen to be inter-connected, then there is a very high likelihood that a consumer on one of those brokers will get duplicate messages.</p></div></div>
+<structured-macro ac:macro-id="151fccae-78c3-4ec7-a133-2f736fa215f4" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body>
+<p>It is not recommended that you use the fanout URI for consumers. Also, if a producer fans out across multiple brokers, who happen to be inter-connected, then there is a very high likelihood that a consumer on one of those brokers will get duplicate messages.</p></rich-text-body></structured-macro>
-<h5 id="FanoutTransportReference-ExampleURI">Example URI</h5>
+<h5>Example URI</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>fanout:(static:(tcp://localhost:61616,tcp://remotehost:61616))?initialReconnectDelay=100
-</pre>
-</div></div>
+<structured-macro ac:macro-id="93ce1f99-ce3f-4d11-8d29-062d4c587a36" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+fanout:(static:(tcp://localhost:61616,tcp://remotehost:61616))?initialReconnectDelay=100
+</plain-text-body></structured-macro>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Applying parameters to discovered transports</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Because the Discovery transport is utilized for broker discovery, transport parameters are applied to discovered brokers. See <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport Reference</a>.</p></div></div></div>
+<structured-macro ac:macro-id="aa78e70d-2f24-413a-97b1-54cf7ebb24a8" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Applying parameters to discovered transports</parameter><rich-text-body>
+<p>Because the Discovery transport is utilized for broker discovery, transport parameters are applied to discovered brokers. See <link><page ri:content-title="Discovery Transport Reference"></page></link>.</p></rich-text-body></structured-macro></div>
diff --git a/faq.xml b/faq.xml
index c5dec84..cad40af 100644
--- a/faq.xml
+++ b/faq.xml
@@ -1,65 +1,43 @@
-<div class="wiki-content maincontent"><h2 id="FAQ-FAQ">FAQ</h2>
+<div class="wiki-content maincontent"><h2>FAQ</h2>
-<p>Here are a list of commonly asked questions and answers. If you have any questions which are not on this list, please talk to us on the <a shape="rect" href="discussion-forums.xml">forums</a>. </p>
+<p>Here are a list of commonly asked questions and answers. If you have any questions which are not on this list, please talk to us on the <link><page ri:content-title="Discussion Forums"></page><link-body>forums</link-body></link>. </p>
-<p>We <a shape="rect" href="contributing.xml">welcome contributions</a> and this entire website is a <a shape="rect" href="how-does-the-website-work.xml">wiki that you can edit</a> so please join in and help us make the documentation better!</p>
+<p>We <link><page ri:content-title="Contributing"></page><link-body>welcome contributions</link-body></link> and this entire website is a <link><page ri:content-title="How does the website work"></page><link-body>wiki that you can edit</link-body></link> so please join in and help us make the documentation better!</p>
-<h3 id="FAQ-General"><a shape="rect" href="general.xml">General</a></h3>
+<h3><link><page ri:content-title="General"></page></link></h3>
+<structured-macro ac:macro-id="9965a8dd-121e-405c-a8f6-bd636d0f8f66" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="General"></page></link></parameter></structured-macro>
+<h3><link><page ri:content-title="JMS"></page></link></h3>
+<structured-macro ac:macro-id="17d3399c-8878-4e5c-8581-083615ad8c32" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="JMS"></page></link></parameter></structured-macro>
-<p>General questions about ActiveMQ</p>
+<h3><link><page ri:content-title="Using Apache ActiveMQ"></page></link></h3>
-<ul class="childpages-macro"><li><a shape="rect" href="can-i-get-commercial-support.xml">Can I get commercial support</a></li><li><a shape="rect" href="how-can-i-get-help.xml">How can I get help</a></li><li><a shape="rect" href="how-can-i-get-the-source-code-from-subversion.xml">How can I get the source code from subversion</a></li><li><a shape="rect" href="how-does-activemq-compare-to-amqp.xml">How does ActiveMQ compare to AMQP</a></li><li><a shape="rect" href="how-does-activemq-compare-to-artemis.xml">How does ActiveMQ compare to Artemis</a></li><li><a shape="rect" href="how-does-activemq-compare-to-fuse-message-broker.xml">How does ActiveMQ compare to Fuse Message Broker</a></li><li><a shape="rect" href="how-does-activemq-compare-to-jbossmq.xml">How does ActiveMQ compare to JBossMQ</a></li><li><a shape="rect" href="how-does-activemq-compare-to-mantaray.xml">How does ActiveMQ compare to Mantaray</a></li><li><a shape="rect" href="how-does-activemq-compare-to-mule.xml">How does ActiveMQ compare to Mule</a></li><li><a shape="rect" href="how-does-activemq-compare-to-spread-toolkit.xml">How does ActiveMQ compare to Spread Toolkit</a></li><li><a shape="rect" href="how-does-openwire-compare-to-stomp.xml">How does OpenWire compare to Stomp</a></li><li><a shape="rect" href="how-does-the-website-work.xml">How does the website work</a></li><li><a shape="rect" href="how-do-i-avoid-maven-downloading-latest-jars.xml">How do I avoid Maven downloading latest jars</a></li><li><a shape="rect" href="how-do-i-build-but-disable-the-unit-tests.xml">How do I build but disable the unit tests</a></li><li><a shape="rect" href="how-do-i-compile-from-the-source.xml">How do I compile from the source</a></li><li><a shape="rect" href="how-do-i-edit-the-website.xml">How do I edit the website</a></li><li><a shape="rect" href="how-fast-is-activemq.xml">How fast is ActiveMQ</a></li><li><a shape="rect" href="should-i-run-activemq-on-windows-in-a-directory-with-spaces.xml">Should I run ActiveMQ on Windows in a directory with spaces</a></li><li><a shape="rect" href="what-is-activemq.xml">What is ActiveMQ</a></li><li><a shape="rect" href="what-is-the-license.xml">What is the license</a></li><li><a shape="rect" href="what-jars-do-i-need.xml">What jars do I need</a></li><li><a shape="rect" href="what-open-source-integration-solution-works-best-with-activemq.xml">What open source integration solution works best with ActiveMQ</a></li><li><a shape="rect" href="what-platforms-does-activemq-support.xml">What platforms does ActiveMQ support</a></li><li><a shape="rect" href="what-version-should-i-use.xml">What version should I use</a></li></ul>
+<structured-macro ac:macro-id="2aae721f-14c9-4c89-89f9-7889c8c8ffc2" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Using Apache ActiveMQ"></page></link></parameter></structured-macro>
-<h3 id="FAQ-JMS"><a shape="rect" href="jms.xml">JMS</a></h3>
+<h3><link><page ri:content-title="Configuration"></page></link></h3>
+<structured-macro ac:macro-id="674e4dec-d64f-42e2-aed1-1816cba23995" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Configuration"></page></link></parameter></structured-macro>
-<p>Questions on using the JMS API and <a shape="rect" href="mom.xml">MOM</a> in general</p>
+<h3><link><page ri:content-title="Persistence Questions"></page></link></h3>
-<ul class="childpages-macro"><li><a shape="rect" href="can-i-modify-messages-on-a-queue.xml">Can I modify messages on a queue</a></li><li><a shape="rect" href="can-i-send-and-receive-messages-concurrently-on-one-jms-connection.xml">Can I send and receive messages concurrently on one JMS Connection</a></li><li><a shape="rect" href="can-you-browse-a-topic.xml">Can you browse a topic</a></li><li><a shape="rect" href="how-do-durable-queues-and-topics-work.xml">How do durable queues and topics work</a></li><li><a shape="rect" href="how-does-a-queue-compare-to-a-topic.xml">How does a Queue compare to a Topic</a></li><li><a shape="rect" href="how-does-connectionfactory-relate-to-the-broker.xml">How does ConnectionFactory relate to the Broker</a></li><li><a shape="rect" href="how-does-jms-compare-with-email.xml">How does JMS compare with email</a></li><li><a shape="rect" href="how-do-i-consume-a-specific-message.xml">How do I consume a specific message</a></li><li><a shape="rect" href="how-do-i-get-started-with-jms.xml">How do I get started with JMS</a></li><li><a shape="rect" href="how-do-i-make-messages-durable.xml">How do I make messages durable</a></li><li><a shape="rect" href="how-do-i-send-messages-to-different-destinations-from-a-single-messageproducer.xml">How do I send messages to different Destinations from a single MessageProducer</a></li><li><a shape="rect" href="how-do-i-use-jms-efficiently.xml">How do I use JMS efficiently</a></li><li><a shape="rect" href="how-should-i-implement-request-response-with-jms.xml">How should I implement request response with JMS</a></li><li><a shape="rect" href="how-to-unit-test-jms-code.xml">How To Unit Test JMS Code</a></li><li><a shape="rect" href="multiple-consumers-on-a-queue.xml">Multiple consumers on a queue</a></li><li><a shape="rect" href="should-i-use-transactions.xml">Should I use transactions</a></li><li><a shape="rect" href="should-i-use-xa.xml">Should I use XA</a></li><li><a shape="rect" href="what-are-administered-objects.xml">What are administered objects</a></li></ul>
+<structured-macro ac:macro-id="afb7acf6-f7b3-4609-a8d1-fc6ffad20bfb" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Persistence Questions"></page></link></parameter></structured-macro>
-<h3 id="FAQ-UsingApacheActiveMQ"><a shape="rect" href="using-apache-activemq.xml">Using Apache ActiveMQ</a></h3>
+<h3><link><page ri:content-title="Errors"></page></link></h3>
-Questions on using Apache ActiveMQ
+<structured-macro ac:macro-id="55526355-9de4-4e2e-b58c-83642f981502" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Errors"></page></link></parameter></structured-macro>
-<ul class="childpages-macro"><li><a shape="rect" href="activemq-command-line-tools-reference.xml">ActiveMQ Command Line Tools Reference</a></li><li><a shape="rect" href="are-destinations-case-sensitive.xml">Are destinations case sensitive</a></li><li><a shape="rect" href="can-i-send-really-large-files-over-activemq.xml">Can I send really large files over ActiveMQ</a></li><li><a shape="rect" href="can-i-use-activemq-5x-or-later-on-java-14.xml">Can I use ActiveMQ 5.x or later on Java 1.4</a></li><li><a shape="rect" href="can-two-brokers-share-the-same-database.xml">Can two brokers share the same database</a></li><li><a shape="rect" href="does-activemq-support-clustering.xml">Does ActiveMQ support clustering</a></li><li><a shape="rect" href="how-can-i-avoid-serialization-of-objects-in-objectmessage.xml">How can I avoid serialization of Objects in ObjectMessage</a></li><li><a shape="rect" href="how-can-i-get-a-list-of-the-topics-and-queues-in-a-broker.xml">How can I get a list of the topics and queues in a broker</a></li><li><a shape="rect" href="how-can-i-make-activemq-faster.xml">How can I make ActiveMQ faster</a></li><li><a shape="rect" href="how-can-i-monitor-activemq.xml">How can I monitor ActiveMQ</a></li><li><a shape="rect" href="how-can-i-monitor-the-connection-with-the-broker.xml">How can I monitor the connection with the broker</a></li><li><a shape="rect" href="how-can-i-see-what-destinations-are-used.xml">How can I see what destinations are used</a></li><li><a shape="rect" href="how-can-i-support-auto-reconnection.xml">How can I support auto reconnection</a></li><li><a shape="rect" href="how-can-i-support-priority-queues.xml">How can I support priority queues</a></li><li><a shape="rect" href="how-can-i-use-different-network-protocols.xml">How can I use different network protocols</a></li><li><a shape="rect" href="how-do-distributed-queues-work.xml">How do distributed queues work</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-c.xml">How do I access ActiveMQ from C</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-csharp-or-dotnet.xml">How do I access ActiveMQ from CSharp or dotNet</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-ruby-perl-python-php.xml">How do I access ActiveMQ from Ruby, Perl, Python, PHP</a></li><li><a shape="rect" href="how-do-i-bridge-different-jms-providers.xml">How do I bridge different JMS providers</a></li><li><a shape="rect" href="how-do-i-change-dispatch-policy.xml">How do I change dispatch policy</a></li><li><a shape="rect" href="how-do-i-change-the-logging.xml">How do I change the logging</a></li><li><a shape="rect" href="how-do-i-connect-to-one-of-a-number-of-message-brokers.xml">How do I connect to one of a number of message brokers</a></li><li><a shape="rect" href="how-do-i-create-new-destinations.xml">How do I create new destinations</a></li><li><a shape="rect" href="how-do-i-delete-a-destination.xml">How do I delete a destination</a></li><li><a shape="rect" href="how-do-i-disable-logging.xml">How do I disable logging</a></li><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li><li><a shape="rect" href="how-do-i-enable-asynchronous-sending.xml">How do I enable asynchronous sending</a></li><li><a shape="rect" href="how-do-i-enable-debug-logging.xml">How do I enable debug logging</a></li><li><a shape="rect" href="how-do-i-find-the-size-of-a-queue.xml">How do I find the Size of a Queue</a></li><li><a shape="rect" href="how-do-i-preserve-order-of-messages.xml">How do I preserve order of messages</a></li><li><a shape="rect" href="how-do-i-purge-a-queue.xml">How do I purge a queue</a></li><li><a shape="rect" href="how-do-i-restart-embedded-broker.xml">How do I restart embedded broker</a></li><li><a shape="rect" href="how-do-i-restrict-connections-from-creating-new-queues-or-topics.xml">How do I restrict connections from creating new queues or topics</a></li><li><a shape="rect" href="how-do-i-run-a-broker.xml">How do I run a broker</a></li><li><a shape="rect" href="how-do-i-set-the-message-expiration.xml">How do I set the message expiration</a></li><li><a shape="rect" href="how-do-i-turn-off-creating-an-embedded-activemq-broker-when-using-the-vm-transport.xml">How do I turn off creating an embedded ActiveMQ broker when using the VM transport</a></li><li><a shape="rect" href="how-do-i-unack-the-message-with-stomp.xml">How do I unack the message with Stomp</a></li><li><a shape="rect" href="how-do-i-use-activemq-using-in-jvm-messaging.xml">How do I use ActiveMQ using in JVM messaging</a></li><li><a shape="rect" href="how-do-i-use-durable-subscribers-in-a-network-of-brokers.xml">How do I use durable subscribers in a network of brokers</a></li><li><a shape="rect" href="how-do-i-use-ivy-with-activemq.xml">How do I use Ivy with ActiveMQ</a></li><li><a shape="rect" href="how-do-i-use-log4j-jms-appender-with-activemq.xml">How do I use log4j JMS appender with ActiveMQ</a></li><li><a shape="rect" href="how-do-i-use-ssl.xml">How do I use SSL</a></li><li><a shape="rect" href="how-do-message-groups-compare-to-selectors.xml">How do Message Groups compare to Selectors</a></li><li><a shape="rect" href="how-do-multiple-transports-work.xml">How do multiple transports work</a></li><li><a shape="rect" href="how-do-transactions-work.xml">How Do Transactions Work</a></li><li><a shape="rect" href="how-lightweight-is-sending-a-message.xml">How lightweight is sending a message</a></li><li><a shape="rect" href="how-should-i-package-applications-using-camel-and-activemq.xml">How should I package applications using Camel and ActiveMQ</a></li><li><a shape="rect" href="how-should-i-use-the-vm-transport.xml">How should I use the VM transport</a></li><li><a shape="rect" href="how-to-deal-with-large-number-of-threads-in-clients.xml">How to deal with large number of threads in clients</a></li><li><a shape="rect" href="how-to-disable-auto-destination-creation.xml">How to disable auto destination creation</a></li><li><a shape="rect" href="i-see-nc-client-ids-what-does-that-mean.xml">I see NC_ client-ids, what does that mean</a></li><li><a shape="rect" href="should-i-deploy-enterprise-integration-patterns-in-the-broker-or-another-application.xml">Should I deploy Enterprise Integration Patterns in the broker or another application</a></li><li><a shape="rect" href="should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml">Should I deploy the broker inside my JVM or AppServer</a></li><li><a shape="rect" href="what-are-those-topics-activemqadvisory.xml">What are those topics ActiveMQ.Advisory</a></li><li><a shape="rect" href="what-happens-with-a-fast-producer-and-slow-consumer.xml">What happens with a fast producer and slow consumer</a></li><li><a shape="rect" href="what-is-the-difference-between-a-virtual-topic-and-a-composite-destination.xml">What is the difference between a Virtual Topic and a Composite Destination</a></li><li><a shape="rect" href="what-is-the-difference-between-discovery-multicast-and-zeroconf.xml">What is the difference between discovery, multicast and zeroconf</a></li><li><a shape="rect" href="what-is-the-prefetch-limit-for.xml">What is the Prefetch Limit For?</a></li><li><a shape="rect" href="while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.xml">While posting large binary file to activeMQ, is there a way to measure its progress</a></li></ul>
+<h3><link><page ri:content-title="Developing ActiveMQ"></page></link></h3>
-<h3 id="FAQ-Configuration"><a shape="rect" href="configuration.xml">Configuration</a></h3>
+<structured-macro ac:macro-id="62db6683-cc91-4458-be64-cd302ae61f66" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Developing ActiveMQ"></page></link></parameter></structured-macro>
-
-
-
-<p>Questions on configuring ActiveMQ's JMS client or the Message Broker</p>
-
-<ul class="childpages-macro"><li><a shape="rect" href="how-can-i-enable-detailed-logging.xml">How can I enable detailed logging</a></li><li><a shape="rect" href="how-does-xbean-compare-to-spring-2.xml">How does XBean compare to Spring 2</a></li><li><a shape="rect" href="how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker.xml">How do I configure 10s of 1000s of Queues in a single broker</a></li><li><a shape="rect" href="how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages.xml">How do I configure ActiveMQ to hold 100s of millions of Queue Messages</a></li><li><a shape="rect" href="how-do-i-configure-activemq-to-use-aio-server-transport.xml">How do I configure ActiveMQ to use AIO server transport</a></li><li><a shape="rect" href="how-do-i-configure-automatic-reconnection.xml">How do I configure automatic reconnection</a></li><li><a shape="rect" href="how-do-i-configure-distributed-queues-or-topics.xml">How do I configure distributed queues or topics</a></li><li><a shape="rect" href="how-do-i-configure-the-queues-i-want.xml">How do I configure the queues I want</a></li><li><a shape="rect" href="how-do-i-define-a-local-address-and-local-port-for-tcp-or-ssl.xml">How do I define a local address and local port for TCP or SSL</a></li><li><a shape="rect" href="how-do-i-disable-persistence.xml">How do I disable persistence</a></li><li><a shape="rect" href="how-do-i-run-activemq-under-the-kaffe-jvm.xml">How do I run ActiveMQ under the Kaffe JVM</a></li><li><a shape="rect" href="how-to-configure-a-new-database.xml">How to configure a new database</a></li><li><a shape="rect" href="how-to-deploy-activemq-ra-versionrar-to-weblogic.xml">How to deploy activemq-ra-version.rar to weblogic</a></li><li><a shape="rect" href="how-to-disable-multicast-discovery.xml">How to disable multicast discovery</a></li></ul>
-
-<h3 id="FAQ-PersistenceQuestions"><a shape="rect" href="persistence-questions.xml">Persistence Questions</a></h3>
-
-Questions relating to long term persistence of messages.
-
-<ul class="childpages-macro"><li><a shape="rect" href="are-messages-read-directly-from-the-journal.xml">Are messages read directly from the journal</a></li><li><a shape="rect" href="does-activemq-support-my-sql-database.xml">Does ActiveMQ support my SQL database</a></li><li><a shape="rect" href="how-does-journaling-work-with-multiple-brokers.xml">How does journaling work with multiple brokers</a></li><li><a shape="rect" href="how-does-the-journal-work.xml">How does the journal work</a></li><li><a shape="rect" href="how-do-i-back-up-kahadb.xml">How do I back-up KahaDB</a></li><li><a shape="rect" href="how-do-i-change-the-message-store-directory-for-an-embedded-broker.xml">How do I change the message store directory for an embedded broker</a></li><li><a shape="rect" href="is-there-a-specified-size-of-the-journal.xml">Is there a specified size of the journal</a></li><li><a shape="rect" href="what-happens-when-the-journal-size-is-exceeded.xml">What happens when the journal size is exceeded</a></li><li><a shape="rect" href="what-is-the-difference-between-persistent-and-non-persistent-delivery.xml">What is the difference between persistent and non-persistent delivery</a></li></ul>
-
-<h3 id="FAQ-Errors"><a shape="rect" href="errors.xml">Errors</a></h3>
-
-
-
-<p>Questions on specific kinds of errors. If you have seen a specific exception then check the <a shape="rect" href="exceptions.xml">Exceptions</a></p>
-
-<ul class="childpages-macro"><li><a shape="rect" href="could-not-find-packetreader-for-packet-type-unknown-packet-type.xml">Could not find PacketReader for packet type - UNKNOWN PACKET TYPE</a></li><li><a shape="rect" href="exceptions.xml">Exceptions</a><ul class="childpages-macro"><li><a shape="rect" href="certificateunknown.xml">certificate_unknown</a></li><li><a shape="rect" href="ioexception-could-not-find-class-for-resource.xml">IOException - could not find class for resource</a></li><li><a shape="rect" href="javaiointerruptedioexception.xml">java.io.InterruptedIOException</a></li><li><a shape="rect" href="javaioioexception-failed-to-create-database-derbydb-see-the-next-exception-for-details.xml">java.io.IOException Failed to create database 'derbydb', see the next exception for details</a></li><li><a shape="rect" href="javalangnosuchmethoderror.xml">java.lang.NoSuchMethodError</a></li><li><a shape="rect" href="javalangnosuchmethodexception-orgactivemqraactivemqresourceadaptersetuseembeddedbroker.xml">java.lang.NoSuchMethodException org.activemq.ra.ActiveMQResourceAdapter.setUseEmbeddedBroker</a></li><li><a shape="rect" href="javalangoutofmemory.xml">java.lang.OutOfMemory</a></li><li><a shape="rect" href="javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml">javax.jms.JMSException - Wire format negociation timeout - peer did not send his wire format.</a></li><li><a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI () needs 2.1 API.</a></li><li><a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-xxx-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (xxx) needs 2.1 API</a></li><li><a shape="rect" href="journal-is-already-opened-by-this-application.xml">Journal is already opened by this application</a></li><li><a shape="rect" href="noclassdeffounderror-orgspringframeworkcoreioresource.xml">NoClassDefFoundError - org.springframework.core.io.Resource</a></li><li><a shape="rect" href="no-suitable-driver.xml">No suitable driver</a></li></ul></li><li><a shape="rect" href="i-am-having-problems-with-the-spring-jmstemplate.xml">I am having problems with the Spring JmsTemplate</a></li><li><a shape="rect" href="i-am-not-receiving-any-messages-what-is-wrong.xml">I am not receiving any messages, what is wrong</a></li><li><a shape="rect" href="i-cannot-connect-to-activemq-from-jconsole.xml">I cannot connect to ActiveMQ from JConsole</a></li><li><a shape="rect" href="i-do-not-receive-messages-in-my-second-consumer.xml">I do not receive messages in my second consumer</a></li><li><a shape="rect" href="i-get-errors-building-the-code-whats-wrong.xml">I get errors building the code whats wrong</a></li><li><a shape="rect" href="log4j-warn-no-appenders-could-be-found-for-logger.xml">log4j-WARN No appenders could be found for logger</a></li><li><a shape="rect" href="multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.xml">Multicast - Watch out for IPV6 vs IPV4 support on your operating system or distribution or network</a></li><li><a shape="rect" href="my-producer-blocks.xml">My producer blocks</a></li><li><a shape="rect" href="onmessage-method-of-messagelistener-is-never-called.xml">onMessage method of MessageListener is never called</a></li><li><a shape="rect" href="resource-adapter-does-not-seem-to-pool-connections.xml">Resource Adapter does not seem to pool connections</a></li><li><a shape="rect" href="slow-networks-drop-large-messages.xml">Slow networks drop large messages</a></li><li><a shape="rect" href="the-broker-will-not-start.xml">The Broker will not start</a></li><li><a shape="rect" href="the-vm-transport-starts-a-broker-before-my-configured-broker-starts.xml">The vm transport starts a broker before my configured broker starts</a></li><li><a shape="rect" href="why-do-i-not-get-all-of-the-messages-i-sent.xml">Why do I not get all of the messages I sent</a></li><li><a shape="rect" href="why-do-i-not-receive-messages-on-my-durable-topic-subscription.xml">Why do I not receive messages on my durable topic subscription</a></li><li><a shape="rect" href="why-do-kahadb-log-files-remain-after-cleanup.xml">Why do KahaDB log files remain after cleanup</a></li></ul>
-
-<h3 id="FAQ-DevelopingActiveMQ"><a shape="rect" href="developing-activemq.xml">Developing ActiveMQ</a></h3>
-
-Questions for developers wishing to extend or enhance Apache ActiveMQ
-
-<ul class="childpages-macro"><li><a shape="rect" href="how-can-i-add-a-new-type-of-transport.xml">How can I add a new type of transport</a></li><li><a shape="rect" href="how-can-i-contribute.xml">How can I contribute</a></li><li><a shape="rect" href="how-do-i-add-my-own-plugins.xml">How do I add my own plugins</a></li><li><a shape="rect" href="how-do-i-debug-activemq-from-my-ide.xml">How do I debug ActiveMQ from my IDE</a></li></ul>
-
-<h3 id="FAQ-Terminology"><a shape="rect" href="terminology.xml">Terminology</a></h3>
+<h3><link><page ri:content-title="Terminology"></page></link></h3>
<p>A list of the various messaging related terms and acronyms.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="dr.xml">DR</a></li><li><a shape="rect" href="ha.xml">HA</a></li><li><a shape="rect" href="latency.xml">Latency</a></li><li><a shape="rect" href="mom.xml">MOM</a></li><li><a shape="rect" href="qos.xml">QoS</a></li><li><a shape="rect" href="seda.xml">SEDA</a></li><li><a shape="rect" href="throughput.xml">Throughput</a></li></ul>
+<structured-macro ac:macro-id="c1ff28d3-d9eb-47e9-a9c8-e7cd17617d0e" ac:name="children" ac:schema-version="1"><parameter ac:name="page"><link><page ri:content-title="Terminology"></page></link></parameter></structured-macro>
+
</div>
diff --git a/features-overview.xml b/features-overview.xml
index b5b2fb1..1322df5 100644
--- a/features-overview.xml
+++ b/features-overview.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul><li>Supports a variety of <a shape="rect" href="cross-language-clients.xml">Cross Language Clients and Protocols</a> from Java, C, C++, C#, Ruby, Perl, Python, PHP<ul><li><a shape="rect" href="openwire.xml">OpenWire</a> for high performance clients in Java, C, C++, C#</li><li><a shape="rect" href="stomp.xml">Stomp</a> support so that clients can be written easily in C, Ruby, Perl, Python, PHP, ActionScript/Flash, Smalltalk to talk to ActiveMQ as well as any other popular Message Broker</li><li><a shape="rect" href="amqp.xml">AMQP</a> v1.0 support</li><li><a shape="rect" href="mqtt.xml">MQTT</a> v3.1 support allowing for connections in an IoT environment.</li></ul></li><li>full support for the <a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> both in the JMS client and the Message Broker</li><li>Supports many <a shape="rect" href="features.xml">advanced features</a> such as <a shape="rect" href="message-groups.xml">Message Groups</a>, <a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a>, <a shape="rect" href="wildcards.xml">Wildcards</a> and <a shape="rect" href="composite-destinations.xml">Composite Destinations</a></li><li>Fully supports JMS 1.1 and J2EE 1.4 with support for transient, persistent, transactional and XA messaging</li><li><a shape="rect" href="spring-support.xml">Spring Support</a> so that ActiveMQ can be easily embedded into Spring applications and configured using Spring's XML configuration mechanism</li><li>Tested inside popular J2EE servers such as <a shape="rect" class="external-link" href="http://tomee.apache.org/">TomEE</a>, <a shape="rect" class="external-link" href="http://geronimo.apache.org/">Geronimo</a>, JBoss, GlassFish and WebLogic<ul><li>Includes <a shape="rect" href="resource-adapter.xml">JCA 1.5 resource adaptors</a> for inbound & outbound messaging so that ActiveMQ should auto-deploy in any J2EE 1.4 compliant server</li></ul></li><li>Supports pluggable <a shape="rect" href="uri-protocols.xml">transport protocols</a> such as <a shape="rect" href="how-do-i-use-activemq-using-in-jvm-messaging.xml">in-VM</a>, TCP, SSL, NIO, UDP, multicast, JGroups and JXTA transports</li><li>Supports very fast <a shape="rect" href="persistence.xml">persistence</a> using JDBC along with a high performance journal</li><li>Designed for high performance clustering, client-server, peer based communication</li><li><a shape="rect" href="rest.xml">REST</a> API to provide technology agnostic and language neutral web based API to messaging</li><li><a shape="rect" href="ajax.xml">Ajax</a> to support web streaming support to web browsers using pure DHTML, allowing web browsers to be part of the messaging fabric</li><li><a shape="rect" href="axis-and-cxf-support.xml">CXF and Axis Support</a> so that ActiveMQ can be easily dropped into either of these web service stacks to provide reliable messaging</li><li>Can be used as an in memory JMS provider, ideal for <a shape="rect" href="how-to-unit-test-jms-code.xml">unit testing JMS</a></li></ul></div>
+<div class="wiki-content maincontent"><ul><li>Supports a variety of <link><page ri:content-title="Cross Language Clients"></page><plain-text-link-body>Cross Language Clients and Protocols</plain-text-link-body></link> from Java, C, C++, C#, Ruby, Perl, Python, PHP<ul><li><link><page ri:content-title="OpenWire"></page></link> for high performance clients in Java, C, C++, C#</li><li><link><page ri:content-title="Stomp"></page></link> support so that clients can be written easily in C, Ruby, Perl, Python, PHP, ActionScript/Flash, Smalltalk to talk to ActiveMQ as well as any other popular Message Broker</li><li><link><page ri:content-title="AMQP"></page></link> v1.0 support</li><li><link><page ri:content-title="MQTT"></page></link> v3.1 support allowing for connections in an IoT environment.</li></ul></li><li>full support for the <link><page ri:content-title="Enterprise Integration Patterns"></page></link> both in the JMS client and the Message Broker</li><li>Supports many <link><page ri:content-title="Features"></page><plain-text-link-body>advanced features</plain-text-link-body></link> such as <link><page ri:content-title="Message Groups"></page></link>, <link><page ri:content-title="Virtual Destinations"></page></link>, <link><page ri:content-title="Wildcards"></page></link> and <link><page ri:content-title="Composite Destinations"></page></link></li><li>Fully supports JMS 1.1 and J2EE 1.4 with support for transient, persistent, transactional and XA messaging</li><li><link><page ri:content-title="Spring Support"></page></link> so that ActiveMQ can be easily embedded into Spring applications and configured using Spring's XML configuration mechanism</li><li>Tested inside popular J2EE servers such as <a shape="rect" href="http://tomee.apache.org/">TomEE</a>, <a shape="rect" href="http://geronimo.apache.org/">Geronimo</a>, JBoss, GlassFish and WebLogic<ul><li>Includes <link><page ri:content-title="Resource Adapter"></page><plain-text-link-body>JCA 1.5 resource adaptors</plain-text-link-body></link> for inbound & outbound messaging so that ActiveMQ should auto-deploy in any J2EE 1.4 compliant server</li></ul></li><li>Supports pluggable <link><page ri:content-title="URI Protocols"></page><plain-text-link-body>transport protocols</plain-text-link-body></link> such as <link><page ri:content-title="How do I use ActiveMQ using in JVM messaging"></page><plain-text-link-body>in-VM</plain-text-link-body></link>, TCP, SSL, NIO, UDP, multicast, JGroups and JXTA transports</li><li>Supports very fast <link><page ri:content-title="Persistence"></page><plain-text-link-body>persistence</plain-text-link-body></link> using JDBC along with a high performance journal</li><li>Designed for high performance clustering, client-server, peer based communication</li><li><link><page ri:content-title="REST"></page></link> API to provide technology agnostic and language neutral web based API to messaging</li><li><link><page ri:content-title="Ajax"></page></link> to support web streaming support to web browsers using pure DHTML, allowing web browsers to be part of the messaging fabric</li><li><link><page ri:content-title="Axis and CXF Support"></page><plain-text-link-body>CXF and Axis Support</plain-text-link-body></link> so that ActiveMQ can be easily dropped into either of these web service stacks to provide reliable messaging</li><li>Can be used as an in memory JMS provider, ideal for <link><page ri:content-title="How To Unit Test JMS Code"></page><plain-text-link-body>unit testing JMS</plain-text-link-body></link></li></ul></div>
diff --git a/features.xml b/features.xml
index a13e052..c06392b 100644
--- a/features.xml
+++ b/features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Features-ApacheActiveMQFeatures">Apache ActiveMQ Features</h2><p>Apache ActiveMQ is packed with features; to get an idea you might want to look at the <a shape="rect" href="features-overview.xml">Features Overview</a> otherwise here is the list of all of the main features...</p><p></p><ul class="childpages-macro"><li><a shape="rect" href="active-groups.xml">Active Groups</a></li><li><a shape="rect" href="activemq-real-time.xml">ActiveMQ Real Time</a><ul class="childpages-macro"><li><a shape="rect" href="broadcasting.xml">Broadcasting</a></li><li><a shape="rect" href="group-membership.xml">Group Membership</a></li><li><a shape="rect" href="life-cycle.xml">Life Cycle</a></li><li><a shape="rect" href="the-activeblaze-message-type.xml">The ActiveBlaze Message type</a></li></ul></li><li><a shape="rect" href="broker-camel-component.xml">Broker Camel Component</a></li><li><a shape="rect" href="clustering.xml">Clustering</a><ul class="childpages-macro"><li><a shape="rect" href="masterslave.xml">MasterSlave</a><ul class="childpages-macro"><li><a shape="rect" href="jdbc-master-slave.xml">JDBC Master Slave</a></li><li><a shape="rect" href="kahadb-replication-experimental.xml">KahaDB Replication (Experimental)</a></li><li><a shape="rect" href="pure-master-slave.xml">Pure Master Slave</a></li><li><a shape="rect" href="shared-file-system-master-slave.xml">Shared File System Master Slave</a></li></ul></li><li><a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a></li><li><a shape="rect" href="replicated-message-store.xml">Replicated Message Store</a></li></ul></li><li><a shape="rect" href="command-agent.xml">Command Agent</a></li><li><a shape="rect" href="consumer-features.xml">Consumer Features</a><ul class="childpages-macro"><li><a shape="rect" href="consumer-dispatch-async.xml">Consumer Dispatch Async</a></li><li><a shape="rect" href="consumer-priority.xml">Consumer Priority</a></li><li><a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a></li><li><a shape="rect" href="manage-durable-subscribers.xml">Manage Durable Subscribers</a></li><li><a shape="rect" href="message-groups.xml">Message Groups</a></li><li><a shape="rect" href="redelivery-policy.xml">Redelivery Policy</a></li><li><a shape="rect" href="retroactive-consumer.xml">Retroactive Consumer</a></li><li><a shape="rect" href="selectors.xml">Selectors</a></li><li><a shape="rect" href="slow-consumer-handling.xml">Slow Consumer Handling</a></li><li><a shape="rect" href="subscription-recovery-policy.xml">Subscription Recovery Policy</a></li></ul></li><li><a shape="rect" href="destination-features.xml">Destination Features</a><ul class="childpages-macro"><li><a shape="rect" href="composite-destinations.xml">Composite Destinations</a></li><li><a shape="rect" href="configure-startup-destinations.xml">Configure Startup Destinations</a></li><li><a shape="rect" href="delete-inactive-destinations.xml">Delete Inactive Destinations</a></li><li><a shape="rect" href="destination-options.xml">Destination Options</a></li><li><a shape="rect" href="mirrored-queues.xml">Mirrored Queues</a></li><li><a shape="rect" href="per-destination-policies.xml">Per Destination Policies</a></li><li><a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a></li><li><a shape="rect" href="wildcards.xml">Wildcards</a></li></ul></li><li><a shape="rect" href="discovery.xml">Discovery</a></li><li><a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a></li><li><a shape="rect" href="features-overview.xml">Features Overview</a></li><li><a shape="rect" href="horizontal-scaling.xml">Horizontal Scaling</a><ul class="childpages-macro"><li><a shape="rect" href="scaling-queues.xml">Scaling Queues</a></li></ul></li><li><a shape="rect" href="interceptors.xml">Interceptors</a><ul class="childpages-macro"><li><a shape="rect" href="destinations-plugin.xml">Destinations Plugin</a></li><li><a shape="rect" href="logging-interceptor.xml">Logging Interceptor</a></li><li><a shape="rect" href="statisticsplugin.xml">StatisticsPlugin</a></li><li><a shape="rect" href="timestampplugin.xml">TimeStampPlugin</a></li></ul></li><li><a shape="rect" href="jmsxuserid.xml">JMSXUserID</a></li><li><a shape="rect" href="jmx.xml">JMX</a><ul class="childpages-macro"><li><a shape="rect" href="jmx-support.xml">JMX Support</a></li></ul></li><li><a shape="rect" href="logging-a-warning-if-you-forget-to-start-a-connection.xml">Logging a warning if you forget to start a Connection</a></li><li><a shape="rect" href="mdc-logging.xml">MDC Logging</a></li><li><a shape="rect" href="message-dispatching-features.xml">Message Dispatching Features</a><ul class="childpages-macro"><li><a shape="rect" href="async-sends.xml">Async Sends</a></li><li><a shape="rect" href="dispatch-policies.xml">Dispatch Policies</a></li><li><a shape="rect" href="message-cursors.xml">Message Cursors</a></li><li><a shape="rect" href="optimized-acknowledgement.xml">Optimized Acknowledgement</a></li><li><a shape="rect" href="producer-flow-control.xml">Producer Flow Control</a></li><li><a shape="rect" href="total-ordering.xml">Total Ordering</a></li></ul></li><li><a shape="rect" href="message-features.xml">Message Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-message-properties.xml">ActiveMQ Message Properties</a></li><li><a shape="rect" href="advisory-message.xml">Advisory Message</a></li><li><a shape="rect" href="blob-messages.xml">Blob Messages</a></li><li><a shape="rect" href="delay-and-schedule-message-delivery.xml">Delay and Schedule Message Delivery</a></li><li><a shape="rect" href="jms-streams.xml">JMS Streams</a></li><li><a shape="rect" href="message-transformation.xml">Message Transformation</a></li><li><a shape="rect" href="objectmessage.xml">ObjectMessage</a></li><li><a shape="rect" href="structured-message-properties-and-mapmessages.xml">Structured Message Properties and MapMessages</a></li></ul></li><li><a shape="rect" href="new-features.xml">New Features</a><ul class="childpages-macro"><li><a shape="rect" href="changes-in-40.xml">Changes in 4.0</a></li><li><a shape="rect" href="new-features-in-41.xml">New Features in 4.1</a></li><li><a shape="rect" href="new-features-in-50.xml">New Features in 5.0</a></li><li><a shape="rect" href="new-features-in-51.xml">New Features in 5.1</a></li><li><a shape="rect" href="new-features-in-52.xml">New Features in 5.2</a></li><li><a shape="rect" href="new-features-in-53.xml">New Features in 5.3</a></li><li><a shape="rect" href="new-features-in-54.xml">New Features in 5.4</a></li><li><a shape="rect" href="new-features-in-55.xml">New Features in 5.5</a></li><li><a shape="rect" href="new-features-in-56.xml">New Features in 5.6</a></li><li><a shape="rect" href="new-features-in-57.xml">New Features in 5.7</a></li><li><a shape="rect" href="new-features-in-58.xml">New Features in 5.8</a></li><li><a shape="rect" href="new-features-in-59.xml">New Features in 5.9</a><ul class="childpages-macro"><li><a shape="rect" href="runtime-configuration.xml">Runtime Configuration</a></li></ul></li><li><a shape="rect" href="new-features-in-511.xml">New Features in 5.11</a></li><li><a shape="rect" href="new-features-in-513.xml">New Features in 5.13</a></li><li><a shape="rect" href="new-features-in-60.xml">New Features in 6.0</a></li></ul></li><li><a shape="rect" href="performance.xml">Performance</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a><ul class="childpages-macro"><li><a shape="rect" href="sample-report.xml">sample report</a></li></ul></li><li><a shape="rect" href="load-testing-with-camel.xml">Load Testing with Camel</a></li><li><a shape="rect" href="performance-report.xml">Performance report</a></li></ul></li><li><a shape="rect" href="persistence.xml">Persistence</a><ul class="childpages-macro"><li><a shape="rect" href="amq-message-store.xml">AMQ Message Store</a></li><li><a shape="rect" href="configurable-ioexception-handling.xml">Configurable IOException Handling</a></li><li><a shape="rect" href="jdbc-support.xml">JDBC Support</a><ul class="childpages-macro"><li><a shape="rect" href="sqlserver.xml">SQLServer</a></li><li><a shape="rect" href="sybase.xml">Sybase</a></li></ul></li><li><a shape="rect" href="kahadb.xml">KahaDB</a></li><li><a shape="rect" href="kaha-persistence.xml">Kaha Persistence</a></li><li><a shape="rect" href="leveldb-store.xml">LevelDB Store</a></li><li><a shape="rect" href="periodically-checking-disk-limits.xml">Periodically checking disk limits</a></li><li><a shape="rect" href="pluggable-storage-lockers.xml">Pluggable storage lockers</a></li><li><a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a></li></ul></li><li><a shape="rect" href="scaling-the-depth-of-a-queue.xml">Scaling the Depth of a Queue</a></li><li><a shape="rect" href="security.xml">Security</a><ul class="childpages-macro"><li><a shape="rect" href="audit-logging.xml">Audit Logging</a></li><li><a shape="rect" href="cached-ldap-authorization-module.xml">Cached LDAP Authorization Module</a></li><li><a shape="rect" href="encrypted-passwords.xml">Encrypted passwords</a></li><li><a shape="rect" href="shiro.xml">Shiro</a></li></ul></li><li><a shape="rect" href="the-proxy-connector.xml">The Proxy Connector</a></li><li><a shape="rect" href="unix.xml">Unix</a><ul class="childpages-macro"><li><a shape="rect" href="unix-service.xml">Unix Service</a></li><li><a shape="rect" href="unix-shell-script.xml">Unix Shell Script</a></li></ul></li><li><a shape="rect" href="uri-protocols.xml">URI Protocols</a><ul class="childpages-macro"><li><a shape="rect" href="vm-protocol.xml">VM Protocol</a></li></ul></li><li><a shape="rect" href="visualisation.xml">Visualisation</a><ul class="childpages-macro"><li><a shape="rect" href="visualisation-wish-list.xml">Visualisation Wish List</a></li></ul></li></ul></div>
+<div class="wiki-content maincontent"><h2>Apache ActiveMQ Features</h2><p>Apache ActiveMQ is packed with features; to get an idea you might want to look at the <link><page ri:content-title="Features Overview"></page></link> otherwise here is the list of all of the main features...</p><p><structured-macro ac:macro-id="00811776-2d5a-4b5e-99ed-6750b2bf8eac" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro></p></div>
diff --git a/general.xml b/general.xml
index ad5fdcc..3664ab6 100644
--- a/general.xml
+++ b/general.xml
@@ -3,5 +3,5 @@
<p>General questions about ActiveMQ</p>
-<ul class="childpages-macro"><li><a shape="rect" href="can-i-get-commercial-support.xml">Can I get commercial support</a></li><li><a shape="rect" href="how-can-i-get-help.xml">How can I get help</a></li><li><a shape="rect" href="how-can-i-get-the-source-code-from-subversion.xml">How can I get the source code from subversion</a></li><li><a shape="rect" href="how-does-activemq-compare-to-amqp.xml">How does ActiveMQ compare to AMQP</a></li><li><a shape="rect" href="how-does-activemq-compare-to-artemis.xml">How does ActiveMQ compare to Artemis</a></li><li><a shape="rect" href="how-does-activemq-compare-to-fuse-message-broker.xml">How does ActiveMQ compare to Fuse Message Broker</a></li><li><a shape="rect" href="how-does-activemq-compare-to-jbossmq.xml">How does ActiveMQ compare to JBossMQ</a></li><li><a shape="rect" href="how-does-activemq-compare-to-mantaray.xml">How does ActiveMQ compare to Mantaray</a></li><li><a shape="rect" href="how-does-activemq-compare-to-mule.xml">How does ActiveMQ compare to Mule</a></li><li><a shape="rect" href="how-does-activemq-compare-to-spread-toolkit.xml">How does ActiveMQ compare to Spread Toolkit</a></li><li><a shape="rect" href="how-does-openwire-compare-to-stomp.xml">How does OpenWire compare to Stomp</a></li><li><a shape="rect" href="how-does-the-website-work.xml">How does the website work</a></li><li><a shape="rect" href="how-do-i-avoid-maven-downloading-latest-jars.xml">How do I avoid Maven downloading latest jars</a></li><li><a shape="rect" href="how-do-i-build-but-disable-the-unit-tests.xml">How do I build but disable the unit tests</a></li><li><a shape="rect" href="how-do-i-compile-from-the-source.xml">How do I compile from the source</a></li><li><a shape="rect" href="how-do-i-edit-the-website.xml">How do I edit the website</a></li><li><a shape="rect" href="how-fast-is-activemq.xml">How fast is ActiveMQ</a></li><li><a shape="rect" href="should-i-run-activemq-on-windows-in-a-directory-with-spaces.xml">Should I run ActiveMQ on Windows in a directory with spaces</a></li><li><a shape="rect" href="what-is-activemq.xml">What is ActiveMQ</a></li><li><a shape="rect" href="what-is-the-license.xml">What is the license</a></li><li><a shape="rect" href="what-jars-do-i-need.xml">What jars do I need</a></li><li><a shape="rect" href="what-open-source-integration-solution-works-best-with-activemq.xml">What open source integration solution works best with ActiveMQ</a></li><li><a shape="rect" href="what-platforms-does-activemq-support.xml">What platforms does ActiveMQ support</a></li><li><a shape="rect" href="what-version-should-i-use.xml">What version should I use</a></li></ul></div>
+<structured-macro ac:macro-id="e9504c5e-0217-433d-a299-002d125571a2" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/geronimo.xml b/geronimo.xml
index 76d67b7..1c7f2c9 100644
--- a/geronimo.xml
+++ b/geronimo.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>ActiveMQ is the default JMS provider in <a shape="rect" class="external-link" href="http://geronimo.apache.org">Apache Geronimo</a>.</p>
+<p>ActiveMQ is the default JMS provider in <a shape="rect" href="http://geronimo.apache.org">Apache Geronimo</a>.</p>
<p>ActiveMQ can be used both as JMS Client and a JMS Broker. This short<br clear="none">
article explains how to use it on a standalone client to access the<br clear="none">
@@ -14,19 +14,18 @@
The following deployment descriptor can be used to deploy two topics and a<br clear="none">
ConnectionFactory: weatherTopic and weatherRequestsTopic</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector"
- version="1.5"
- configId="weather/Topics"
- parentId="org/apache/geronimo/SystemJMS">
+<structured-macro ac:macro-id="d2250b10-bf1d-4e52-8a7e-e645e9fb44a1" ac:name="code" ac:schema-version="1"><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
+<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector"
+ version="1.5"
+ configId="weather/Topics"
+ parentId="org/apache/geronimo/SystemJMS">
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>ActiveMQ RA</resourceadapter-name>
- <config-property-setting name="ServerUrl">tcp://localhost:61616</config-property-setting>
- <config-property-setting name="UserName">geronimo</config-property-setting>
- <config-property-setting name="Password">geronimo</config-property-setting>
+ <config-property-setting name="ServerUrl">tcp://localhost:61616</config-property-setting>
+ <config-property-setting name="UserName">geronimo</config-property-setting>
+ <config-property-setting name="Password">geronimo</config-property-setting>
<workmanager>
<gbean-link>DefaultWorkManager</gbean-link>
</workmanager>
@@ -67,7 +66,7 @@
<adminobject-instance>
<message-destination-name>weatherTopic</message-destination-name>
<config-property-setting
-name="PhysicalName">weatherTopic</config-property-setting>
+name="PhysicalName">weatherTopic</config-property-setting>
</adminobject-instance>
</adminobject>
<adminobject>
@@ -78,25 +77,22 @@
<message-destination-name>weatherRequestsTopic</message-destination-name>
<config-property-setting
-name="PhysicalName">weatherRequestsTopic</config-property-setting>
+name="PhysicalName">weatherRequestsTopic</config-property-setting>
</adminobject-instance>
</adminobject>
</connector>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Then deploy it using Geronimo's deploy tool :</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d52711e4-100d-4c6a-bd05-d7b309b3b4d1" ac:name="code" ac:schema-version="1"><plain-text-body>
D:\geronimo>java -jar bin\deployer.jar deploy d:\projects\weather\src\resources\
geronimo-activemq.xml repository\activemq\rars\activemq-ra-3.1-SNAPSHOT.rar
Username: system
Password: manager
Deployed weather/Topics
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The geronimo.log file should now refer to these newly deployed Topics.</p>
@@ -132,54 +128,48 @@
<ul class="alternate"><li>Now, in your Spring description file, declare the bean that will read<br clear="none">
the properties from the bootstrap.properties file
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <bean id="placeholderConfig"
- class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
- <property name="location"><value>classpath:/bootstrap.properties</value></property>
+<structured-macro ac:macro-id="4c35d9fb-b949-42d6-ac4a-848b747a8fa2" ac:name="code" ac:schema-version="1"><plain-text-body>
+ <bean id="placeholderConfig"
+ class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
+ <property name="location"><value>classpath:/bootstrap.properties</value></property>
</bean>
-]]></script>
-</div></div></li></ul>
+</plain-text-body></structured-macro></li></ul>
<ul class="alternate"><li>Create a JNDI template (A Spring-specific wrapper around the JNDI InitialContext
- <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
- <property name="environment">
+ <structured-macro ac:macro-id="2c47a0d9-75fe-436a-8995-0ced8834813c" ac:name="code" ac:schema-version="1"><plain-text-body>
+ <bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
+ <property name="environment">
<props>
- <prop key="java.naming.factory.initial">${jms.jndiContextFactory}</prop>
+ <prop key="java.naming.factory.initial">${jms.jndiContextFactory}</prop>
<!-- Specific to ActiveMQ -->
<!-- the address of the ActiveMQ broker -->
- <prop key="brokerURL">${jms.jndiProviderUrl}</prop>
+ <prop key="brokerURL">${jms.jndiProviderUrl}</prop>
<!-- Some Topics Registration, since we are using a fake JNDI implementation -->
- <prop key="topic.${jms.weatherTopic}">${jms.weatherTopic}</prop>
- <prop key="topic.${jms.weatherRequestsTopic}">${jms.weatherRequestsTopic}</prop>
+ <prop key="topic.${jms.weatherTopic}">${jms.weatherTopic}</prop>
+ <prop key="topic.${jms.weatherRequestsTopic}">${jms.weatherRequestsTopic}</prop>
</props>
</property>
</bean>
-]]></script>
-</div></div></li></ul>
+</plain-text-body></structured-macro></li></ul>
<ul class="alternate"><li>Retrieve the ConnectionFactory from the JNDI context</li></ul>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <bean id="internalJmsQueueConnectionFactory"
- class="org.springframework.jndi.JndiObjectFactoryBean">
- <property name="jndiTemplate">
- <ref bean="jndiTemplate"/>
+<structured-macro ac:macro-id="060cb49a-9253-4db0-8a36-06f8fcef8896" ac:name="code" ac:schema-version="1"><plain-text-body>
+ <bean id="internalJmsQueueConnectionFactory"
+ class="org.springframework.jndi.JndiObjectFactoryBean">
+ <property name="jndiTemplate">
+ <ref bean="jndiTemplate"/>
</property>
- <property name="jndiName">
+ <property name="jndiName">
<value>${jms.connectionFactoryName}</value>
</property>
</bean>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>I'm not 100% sure, but I think that you can put any Factory Name, it will just<br clear="none">
work. (In a scenario where the JNDI context actually contacts a naming server,<br clear="none">
@@ -188,30 +178,29 @@
<ul class="alternate"><li>Get the Topics instances from the JNDI Context</li></ul>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<bean id="weatherTopic"
- class="org.springframework.jndi.JndiObjectFactoryBean"
- singleton="true">
- <property name="jndiTemplate">
- <ref bean="jndiTemplate"/>
+<structured-macro ac:macro-id="d7a1771f-06d0-4f42-9806-62aa17e81627" ac:name="code" ac:schema-version="1"><plain-text-body>
+<bean id="weatherTopic"
+ class="org.springframework.jndi.JndiObjectFactoryBean"
+ singleton="true">
+ <property name="jndiTemplate">
+ <ref bean="jndiTemplate"/>
</property>
- <property name="jndiName">
+ <property name="jndiName">
<value>${jms.weatherTopic}</value>
</property>
</bean>
-<bean id="weatherRequestTopic"
- class="org.springframework.jndi.JndiObjectFactoryBean"
- singleton="true">
- <property name="jndiTemplate">
- <ref bean="jndiTemplate"/>
+<bean id="weatherRequestTopic"
+ class="org.springframework.jndi.JndiObjectFactoryBean"
+ singleton="true">
+ <property name="jndiTemplate">
+ <ref bean="jndiTemplate"/>
</property>
- <property name="jndiName">
+ <property name="jndiName">
<value>${jms.weatherRequestsTopic}</value>
</property>
</bean>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<ul class="alternate"><li>Now, you can reuse these Topics beans the way you want.</li></ul></div>
+<ul class="alternate"><li>Now, you can reuse these Topics beans the way you want.</li></ul>
+</div>
diff --git a/getting-started.xml b/getting-started.xml
index 4d4a659..a08c454 100644
--- a/getting-started.xml
+++ b/getting-started.xml
@@ -1,87 +1,39 @@
-<div class="wiki-content maincontent"><h2 id="GettingStarted-Introduction">Introduction</h2><p>This document describes how to install and configure ActiveMQ 4.x/5.x for both Unix and Windows' platforms.</p><h2 id="GettingStarted-DocumentOrganization">Document Organization</h2><p class="confluence-link">The Getting Started Guide for ActiveMQ 4.x document contains the following sections:</p><p class="confluence-link"></p><div class="toc-macro client-side-toc-macro" data-headerelements="H1,H2,H3,H4,H5,H6,H7"></div><h2 id="GettingStarted-Pre-InstallationRequirements">Pre-Installation Requirements</h2><p><strong>Hardware:</strong></p><ul><li>~ 60 MB of free disk space for the ActiveMQ 5.x binary distribution.<br clear="none">(you need additional disk space for storing persistent messages to disk)</li><li>~ 300 MB of free disk space for the ActiveMQ 5.x source or developer's distributions.</li></ul><p><strong>Operating Systems:</strong></p><ul><li>Windows: Windows XP SP2, Windows 2000, Windows Vista, Windows 7.</li><li>Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, or any Unix platform that supports Java.</li></ul><p><strong>Environment:</strong></p><ul><li><a shape="rect" class="external-link" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html" rel="nofollow">Java Runtime Environment (JRE)</a>  <strong>JRE 1.7</strong> (1.6 for version <=5.10.0)<br clear="none">(a JDK is required if you plan to recompile source code)</li><li>The JAVA_HOME environment variable must be set to the directory where the JRE is installed<br clear="none">(Unix: the binary "java" has to be resolvable by the PATH variable; execute "which java" to verify)</li><li><a shape="rect" class="external-link" href="http://maven.apache.org/">Maven</a> 3.0.0 build system<br clear="none">(only if you plan to recompile source code)</li><li><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/geronimo-spec/jars/">JARs</a> that will be used must be added to the classpath.<br clear="none">(only if you plan to recompile source code)</li></ul><h2 id="GettingStarted-InstallationProcedureforWindows">Installation Procedure for Windows</h2><p>This section of the Getting Started Guide explains how to install binary and source distributions of ActiveMQ on a Windows system.</p><h4 id="GettingStarted-WindowsBinaryInstallation">Windows Binary Installation</h4><p>This procedure explains how to download and install the binary distribution on a Windows system.</p><ol><li>Download the latest release<br clear="none">(see <a shape="rect" href="download.xml">Download</a> -> "The latest stable release" -> "<span class="external-link">apache-activemq-x.x.x-bin.zip</span>")</li><li>Extract the files from the ZIP file into a directory of your choice.</li><li>Proceed to the <a shape="rect" href="#GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.</li><li>Following start-up, go to the <a shape="rect" href="#GettingStarted-TestingtheInstallation">#Testing the Installation</a> section of this document.</li></ol><h4 id="GettingStarted-WindowsSourceInstallation">Windows Source Installation</h4><p>This procedure explains how to download and install the source distribution on a Windows system.</p><ol><li>Download the latest release<br clear="none">(see <a shape="rect" href="download.xml">Download</a> -> "The latest stable release" -> "<span class="external-link">apache-activemq-x.x.x-source-release.zip</span>")</li><li>Extract ActiveMQ from the ZIP file into a directory of your choice.</li><li><p><span class="confluence-anchor-link" id="GettingStarted-WindowsSourceInstallation"></span><br clear="none">The recommended method of building ActiveMQ is the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[REM add "-Dmaven.test.skip=true" if tests are failing on your system (should not happen)
+<div class="wiki-content maincontent"><h2>Introduction</h2><p>This document describes how to install and configure ActiveMQ 4.x/5.x for both Unix and Windows' platforms.</p><h2>Document Organization</h2><p class="confluence-link">The Getting Started Guide for ActiveMQ 4.x document contains the following sections:</p><p class="confluence-link"><structured-macro ac:macro-id="83d4dda2-6235-4647-bb2f-2fdaf82efe66" ac:name="toc" ac:schema-version="1"></structured-macro></p><h2>Pre-Installation Requirements</h2><p><strong>Hardware:</strong></p><ul><li>~ 60 MB of free disk space for the ActiveMQ 5.x binary distribution.<br clear="none">(you need additional disk space for storing persistent messages to disk)</li><li>~ 300 MB of free disk space for the ActiveMQ 5.x source or developer's distributions.</li></ul><p><strong>Operating Systems:</strong></p><ul><li>Windows: Windows XP SP2, Windows 2000, Windows Vista, Windows 7.</li><li>Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, or any Unix platform that supports Java.</li></ul><p><strong>Environment:</strong></p><ul><li><a shape="rect" href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Java Runtime Environment (JRE)</a>  <strong>JRE 1.7</strong> (1.6 for version <=5.10.0)<br clear="none">(a JDK is required if you plan to recompile source code)</li><li>The JAVA_HOME environment variable must be set to the directory where the JRE is installed<br clear="none">(Unix: the binary "java" has to be resolvable by the PATH variable; execute "which java" to verify)</li><li><a shape="rect" href="http://maven.apache.org/">Maven</a> 3.0.0 build system<br clear="none">(only if you plan to recompile source code)</li><li><a shape="rect" href="http://cvs.apache.org/repository/geronimo-spec/jars/">JARs</a> that will be used must be added to the classpath.<br clear="none">(only if you plan to recompile source code)</li></ul><h2>Installation Procedure for Windows</h2><p>This section of the Getting Started Guide explains how to install binary and source distributions of ActiveMQ on a Windows system.</p><h4>Windows Binary Installation</h4><p>This procedure explains how to download and install the binary distribution on a Windows system.</p><ol><li>Download the latest release<br clear="none">(see <link><page ri:content-title="Download"></page></link> -> "The latest stable release" -> "<span class="external-link">apache-activemq-x.x.x-bin.zip</span>")</li><li>Extract the files from the ZIP file into a directory of your choice.</li><li>Proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.</li><li>Following start-up, go to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section of this document.</li></ol><h4>Windows Source Installation</h4><p>This procedure explains how to download and install the source distribution on a Windows system.</p><ol><li>Download the latest release<br clear="none">(see <link><page ri:content-title="Download"></page></link> -> "The latest stable release" -> "<span class="external-link">apache-activemq-x.x.x-source-release.zip</span>")</li><li>Extract ActiveMQ from the ZIP file into a directory of your choice.</li><li><p><structured-macro ac:macro-id="12713513-1e78-4853-94d7-aead9600d31f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Windows Source Installation</parameter></structured-macro><br clear="none">The recommended method of building ActiveMQ is the following:</p><structured-macro ac:macro-id="7517318b-d32d-4ffb-8d12-a0e79decca5f" ac:name="code" ac:schema-version="1"><plain-text-body>REM add "-Dmaven.test.skip=true" if tests are failing on your system (should not happen)
mvn clean install
-]]></script>
-</div></div><p>where [activemq_install_dir] is the directory in which ActiveMQ was installed.</p></li><li><p>If you prefer to use an IDE, then you can auto-generate the IDE's project file using maven plugins:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn eclipse:eclipse
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn idea:idea
-]]></script>
-</div></div><p>Feel free to use any other applicable IDE. Please refer to the <a shape="rect" class="external-link" href="http://maven.apache.org/reference/plugins/plugins.html">plugin reference</a> for more details.</p></li></ol><ol><li><p>Start ActiveMQ from the target directory, for example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]\assembly\target
+</plain-text-body></structured-macro><p>where [activemq_install_dir] is the directory in which ActiveMQ was installed.</p></li><li><p>If you prefer to use an IDE, then you can auto-generate the IDE's project file using maven plugins:</p><structured-macro ac:macro-id="5e3e66c2-a3f9-4106-acbf-b4f0f92bbc6f" ac:name="code" ac:schema-version="1"><plain-text-body>mvn eclipse:eclipse
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="ffbbf3b4-818d-49da-bff7-1f7aa7d3002e" ac:name="code" ac:schema-version="1"><plain-text-body>mvn idea:idea
+</plain-text-body></structured-macro><p>Feel free to use any other applicable IDE. Please refer to the <a shape="rect" href="http://maven.apache.org/reference/plugins/plugins.html">plugin reference</a> for more details.</p></li></ol><ol><li><p>Start ActiveMQ from the target directory, for example:</p><structured-macro ac:macro-id="bad7063a-88b2-400d-a879-ee55bbb0a9cb" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]\assembly\target
unzip activemq-x.x-SNAPSHOT.zip
cd activemq-x.x-SNAPSHOT
bin\activemq
-]]></script>
-</div></div><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create the working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p></li><li><p>Proceed to the <a shape="rect" href="#GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you are building ActiveMQ 4.x under Windows using Cygwin there is a path name length limitation. If the path name length is exceeded, you may see build errors. To correct this, move the ActiveMQ source directory higher in the file system tree, e.g., /cygdrive/c/d/sm.</p></div></div></li></ol><h4 id="GettingStarted-WindowsDeveloper'sRelease">Windows Developer's Release</h4><p>This procedure explains how to download and install the latest developer's snapshot.</p><ol><li>Open the release archive: <a shape="rect" class="external-link" href="https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/">https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/</a><br clear="none">(open one of the SNAPSHOT directories)</li><li>Select the version of ActiveMQ to download (if necessary, scroll down to see the ActiveMQ snapshots).</li><li>Extract the files from the ZIP file into a directory of your choice.</li><li>If a binary snapshot was downloaded, proceed to the <a shape="rect" href="#GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.<br clear="none"> If a source snapshot was downloaded, perform step 6 and step 7 of the <a shape="rect" href="#GettingStarted-WindowsSourceInstallation">#Windows Source Installation</a> procedure.</li><li>Following start-up, proceed to the <a shape="rect" href="#GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><h2 id="GettingStarted-InstallationProcedureforUnix">Installation Procedure for Unix</h2><h4 id="GettingStarted-UnixBinaryInstallationUnixBinaryInstallation"><span class="confluence-anchor-link" id="GettingStarted-UnixBinaryInstallation"></span> Unix Binary Installation</h4><p>This procedure explains how to download and install the binary distribution on a Unix system.<br clear="none"> <strong>NOTE:</strong> There are several alternative ways to perform this type of installation.</p><ol><li><p>Download the activemq zipped tarball file to the Unix machine, using either a browser or a tool, i.e., wget, scp, ftp, etc. for example:<br clear="none">(see <a shape="rect" href="download.xml">Download</a> -> "The latest stable release")</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[wget http://activemq.apache.org/path/tofile/apache-activemq-x.x.x-bin.tar.gz
-]]></script>
-</div></div></li><li><p>Extract the files from the zipped tarball into a directory of your choice. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
+</plain-text-body></structured-macro><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create the working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p></li><li><p>Proceed to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</p><structured-macro ac:macro-id="96beee6a-1399-4d29-bb22-06d5e8ec4bd4" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>If you are building ActiveMQ 4.x under Windows using Cygwin there is a path name length limitation. If the path name length is exceeded, you may see build errors. To correct this, move the ActiveMQ source directory higher in the file system tree, e.g., /cygdrive/c/d/sm.</p></rich-text-body></structured-macro></li></ol><h4>Windows Developer's Release</h4><p>This procedure explains how to download and install the latest developer's snapshot.</p><ol><li>Open the release archive: <a shape="rect" href="https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/">https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/</a><br clear="none">(open one of the SNAPSHOT directories)</li><li>Select the version of ActiveMQ to download (if necessary, scroll down to see the ActiveMQ snapshots).</li><li>Extract the files from the ZIP file into a directory of your choice.</li><li>If a binary snapshot was downloaded, proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.<br clear="none"> If a source snapshot was downloaded, perform step 6 and step 7 of the <link ac:anchor="Windows Source Installation"><plain-text-link-body>#Windows Source Installation</plain-text-link-body></link> procedure.</li><li>Following start-up, proceed to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><h2>Installation Procedure for Unix</h2><h4><structured-macro ac:macro-id="4f054d84-738e-410c-b571-1e89ae9dc91c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Unix Binary Installation</parameter></structured-macro> Unix Binary Installation</h4><p>This procedure explains how to download and install the binary distribution on a Unix system.<br clear="none"> <strong>NOTE:</strong> There are several alternative ways to perform this type of installation.</p><ol><li><p>Download the activemq zipped tarball file to the Unix machine, using either a browser or a tool, i.e., wget, scp, ftp, etc. for example:<br clear="none">(see <link><page ri:content-title="Download"></page></link> -> "The latest stable release")</p><structured-macro ac:macro-id="df6f9691-1cfa-476b-8f95-f2a1b5f3960a" ac:name="code" ac:schema-version="1"><plain-text-body>wget http://activemq.apache.org/path/tofile/apache-activemq-x.x.x-bin.tar.gz
+</plain-text-body></structured-macro></li><li><p>Extract the files from the zipped tarball into a directory of your choice. For example:</p><structured-macro ac:macro-id="6eb21686-0107-4421-a955-e57803e67163" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
tar zxvf activemq-x.x.x-bin.tar.gz
-]]></script>
-</div></div></li><li><p>Proceed to the <a shape="rect" href="#GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.</p></li><li>Following start-up, go to the <a shape="rect" href="#GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><h4 id="GettingStarted-UsingHomebrewinstalleronOSX">Using Homebrew installer on OSX</h4><p>If you use OSX as your platform, you can use <a shape="rect" class="external-link" href="http://mxcl.github.com/homebrew/" rel="nofollow">Homebrew</a> package manager to easily install Apache ActiveMQ.</p><ol><li><p>After installing Homebrew package manager successfully, just run</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ brew install apache-activemq
-]]></script>
-</div></div><p>You can expect the following output:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[==> Downloading http://www.gossipcheck.com/mirrors/apache/activemq/apache-activemq/x.x.x/apache-activemq-x.x.x-bin.tar.gz
+</plain-text-body></structured-macro></li><li><p>Proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.</p></li><li>Following start-up, go to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><h4>Using Homebrew installer on OSX</h4><p>If you use OSX as your platform, you can use <a shape="rect" href="http://mxcl.github.com/homebrew/">Homebrew</a> package manager to easily install Apache ActiveMQ.</p><ol><li><p>After installing Homebrew package manager successfully, just run</p><structured-macro ac:macro-id="043a2c7d-bc97-4a14-83e6-5ee04057a267" ac:name="code" ac:schema-version="1"><plain-text-body>$ brew install apache-activemq
+</plain-text-body></structured-macro><p>You can expect the following output:</p><structured-macro ac:macro-id="4213c84c-66dd-42d4-94ee-9e59edd230df" ac:name="code" ac:schema-version="1"><plain-text-body>==> Downloading http://www.gossipcheck.com/mirrors/apache/activemq/apache-activemq/x.x.x/apache-activemq-x.x.x-bin.tar.gz
######################################################################## 100.0%
==> Caveats
Software was installed to:
/usr/local/Cellar/apache-activemq/x.x.x/libexec
==> Summary
/usr/local/Cellar/apache-activemq/x.x.x: 406 files, 35M, built in 2 seconds
-]]></script>
-</div></div></li></ol><p>ActiveMQ will be installed in <code>/usr/local/Cellar/apache-activemq/x.x.x/</code> directory (where <code>x.x.x</code> denotes the actual version being installed).</p><p>Now you can proceed to <a shape="rect" href="#GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> and <a shape="rect" href="#GettingStarted-TestingtheInstallation">#Testing the Installation</a> sections.</p><h4 id="GettingStarted-UnixSourceInstallation">Unix Source Installation</h4><p>This procedure explains how to download and install the source distribution on a Unix system. This procedure assumes the Unix machine has a browser. Please see the previous <a shape="rect" href="#GettingStarted-UnixBinaryInstallation">#Unix Binary Installation</a> section for details on how to install ActiveMQ without a browser.</p><ol><li>Download the latest source release<br clear="none">(see <a shape="rect" href="download.xml">Download</a> -> "The latest stable release" -> "<span class="external-link">activemq-parent-x.x.x-source-release.zip</span>")</li><li><p>Extract the files from the ZIP file into a directory of your choice. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tar zxvf activemq.x.x-src.tar.gz
-]]></script>
-</div></div></li><li><p>Build ActiveMQ using Maven:<br clear="none"> The preferred method of building ActiveMQ is the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
-mvn clean install # add "-Dmaven.test.skip=true" if tests are failing on your system (should not happen)]]></script>
-</div></div><p>If Maven crashes with a java.lang.OutOfMemoryError, you you need to do this first (assuming a Bourne-like shell):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[export MAVEN_OPTS="-Xmx512M"
-]]></script>
-</div></div><p>If you prefer to use an IDE then you can auto-generate the IDE's project file using maven plugins:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn eclipse:eclipse
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn idea:idea
-]]></script>
-</div></div><p>Feel free to use any other applicable IDE. Please refer to the <a shape="rect" class="external-link" href="http://maven.apache.org/reference/plugins/plugins.html">plugin reference</a> for more details.<br clear="none"> <strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p></li><li>Proceed to the <a shape="rect" href="#GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.</li><li>Proceed to <a shape="rect" href="#GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><h4 id="GettingStarted-UnixDeveloper'sRelease">Unix Developer's Release</h4><p>This procedure explains how to download and install the latest developer's snapshot.</p><ol><li>Open the release archive: <a shape="rect" class="external-link" href="https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/">https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/</a><br clear="none">(open one of the SNAPSHOT directories)</li><li>Select the version of ActiveMQ to download (you may have to scroll down to see the ActiveMQ snapshots). <br clear="none">The filename will be similar to: <code>activemq-x.x.x-tar.gz</code>.</li><li><p>Extract the files from the gzip file into a directory of your choice. For example:<br clear="none"> For a binary developer's snapshot:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tar zxvf activemq-x.x.x.tar.gz
-]]></script>
-</div></div><p>For a source developer's snapshot:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tar zxvf activemq-x.x.x-src.tar.gz
-]]></script>
-</div></div></li><li><p>If a binary snapshot was downloaded, to make it executable, the <code>ActiveMQ</code> script may need its permissions changed:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]/bin
+</plain-text-body></structured-macro></li></ol><p>ActiveMQ will be installed in <code>/usr/local/Cellar/apache-activemq/x.x.x/</code> directory (where <code>x.x.x</code> denotes the actual version being installed).</p><p>Now you can proceed to <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> and <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> sections.</p><h4>Unix Source Installation</h4><p>This procedure explains how to download and install the source distribution on a Unix system. This procedure assumes the Unix machine has a browser. Please see the previous <link ac:anchor="Unix Binary Installation"><plain-text-link-body>#Unix Binary Installation</plain-text-link-body></link> section for details on how to install ActiveMQ without a browser.</p><ol><li>Download the latest source release<br clear="none">(see <link><page ri:content-title="Download"></page></link> -> "The latest stable release" -> "<span class="external-link">activemq-parent-x.x.x-source-release.zip</span>")</li><li><p>Extract the files from the ZIP file into a directory of your choice. For example:</p><structured-macro ac:macro-id="927fbb02-22fd-4c91-a5c3-7aa9501dc756" ac:name="code" ac:schema-version="1"><plain-text-body>tar zxvf activemq.x.x-src.tar.gz
+</plain-text-body></structured-macro></li><li><p>Build ActiveMQ using Maven:<br clear="none"> The preferred method of building ActiveMQ is the following:</p><structured-macro ac:macro-id="5826269a-b0d2-475b-89ce-9fe77715a810" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
+mvn clean install # add "-Dmaven.test.skip=true" if tests are failing on your system (should not happen)</plain-text-body></structured-macro><p>If Maven crashes with a java.lang.OutOfMemoryError, you you need to do this first (assuming a Bourne-like shell):</p><structured-macro ac:macro-id="10e06e10-3e8d-4dfd-a58b-6a0f5c4df243" ac:name="code" ac:schema-version="1"><plain-text-body>export MAVEN_OPTS="-Xmx512M"
+</plain-text-body></structured-macro><p>If you prefer to use an IDE then you can auto-generate the IDE's project file using maven plugins:</p><structured-macro ac:macro-id="837cdfc6-8605-4279-b050-9c5d5f799b99" ac:name="code" ac:schema-version="1"><plain-text-body>mvn eclipse:eclipse
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="ab1ca934-28d3-4c3d-bcb8-a8b293855006" ac:name="code" ac:schema-version="1"><plain-text-body>mvn idea:idea
+</plain-text-body></structured-macro><p>Feel free to use any other applicable IDE. Please refer to the <a shape="rect" href="http://maven.apache.org/reference/plugins/plugins.html">plugin reference</a> for more details.<br clear="none"> <strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p></li><li>Proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.</li><li>Proceed to <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><h4>Unix Developer's Release</h4><p>This procedure explains how to download and install the latest developer's snapshot.</p><ol><li>Open the release archive: <a shape="rect" href="https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/">https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/</a><br clear="none">(open one of the SNAPSHOT directories)</li><li>Select the version of ActiveMQ to download (you may have to scroll down to see the ActiveMQ snapshots). <br clear="none">The filename will be similar to: <code>activemq-x.x.x-tar.gz</code>.</li><li><p>Extract the files from the gzip file into a directory of your choice. For example:<br clear="none"> For a binary developer's snapshot:</p><structured-macro ac:macro-id="753d5cb8-9c85-451e-ad97-7e488ebe7469" ac:name="code" ac:schema-version="1"><plain-text-body>tar zxvf activemq-x.x.x.tar.gz
+</plain-text-body></structured-macro><p>For a source developer's snapshot:</p><structured-macro ac:macro-id="210f3fa1-edaa-4dec-96ba-b09493a7b67b" ac:name="code" ac:schema-version="1"><plain-text-body>tar zxvf activemq-x.x.x-src.tar.gz
+</plain-text-body></structured-macro></li><li><p>If a binary snapshot was downloaded, to make it executable, the <code>ActiveMQ</code> script may need its permissions changed:</p><structured-macro ac:macro-id="cb9549fd-d58b-4277-a978-4e8637b21118" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]/bin
chmod 755 activemq
-]]></script>
-</div></div></li><li>For a binary snapshot, proceed to the <a shape="rect" href="#GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.</li><li>If a source snapshot was downloaded perform steps 6 - 8 of the <a shape="rect" href="#GettingStarted-UnixSourceInstallation">#Unix Source Installation</a> procedure.</li><li>Proceed to the <a shape="rect" href="#GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><h2 id="GettingStarted-StartingActiveMQStartingActiveMQ"><span class="confluence-anchor-link" id="GettingStarted-StartingActiveMQ"></span> Starting ActiveMQ</h2><p>There now follows instructions on how to <a shape="rect" href="run-broker.xml">run the ActiveMQ Message Broker</a>.</p><h4 id="GettingStarted-OnWindows:">On Windows:</h4><p>From a console window, change to the installation directory and run <code>ActiveMQ</code>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
-]]></script>
-</div></div><p>where <code>activemq_install_dir</code> is the directory in which ActiveMQ was installed, e.g., <code>c:\Program Files\ActiveMQ-5.x</code>. <br clear="none" class="atl-forced-newline"> Then type:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin\activemq start
-]]></script>
-</div></div><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p><h4 id="GettingStarted-OnUnix:">On Unix:</h4><p>From a command shell, change to the installation directory and run <code>ActiveMQ</code> as a <strong>foregroud</strong> process:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]/bin
-./activemq console]]></script>
-</div></div><p>From a command shell, change to the installation directory and run <code>ActiveMQ</code> as a <strong>daemon</strong> process:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]/bin
-./activemq start]]></script>
-</div></div><h3 id="GettingStarted-Morehelp">More help</h3><p>For other ways of running the broker see <a shape="rect" href="run-broker.xml">Here</a>. For example you can run an <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">embedded broker</a> inside your JMS Connection to avoid starting a separate process.</p><h2 id="GettingStarted-TestingtheInstallationTestingtheInstallation"><span class="confluence-anchor-link" id="GettingStarted-TestingtheInstallation"></span> Testing the Installation</h2><h3 id="GettingStarted-Usingtheadministrativeinterface">Using the administrative interface</h3><ul><li>Open the administrative interface</li><li style="list-style-type: none;background-image: none;"><ul><li>URL: <a shape="rect" class="external-link" href="http://127.0.0.1:8161/admin/" rel="nofollow">http://127.0.0.1:8161/admin/</a></li><li>Login: admin</li><li>Passwort: admin</li></ul></li><li>Navigate to "Queues"</li><li>Add a queue name and click create</li><li>Send test message by klicking on "Send to"</li></ul><h3 id="GettingStarted-Logfileandconsoleoutput">Logfile and console output</h3><p>If ActiveMQ is up and running without problems, the Window's console window or the Unix command shell will display information similar to the following log line:<br clear="none">(see stdout output or "[activemq_install_dir]/data/activemq.log")</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Apache ActiveMQ 5.11.1 (localhost, ID:ntbk11111-50816-1428933306116-0:1) started | org.apache.activemq.broker.BrokerService | main
-]]></script>
-</div></div><h3 id="GettingStarted-Listenport">Listen port</h3><p>ActiveMQ's default port is 61616. From another window run netstat and search for port 61616.</p><p>From a Windows console, type:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[netstat -an|find "61616"
-]]></script>
-</div></div><p><strong>OR</strong></p><p>From a Unix command shell, type:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[netstat -nl|grep 61616
-]]></script>
-</div></div><h2 id="GettingStarted-MonitoringActiveMQ">Monitoring ActiveMQ</h2><p>You can monitor ActiveMQ using the <a shape="rect" href="web-console.xml">Web Console</a> by pointing your browser at</p><p><a shape="rect" class="external-link" href="http://localhost:8161/admin" rel="nofollow">http://localhost:8161/admin</a></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>From ActiveMQ 5.8 onwards the web apps is secured out of the box.<br clear="none"> The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.</p></div></div><p>Or you can use the <a shape="rect" href="jmx.xml">JMX</a> support to view the running state of ActiveMQ.</p><p>For more information see the file <code>docs/WebConsole-README.txt</code> in the distribution.</p><h2 id="GettingStarted-StoppingActiveMQ">Stopping ActiveMQ</h2><p>For both Windows and Unix installations, terminate ActiveMQ by typing "CTRL-C" in the console or command shell in which it is running.</p><p>If ActiveMQ was started in the background on Unix, the process can be killed, with the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]/bin
+</plain-text-body></structured-macro></li><li>For a binary snapshot, proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.</li><li>If a source snapshot was downloaded perform steps 6 - 8 of the <link ac:anchor="Unix Source Installation"><plain-text-link-body>#Unix Source Installation</plain-text-link-body></link> procedure.</li><li>Proceed to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><h2><structured-macro ac:macro-id="2fd79e3b-e06e-4195-8fec-e57603deeb44" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Starting ActiveMQ</parameter></structured-macro> Starting ActiveMQ</h2><p>There now follows instructions on how to <link><page ri:content-title="Run Broker"></page><plain-text-link-body>run the ActiveMQ Message Broker</plain-text-link-body></link>.</p><h4>On Windows:</h4><p>From a console window, change to the installation directory and run <code>ActiveMQ</code>:</p><structured-macro ac:macro-id="cf300c16-c08f-461b-89a0-7843597e1d37" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
+</plain-text-body></structured-macro><p>where <code>activemq_install_dir</code> is the directory in which ActiveMQ was installed, e.g., <code>c:\Program Files\ActiveMQ-5.x</code>. <br clear="none" class="atl-forced-newline"> Then type:</p><structured-macro ac:macro-id="d3c78c22-4903-4bc2-ae87-aa44b9e9d65e" ac:name="code" ac:schema-version="1"><plain-text-body>bin\activemq start
+</plain-text-body></structured-macro><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p><h4>On Unix:</h4><p>From a command shell, change to the installation directory and run <code>ActiveMQ</code> as a <strong>foregroud</strong> process:</p><structured-macro ac:macro-id="17788469-2f81-4294-addd-dba15eee852e" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]/bin
+./activemq console</plain-text-body></structured-macro><p>From a command shell, change to the installation directory and run <code>ActiveMQ</code> as a <strong>daemon</strong> process:</p><structured-macro ac:macro-id="233f7a71-6b58-4eb9-8185-7fa8af92a759" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]/bin
+./activemq start</plain-text-body></structured-macro><h3>More help</h3><p>For other ways of running the broker see <link><page ri:content-title="Run Broker"></page><plain-text-link-body>Here</plain-text-link-body></link>. For example you can run an <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>embedded broker</plain-text-link-body></link> inside your JMS Connection to avoid starting a separate process.</p><h2><structured-macro ac:macro-id="f5fd2cc6-ce2a-408e-a349-8a0a70273b0f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Testing the Installation</parameter></structured-macro> Testing the Installation</h2><h3>Using the administrative interface</h3><ul><li>Open the administrative interface</li><li style="list-style-type: none;background-image: none;"><ul><li>URL: <a shape="rect" href="http://127.0.0.1:8161/admin/">http://127.0.0.1:8161/admin/</a></li><li>Login: admin</li><li>Passwort: admin</li></ul></li><li>Navigate to "Queues"</li><li>Add a queue name and click create</li><li>Send test message by klicking on "Send to"</li></ul><h3>Logfile and console output</h3><p>If ActiveMQ is up and running without problems, the Window's console window or the Unix command shell will display information similar to the following log line:<br clear="none">(see stdout output or "[activemq_install_dir]/data/activemq.log")</p><structured-macro ac:macro-id="acba31d9-fffc-4d2f-a2d6-a8c2f84605e2" ac:name="code" ac:schema-version="1"><plain-text-body>Apache ActiveMQ 5.11.1 (localhost, ID:ntbk11111-50816-1428933306116-0:1) started | org.apache.activemq.broker.BrokerService | main
+</plain-text-body></structured-macro><h3>Listen port</h3><p>ActiveMQ's default port is 61616. From another window run netstat and search for port 61616.</p><p>From a Windows console, type:</p><structured-macro ac:macro-id="45b33dc5-47a0-4333-9823-42c08431ad51" ac:name="code" ac:schema-version="1"><plain-text-body>netstat -an|find "61616"
+</plain-text-body></structured-macro><p><strong>OR</strong></p><p>From a Unix command shell, type:</p><structured-macro ac:macro-id="48ad0806-4478-4942-b4cb-258f9c390733" ac:name="code" ac:schema-version="1"><plain-text-body>netstat -nl|grep 61616
+</plain-text-body></structured-macro><h2>Monitoring ActiveMQ</h2><p><structured-macro ac:macro-id="0c439581-e0ce-4a78-8ac2-8f01d36f2ca6" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Monitoring ActiveMQ"></page></link></parameter></structured-macro></p><h2>Stopping ActiveMQ</h2><p>For both Windows and Unix installations, terminate ActiveMQ by typing "CTRL-C" in the console or command shell in which it is running.</p><p>If ActiveMQ was started in the background on Unix, the process can be killed, with the following:</p><structured-macro ac:macro-id="6be78f73-6679-4ebd-9102-c0ff5ec26b6f" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]/bin
./activemq stop
-]]></script>
-</div></div><h2 id="GettingStarted-ConfiguringActiveMQ">Configuring ActiveMQ</h2><p>The ActiveMQ broker should now run. You can configure the broker by specifying an <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> file as a parameter to the <em>activemq</em> command. An alternative is to use the <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a> to configure things on the command line in a concise format (though the configuration options are not as extensive as if you use Java or XML code). You can also</p><p>Also see <a shape="rect" href="configuring-transports.xml">Configuring Transports</a> to see how you can configure the various connection, transport and broker options using the connection URL in the ActiveMQConnectionFactory.</p><p>See the <a shape="rect" href="initial-configuration.xml">Initial Configuration</a> for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code</p><p>If you want to use JNDI to connect to your JMS provider then please view the <a shape="rect" href="jndi-support.xml">JNDI Support</a>. If you are a Spring user you should read about <a shape="rect" href="spring-support.xml">Spring Support</a></p><p>After the installation, ActiveMQ is running with a basic configuration. For details on configuring options, please see refer to the <a shape="rect" href="configuration.xml">Configuration</a> section.</p><h2 id="GettingStarted-AdditionalResources">Additional Resources</h2><p>If you are new to using ActiveMQ, running the <a shape="rect" href="web-samples.xml">Web Samples</a> or the <a shape="rect" href="examples.xml">Examples</a> is a good next step to learn more about ActiveMQ.</p><p>The Commercial Providers listed on the <a shape="rect" href="support.xml">Support</a> page may also have additional documentation, examples, tutorials, etc... that can help you get started.</p></div>
+</plain-text-body></structured-macro><h2>Configuring ActiveMQ</h2><p>The ActiveMQ broker should now run. You can configure the broker by specifying an <link><page ri:content-title="Xml Configuration"></page></link> file as a parameter to the <em>activemq</em> command. An alternative is to use the <link><page ri:content-title="Broker Configuration URI"></page></link> to configure things on the command line in a concise format (though the configuration options are not as extensive as if you use Java or XML code). You can also</p><p>Also see <link><page ri:content-title="Configuring Transports"></page></link> to see how you can configure the various connection, transport and broker options using the connection URL in the ActiveMQConnectionFactory.</p><p>See the <link><page ri:content-title="Initial Configuration"></page></link> for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code</p><p>If you want to use JNDI to connect to your JMS provider then please view the <link><page ri:content-title="JNDI Support"></page></link>. If you are a Spring user you should read about <link><page ri:content-title="Spring Support"></page></link></p><p>After the installation, ActiveMQ is running with a basic configuration. For details on configuring options, please see refer to the <link><page ri:content-title="Configuration"></page></link> section.</p><h2>Additional Resources</h2><p>If you are new to using ActiveMQ, running the <link><page ri:content-title="Web Samples"></page></link> or the <link><page ri:content-title="Examples"></page></link> is a good next step to learn more about ActiveMQ.</p><p>The Commercial Providers listed on the <link><page ri:content-title="Support"></page></link> page may also have additional documentation, examples, tutorials, etc... that can help you get started.</p></div>
diff --git a/group-membership.xml b/group-membership.xml
index 3e5e3c8..a21c361 100644
--- a/group-membership.xml
+++ b/group-membership.xml
@@ -2,17 +2,16 @@
You have to explicitly say which group you want to join/leave - and you can join multiple groups.<br clear="none">
Each GroupChannel has both a globally unique id and a name.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a74c7a79-dbfb-4d45-befd-60b5910478b9" ac:name="code" ac:schema-version="1"><plain-text-body>
import org.apache.activeblaze.group.*;
...
BlazeGroupChannelFactory factory = new BlazeGroupChannelFactory();
-BlazeGroupChannel channel = factory.createGroupChannel("My Channel");
+BlazeGroupChannel channel = factory.createGroupChannel("My Channel");
//join a group
-channel.addToGroup("test");
+channel.addToGroup("test");
channel.start();
//listen for other members
@@ -20,14 +19,13 @@
channel.addMemberChangedListener(new MemberChangedListener(){
public void memberStarted(Member member) {
- System.out.println("Member started");
+ System.out.println("Member started");
}
public void memberStopped(Member member) {
- System.out.println("Member stopped");
+ System.out.println("Member stopped");
}
});
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/hello-world.xml b/hello-world.xml
index d7bb4ea..b77074d 100644
--- a/hello-world.xml
+++ b/hello-world.xml
@@ -1,12 +1,11 @@
-<div class="wiki-content maincontent"><p>The following is a very simple JMS application with multiple, concurrent, consumers and producers. See the <a shape="rect" href="initial-configuration.xml">Initial Configuration</a> guide for details on how to setup your classpath correctly.</p>
+<div class="wiki-content maincontent"><p>The following is a very simple JMS application with multiple, concurrent, consumers and producers. See the <link><page ri:content-title="Initial Configuration"></page></link> guide for details on how to setup your classpath correctly.</p>
<p>Things you might do after running this example:</p>
-<ul class="alternate"><li><a shape="rect" href="run-broker.xml">Setup a broker</a> instead of using the org.activemq.broker.impl.Main class directly</li><li>Use JNDI to lookup a javax.jms.ConnectionFactory rather than creating ActiveMQConnectionFactory directly.</li><li>Implement the javax.jms.MessageListener interface rather than calling consumer.receive()</li><li>Use transactional sessions</li><li>Use a Topic rather than a queue</li></ul>
+<ul class="alternate"><li><link><page ri:content-title="Run Broker"></page><link-body>Setup a broker</link-body></link> instead of using the org.activemq.broker.impl.Main class directly</li><li>Use JNDI to lookup a javax.jms.ConnectionFactory rather than creating ActiveMQConnectionFactory directly.</li><li>Implement the javax.jms.MessageListener interface rather than calling consumer.receive()</li><li>Use transactional sessions</li><li>Use a Topic rather than a queue</li></ul>
<p>The point of this example is to show you the basic code required to use JMS in a straightforward way. The Consumers and Producers could very easy be on completely different machines or in different processes.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>App.java</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9a9982ea-46ba-4ce4-a8d8-8aaa2cc93092" ac:name="code" ac:schema-version="1"><parameter ac:name="title">App.java</parameter><plain-text-body>
import org.apache.activemq.ActiveMQConnectionFactory;
import javax.jms.Connection;
@@ -65,7 +64,7 @@
public void run() {
try {
// Create a ConnectionFactory
- ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost");
+ ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost");
// Create a Connection
Connection connection = connectionFactory.createConnection();
@@ -75,18 +74,18 @@
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
// Create the destination (Topic or Queue)
- Destination destination = session.createQueue("TEST.FOO");
+ Destination destination = session.createQueue("TEST.FOO");
// Create a MessageProducer from the Session to the Topic or Queue
MessageProducer producer = session.createProducer(destination);
producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
// Create a messages
- String text = "Hello world! From: " + Thread.currentThread().getName() + " : " + this.hashCode();
+ String text = "Hello world! From: " + Thread.currentThread().getName() + " : " + this.hashCode();
TextMessage message = session.createTextMessage(text);
// Tell the producer to send the message
- System.out.println("Sent message: "+ message.hashCode() + " : " + Thread.currentThread().getName());
+ System.out.println("Sent message: "+ message.hashCode() + " : " + Thread.currentThread().getName());
producer.send(message);
// Clean up
@@ -94,7 +93,7 @@
connection.close();
}
catch (Exception e) {
- System.out.println("Caught: " + e);
+ System.out.println("Caught: " + e);
e.printStackTrace();
}
}
@@ -105,7 +104,7 @@
try {
// Create a ConnectionFactory
- ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost");
+ ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost");
// Create a Connection
Connection connection = connectionFactory.createConnection();
@@ -117,7 +116,7 @@
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
// Create the destination (Topic or Queue)
- Destination destination = session.createQueue("TEST.FOO");
+ Destination destination = session.createQueue("TEST.FOO");
// Create a MessageConsumer from the Session to the Topic or Queue
MessageConsumer consumer = session.createConsumer(destination);
@@ -128,25 +127,24 @@
if (message instanceof TextMessage) {
TextMessage textMessage = (TextMessage) message;
String text = textMessage.getText();
- System.out.println("Received: " + text);
+ System.out.println("Received: " + text);
} else {
- System.out.println("Received: " + message);
+ System.out.println("Received: " + message);
}
consumer.close();
session.close();
connection.close();
} catch (Exception e) {
- System.out.println("Caught: " + e);
+ System.out.println("Caught: " + e);
e.printStackTrace();
}
}
public synchronized void onException(JMSException ex) {
- System.out.println("JMS Exception occured. Shutting down client.");
+ System.out.println("JMS Exception occured. Shutting down client.");
}
}
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/hermes-jms.xml b/hermes-jms.xml
index 19a3735..c832bc9 100644
--- a/hermes-jms.xml
+++ b/hermes-jms.xml
@@ -1,22 +1,22 @@
-<div class="wiki-content maincontent"><p>You can use ActiveMQ with <a shape="rect" class="external-link" href="http://hermesjms.sourceforge.net/" rel="nofollow">Hermes JMS</a> which is a graphical user interface for working with JMS queues. Please refer to the <a shape="rect" class="external-link" href="http://hermesjms.sourceforge.net/" rel="nofollow">Hermes JMS</a> site for detailed instructions on using this software. </p>
+<div class="wiki-content maincontent"><p>You can use ActiveMQ with <a shape="rect" href="http://hermesjms.sourceforge.net/">Hermes JMS</a> which is a graphical user interface for working with JMS queues. Please refer to the <a shape="rect" href="http://hermesjms.sourceforge.net/">Hermes JMS</a> site for detailed instructions on using this software. </p>
-<h3 id="HermesJms-Demo">Demo </h3>
+<h3>Demo </h3>
-<p>Mark Bucayan kindly submitted a <a shape="rect" class="external-link" href="http://activemq.codehaus.org/HermesAndActiveMQ.html" rel="nofollow">Flash demo</a> showing how to use ActiveMQ inside Hermes.</p>
+<p>Mark Bucayan kindly submitted a <a shape="rect" href="http://activemq.codehaus.org/HermesAndActiveMQ.html">Flash demo</a> showing how to use ActiveMQ inside Hermes.</p>
<p>Here are a few steps to get you started with ActiveMQ when using HermesJMS. </p>
-<h3 id="HermesJms-AddActiveMQasaProvider">Add ActiveMQ as a Provider</h3>
+<h3>Add ActiveMQ as a Provider</h3>
<p>You need to register the jars required to run ActiveMQ inside HermesJMS. To do this click on Options -> Preferences. Then on the Providers tab add the following jars: </p>
-<ul><li><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/org/apache/activemq/" rel="nofollow">activemq-all.jar</a> Choose the version that matches your projects needs.</li></ul>
+<ul><li><a shape="rect" href="http://repo1.maven.org/maven2/org/apache/activemq/">activemq-all.jar</a> Choose the version that matches your projects needs.</li></ul>
-<ul><li><a shape="rect" class="external-link" href="http://repo2.maven.org/maven2/org/apache/geronimo/specs/geronimo-j2ee-management_1.0_spec/1.0/geronimo-j2ee-management_1.0_spec-1.0.jar" rel="nofollow">geronimo-j2ee-management_1.0_spec-1.0.jar</a></li></ul>
+<ul><li><a shape="rect" href="http://repo2.maven.org/maven2/org/apache/geronimo/specs/geronimo-j2ee-management_1.0_spec/1.0/geronimo-j2ee-management_1.0_spec-1.0.jar">geronimo-j2ee-management_1.0_spec-1.0.jar</a></li></ul>
-<h3 id="HermesJms-ConfigureanActiveMQSession">Configure an ActiveMQ Session</h3>
+<h3>Configure an ActiveMQ Session</h3>
<p>On the Preferences dialog, the Sessions tab, create a new session using the org.activemq.ActiveMQConnectionFactory connection factory. </p>
@@ -24,15 +24,13 @@
<p>Finally you can add some Destinations to the dialog on this page. (Right click to add). Add the destination FOO.BAR for the default test programs.</p>
-<h3 id="HermesJms-Viewingmessagesonqueues">Viewing messages on queues</h3>
+<h3>Viewing messages on queues</h3>
<p>Use the tree control to open your session and the FOO.BAR destination. Try browse the queue. Then run the ActiveMQ sample producer via</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="83588121-5686-460b-b5c8-3a8d44c5eb45" ac:name="code" ac:schema-version="1"><plain-text-body>
mvn producer
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>And hitting refresh in HermesJMS and you should see the messages that have just been published.</p></div>
diff --git a/hermes-screenshot.xml b/hermes-screenshot.xml
index f3ed469..1f7f3f0 100644
--- a/hermes-screenshot.xml
+++ b/hermes-screenshot.xml
@@ -3,5 +3,5 @@
<p>The following is an example of running HermesJms with ActiveMQ on OS X</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://activemq.codehaus.org/hermes.png" data-image-src="http://activemq.codehaus.org/hermes.png"></span></p></div>
+<p><image><url ri:value="http://activemq.codehaus.org/hermes.png"></url></image></p></div>
diff --git a/how-can-i-add-a-new-type-of-transport.xml b/how-can-i-add-a-new-type-of-transport.xml
index f677b59..8da885f 100644
--- a/how-can-i-add-a-new-type-of-transport.xml
+++ b/how-can-i-add-a-new-type-of-transport.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><p>ActiveMQ is specifically designed to allow custom transports to be plugged in. You can programatically create TransportConnector instances and add them to the BrokerService in Java code using the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/apidocs/org/apache/activemq/broker/BrokerService.html#addConnector(org.apache.activemq.broker.TransportConnector)" rel="nofollow">BrokerService.addConnector() method</a></p>
+<div class="wiki-content maincontent"><p>ActiveMQ is specifically designed to allow custom transports to be plugged in. You can programatically create TransportConnector instances and add them to the BrokerService in Java code using the <a shape="rect" href="http://activemq.codehaus.org/maven/apidocs/org/apache/activemq/broker/BrokerService.html#addConnector(org.apache.activemq.broker.TransportConnector)">BrokerService.addConnector() method</a></p>
<p>or you can use the transport discovery mechanism, so that folks can just use your new transport using the neat URI syntax.</p>
-<p>The way it works is that the URI scheme (e.g. "vm") is used to find a text file on the classpath - <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/main/resources/META-INF/services/org/apache/activemq/transport/">here are all the schemes provided</a>.</p>
+<p>The way it works is that the URI scheme (e.g. "vm") is used to find a text file on the classpath - <a shape="rect" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/main/resources/META-INF/services/org/apache/activemq/transport/">here are all the schemes provided</a>.</p>
-<p>then the contents of the file is the class name of a Java class on the classpath which extends the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/apidocs/org/apache/activemq/transport/TransportFactory.html" rel="nofollow">TransportFactory class</a>.</p>
+<p>then the contents of the file is the class name of a Java class on the classpath which extends the <a shape="rect" href="http://activemq.codehaus.org/maven/apidocs/org/apache/activemq/transport/TransportFactory.html">TransportFactory class</a>.</p>
<p>Then once you've implemented a Transport and TransportFactory class, folks can use your new transport using a URI in the JMS client or broker XML config file using the URI using your new schema name. e.g. if you wrote a new <em>foo</em> transport, you could use a URI of <em>foo://localhost?myParam=bar</em></p></div>
diff --git a/how-can-i-avoid-serialization-of-objects-in-objectmessage.xml b/how-can-i-avoid-serialization-of-objects-in-objectmessage.xml
index 802c1f2..5a4a9bc 100644
--- a/how-can-i-avoid-serialization-of-objects-in-objectmessage.xml
+++ b/how-can-i-avoid-serialization-of-objects-in-objectmessage.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent">
-<p>Use the VM transport and see <a shape="rect" href="how-should-i-use-the-vm-transport.xml">details on how to disable serialization to pass by value</a></p></div>
+<p>Use the VM transport and see <link><page ri:content-title="How should I use the VM transport"></page><link-body>details on how to disable serialization to pass by value</link-body></link></p></div>
diff --git a/how-can-i-contribute.xml b/how-can-i-contribute.xml
index dbc4eb9..3f34ff5 100644
--- a/how-can-i-contribute.xml
+++ b/how-can-i-contribute.xml
@@ -1,17 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="HowcanIcontribute-HowcanIcontributetoApacheActiveMQ?">How can I contribute to Apache ActiveMQ?</h2>
+<div class="wiki-content maincontent"><h2>How can I contribute to Apache ActiveMQ?</h2>
-There are many ways you can help make ActiveMQ a better piece of software - please dive in and help!<p>Try surf the documentation - if somethings confusing or not clear, let us know. Download the code & try it out and see what you think. Browse the source code. Got an itch to scratch, want to tune some operation or add some feature?</p><p>Want to do some hacking on ActiveMQ? Try surfing to our <a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/AMQ">issue tracker</a> for open issues or features that need to be implemented, take ownership of an issue and try fix it.</p><h2 id="HowcanIcontribute-Gettingintouch">Getting in touch</h2><p>There are various ways of communicating with the ActiveMQ community.</p><ul class="alternate"><li>join us on the <a shape="rect" href="discussion-forums.xml">Discussion Forums</a> or subscribe to the <a shape="rect" href="mailing-lists.xml">Mailing Lists</a> and take part in any conversations</li><li><p>pop by on <span>in <a shape="rect" href="irc.xml">irc</a> and say hi</span></p></li><li>add some comments to the <a shape="rect" href="navigation.xml">wiki</a></li></ul><h2 id="HowcanIcontribute-Ifyoufindabugorproblem">If you find a bug or problem</h2><p>Please raise a new issue in our <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ">issue tracker</a></p><p>If you can create a JUnit test case then your issue is more likely to be resolved quicker.<br clear="none"> e.g. take a look at some of the existing <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tree;f=activemq-unit-tests/src/test;h=185a655c5200ed30fd2964bc236c18c5bde534c4;hb=refs/heads/master">unit tests cases</a></p><p>Then we can add your issue to the test suite and then we'll know when its really fixed and we can ensure that the problem <strong>stays fixed</strong> in future releases.</p><h2 id="HowcanIcontribute-Ifyouwanttohelpoutwiththedocumentation">If you want to help out with the documentation</h2><p>If you want to contribute to the ActiveMQ documentation you should first subscribe our <a shape="rect" class="external-link" href="mailto:dev-subscribe@activemq.apache.org" rel="nofollow">dev@</a> where ActiveMQ developers interact with each other. If you want edit rights on the ActiveMQ site, create an account in the <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ">ActiveMQ wiki</a> and fill in and submit an ICLA to the ASF (see the <a shape="rect" href="becoming-a-committer.xml">Committer Guide</a>). Then ask on the dev@ list to be granted edit rights and an admin will do so fairly quickly. If you want to just contribute the content, please submit the content on the dev@ list or create an issue and attach it there. <strong>All</strong> contributions are highly appreciated.</p><h2 id="HowcanIcontribute-Workingonthecode">Working on the code</h2><p>Grab the <a shape="rect" href="source.xml">Source</a> from git</p><p>Build the project.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=128M"
-mvn -Dtest=false install
-]]></script>
-</div></div><p>PS: You might need to build multiple times (if you get a build error) because sometimes maven fails to download all the files.</p><p>Create a project in your IDE. e.g. if you are using Eclipse the following should do the trick.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn eclipse:eclipse
-]]></script>
-</div></div><p>Then import the projects into your workspace.</p><h2 id="HowcanIcontribute-Creatingpatches">Creating patches</h2><p>We gladly accept patches if you can find ways to improve, tune or fix ActiveMQ in some way.</p><p>Most IDEs can create nice patches now very easily. e.g. in Eclipse just right click on a file/directory and select Team -> Create Patch. Then just save the patch as a file and then submit it. (You may have to click on Team -> Share... first to enable the Subversion options).</p><p>If you're a command line person try the following to create the patch</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[diff -u Main.java.orig Main.java >> patchfile.txt
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[git diff Main.java >> patchfile.txt
-]]></script>
-</div></div><h2 id="HowcanIcontribute-Submittingpatches">Submitting patches</h2><p>The easiest way to submit a patch is to create a new JIRA issue, attach the patch and tick the ASF license grant check box, tick the Patch Attached button on the issue then fire off an email to the <a shape="rect" href="mailing-lists.xml">Mailing Lists</a> or <a shape="rect" href="discussion-forums.xml">Discussion Forums</a>.</p><h2 id="HowcanIcontribute-Becomingacommmitter">Becoming a commmitter</h2><p>Once you've got involved as above, we may well invite you to be a committer. See <a shape="rect" href="becoming-a-committer.xml">Becoming a committer</a> for more details.</p><h2 id="HowcanIcontribute-Usingtheissuetracker">Using the issue tracker</h2><p>Before you can raise an issue in the issue tracker you need to register with it. This is quick & painless.</p><p>If you want to have a go at fixing an issue you need to be in the list of activemq-developers on the issue tracker. To join the group, please mail the <a shape="rect" class="external-link" href="mailto:dev@activemq.apache.org" rel="nofollow">dev@activemq.apache.org</a> mail list with the email address you used to register with the issue tracker and we'll add you to the group.</p><p>Why not dive in the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ">issue tracker</a>, and try tackle some of our outstanding issues?</p><h2 id="HowcanIcontribute-Becomingacommitter">Becoming a committer</h2><p>The first step is contributing to the project; if you want to take that a step forward and become a fellow committer on the project then see the <a shape="rect" href="becoming-a-committer.xml">Committer Guide</a></p></div>
+<structured-macro ac:macro-id="6092c4fa-bda2-400b-b3d2-ddfb8e0596b2" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Contributing"></page></link></parameter></structured-macro></div>
diff --git a/how-can-i-enable-detailed-logging.xml b/how-can-i-enable-detailed-logging.xml
index a376434..d938d0f 100644
--- a/how-can-i-enable-detailed-logging.xml
+++ b/how-can-i-enable-detailed-logging.xml
@@ -1,30 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="HowcanIenabledetailedlogging-HowcanIenabledetailedlogging">How can I enable detailed logging</h2>
+<div class="wiki-content maincontent"><h2>How can I enable detailed logging</h2>
-<p>We use <a shape="rect" class="unresolved" href="#">slf4j</a> which allows the underlying logging implementation to be statically bound at startup.<br clear="none">
+<p>We use <link><page ri:content-title="www.slf4j.org"></page><link-body>slf4j</link-body></link> which allows the underlying logging implementation to be statically bound at startup.<br clear="none">
By default we ship with log4j but feel free to make your own choice.</p>
-<p>If you've got log4j.jar on your classpath you can use a log4j.properties file to configure the logging levels. See the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/resources/log4j.properties">log4j.properties example</a> for the kind of thing you'll need.</p>
+<p>If you've got log4j.jar on your classpath you can use a log4j.properties file to configure the logging levels. See the <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/resources/log4j.properties">log4j.properties example</a> for the kind of thing you'll need.</p>
<p>e.g. adding the following to your log4j.properties will enable tracing of ActiveMQ code:</p>
<p>in 4.x</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ddc0a6c6-949f-4615-9978-88251129510c" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j.logger.org.apache.activemq=INFO
log4j.logger.org.apache.activemq.spring=WARN
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>in 3.x</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="47d1fb82-e709-4a6c-9d6a-bb2429076cbc" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j.logger.org.activemq=TRACE
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="HowcanIenabledetailedlogging-Gettinghelponlog4j">Getting help on log4j</h3>
+<h3>Getting help on log4j</h3>
-<p>If you are new to log4j please see the <a shape="rect" class="external-link" href="http://logging.apache.org/log4j/docs/manual.html">log4j manual</a></p></div>
+<p>If you are new to log4j please see the <a shape="rect" href="http://logging.apache.org/log4j/docs/manual.html">log4j manual</a></p></div>
diff --git a/how-can-i-get-a-list-of-the-topics-and-queues-in-a-broker.xml b/how-can-i-get-a-list-of-the-topics-and-queues-in-a-broker.xml
index 7f162b6..df0c927 100644
--- a/how-can-i-get-a-list-of-the-topics-and-queues-in-a-broker.xml
+++ b/how-can-i-get-a-list-of-the-topics-and-queues-in-a-broker.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="HowcanIgetalistofthetopicsandqueuesinabroker-HowcanIgetalistofthetopicsandqueuesinabroker?">How can I get a list of the topics and queues in a broker?</h2>
+<div class="wiki-content maincontent"><h2>How can I get a list of the topics and queues in a broker?</h2>
-<p>As of 5.1.0 you can use the new <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/DestinationSource.html">DestinationSource</a> on an ActiveMQConnection to access the available queues or topics or listen to queues/topics being created or deleted.</p>
+<p>As of 5.1.0 you can use the new <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/DestinationSource.html">DestinationSource</a> on an ActiveMQConnection to access the available queues or topics or listen to queues/topics being created or deleted.</p>
-<p>You can use <a shape="rect" href="jmx.xml">JMX</a> to browse the available topics and queues in a broker together with the connectors and connections along with their statistics etc.</p>
+<p>You can use <link><page ri:content-title="JMX"></page></link> to browse the available topics and queues in a broker together with the connectors and connections along with their statistics etc.</p>
-<p>Or you can access statistics <a shape="rect" href="how-can-i-see-what-destinations-are-used.xml">programmatically</a>.</p>
+<p>Or you can access statistics <link><page ri:content-title="How can I see what destinations are used"></page><link-body>programmatically</link-body></link>.</p>
-<p>Finally you could just use the <a shape="rect" href="web-console.xml">Web Console</a></p></div>
+<p>Finally you could just use the <link><page ri:content-title="Web Console"></page></link></p></div>
diff --git a/how-can-i-get-help.xml b/how-can-i-get-help.xml
index 396d244..4ea6bbc 100644
--- a/how-can-i-get-help.xml
+++ b/how-can-i-get-help.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="HowcanIgethelp-GettingHelp">Getting Help</h2><p>If you are experiencing problems using ActiveMQ then please report your problem to our <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ">Issue Tracker</a>. You may also find it useful to discuss your issues with the community on the <a shape="rect" href="discussion-forums.xml">Discussion Forums</a> or join one of our <a shape="rect" href="mailing-lists.xml">Mailing Lists</a>.</p><ul><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ">Issue Tracker</a></li><li><a shape="rect" href="discussion-forums.xml">Discussion Forums</a></li><li><a shape="rect" href="mailing-lists.xml">Mailing Lists</a></li><li><a shape="rect" href="faq.xml">FAQ</a></li></ul><h3 id="HowcanIgethelp-Howtogethelp">How to get help</h3><p>Before you report a problem you might want to read the <a shape="rect" href="faq.xml">FAQ</a>.<br clear="none"> Whenever you are reporting a problem please be sure to include as much information as possible; the more we know the more chance of a quicker resolution.</p><ul><li>Which <a shape="rect" class="external-link" href="http://activemq.apache.org/download.html">version</a> of ActiveMQ</li><li>What platform of Java (e.g., Java SE 6 with JRE/<a shape="rect" class="unresolved" href="#">JDK</a> 1.6.0 or J2SE 5 with JRE/<a shape="rect" class="unresolved" href="#">JDK</a> 1.5.0)</li><li>Any particular application/web server or container being used - if so what version?</li><li>Stack traces generally really help! If in doubt include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. It's very easy for us to skim-read past unnecessary parts of a stack trace.</li><li>Log output (e.g., <code>data/activemq.log</code>) can be useful too; sometimes <a shape="rect" href="how-do-i-change-the-logging.xml">enabling DEBUG logging</a> can help</li><li>Your code & configuration files are often useful</li></ul><h3 id="HowcanIgethelp-Howtogethelpfaster">How to get help faster</h3><p>We can help you much quicker if you try the following</p><ul><li>Provide us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug, can you create a test case to demonstrate the bug?</li><li><a shape="rect" href="contributing.xml">Submit a patch</a> fixing the bug! (We also buy you beer when we meet you if you submit bug fixes <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"> )</li><li>For memory leaks or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if it's huge) to the JIRA we can normally fix things much faster. e.g. you could run <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html" rel="nofollow">jmap</a>/<a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html" rel="nofollow">jhat</a>, JProfiler or YourKit on your code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that.</li></ul><h2 id="HowcanIgethelp-CommercialSupport">Commercial Support</h2><p>This is an open source project, so the amount of time we have available to help resolve your issue is often limited as all help is provided on a volunteer basis. If you want to get priority help, need to get up to speed quickly, require some training or mentoring, or need full 24 x 7 production support you should contact a commercial company specializing in ActiveMQ support such as...</p><ul><li><a shape="rect" class="external-link" href="https://apifocal.com" rel="nofollow">apifocal</a> is a Professional Services company. Headquartered near Washington, DC, USA, APIfocal provides consulting and training for leveraging the Apache Integration stack and commercial ESBs at large scale, adding automation and devops capabilities.</li><li><a shape="rect" class="external-link" href="http://mediadriver.com" rel="nofollow">Media Driver</a> provides consulting services and management tools for Apache ActiveMQ and the Apache Integration stack for both the commercial and public sector.  We bring a full suite of project delivery services including business and technical analysis, proof of concepts, architectural guidance, best practice integration, and project management.  Media Driver offers training classes for developers and administrators, as well as middleware management software.</li><li><a shape="rect" class="external-link" href="http://www.openlogic.com/" rel="nofollow">Rogue Wave / OpenLogic</a> <span style="line-height: 1.4285715;">has a dedicated team of OSS experts offering </span><span style="line-height: 1.4285715;">round-the-clock Production Support with competitive SLAs for </span><span style="line-height: 1.4285715;">troubleshooting ActiveMQ issues and outages. Rogue </span><span style="line-height: 1.4285715;">Wave offers a comprehensive week-long instructor-led training program for </span><span style="line-height: 1.4285715;">developers and admins. Rogue Wave OpenLogic also provides Architecture </span><span style="line-height: 1.4285715;">and Design Consulting, and a Developer Support contract to assist in the </span><span style="line-height: 1.4285715;">development of messaging applications.</span></li><li><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/amq/" rel="nofollow">Red Hat</a> offers JBoss A-MQ, a supported distribution of Apache ActiveMQ, that include Enterprise Developer and Production Support, and offer training and consultancy for enterprise deployments.</li><li><a shape="rect" class="external-link" href="http://www.savoirtech.com" rel="nofollow">Savoir Technologies, Inc</a> provides enterprise consulting, training and support for ActiveMQ and a host of other Apache service containers. Savoir can provide best practice mentoring for developing with ActiveMQ, as well as architectural/design reviews, troubleshooting and SOA infrastructure implementations. Savoir's staff includes some of the contributors of ActiveMQ who are on the ground consulting and are familiar with real world implementations and issues.</li><li><a shape="rect" class="external-link" href="http://www.ttmsolutions.com/" rel="nofollow">Total Transaction Management (TTM)</a> provides ActiveMQ consulting and support, as well as security and <a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor_AMon.php/" rel="nofollow">monitoring</a> add-on products and <a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php" rel="nofollow">reference guide</a> for ActiveMQ.</li><li><a shape="rect" class="external-link" href="http://tomitribe.com" rel="nofollow">Tomitribe</a> are experts in Tomcat and ActiveMQ integration, champions of Open Source and Java EE.  Tomitribe offers consulting, training and support for TomEE, Tomcat, ActiveMQ, CXF and more.</li><li><a shape="rect" class="external-link" href="http://www.tytoease.com/activemq" rel="nofollow">TytoEASE</a> offers support, consulting and training on enterprise ready open source projects including ActiveMQ.   Support offerings are at three levels with guaranteed SLA's. The company's consulting work is short term to help troubleshoot, fine-tune, do architectural reviews or help with initial design.  TytoEASE's focus is on the Enterprise with how customers integrate open source with their current technologies.</li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="f2f78dc4-e6c3-4cfe-bb52-7f9da4f178fd" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Support"></page></link></parameter></structured-macro></div>
diff --git a/how-can-i-get-the-source-code-from-subversion.xml b/how-can-i-get-the-source-code-from-subversion.xml
index 927a7cb..e9ea712 100644
--- a/how-can-i-get-the-source-code-from-subversion.xml
+++ b/how-can-i-get-the-source-code-from-subversion.xml
@@ -1,13 +1,3 @@
<div class="wiki-content maincontent">
-<h1 id="HowcanIgetthesourcecodefromsubversion-ActiveMQ5">ActiveMQ 5</h1><h2 id="HowcanIgetthesourcecodefromsubversion-WebBrowsingofthegitRepo">Web Browsing of the git Repo</h2><p>To browse via the web:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git">https://git-wip-us.apache.org/repos/asf?p=activemq.git</a></p>
-</div></div><h2 id="HowcanIgetthesourcecodefromsubversion-CheckingoutfromthegitRepo">Checking out from the git Repo</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq.git">https://git-wip-us.apache.org/repos/asf/activemq.git</a></p>
-</div></div><p>Only project developers can commit to the git repo via this method. SSH must be installed on your client machine. Enter your site password when prompted.</p><h2 id="HowcanIgetthesourcecodefromsubversion-Buildingthecode">Building the code</h2><p>To then build the code, see <a shape="rect" href="building.xml">Building</a>.</p><p> </p><h1 id="HowcanIgetthesourcecodefromsubversion-ActiveMQArtemis">ActiveMQ Artemis</h1><h2 id="HowcanIgetthesourcecodefromsubversion-WebBrowsingoftheASFgitRepo">Web Browsing of the ASF git Repo</h2><p>To browse via the web:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git">https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git</a></p>
-</div></div><h2 id="HowcanIgetthesourcecodefromsubversion-BrowsingtheGithubRepo">Browsing the Github Repo </h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">https://github.com/apache/activemq-artemis</a></p>
-</div></div><h2 id="HowcanIgetthesourcecodefromsubversion-CheckingoutfromtheGithubRepo">Checking out from the Github Repo</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">https://github.com/apache/activemq-artemis</a></p>
-</div></div><p><strong>Committers:</strong> Please follow the instructions for properly configuring the <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/SUMMARY.md" rel="nofollow">Instructions for Core Contributors/Hacking Guide</a></p><p><strong>Contributors:</strong> Please create a <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">pull request</a> to contribute changes to the source code. </p><h2 id="HowcanIgetthesourcecodefromsubversion-Buildingthecode.1">Building the code</h2><p>To then build the code, take a look at <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/building.md" rel="nofollow">Building the distribution</a></p></div>
+<structured-macro ac:macro-id="e2378983-65b6-4f96-968f-ccb50c499e06" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Source"></page></link></parameter></structured-macro></div>
diff --git a/how-can-i-make-activemq-faster.xml b/how-can-i-make-activemq-faster.xml
index 6a2e768..7602045 100644
--- a/how-can-i-make-activemq-faster.xml
+++ b/how-can-i-make-activemq-faster.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>See the <a shape="rect" href="performance.xml">Performance</a> page for information about the performance of ActiveMQ and it's tuning parameters.</p></div>
+<div class="wiki-content maincontent"><p>See the <link><page ri:content-title="Performance"></page></link> page for information about the performance of ActiveMQ and it's tuning parameters.</p></div>
diff --git a/how-can-i-monitor-activemq.xml b/how-can-i-monitor-activemq.xml
index b455827..c7f219a 100644
--- a/how-can-i-monitor-activemq.xml
+++ b/how-can-i-monitor-activemq.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="HowcanImonitorActiveMQ-HowcanImonitorActiveMQ">How can I monitor ActiveMQ</h2><p>Starting with ActiveMQ 5.8.0 <a shape="rect" class="external-link" href="http://www.jolokia.org/" rel="nofollow">Jolokia</a> is bundled which provides a RESTful interface to ActiveMQ's JMX capabilities. An open source third party tool that connects via Jolokia is <a shape="rect" class="external-link" href="http://hawt.io/" rel="nofollow">hawt.io</a>, an HTML-5 web console with an ActiveMQ plugin that is at least worth being familiar with as <span style="line-height: 1.4285715;">ActiveMQ and hawt.io share developers.</span></p><p>In ActiveMQ 4.x you can monitor the broker to see what destinations are being used, their activity along with connections and subscriptions using the following tools</p><ul><li><a shape="rect" href="jmx.xml">JMX</a> and a JMX console such as <a shape="rect" class="external-link" href="http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html" rel="nofollow">jConsole</a></li><li>The <a shape="rect" href="web-console.xml">Web Console</a></li><li>the <a shape="rect" href="advisory-message.xml">Advisory Message</a> feature (using JMS messages to monitor the system)</li><li>The <a shape="rect" href="command-agent.xml">Command Agent</a>; ActiveMQ.Agent topic that you query for status</li><li>The <a shape="rect" href="visualisation.xml">Visualisation</a> plug-in</li><li>The <a shape="rect" class="external-link" href="http://activemq.apache.org/statisticsplugin.html">Statistics</a> plug-in (from 5.3)</li></ul><h3 id="HowcanImonitorActiveMQ-ThirdPartyTools">Third Party Tools</h3><ul><li><a shape="rect" class="external-link" href="https://github.com/jmxtrans/jmxtrans" rel="nofollow">jmxtrans</a> which can be used to continuously query ActiveMQ via JMX and write to a chosen output. For instance, write to a graphite database file which can then be used to graph trends over time and be queried by Nagios to alarm should your thresholds be exceeded.</li><li><a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor_AMon.php" rel="nofollow">ActiveMQ Monitor (AMon)</a></li><li><a shape="rect" class="external-link" href="http://sourceforge.net/projects/activemqbrowser/" rel="nofollow">Apache ActiveMQBrowser</a></li><li><a shape="rect" class="external-link" href="http://www.hermesjms.com/confluence/display/HJMS/Home" rel="nofollow">HermesJMS</a></li><li><a shape="rect" class="external-link" href="http://www.soapui.org/JMS/working-with-jms-messages.html" rel="nofollow">HermesJMS/soapUI</a></li><li><a shape="rect" class="external-link" href="http://www.hyperic.com/products/open-source-systems-monitoring" rel="nofollow">Hyperic HQ</a> and <a shape="rect" class="external-link" href="http://www.hyperic.com/products/enterprise-systems-monitoring" rel="nofollow">Hyperic HQ Enterprise</a></li><li><a shape="rect" class="external-link" href="http://fusesource.com/products/fuse-hq/" rel="nofollow">FuseHQ</a> (based on Hyperic HQ Enterprise)</li><li><a shape="rect" class="external-link" href="http://www.itko.com/products/jms.jsp" rel="nofollow">iTKO LISA Test</a></li><li><a shape="rect" class="external-link" href="https://cwiki.apache.org/GMOxDOC11/geronimo-administration-console.html#GeronimoAdministrationConsole-JMSServer">Geronimo Administration Console</a> (JMS Resources)</li><li><a shape="rect" class="external-link" href="https://mediadriver.com/software/" rel="nofollow">Media Driver Integrated Console</a> can manage and monitor ActiveMQ, IBM MQ and Tibco EMS</li></ul><h3 id="HowcanImonitorActiveMQ-SeeAlso">See Also</h3><ul><li><a shape="rect" href="how-can-i-monitor-the-connection-with-the-broker.xml">How can I monitor the connection with the broker</a></li></ul></div>
+<div class="wiki-content maincontent"><h2>How can I monitor ActiveMQ</h2><p>Starting with ActiveMQ 5.8.0 <a shape="rect" href="http://www.jolokia.org/">Jolokia</a> is bundled which provides a RESTful interface to ActiveMQ's JMX capabilities. An open source third party tool that connects via Jolokia is <a shape="rect" href="http://hawt.io/">hawt.io</a>, an HTML-5 web console with an ActiveMQ plugin that is at least worth being familiar with as <span style="line-height: 1.4285715;">ActiveMQ and hawt.io share developers.</span></p><p>In ActiveMQ 4.x you can monitor the broker to see what destinations are being used, their activity along with connections and subscriptions using the following tools</p><ul><li><link><page ri:content-title="JMX"></page></link> and a JMX console such as <a shape="rect" href="http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html">jConsole</a></li><li>The <link><page ri:content-title="Web Console"></page></link></li><li>the <link><page ri:content-title="Advisory Message"></page></link> feature (using JMS messages to monitor the system)</li><li>The <link><page ri:content-title="Command Agent"></page></link>; ActiveMQ.Agent topic that you query for status</li><li>The <link><page ri:content-title="Visualisation"></page></link> plug-in</li><li>The <a shape="rect" href="http://activemq.apache.org/statisticsplugin.html">Statistics</a> plug-in (from 5.3)</li></ul><h3>Third Party Tools</h3><ul><li><a shape="rect" href="https://github.com/jmxtrans/jmxtrans">jmxtrans</a> which can be used to continuously query ActiveMQ via JMX and write to a chosen output. For instance, write to a graphite database file which can then be used to graph trends over time and be queried by Nagios to alarm should your thresholds be exceeded.</li><li><a shape="rect" href="http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor_AMon.php">ActiveMQ Monitor (AMon)</a></li><li><a shape="rect" href="http://sourceforge.net/projects/activemqbrowser/">Apache ActiveMQBrowser</a></li><li><a shape="rect" href="http://www.hermesjms.com/confluence/display/HJMS/Home">HermesJMS</a></li><li><a shape="rect" href="http://www.soapui.org/JMS/working-with-jms-messages.html">HermesJMS/soapUI</a></li><li><a shape="rect" href="http://www.hyperic.com/products/open-source-systems-monitoring">Hyperic HQ</a> and <a shape="rect" href="http://www.hyperic.com/products/enterprise-systems-monitoring">Hyperic HQ Enterprise</a></li><li><a shape="rect" href="http://fusesource.com/products/fuse-hq/">FuseHQ</a> (based on Hyperic HQ Enterprise)</li><li><a shape="rect" href="http://www.itko.com/products/jms.jsp">iTKO LISA Test</a></li><li><a shape="rect" href="https://cwiki.apache.org/GMOxDOC11/geronimo-administration-console.html#GeronimoAdministrationConsole-JMSServer">Geronimo Administration Console</a> (JMS Resources)</li><li><a shape="rect" href="https://mediadriver.com/software/">Media Driver Integrated Console</a> can manage and monitor ActiveMQ, IBM MQ and Tibco EMS</li></ul><h3>See Also</h3><ul><li><link><page ri:content-title="How can I monitor the connection with the broker"></page></link></li></ul></div>
diff --git a/how-can-i-monitor-the-connection-with-the-broker.xml b/how-can-i-monitor-the-connection-with-the-broker.xml
index 3a12fda..58a8080 100644
--- a/how-can-i-monitor-the-connection-with-the-broker.xml
+++ b/how-can-i-monitor-the-connection-with-the-broker.xml
@@ -1,11 +1,12 @@
-<div class="wiki-content maincontent"><h2 id="HowcanImonitortheconnectionwiththebroker-HowcanImonitortheconnectionwiththebroker">How can I monitor the connection with the broker</h2>
+<div class="wiki-content maincontent"><h2>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 shape="rect" class="external-link" 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 shape="rect" 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>This method takes a <a shape="rect" class="external-link" 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 shape="rect" href="failover-transport-reference.xml">Failover Transport</a> yet still know the status of the connection.</p>
+<p>This method takes a <a shape="rect" 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 <link><page ri:content-title="Failover Transport Reference"></page><link-body>Failover Transport</link-body></link> yet still know the status of the connection.</p>
-<h3 id="HowcanImonitortheconnectionwiththebroker-SeeAlso">See Also</h3>
+<h3>See Also</h3>
-<ul><li><a shape="rect" href="how-can-i-monitor-activemq.xml">How can I monitor ActiveMQ</a></li></ul></div>
+<ul><li><link><page ri:content-title="How can I monitor ActiveMQ"></page></link></li></ul>
+</div>
diff --git a/how-can-i-see-what-destinations-are-used.xml b/how-can-i-see-what-destinations-are-used.xml
index f54208e..e069008 100644
--- a/how-can-i-see-what-destinations-are-used.xml
+++ b/how-can-i-see-what-destinations-are-used.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The easiest way is to use <a shape="rect" href="jmx.xml">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 shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.8.0/apidocs/org/apache/activemq/broker/region/Region.html#getDestinations%28org.apache.activemq.command.ActiveMQDestination%29">getDestinations()</a>.</p><p>You can also get a Map of all the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.8.0/apidocs/org/apache/activemq/broker/region/Destination.html">Destination</a> objects indexed by ActiveMQDestination via <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.8.0/apidocs/org/apache/activemq/broker/region/Region.html#getDestinationMap%28%29">getDestinationMap()</a>. This allows you to look at the individual destination details such as the queue depths and so forth</p></div>
+<div class="wiki-content maincontent"><p>The easiest way is to use <link><page ri:content-title="JMX"></page></link> 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 shape="rect" href="http://activemq.apache.org/maven/5.8.0/apidocs/org/apache/activemq/broker/region/Region.html#getDestinations%28org.apache.activemq.command.ActiveMQDestination%29">getDestinations()</a>.</p><p>You can also get a Map of all the <a shape="rect" href="http://activemq.apache.org/maven/5.8.0/apidocs/org/apache/activemq/broker/region/Destination.html">Destination</a> objects indexed by ActiveMQDestination via <a shape="rect" href="http://activemq.apache.org/maven/5.8.0/apidocs/org/apache/activemq/broker/region/Region.html#getDestinationMap%28%29">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/how-can-i-support-auto-reconnection.xml b/how-can-i-support-auto-reconnection.xml
index 0ca8b41..1fcdcb7 100644
--- a/how-can-i-support-auto-reconnection.xml
+++ b/how-can-i-support-auto-reconnection.xml
@@ -1,19 +1,17 @@
-<div class="wiki-content maincontent"><h2 id="HowcanIsupportautoreconnection-HowcanIsupportautoreconnection?">How can I support auto reconnection?</h2>
+<div class="wiki-content maincontent"><h2>How can I support auto reconnection?</h2>
<p>Networks are unreliable and sockets do get dropped from time to time (it could be a network glitch, dodgy router, firewall, or someone could even just restart a broker).</p>
<p>You often want a JMS client to automatically handle the fact that the connection to the broker was lost such that the JMS client either reconnnects to the same broker when it becomes available, or reconnects to another broker in the cluster.</p>
-<p>Its easy to perform auto-reconnection. In Apache ActiveMQ using the <a shape="rect" href="failover-transport-reference.xml">failover transport</a> in which the JMS client (connection) will automatically reconnect to the broker if there is a socket exception. </p>
+<p>Its easy to perform auto-reconnection. In Apache ActiveMQ using the <link><page ri:content-title="Failover Transport Reference"></page><link-body>failover transport</link-body></link> in which the JMS client (connection) will automatically reconnect to the broker if there is a socket exception. </p>
<p>Just use the following connection URI (setting the brokerURL in the ActiveMQConnectionFactory)</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b7cbcc04-7a5f-4161-8a80-f101a8c31ead" ac:name="code" ac:schema-version="1"><plain-text-body>
failover:tcp://host:port
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>You can use a list of URIs to specify which machines to connect to and use discovery to find the brokers to connect to. More details on this see <a shape="rect" href="configuring-transports.xml">Configuring Transports</a></p></div>
+<p>You can use a list of URIs to specify which machines to connect to and use discovery to find the brokers to connect to. More details on this see <link><page ri:content-title="Configuring Transports"></page></link></p></div>
diff --git a/how-can-i-support-priority-queues.xml b/how-can-i-support-priority-queues.xml
index 71a8dd3..b0c5d41 100644
--- a/how-can-i-support-priority-queues.xml
+++ b/how-can-i-support-priority-queues.xml
@@ -1,59 +1,51 @@
-<div class="wiki-content maincontent"><h2 id="HowcanIsupportpriorityqueues-HowcanIsupportpriorityqueues?">How can I support priority queues?</h2>
+<div class="wiki-content maincontent"><h2>How can I support priority queues?</h2>
-<h3 id="HowcanIsupportpriorityqueues-UseMessagePriority">Use Message Priority</h3>
+<h3>Use Message Priority</h3>
<p>A common requirement is to support priority consumption; so high priority messages are consumed before low priority.</p>
-<p>In version 5.4 priority queues are supported. Both the message cursors and the message stores (KahaDB and JDBC) support message priority. The support is disabled by default so it needs to be be enabled using <a shape="rect" href="per-destination-policies.xml">per destination policies</a> through xml configuration, in the example below, 'prioritizedMessages' is enabled for all queues. </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>In version 5.4 priority queues are supported. Both the message cursors and the message stores (KahaDB and JDBC) support message priority. The support is disabled by default so it needs to be be enabled using <link><page ri:content-title="per destination policies"></page></link> through xml configuration, in the example below, 'prioritizedMessages' is enabled for all queues. </p>
+<structured-macro ac:macro-id="d0404155-3918-434f-b576-8f72b792b667" ac:name="code" ac:schema-version="1"><plain-text-body>
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue=">" prioritizedMessages="true"/>
+ <policyEntry queue=">" prioritizedMessages="true"/>
...
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>The full range of priority values (0-9) are supported by the <a shape="rect" href="jdbc-support.xml">JDBC</a> message store. For <a shape="rect" href="kahadb.xml">KahaDB</a> three priority categories are supported, Low (< 4), Default (= 4) and High (> 4).</p>
+<p>The full range of priority values (0-9) are supported by the <link><page ri:content-title="jdbc support"></page><link-body>JDBC</link-body></link> message store. For <link><page ri:content-title="KahaDB"></page></link> three priority categories are supported, Low (< 4), Default (= 4) and High (> 4).</p>
<p>Since the message cursors (and client side) implement strict ordering of priorities, it's possible to observe strict priority ordering if message dispatching can happen from the cache and not have to hit the disk (i.e., your consumers are fast enough to keep up with producers), or if you're using non-persistent messages that never have to flush to disk (using the FilePendingMessageCursor). However, once you hit a situation where consumers are slow, or producers are just significantly faster, you'll observe that the cache will fill up (possibly with lower priority messages) while higher priority messages get stuck on disk and not available until they're paged in. In this case, you can make a decision to tradeoff optimized message dispatching for priority enforcement. You can disable the cache, message expiration check, and lower you consumer prefetch to 1 to ensure getting the high priority messages from the store ahead of lower priority messages Note, this sort of tradeoff can have significant performance implications, so you must test your scenarios thoroughly. :</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="11e4935d-0104-4709-a871-c3467bedb529" ac:name="code" ac:schema-version="1"><plain-text-body>
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue=">" prioritizedMessages="true" useCache="false" expireMessagesPeriod="0" queuePrefetch="1" />
+ <policyEntry queue=">" prioritizedMessages="true" useCache="false" expireMessagesPeriod="0" queuePrefetch="1" />
...
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="HowcanIsupportpriorityqueues-Alternativestrategies">Alternative strategies</h3>
-<h4 id="HowcanIsupportpriorityqueues-UseSelectors">Use Selectors</h4>
+<h3>Alternative strategies</h3>
+<h4>Use Selectors</h4>
<p>You can have say 100 consumers using a selector to find the high priority stuff</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ce5db972-0df5-47c1-92be-39bf60b456f7" ac:name="code" ac:schema-version="1"><plain-text-body>
JMSPriority > 6
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>then have 50 consumers doing average or above</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0fc1e06f-98b9-4e33-8552-2e3bd2cfa13e" ac:name="code" ac:schema-version="1"><plain-text-body>
JMSPriority >= 4
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Then say 10 consumers consuming all messages (so all priorities). Then this way you'll have a pool of threads always processing high priority messages - giving you very efficient priority based dispatching of messages without ActiveMQ having to batch up messages and reorder them before dispatching them.</p>
-<h4 id="HowcanIsupportpriorityqueues-UseResequencer">Use Resequencer</h4>
+<h4>Use Resequencer</h4>
<p>You can reorder messages on some input queue A and send them to queue B in sorted order to avoid having to change your clients. This avoids the need to use selectors in your application as shown above.</p>
-<p>To do this use the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/resequencer.html">Resequencer</a> from the <a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a></p></div>
+<p>To do this use the <a shape="rect" href="http://activemq.apache.org/camel/resequencer.html">Resequencer</a> from the <link><page ri:content-title="Enterprise Integration Patterns"></page></link></p></div>
diff --git a/how-can-i-use-different-network-protocols.xml b/how-can-i-use-different-network-protocols.xml
index cb25761..ef8bed5 100644
--- a/how-can-i-use-different-network-protocols.xml
+++ b/how-can-i-use-different-network-protocols.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>For easy configuration, ActiveMQ supports a configurable URL to denote the connection mechanism to other clients. There is an example of how to do this along with a description of the available protocols in the <a shape="rect" href="uri-protocols.xml">Protocols overview</a></p></div>
+<p>For easy configuration, ActiveMQ supports a configurable URL to denote the connection mechanism to other clients. There is an example of how to do this along with a description of the available protocols in the <link><page ri:content-title="URI Protocols"></page><link-body>Protocols overview</link-body></link></p></div>
diff --git a/how-do-distributed-queues-work.xml b/how-do-distributed-queues-work.xml
index 08ed62a..9949e03 100644
--- a/how-do-distributed-queues-work.xml
+++ b/how-do-distributed-queues-work.xml
@@ -1,32 +1,32 @@
-<div class="wiki-content maincontent"><p>There are various <a shape="rect" href="topologies.xml">Topologies</a> that you can employ with ActiveMQ, where clients are connected to message brokers in various ways like</p>
+<div class="wiki-content maincontent"><p>There are various <link><page ri:content-title="Topologies"></page></link> that you can employ with ActiveMQ, where clients are connected to message brokers in various ways like</p>
<ul><li>peer based</li><li>client server</li><li>hub and spoke</li></ul>
-<p>Each client communicates with a broker using some kind of <a shape="rect" href="cross-language-clients.xml">client library and network protocol</a>. </p>
+<p>Each client communicates with a broker using some kind of <link><page ri:content-title="Cross Language Clients"></page><link-body>client library and network protocol</link-body></link>. </p>
<p>To create distributed queues or topics we need to have the message brokers communicate with each other. There are two different types of broker to broker communication...</p>
-<h2 id="Howdodistributedqueueswork-Master/SlaveforHighAvailability">Master/Slave for High Availability</h2>
+<h2>Master/Slave for High Availability</h2>
-<p>A <a shape="rect" href="masterslave.xml">Master/Slave Cluster</a> is used for <a shape="rect" href="ha.xml">HA</a>. Basically it means that all messages are replicated across each broker in the master/slave cluster. If the Master goes down, the clients can automatically failover to a slave which will have all the messages already, so each message is highly available. The Slave(s) provide a hot standby broker which will always be in sync ready to take over if the master goes away due to hardware failure etc.</p>
+<p>A <link><page ri:content-title="MasterSlave"></page><link-body>Master/Slave Cluster</link-body></link> is used for <link><page ri:content-title="HA"></page></link>. Basically it means that all messages are replicated across each broker in the master/slave cluster. If the Master goes down, the clients can automatically failover to a slave which will have all the messages already, so each message is highly available. The Slave(s) provide a hot standby broker which will always be in sync ready to take over if the master goes away due to hardware failure etc.</p>
<p>Master/Slave works by having some form of replication; each message is owned by every broker in the logical cluster. A master/slave cluster then acts as one logical message broker which could then be connected via store and forward to other brokers (as we'll see in the next section).</p>
-<h3 id="Howdodistributedqueueswork-DistributedQueuesandTopics">Distributed Queues and Topics</h3>
+<h3>Distributed Queues and Topics</h3>
<p>In Master/Slave, queues and topics are all replicated between each broker in the cluster (so often to a master and maybe a single slave). So each broker in the cluster has exactly the same messages available at any time so if a master fails, clients failover to a slave and you don't loose a message.</p>
-<h2 id="Howdodistributedqueueswork-Storeandforwardnetworksofbrokers">Store and forward networks of brokers</h2>
+<h2>Store and forward networks of brokers</h2>
-<p>A <a shape="rect" href="networks-of-brokers.xml">Store and Forward Network of Brokers</a> means the messages travel from broker to broker until they reach a consumer; with each message being owned by a single broker at any point in time. When a JMS producer sends a message to a JMS consumer, it may travel through several brokers to reach its final destination. ActiveMQ uses <a shape="rect" href="consumer-priority.xml">Consumer Priority</a> so that local JMS consumers are always higher priority than remote brokers in a store and forward network.</p>
+<p>A <link><page ri:content-title="Networks of Brokers"></page><link-body>Store and Forward Network of Brokers</link-body></link> means the messages travel from broker to broker until they reach a consumer; with each message being owned by a single broker at any point in time. When a JMS producer sends a message to a JMS consumer, it may travel through several brokers to reach its final destination. ActiveMQ uses <link><page ri:content-title="Consumer Priority"></page></link> so that local JMS consumers are always higher priority than remote brokers in a store and forward network.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Note though that a store and forward network is not a solution for message <a shape="rect" href="ha.xml">HA</a>; if a broker fails in a Store and Forward network, the messages owned by that broker remain inside the broker's persistent store until the broker comes back online. If you need <a shape="rect" href="ha.xml">HA</a> of messages then you need to use Master/Slave described above.</p></div></div>
+<structured-macro ac:macro-id="170ca14d-b8a6-4564-be68-bd68a0f854bc" ac:name="info" ac:schema-version="1"><parameter ac:name="">Store and Forward is not HA</parameter><rich-text-body>
+<p>Note though that a store and forward network is not a solution for message <link><page ri:content-title="HA"></page></link>; if a broker fails in a Store and Forward network, the messages owned by that broker remain inside the broker's persistent store until the broker comes back online. If you need <link><page ri:content-title="HA"></page></link> of messages then you need to use Master/Slave described above.</p></rich-text-body></structured-macro>
<p>Store and forward is often used in large networks where producers are on one LAN and consumers are on another LAN and you wish to use a broker on each LAN as a kind of network concentrator to minimise chattiness over the WAN between them (and to minimise the number of connections required across the WAN too). Similar uses of store and forward can be found when using firewalls or SSL across certain networks etc. One other use case for store and forward networks is if your OS does not support many sockets (and you can't reconfigure that) you could use a store and forward network to connect massive numbers of clients together in one logical network.</p>
-<h3 id="Howdodistributedqueueswork-DistributedQueuesinStore/Forward">Distributed Queues in Store/Forward</h3>
+<h3>Distributed Queues in Store/Forward</h3>
<p>When we publish a message on a queue, it is stored in the persistent store of the broker that the publisher is communicating. Then if that broker is configured to store/foward to other brokers and clients, the broker will send it to <em>one</em> of these clients (which could be a node or a broker depending on the dispatch algorithm). This dispatch algorithm continues until the message is finally dispatched and consumed by a client.</p>
<p>At any point in time the message will only exist in one broker's store until its consumed. Note that messages are only distributed onto other brokers if there is a consumer on those brokers.</p>
@@ -34,10 +34,11 @@
<p>e.g. if we had broker A, B, C and a publisher on a queue on A. If we have consumers on the queue on A and B then messages for the queue will be spread across both brokers A and B; some messages going to B, some being consumed on A, none going to C. If a consumer on the queue starts <br clear="none">
on C, then messages will flow there too. If the consumer stops then no more messages will be dispatched to C.</p>
-<h2 id="Howdodistributedqueueswork-DistributedTopicsinStore/Forward">Distributed Topics in Store/Forward</h2>
+<h2>Distributed Topics in Store/Forward</h2>
<p>For topics the above algorithm is followed except, every interested client receives a copy of the message - plus ActiveMQ will check for loops (to avoid a message flowing infinitely around a ring of brokers).</p>
-<h3 id="Howdodistributedqueueswork-SeeAlso">See Also</h3>
+<h3>See Also</h3>
-<ul><li><a shape="rect" href="how-do-i-configure-distributed-queues-or-topics.xml">How do I configure distributed queues or topics</a></li><li><a shape="rect" href="masterslave.xml">MasterSlave</a></li><li><a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a></li></ul></div>
+<ul><li><link><page ri:content-title="How do I configure distributed queues or topics"></page></link></li><li><link><page ri:content-title="MasterSlave"></page></link></li><li><link><page ri:content-title="Networks of Brokers"></page></link></li></ul>
+</div>
diff --git a/how-do-durable-queues-and-topics-work.xml b/how-do-durable-queues-and-topics-work.xml
index ce50c4d..c4dacaa 100644
--- a/how-do-durable-queues-and-topics-work.xml
+++ b/how-do-durable-queues-and-topics-work.xml
@@ -10,5 +10,5 @@
<p>So for durable topic subscription, the JMS provider needs to be able to identify S when it shuts down and later on in the future reconnects, so it can know what messages to send to it while it was not running. JMS specification dictates that the identification of S is done by a combination of the clientID and the durable subscriber name. This is so that the JMS connection S uses can have many different durable subscriptions on different topics or on the same topic with different selectors - yet the JMS provider can know which message for which subscription to keep around for it.</p>
-<p>So setting the clientID on a JMS connection is vital (along with using a sensible durable consumer name) for durable topic subscription. Its not an issue for other <a shape="rect" href="qos.xml">QoS</a></p></div>
+<p>So setting the clientID on a JMS connection is vital (along with using a sensible durable consumer name) for durable topic subscription. Its not an issue for other <link><page ri:content-title="QoS"></page></link></p></div>
diff --git a/how-do-i-access-activemq-from-c.xml b/how-do-i-access-activemq-from-c.xml
index a1db78a..15d8c1e 100644
--- a/how-do-i-access-activemq-from-c.xml
+++ b/how-do-i-access-activemq-from-c.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent">
-<p>See the <a shape="rect" href="c-integration.xml">C Integration</a> page for the available options.</p></div>
+<p>See the <link><page ri:content-title="C Integration"></page></link> page for the available options.</p></div>
diff --git a/how-do-i-access-activemq-from-csharp-or-dotnet.xml b/how-do-i-access-activemq-from-csharp-or-dotnet.xml
index c755e54..7a3b862 100644
--- a/how-do-i-access-activemq-from-csharp-or-dotnet.xml
+++ b/how-do-i-access-activemq-from-csharp-or-dotnet.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent">
-<div class="error"><span class="error">Unable to render {include}</span> The included page could not be found.</div></div>
+<structured-macro ac:macro-id="c77675b8-b961-4f54-b311-d7206e0d6d0d" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="dot Net"></page></link></parameter></structured-macro></div>
diff --git a/how-do-i-access-activemq-from-ruby-perl-python-php.xml b/how-do-i-access-activemq-from-ruby-perl-python-php.xml
index 75ad58e..e899d23 100644
--- a/how-do-i-access-activemq-from-ruby-perl-python-php.xml
+++ b/how-do-i-access-activemq-from-ruby-perl-python-php.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent">
-<p>Use <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> which is a simple to implement client protocol for working with ActiveMQ and other messaging systems.</p></div>
+<p>Use <a shape="rect" href="http://stomp.codehaus.org/">Stomp</a> which is a simple to implement client protocol for working with ActiveMQ and other messaging systems.</p></div>
diff --git a/how-do-i-add-my-own-plugins.xml b/how-do-i-add-my-own-plugins.xml
index 90bd8d4..bf12f95 100644
--- a/how-do-i-add-my-own-plugins.xml
+++ b/how-do-i-add-my-own-plugins.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>See <a shape="rect" href="developing-plugins.xml">Developing Plugins</a> for how to add your own functionality into Apache ActiveMQ</p></div>
+<div class="wiki-content maincontent"><p>See <link><page ri:content-title="Developing Plugins"></page></link> for how to add your own functionality into Apache ActiveMQ</p></div>
diff --git a/how-do-i-avoid-maven-downloading-latest-jars.xml b/how-do-i-avoid-maven-downloading-latest-jars.xml
index 106876f..8af0743 100644
--- a/how-do-i-avoid-maven-downloading-latest-jars.xml
+++ b/how-do-i-avoid-maven-downloading-latest-jars.xml
@@ -1,15 +1,11 @@
<div class="wiki-content maincontent">
<p>You can use the -o switch (for offline mode) to avoid maven auto-downloading new snapshot jars (e.g. the Geronimo jars at the time of writing).</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6dd5d712-dd1e-4985-b705-e469d0c5769b" ac:name="code" ac:schema-version="1"><plain-text-body>
maven -o
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>or to run a server go to the \assembly module and run</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="306141b6-06de-44f5-8fd1-ecc0dab0ab1c" ac:name="code" ac:schema-version="1"><plain-text-body>
maven -o server
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-bridge-different-jms-providers.xml b/how-do-i-bridge-different-jms-providers.xml
index 23b7ecf..4947f45 100644
--- a/how-do-i-bridge-different-jms-providers.xml
+++ b/how-do-i-bridge-different-jms-providers.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>To bridge from ActiveMQ to another JMS provider use the <a shape="rect" href="jms-to-jms-bridge.xml">JMS bridge</a>. </p>
+<div class="wiki-content maincontent"><p>To bridge from ActiveMQ to another JMS provider use the <link><page ri:content-title="jms to jms bridge"></page><link-body>JMS bridge</link-body></link>. </p>
-<p>To bridge to another kind of transport completely, use <a shape="rect" class="external-link" href="http://camel.apache.org">Camel</a> or <a shape="rect" class="external-link" href="http://servicemix.apache.org">ServiceMix</a></p></div>
+<p>To bridge to another kind of transport completely, use <a shape="rect" href="http://camel.apache.org">Camel</a> or <a shape="rect" href="http://servicemix.apache.org">ServiceMix</a></p></div>
diff --git a/how-do-i-build-but-disable-the-unit-tests.xml b/how-do-i-build-but-disable-the-unit-tests.xml
index 74346b3..ce1e503 100644
--- a/how-do-i-build-but-disable-the-unit-tests.xml
+++ b/how-do-i-build-but-disable-the-unit-tests.xml
@@ -1,12 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIbuildbutdisabletheunittests-HowdoIbuildbutdisabletheunittests">How do I build but disable the unit tests</h2>
+<div class="wiki-content maincontent"><h2>How do I build but disable the unit tests</h2>
-<p>The test cases in ActiveMQ can take a very long time to run! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>The test cases in ActiveMQ can take a very long time to run! <emoticon ac:name="smile"></emoticon></p>
<p>To disable this you can try the following</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a89a4ffe-28f9-4290-86b1-bbb13431bbc4" ac:name="code" ac:schema-version="1"><plain-text-body>
mvn install -Dmaven.test.skip=true
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-change-dispatch-policy.xml b/how-do-i-change-dispatch-policy.xml
index e14c15a..d0de7e0 100644
--- a/how-do-i-change-dispatch-policy.xml
+++ b/how-do-i-change-dispatch-policy.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><p>This is much simpler and more powerful in ActiveMQ 4.0 - you can configure different <a shape="rect" href="dispatch-policies.xml">Dispatch Policies</a> directly. </p>
+<div class="wiki-content maincontent"><p>This is much simpler and more powerful in ActiveMQ 4.0 - you can configure different <link><page ri:content-title="Dispatch Policies"></page></link> directly. </p>
-<p>For now in ActiveMQ 3.x we have a <a shape="rect" href="what-is-the-prefetch-limit-for.xml">PrefetchPolicy configuration</a>. This allows a certain number of messages to be dispatched to a consumer before they are acknowledged. This feature is to achieve high performance; the higher the value the less likely it is that a client has to wait for messages to arrive before processing the message and so the higher the throughput.</p>
+<p>For now in ActiveMQ 3.x we have a <link><page ri:content-title="What is the Prefetch Limit For?"></page><link-body>PrefetchPolicy configuration</link-body></link>. This allows a certain number of messages to be dispatched to a consumer before they are acknowledged. This feature is to achieve high performance; the higher the value the less likely it is that a client has to wait for messages to arrive before processing the message and so the higher the throughput.</p>
<p>e.g. under heavy load of a busy system you probably want to dispatch 1000 or so messages to a consumer, so as soon as its ready to receive a message, there are a bunch of them in memory waiting to be used - rather than having a slow request-response RPC each time.</p>
@@ -8,16 +8,15 @@
<p>In ActiveMQ 3.x or later a work around for this issue is to reconfigure the PrefetchPolicy on the ConnectionFactory/Connection so that the broker only prefetches a single message per consumer; though this will greatly reduce the performance and throughput of the system.</p>
-<h3 id="HowdoIchangedispatchpolicy-ConfiguringthedispatchpolicyinActiveMQ4.x">Configuring the dispatch policy in ActiveMQ 4.x</h3>
+<h3>Configuring the dispatch policy in ActiveMQ 4.x</h3>
<p>In AMQ 4.x, the dispatch policy can now be configured on the xml configuration file (ie. activemq.xml)<br clear="none">
ie.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b215a33e-7bd9-4d85-83b6-523f38286caa" ac:name="code" ac:schema-version="1"><plain-text-body>
<destinationPolicy>
<policyMap><policyEntries>
- <policyEntry topic="COMMAND.>">
+ <policyEntry topic="COMMAND.>">
<dispatchPolicy>
<strictOrderDispatchPolicy />
</dispatchPolicy>
@@ -27,6 +26,5 @@
</policyEntry>
</policyEntries></policyMap>
</destinationPolicy>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-change-the-logging.xml b/how-do-i-change-the-logging.xml
index 7fa1bd1..3397942 100644
--- a/how-do-i-change-the-logging.xml
+++ b/how-do-i-change-the-logging.xml
@@ -1,37 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIchangethelogging-HowdoIchangethelogging">How do I change the logging</h2>
+<div class="wiki-content maincontent"><h2>How do I change the logging</h2>
-<p>We use <a shape="rect" class="unresolved" href="#">slf4j</a> to log information in the broker client and the broker itself so you can fully configure which logging levels are used and whether to log to files or the console etc. For more information see the <a shape="rect" class="external-link" href="http://logging.apache.org/log4j/docs/manual.html">log4j manual.</a>.</p>
+<p>We use <link><page ri:content-title="www.slf4j.org"></page><link-body>slf4j</link-body></link> to log information in the broker client and the broker itself so you can fully configure which logging levels are used and whether to log to files or the console etc. For more information see the <a shape="rect" href="http://logging.apache.org/log4j/docs/manual.html">log4j manual.</a>.</p>
<p>You can disable the ActiveMQ logging by editing the <strong>conf/log4j.properties</strong> file to disable all INFO level logging for activemq by adding this line</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="7662763d-89e4-4530-a809-80b4837b9ac5" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j.logger.org.apache.activemq=WARN
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>or to disable stdout logging all together change this line</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="329e6a3c-02be-4370-a6d9-ae07172450c1" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j.rootLogger=INFO, stdout, out
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>to</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5bfdd37d-318b-4c45-87c0-76fc34ea3276" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j.rootLogger=INFO, out
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="HowdoIchangethelogging-HowDoIChangetheLoggingatRuntime?">How Do I Change the Logging at Runtime? </h2>
+<h2>How Do I Change the Logging at Runtime? </h2>
<p>The default logging level in ActiveMQ is INFO. This can be seen by starting up the default ActiveMQ binary in a terminal. In doing so, you will see the output shown below: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f615105d-e205-4750-b028-693bb3957169" ac:name="code" ac:schema-version="1"><plain-text-body>
$ ./bin/activemq
ACTIVEMQ_HOME: /Users/bsnyder/amq/apache-activemq-5.1.0
ACTIVEMQ_BASE: /Users/bsnyder/amq/apache-activemq-5.1.0
@@ -56,25 +49,23 @@
INFO log - Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
INFO log - jetty-6.1.9
INFO WebConsoleStarter - ActiveMQ WebConsole initialized.
-INFO /admin - Initializing Spring FrameworkServlet 'dispatcher'
+INFO /admin - Initializing Spring FrameworkServlet 'dispatcher'
INFO log - ActiveMQ Console at http://0.0.0.0:8161/admin
INFO log - ActiveMQ Web Demos at http://0.0.0.0:8161/demo
INFO log - RESTful file access application at http://0.0.0.0:8161/fileserver
INFO log - Started SelectChannelConnector@0.0.0.0:8161
INFO FailoverTransport - Successfully connected to tcp://localhost:61616
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>But stopping ActiveMQ to change the logging level is not always feasible. There are many cases where the logging level and other configuration details may need to be changed at runtime. Using a JMX tool such as jconsole, the logging configuration file can be changed and reloaded without shutting down ActiveMQ. </p>
<p>To change the ActiveMQ logging level from INFO to DEBUG while ActiveMQ is running, start up jconsole, point to the ActiveMQ instance and navigate to the Broker object's Operations tab as shown below: </p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="how-do-i-change-the-logging.data/reloadLog4jProperties1.png" data-image-src="/confluence/download/attachments/35929/reloadLog4jProperties1.png?version=2&modificationDate=1224001802000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="9148" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="reloadLog4jProperties1.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35929" data-linked-resource-container-version="7"></span> </p>
+<p><image><attachment ri:filename="reloadLog4jProperties1.png"></attachment></image> </p>
<p>To enable debug level logging in ActiveMQ, edit the <code>conf/log4j.properties</code> file that is part of the ActiveMQ binary distribution to disable INFO level logging and enable DEBUG level logging from this: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="69566c36-e040-447f-b6a7-c3b605598339" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j.rootLogger=INFO, stdout, out
log4j.logger.org.apache.activemq.spring=WARN
log4j.logger.org.springframework=WARN
@@ -84,13 +75,11 @@
# comment out the above lines and uncomment the next.
#log4j.rootLogger=DEBUG, out, stdout
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>to this: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3d1df33e-61ff-437d-8f1f-6f8966109da9" ac:name="code" ac:schema-version="1"><plain-text-body>
#log4j.rootLogger=INFO, stdout, out
log4j.logger.org.apache.activemq.spring=WARN
log4j.logger.org.springframework=WARN
@@ -100,19 +89,17 @@
# comment out the above lines and uncomment the next.
log4j.rootLogger=DEBUG, out, stdout
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Notice that the line <code>log4j.rootLogger=INFO, stdout, out</code> has been commented out and the line <code>log4j.rootLogger=DEBUG, out, stdout</code> has been uncommented. Save this change and then, in jconsole, click the button named <strong>reloadLog4jProperties</strong> as shown below: </p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="how-do-i-change-the-logging.data/reloadLog4jProperties2.png" data-image-src="/confluence/download/attachments/35929/reloadLog4jProperties2.png?version=2&modificationDate=1224001802000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="9147" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="reloadLog4jProperties2.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35929" data-linked-resource-container-version="7"></span> </p>
+<p><image><attachment ri:filename="reloadLog4jProperties2.png"></attachment></image> </p>
<p>After clicking the <strong>reloadLog4jProperties</strong> button, the dialog pops up stating, 'Method successfully invoked'. This just lets you know that the <code>reloadLog4jProperties</code> method was invoked to reload the <code>conf/log4j.properties</code> file. Now notice in the terminal where ActiveMQ is running that the logging that is being output is now DEBUG: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4254803e-e312-467b-819b-c303a0be9254" ac:name="code" ac:schema-version="1"><plain-text-body>
INFO WebConsoleStarter - ActiveMQ WebConsole initialized.
-INFO /admin - Initializing Spring FrameworkServlet 'dispatcher'
+INFO /admin - Initializing Spring FrameworkServlet 'dispatcher'
INFO log - ActiveMQ Console at http://0.0.0.0:8161/admin
INFO log - ActiveMQ Web Demos at http://0.0.0.0:8161/demo
INFO log - RESTful file access application at http://0.0.0.0:8161/fileserver
@@ -134,8 +121,7 @@
DEBUG InactivityMonitor - 9999 ms elapsed since last write check.
DEBUG InactivityMonitor - 10000 ms elapsed since last write check.
DEBUG InactivityMonitor - 29999 ms elapsed since last read check.
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Disabling DEBUG level logging and enabling INFO level logging is done by editing the <code>log4j.properties</code> file and clicking the <strong>reloadLog4jProperties</strong> button again. </p></div>
diff --git a/how-do-i-change-the-message-store-directory-for-an-embedded-broker.xml b/how-do-i-change-the-message-store-directory-for-an-embedded-broker.xml
index 6a9e0e4..1cb7992 100644
--- a/how-do-i-change-the-message-store-directory-for-an-embedded-broker.xml
+++ b/how-do-i-change-the-message-store-directory-for-an-embedded-broker.xml
@@ -1,5 +1,3 @@
-<div class="wiki-content maincontent"><p>Embedded brokers create an ActiveMQ directory under the current working directory to store it's persistent message data. To change the location of the directory used by the message store, set the <strong>activemq.store.dir</strong> system property to the directory you want it to use.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[java -Dactivemq.store.dir=/temp your.Application
-]]></script>
-</div></div></div>
+<div class="wiki-content maincontent"><p>Embedded brokers create an ActiveMQ directory under the current working directory to store it's persistent message data. To change the location of the directory used by the message store, set the <strong>activemq.store.dir</strong> system property to the directory you want it to use.</p><p>Example:</p><structured-macro ac:macro-id="1086a0e9-3648-4f5a-aa24-ce29a6c1cd3b" ac:name="code" ac:schema-version="1"><plain-text-body>java -Dactivemq.store.dir=/temp your.Application
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-compile-from-the-source.xml b/how-do-i-compile-from-the-source.xml
index b3bac0c..d97d72e 100644
--- a/how-do-i-compile-from-the-source.xml
+++ b/how-do-i-compile-from-the-source.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIcompilefromthesource-HowdoIcompilefromthesourcecode?">How do I compile from the source code?</h2>
+<div class="wiki-content maincontent"><h2>How do I compile from the source code?</h2>
-<p>See the <a shape="rect" href="building.xml">Building</a> page</p></div>
+<p>See the <link><page ri:content-title="Building"></page></link> page</p></div>
diff --git a/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker.xml b/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker.xml
index 7207486..01b03cd 100644
--- a/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker.xml
+++ b/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker.xml
@@ -1,11 +1,2 @@
-<div class="wiki-content maincontent"><p>Scaling to tens of thousands of Queues in a single broker is relatively straightforward - but requires some configuration changes from the default.</p><h2 id="HowdoIconfigure10sof1000sofQueuesinasinglebroker-ReducingThreads">Reducing Threads</h2><p>With the default configuration, ActiveMQ is configured to use a dispatch thread per Queue - you can use set the optimizedDispatch property on the destination policy entry - see <a shape="rect" href="per-destination-policies.xml">configuring Queues</a>.</p><p>ActiveMQ can optionally use internally a thread pool to control dispatching of messages - but as a lot of deployment operating systems are good at handling a large number of threads, this is off by default. To enable this option, either set the ACTIVEMQ_OPTS to disable dedicated task runners in the start up script, INSTALL_DIR/bin/activemq -e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ACTIVEMQ_OPTS="-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=false"
-]]></script>
-</div></div><p>or you can set ACTIVEMQ_OPTS in /etc/activemq.conf.</p><p><strong>Note:</strong> From ActiveMQ 5.6 onwards the dedicated task runner is disabled by default (see
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-3667?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/improvement.png">AMQ-3667</a>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
-).</p><p>To reduce the number of threads used for the transport - take a look at using the NIO transport - see <a shape="rect" href="configuring-transports.xml">Configuring Transports</a></p><p>Here is an <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/sample-conf/activemq-scalability.xml">example</a> of this in use in one of the provided sample broker configuration files.</p><h2 id="HowdoIconfigure10sof1000sofQueuesinasinglebroker-ReducingMemoryConsumption">Reducing Memory Consumption</h2><p>Reduce the memory used per thread - see <a shape="rect" href="javalangoutofmemory.xml">reducing memory consumption</a></p><h2 id="HowdoIconfigure10sof1000sofQueuesinasinglebroker-Reducenumberoffiledescriptors">Reduce number of file descriptors</h2><p>ActiveMQ uses the amqPersistenceAdapter by default for persistent messages. Unfortunately, this persistence adapter (as well as the kahaPersistenceAdapter) opens a file descriptor for each queue. When creating large numbers of queues, you'll quickly run into the limit for your OS.</p><p>You can either choose another <a shape="rect" href="persistence.xml">persistence option</a></p><p>or - try out the new <a shape="rect" href="kahadb.xml">KahaDB</a> in version 5.3 and higher</p><h2 id="HowdoIconfigure10sof1000sofQueuesinasinglebroker-Increasethelimitonfiledescriptorsperprocess">Increase the limit on file descriptors per process</h2><p>Try <a shape="rect" class="external-link" href="http://tinyurl.com/o9qs2f" rel="nofollow">googling for the OS you are using</a></p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="636bff55-db89-48bb-be51-893e883ae03e" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Scaling Queues"></page></link></parameter></structured-macro></p></div>
diff --git a/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages.xml b/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages.xml
index f5933e7..9ad8956 100644
--- a/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages.xml
+++ b/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Nearly all messaging systems (certainly open source ones) hold either a copy of a persistent message or a reference to a persisted message in memory. This is primarily to try and improve performance, but it also can significantly decrease the complexity of implementation. In fact ActiveMQ version 4 and below worked this - way - by holding references to persisted messages in memory.</p><p>However there is a limitation to this approach, no matter how much memory you have at your disposal, you will hit a limit to the number persistent messages a broker can handle at any particular time.</p><p>To get around this limitation, ActiveMQ introduced a paging cache - for all message stores (except the memory store) to get the best of both worlds - great performance and the ability to hold 100s of millions of messages in persistent store. ActiveMQ is <strong>not</strong> limited by memory availability, but by the size of the disk available to hold the persistent messages.</p><p>For more information see: <a shape="rect" href="message-cursors.xml">Message Cursors</a></p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="726a720b-0202-42db-aa45-6578592397db" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Scaling the Depth of a Queue"></page></link></parameter></structured-macro></p></div>
diff --git a/how-do-i-configure-activemq-to-use-aio-server-transport.xml b/how-do-i-configure-activemq-to-use-aio-server-transport.xml
index 0641644..69d78df 100644
--- a/how-do-i-configure-activemq-to-use-aio-server-transport.xml
+++ b/how-do-i-configure-activemq-to-use-aio-server-transport.xml
@@ -2,7 +2,7 @@
<p>For Windows XP:</p>
-<p>1. Download AIO (Asynchronous IO for Java) from IBM (<a shape="rect" class="external-link" href="http://www.alphaworks.ibm.com/tech/aio4j" rel="nofollow">http://www.alphaworks.ibm.com/tech/aio4j</a>).</p>
+<p>1. Download AIO (Asynchronous IO for Java) from IBM (<a shape="rect" href="http://www.alphaworks.ibm.com/tech/aio4j">http://www.alphaworks.ibm.com/tech/aio4j</a>).</p>
<p>2. Unzip the downloaded file and copy the following files: </p>
@@ -15,8 +15,8 @@
<p>5. Edit ActiveMQ's configuration file (<strong>activemq.xml</strong>, found in the conf folder). Look the following snippet:
<br clear="none" class="atl-forced-newline"></p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre><!-- ==================================================================== -->
+<structured-macro ac:macro-id="8206c53e-2e9b-45bc-a393-0943547bde5e" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+<!-- ==================================================================== -->
<!-- ActiveMQ Broker Configuration -->
<!-- ==================================================================== -->
<broker>
@@ -26,27 +26,23 @@
.
.
</broker>
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
<p><br clear="none" class="atl-forced-newline"></p>
<p> Change the connector settings, change <strong>tcpServerTransport</strong> to <strong>serverTransport</strong> and remove the unneeded parameters):
<br clear="none" class="atl-forced-newline"></p>
- <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre><connector>
+ <structured-macro ac:macro-id="910ac916-db01-4ecd-92d7-49c2996bc791" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+<connector>
<serverTransport uri="activeio:aio://<ip address>:<port>" />
</connector>
- </pre>
-</div></div>
+ </plain-text-body></structured-macro>
<p><br clear="none" class="atl-forced-newline"></p>
<p> Example:
<br clear="none" class="atl-forced-newline"></p>
- <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>
+ <structured-macro ac:macro-id="e6ac3503-9331-425d-8a3c-e928fd877cac" ac:name="noformat" ac:schema-version="1"><plain-text-body>
<connector>
<serverTransport uri="activeio:aio://192.168.0.162:61616" />
</connector>
- </pre>
-</div></div></div>
+ </plain-text-body></structured-macro></div>
diff --git a/how-do-i-configure-automatic-reconnection.xml b/how-do-i-configure-automatic-reconnection.xml
index c34a2d9..ed460d9 100644
--- a/how-do-i-configure-automatic-reconnection.xml
+++ b/how-do-i-configure-automatic-reconnection.xml
@@ -4,11 +4,9 @@
<p>e.g. connecting to the URL</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="103c4336-24eb-48b3-8809-5d7e5adba995" ac:name="code" ac:schema-version="1"><plain-text-body>
failover:tcp://host1:port1,tcp://host2:port2
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>For more detail see <a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></p></div>
+<p>For more detail see <link><page ri:content-title="Failover Transport Reference"></page></link></p></div>
diff --git a/how-do-i-configure-distributed-queues-or-topics.xml b/how-do-i-configure-distributed-queues-or-topics.xml
index 7f26bb8..39ed60d 100644
--- a/how-do-i-configure-distributed-queues-or-topics.xml
+++ b/how-do-i-configure-distributed-queues-or-topics.xml
@@ -1,13 +1,14 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIconfiguredistributedqueuesortopics-HowdoIconfiguredistributedqueuesortopics">How do I configure distributed queues or topics</h2>
+<div class="wiki-content maincontent"><h2>How do I configure distributed queues or topics</h2>
-<p>You don't need to explicitly <a shape="rect" href="how-do-i-configure-the-queues-i-want.xml">configure distributed queues or topics</a> as any queue or topic is automatically distributed across other brokers when the brokers are configured in either a store and forward network or a master/slave cluster. </p>
+<p>You don't need to explicitly <link><page ri:content-title="How do I configure the queues I want"></page><link-body>configure distributed queues or topics</link-body></link> as any queue or topic is automatically distributed across other brokers when the brokers are configured in either a store and forward network or a master/slave cluster. </p>
<p>So you just need to connect brokers together to form either</p>
-<ul><li>a <a shape="rect" href="networks-of-brokers.xml">Store and Forward Network of Brokers</a>, which means the messages travel from broker to broker until they reach a consumer; with each message being owned by a single broker at any point in time</li><li>a <a shape="rect" href="masterslave.xml">Master/Slave Cluster</a>, which means all messages are replicated across each broker in the master/slave cluster</li></ul>
+<ul><li>a <link><page ri:content-title="Networks of Brokers"></page><link-body>Store and Forward Network of Brokers</link-body></link>, which means the messages travel from broker to broker until they reach a consumer; with each message being owned by a single broker at any point in time</li><li>a <link><page ri:content-title="MasterSlave"></page><link-body>Master/Slave Cluster</link-body></link>, which means all messages are replicated across each broker in the master/slave cluster</li></ul>
-<h3 id="HowdoIconfiguredistributedqueuesortopics-Alsosee">Also see</h3>
+<h3>Also see</h3>
-<ul><li><a shape="rect" href="how-do-i-configure-the-queues-i-want.xml">How do I configure the queues I want</a></li><li><a shape="rect" href="how-do-distributed-queues-work.xml">How do distributed queues work</a></li><li><a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a></li><li><a shape="rect" href="masterslave.xml">MasterSlave</a></li></ul></div>
+<ul><li><link><page ri:content-title="How do I configure the queues I want"></page></link></li><li><link><page ri:content-title="How do distributed queues work"></page></link></li><li><link><page ri:content-title="Networks of Brokers"></page></link></li><li><link><page ri:content-title="MasterSlave"></page></link></li></ul>
+</div>
diff --git a/how-do-i-configure-the-queues-i-want.xml b/how-do-i-configure-the-queues-i-want.xml
index f3356b4..541cc19 100644
--- a/how-do-i-configure-the-queues-i-want.xml
+++ b/how-do-i-configure-the-queues-i-want.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><p><span class="error">The license could not be verified: License Certificate has expired!</span></p>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="2affa320-6478-41f3-92c5-b82475c1c623" ac:name="redirect" ac:schema-version="1"><parameter ac:name="location"><link><page ri:content-title="How do I create new destinations"></page></link></parameter></structured-macro></p>
<p>With ActiveMQ there is no real resaon to explicitly setup/configure the queues you are gonna need. If you try to publish or subscribe from any queue or topic it will be silently created on the fly.</p>
<p>Sometimes people put destinations into JNDI so that they can be pulled out by their application without needing to know the real, physical queue/topic name. This is fine, you can just add the ActiveMQQueue and ActiveMQTopic objects into JNDI (or any configuration mechanism you wish).</p>
-<p>Also if you use the ActiveMQInitialContextFactory, then you can explicitly configure which destinations appear in the context using the jndi.properties approach. For more information please refer to the <a shape="rect" href="jndi-support.xml">JNDI Support</a></p></div>
+<p>Also if you use the ActiveMQInitialContextFactory, then you can explicitly configure which destinations appear in the context using the jndi.properties approach. For more information please refer to the <link><page ri:content-title="JNDI Support"></page></link></p></div>
diff --git a/how-do-i-connect-to-one-of-a-number-of-message-brokers.xml b/how-do-i-connect-to-one-of-a-number-of-message-brokers.xml
index c9a13f0..87aff01 100644
--- a/how-do-i-connect-to-one-of-a-number-of-message-brokers.xml
+++ b/how-do-i-connect-to-one-of-a-number-of-message-brokers.xml
@@ -2,11 +2,9 @@
<p>You can specify a list of URLs to connect to (for example if you have message brokers running on a number of machines). To specify a list of URLs, use a comma separated list of URLs with a prefix of list:. e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="25ac053a-6b38-4166-85ed-49477b4e7659" ac:name="code" ac:schema-version="1"><plain-text-body>
list:tcp://localhost:61699,tcp://localhost:61617,tcp://localhost:61698
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>The JMS client will then try and connect to each one in turn, in a random order until one is connected. If they all fail to connect a sleep occurs and then this loop is retried a number of times until either a connection can be established or an exception is thrown. For more detail see <a shape="rect" href="configuring-transports.xml">Configuring Transports</a></p></div>
+<p>The JMS client will then try and connect to each one in turn, in a random order until one is connected. If they all fail to connect a sleep occurs and then this loop is retried a number of times until either a connection can be established or an exception is thrown. For more detail see <link><page ri:content-title="Configuring Transports"></page></link></p></div>
diff --git a/how-do-i-consume-a-specific-message.xml b/how-do-i-consume-a-specific-message.xml
index 1f5aaf1..f37823a 100644
--- a/how-do-i-consume-a-specific-message.xml
+++ b/how-do-i-consume-a-specific-message.xml
@@ -6,13 +6,11 @@
<p>e.g. here is an example selector</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-JMSMessageID = 'abc'
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="8edc4aec-e914-4d4b-912f-59a0a0fccd19" ac:name="code" ac:schema-version="1"><plain-text-body>
+JMSMessageID = 'abc'
+</plain-text-body></structured-macro>
<p>Note that this is not a very efficient way of working with JMS (JMS is designed for consumers to be long lived objects working across many messageS), but it can be useful in certain situations.</p>
-<p>Another option is just to use <a shape="rect" href="jmx.xml">JMX</a> directly to browse messages on a queue, process them and then delete them.</p></div>
+<p>Another option is just to use <link><page ri:content-title="JMX"></page></link> directly to browse messages on a queue, process them and then delete them.</p></div>
diff --git a/how-do-i-create-new-destinations.xml b/how-do-i-create-new-destinations.xml
index a4613cc..01aa301 100644
--- a/how-do-i-create-new-destinations.xml
+++ b/how-do-i-create-new-destinations.xml
@@ -7,21 +7,21 @@
<p>and the broker will automatically create the physical destinations for you. This avoids spending large amounts of time creating every individual destination you wish to use and possibly then exposing it in some JNDI provider.</p>
-<p>In addition, if you are using JNDI to lookup connection factory and destinations, you can specify which destinations you wish to create by default using the properties file. See the <a shape="rect" href="jndi-support.xml">JNDI Support</a> for more details. </p>
+<p>In addition, if you are using JNDI to lookup connection factory and destinations, you can specify which destinations you wish to create by default using the properties file. See the <link><page ri:content-title="JNDI Support"></page></link> for more details. </p>
-<h3 id="HowdoIcreatenewdestinations-Creatingdestinationsonstartup">Creating destinations on startup</h3>
+<h3>Creating destinations on startup</h3>
-<p>Its completely optional but as of 4.1 you can <a shape="rect" href="configure-startup-destinations.xml">Configure Startup Destinations</a> to specify which destinations are automatically created when the broker starts.</p>
+<p>Its completely optional but as of 4.1 you can <link><page ri:content-title="Configure Startup Destinations"></page></link> to specify which destinations are automatically created when the broker starts.</p>
-<h3 id="HowdoIcreatenewdestinations-Limitingcreationofdestinations">Limiting creation of destinations</h3>
+<h3>Limiting creation of destinations</h3>
-<p>If you need to restrict access or creation of destinations then please use the <a shape="rect" href="security.xml">Security</a> option to disable destinations being auto-created for certain users. </p>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Client side destination objects are not the same as server side resources</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<p>If you need to restrict access or creation of destinations then please use the <link><page ri:content-title="Security"></page></link> option to disable destinations being auto-created for certain users. </p>
+<structured-macro ac:macro-id="5a28a8d5-28a7-45ad-87a8-b42708854c9a" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Client side destination objects are not the same as server side resources</parameter><rich-text-body>
<p>Note that the ActiveMQ Broker will only create server side resources for destinations when messages are actually sent to them. So you can create as many instances of ActiveMQTopic and ActiveMQQueue on a client without any real overhead until you actually send messages to them on a broker. So a JMS client creating a new ActiveMQQueue POJO does not mean you are creating server side queue resources.</p>
<p>Think of the ActiveMQQueue and ActiveMQTopic classes as like java.net.URL. They are just names which refer to server side resources which are auto-created when they are used.<br clear="none">
-This means that different clients creating different ActiveMQQueue instances will communicate with the same physical queue on a JMS broker if the name is the same.</p></div></div>
+This means that different clients creating different ActiveMQQueue instances will communicate with the same physical queue on a JMS broker if the name is the same.</p></rich-text-body></structured-macro>
-<p>You can browse the currently available queues and topics using <a shape="rect" href="jmx.xml">JMX</a>. You can also use the <a shape="rect" href="jmx.xml">JMX</a> MBeans to create the destinations you require.</p></div>
+<p>You can browse the currently available queues and topics using <link><page ri:content-title="JMX"></page></link>. You can also use the <link><page ri:content-title="JMX"></page></link> MBeans to create the destinations you require.</p></div>
diff --git a/how-do-i-debug-activemq-from-my-ide.xml b/how-do-i-debug-activemq-from-my-ide.xml
index 849de9a..0f9fe11 100644
--- a/how-do-i-debug-activemq-from-my-ide.xml
+++ b/how-do-i-debug-activemq-from-my-ide.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>One option is to run your broker in the same JVM as your application; see <a shape="rect" href="how-to-unit-test-jms-code.xml">How To Unit Test JMS Code</a>.</p><p>Or you can try uncommenting ACTIVEMQ_DEBUG_OPTS in your activemq start script (bin/activemq or bin\activemq.bat) and start remote debugging in your IDE.</p><p>For IDEA, see this article <a shape="rect" class="external-link" href="http://www.javaranch.com/journal/200408/DebuggingServer-sideCode.html" rel="nofollow">http://www.javaranch.com/journal/200408/DebuggingServer-sideCode.html</a></p></div>
+<div class="wiki-content maincontent"><p>One option is to run your broker in the same JVM as your application; see <link><page ri:content-title="How To Unit Test JMS Code"></page></link>.</p><p>Or you can try uncommenting ACTIVEMQ_DEBUG_OPTS in your activemq start script (bin/activemq or bin\activemq.bat) and start remote debugging in your IDE.</p><p>For IDEA, see this article <a shape="rect" class="external-link" href="http://www.javaranch.com/journal/200408/DebuggingServer-sideCode.html" rel="nofollow">http://www.javaranch.com/journal/200408/DebuggingServer-sideCode.html</a></p></div>
diff --git a/how-do-i-define-a-local-address-and-local-port-for-tcp-or-ssl.xml b/how-do-i-define-a-local-address-and-local-port-for-tcp-or-ssl.xml
index 6ed70e5..e210d57 100644
--- a/how-do-i-define-a-local-address-and-local-port-for-tcp-or-ssl.xml
+++ b/how-do-i-define-a-local-address-and-local-port-for-tcp-or-ssl.xml
@@ -1,5 +1,3 @@
-<div class="wiki-content maincontent"><p>TCP based transport protocols (including SSL) allow you to define the local address and local port for Socket to use when it's created.<br clear="none"> This can be useful for clients that reside on multi-homed machines or for clients operating in a DMZ, where only pre-defined ports can be used.</p><p>To specify the local address and local port, ActiveMQ supports the use of the path on the URI, e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ssl://localhost:5666/localhost:60606
-]]></script>
-</div></div><p> </p><p>where the path following the forward slash "localhost:60606" defines the local address and local port</p></div>
+<div class="wiki-content maincontent"><p>TCP based transport protocols (including SSL) allow you to define the local address and local port for Socket to use when it's created.<br clear="none"> This can be useful for clients that reside on multi-homed machines or for clients operating in a DMZ, where only pre-defined ports can be used.</p><p>To specify the local address and local port, ActiveMQ supports the use of the path on the URI, e.g.</p><structured-macro ac:macro-id="f096e582-9220-4ce7-a139-7ba5c7b744d4" ac:name="code" ac:schema-version="1"><plain-text-body>ssl://localhost:5666/localhost:60606
+</plain-text-body></structured-macro><p> </p><p>where the path following the forward slash "localhost:60606" defines the local address and local port</p></div>
diff --git a/how-do-i-delete-a-destination.xml b/how-do-i-delete-a-destination.xml
index 4bcacd8..bed918b 100644
--- a/how-do-i-delete-a-destination.xml
+++ b/how-do-i-delete-a-destination.xml
@@ -1,12 +1,13 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIdeleteadestination-HowdoIdeleteadestination">How do I delete a destination</h2>
+<div class="wiki-content maincontent"><h2>How do I delete a destination</h2>
-<p>via Java code or <a shape="rect" href="jmx.xml">JMX</a> you can grab the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html">BrokerViewMBean</a> and call one of the following methods</p>
+<p>via Java code or <link><page ri:content-title="JMX"></page></link> you can grab the <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html">BrokerViewMBean</a> and call one of the following methods</p>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html#removeQueue(java.lang.String)">removeQueue(String)</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html#removeTopic(java.lang.String)">removeTopic(String)</a></li></ul>
+<ul><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html#removeQueue(java.lang.String)">removeQueue(String)</a></li><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html#removeTopic(java.lang.String)">removeTopic(String)</a></li></ul>
-<h3 id="HowdoIdeleteadestination-Seealso">See also</h3>
+<h3>See also</h3>
-<ul><li><a shape="rect" href="how-do-i-create-new-destinations.xml">How do I create new destinations</a></li><li><a shape="rect" href="how-can-i-monitor-activemq.xml">How can I monitor ActiveMQ</a></li><li><a shape="rect" href="jmx.xml">JMX</a></li><li><a shape="rect" href="web-console.xml">Web Console</a></li></ul></div>
+<ul><li><link><page ri:content-title="How do I create new destinations"></page></link></li><li><link><page ri:content-title="How can I monitor ActiveMQ"></page></link></li><li><link><page ri:content-title="JMX"></page></link></li><li><link><page ri:content-title="Web Console"></page></link></li></ul>
+</div>
diff --git a/how-do-i-disable-logging.xml b/how-do-i-disable-logging.xml
index 5edf5f1..f660be1 100644
--- a/how-do-i-disable-logging.xml
+++ b/how-do-i-disable-logging.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIdisablelogging-HowdoIdisablelogging?">How do I disable logging?</h2>
+<div class="wiki-content maincontent"><h2>How do I disable logging?</h2>
-<p>See <a shape="rect" href="how-do-i-change-the-logging.xml">How do I change the logging</a></p></div>
+<p>See <link><page ri:content-title="How do I change the logging"></page></link></p></div>
diff --git a/how-do-i-disable-persistence.xml b/how-do-i-disable-persistence.xml
index d123b6c..f300c0d 100644
--- a/how-do-i-disable-persistence.xml
+++ b/how-do-i-disable-persistence.xml
@@ -1,9 +1,9 @@
<div class="wiki-content maincontent"><p>There are three main ways to disable persistence, such as for unit testing JMS code</p>
-<ol><li>Set the NON_PERSISTENT message delivery flag on your MessageProducer</li><li>Set the <strong>persistent=false</strong> flag in the <strong><broker/></strong> element of the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> or on the property <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerService.html">BrokerService</a></li><li>Delete the persistence files before running your tests (a bit hacky)</li></ol>
+<ol><li>Set the NON_PERSISTENT message delivery flag on your MessageProducer</li><li>Set the <strong>persistent=false</strong> flag in the <strong><broker/></strong> element of the <link><page ri:content-title="Xml Configuration"></page></link> or on the property <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerService.html">BrokerService</a></li><li>Delete the persistence files before running your tests (a bit hacky)</li></ol>
-<p>If you are unit testing you may be interested in <a shape="rect" href="how-to-unit-test-jms-code.xml">How To Unit Test JMS Code</a>.</p>
+<p>If you are unit testing you may be interested in <link><page ri:content-title="How To Unit Test JMS Code"></page></link>.</p>
-<p>Please refer to the <a shape="rect" href="initial-configuration.xml">Initial Configuration</a> guide on how to disable persistence via system properties, java code or using the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a></p></div>
+<p>Please refer to the <link><page ri:content-title="Initial Configuration"></page></link> guide on how to disable persistence via system properties, java code or using the <link><page ri:content-title="Xml Configuration"></page></link></p></div>
diff --git a/how-do-i-edit-the-website.xml b/how-do-i-edit-the-website.xml
index a152cde..777f479 100644
--- a/how-do-i-edit-the-website.xml
+++ b/how-do-i-edit-the-website.xml
@@ -1,20 +1,20 @@
-<div class="wiki-content maincontent"><p>The website is all contained on a Wiki so that anyone can <a shape="rect" href="contributing.xml">contribute</a></p>
+<div class="wiki-content maincontent"><p>The website is all contained on a Wiki so that anyone can <link><page ri:content-title="Contributing"></page><link-body>contribute</link-body></link></p>
-<h3 id="HowdoIeditthewebsite-Howtoedit">How to edit</h3>
+<h3>How to edit</h3>
<p>You can also click the <strong>edit</strong> button when viewing the website which is located on the bottom of each page.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Spam Prevention</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<structured-macro ac:macro-id="789e806b-e666-4c9b-ac2f-bd25b7630156" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Spam Prevention</parameter><rich-text-body>
<p>We have been attacked by spammers so we are running a spam-avoiding scheme. So you have to ask to be added to the editing group of Confluence. This is quick and easy to do.</p>
-<p>Just send a quick mail to the <a shape="rect" href="discussion-forums.xml">Discussion Forums</a> giving details of your confluence username and we can grant you the necessary editing karma.</p></div></div>
+<p>Just send a quick mail to the <link><page ri:content-title="Discussion Forums"></page></link> giving details of your confluence username and we can grant you the necessary editing karma.</p></rich-text-body></structured-macro>
<p>Note that after you've changed the wiki it is immediately rendered on the <a shape="rect" class="external-link" href="http://cwiki.apache.org/ACTIVEMQ/">http://cwiki.apache.org/ACTIVEMQ/</a> site so you can test it out; then up to an hour or two later it is updated on the Apache site.</p>
-<h3 id="HowdoIeditthewebsite-Howthesiteworks">How the site works</h3>
-<p>There are a few special pages; for example the <a shape="rect" href="navigation.xml">Navigation</a> page is the left hand navigation bar and the <a shape="rect" href="quicklinks.xml">QuickLinks</a> is the top right navigation bar.</p>
+<h3>How the site works</h3>
+<p>There are a few special pages; for example the <link><page ri:content-title="Navigation"></page></link> page is the left hand navigation bar and the <link><page ri:content-title="QuickLinks"></page></link> is the top right navigation bar.</p>
-<p>Other useful <a shape="rect" href="site.xml">links</a> are</p>
+<p>Other useful <link><page ri:content-title="Site"></page><link-body>links</link-body></link> are</p>
-<ul class="childpages-macro"><li><a shape="rect" href="banner.xml">Banner</a></li><li><a shape="rect" href="navigation.xml">Navigation</a></li><li><a shape="rect" href="quicklinks.xml">QuickLinks</a></li><li><a shape="rect" href="siteindex.xml">SiteIndex</a></li><li><a shape="rect" href="sitemap.xml">SiteMap</a></li></ul></div>
+<structured-macro ac:macro-id="bf1b0c9c-5191-4874-9ce5-d01b82b366fa" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Site"></page></link></parameter></structured-macro></div>
diff --git a/how-do-i-embed-a-broker-inside-a-connection.xml b/how-do-i-embed-a-broker-inside-a-connection.xml
index d054702..b362669 100644
--- a/how-do-i-embed-a-broker-inside-a-connection.xml
+++ b/how-do-i-embed-a-broker-inside-a-connection.xml
@@ -1,136 +1,116 @@
-<div class="wiki-content maincontent"><p>In many messaging topologies there are JMS Brokers (server side) and a JMS client side. Often it makes sense to deploy a broker within your JVM. This allows you to optimise away a network hop; making the networking of JMS as efficient as pure RMI, but with all the usual JMS features of location independence, reliability, load balancing etc.</p><p>There are various ways to embed a broker in ActiveMQ depending on if you are using Java, Spring, XBean or using the ActiveMQConnectionFactory .</p><h3 id="HowdoIembedaBrokerinsideaConnection-UsingexplicitJavacode">Using explicit Java code</h3><p>The following Java code will create an embedded broker</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[BrokerService broker = new BrokerService();
+<div class="wiki-content maincontent"><p>In many messaging topologies there are JMS Brokers (server side) and a JMS client side. Often it makes sense to deploy a broker within your JVM. This allows you to optimise away a network hop; making the networking of JMS as efficient as pure RMI, but with all the usual JMS features of location independence, reliability, load balancing etc.</p><p>There are various ways to embed a broker in ActiveMQ depending on if you are using Java, Spring, XBean or using the ActiveMQConnectionFactory .</p><h3>Using explicit Java code</h3><p>The following Java code will create an embedded broker</p><structured-macro ac:macro-id="9eaa5bb3-576f-42b5-9c4b-04d93d7c7ee6" ac:name="code" ac:schema-version="1"><plain-text-body>BrokerService broker = new BrokerService();
// configure the broker
-broker.addConnector("tcp://localhost:61616");
+broker.addConnector("tcp://localhost:61616");
broker.start();
-]]></script>
-</div></div><p>If you want to lazily bind the transport connector as part of start(), useful when start() will block pending a store lock (as in a slave start), you can use the following code</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[BrokerService broker = new BrokerService();
+</plain-text-body></structured-macro><p>If you want to lazily bind the transport connector as part of start(), useful when start() will block pending a store lock (as in a slave start), you can use the following code</p><structured-macro ac:macro-id="ac608f29-1173-4703-b0cc-192bed0dd67f" ac:name="code" ac:schema-version="1"><plain-text-body>BrokerService broker = new BrokerService();
TransportConnector connector = new TransportConnector();
-connector.setUri(new URI("tcp://localhost:61616"));
+connector.setUri(new URI("tcp://localhost:61616"));
broker.addConnector(connector);
broker.start();
-]]></script>
-</div></div><p>In the same JVM clients can then use the <a shape="rect" href="vm-transport-reference.xml">vm:// transport</a> to connect to the embedded broker - whilst external clients can use the <a shape="rect" href="tcp-transport-reference.xml">tcp:// protocol</a></p><p>If you have more than one embedded broker, ensure that you give them a unique name and - e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[BrokerService broker = new BrokerService();
+</plain-text-body></structured-macro><p>In the same JVM clients can then use the <link><page ri:content-title="VM Transport Reference"></page><plain-text-link-body>vm:// transport</plain-text-link-body></link> to connect to the embedded broker - whilst external clients can use the <link><page ri:content-title="TCP Transport Reference"></page><plain-text-link-body>tcp:// protocol</plain-text-link-body></link></p><p>If you have more than one embedded broker, ensure that you give them a unique name and - e.g.</p><structured-macro ac:macro-id="ab19815a-2dfd-4e65-a5be-b8210339a28c" ac:name="code" ac:schema-version="1"><plain-text-body>BrokerService broker = new BrokerService();
// configure the broker
-broker.setBrokerName("fred");
-broker.addConnector("tcp://localhost:61616");
+broker.setBrokerName("fred");
+broker.addConnector("tcp://localhost:61616");
broker.start();
-]]></script>
-</div></div><p>Then if you want to connect to the broker named 'fred' from within the same JVM, you can by using the uri <strong>vm://fred</strong></p><p>It is possible to fully configure a broker through application code e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[BrokerService broker = new BrokerService();
-broker.setBrokerName("fred");
+</plain-text-body></structured-macro><p>Then if you want to connect to the broker named 'fred' from within the same JVM, you can by using the uri <strong>vm://fred</strong></p><p>It is possible to fully configure a broker through application code e.g.</p><structured-macro ac:macro-id="7e0ebf92-ef49-416b-b093-0dd90aa42955" ac:name="code" ac:schema-version="1"><plain-text-body>BrokerService broker = new BrokerService();
+broker.setBrokerName("fred");
broker.setUseShutdownHook(false);
//Add plugin
broker.setPlugins(new BrokerPlugin[]{new JaasAuthenticationPlugin()});
//Add a network connection
-NetworkConnector connector = answer.addNetworkConnector("static://"+"tcp://somehost:61616");
+NetworkConnector connector = answer.addNetworkConnector("static://"+"tcp://somehost:61616");
connector.setDuplex(true);
-broker.addConnector("tcp://localhost:61616");
+broker.addConnector("tcp://localhost:61616");
broker.start();
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Please note that you should add plugins before connectors or they will not be initialized</p></div></div><p>For more details on the available properties you can specify, see the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.11.0/apidocs/org/apache/activemq/broker/BrokerService.html">BrokerService javadoc</a></p><h3 id="HowdoIembedaBrokerinsideaConnection-UsingtheBrokerFactory">Using the BrokerFactory</h3><p>There is a helper class called <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerFactory.html">BrokerFactory</a> which can be used to create a broker via URI for configuration.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[BrokerService broker = BrokerFactory.createBroker(new URI(someURI));
-]]></script>
-</div></div><p>The available values of the URI are</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>URI scheme</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>xbean:</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>xbean:activemq.xml</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Searches the classpath (and file system) for an XML document with the given URI (activemq.xml in this case) which will then be used as the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>broker:</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>broker:tcp://localhost:61616</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a> to confgure the broker</p></td></tr></tbody></table></div><h3 id="HowdoIembedaBrokerinsideaConnection-UsingSpring">Using Spring</h3><p>There is a factory bean that can refer to an external ActiveMQ XML configuration file</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
- <property name="config" value="classpath:org/apache/activemq/xbean/activemq.xml" />
- <property name="start" value="true" />
+</plain-text-body></structured-macro><structured-macro ac:macro-id="b7967e06-0454-4e9a-af9a-5c24b63b0501" ac:name="note" ac:schema-version="1"><rich-text-body><p>Please note that you should add plugins before connectors or they will not be initialized</p></rich-text-body></structured-macro><p>For more details on the available properties you can specify, see the <a shape="rect" href="http://activemq.apache.org/maven/5.11.0/apidocs/org/apache/activemq/broker/BrokerService.html">BrokerService javadoc</a></p><h3>Using the BrokerFactory</h3><p>There is a helper class called <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerFactory.html">BrokerFactory</a> which can be used to create a broker via URI for configuration.</p><structured-macro ac:macro-id="a8d3bdfc-dd6d-4a02-aa2e-76524c94fc34" ac:name="code" ac:schema-version="1"><plain-text-body>BrokerService broker = BrokerFactory.createBroker(new URI(someURI));
+</plain-text-body></structured-macro><p>The available values of the URI are</p><table><tbody><tr><th colspan="1" rowspan="1"><p>URI scheme</p></th><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>xbean:</p></td><td colspan="1" rowspan="1"><p>xbean:activemq.xml</p></td><td colspan="1" rowspan="1"><p>Searches the classpath (and file system) for an XML document with the given URI (activemq.xml in this case) which will then be used as the <link><page ri:content-title="Xml Configuration"></page></link></p></td></tr><tr><td colspan="1" rowspan="1"><p>broker:</p></td><td colspan="1" rowspan="1"><p>broker:tcp://localhost:61616</p></td><td colspan="1" rowspan="1"><p>Uses the <link><page ri:content-title="Broker Configuration URI"></page></link> to confgure the broker</p></td></tr></tbody></table><h3>Using Spring</h3><p>There is a factory bean that can refer to an external ActiveMQ XML configuration file</p><structured-macro ac:macro-id="2243664c-6d07-401c-94c7-af12ccb45fbf" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
+ <property name="config" value="classpath:org/apache/activemq/xbean/activemq.xml" />
+ <property name="start" value="true" />
</bean>
-]]></script>
-</div></div><p>In this case the usual Spring 'classpath:org/apache/activemq/xbean/activemq.xml' resource mechanism is being used so that the activemq.xml file would be found on the classpath by looking inside all the directories on the classpath then looking for 'org/apache/activemq/xbean/activemq.xml'. You can of course change this to any value you like. e.g. use classpath:activemq.xml if you just want to drop it in a directory that is in the classpath; like WEB-INF/classes in a web application.</p><p>If you wish you can use a URL instead using the <strong>file:* or *http:</strong> prefixes. For more details see how <a shape="rect" class="external-link" href="http://static.springframework.org/spring/docs/1.2.x/reference/beans.html#context-functionality-resources" rel="nofollow">Spring deals with resources</a></p><h3 id="HowdoIembedaBrokerinsideaConnection-UsingXBean">Using XBean</h3><p>If you are already using <a shape="rect" class="external-link" href="http://geronimo.apache.org/xbean/">XBean</a> then you can just mix and match your Spring/XBean <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/xbean/activemq.xml">XML configuration</a> with ActiveMQ's configuration.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans
- xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
+</plain-text-body></structured-macro><p>In this case the usual Spring 'classpath:org/apache/activemq/xbean/activemq.xml' resource mechanism is being used so that the activemq.xml file would be found on the classpath by looking inside all the directories on the classpath then looking for 'org/apache/activemq/xbean/activemq.xml'. You can of course change this to any value you like. e.g. use classpath:activemq.xml if you just want to drop it in a directory that is in the classpath; like WEB-INF/classes in a web application.</p><p>If you wish you can use a URL instead using the <strong>file:* or *http:</strong> prefixes. For more details see how <a shape="rect" href="http://static.springframework.org/spring/docs/1.2.x/reference/beans.html#context-functionality-resources">Spring deals with resources</a></p><h3>Using XBean</h3><p>If you are already using <a shape="rect" href="http://geronimo.apache.org/xbean/">XBean</a> then you can just mix and match your Spring/XBean <a shape="rect" href="https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/xbean/activemq.xml">XML configuration</a> with ActiveMQ's configuration.</p><structured-macro ac:macro-id="8349179f-1e83-4dd6-801a-e787987af165" ac:name="code" ac:schema-version="1"><plain-text-body><beans
+ xmlns="http://www.springframework.org/schema/beans"
+ xmlns:amq="http://activemq.apache.org/schema/core"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+ http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" xmlns="http://activemq.apache.org/schema/core">
+ <broker useJmx="true" xmlns="http://activemq.apache.org/schema/core">
<persistenceFactory>
- <kahaDB directory="${basedir}/target" />
+ <kahaDB directory="${basedir}/target" />
</persistenceFactory>
<transportConnectors>
- <transportConnector uri="tcp://localhost:61636" />
+ <transportConnector uri="tcp://localhost:61636" />
</transportConnectors>
</broker>
</beans>
-]]></script>
-</div></div><h3 id="HowdoIembedaBrokerinsideaConnection-UsingSpring2.0">Using Spring 2.0</h3><p>If you are using Spring 2.0 and ActiveMQ 4.1 or later (and xbean-spring 2.5 or later) you can embed the ActiveMQ broker XML inside any regular Spring.xml file without requiring the above factory bean. e.g. here is an <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/spring-embedded-xbean.xml">example</a> of a regular Spring XML file in Spring 2.0 which also configures a broker.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans
- xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
+</plain-text-body></structured-macro><h3>Using Spring 2.0</h3><p>If you are using Spring 2.0 and ActiveMQ 4.1 or later (and xbean-spring 2.5 or later) you can embed the ActiveMQ broker XML inside any regular Spring.xml file without requiring the above factory bean. e.g. here is an <a shape="rect" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/test/resources/spring-embedded-xbean.xml">example</a> of a regular Spring XML file in Spring 2.0 which also configures a broker.</p><structured-macro ac:macro-id="fe131cb2-ea4a-4f1f-a40a-fc78932b400b" ac:name="code" ac:schema-version="1"><plain-text-body><beans
+ xmlns="http://www.springframework.org/schema/beans"
+ xmlns:amq="http://activemq.apache.org/schema/core"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+ http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
<!-- lets create an embedded ActiveMQ Broker -->
- <amq:broker useJmx="false" persistent="false">
+ <amq:broker useJmx="false" persistent="false">
<amq:transportConnectors>
- <amq:transportConnector uri="tcp://localhost:0" />
+ <amq:transportConnector uri="tcp://localhost:0" />
</amq:transportConnectors>
</amq:broker>
<!-- ActiveMQ destinations to use -->
- <amq:queue id="destination" physicalName="org.apache.activemq.spring.Test.spring.embedded"/>
+ <amq:queue id="destination" physicalName="org.apache.activemq.spring.Test.spring.embedded"/>
<!-- JMS ConnectionFactory to use, configuring the embedded broker using XML -->
- <amq:connectionFactory id="jmsFactory" brokerURL="vm://localhost"/>
+ <amq:connectionFactory id="jmsFactory" brokerURL="vm://localhost"/>
<!-- Spring JMS Template -->
- <bean id="myJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
- <property name="connectionFactory">
+ <bean id="myJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
+ <property name="connectionFactory">
<!-- lets wrap in a pool to avoid creating a connection per send -->
- <bean class="org.springframework.jms.connection.SingleConnectionFactory">
- <property name="targetConnectionFactory">
- <ref local="jmsFactory" />
+ <bean class="org.springframework.jms.connection.SingleConnectionFactory">
+ <property name="targetConnectionFactory">
+ <ref local="jmsFactory" />
</property>
</bean>
</property>
</bean>
- <bean id="consumerJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
- <property name="connectionFactory" ref="jmsFactory"/>
+ <bean id="consumerJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
+ <property name="connectionFactory" ref="jmsFactory"/>
</bean>
<!-- a sample POJO which uses a Spring JmsTemplate -->
- <bean id="producer" class="org.apache.activemq.spring.SpringProducer">
- <property name="template">
- <ref bean="myJmsTemplate"></ref>
+ <bean id="producer" class="org.apache.activemq.spring.SpringProducer">
+ <property name="template">
+ <ref bean="myJmsTemplate"></ref>
</property>
- <property name="destination">
- <ref bean="destination" />
+ <property name="destination">
+ <ref bean="destination" />
</property>
- <property name="messageCount">
+ <property name="messageCount">
<value>10</value>
</property>
</bean>
<!-- a sample POJO consumer -->
- <bean id="consumer" class="org.apache.activemq.spring.SpringConsumer">
- <property name="template" ref="consumerJmsTemplate"/>
- <property name="destination" ref="destination"/>
+ <bean id="consumer" class="org.apache.activemq.spring.SpringConsumer">
+ <property name="template" ref="consumerJmsTemplate"/>
+ <property name="destination" ref="destination"/>
</bean>
</beans>
-]]></script>
-</div></div><h3 id="HowdoIembedaBrokerinsideaConnection-UsingActiveMQConnectionFactory">Using ActiveMQConnectionFactory</h3><p>An embedded broker can also be created using an ActiveMQConnectionFactory and using a vm connector as a uri. e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory("vm://localhost?broker.persistent=false");
-]]></script>
-</div></div><p>Use the query parameters "broker.<property>" to configure the broker, where <property> matches the bean properties on the BrokerService.</p><p>The broker will be created upon creation of the first connection.</p><p>You can turn off auto creation by setting the create property on the VM Transport to false:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory("vm://localhost?create=false");
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro><h3>Using ActiveMQConnectionFactory</h3><p>An embedded broker can also be created using an ActiveMQConnectionFactory and using a vm connector as a uri. e.g.</p><structured-macro ac:macro-id="3f36f9a1-bc84-4200-9611-e572416daf76" ac:name="code" ac:schema-version="1"><plain-text-body>ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory("vm://localhost?broker.persistent=false");
+</plain-text-body></structured-macro><p>Use the query parameters "broker.<property>" to configure the broker, where <property> matches the bean properties on the BrokerService.</p><p>The broker will be created upon creation of the first connection.</p><p>You can turn off auto creation by setting the create property on the VM Transport to false:</p><structured-macro ac:macro-id="5d37b378-935e-4ddb-872f-10e99dce2b27" ac:name="code" ac:schema-version="1"><plain-text-body>ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory("vm://localhost?create=false");
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-enable-asynchronous-sending.xml b/how-do-i-enable-asynchronous-sending.xml
index a768473..c878fb5 100644
--- a/how-do-i-enable-asynchronous-sending.xml
+++ b/how-do-i-enable-asynchronous-sending.xml
@@ -5,9 +5,7 @@
<ul><li>set the useAsyncSend property on the ActiveMQConnectionFactory</li><li>set the property using the URI when you connect to the broker</li></ul>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="44308207-4c2b-4a2a-9a3d-33831df7c467" ac:name="code" ac:schema-version="1"><plain-text-body>
tcp://localhost:61616?jms.useAsyncSend=true
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-enable-debug-logging.xml b/how-do-i-enable-debug-logging.xml
index 098ca3a..c95567b 100644
--- a/how-do-i-enable-debug-logging.xml
+++ b/how-do-i-enable-debug-logging.xml
@@ -1,12 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIenabledebuglogging-HowdoIenabledebuglogging?">How do I enable debug logging?</h2>
+<div class="wiki-content maincontent"><h2>How do I enable debug logging?</h2>
-<p>For background see <a shape="rect" href="how-do-i-change-the-logging.xml">How do I change the logging</a>.</p>
+<p>For background see <link><page ri:content-title="How do I change the logging"></page></link>.</p>
<p>You can enable debug logging in ActiveMQ by adding the following line to the <code><strong>conf/log4j.properties</strong></code> file </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c8dded93-20c3-4af9-a3bf-64b6e312f91d" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j.logger.org.apache.activemq=DEBUG
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-find-the-size-of-a-queue.xml b/how-do-i-find-the-size-of-a-queue.xml
index c5f4c35..4869196 100644
--- a/how-do-i-find-the-size-of-a-queue.xml
+++ b/how-do-i-find-the-size-of-a-queue.xml
@@ -1,10 +1,10 @@
<div class="wiki-content maincontent"><p>How do I check on the size of the queue? I know it's not JMS standard, but most JMS implementations have a way to do this.</p>
-<p>You can view the queue depth using the MBeans in ActiveMQ 5.x. Use any JMX management console to see the statistics. See <a shape="rect" href="how-can-i-monitor-activemq.xml">How can I monitor ActiveMQ</a>.</p>
+<p>You can view the queue depth using the MBeans in ActiveMQ 5.x. Use any JMX management console to see the statistics. See <link><page ri:content-title="How can I monitor ActiveMQ"></page></link>.</p>
-<p>You can also browse the contents of a queue using the JMS <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/QueueBrowser.html" rel="nofollow">QueueBrowser</a>.</p>
+<p>You can also browse the contents of a queue using the JMS <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/QueueBrowser.html">QueueBrowser</a>.</p>
-<p>Or you can access statistics <a shape="rect" href="how-can-i-see-what-destinations-are-used.xml">programmatically</a></p>
+<p>Or you can access statistics <link><page ri:content-title="How can I see what destinations are used"></page><link-body>programmatically</link-body></link></p>
<p>Through the MBeans, you can monitor individual destinations including message statistics related to the destination. For example, you'll see the following attributes on a destination (Queue or Topic):</p>
diff --git a/how-do-i-get-started-with-jms.xml b/how-do-i-get-started-with-jms.xml
index 5e209e9..fc5b877 100644
--- a/how-do-i-get-started-with-jms.xml
+++ b/how-do-i-get-started-with-jms.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIgetstartedwithJMS-HowdoIgetstartedwithJMS">How do I get started with JMS</h2>
+<div class="wiki-content maincontent"><h2>How do I get started with JMS</h2>
-<p>Your best way to get started understanding the JMS API is <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JMS.html#wp84181" rel="nofollow">Sun's JMS tutorial</a>.</p>
+<p>Your best way to get started understanding the JMS API is <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JMS.html#wp84181">Sun's JMS tutorial</a>.</p>
-<p>Alternatively you could stick to writing business level POJOs and hide the middleware via <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Apache Camel</a> which hides the JMS API from you letting you focus on your business logic via the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/bean-integration.html">Bean Integration</a> </p></div>
+<p>Alternatively you could stick to writing business level POJOs and hide the middleware via <a shape="rect" href="http://activemq.apache.org/camel/">Apache Camel</a> which hides the JMS API from you letting you focus on your business logic via the <a shape="rect" href="http://activemq.apache.org/camel/bean-integration.html">Bean Integration</a> </p></div>
diff --git a/how-do-i-make-messages-durable.xml b/how-do-i-make-messages-durable.xml
index f0e2b20..420b72c 100644
--- a/how-do-i-make-messages-durable.xml
+++ b/how-do-i-make-messages-durable.xml
@@ -1,12 +1,10 @@
<div class="wiki-content maincontent">
-<p>Durability of messages is defined by the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html" rel="nofollow">MessagerProducer</a>. You can explicitly configure the durability via the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#setDeliveryMode(int)" rel="nofollow">setDeliveryMode() method</a>. e.g.</p>
+<p>Durability of messages is defined by the <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html">MessagerProducer</a>. You can explicitly configure the durability via the <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#setDeliveryMode(int)">setDeliveryMode() method</a>. e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5ec93947-a8e0-4c38-ad32-61b5733ffee4" ac:name="code" ac:schema-version="1"><plain-text-body>
MessageProducer producer = ...;
producer.setDeliveryMode(DeliveryMode.PERSISTENT);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Note that the default is for durable messages to be used if you don't specify a delivery mode.</p></div>
diff --git a/how-do-i-preserve-order-of-messages.xml b/how-do-i-preserve-order-of-messages.xml
index df56587..358180e 100644
--- a/how-do-i-preserve-order-of-messages.xml
+++ b/how-do-i-preserve-order-of-messages.xml
@@ -2,5 +2,6 @@
<p>ActiveMQ will preserve the order of messages sent by a single producer to all consumers on a topic. If there is a single consumer on a queue then the order of messages sent by a single producer will be preserved as well.</p>
<p>If you have multiple consumers on a single queue the consumers will compete for messages and ActiveMQ will load balance across them, so order will be lost. For background on the issue and how it can be solved see</p>
-<ul><li><a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a> which allows only a single consumer to consume from the queue at once to preseve order</li><li><a shape="rect" href="message-groups.xml">Message Groups</a> which splits the messages on a queue into parallel virtual exclusive queues to ensure that messages to a single message group (defined by the JMSXGroupID header) will have their order preserved but that different groups will be load balanced to different consumers.</li></ul></div>
+<ul><li><link><page ri:content-title="Exclusive Consumer"></page></link> which allows only a single consumer to consume from the queue at once to preseve order</li><li><link><page ri:content-title="Message Groups"></page></link> which splits the messages on a queue into parallel virtual exclusive queues to ensure that messages to a single message group (defined by the JMSXGroupID header) will have their order preserved but that different groups will be load balanced to different consumers.</li></ul>
+</div>
diff --git a/how-do-i-purge-a-queue.xml b/how-do-i-purge-a-queue.xml
index a83ded2..9999e15 100644
--- a/how-do-i-purge-a-queue.xml
+++ b/how-do-i-purge-a-queue.xml
@@ -1,16 +1,17 @@
<div class="wiki-content maincontent"><p>A frequent requirement is to purge a queue (i.e. delete all the messages on it).</p>
-<h3 id="HowdoIpurgeaqueue-Solution">Solution</h3>
+<h3>Solution</h3>
-<p>You can use the <a shape="rect" href="web-console.xml">Web Console</a> to view queues, add/remove queues, purge queues or delete/forward individual messages.</p>
+<p>You can use the <link><page ri:content-title="Web Console"></page></link> to view queues, add/remove queues, purge queues or delete/forward individual messages.</p>
-<p>Another option is to use <a shape="rect" href="jmx.xml">JMX</a> to browse the queues and call the <strong>purge()</strong> method on the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/jmx/QueueViewMBean.html">QueueViewMBean</a>. </p>
+<p>Another option is to use <link><page ri:content-title="JMX"></page></link> to browse the queues and call the <strong>purge()</strong> method on the <a shape="rect" href="http://activemq.apache.org/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 shape="rect" class="external-link" 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 shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html">BrokerViewMBean</a></p>
-<p>You can also do it <a shape="rect" href="how-can-i-see-what-destinations-are-used.xml">programmatically</a></p>
+<p>You can also do it <link><page ri:content-title="How can I see what destinations are used"></page><link-body>programmatically</link-body></link></p>
-<h3 id="HowdoIpurgeaqueue-AlsoSee">Also See</h3>
+<h3>Also See</h3>
-<ul><li><a shape="rect" href="web-console.xml">Web Console</a></li><li><a shape="rect" href="jmx.xml">JMX</a></li><li><a shape="rect" href="how-do-i-find-the-size-of-a-queue.xml">How do I find the Size of a Queue</a></li><li><a shape="rect" href="how-can-i-see-what-destinations-are-used.xml">How can I see what destinations are used</a></li></ul></div>
+<ul><li><link><page ri:content-title="Web Console"></page></link></li><li><link><page ri:content-title="JMX"></page></link></li><li><link><page ri:content-title="How do I find the Size of a Queue"></page></link></li><li><link><page ri:content-title="How can I see what destinations are used"></page></link></li></ul>
+</div>
diff --git a/how-do-i-restart-embedded-broker.xml b/how-do-i-restart-embedded-broker.xml
index 7dee46e..8942db2 100644
--- a/how-do-i-restart-embedded-broker.xml
+++ b/how-do-i-restart-embedded-broker.xml
@@ -1,34 +1,29 @@
<div class="wiki-content maincontent"><p>Pure restart of the embedded broker is not advisable, since it's state could be corrupted. Therefore, you're advised to instantiate the broker again before restarting it.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-BrokerService service = BrokerFactory.createBroker("xbean:activemq.xml");
+<structured-macro ac:macro-id="83b8db39-13df-4c7d-8bd8-e959f2722bfb" ac:name="code" ac:schema-version="1"><plain-text-body>
+BrokerService service = BrokerFactory.createBroker("xbean:activemq.xml");
service.start();
service.waitUntilStarted();
service.stop();
service.waitUntilStopped();
-service = BrokerFactory.createBroker("xbean:activemq.xml");
+service = BrokerFactory.createBroker("xbean:activemq.xml");
service.start();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>In 5.3 however, we allowed the force start of the broker that has been stopped for use cases that need this functionality. You can do it by using </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2781ad46-6498-41c8-833e-8adb8bbf24ac" ac:name="code" ac:schema-version="1"><plain-text-body>
BrokerService.start(boolean force);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>method.</p>
<p>The following example demonstrates it.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-BrokerService service = BrokerFactory.createBroker("xbean:activemq.xml");
+<structured-macro ac:macro-id="708b1ca9-f8db-4529-831c-180bd947d7b0" ac:name="code" ac:schema-version="1"><plain-text-body>
+BrokerService service = BrokerFactory.createBroker("xbean:activemq.xml");
service.start();
service.waitUntilStarted();
@@ -36,8 +31,7 @@
service.waitUntilStopped();
service.start(true);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>However, it's better (more reliable) to instantiate the broker again if it is possible.</p></div>
diff --git a/how-do-i-restrict-connections-from-creating-new-queues-or-topics.xml b/how-do-i-restrict-connections-from-creating-new-queues-or-topics.xml
index 2c370ea..9eec89d 100644
--- a/how-do-i-restrict-connections-from-creating-new-queues-or-topics.xml
+++ b/how-do-i-restrict-connections-from-creating-new-queues-or-topics.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIrestrictconnectionsfromcreatingnewqueuesortopics-HowdoIrestrictconnectionsfromcreatingnewqueuesortopics?">How do I restrict connections from creating new queues or topics?</h2>
+<div class="wiki-content maincontent"><h2>How do I restrict connections from creating new queues or topics?</h2>
-<p>As is described in <a shape="rect" href="how-do-i-create-new-destinations.xml">How do I create new destinations</a> there is no need to create all the destinations up front, you can let the broker create them on the fly.</p>
+<p>As is described in <link><page ri:content-title="How do I create new destinations"></page></link> there is no need to create all the destinations up front, you can let the broker create them on the fly.</p>
-<p>However if you don't want this behaviour, or wish to restrict this behaviour to certain topic or queue <a shape="rect" href="wildcards.xml">Wildcards</a> (areas of the queue or topic name space) then you can use the <a shape="rect" href="security.xml">Security</a> plugins to disallow the <strong>admin</strong> role on whatever areas of the queue and topic namespace you wish</p></div>
+<p>However if you don't want this behaviour, or wish to restrict this behaviour to certain topic or queue <link><page ri:content-title="Wildcards"></page></link> (areas of the queue or topic name space) then you can use the <link><page ri:content-title="Security"></page></link> plugins to disallow the <strong>admin</strong> role on whatever areas of the queue and topic namespace you wish</p></div>
diff --git a/how-do-i-run-a-broker.xml b/how-do-i-run-a-broker.xml
index bc2ac33..ce2da3b 100644
--- a/how-do-i-run-a-broker.xml
+++ b/how-do-i-run-a-broker.xml
@@ -1,6 +1,6 @@
<div class="wiki-content maincontent">
-<h3 id="HowdoIrunabroker-ForActiveMQ3.x/4.x">For ActiveMQ 3.x/4.x</h3>
+<h3>For ActiveMQ 3.x/4.x</h3>
-<p>Please see the <a shape="rect" href="run-broker.xml">running a broker page</a></p></div>
+<p>Please see the <link><page ri:content-title="Run Broker"></page><link-body>running a broker page</link-body></link></p></div>
diff --git a/how-do-i-run-activemq-under-the-kaffe-jvm.xml b/how-do-i-run-activemq-under-the-kaffe-jvm.xml
index 491778d..f5f2ddf 100644
--- a/how-do-i-run-activemq-under-the-kaffe-jvm.xml
+++ b/how-do-i-run-activemq-under-the-kaffe-jvm.xml
@@ -14,25 +14,23 @@
<p>The following is the activemq.xml that was used:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="8e4c7537-d5e9-4587-9711-486889e4f14d" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<beans>
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="false" xmlns="http://activemq.org/config/1.0">
+ <broker useJmx="false" xmlns="http://activemq.org/config/1.0">
<persistenceAdapter>
- <journaledJDBC useJournal="false" dataDirectory="activemq-data"/>
+ <journaledJDBC useJournal="false" dataDirectory="activemq-data"/>
</persistenceAdapter>
<transportConnectors>
- <transportConnector name="default" uri="tcp://localhost:61616"/>
- <transportConnector name="stomp" uri="stomp://localhost:61613"/>
+ <transportConnector name="default" uri="tcp://localhost:61616"/>
+ <transportConnector name="stomp" uri="stomp://localhost:61613"/>
</transportConnectors>
</broker>
</beans>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-send-messages-to-different-destinations-from-a-single-messageproducer.xml b/how-do-i-send-messages-to-different-destinations-from-a-single-messageproducer.xml
index ff5c43b..f2be69e 100644
--- a/how-do-i-send-messages-to-different-destinations-from-a-single-messageproducer.xml
+++ b/how-do-i-send-messages-to-different-destinations-from-a-single-messageproducer.xml
@@ -1,14 +1,12 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIsendmessagestodifferentDestinationsfromasingleMessageProducer-HowdoIsendmessagestodifferentDestinationsfromasingleMessageProducer?">How do I send messages to different Destinations from a single MessageProducer?</h2>
+<div class="wiki-content maincontent"><h2>How do I send messages to different Destinations from a single MessageProducer?</h2>
<p>Create the MessageProducer using a null destination; then specify the destination each time you send...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="cfdfbd31-1bde-4d5f-aa90-0f60d4ed9759" ac:name="code" ac:schema-version="1"><plain-text-body>
MessageProducer producer = session.createProducer(null);
...
producer.send(someDestination, message);
...
producer.send(anotherDestination, message);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-set-the-message-expiration.xml b/how-do-i-set-the-message-expiration.xml
index 993ef4e..c652860 100644
--- a/how-do-i-set-the-message-expiration.xml
+++ b/how-do-i-set-the-message-expiration.xml
@@ -1,4 +1,5 @@
<div class="wiki-content maincontent"><p>JMSExpiration on a message is set by the MessageProducer in JMS - either via</p>
-<ul><li><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#setTimeToLive(long)" rel="nofollow">producer.setTimeToLive()</a></li><li><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#send(javax.jms.Destination,%20javax.jms.Message,%20int,%20int,%20long)" rel="nofollow">producer.send(Destination, Message, int, int, long)</a></li></ul></div>
+<ul><li><a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#setTimeToLive(long)">producer.setTimeToLive()</a></li><li><a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#send(javax.jms.Destination,%20javax.jms.Message,%20int,%20int,%20long)">producer.send(Destination, Message, int, int, long)</a></li></ul>
+</div>
diff --git a/how-do-i-unack-the-message-with-stomp.xml b/how-do-i-unack-the-message-with-stomp.xml
index 33b345a..18ec01d 100644
--- a/how-do-i-unack-the-message-with-stomp.xml
+++ b/how-do-i-unack-the-message-with-stomp.xml
@@ -4,54 +4,51 @@
<p>Take a look at the following example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="bd6d23fc-406a-498a-8d12-05f047cb310f" ac:name="code" ac:schema-version="1"><plain-text-body>
StompConnection connection = new StompConnection();
-connection.open("localhost", 61613);
+connection.open("localhost", 61613);
-connection.connect("system", "manager");
+connection.connect("system", "manager");
-connection.send("/queue/test", "message 1");
-connection.send("/queue/test", "message 2");
-connection.send("/queue/test", "message 3");
+connection.send("/queue/test", "message 1");
+connection.send("/queue/test", "message 2");
+connection.send("/queue/test", "message 3");
HashMap<String, String> headers = new HashMap<String, String>();
-headers.put("activemq.prefetchSize", "1");
-connection.subscribe("/queue/test", "client", headers);
+headers.put("activemq.prefetchSize", "1");
+connection.subscribe("/queue/test", "client", headers);
-connection.begin("tx1");
+connection.begin("tx1");
StompFrame frame = connection.receive();
System.out.println(frame.getBody());
-connection.ack(frame, "tx1");
-connection.abort("tx1");
+connection.ack(frame, "tx1");
+connection.abort("tx1");
-connection.begin("tx2");
-connection.ack(frame, "tx2"); //sending the ack again
+connection.begin("tx2");
+connection.ack(frame, "tx2"); //sending the ack again
frame = connection.receive();
System.out.println(frame.getBody());
-connection.ack(frame, "tx2");
-connection.commit("tx2");
+connection.ack(frame, "tx2");
+connection.commit("tx2");
-connection.begin("tx3");
+connection.begin("tx3");
frame = connection.receive();
System.out.println(frame.getBody());
-connection.ack(frame, "tx3");
-connection.commit("tx3");
-]]></script>
-</div></div>
+connection.ack(frame, "tx3");
+connection.commit("tx3");
+</plain-text-body></structured-macro>
<p>This simple application will print </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="56487b6e-0246-466b-9e13-4c366a548105" ac:name="code" ac:schema-version="1"><plain-text-body>
message 1
message 2
message 3
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Since the transaction <code>tx1</code> has been aborted, we needed to acknowledge that message again in <code>tx2</code> in order to be able to receive the next message (since the prefetch size used is 1).</p>
<p>Also take a look at these pages for more info:</p>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/stomp/stomp10/additional.html#transaction_handling">http://activemq.apache.org/stomp/stomp10/additional.html#transaction_handling</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">http://activemq.apache.org/what-is-the-prefetch-limit-for.html</a></li></ul></div>
+<ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/stomp/stomp10/additional.html#transaction_handling">http://activemq.apache.org/stomp/stomp10/additional.html#transaction_handling</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">http://activemq.apache.org/what-is-the-prefetch-limit-for.html</a></li></ul>
+</div>
diff --git a/how-do-i-use-activemq-using-in-jvm-messaging.xml b/how-do-i-use-activemq-using-in-jvm-messaging.xml
index d86df89..8f6980f 100644
--- a/how-do-i-use-activemq-using-in-jvm-messaging.xml
+++ b/how-do-i-use-activemq-using-in-jvm-messaging.xml
@@ -1,18 +1,16 @@
<div class="wiki-content maincontent">
-<h3 id="HowdoIuseActiveMQusinginJVMmessaging-ForActiveMQ3.x/4.x">For ActiveMQ 3.x/4.x</h3>
+<h3>For ActiveMQ 3.x/4.x</h3>
<p>To use pure in-memory messaging you just need to set the broker URL to be</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b3266292-d211-4cd5-b05d-8bae5faa307c" ac:name="code" ac:schema-version="1"><plain-text-body>
vm://localhost
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> </p>
<p>Actually you can use any text after <em>vm://</em> so that you can segment multiple logical JMS brokers within the same JVM and classloader, using the name to distinguish between them.</p>
-<p>There is an example of how to do this along with a description of the available protocols in the <a shape="rect" href="uri-protocols.xml">Protocols overview</a>.</p>
+<p>There is an example of how to do this along with a description of the available protocols in the <link><page ri:content-title="URI Protocols"></page><link-body>Protocols overview</link-body></link>.</p>
-<p>Also see: <a shape="rect" href="how-should-i-use-the-vm-transport.xml">how to optimise the VM transport</a></p></div>
+<p>Also see: <link><page ri:content-title="How should I use the VM transport"></page><link-body>how to optimise the VM transport</link-body></link></p></div>
diff --git a/how-do-i-use-durable-subscribers-in-a-network-of-brokers.xml b/how-do-i-use-durable-subscribers-in-a-network-of-brokers.xml
index 4082c02..bcdaaab 100644
--- a/how-do-i-use-durable-subscribers-in-a-network-of-brokers.xml
+++ b/how-do-i-use-durable-subscribers-in-a-network-of-brokers.xml
@@ -2,23 +2,21 @@
<p>For example, if you have two brokers A and B networked together in both directions to form a cluster, and a durable subscriber connects to broker B, a producer P on broker A will have its messages properly forwarded to broker B and the durable subscriber. However, if the subscriber disconnects and reconnects to broker A, any messages sent by P while the subscriber was away will be stuck on B until the subscriber reconnects to B. </p>
-<p>The solution is to use <a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a></p>
+<p>The solution is to use <link><page ri:content-title="Virtual Destinations"></page></link></p>
-<p>Virtual topics use queues under the covers and this allows ActiveMQ to treat each subscriber as a plain old Queue subscriber. This allows ActiveMQ to replay messages that have been orphaned on another broker in the cluster using this configuration as explained in the <a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a> documentation:</p>
+<p>Virtual topics use queues under the covers and this allows ActiveMQ to treat each subscriber as a plain old Queue subscriber. This allows ActiveMQ to replay messages that have been orphaned on another broker in the cluster using this configuration as explained in the <link><page ri:content-title="Networks of Brokers"></page></link> documentation:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <destinationPolicy>
+<structured-macro ac:macro-id="ce6314bd-e55b-41ec-933d-471a912c167a" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue="TEST.>" enableAudit="false">
- <conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true"/>
+ <policyEntry queue="TEST.>" enableAudit="false">
+ <conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true"/>
</policyEntry>
</policyEntries>
</policyMap>
- </destinationPolicy>]]></script>
-</div></div>
+ </destinationPolicy></plain-text-body></structured-macro>
-<p>Also, take a look at <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/usecases/VirtualTopicNetworkClusterReactivationTest.java?view=markup">this unit test to see the full configuration and usage</a></p></div>
+<p>Also, take a look at <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/usecases/VirtualTopicNetworkClusterReactivationTest.java?view=markup">this unit test to see the full configuration and usage</a></p></div>
diff --git a/how-do-i-use-ivy-with-activemq.xml b/how-do-i-use-ivy-with-activemq.xml
index 0af8af1..3574006 100644
--- a/how-do-i-use-ivy-with-activemq.xml
+++ b/how-do-i-use-ivy-with-activemq.xml
@@ -1,11 +1,10 @@
<div class="wiki-content maincontent">
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5ff6c8bd-e17a-4f67-a44d-35d367e4cfc3" ac:name="code" ac:schema-version="1"><plain-text-body>
<ivyconf>
<!--loads properties file as ivy variables, 0..n-->
- <properties file="${ivy.conf.dir}/ivyconf-file.properties" />
+ <properties file="${ivy.conf.dir}/ivyconf-file.properties" />
<!--configures ivy with some defaults, 0..1-->
- <conf defaultResolver="localChain" checkUpToDate="false" />
+ <conf defaultResolver="localChain" checkUpToDate="false" />
<!--typedef:defines new types in ivy-->
<!--latest-strategies: defines latest strategies-->
@@ -13,32 +12,31 @@
<!--defines dependency resolvers-->
<resolvers>
- <chain name="localChain" returnFirst="false">
- <filesystem name="internal" latest="latest-revision">
+ <chain name="localChain" returnFirst="false">
+ <filesystem name="internal" latest="latest-revision">
<ivy
-pattern="${repository.dir}/[organisation]/[module]/[type]s/ivy-[revision].xml" />
+pattern="${repository.dir}/[organisation]/[module]/[type]s/ivy-[revision].xml" />
<artifact
-pattern="${repository.dir}/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]" />
+pattern="${repository.dir}/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]" />
</filesystem>
- <ivyrep name="ivyrep"/>
+ <ivyrep name="ivyrep"/>
</chain>
- <ibiblio name="ibiblio"
-pattern="[organisation]/jars/[module]-[revision].[ext]"/>
+ <ibiblio name="ibiblio"
+pattern="[organisation]/jars/[module]-[revision].[ext]"/>
</resolvers>
<!--defines rules between modules and dependency resolvers-->
<modules>
- <module organisation="verticon" name=".*"
-resolver="internal" />
- <module organisation="mandarax" name=".*"
-resolver="internal" />
- <module organisation="geronimo-spec" name=".*"
-resolver="ibiblio" />
- <module organisation="tomcat" name=".*"
-resolver="ibiblio" />
+ <module organisation="verticon" name=".*"
+resolver="internal" />
+ <module organisation="mandarax" name=".*"
+resolver="internal" />
+ <module organisation="geronimo-spec" name=".*"
+resolver="ibiblio" />
+ <module organisation="tomcat" name=".*"
+resolver="ibiblio" />
</modules>
</ivyconf>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-use-jms-efficiently.xml b/how-do-i-use-jms-efficiently.xml
index a3da3cb..dbecb3a 100644
--- a/how-do-i-use-jms-efficiently.xml
+++ b/how-do-i-use-jms-efficiently.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="HowdoIuseJMSefficiently-HowdoIuseJMSefficiently?">How do I use JMS efficiently?</h2>
+<div class="wiki-content maincontent"><h2>How do I use JMS efficiently?</h2>
<p>JMS is designed for high performance. In particular its design is such that you are meant to create a number of objects up front on the startup of your application and then resuse them throughout your application. e.g. its a good idea to create upfront and then reuse the following</p>
@@ -9,26 +9,26 @@
<p>Note a little trick - you can reuse the same MessageProducer for sending messages to different destinations; just create it with a null destination and specify it on the send method.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>MessageProducer instances that are created with a null destination are anonymous producers and as such the broker cannot fire an advisory for producer when these are created. This means that when the pooled MessageProducer is in use no advisories for producers will ever be sent.</p></div></div>
+<structured-macro ac:macro-id="ccc153ab-d88c-47fe-8513-11d4a6743a3b" ac:name="info" ac:schema-version="1"><rich-text-body><p>MessageProducer instances that are created with a null destination are anonymous producers and as such the broker cannot fire an advisory for producer when these are created. This means that when the pooled MessageProducer is in use no advisories for producers will ever be sent.</p></rich-text-body></structured-macro>
-<h3 id="HowdoIuseJMSefficiently-UsingPoolingwithJMS">Using Pooling with JMS</h3>
+<h3>Using Pooling with JMS</h3>
-<p>To use JMS efficiently we recommend you use <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Camel</a> to hide the JMS API and <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/bean-integration.html">bind the messaging to your beans</a>. </p>
+<p>To use JMS efficiently we recommend you use <a shape="rect" href="http://activemq.apache.org/camel/">Camel</a> to hide the JMS API and <a shape="rect" href="http://activemq.apache.org/camel/bean-integration.html">bind the messaging to your beans</a>. </p>
-<p>Alternatively try using Spring's <a shape="rect" class="external-link" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-mdp" rel="nofollow">MessageListenerContainer</a> for consuming messages and <a shape="rect" class="external-link" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-jmstemplate" rel="nofollow">JmsTemplate</a> for sending - but be <a shape="rect" class="external-link" href="http://activemq.apache.org/jmstemplate-gotchas.html">aware of the gotchas</a></p>
+<p>Alternatively try using Spring's <a shape="rect" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-mdp">MessageListenerContainer</a> for consuming messages and <a shape="rect" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-jmstemplate">JmsTemplate</a> for sending - but be <a shape="rect" href="http://activemq.apache.org/jmstemplate-gotchas.html">aware of the gotchas</a></p>
-<h3 id="HowdoIuseJMSefficiently-Otherperformancetips">Other performance tips</h3>
+<h3>Other performance tips</h3>
<p>Also see</p>
-<ul><li><a shape="rect" href="should-i-use-transactions.xml">Should I use transactions</a></li><li><a shape="rect" href="should-i-use-xa.xml">Should I use XA</a></li></ul>
+<ul><li><link><page ri:content-title="Should I use transactions"></page></link></li><li><link><page ri:content-title="Should I use XA"></page></link></li></ul>
-<h3 id="HowdoIuseJMSefficiently-JavaConnectorArchitecture">Java Connector Architecture</h3>
+<h3>Java Connector Architecture</h3>
-<p><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/" rel="nofollow">Java Connector Architecture</a> supports the pooling of JMS connections, sessions and MessageListeners, parallel message processing, thread pooling and transaction & exception handling, through the use of a JCA <a shape="rect" href="resource-adapter.xml">Resource Adapter</a>.</p>
+<p><a shape="rect" href="http://java.sun.com/j2ee/connector/">Java Connector Architecture</a> supports the pooling of JMS connections, sessions and MessageListeners, parallel message processing, thread pooling and transaction & exception handling, through the use of a JCA <link><page ri:content-title="Resource Adapter"></page></link>.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All of these benefits are also available through Spring's MessageListenerContiner <strong>except</strong> for the XA transactions. If you need XA support then you must use JCA</p></div></div>
+<structured-macro ac:macro-id="9defc5ad-cad2-4c9b-a04d-f628a5477c2b" ac:name="info" ac:schema-version="1"><rich-text-body><p>All of these benefits are also available through Spring's MessageListenerContiner <strong>except</strong> for the XA transactions. If you need XA support then you must use JCA</p></rich-text-body></structured-macro>
-<p>Typically JCA is used in a J2EE container via MDBs; though there is a POJO Spring based <a shape="rect" href="jca-container.xml">JCA Container</a> you can use, which is simple and lightweight and easy to embed inside Tomcat or any J2SE application.</p></div>
+<p>Typically JCA is used in a J2EE container via MDBs; though there is a POJO Spring based <link><page ri:content-title="JCA Container"></page></link> you can use, which is simple and lightweight and easy to embed inside Tomcat or any J2SE application.</p></div>
diff --git a/how-do-i-use-log4j-jms-appender-with-activemq.xml b/how-do-i-use-log4j-jms-appender-with-activemq.xml
index 67dda65..8179ec5 100644
--- a/how-do-i-use-log4j-jms-appender-with-activemq.xml
+++ b/how-do-i-use-log4j-jms-appender-with-activemq.xml
@@ -1,50 +1,45 @@
-<div class="wiki-content maincontent"><p><a shape="rect" class="external-link" href="http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/net/JMSAppender.html">Log4j JMS appender</a> can be used to send your log messages to JMS broker. To use ActiveMQ as a destination of your messages, you need to configure JMS appender properly. The code sample below shows example configuration:</p>
+<div class="wiki-content maincontent"><p><a shape="rect" href="http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/net/JMSAppender.html">Log4j JMS appender</a> can be used to send your log messages to JMS broker. To use ActiveMQ as a destination of your messages, you need to configure JMS appender properly. The code sample below shows example configuration:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1e4e9cda-6e94-4f52-9920-cdafe5b54326" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j.rootLogger=INFO, stdout, jms
-## Be sure that ActiveMQ messages are not logged to 'jms' appender
+## Be sure that ActiveMQ messages are not logged to 'jms' appender
log4j.logger.org.apache.activemq=INFO, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d %-5p %c - %m%n
-## Configure 'jms' appender. You'll also need jndi.properties file in order to make it work
+## Configure 'jms' appender. You'll also need jndi.properties file in order to make it work
log4j.appender.jms=org.apache.log4j.net.JMSAppender
log4j.appender.jms.InitialContextFactoryName=org.apache.activemq.jndi.ActiveMQInitialContextFactory
log4j.appender.jms.ProviderURL=tcp://localhost:61616
log4j.appender.jms.TopicBindingName=logTopic
log4j.appender.jms.TopicConnectionFactoryBindingName=ConnectionFactory
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The important thing is not to send ActiveMQ logs to JMS appender, as it can cause errors since the broker will want to log before the connection is established. You will also need a JNDI configuration, so that appender can find appropriate topic to send log messages to. The example <code>jndi.properties</code> file can look like this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c31e68dc-dc6a-4b98-a5d0-39136b232d7d" ac:name="code" ac:schema-version="1"><plain-text-body>
topic.logTopic=logTopic
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Finally, you can subscribe to the topic and listen for log messages:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="66ba3987-6740-460b-8c38-f1c5528edcd1" ac:name="code" ac:schema-version="1"><plain-text-body>
public class Log4jJMSAppenderExample implements MessageListener {
public Log4jJMSAppenderExample() throws Exception {
// create a logTopic topic consumer
- ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory("tcp://localhost:61616");
+ ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory("tcp://localhost:61616");
Connection conn = factory.createConnection();
Session sess = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
conn.start();
- MessageConsumer consumer = sess.createConsumer(sess.createTopic("logTopic"));
+ MessageConsumer consumer = sess.createConsumer(sess.createTopic("logTopic"));
consumer.setMessageListener(this);
// log a message
Logger log = Logger.getLogger(Log4jJMSAppenderExample.class);
- log.info("Test log");
+ log.info("Test log");
// clean up
Thread.sleep(1000);
consumer.close();
@@ -61,34 +56,29 @@
try {
// receive log event in your consumer
LoggingEvent event = (LoggingEvent)((ActiveMQObjectMessage)message).getObject();
- System.out.println("Received log [" + event.getLevel() + "]: "+ event.getMessage());
+ System.out.println("Received log [" + event.getLevel() + "]: "+ event.getMessage());
} catch (Exception e) {
e.printStackTrace();
}
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Note that appender send logging event wrapped in an object message, so you can extract information such as logger name, level and of course the message.</p>
<p>Starting with ActiveMQ 5.3, this example is included in the standard distribution. You can run it by executing</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f04a5d05-04c5-4f1f-a6ba-53458c756417" ac:name="code" ac:schema-version="1"><plain-text-body>
ant log4j-jms
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>inside <code>example/</code> folder. You can expect the following output as a result:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="56c65ae1-19f4-4da9-9411-2adf43fa2cf9" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j-jms:
[echo] Running a Log4j JMS Appender example
[java] 2009-08-11 13:58:46,767 INFO Log4jJMSAppenderExample - Test log
[java] Received log [INFO]: Test log
[java] Java Result: 1
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-do-i-use-ssl.xml b/how-do-i-use-ssl.xml
index b5985e4..2643dfd 100644
--- a/how-do-i-use-ssl.xml
+++ b/how-do-i-use-ssl.xml
@@ -1,61 +1,33 @@
-<div class="wiki-content maincontent"><h3 id="HowdoIuseSSL-SettinguptheKeyandTrustStores">Setting up the Key and Trust Stores</h3><p>Also see <a shape="rect" class="external-link" href="http://jakarta.apache.org/tomcat/tomcat-5.5-doc/ssl-howto.html">Tomcat's SSL instructions</a> for more info. The following was provided by Colin Kilburn. Thanks Colin!</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">ActiveMQ uses dummy credentials by default</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>ActiveMQ includes key and trust stores that reference a dummy self signed cert. When you create a broker certificate and stores for your installation, either overwrite the values in the conf directory or delete the existing dummy key and trust stores so they cannot interfere)</p></div></div><ol><li><p>Using keytool, create a certificate for the broker:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[keytool -genkey -alias broker -keyalg RSA -keystore broker.ks
-]]></script>
-</div></div></li><li><p>Export the broker's certificate so it can be shared with clients:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[keytool -export -alias broker -keystore broker.ks -file broker_cert
-]]></script>
-</div></div></li><li><p>Create a certificate/keystore for the client:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[keytool -genkey -alias client -keyalg RSA -keystore client.ks]]></script>
-</div></div></li><li><p>Create a truststore for the client, and import the broker's certificate. This establishes that the client "trusts" the broker:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[keytool -import -alias broker -keystore client.ts -file broker_cert]]></script>
-</div></div></li></ol><h3 id="HowdoIuseSSL-StartingtheBroker">Starting the Broker</h3><h4 id="HowdoIuseSSL-Usingthejavax.net.ssl.*SystemProperties">Using the javax.net.ssl.* System Properties</h4><p>Before starting the broker's VM set the ACTIVEMQ_SSL_OPTS environment variable so that it knows to use the broker keystore.  (note that in previous versions of ActiveMQ this property was called SSL_OPTS in some scripts.  As of v5.12.0 all scripts use ACTIVEMQ_SSL_OPTS)</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[export ACTIVEMQ_SSL_OPTS = -Djavax.net.ssl.keyStore=/path/to/broker.ks -Djavax.net.ssl.keyStorePassword=password
-]]></script>
-</div></div><h4 id="HowdoIuseSSL-UsingSpringtoconfigureSSLforaBrokerinstance">Using Spring to configure SSL for a Broker instance</h4><p>Sometimes the use of javax.net.ssl.* system properties is not appropriate as they effect all SSL users in a JVM. ActiveMQ 5.2.x adds an <sslContext> element to the <amq:broker> that allows a broker specific set of SSL properties to be configured.</p><p>The SslContext <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/transport/tcp/SslContextBrokerServiceTest.java">test case</a> validates starting an SSL transport listener using the configuration specified in the broker Xbean. The SslContext element is added to the broker as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans
- <amq:broker useJmx="false" persistent="false">
+<div class="wiki-content maincontent"><h3>Setting up the Key and Trust Stores</h3><p>Also see <a shape="rect" href="http://jakarta.apache.org/tomcat/tomcat-5.5-doc/ssl-howto.html">Tomcat's SSL instructions</a> for more info. The following was provided by Colin Kilburn. Thanks Colin!</p><structured-macro ac:macro-id="976b2a51-1506-40ba-ae9d-908d1a5545b2" ac:name="info" ac:schema-version="1"><parameter ac:name="title">ActiveMQ uses dummy credentials by default</parameter><rich-text-body><p>ActiveMQ includes key and trust stores that reference a dummy self signed cert. When you create a broker certificate and stores for your installation, either overwrite the values in the conf directory or delete the existing dummy key and trust stores so they cannot interfere)</p></rich-text-body></structured-macro><ol><li><p>Using keytool, create a certificate for the broker:</p><structured-macro ac:macro-id="91038e3a-caa3-4865-9974-074b6d87c07f" ac:name="code" ac:schema-version="1"><plain-text-body>keytool -genkey -alias broker -keyalg RSA -keystore broker.ks
+</plain-text-body></structured-macro></li><li><p>Export the broker's certificate so it can be shared with clients:</p><structured-macro ac:macro-id="be4ed62e-85bb-4c7e-b02a-70b697c0d4d9" ac:name="code" ac:schema-version="1"><plain-text-body>keytool -export -alias broker -keystore broker.ks -file broker_cert
+</plain-text-body></structured-macro></li><li><p>Create a certificate/keystore for the client:</p><structured-macro ac:macro-id="d7265148-3905-4928-a608-30e11f0a2c97" ac:name="code" ac:schema-version="1"><plain-text-body>keytool -genkey -alias client -keyalg RSA -keystore client.ks</plain-text-body></structured-macro></li><li><p>Create a truststore for the client, and import the broker's certificate. This establishes that the client "trusts" the broker:</p><structured-macro ac:macro-id="e573e708-be21-4b0f-a46d-40054c5d3e5e" ac:name="code" ac:schema-version="1"><plain-text-body>keytool -import -alias broker -keystore client.ts -file broker_cert</plain-text-body></structured-macro></li></ol><h3>Starting the Broker</h3><h4>Using the javax.net.ssl.* System Properties</h4><p>Before starting the broker's VM set the ACTIVEMQ_SSL_OPTS environment variable so that it knows to use the broker keystore.  (note that in previous versions of ActiveMQ this property was called SSL_OPTS in some scripts.  As of v5.12.0 all scripts use ACTIVEMQ_SSL_OPTS)</p><structured-macro ac:macro-id="1b53f6c7-66f1-4df8-9aaa-371607cd3e5c" ac:name="code" ac:schema-version="1"><plain-text-body>export ACTIVEMQ_SSL_OPTS = -Djavax.net.ssl.keyStore=/path/to/broker.ks -Djavax.net.ssl.keyStorePassword=password
+</plain-text-body></structured-macro><h4>Using Spring to configure SSL for a Broker instance</h4><p>Sometimes the use of javax.net.ssl.* system properties is not appropriate as they effect all SSL users in a JVM. ActiveMQ 5.2.x adds an <sslContext> element to the <amq:broker> that allows a broker specific set of SSL properties to be configured.</p><p>The SslContext <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/transport/tcp/SslContextBrokerServiceTest.java">test case</a> validates starting an SSL transport listener using the configuration specified in the broker Xbean. The SslContext element is added to the broker as follows:</p><structured-macro ac:macro-id="e8315105-9b37-4739-a749-b7b7b512f6cc" ac:name="code" ac:schema-version="1"><plain-text-body><beans
+ <amq:broker useJmx="false" persistent="false">
<amq:sslContext>
<amq:sslContext
- keyStore="broker.ks" keyStorePassword="password"
- trustStore="client.ks" trustStorePassword="password"/>
+ keyStore="broker.ks" keyStorePassword="password"
+ trustStore="client.ks" trustStorePassword="password"/>
</amq:sslContext>
<amq:transportConnectors>
- <amq:transportConnector uri="ssl://localhost:61616" />
+ <amq:transportConnector uri="ssl://localhost:61616" />
</amq:transportConnectors>
</amq:broker>
</beans>
-]]></script>
-</div></div><p>The SslContext is used to configure the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/transport/tcp/SslTransportFactory.java">SslTransportFactory</a> for that broker. Full details of the configuration options available can be seen in the <a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.2-SNAPSHOT.xsd">schema definition</a> or in the accessors of <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-spring/src/main/java/org/apache/activemq/spring/SpringSslContext.java">org.apache.activemq.spring.SpringSslContext</a></p><h3 id="HowdoIuseSSL-StartingtheClient">Starting the Client</h3><p>When starting the client's VM, specify the following system properties:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[javax.net.ssl.keyStore=/path/to/client.ks
+</plain-text-body></structured-macro><p>The SslContext is used to configure the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/transport/tcp/SslTransportFactory.java">SslTransportFactory</a> for that broker. Full details of the configuration options available can be seen in the <a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.2-SNAPSHOT.xsd">schema definition</a> or in the accessors of <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-spring/src/main/java/org/apache/activemq/spring/SpringSslContext.java">org.apache.activemq.spring.SpringSslContext</a></p><h3>Starting the Client</h3><p>When starting the client's VM, specify the following system properties:</p><structured-macro ac:macro-id="a25e8ade-909a-4083-8e1d-dc35710cf62d" ac:name="code" ac:schema-version="1"><plain-text-body>javax.net.ssl.keyStore=/path/to/client.ks
javax.net.ssl.keyStorePassword=password
javax.net.ssl.trustStore=/path/to/client.ts
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>In Linux, do not use absolute path to keystore. By default, keytool uses ~/.keystore, but in some setups passing -Djavax.net.ssl.keyStore=/home/account/.keystore to Java VM does not work. This is not ActiveMQ specific but good to keep in mind anyway.</p></div></div><h3 id="HowdoIuseSSL-Clientcertificates">Client certificates</h3><p>If you want to verify client certificates, you need to take a few extra steps:</p><ol><li><p>Export the client's certificate so it can be shared with broker:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[keytool -export -alias client -keystore client.ks -file client_cert
-]]></script>
-</div></div></li><li><p>Create a truststore for the broker, and import the client's certificate. This establishes that the broker "trusts" the client:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[keytool -import -alias client -keystore broker.ts -file client_cert]]></script>
-</div></div></li><li><p>Add</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[-Djavax.net.ssl.trustStore=/path/to/broker.ts]]></script>
-</div></div><p>to ACTIVEMQ_SSL_OPTS</p></li><li><p>Instruct ActiveMQ to require client authentication by setting the following in activemq.xml:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnectors>
- <transportConnector name="ssl" uri="ssl://localhost:61617?needClientAuth=true" />
- </transportConnectors>]]></script>
-</div></div></li></ol><h3 id="HowdoIuseSSL-Certificaterevocation">Certificate revocation</h3><p>Starting with version <strong>5.12</strong>, you can define certificate revocation list (CRL) path on ssl context, so that invalid certificates can revoked</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <sslContext>
- <sslContext keyStore="org/apache/activemq/security/broker1.ks"
- keyStorePassword="password"
- trustStore="org/apache/activemq/security/activemq-revoke.jks"
- trustStorePassword="password"
- crlPath="org/apache/activemq/security/activemq-revoke.crl"/>
- </sslContext>]]></script>
-</div></div><p>This list is static and loaded on broker startup.</p><p>Starting with version <strong>5.14.0</strong>, you can also enable more advanced Online Certificate Status Protocol (OCSP) protocol. For that you need to configure a location for the<code> java.security</code> configuration extension by setting appropriate system properties (in <code>${ACTIVEMQ_HOME}/bin/env</code>) like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ACTIVEMQ_SSL_OPTS="-Djava.security.properties=$ACTIVEMQ_CONF/java.security"]]></script>
-</div></div><p>Then you need to configure OCSP responder properties in <code>java.security</code> file like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ocsp.enable=true
-ocsp.responderURL=http://ocsp.example.net:80]]></script>
-</div></div><p>A demo of the broker configuration working with OCSP responder can be found at <a shape="rect" class="external-link" href="https://github.com/dejanb/sslib" rel="nofollow">https://github.com/dejanb/sslib</a></p><h3 id="HowdoIuseSSL-WorkingAroundJava7SSLBugs">Working Around Java 7 SSL Bugs</h3><p>As noted by issue AMQ-5970, it seems some versions of Java 7 have problems with SSL sessions that need to use the Diffie-Hellman cypher suite. If you run into this issue, just copy the Bouncy Castle bcprov-jdk15on-148.jar to ActiveMQ's lib directory and restart your broker.</p><h3 id="HowdoIuseSSL-Usefullinks">Useful links</h3><p>These links might also help</p><ul><li><a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/guide/security/jsse/JSSERefGuide.html#CreateKeystore" rel="nofollow">Sun's JSSE guide</a></li><li><a shape="rect" class="external-link" href="https://search.thawte.com/support/ssl-digital-certificates/index?page=content&id=SO10061" rel="nofollow">Thawte SSL Troubleshooting Tips</a></li></ul></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="156cab22-46c8-47ee-9d80-84f5f67aaed8" ac:name="warning" ac:schema-version="1"><parameter ac:name="">Be careful on Linux</parameter><rich-text-body><p>In Linux, do not use absolute path to keystore. By default, keytool uses ~/.keystore, but in some setups passing -Djavax.net.ssl.keyStore=/home/account/.keystore to Java VM does not work. This is not ActiveMQ specific but good to keep in mind anyway.</p></rich-text-body></structured-macro><h3>Client certificates</h3><p>If you want to verify client certificates, you need to take a few extra steps:</p><ol><li><p>Export the client's certificate so it can be shared with broker:</p><structured-macro ac:macro-id="fd39bcff-a4ce-402b-871d-d0cf04657d86" ac:name="code" ac:schema-version="1"><plain-text-body>keytool -export -alias client -keystore client.ks -file client_cert
+</plain-text-body></structured-macro></li><li><p>Create a truststore for the broker, and import the client's certificate. This establishes that the broker "trusts" the client:</p><structured-macro ac:macro-id="86e24c54-d55a-4818-8d02-45f6f0f20e80" ac:name="code" ac:schema-version="1"><plain-text-body>keytool -import -alias client -keystore broker.ts -file client_cert</plain-text-body></structured-macro></li><li><p>Add</p><structured-macro ac:macro-id="6bd663bb-0dd6-4f0d-8a17-3e9f7557b781" ac:name="code" ac:schema-version="1"><plain-text-body>-Djavax.net.ssl.trustStore=/path/to/broker.ts</plain-text-body></structured-macro><p>to ACTIVEMQ_SSL_OPTS</p></li><li><p>Instruct ActiveMQ to require client authentication by setting the following in activemq.xml:</p><structured-macro ac:macro-id="552bbf90-fc3d-4452-adb1-043f39b7a36c" ac:name="code" ac:schema-version="1"><plain-text-body> <transportConnectors>
+ <transportConnector name="ssl" uri="ssl://localhost:61617?needClientAuth=true" />
+ </transportConnectors></plain-text-body></structured-macro></li></ol><h3>Certificate revocation</h3><p>Starting with version <strong>5.12</strong>, you can define certificate revocation list (CRL) path on ssl context, so that invalid certificates can revoked</p><structured-macro ac:macro-id="4711bfda-6a1d-4233-801a-0294d3b0619e" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body> <sslContext>
+ <sslContext keyStore="org/apache/activemq/security/broker1.ks"
+ keyStorePassword="password"
+ trustStore="org/apache/activemq/security/activemq-revoke.jks"
+ trustStorePassword="password"
+ crlPath="org/apache/activemq/security/activemq-revoke.crl"/>
+ </sslContext></plain-text-body></structured-macro><p>This list is static and loaded on broker startup.</p><p>Starting with version <strong>5.14.0</strong>, you can also enable more advanced Online Certificate Status Protocol (OCSP) protocol. For that you need to configure a location for the<code> java.security</code> configuration extension by setting appropriate system properties (in <code>${ACTIVEMQ_HOME}/bin/env</code>) like</p><structured-macro ac:macro-id="8d57fab2-5a8b-4204-891d-94b910374942" ac:name="code" ac:schema-version="1"><plain-text-body>ACTIVEMQ_SSL_OPTS="-Djava.security.properties=$ACTIVEMQ_CONF/java.security"</plain-text-body></structured-macro><p>Then you need to configure OCSP responder properties in <code>java.security</code> file like</p><structured-macro ac:macro-id="4da0cadd-0e98-4b9e-8001-cb66c53b8c2c" ac:name="code" ac:schema-version="1"><plain-text-body>ocsp.enable=true
+ocsp.responderURL=http://ocsp.example.net:80</plain-text-body></structured-macro><p>A demo of the broker configuration working with OCSP responder can be found at <a shape="rect" href="https://github.com/dejanb/sslib">https://github.com/dejanb/sslib</a></p><h3>Working Around Java 7 SSL Bugs</h3><p>As noted by issue AMQ-5970, it seems some versions of Java 7 have problems with SSL sessions that need to use the Diffie-Hellman cypher suite. If you run into this issue, just copy the Bouncy Castle bcprov-jdk15on-148.jar to ActiveMQ's lib directory and restart your broker.</p><h3>Useful links</h3><p>These links might also help</p><ul><li><a shape="rect" href="http://java.sun.com/j2se/1.4.2/docs/guide/security/jsse/JSSERefGuide.html#CreateKeystore">Sun's JSSE guide</a></li><li><a shape="rect" href="https://search.thawte.com/support/ssl-digital-certificates/index?page=content&id=SO10061">Thawte SSL Troubleshooting Tips</a></li></ul></div>
diff --git a/how-do-message-groups-compare-to-selectors.xml b/how-do-message-groups-compare-to-selectors.xml
index 23adaee..756a9b0 100644
--- a/how-do-message-groups-compare-to-selectors.xml
+++ b/how-do-message-groups-compare-to-selectors.xml
@@ -17,5 +17,6 @@
<ul><li>there's nothing to stop you accidentally creating 2 threads with the same selector - or 2 processes on the network starting up with the same selector and accidentally consuming from the same group of messages which completely breaks ordering; with message groups you don't have to worry about this - since it guarrentees that only 1 thread in your entire system will process messages from one group at once in order - irrespective how many consumers you start.</li></ul>
-<p>So in general; you can manually partition yourself using selectors. Message Groups however are a self-partitioning and auto-failvoer mechanism which also guarrentees that a single thread will process a specific message group at once, in order.</p></div>
+<p>So in general; you can manually partition yourself using selectors. Message Groups however are a self-partitioning and auto-failvoer mechanism which also guarrentees that a single thread will process a specific message group at once, in order.</p>
+</div>
diff --git a/how-do-multiple-transports-work.xml b/how-do-multiple-transports-work.xml
index 2ab1a3c..c7cb62a 100644
--- a/how-do-multiple-transports-work.xml
+++ b/how-do-multiple-transports-work.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<h3 id="Howdomultipletransportswork-ForActiveMQ3.x/4.x">For ActiveMQ 3.x/4.x</h3>
+<h3>For ActiveMQ 3.x/4.x</h3>
<p>The transport a client uses to connect to the broker is just the transport your client uses. So messages the broker sends to your client will be sent over that transport. However the broker can support many transports.</p>
diff --git a/how-do-transactions-work.xml b/how-do-transactions-work.xml
index 863e079..f2c8cf4 100644
--- a/how-do-transactions-work.xml
+++ b/how-do-transactions-work.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>There are two levels of transaction support in ActiveMQ:</p><ul><li>JMS Transactions - the <strong><code>commit()/</code></strong><strong><code>rollback()</code></strong> methods on a Session (which is like doing <strong><code>commit()/</code></strong><strong><code>rollback()</code></strong> on a JDBC connection)</li><li>XA Transactions - where the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/src-html/org/apache/activemq/ActiveMQXASession.html">XASession</a> acts as an <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/transaction/xa/XAResource.html" rel="nofollow">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 <strong><code>commit()</code></strong> or <strong><code>rollback()</code></strong> is called on the Session, this command is sent to the broker for it to commit or rollback the transaction.</p><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 uses <a shape="rect" class="external-link" 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. <strong><code>TransactionStore</code></strong> 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 code, take a look at <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/src-html/org/apache/activemq/store/memory/MemoryTransactionStore.html">MemoryTransactionStore</a> which proxies transactions for Memory and JDBC persistence adapters.  The only real difference with XA transactions is that at the PREPARE stage we MUST write every command we have received (the send message or acknowledge message commands) to a persistent store so that we can recover properly.</p></div>
+<div class="wiki-content maincontent"><p>There are two levels of transaction support in ActiveMQ:</p><ul><li>JMS Transactions - the <strong><code>commit()/</code></strong><strong><code>rollback()</code></strong> methods on a Session (which is like doing <strong><code>commit()/</code></strong><strong><code>rollback()</code></strong> on a JDBC connection)</li><li>XA Transactions - where the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/src-html/org/apache/activemq/ActiveMQXASession.html">XASession</a> acts as an <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/transaction/xa/XAResource.html">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 <strong><code>commit()</code></strong> or <strong><code>rollback()</code></strong> is called on the Session, this command is sent to the broker for it to commit or rollback the transaction.</p><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 uses <a shape="rect" 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. <strong><code>TransactionStore</code></strong> 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 code, take a look at <a shape="rect" href="http://activemq.apache.org/maven/apidocs/src-html/org/apache/activemq/store/memory/MemoryTransactionStore.html">MemoryTransactionStore</a> which proxies transactions for Memory and JDBC persistence adapters.  The only real difference with XA transactions is that at the PREPARE stage we MUST write every command we have received (the send message or acknowledge message commands) to a persistent store so that we can recover properly.</p></div>
diff --git a/how-does-a-queue-compare-to-a-topic.xml b/how-does-a-queue-compare-to-a-topic.xml
index 94fc25c..30167dc 100644
--- a/how-does-a-queue-compare-to-a-topic.xml
+++ b/how-does-a-queue-compare-to-a-topic.xml
@@ -1,7 +1,7 @@
-<div class="wiki-content maincontent"><h3 id="HowdoesaQueuecomparetoaTopic-Topics">Topics</h3>
+<div class="wiki-content maincontent"><h3>Topics</h3>
<p>In JMS a Topic implements <em>publish and subscribe</em> semantics. When you publish a message it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message. Only subscribers who had an active subscription at the time the broker receives the message will get a copy of the message.</p>
-<h3 id="HowdoesaQueuecomparetoaTopic-Queues">Queues</h3>
+<h3>Queues</h3>
<p>A JMS Queue implements <em>load balancer</em> semantics. A single message will be received by exactly one consumer. If there are no consumers available at the time the message is sent it will be kept until a consumer is available that can process the message. If a consumer receives a message and does not acknowledge it before closing then the message will be redelivered to another consumer. A queue can have many consumers with messages <em>load balanced</em> across the available consumers.</p>
<p>So Queues implement a reliable load balancer in JMS.</p></div>
diff --git a/how-does-activemq-compare-to-amqp.xml b/how-does-activemq-compare-to-amqp.xml
index c7be595..ec89dbc 100644
--- a/how-does-activemq-compare-to-amqp.xml
+++ b/how-does-activemq-compare-to-amqp.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><p><a shape="rect" href="amqp.xml">AMQP</a> stands for the <em>Advanced Message Queue Protocol</em> and is a specification for how messaging clients and brokers can interoperate. AMQP is a specification of a wire-level protocol for client to message broker communication. It is not a messaging system like ActiveMQ, but just a messaging protocol.</p>
+<div class="wiki-content maincontent"><p><link><page ri:content-title="AMQP"></page></link> stands for the <em>Advanced Message Queue Protocol</em> and is a specification for how messaging clients and brokers can interoperate. AMQP is a specification of a wire-level protocol for client to message broker communication. It is not a messaging system like ActiveMQ, but just a messaging protocol.</p>
<p>ActiveMQ now implements AMQP 1.0!</p>
<p>ActiveMQ also supports other open wire protocols:</p>
-<ul><li><a shape="rect" href="openwire.xml">OpenWire</a>, a fast binary format</li><li><a shape="rect" href="stomp.xml">Stomp</a>, a simple and easily implemented text based-protocol</li><li><a shape="rect" href="mqtt.xml">MQTT</a>, a compact binary format for limited devices on an unreliable network</li></ul>
+<ul><li><link><page ri:content-title="OpenWire"></page></link>, a fast binary format</li><li><link><page ri:content-title="Stomp"></page></link>, a simple and easily implemented text based-protocol</li><li><link><page ri:content-title="MQTT"></page></link>, a compact binary format for limited devices on an unreliable network</li></ul>
<p>Through these protocols, ActiveMQ can support clients in C, C++, C#, Ruby, Python, Perl, PHP, Pike etc. AMQP is most similar to OpenWire, because both OpenWire and AMQP are designed for high performance messaging, through a binary (rather than text-based) format. As a text-based format, STOMP is much easier to implement, but gives somewhat slower performance.</p></div>
diff --git a/how-does-activemq-compare-to-artemis.xml b/how-does-activemq-compare-to-artemis.xml
index 892920c..2e6c9d8 100644
--- a/how-does-activemq-compare-to-artemis.xml
+++ b/how-does-activemq-compare-to-artemis.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><a shape="rect" class="external-link" href="https://activemq.apache.org/artemis/">Artemis</a> is the codename used for the HornetQ code that was donated to the Apache Foundation.</p><p>It is possible that Artemis will eventually become the successor to ActiveMQ 5.x (and that it might eventually be branded as ActiveMQ 6.x), but no decision about that had been made as of April 2015 as documented in that month's <a shape="rect" class="external-link" href="http://activemq.apache.org/apache-activemq-board-report-201504-april.html">ActiveMQ Board Report</a>.</p></div>
+<div class="wiki-content maincontent"><p><a shape="rect" href="https://activemq.apache.org/artemis/">Artemis</a> is the codename used for the HornetQ code that was donated to the Apache Foundation.</p><p>It is possible that Artemis will eventually become the successor to ActiveMQ 5.x (and that it might eventually be branded as ActiveMQ 6.x), but no decision about that had been made as of April 2015 as documented in that month's <a shape="rect" href="http://activemq.apache.org/apache-activemq-board-report-201504-april.html">ActiveMQ Board Report</a>.</p></div>
diff --git a/how-does-activemq-compare-to-fuse-message-broker.xml b/how-does-activemq-compare-to-fuse-message-broker.xml
index dcb3d80..2d13240 100644
--- a/how-does-activemq-compare-to-fuse-message-broker.xml
+++ b/how-does-activemq-compare-to-fuse-message-broker.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><a shape="rect" class="external-link" href="http://fusesource.com/products/enterprise-activemq/" rel="nofollow">Fuse Message Broker</a> is a certified distribution of Apache ActiveMQ provided by FuseSource. <a shape="rect" class="external-link" href="http://fusesource.com" rel="nofollow">FuseSource</a> does all of its development and bug fixes as part of the Apache ActiveMQ community, so there are no functional differences between the two. FuseSource may do more frequent releases than Apache, so it is possible to get bug fixes from a Fuse Message Broker release sooner than from an official Apache ActiveMQ release.</p></div>
+<div class="wiki-content maincontent"><p><a shape="rect" href="http://fusesource.com/products/enterprise-activemq/">Fuse Message Broker</a> is a certified distribution of Apache ActiveMQ provided by FuseSource. <a shape="rect" href="http://fusesource.com">FuseSource</a> does all of its development and bug fixes as part of the Apache ActiveMQ community, so there are no functional differences between the two. FuseSource may do more frequent releases than Apache, so it is possible to get bug fixes from a Fuse Message Broker release sooner than from an official Apache ActiveMQ release.</p></div>
diff --git a/how-does-activemq-compare-to-jbossmq.xml b/how-does-activemq-compare-to-jbossmq.xml
index 8e4a806..bf6162a 100644
--- a/how-does-activemq-compare-to-jbossmq.xml
+++ b/how-does-activemq-compare-to-jbossmq.xml
@@ -1,17 +1,13 @@
-<div class="wiki-content maincontent"><p>There are some similarities between the two; they both support JMS 1.1 and run inside <a shape="rect" href="jboss-integration.xml">JBoss 4.x</a>.</p>
+<div class="wiki-content maincontent"><p>There are some similarities between the two; they both support JMS 1.1 and run inside <link><page ri:content-title="JBoss Integration"></page><link-body>JBoss 4.x</link-body></link>.</p>
<p>However ActiveMQ does offer some specific differences and advantages (at least from our perspective)</p>
-<ul><li>ActiveMQ works great in any JVM not just inside the JBoss application server</li><li>ActiveMQ comes complete with a large number of <a shape="rect" href="cross-language-clients.xml">Cross Language Clients</a></li><li>ActiveMQ supports many different <a shape="rect" href="protocols.xml">Protocols</a> such as <a shape="rect" href="ajax.xml">Ajax</a>, <a shape="rect" href="rest.xml">REST</a>, <a shape="rect" href="stomp.xml">Stomp</a>, <a shape="rect" href="openwire.xml">OpenWire</a>, <a shape="rect" href="xmpp.xml">XMPP</a></li><li>ActiveMQ supports a large number of advanced features like <a shape="rect" href="message-groups.xml">Message Groups</a>, <a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a>, <a shape="rect" href="composite-destinations.xml">Composite Destinations</a>, <a shape="rect" href="advisory-message.xml">Advisory Message</a> support</li><li>ActiveMQ supports reliable connections with <a shape="rect" href="configuring-transports.xml">configurable</a> automatic reconnection</li><li>ActiveMQ has great <a shape="rect" href="spring-support.xml">Spring Support</a></li><li>ActiveMQ supports distributed destinations across networks</li><li>ActiveMQ is very fast; often 10x faster than JBossMQ.</li></ul>
+<ul><li>ActiveMQ works great in any JVM not just inside the JBoss application server</li><li>ActiveMQ comes complete with a large number of <link><page ri:content-title="Cross Language Clients"></page></link></li><li>ActiveMQ supports many different <link><page ri:content-title="Protocols"></page></link> such as <link><page ri:content-title="Ajax"></page></link>, <link><page ri:content-title="REST"></page></link>, <link><page ri:content-title="Stomp"></page></link>, <link><page ri:content-title="OpenWire"></page></link>, <link><page ri:content-title="XMPP"></page></link></li><li>ActiveMQ supports a large number of advanced features like <link><page ri:content-title="Message Groups"></page></link>, <link><page ri:content-title="Exclusive Consumer"></page></link>, <link><page ri:content-title="Composite Destinations"></page></link>, <link><page ri:content-title="Advisory Message"></page></link> support</li><li>ActiveMQ supports reliable connections with <link><page ri:content-title="Configuring Transports"></page><link-body>configurable</link-body></link> automatic reconnection</li><li>ActiveMQ has great <link><page ri:content-title="Spring Support"></page></link></li><li>ActiveMQ supports distributed destinations across networks</li><li>ActiveMQ is very fast; often 10x faster than JBossMQ.</li></ul>
-<h2 id="HowdoesActiveMQcomparetoJBossMQ-Performanceguides">Performance guides</h2>
+<structured-macro ac:macro-id="615ae0c7-9f69-416b-a39e-2f40b2fe9130" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Performance report"></page></link></parameter></structured-macro>
-<p>If you're not convinced by performance reports then please do try running performance tests yourself. You might wanna check out our overview of <a shape="rect" href="performance.xml">Performance</a> or try using out the <a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a></p>
+<h2>More on JBoss Integration </h2>
-<p>The Commercial Providers on the <a shape="rect" href="support.xml">Support</a> page may also be able to help diagnose performance issues, suggest changes, etc...</p>
-
-<h2 id="HowdoesActiveMQcomparetoJBossMQ-MoreonJBossIntegration">More on JBoss Integration </h2>
-
-<p><a shape="rect" href="integrating-apache-activemq-with-jboss.xml">Integrating Apache ActiveMQ with JBoss</a></p></div>
+<p><link><page ri:content-title="Integrating Apache ActiveMQ with JBoss"></page></link></p></div>
diff --git a/how-does-activemq-compare-to-mantaray.xml b/how-does-activemq-compare-to-mantaray.xml
index c369376..7f5183d 100644
--- a/how-does-activemq-compare-to-mantaray.xml
+++ b/how-does-activemq-compare-to-mantaray.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><p>We are obviously biased, and will tell you "just use ActiveMQ!" <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"> But Mantaray is an OK JMS provider. The interesting thing about MantaRay is it can support a peer-based network, just as ActiveMQ does with its <a shape="rect" href="peer-transport-reference.xml">peer transport</a>.</p>
+<div class="wiki-content maincontent"><p>We are obviously biased, and will tell you "just use ActiveMQ!" <emoticon ac:name="smile"></emoticon> But Mantaray is an OK JMS provider. The interesting thing about MantaRay is it can support a peer-based network, just as ActiveMQ does with its <link><page ri:content-title="Peer Transport Reference"></page><link-body>peer transport</link-body></link>.</p>
-<p>We <a shape="rect" href="performance.xml">benchmark</a> against Mantaray and other open source JMS providers and in our tests (in which we try to be as objective as possible) ActiveMQ exhibits higher performance in most scenarios.</p>
+<p>We <link><page ri:content-title="Performance"></page><link-body>benchmark</link-body></link> against Mantaray and other open source JMS providers and in our tests (in which we try to be as objective as possible) ActiveMQ exhibits higher performance in most scenarios.</p>
<p>A peer transport can be useful when using non-persistent messaging. But if you want persistent messaging you often want to use a federated network with certain brokers on the network being the persistence brokers (so you can backup the file systems etc).</p>
-<p>The ideal topology often depends on your requirements and how you want to manage persistence and deal with hardware failures such as with <a shape="rect" href="masterslave.xml">MasterSlave</a>.</p></div>
+<p>The ideal topology often depends on your requirements and how you want to manage persistence and deal with hardware failures such as with <link><page ri:content-title="MasterSlave"></page></link>.</p></div>
diff --git a/how-does-activemq-compare-to-mule.xml b/how-does-activemq-compare-to-mule.xml
index 72ba2ef..72167d8 100644
--- a/how-does-activemq-compare-to-mule.xml
+++ b/how-does-activemq-compare-to-mule.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Apache ActiveMQ is a messaging provider, with extensive capabilities for message brokering. Mule is described as an ESB, in that it defines and executes the brokering of message exchanges among integrated software components.</p><h4 id="HowdoesActiveMQcomparetoMule-Architecture">Architecture</h4><p>Mule provides an accessible programming model for integration, designed to work well with - and leverage - other middleware technologies. For this reason, Mule does not provide a native messaging system, and it is therefore frequently used with Apache ActiveMQ.</p><p>If you use Mule to define an integration based on Apache ActiveMQ, you would use a distinct framework, (the Mule Component Model) to define interfaces for connectivity, as well as mediating activities such as transformations and exception handling. (Note that the Mule framework model presumes a SEDA process model.)Used in this manner, you could think of Mule as a library for defining the interactions among components, with the advantage that it is loosely coupled to both the integrated components and the messaging infrastructure.</p><p>If you have made the choice to use Apache ActiveMQ for messaging and such loose coupling to the messaging infrastructure is not required, you can also configure ActiveMQ directly or through the <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Apache Camel container</a>. This may give you access to message handling features not defined in the Mule framework, while still providing connectivity to non-JMS clients through ActiveMQ's numerous options for client connectivity. Working with ActiveMQ directly also allows you to take advantage of clustering and failover capabilities that lie outside the scope of the Mule Component Model.</p><h4 id="HowdoesActiveMQcomparetoMule-PointsinCommon">Points in Common</h4><p>The Mule framework is quite user-friendly, is Java-based (Mule components, called Universal Model Objects, are essentially POJOs), and is both flexible (deploys to virtually any Java environment) and lightweight (can be deployed in Spring). These are advantages that it shares with ActiveMQ, so it's not surprising that the two technologies were often used together, before the advent of <a shape="rect" class="external-link" href="http://activemq.apache.org/camel">Apache Camel</a></p><h4 id="HowdoesActiveMQcomparetoMule-"ESB"versus"Messaging"">"ESB" versus "Messaging"</h4><p>Mule supports a number of integration capabilities that go beyond the scope of messaging, such as BPEL-based orchestration and (SOAP-to-Java) Web Services support. These are rightly described as ESB features, in that they are more than what one would expect from a messaging platform alone. For environments with these requirements, Camel or Mule provides a good extension to the capabilities of ActiveMQ.</p><p>Additional ESB requirements, such as support for a distributed architecture and a native JBI container and components, are not supported by Mule. If you require these capabilities, we encourage you to investigate other open source ESBs that also integrate Apache ActiveMQ, such as <a shape="rect" class="external-link" href="http://servicemix.org/" rel="nofollow">Apache ServiceMix</a>, and even the <a shape="rect" class="external-link" href="http://incubator.apache.org/cxf/">Apache CXF</a> service framework.</p><h4 id="HowdoesActiveMQcomparetoMule-CommercialSupport,CopyrightandLicense">Commercial Support, Copyright and License</h4><p>Both Mule and ActiveMQ have commercial support available from companies dedicated to the technologies. The commercial support corporation for Mule (MuleSource) holds the copyright to Mule, and licenses it under an open source license adapted from the Mozilla Public License (an "MPL+" license). Apache ActiveMQ is an open source project at the Apache Software Foundation, and as such is available under the Apache License 2.0. Commercial support for ActiveMQ is provided by <a shape="rect" class="external-link" href="http://open.iona.com/" rel="nofollow">Iona plc</a>.</p></div>
+<div class="wiki-content maincontent"><p>Apache ActiveMQ is a messaging provider, with extensive capabilities for message brokering. Mule is described as an ESB, in that it defines and executes the brokering of message exchanges among integrated software components.</p><h4>Architecture</h4><p>Mule provides an accessible programming model for integration, designed to work well with - and leverage - other middleware technologies. For this reason, Mule does not provide a native messaging system, and it is therefore frequently used with Apache ActiveMQ.</p><p>If you use Mule to define an integration based on Apache ActiveMQ, you would use a distinct framework, (the Mule Component Model) to define interfaces for connectivity, as well as mediating activities such as transformations and exception handling. (Note that the Mule framework model presumes a SEDA process model.)Used in this manner, you could think of Mule as a library for defining the interactions among components, with the advantage that it is loosely coupled to both the integrated components and the messaging infrastructure.</p><p>If you have made the choice to use Apache ActiveMQ for messaging and such loose coupling to the messaging infrastructure is not required, you can also configure ActiveMQ directly or through the <a shape="rect" href="http://activemq.apache.org/camel/">Apache Camel container</a>. This may give you access to message handling features not defined in the Mule framework, while still providing connectivity to non-JMS clients through ActiveMQ's numerous options for client connectivity. Working with ActiveMQ directly also allows you to take advantage of clustering and failover capabilities that lie outside the scope of the Mule Component Model.</p><h4>Points in Common</h4><p>The Mule framework is quite user-friendly, is Java-based (Mule components, called Universal Model Objects, are essentially POJOs), and is both flexible (deploys to virtually any Java environment) and lightweight (can be deployed in Spring). These are advantages that it shares with ActiveMQ, so it's not surprising that the two technologies were often used together, before the advent of <a shape="rect" href="http://activemq.apache.org/camel">Apache Camel</a></p><h4>"ESB" versus "Messaging"</h4><p>Mule supports a number of integration capabilities that go beyond the scope of messaging, such as BPEL-based orchestration and (SOAP-to-Java) Web Services support. These are rightly described as ESB features, in that they are more than what one would expect from a messaging platform alone. For environments with these requirements, Camel or Mule provides a good extension to the capabilities of ActiveMQ.</p><p>Additional ESB requirements, such as support for a distributed architecture and a native JBI container and components, are not supported by Mule. If you require these capabilities, we encourage you to investigate other open source ESBs that also integrate Apache ActiveMQ, such as <a shape="rect" href="http://servicemix.org/">Apache ServiceMix</a>, and even the <a shape="rect" href="http://incubator.apache.org/cxf/">Apache CXF</a> service framework.</p><h4>Commercial Support, Copyright and License</h4><p>Both Mule and ActiveMQ have commercial support available from companies dedicated to the technologies. The commercial support corporation for Mule (MuleSource) holds the copyright to Mule, and licenses it under an open source license adapted from the Mozilla Public License (an "MPL+" license). Apache ActiveMQ is an open source project at the Apache Software Foundation, and as such is available under the Apache License 2.0. Commercial support for ActiveMQ is provided by <a shape="rect" href="http://open.iona.com/">Iona plc</a>.</p></div>
diff --git a/how-does-activemq-compare-to-spread-toolkit.xml b/how-does-activemq-compare-to-spread-toolkit.xml
index 9651be1..1770989 100644
--- a/how-does-activemq-compare-to-spread-toolkit.xml
+++ b/how-does-activemq-compare-to-spread-toolkit.xml
@@ -1,11 +1,7 @@
<div class="wiki-content maincontent">
-<p>Spread Toolkit is a C++ library for messaging and only has <a shape="rect" class="external-link" href="http://www.spread.org/JMS4Spread/docs/" rel="nofollow">partial support for JMS</a>. It doesn't support durable messaging, transactions, XA or full JMS 1.1. It is also dependent on a native code Spread daemon running on the machine.</p>
+<p>Spread Toolkit is a C++ library for messaging and only has <a shape="rect" href="http://www.spread.org/JMS4Spread/docs/">partial support for JMS</a>. It doesn't support durable messaging, transactions, XA or full JMS 1.1. It is also dependent on a native code Spread daemon running on the machine.</p>
-<p>Apache ActiveMQ on the other hand is the JMS provider used in <a shape="rect" class="external-link" href="http://geronimo.apache.org">Apache Geronimo</a> and is J2EE 1.4 certified in Geronimo and is 100% pure Java. ActiveMQ supports transient and durable messaging, transactions, XA, J2EE 1.4, JMS 1.1, JCA 1.5 as well as heaps of different features like <a shape="rect" href="message-groups.xml">Message Groups</a> and <a shape="rect" href="clustering.xml">Clustering</a></p>
+<p>Apache ActiveMQ on the other hand is the JMS provider used in <a shape="rect" href="http://geronimo.apache.org">Apache Geronimo</a> and is J2EE 1.4 certified in Geronimo and is 100% pure Java. ActiveMQ supports transient and durable messaging, transactions, XA, J2EE 1.4, JMS 1.1, JCA 1.5 as well as heaps of different features like <link><page ri:content-title="Message Groups"></page></link> and <link><page ri:content-title="Clustering"></page></link></p>
-<h2 id="HowdoesActiveMQcomparetoSpreadToolkit-Performanceguides">Performance guides</h2>
-
-<p>If you're not convinced by performance reports then please do try running performance tests yourself. You might wanna check out our overview of <a shape="rect" href="performance.xml">Performance</a> or try using out the <a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a></p>
-
-<p>The Commercial Providers on the <a shape="rect" href="support.xml">Support</a> page may also be able to help diagnose performance issues, suggest changes, etc...</p></div>
+<structured-macro ac:macro-id="3a3420b9-f796-4044-895d-6667e944d341" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Performance report"></page></link></parameter></structured-macro></div>
diff --git a/how-does-connectionfactory-relate-to-the-broker.xml b/how-does-connectionfactory-relate-to-the-broker.xml
index 8465ac1..b0137a9 100644
--- a/how-does-connectionfactory-relate-to-the-broker.xml
+++ b/how-does-connectionfactory-relate-to-the-broker.xml
@@ -1,9 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="HowdoesConnectionFactoryrelatetotheBroker-HowdoesConnectionFactoryrelatetotheBroker?">How does ConnectionFactory relate to the Broker?</h2>
+<div class="wiki-content maincontent"><h2>How does ConnectionFactory relate to the Broker?</h2>
-<p>The ConnectionFactory is a JMS specification client side interface for creating connections to a JMS broker. The Broker is a service on the network or <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">embedded in the same JVM</a> which provides the message provider. So think of the ConnectionFactory as the client API for sending and receiving messages and the broker is a server side implementation.</p>
+<p>The ConnectionFactory is a JMS specification client side interface for creating connections to a JMS broker. The Broker is a service on the network or <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><link-body>embedded in the same JVM</link-body></link> which provides the message provider. So think of the ConnectionFactory as the client API for sending and receiving messages and the broker is a server side implementation.</p>
-<h3 id="HowdoesConnectionFactoryrelatetotheBroker-SeeAlso">See Also</h3>
+<h3>See Also</h3>
-<ul><li><a shape="rect" href="how-do-i-create-new-destinations.xml">How do I create new destinations</a></li><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li><li><a shape="rect" href="what-are-administered-objects.xml">What are administered objects</a></li></ul>
+<ul><li><link><page ri:content-title="How do I create new destinations"></page></link></li><li><link><page ri:content-title="How do I embed a Broker inside a Connection"></page></link></li><li><link><page ri:content-title="What are administered objects"></page></link></li></ul>
+
</div>
diff --git a/how-does-jms-compare-with-email.xml b/how-does-jms-compare-with-email.xml
index a23fdcc..6df5b80 100644
--- a/how-does-jms-compare-with-email.xml
+++ b/how-does-jms-compare-with-email.xml
@@ -1,7 +1,7 @@
<div class="wiki-content maincontent">
<p>Certainly they both do similar things. The main difference between them is their history and design criteria. </p>
-<p>JMS has a bunch of different qualities of service (durable v non-durable, queue v topic) designed for very high performance messaging with low latency together with reliability. Email is designed for connectivitiy on the web. So they have different design trade offs. e.g. its not a big deal to get multiple copies of an email (which I get fairly often if I loose a connection with an email server over POP for example). It would be a major disaster to get 2 copies of the "remove $1000 from my bank account" messages <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>JMS has a bunch of different qualities of service (durable v non-durable, queue v topic) designed for very high performance messaging with low latency together with reliability. Email is designed for connectivitiy on the web. So they have different design trade offs. e.g. its not a big deal to get multiple copies of an email (which I get fairly often if I loose a connection with an email server over POP for example). It would be a major disaster to get 2 copies of the "remove $1000 from my bank account" messages <emoticon ac:name="smile"></emoticon></p>
<p>The main reasons for using JMS is performance (throughput & latency), together with support for transactions & XA together with avoiding duplicates and message loss.</p></div>
diff --git a/how-does-openwire-compare-to-stomp.xml b/how-does-openwire-compare-to-stomp.xml
index 8f0af69..79fe8cb 100644
--- a/how-does-openwire-compare-to-stomp.xml
+++ b/how-does-openwire-compare-to-stomp.xml
@@ -1,5 +1,5 @@
-<div class="wiki-content maincontent"><p><a shape="rect" href="openwire.xml">OpenWire</a> is the native protocol that Apache ActiveMQ uses. It is designed for performance and size on the wire - sacrificing some ease of implementation with higher performance and reduced network bandwidth as a priority. OpenWire was first released in Apache ActiveMQ 4.0.</p>
+<div class="wiki-content maincontent"><p><link><page ri:content-title="OpenWire"></page></link> is the native protocol that Apache ActiveMQ uses. It is designed for performance and size on the wire - sacrificing some ease of implementation with higher performance and reduced network bandwidth as a priority. OpenWire was first released in Apache ActiveMQ 4.0.</p>
-<p><a shape="rect" href="stomp.xml">Stomp</a> is a simpler text based protocol which is designed to be very simple to implement in a few hours in any language or platform (e.g. you can use a telnet client to communicate via Stomp). A Stomp client is not going to be as efficient as an client that uses<br clear="none">
+<p><link><page ri:content-title="Stomp"></page></link> is a simpler text based protocol which is designed to be very simple to implement in a few hours in any language or platform (e.g. you can use a telnet client to communicate via Stomp). A Stomp client is not going to be as efficient as an client that uses<br clear="none">
OpenWire, but it much simpler so you can generally be up and running with it much quicker.</p></div>
diff --git a/how-does-the-journal-work.xml b/how-does-the-journal-work.xml
index 71ae34a..b756f47 100644
--- a/how-does-the-journal-work.xml
+++ b/how-does-the-journal-work.xml
@@ -1,3 +1,3 @@
<div class="wiki-content maincontent">
-<p>See the description <a shape="rect" href="persistence.xml">here</a></p></div>
+<p>See the description <link><page ri:content-title="Persistence"></page><link-body>here</link-body></link></p></div>
diff --git a/how-does-the-website-work.xml b/how-does-the-website-work.xml
index 9d9fd7d..6e39830 100644
--- a/how-does-the-website-work.xml
+++ b/how-does-the-website-work.xml
@@ -1,9 +1,9 @@
-<div class="wiki-content maincontent"><p>This website is actually rendered from the Wiki contents that you can <a shape="rect" href="how-do-i-edit-the-website.xml">edit</a>. <br clear="none">
+<div class="wiki-content maincontent"><p>This website is actually rendered from the Wiki contents that you can <link><page ri:content-title="How do I edit the website"></page><link-body>edit</link-body></link>. <br clear="none">
When viewing a page on the static HTML website you can click on the <strong>edit</strong> link (bottom of the page) and you can edit the page. </p>
-<p>Other useful <a shape="rect" href="site.xml">Site links</a> are</p>
+<p>Other useful <link><page ri:content-title="Site"></page><link-body>Site links</link-body></link> are</p>
-<ul class="childpages-macro"><li><a shape="rect" href="banner.xml">Banner</a></li><li><a shape="rect" href="navigation.xml">Navigation</a></li><li><a shape="rect" href="quicklinks.xml">QuickLinks</a></li><li><a shape="rect" href="siteindex.xml">SiteIndex</a></li><li><a shape="rect" href="sitemap.xml">SiteMap</a></li></ul>
+<structured-macro ac:macro-id="d6f12256-015e-46f5-91b7-1ba114ec712e" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Site"></page></link></parameter></structured-macro>
<p>Note that it takes a little while to update the Apache site at <a shape="rect" class="external-link" href="http://activemq.apache.org/">http://activemq.apache.org/</a> due to caching. Though this site usually updates quickly: <a shape="rect" class="external-link" href="http://cwiki.apache.org/ACTIVEMQ/">http://cwiki.apache.org/ACTIVEMQ/</a></p></div>
diff --git a/how-does-xbean-compare-to-spring-2.xml b/how-does-xbean-compare-to-spring-2.xml
index 669ca9c..b43b187 100644
--- a/how-does-xbean-compare-to-spring-2.xml
+++ b/how-does-xbean-compare-to-spring-2.xml
@@ -1,17 +1,17 @@
-<div class="wiki-content maincontent"><p>Spring 2.0 has introduced the ability to handle custom XML languages inside the spring.xml. This is something we developed <a shape="rect" class="external-link" href="http://geronimo.apache.org/xbean/">XBean</a> for way back in the Spring 1.x days.</p>
+<div class="wiki-content maincontent"><p>Spring 2.0 has introduced the ability to handle custom XML languages inside the spring.xml. This is something we developed <a shape="rect" href="http://geronimo.apache.org/xbean/">XBean</a> for way back in the Spring 1.x days.</p>
<p>The Spring hook requires component developers to write their own XML handling, processing DOMs and so forth. On various projects like ActiveMQ, Jencks, Jetty, ServiceMix, XFire - we didn't want to have to spend time hand-crafting parsing of XML code. So XBean is used to auto-create the parsing code along with an XSD and reference documentation for how to configure these services in custom XML languages.</p>
<p>So you can think of XBean as being like a JAXB2 tool for working inside Spring XML files</p>
-<h3 id="HowdoesXBeancomparetoSpring2-Springversionssupported">Spring versions supported</h3>
+<h3>Spring versions supported</h3>
<p>So you can use XBean in Spring 1.x or Spring 2.x (for Spring 2.0 support you need XBean 2.6 or later along with the matching release of ActiveMQ).</p>
<p>If you are using Spring 1.x you use the XBean versions of the Spring ApplicationContext classes. In Spring 2.0 the XBean functionality works perfectly fine inside a regular spring.xml file. The only main difference between using the XBean ApplicationContext files and the Spring ones is that the Spring ones mandate validation, so your XML must include all the XSD information (which is handy for IDE completion anyway) whereas this is not mandatory in the XBean configuraiton files.</p>
-<h3 id="HowdoesXBeancomparetoSpring2-Examples">Examples</h3>
+<h3>Examples</h3>
<p>Here's a regular Spring 2 XML file using ActiveMQ's XML inside it to configure a broker & destinations & a connection factory</p>
diff --git a/how-fast-is-activemq.xml b/how-fast-is-activemq.xml
index b51ea90..4d2e421 100644
--- a/how-fast-is-activemq.xml
+++ b/how-fast-is-activemq.xml
@@ -1,10 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="HowfastisActiveMQ-HowfastisActiveMQ?">How fast is ActiveMQ?</h2>
+<div class="wiki-content maincontent"><h2>How fast is ActiveMQ?</h2>
-<p>It all depends on the configuration, the operating system, hardware, JVM, JVM configuration and what you're doing. For more details see <a shape="rect" href="performance.xml">Performance</a></p>
+<p>It all depends on the configuration, the operating system, hardware, JVM, JVM configuration and what you're doing. For more details see <link><page ri:content-title="Performance"></page></link></p>
-<h2 id="HowfastisActiveMQ-Performanceguides">Performance guides</h2>
-
-<p>If you're not convinced by performance reports then please do try running performance tests yourself. You might wanna check out our overview of <a shape="rect" href="performance.xml">Performance</a> or try using out the <a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a></p>
-
-<p>The Commercial Providers on the <a shape="rect" href="support.xml">Support</a> page may also be able to help diagnose performance issues, suggest changes, etc...</p></div>
+<structured-macro ac:macro-id="47f7b2f3-f9ea-4700-bec0-7e30bf92562a" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Performance report"></page></link></parameter></structured-macro></div>
diff --git a/how-lightweight-is-sending-a-message.xml b/how-lightweight-is-sending-a-message.xml
index 7a9cfdd..8eda934 100644
--- a/how-lightweight-is-sending-a-message.xml
+++ b/how-lightweight-is-sending-a-message.xml
@@ -1,12 +1,12 @@
<div class="wiki-content maincontent">
-<h3 id="Howlightweightissendingamessage-ForActiveMQ3.x/4.x">For ActiveMQ 3.x/4.x</h3>
+<h3>For ActiveMQ 3.x/4.x</h3>
-<p>It depends <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>It depends <emoticon ac:name="smile"></emoticon></p>
<p>If you are in a JMS transaction, are using non-durable messaging then its fairly lightweight and fast - typically just blocking until the message has got onto the socket buffer. Though if you are using durable messaging and not using JMS transactions then by default we will perform a blocking request-response with the broker to ensure the message is persisted to disk by the time the call to send() is complete - which is pretty slow.</p>
-<p>However if you really want it to be very lightweight and fast, <a shape="rect" href="configuring-transports.xml">enable async sending</a> on your JMS connection.</p>
+<p>However if you really want it to be very lightweight and fast, <link><page ri:content-title="Configuring Transports"></page><link-body>enable async sending</link-body></link> on your JMS connection.</p>
<p>If you really want low latency, such as in a GUI thread or very high performance server, you probably want to enable asynchronous sending. The only downside of asynchronous sending is if the send fails for whatever reason (security exception typically or some transport failure), then you don't get an exception thrown in the sender thread, since all the work is done asynchronously, though your ErrorListener will get notified.</p>
diff --git a/how-should-i-implement-request-response-with-jms.xml b/how-should-i-implement-request-response-with-jms.xml
index bd87e5d..2e91e5e 100644
--- a/how-should-i-implement-request-response-with-jms.xml
+++ b/how-should-i-implement-request-response-with-jms.xml
@@ -1,31 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="HowshouldIimplementrequestresponsewithJMS-HowshouldIimplementrequestresponsewithJMS?">How should I implement request response with JMS?</h2>
+<div class="wiki-content maincontent"><h2>How should I implement request response with JMS?</h2>
-<p>The simplest solution is to use <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/spring-remoting.html">Camel as a Spring Remoting provider</a> which allows you to hide all the JMS API from your business logic and letting Camel provide the request/response handling code for you.</p>
+<p>The simplest solution is to use <a shape="rect" href="http://activemq.apache.org/camel/spring-remoting.html">Camel as a Spring Remoting provider</a> which allows you to hide all the JMS API from your business logic and letting Camel provide the request/response handling code for you.</p>
<p>However if you wish to write the JMS client code yourself, please read on how it works...</p>
-<h3 id="HowshouldIimplementrequestresponsewithJMS-UsingtheJMSAPItoimplementrequest-response">Using the JMS API to implement request-response</h3>
+<h3>Using the JMS API to implement request-response</h3>
<p>You might think at first that to implement request-response type operations in JMS that you should create a new consumer with a selector per request; or maybe create a new temporary queue per request.</p>
<p>Creating temporary destinations, consumers, producers and connections are all synchronous request-response operations with the broker and so should be avoided for processing each request as it results in lots of chat with the JMS broker.</p>
-<p>The best way to implement request-response over JMS is to create a temporary queue and consumer per client on startup, set JMSReplyTo property on each message to the temporary queue and then use a <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html#setJMSCorrelationID(java.lang.String)" rel="nofollow">correlationID on each message</a> to correlate request messages to response messages. This avoids the overhead of creating and closing a consumer for each request (which is expensive). It also means you can share the same producer & consumer across many threads if you want (or pool them maybe).</p>
+<p>The best way to implement request-response over JMS is to create a temporary queue and consumer per client on startup, set JMSReplyTo property on each message to the temporary queue and then use a <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html#setJMSCorrelationID(java.lang.String)">correlationID on each message</a> to correlate request messages to response messages. This avoids the overhead of creating and closing a consumer for each request (which is expensive). It also means you can share the same producer & consumer across many threads if you want (or pool them maybe).</p>
-<p>The <a shape="rect" class="external-link" href="http://lingo.codehaus.org/" rel="nofollow">Lingo library</a> is an implementation of Spring remoting using JMS. (Spring remoting is a kind of POJO based remoting where the remoting code is invisible to your business logic code).</p>
+<p>The <a shape="rect" href="http://lingo.codehaus.org/">Lingo library</a> is an implementation of Spring remoting using JMS. (Spring remoting is a kind of POJO based remoting where the remoting code is invisible to your business logic code).</p>
<p>It uses exactly this pattern; of using correlation IDs to correlate requests to responses. The server side just has to remember to put the inbound message's correlation ID on the response.</p>
-<p>The actual class which does this is the <a shape="rect" class="external-link" href="http://lingo.codehaus.org/maven/apidocs/org/logicblaze/lingo/jms/impl/MultiplexingRequestor.html" rel="nofollow">MultiplexingRequestor</a> . It may be just using Spring remoting with Lingo is the simplest way of implementing request response - or maybe you could just use Lingo's <a shape="rect" class="external-link" href="http://lingo.codehaus.org/maven/apidocs/org/logicblaze/lingo/jms/Requestor.html" rel="nofollow">Requestor</a> interface to keep the JMS semantics.</p>
+<p>The actual class which does this is the <a shape="rect" href="http://lingo.codehaus.org/maven/apidocs/org/logicblaze/lingo/jms/impl/MultiplexingRequestor.html">MultiplexingRequestor</a> . It may be just using Spring remoting with Lingo is the simplest way of implementing request response - or maybe you could just use Lingo's <a shape="rect" href="http://lingo.codehaus.org/maven/apidocs/org/logicblaze/lingo/jms/Requestor.html">Requestor</a> interface to keep the JMS semantics.</p>
-<p>More details <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/LINGO/Request+Response+with+JMS" rel="nofollow">here</a></p>
+<p>More details <a shape="rect" href="http://docs.codehaus.org/display/LINGO/Request+Response+with+JMS">here</a></p>
-<h3 id="HowshouldIimplementrequestresponsewithJMS-Clientside">Client side</h3>
+<h3>Client side</h3>
<p>So the client side creates a consumer on a temporary queue as follows...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e5020b3a-4e69-470a-b610-ea3fbee197fb" ac:name="code" ac:schema-version="1"><plain-text-body>
// client side
Destination tempDest = session.createTemporaryQueue();
MessageConsumer responseConsumer = session.createConsumer(tempDest);
@@ -36,13 +35,11 @@
message.setJMSCorrelationID(myCorrelationID);
producer.send(message);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="HowshouldIimplementrequestresponsewithJMS-Serverside">Server side</h3>
+<h3>Server side</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="785c40c9-dacb-477c-b52b-d6cf5a93efdd" ac:name="code" ac:schema-version="1"><plain-text-body>
public void onMessage(Message request) {
Message response = session.createMessage();
@@ -50,15 +47,13 @@
producer.send(request.getJMSReplyTo(), response)
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="HowshouldIimplementrequestresponsewithJMS-FullExamples">Full Examples</h2>
+<h2>Full Examples</h2>
-<h3 id="HowshouldIimplementrequestresponsewithJMS-ServerSide">Server Side</h3>
+<h3>Server Side</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c70ef9de-68d0-4a3f-914d-a38cd43b1119" ac:name="code" ac:schema-version="1"><parameter ac:name="type">java</parameter><plain-text-body>
import org.apache.activemq.broker.BrokerService;
import org.apache.activemq.ActiveMQConnectionFactory;
@@ -75,8 +70,8 @@
private MessageProtocol messageProtocol;
static {
- messageBrokerUrl = "tcp://localhost:61616";
- messageQueueName = "client.messages";
+ messageBrokerUrl = "tcp://localhost:61616";
+ messageQueueName = "client.messages";
ackMode = Session.AUTO_ACKNOWLEDGE;
}
@@ -146,13 +141,11 @@
new Server();
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="HowshouldIimplementrequestresponsewithJMS-ClientSide">Client Side</h3>
+<h3>Client Side</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a2819c9c-22b8-449b-b6d3-1938be462d9e" ac:name="code" ac:schema-version="1"><parameter ac:name="type">java</parameter><plain-text-body>
import org.apache.activemq.ActiveMQConnectionFactory;
import javax.jms.*;
@@ -166,12 +159,12 @@
private MessageProducer producer;
static {
- clientQueueName = "client.messages";
+ clientQueueName = "client.messages";
ackMode = Session.AUTO_ACKNOWLEDGE;
}
public Client() {
- ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
+ ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
Connection connection;
try {
connection = connectionFactory.createConnection();
@@ -194,7 +187,7 @@
//Now create the actual message you want to send
TextMessage txtMessage = session.createTextMessage();
- txtMessage.setText("MyProtocolMessage");
+ txtMessage.setText("MyProtocolMessage");
//Set the reply to field to the temp queue you created above, this is the queue the server
//will respond to
@@ -225,7 +218,7 @@
if (message instanceof TextMessage) {
TextMessage textMessage = (TextMessage) message;
messageText = textMessage.getText();
- System.out.println("messageText = " + messageText);
+ System.out.println("messageText = " + messageText);
}
} catch (JMSException e) {
//Handle the exception appropriately
@@ -236,27 +229,24 @@
new Client();
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="HowshouldIimplementrequestresponsewithJMS-ProtocolClass">Protocol Class</h3>
+<h3>Protocol Class</h3>
<p>This class is needed to run the client/server example above. Delegating the handling of messages to a seperate class is solely a personal preference.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="03110497-2192-42aa-b217-ccd1d89e36e2" ac:name="code" ac:schema-version="1"><parameter ac:name="type">java</parameter><plain-text-body>
public class MessageProtocol {
public String handleProtocolMessage(String messageText) {
String responseText;
- if ("MyProtocolMessage".equalsIgnoreCase(messageText)) {
- responseText = "I recognize your protocol message";
+ if ("MyProtocolMessage".equalsIgnoreCase(messageText)) {
+ responseText = "I recognize your protocol message";
} else {
- responseText = "Unknown protocol message: " + messageText;
+ responseText = "Unknown protocol message: " + messageText;
}
return responseText;
}
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/how-should-i-package-applications-using-camel-and-activemq.xml b/how-should-i-package-applications-using-camel-and-activemq.xml
index 74759d9..98bb981 100644
--- a/how-should-i-package-applications-using-camel-and-activemq.xml
+++ b/how-should-i-package-applications-using-camel-and-activemq.xml
@@ -1,12 +1,13 @@
-<div class="wiki-content maincontent"><h2 id="HowshouldIpackageapplicationsusingCamelandActiveMQ-HowshouldIpackageapplicationsusingCamelandActiveMQ">How should I package applications using Camel and ActiveMQ</h2>
+<div class="wiki-content maincontent"><h2>How should I package applications using Camel and ActiveMQ</h2>
-<p>So you may wish to use Camel's <a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> inside the ActiveMQ Broker. In which case the stand alone broker is already packaged to work with Camel out of the box; just add your EIP routing rules to ActiveMQ's <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> like the example routing rule which ships with ActiveMQ 5.x or later. If you want to include some Java routing rules, then just add your jar to somewhere inside ActiveMQ's lib directory.</p>
+<p>So you may wish to use Camel's <link><page ri:content-title="Enterprise Integration Patterns"></page></link> inside the ActiveMQ Broker. In which case the stand alone broker is already packaged to work with Camel out of the box; just add your EIP routing rules to ActiveMQ's <link><page ri:content-title="Xml Configuration"></page></link> like the example routing rule which ships with ActiveMQ 5.x or later. If you want to include some Java routing rules, then just add your jar to somewhere inside ActiveMQ's lib directory.</p>
<p>If you wish to use ActiveMQ and/or Camel in a standalone application, we recommend you just create a normal Spring application; then add the necessary jars and customise the Spring XML and you're good to go.</p>
-<h3 id="HowshouldIpackageapplicationsusingCamelandActiveMQ-WhatjarsdoIneed">What jars do I need</h3>
+<h3>What jars do I need</h3>
-<ul><li><a shape="rect" href="initial-configuration.xml">what jars are required for ActiveMQ</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/camel/what-jars-do-i-need.html">what jars are required for Camel</a></li></ul>
+<ul><li><link><page ri:content-title="Initial Configuration"></page><link-body>what jars are required for ActiveMQ</link-body></link></li><li><a shape="rect" href="http://activemq.apache.org/camel/what-jars-do-i-need.html">what jars are required for Camel</a></li></ul>
+
</div>
diff --git a/how-should-i-use-the-vm-transport.xml b/how-should-i-use-the-vm-transport.xml
index ae26596..df7fdcd 100644
--- a/how-should-i-use-the-vm-transport.xml
+++ b/how-should-i-use-the-vm-transport.xml
@@ -1,30 +1,28 @@
<div class="wiki-content maincontent">
-<h3 id="HowshouldIusetheVMtransport-ForActiveMQ3.x/4.x">For ActiveMQ 3.x/4.x</h3>
+<h3>For ActiveMQ 3.x/4.x</h3>
-<p><a shape="rect" href="how-do-i-use-activemq-using-in-jvm-messaging.xml">Using the VM transport</a> to connect to an in-JVM broker is the fastest and most efficient transport you can use.</p>
+<p><link><page ri:content-title="How do I use ActiveMQ using in JVM messaging"></page><link-body>Using the VM transport</link-body></link> to connect to an in-JVM broker is the fastest and most efficient transport you can use.</p>
<p>This is because by default there is no serialization to a socket or operating system socket resources used up; its purely an in-JVM List used to exchange messages with clients and the broker. Sometimes you want the VM transport to work as an async SEDA queue; other times you want to inline the processing so that there are less thread context switches which can improve throughput in high performance scenarios.</p>
<p>One thing to note with the VM transport is that messages are passed by reference. One slight exception to this is the JMS ObjectMessage. (see below for details on how to disable it in ActiveMQ 4.x)</p>
<p> You can also further optimise things by setting the <strong>copyMessageOnSend</strong> property to be false; which avoids making a copy of the ObjectMessage to send; though this assumes that you don't try and resuse the ObjectMessage instance; you just create it once and send it once and don't try and change the body of the message after sending it.</p>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Be careful of ClassLoaders</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Note that you should only perform the above optimisation if all the producers and consumers are in a compatible class loader. For example if you have 2 WARs with their own jars which are sending messages to each other, you could get strange ClassCastExceptions occuring due to the same class being loaded in each class loader; so sometimes serializing ObjectMessage is a good thing to avoid ClassPath hell - so only perform the above optimisation if you are sure you're ClassPaths are OK</p></div></div>
+<structured-macro ac:macro-id="86215832-e59d-4c91-a3d4-21bf38859198" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Be careful of ClassLoaders</parameter><rich-text-body>
+<p>Note that you should only perform the above optimisation if all the producers and consumers are in a compatible class loader. For example if you have 2 WARs with their own jars which are sending messages to each other, you could get strange ClassCastExceptions occuring due to the same class being loaded in each class loader; so sometimes serializing ObjectMessage is a good thing to avoid ClassPath hell - so only perform the above optimisation if you are sure you're ClassPaths are OK</p></rich-text-body></structured-macro>
-<h3 id="HowshouldIusetheVMtransport-DisablingObjectserializationwithObjectMessageforActiveMQ4.x">Disabling Object serialization with ObjectMessage for ActiveMQ 4.x</h3>
+<h3>Disabling Object serialization with ObjectMessage for ActiveMQ 4.x</h3>
<p>The JMS specification dictates that the body of an ObjectMessage must be serialized when you call send() to avoid the object changing under your feet affecting what view the consumer sees of the object.</p>
<p>You can disable the automatic serialization of ObjectMessage payloads so that the objects are passed by value in 4.x by setting the <strong>objectMessageSerializationDefered</strong> flag to true on the ActiveMQConnectionFactory (or ActiveMQConnection).</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory("vm://localhost");
+<structured-macro ac:macro-id="95dfa68c-f295-45ed-8a8f-1c45802a06f5" ac:name="code" ac:schema-version="1"><plain-text-body>
+ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory("vm://localhost");
factory.setObjectMessageSerializationDefered(true);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> </p>
<p> </p>
diff --git a/how-to-become-a-committer-on-the-activemq-project.xml b/how-to-become-a-committer-on-the-activemq-project.xml
index 42eb9ff..a862d0b 100644
--- a/how-to-become-a-committer-on-the-activemq-project.xml
+++ b/how-to-become-a-committer-on-the-activemq-project.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="HowtoBecomeaCommitterontheActiveMQProject-HowtoBecomeaCommitterontheActiveMQProject">How to Become a Committer on the ActiveMQ Project</h1><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><span>This page is under active development so the ideas here are very fluid right now.</span></p></div></div><p><span style="line-height: 1.4285715;">As outlined on <a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How It Works document</a> and the </span><a shape="rect" class="external-link" href="https://www.apache.org/foundation/how-it-works.html#roles" style="line-height: 1.4285715;">ASF roles</a> defined there, we want to actively<span style="line-height: 1.4285715;"> </span><span style="line-height: 1.4285715;"> encourage folks to move from being contributors to the ActiveMQ TLP toward becoming full-fledged committers on the project. </span><span style="line-height: 1.4285715;">In an effort to provide more transparency on what it takes to become a committer on the ActiveMQ project, we are assembling our thoughts here. </span><span style="line-height: 1.4285715;">As we work through the identification of the skills and values we feel are necessary to become a committer on the ActiveMQ project, we should continue to discuss our thoughts on the dev@activemq mailing list so that everyone is able to participate. </span></p><p>Below is the list of some of the guidelines we believe make up a good candidate for being offered committership:</p><p> </p><ul><li>Demonstrated ability to contribute patches/pull requests to ActiveMQ projects </li><li>Demonstrated participation in discussions on the ActiveMQ mailing lists </li><li>Willingness to contribute to the documentation</li><li>Willingness to mentor and be mentored</li><li>Helping to promote the community and this project, including outside of Apache</li><li>Sustained interest and contribution</li></ul></div>
+<div class="wiki-content maincontent"><h1>How to Become a Committer on the ActiveMQ Project</h1><structured-macro ac:macro-id="e493ce13-fb9f-4f9f-a147-09caf854f661" ac:name="warning" ac:schema-version="1"><rich-text-body><p><span>This page is under active development so the ideas here are very fluid right now.</span></p></rich-text-body></structured-macro><p><span style="line-height: 1.4285715;">As outlined on <a shape="rect" href="http://www.apache.org/foundation/how-it-works.html">How It Works document</a> and the </span><a shape="rect" href="https://www.apache.org/foundation/how-it-works.html#roles" style="line-height: 1.4285715;">ASF roles</a> defined there, we want to actively<span style="line-height: 1.4285715;"> </span><span style="line-height: 1.4285715;"> encourage folks to move from being contributors to the ActiveMQ TLP toward becoming full-fledged committers on the project. </span><span style="line-height: 1.4285715;">In an effort to provide more transparency on what it takes to become a committer on the ActiveMQ project, we are assembling our thoughts here. </span><span style="line-height: 1.4285715;">As we work through the identification of the skills and values we feel are necessary to become a committer on the ActiveMQ project, we should continue to discuss our thoughts on the dev@activemq mailing list so that everyone is able to participate. </span></p><p>Below is the list of some of the guidelines we believe make up a good candidate for being offered committership:</p><p> </p><ul><li>Demonstrated ability to contribute patches/pull requests to ActiveMQ projects </li><li>Demonstrated participation in discussions on the ActiveMQ mailing lists </li><li>Willingness to contribute to the documentation</li><li>Willingness to mentor and be mentored</li><li>Helping to promote the community and this project, including outside of Apache</li><li>Sustained interest and contribution</li></ul></div>
diff --git a/how-to-configure-a-new-database.xml b/how-to-configure-a-new-database.xml
index c7c3142..f09d1c2 100644
--- a/how-to-configure-a-new-database.xml
+++ b/how-to-configure-a-new-database.xml
@@ -5,41 +5,37 @@
<p>e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
- <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
- <property name="url" value="jdbc:mysql://localhost/activemq"/>
- <property name="username" value="activemq"/>
- <property name="password" value="activemq"/>
- <property name="poolPreparedStatements" value="true"/>
+<structured-macro ac:macro-id="8c9473ba-d5ec-4a14-b9dc-dcefecdec2c2" ac:name="code" ac:schema-version="1"><plain-text-body>
+ <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
+ <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
+ <property name="url" value="jdbc:mysql://localhost/activemq"/>
+ <property name="username" value="activemq"/>
+ <property name="password" value="activemq"/>
+ <property name="poolPreparedStatements" value="true"/>
</bean>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p><strong>For AMQ 3.x</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<bean id="mssql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
- <property name="driverClassName">
+<structured-macro ac:macro-id="3423b393-7e75-4fe6-baf4-6d8d7d26dc7e" ac:name="code" ac:schema-version="1"><plain-text-body>
+<bean id="mssql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
+ <property name="driverClassName">
<value>com.microsoft.jdbc.sqlserver.SQLServerDriver</value>
</property>
- <property name="url">
+ <property name="url">
<value>jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=activedb</value>
</property>
- <property name="username">
+ <property name="username">
<value>sa</value>
</property>
- <property name="password">
+ <property name="password">
<value></value>
</property>
- <property name="poolPreparedStatements">
+ <property name="poolPreparedStatements">
<value>true</value>
</property>
</bean>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>2. Set the datasource reference to use the new jdbc configuration e.g <jdbcPersistence dataSourceRef="mssql-ds"/></p>
<p>3. Place the jdbc driver in the directory "activemq_home/lib/optional".</p></div>
diff --git a/how-to-deal-with-large-number-of-threads-in-clients.xml b/how-to-deal-with-large-number-of-threads-in-clients.xml
index a3b7fa7..3b36146 100644
--- a/how-to-deal-with-large-number-of-threads-in-clients.xml
+++ b/how-to-deal-with-large-number-of-threads-in-clients.xml
@@ -1,33 +1,27 @@
-<div class="wiki-content maincontent"><p>If you study thread allocation in ActiveMQ clients, you'll notice that by default there is one thread allocated by every session. This basically means that session will use its <a shape="rect" class="external-link" href="http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html" rel="nofollow">ThreadPoolExecutor</a> to execute its tasks. Up until version 5.7 this executor was unbound which could lead to OOM problems in rare case where are a large number of busy sessions in the same JVM could cause uncontrollable spikes in thread creation. </p>
+<div class="wiki-content maincontent"><p>If you study thread allocation in ActiveMQ clients, you'll notice that by default there is one thread allocated by every session. This basically means that session will use its <a shape="rect" href="http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html">ThreadPoolExecutor</a> to execute its tasks. Up until version 5.7 this executor was unbound which could lead to OOM problems in rare case where are a large number of busy sessions in the same JVM could cause uncontrollable spikes in thread creation. </p>
<p>In 5.7 we bounded this executor to a maximum of 1000 threads by default, which we believe should be enough for most use cases. In case of large number of busy sessions, each of them could end up using large number of threads and eventually OOM your application. There are couple of things you can do. The first obvious thing is to decrease the max thread limit a session can use, like this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
+<structured-macro ac:macro-id="1bc48d77-6421-4fdb-ab92-c96802229184" ac:name="code" ac:schema-version="1"><plain-text-body>ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
connectionFactory.setMaxThreadPoolSize(10);
Connection conn = connectionFactory.createConnection();
-conn.start();]]></script>
-</div></div>
+conn.start();</plain-text-body></structured-macro>
<p>On the other hand this can lead to the scenario where a single session exaust its max thread number. A default behavior of <code>ThreadPoolExecutor</code> in this case is to throw an exception, so you'll notice it. A workaround for this scenario is to provide a rejected task handler that will synchronize the execution with the calling thread, like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
+<structured-macro ac:macro-id="b9389b13-20a8-4080-aafe-1fa75119999c" ac:name="code" ac:schema-version="1"><plain-text-body>ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
connectionFactory.setRejectedTaskHandler(new ThreadPoolExecutor.CallerRunsPolicy());
Connection conn = connectionFactory.createConnection();
-conn.start();]]></script>
-</div></div>
+conn.start();</plain-text-body></structured-macro>
<p>This will prevent the <code>ThreadPoolExecutor</code> from throwing an exception when it reaches its bound. Instead it will execute the rejected task in the calling thread.</p>
<p>Finally, you can eliminate these threads completly, you can do that by setting <code>alwaysSessionAsync</code> property to false</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
+<structured-macro ac:macro-id="707b37e8-ac2b-487b-be52-ebf66d194721" ac:name="code" ac:schema-version="1"><plain-text-body>ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
connectionFactory.setAlwaysSessionAsync(false);
Connection conn = connectionFactory.createConnection();
-conn.start();]]></script>
-</div></div>
+conn.start();</plain-text-body></structured-macro>
<p>However you need to have in mind that this approach can affect performance of the whole system.</p>
diff --git a/how-to-deploy-activemq-ra-versionrar-to-weblogic.xml b/how-to-deploy-activemq-ra-versionrar-to-weblogic.xml
index fd11756..62494e8 100644
--- a/how-to-deploy-activemq-ra-versionrar-to-weblogic.xml
+++ b/how-to-deploy-activemq-ra-versionrar-to-weblogic.xml
@@ -1,12 +1,11 @@
<div class="wiki-content maincontent">
-<h3 id="Howtodeployactivemq-ra-version.rartoweblogic-ThisisaguideonhowtodeployActiveMQ'sresouceadaptertoweblogic9.1.">This is a guide on how to deploy ActiveMQ's resouce adapter to weblogic 9.1.</h3>
+<h3>This is a guide on how to deploy ActiveMQ's resouce adapter to weblogic 9.1.</h3>
<ol><li>Create a new domain in weblogic using the configuration wizard (Start menu BEA Products -> Tools -> configuration Wizard ).</li><li>Add the jar dependencies (these are the jars inside the rar file..for some reason weblogic is not loading these from the rar file)  in the classpath . One way to do this is by dropping the jars in the lib directory of the domain (<%BEA_HOME%>\user_projects\domains\<%DOMAIN_NAME%>\lib). </li></ol>
<ol><li>Add the BrokerXmlConfig file called "broker-config.xml" in the classpath. This can be found in the rar file "activemq-rar-*.rar". Otherwise, modify ra.xml by providing an absolute path to "broker-config.xml", see below.
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e40688bb-e6be-4280-895d-cc1b33d28668" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<config-property>
<description>
Sets the XML configuration file used to configure the ActiveMQ broker via
@@ -21,11 +20,11 @@
<config-property-type>java.lang.String</config-property-type>
<config-property-value>xbean:file:C:\broker-config.xml</config-property-value>
</config-property>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
 
<br clear="none" class="atl-forced-newline">
 
<br clear="none" class="atl-forced-newline">
- </li><li>Start the domain's weblogic server (BEA Products -> User Projects -> <domain_name> -> Start Admin Server for Weblogic Server Domain).</li><li>Start the domain's admin console (BEA Products -> User Projects -> <domain_name> -> Admin Server Console) and enter the username and password.</li><li>On the main menu, click "Deployments" under "Your Deployed Resources"</li><li>On the deployment table, click "install" button. If the button is disabled, then click "Lock & Edit" to enable it.</li><li>Browse for the activemq-ra-*.rar file then click next (for testing purpose, choose the default onwards).</li><li>Click the "activate changes" button to check if the resource adapter is properly deployed.</li></ol></div>
+ </li><li>Start the domain's weblogic server (BEA Products -> User Projects -> <domain_name> -> Start Admin Server for Weblogic Server Domain).</li><li>Start the domain's admin console (BEA Products -> User Projects -> <domain_name> -> Admin Server Console) and enter the username and password.</li><li>On the main menu, click "Deployments" under "Your Deployed Resources"</li><li>On the deployment table, click "install" button. If the button is disabled, then click "Lock & Edit" to enable it.</li><li>Browse for the activemq-ra-*.rar file then click next (for testing purpose, choose the default onwards).</li><li>Click the "activate changes" button to check if the resource adapter is properly deployed.</li></ol>
+</div>
diff --git a/how-to-disable-auto-destination-creation.xml b/how-to-disable-auto-destination-creation.xml
index 1190598..645be12 100644
--- a/how-to-disable-auto-destination-creation.xml
+++ b/how-to-disable-auto-destination-creation.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>see <a shape="rect" href="how-do-i-restrict-connections-from-creating-new-queues-or-topics.xml">How do I restrict connections from creating new queues or topics</a></p></div>
+<div class="wiki-content maincontent"><p>see <link><page ri:content-title="How do I restrict connections from creating new queues or topics"></page></link></p></div>
diff --git a/how-to-disable-multicast-discovery.xml b/how-to-disable-multicast-discovery.xml
index 19735f1..e93e897 100644
--- a/how-to-disable-multicast-discovery.xml
+++ b/how-to-disable-multicast-discovery.xml
@@ -1,11 +1,5 @@
-<div class="wiki-content maincontent"><p>By default, the <a shape="rect" href="xml-configuration.xml">ActiveMQ xml configuration</a> includes the <a shape="rect" href="discovery.xml">multicast discovery</a> mechanism. The tcp transport connector advertises its self using multicast and a multicast network connector is configured to listen to the same address. In this way, all brokers that share the default multicast address will automatically network with each other. <br clear="none"> If multicast is not required, the multicast attributes of the Transport Connector and Network Connector can be removed.</p><p>To stop advertising your connection URI on the multicast network remove the discoveryUri attribute from the <transportConnector/>:</p><p>replace:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
-]]></script>
-</div></div><p>with:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="openwire" uri="tcp://localhost:61616" />
-]]></script>
-</div></div><p>If you do not require any networked broker support remove the <networkConnector/> altogether. Remove</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnector name="default-nc" uri="multicast://default"/>
-]]></script>
-</div></div><p>Alternatively, provide a static networkConnector for each broker you wish to network with by replacing the the discoveryUri with the static transport connection URI of your target broker.</p><p>For more information see the <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport Reference</a></p></div>
+<div class="wiki-content maincontent"><p>By default, the <link><page ri:content-title="Xml Configuration"></page><plain-text-link-body>ActiveMQ xml configuration</plain-text-link-body></link> includes the <link><page ri:content-title="Discovery"></page><plain-text-link-body>multicast discovery</plain-text-link-body></link> mechanism. The tcp transport connector advertises its self using multicast and a multicast network connector is configured to listen to the same address. In this way, all brokers that share the default multicast address will automatically network with each other. <br clear="none"> If multicast is not required, the multicast attributes of the Transport Connector and Network Connector can be removed.</p><p>To stop advertising your connection URI on the multicast network remove the discoveryUri attribute from the <transportConnector/>:</p><p>replace:</p><structured-macro ac:macro-id="9c0c7c8b-3210-4afb-91ac-4eb547e20b7a" ac:name="code" ac:schema-version="1"><plain-text-body><transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
+</plain-text-body></structured-macro><p>with:</p><structured-macro ac:macro-id="095890d1-4326-467d-81ff-9f22411ce4c6" ac:name="code" ac:schema-version="1"><plain-text-body><transportConnector name="openwire" uri="tcp://localhost:61616" />
+</plain-text-body></structured-macro><p>If you do not require any networked broker support remove the <networkConnector/> altogether. Remove</p><structured-macro ac:macro-id="9aa1c552-8664-4833-812c-6173fc7855ee" ac:name="code" ac:schema-version="1"><plain-text-body><networkConnector name="default-nc" uri="multicast://default"/>
+</plain-text-body></structured-macro><p>Alternatively, provide a static networkConnector for each broker you wish to network with by replacing the the discoveryUri with the static transport connection URI of your target broker.</p><p>For more information see the <link><page ri:content-title="Discovery Transport Reference"></page></link></p></div>
diff --git a/how-to-unit-test-jms-code.xml b/how-to-unit-test-jms-code.xml
index 1dd0b21..3a38262 100644
--- a/how-to-unit-test-jms-code.xml
+++ b/how-to-unit-test-jms-code.xml
@@ -1,18 +1,9 @@
-<div class="wiki-content maincontent"><p>When unit testing code with JMS you'll typically want to avoid the overhead of running separate proceses; plus you'll want to increase startup time as fast as possible as you tend to run unit tests often and want immediate feedback. Also persistence can often cause problems - as previous test case results can adversely affect future test case runs - so you often need to purge queues on startup.</p><p>So when unit testing JMS code we recommend the following</p><ul><li>Use <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">an embedded broker</a> to avoid a separate broker process being required.</li><li>Disable <a shape="rect" href="broker-configuration-uri.xml">broker persistence</a> so that no queue purging is required before/after tests.</li><li>It's often simpler and faster to just use Java code to create the broker via an XML configuration file using Spring etc.</li></ul><p>You can do all of this using the following Java code to create your JMS <strong><code>ConnectionFactory</code></strong> which will also automatically create an embedded broker</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost?broker.persistent=false");
-]]></script>
-</div></div><p>For more configuration options see the <a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a> and the <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a></p><p>Or if you really would rather be more explicit you can create the broker first using the following Java code</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[BrokerService broker = new BrokerService();
+<div class="wiki-content maincontent"><p>When unit testing code with JMS you'll typically want to avoid the overhead of running separate proceses; plus you'll want to increase startup time as fast as possible as you tend to run unit tests often and want immediate feedback. Also persistence can often cause problems - as previous test case results can adversely affect future test case runs - so you often need to purge queues on startup.</p><p>So when unit testing JMS code we recommend the following</p><ul><li>Use <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>an embedded broker</plain-text-link-body></link> to avoid a separate broker process being required.</li><li>Disable <link><page ri:content-title="Broker Configuration URI"></page><plain-text-link-body>broker persistence</plain-text-link-body></link> so that no queue purging is required before/after tests.</li><li>It's often simpler and faster to just use Java code to create the broker via an XML configuration file using Spring etc.</li></ul><p>You can do all of this using the following Java code to create your JMS <strong><code>ConnectionFactory</code></strong> which will also automatically create an embedded broker</p><structured-macro ac:macro-id="964aef1a-20fb-4432-a94d-0c00a5328ca4" ac:name="code" ac:schema-version="1"><plain-text-body>ConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost?broker.persistent=false");
+</plain-text-body></structured-macro><p>For more configuration options see the <link><page ri:content-title="VM Transport Reference"></page></link> and the <link><page ri:content-title="Broker Configuration URI"></page></link></p><p>Or if you really would rather be more explicit you can create the broker first using the following Java code</p><structured-macro ac:macro-id="e0b3331e-ce0f-494e-8899-e62b59709eea" ac:name="code" ac:schema-version="1"><plain-text-body>BrokerService broker = new BrokerService();
broker.setPersistent(false);
broker.start();
-]]></script>
-</div></div><p>or you could use <a shape="rect" href="spring-support.xml">Spring Support.</a></p><h3 id="HowToUnitTestJMSCode-UsingJNDI">Using JNDI</h3><p>If your application code is using JNDI to lookup the JMS <strong><code>ConnectionFactory</code></strong> and <strong><code>Destination</code></strong>'s to use, then you could use the <a shape="rect" href="jndi-support.xml">JNDI Support</a> in ActiveMQ.</p><p>Add the following <strong><code>jndi.properties</code></strong> to your classpath, e.g., in <strong><code>src/test/resources</code></strong>, if you are using maven:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory
-java.naming.provider.url = vm://localhost?broker.persistent=false]]></script>
-</div></div><p>You should then consider using <a shape="rect" href="jndi-support.xml">Dynamic destinations in JNDI</a> so that your code looks up destinations via</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[context.lookup("dynamicQueues/FOO.BAR");]]></script>
-</div></div><h3 id="HowToUnitTestJMSCode-UsingTheEmbeddedActiveMQBrokerJUnitRule(ActiveMQ5.13)">Using The <code>EmbeddedActiveMQBroker</code> JUnit Rule (ActiveMQ 5.13)</h3><p>If your test code is using JUnit, then you could use the <strong><code>EmbeddedActiveMQBroker</code></strong> JUnit Rule provided in the <strong><code>activemq-junit</code></strong> library. Add the <strong><code>activemq-junit</code></strong> library along with the <strong><code>activemq-broker</code></strong> libraries for the version of ActiveMQ you want to test with.  The rule will use whatever version of ActiveMQ it finds in the classpath, so the ActiveMQ libraries need to be specified if they are not already there.</p><p>If you are using Maven, add the following to your <strong><code>pom.xml</code></strong>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+</plain-text-body></structured-macro><p>or you could use <link><page ri:content-title="Spring Support"></page><plain-text-link-body>Spring Support.</plain-text-link-body></link></p><h3>Using JNDI</h3><p>If your application code is using JNDI to lookup the JMS <strong><code>ConnectionFactory</code></strong> and <strong><code>Destination</code></strong>'s to use, then you could use the <link><page ri:content-title="JNDI Support"></page></link> in ActiveMQ.</p><p>Add the following <strong><code>jndi.properties</code></strong> to your classpath, e.g., in <strong><code>src/test/resources</code></strong>, if you are using maven:</p><structured-macro ac:macro-id="17e1b668-d297-4975-950f-dbb2ef742cde" ac:name="code" ac:schema-version="1"><plain-text-body>java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory
+java.naming.provider.url = vm://localhost?broker.persistent=false</plain-text-body></structured-macro><p>You should then consider using <link><page ri:content-title="JNDI Support"></page><plain-text-link-body>Dynamic destinations in JNDI</plain-text-link-body></link> so that your code looks up destinations via</p><structured-macro ac:macro-id="d2677683-9688-427e-9554-dc0eaf165251" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><plain-text-body>context.lookup("dynamicQueues/FOO.BAR");</plain-text-body></structured-macro><h3>Using The <code>EmbeddedActiveMQBroker</code> JUnit Rule (ActiveMQ 5.13)</h3><p>If your test code is using JUnit, then you could use the <strong><code>EmbeddedActiveMQBroker</code></strong> JUnit Rule provided in the <strong><code>activemq-junit</code></strong> library. Add the <strong><code>activemq-junit</code></strong> library along with the <strong><code>activemq-broker</code></strong> libraries for the version of ActiveMQ you want to test with.  The rule will use whatever version of ActiveMQ it finds in the classpath, so the ActiveMQ libraries need to be specified if they are not already there.</p><p>If you are using Maven, add the following to your <strong><code>pom.xml</code></strong>:</p><structured-macro ac:macro-id="6c23691e-68d8-4990-8b71-a922a216952e" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><dependency>
<groupId>org.apache.activemq.tooling</groupId>
<artifactId>activemq-junit</artifactId>
<version>${activemq-junit-version}</version>
@@ -24,24 +15,16 @@
<artifactId>activemq-broker</artifactId>
<version>${activemq-version}</version>
<scope>test</scope>
-</dependency>]]></script>
-</div></div><p> Then add the <strong><code>EmbeddedActiveMQBroker</code></strong> JUnit Rule to your test, and JUnit will start the embedded broker at the beginning of each test and stop the broker at the end of the test.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Use The ActiveMQ JUnit Rule</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[@Rule
-public EmbeddedActiveMQBroker broker = new EmbeddedActiveMQBroker();]]></script>
-</div></div><p>By default, the <strong><code>EmbeddedActiveMQBroker</code></strong> will configure the broker as non-persistent, and the only transport available will be the VM transport. To customize this configuration, either extend the <strong><code>EmbeddedActiveMQBroker</code></strong> class and override the <strong><code>configure()</code></strong> method, or use an XML configuration for the broker.  </p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><strong>Note</strong>: to configure an <strong><code>EmbeddedActiveMQBroker</code></strong> using XML configuration, you may need to add additional libraries to the classpath to support XBean configuration of ActiveMQ.</div></div><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Customizing An EmbeddedActiveMQBroker Using Java</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[@Rule
+</dependency></plain-text-body></structured-macro><p> Then add the <strong><code>EmbeddedActiveMQBroker</code></strong> JUnit Rule to your test, and JUnit will start the embedded broker at the beginning of each test and stop the broker at the end of the test.</p><structured-macro ac:macro-id="b5da19f2-ebc7-4557-a357-ff6f3d244afa" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><parameter ac:name="title">Use The ActiveMQ JUnit Rule</parameter><plain-text-body>@Rule
+public EmbeddedActiveMQBroker broker = new EmbeddedActiveMQBroker();</plain-text-body></structured-macro><p>By default, the <strong><code>EmbeddedActiveMQBroker</code></strong> will configure the broker as non-persistent, and the only transport available will be the VM transport. To customize this configuration, either extend the <strong><code>EmbeddedActiveMQBroker</code></strong> class and override the <strong><code>configure()</code></strong> method, or use an XML configuration for the broker.  </p><structured-macro ac:macro-id="abacc4e2-d9bb-4b83-a7f3-301bf125c3e5" ac:name="info" ac:schema-version="1"><rich-text-body><strong>Note</strong>: to configure an <strong><code>EmbeddedActiveMQBroker</code></strong> using XML configuration, you may need to add additional libraries to the classpath to support XBean configuration of ActiveMQ.</rich-text-body></structured-macro><structured-macro ac:macro-id="232d811d-409b-45ba-a74f-999ba056d56c" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><parameter ac:name="title">Customizing An EmbeddedActiveMQBroker Using Java</parameter><plain-text-body>@Rule
EmbeddedActiveMQBroker customizedBroker = new EmbeddedActiveMQBroker() {
@Override
protected void configure() {
// Perform additional configuration here...
}
-}]]></script>
-</div></div><p><span><br clear="none"></span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Customizing An EmbeddedActiveMQBroker Using XML Configuration</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[@Rule
-EmbeddedActiveMQBroker customizedBroker = new EmbeddedActiveMQBroker("bean:customize-activemq.xml");
-]]></script>
-</div></div><p>Note that to use the XML configuration, you may need to add additional libraries on the classpath to support the XBean configuration of ActiveMQ.  The versions of the <strong><code>spring-context</code></strong> library should correspond with the version used by your selected version of ActiveMQ.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Maven Configuration For XBean Configuration</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+}</plain-text-body></structured-macro><p><span><br clear="none"></span></p><structured-macro ac:macro-id="cbaabf0f-fc90-4577-a2f5-d7605414c3db" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><parameter ac:name="title">Customizing An EmbeddedActiveMQBroker Using XML Configuration</parameter><plain-text-body>@Rule
+EmbeddedActiveMQBroker customizedBroker = new EmbeddedActiveMQBroker("bean:customize-activemq.xml");
+</plain-text-body></structured-macro><p>Note that to use the XML configuration, you may need to add additional libraries on the classpath to support the XBean configuration of ActiveMQ.  The versions of the <strong><code>spring-context</code></strong> library should correspond with the version used by your selected version of ActiveMQ.</p><structured-macro ac:macro-id="4139db17-61be-4519-a250-924edb3b8dc3" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Maven Configuration For XBean Configuration</parameter><plain-text-body><dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
<version>Appropriate version for activemq-version</version>
@@ -51,10 +34,5 @@
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-spring</artifactId>
<version>${activemq-version></version>
-</dependency>]]></script>
-</div></div><p>Then you can use the VM URI to connect with the broker</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://embedded-broker?create=false");]]></script>
-</div></div><p>You can also get a connection factory from the <strong><code>EmbeddedActiveMQBroker</code></strong>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ConnectionFactory connectionFactory = embeddedBroker.createConnectionFactory();]]></script>
-</div></div></div>
+</dependency></plain-text-body></structured-macro><p>Then you can use the VM URI to connect with the broker</p><structured-macro ac:macro-id="2e52bef4-907c-41ff-bf56-096812c967ac" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><plain-text-body>ConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://embedded-broker?create=false");</plain-text-body></structured-macro><p>You can also get a connection factory from the <strong><code>EmbeddedActiveMQBroker</code></strong>:</p><structured-macro ac:macro-id="19cc19a7-79f8-4d09-9ac1-61b359a83769" ac:name="code" ac:schema-version="1"><parameter ac:name="language">java</parameter><plain-text-body>ConnectionFactory connectionFactory = embeddedBroker.createConnectionFactory();</plain-text-body></structured-macro></div>
diff --git a/how-you-can-help-release.xml b/how-you-can-help-release.xml
index 2aa7f19..1465856 100644
--- a/how-you-can-help-release.xml
+++ b/how-you-can-help-release.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="Howyoucanhelprelease-HowtoHelp">How to Help</h2>
+<div class="wiki-content maincontent"><h2>How to Help</h2>
-<p>Everyone in the ActiveMQ community can help with releases; users, developers, commmiters are all encouraged to test out a release and post any comments to the <a shape="rect" href="mailing-lists.xml">activemq-dev@ mailing list</a> or create a <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ">JIRA</a> issue.</p>
+<p>Everyone in the ActiveMQ community can help with releases; users, developers, commmiters are all encouraged to test out a release and post any comments to the <link><page ri:content-title="Mailing Lists"></page><link-body>activemq-dev@ mailing list</link-body></link> or create a <a shape="rect" href="https://issues.apache.org/activemq/browse/AMQ">JIRA</a> issue.</p>
-<p>ActiveMQ is available in both source and binary distributions. See <a shape="rect" href="getting-started.xml">Getting Started</a>.</p></div>
+<p>ActiveMQ is available in both source and binary distributions. See <link><page ri:content-title="Getting Started"></page></link>.</p></div>
diff --git a/http-and-https-transports-reference.xml b/http-and-https-transports-reference.xml
index ff0283f..95b2cab 100644
--- a/http-and-https-transports-reference.xml
+++ b/http-and-https-transports-reference.xml
@@ -1,32 +1,31 @@
-<div class="wiki-content maincontent"><h3 id="HTTPandHTTPsTransportsReference-HTTPandHTTPSTransports">HTTP and HTTPS Transports</h3>
+<div class="wiki-content maincontent"><h3>HTTP and HTTPS Transports</h3>
<p>The HTTP and HTTPS transports are used to tunnel over HTTP or HTTPS using XML payloads. This allows the ActiveMQ client and broker to tunnel over HTTP avoiding any firewall issues. </p>
-<p>If the client is not JMS you might want to look at <a shape="rect" href="rest.xml">REST</a> or <a shape="rect" href="ajax.xml">Ajax</a> support instead.</p>
+<p>If the client is not JMS you might want to look at <link><page ri:content-title="REST"></page></link> or <link><page ri:content-title="Ajax"></page></link> support instead.</p>
<p>Note that the HTTP Transport is located in the activemq-optional jar.</p>
-<p>ActiveMQ uses a combination of Jetty's Server and SslSocketConnector objects to communicate via the HTTPS transport. When using HTTPS, improper configuration of the corresponding SSL certificates and/or keys may very well lead to the Jetty infinite loop problem described in this <a shape="rect" class="external-link" href="http://www.nabble.com/SslSocketConnector-loops-forever-during-initialization-to14621825.html#a17535467" rel="nofollow">nabble thread</a>. A good reference on creating and configuring keys and certificates can be found <a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/How+to+configure+SSL" rel="nofollow">here</a>.</p>
+<p>ActiveMQ uses a combination of Jetty's Server and SslSocketConnector objects to communicate via the HTTPS transport. When using HTTPS, improper configuration of the corresponding SSL certificates and/or keys may very well lead to the Jetty infinite loop problem described in this <a shape="rect" href="http://www.nabble.com/SslSocketConnector-loops-forever-during-initialization-to14621825.html#a17535467">nabble thread</a>. A good reference on creating and configuring keys and certificates can be found <a shape="rect" href="http://docs.codehaus.org/display/JETTY/How+to+configure+SSL">here</a>.</p>
-<h4 id="HTTPandHTTPsTransportsReference-ConfigurationSyntax">Configuration Syntax</h4>
+<h4>Configuration Syntax</h4>
<p><a shape="rect" class="external-link" href="http://host:port" rel="nofollow">http://host:port</a>
<a shape="rect" class="external-link" href="https://host:port" rel="nofollow">https://host:port</a></p>
-<h4 id="HTTPandHTTPsTransportsReference-ExampleURI">Example URI</h4>
+<h4>Example URI</h4>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>http://localhost
+<structured-macro ac:macro-id="4d99dd99-68a7-450b-b7b3-d7bf05c8b555" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+http://localhost
https://localhost:8080
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="HTTPandHTTPsTransportsReference-Dependencies">Dependencies</h4>
+<h4>Dependencies</h4>
<p>Clients that use http(s) transport have some additional dependencies, over tcp ones. Those are </p>
-<ul><li><a shape="rect" class="external-link" href="http://hc.apache.org/httpclient-3.x/">HttpClient</a></li><li>and <a shape="rect" class="external-link" href="http://xstream.codehaus.org/" rel="nofollow">XStream</a></li></ul>
+<ul><li><a shape="rect" href="http://hc.apache.org/httpclient-3.x/">HttpClient</a></li><li>and <a shape="rect" href="http://xstream.codehaus.org/">XStream</a></li></ul>
<p>Make sure you have them in your classpath if you use this transport. Also, if you're configuring networks of brokers with http(s) transport make sure you have them in broker's classpath (somewhere under <code>lib/</code> directory) as the broker will act as a client in that case.</p></div>
diff --git a/i-am-having-problems-with-the-spring-jmstemplate.xml b/i-am-having-problems-with-the-spring-jmstemplate.xml
index 7543b20..6698637 100644
--- a/i-am-having-problems-with-the-spring-jmstemplate.xml
+++ b/i-am-having-problems-with-the-spring-jmstemplate.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="IamhavingproblemswiththeSpringJmsTemplate-IamhavingproblemswiththeSpringJmsTemplate">I am having problems with the Spring JmsTemplate</h2>
+<div class="wiki-content maincontent"><h2>I am having problems with the Spring JmsTemplate</h2>
-<p>For more detail see the <a shape="rect" href="jmstemplate-gotchas.xml">JmsTemplate Gotchas</a> page along with the <a shape="rect" href="spring-support.xml">Spring Support</a></p></div>
+<p>For more detail see the <link><page ri:content-title="JmsTemplate Gotchas"></page></link> page along with the <link><page ri:content-title="Spring Support"></page></link></p></div>
diff --git a/i-am-not-receiving-any-messages-what-is-wrong.xml b/i-am-not-receiving-any-messages-what-is-wrong.xml
index f09c574..18115da 100644
--- a/i-am-not-receiving-any-messages-what-is-wrong.xml
+++ b/i-am-not-receiving-any-messages-what-is-wrong.xml
@@ -1,15 +1,15 @@
-<div class="wiki-content maincontent"><h3 id="Iamnotreceivinganymessages,whatiswrong-Iamnotreceivinganymessages-whatiswrong?">I am not receiving any messages - what is wrong?</h3>
+<div class="wiki-content maincontent"><h3>I am not receiving any messages - what is wrong?</h3>
-<p>A <em>very</em> common gotcha when working with JMS is forgetting to start the JMS connection, creating a consumer and not having it receive any messages. I myself have tripped up over this one many many times! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>A <em>very</em> common gotcha when working with JMS is forgetting to start the JMS connection, creating a consumer and not having it receive any messages. I myself have tripped up over this one many many times! <emoticon ac:name="smile"></emoticon></p>
-<p>Make sure you call the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#start()" rel="nofollow">start()</a> method on the JMS connection, otherwise messages will not be dispatched to your consumer.</p>
+<p>Make sure you call the <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#start()">start()</a> method on the JMS connection, otherwise messages will not be dispatched to your consumer.</p>
-<p>This is such a common gotcha that as of 4.2 onwards, ActiveMQ will now <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ-1253">log a warning if a message</a> is received shortly after the connection was created if the connection was not started (as its so easy to forget to do this part <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">. </p>
+<p>This is such a common gotcha that as of 4.2 onwards, ActiveMQ will now <a shape="rect" href="https://issues.apache.org/activemq/browse/AMQ-1253">log a warning if a message</a> is received shortly after the connection was created if the connection was not started (as its so easy to forget to do this part <emoticon ac:name="smile"></emoticon>. </p>
-<p>For more details see the discussion of the <strong>warnAboutUnstartedConnectionTimeout</strong> property on the <a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a></p>
+<p>For more details see the discussion of the <strong>warnAboutUnstartedConnectionTimeout</strong> property on the <link><page ri:content-title="Connection Configuration URI"></page></link></p>
-<h3 id="Iamnotreceivinganymessages,whatiswrong-Ifyouarecallingconnection.start()">If you are calling connection.start()</h3>
+<h3>If you are calling connection.start()</h3>
-<p>Another common gotcha is <a shape="rect" href="i-do-not-receive-messages-in-my-second-consumer.xml">due to another consumer grabbing the messages</a>. If its not that then please look at <a shape="rect" href="jmx.xml">JMX</a> or the <a shape="rect" href="web-console.xml">Web Console</a> to determine what consumers are available and their status. Then get some <a shape="rect" href="support.xml">Support</a> to help you resolve your issue.</p></div>
+<p>Another common gotcha is <link><page ri:content-title="I do not receive messages in my second consumer"></page><link-body>due to another consumer grabbing the messages</link-body></link>. If its not that then please look at <link><page ri:content-title="JMX"></page></link> or the <link><page ri:content-title="Web Console"></page></link> to determine what consumers are available and their status. Then get some <link><page ri:content-title="Support"></page></link> to help you resolve your issue.</p></div>
diff --git a/i-cannot-connect-to-activemq-from-jconsole.xml b/i-cannot-connect-to-activemq-from-jconsole.xml
index ea1f7e2..2b0092c 100644
--- a/i-cannot-connect-to-activemq-from-jconsole.xml
+++ b/i-cannot-connect-to-activemq-from-jconsole.xml
@@ -2,19 +2,15 @@
<p>e.g. on unix (OS X, Linux, Solaris)</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="7b9766cc-e65f-46e3-ac75-a5d24a48e220" ac:name="code" ac:schema-version="1"><plain-text-body>
export ACTIVEMQ_OPTS=$ACTIVEMQ_OPTS -Djava.rmi.server.hostname=<hostname>
activemq
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>or on Windows</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="61232e79-c03a-457a-beda-9bb1d082442f" ac:name="code" ac:schema-version="1"><plain-text-body>
SET ACTIVEMQ_OPTS=%ACTIVEMQ_OPTS% -Djava.rmi.server.hostname=<hostname>
activemq
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/i-do-not-receive-messages-in-my-second-consumer.xml b/i-do-not-receive-messages-in-my-second-consumer.xml
index 8ba1cc3..2f407a3 100644
--- a/i-do-not-receive-messages-in-my-second-consumer.xml
+++ b/i-do-not-receive-messages-in-my-second-consumer.xml
@@ -1,11 +1,11 @@
-<div class="wiki-content maincontent"><h3 id="Idonotreceivemessagesinmysecondconsumer-Scenario">Scenario</h3>
+<div class="wiki-content maincontent"><h3>Scenario</h3>
<ul><li>You send 100 messages to a queue.</li><li>Start consumer A, it receives the message</li><li>You start another consumer B, it doesn't receive any messages.</li><li>You kill A.</li><li>Consumer B receives messages now, why?</li></ul>
-<h3 id="Idonotreceivemessagesinmysecondconsumer-Answer">Answer</h3>
+<h3>Answer</h3>
-<p>This is to do with <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch buffers</a>.</p>
+<p>This is to do with <link><page ri:content-title="What is the Prefetch Limit For?"></page><link-body>prefetch buffers</link-body></link>.</p>
<p>ActiveMQ will try and deliver a number of messages to each consumer as soon as possible to achieve maximum throughput. That means that each consumer typically has 100-1000 messages in RAM ready to be processed so that there is no latency waiting for another message to arrive under periods of high throughput of messages.</p>
@@ -16,11 +16,12 @@
<p>The solution to this problem is to configure the pre-fetch value to something smaller - such as 1, start the consumers together or publish the messages after the consumers have started.</p>
-<p>You can also <a shape="rect" href="how-do-i-change-dispatch-policy.xml">change the dispatch policy</a> to ensure round robin dispatch.</p>
+<p>You can also <link><page ri:content-title="How do I change dispatch policy"></page><link-body>change the dispatch policy</link-body></link> to ensure round robin dispatch.</p>
-<p>To help diagnose these kinds of issues, try <a shape="rect" href="jmx.xml">JMX</a> or the <a shape="rect" href="web-console.xml">Web Console</a></p>
+<p>To help diagnose these kinds of issues, try <link><page ri:content-title="JMX"></page></link> or the <link><page ri:content-title="Web Console"></page></link></p>
-<h3 id="Idonotreceivemessagesinmysecondconsumer-Seealso">See also</h3>
+<h3>See also</h3>
-<ul><li><a shape="rect" href="how-do-i-change-dispatch-policy.xml">How do I change dispatch policy</a></li><li><a shape="rect" href="jmx.xml">JMX</a></li><li><a shape="rect" href="web-console.xml">Web Console</a></li></ul></div>
+<ul><li><link><page ri:content-title="How do I change dispatch policy"></page></link></li><li><link><page ri:content-title="JMX"></page></link></li><li><link><page ri:content-title="Web Console"></page></link></li></ul>
+</div>
diff --git a/i-get-errors-building-the-code-whats-wrong.xml b/i-get-errors-building-the-code-whats-wrong.xml
index 3c224a0..f75dc69 100644
--- a/i-get-errors-building-the-code-whats-wrong.xml
+++ b/i-get-errors-building-the-code-whats-wrong.xml
@@ -1,13 +1,11 @@
<div class="wiki-content maincontent">
<p>We currently use a multi-project maven build system, which can be a little fragile. If you are ever having problems building we suggest you try the following in the root <em>activemq</em> directory</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a23dd9f7-0dec-40a1-bb2d-a15f3c6c609e" ac:name="code" ac:schema-version="1"><plain-text-body>
mvn clean
rm -rf ~/.m2/repository
mvn
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>You may also want to <a shape="rect" href="how-do-i-build-but-disable-the-unit-tests.xml">disable the unit tests</a></p></div>
+<p>You may also want to <link><page ri:content-title="How do I build but disable the unit tests"></page><link-body>disable the unit tests</link-body></link></p></div>
diff --git a/i-see-nc-client-ids-what-does-that-mean.xml b/i-see-nc-client-ids-what-does-that-mean.xml
index 7e412d7..d69944c 100644
--- a/i-see-nc-client-ids-what-does-that-mean.xml
+++ b/i-see-nc-client-ids-what-does-that-mean.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Durable subscription ClientIds and SubscriptionNames using the <strong>NC</strong> prefix are the result of durable subscriptions in a <a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a>.<br clear="none"> When a durable subscription is being forwarded by a network connector (or demand forwarding bridge), the network durable subscription needs to outlive the subscription that created it. This is achieved by using a well known name for the clientId and subscriptionName that can be easily be mapped to the original subscription. The prefix NC_, and NC-DS_ are used, where NC denotes Network Connector and DS denotes Durable Subscription. The prefix is combined with the local broker name and the target destination.</p><p>The expectation is that the connectionId associated with these subscriptions can change on a reconnect, but the durable subsctiption remains. In this way, the durable subscription can continue to receive messages even if there is a network partition between the originating broker and the forwarding broker.</p><p>On a restart, the NC durable subscriptions are activated by default, to ensure that no messages are lost. If lost messages are acceptable, it is possible to ensure that the NC durable sub is activated dynamically, when the original subscription is again activated on the remote broker and propagated to the network connector. The network connector configuration 'dynamicOnly' attribute is used to control this behavior.</p><p>A NC durable subscription is only deleted when the original durable consumer is unsubscribed.</p></div>
+<div class="wiki-content maincontent"><p>Durable subscription ClientIds and SubscriptionNames using the <strong>NC</strong> prefix are the result of durable subscriptions in a <link><page ri:content-title="Networks of Brokers"></page></link>.<br clear="none"> When a durable subscription is being forwarded by a network connector (or demand forwarding bridge), the network durable subscription needs to outlive the subscription that created it. This is achieved by using a well known name for the clientId and subscriptionName that can be easily be mapped to the original subscription. The prefix NC_, and NC-DS_ are used, where NC denotes Network Connector and DS denotes Durable Subscription. The prefix is combined with the local broker name and the target destination.</p><p>The expectation is that the connectionId associated with these subscriptions can change on a reconnect, but the durable subsctiption remains. In this way, the durable subscription can continue to receive messages even if there is a network partition between the originating broker and the forwarding broker.</p><p>On a restart, the NC durable subscriptions are activated by default, to ensure that no messages are lost. If lost messages are acceptable, it is possible to ensure that the NC durable sub is activated dynamically, when the original subscription is again activated on the remote broker and propagated to the network connector. The network connector configuration 'dynamicOnly' attribute is used to control this behavior.</p><p>A NC durable subscription is only deleted when the original durable consumer is unsubscribed.</p></div>
diff --git a/ideas.xml b/ideas.xml
index 9d379fb..a9a590c 100644
--- a/ideas.xml
+++ b/ideas.xml
@@ -3,5 +3,5 @@
<p>This page hosts various ideas and thoughts...</p>
-<ul class="childpages-macro"><li><a shape="rect" href="restful-queue.xml">RESTful Queue</a></li></ul></div>
+<structured-macro ac:macro-id="c3476a72-5260-45de-8054-3851b07b4b41" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/in-progress.xml b/in-progress.xml
index 67d57b1..e814bff 100644
--- a/in-progress.xml
+++ b/in-progress.xml
@@ -1,5 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="InProgress-ReleasesInProgress">Releases In Progress</h2>
+<div class="wiki-content maincontent"><h2>Releases In Progress</h2>
<p>The following releases are currently in progress</p>
-</div>
+
+<structured-macro ac:macro-id="fecbeb2a-0e2b-4eac-b0a6-7bd5e152589d" ac:name="children" ac:schema-version="1"><parameter ac:name="sort">creation</parameter><parameter ac:name="reverse">true</parameter></structured-macro></div>
diff --git a/inbound-communication.xml b/inbound-communication.xml
index 68de133..c71c92c 100644
--- a/inbound-communication.xml
+++ b/inbound-communication.xml
@@ -1,13 +1,12 @@
<div class="wiki-content maincontent">
-<h2 id="InboundCommunication-INLINEConfiguringanMDBtoreceivemessagesfromActiveMQ">Configuring an MDB to receive messages from ActiveMQ</h2>
-<p>There are three MDBs declared in the <a shape="rect" href="inbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3249" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="ejb-jar.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">ejb-jar.xml</a> deployment descriptor. For this example, I will be explaining how to configure the <code>TopicDurableMDB</code> to be invoked by JBoss when a message is received on an ActiveMQ Topic.</p>
+<h2><structured-macro ac:macro-id="266bfef6-a4d2-4ae3-9429-a53a5a694960" ac:name="excerpt" ac:schema-version="1"><parameter ac:name="atlassian-macro-output-type">INLINE</parameter><rich-text-body><p>Configuring an MDB to receive messages from ActiveMQ</p></rich-text-body></structured-macro></h2>
+<p>There are three MDBs declared in the <link><attachment ri:filename="ejb-jar.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>ejb-jar.xml</link-body></link> deployment descriptor. For this example, I will be explaining how to configure the <code>TopicDurableMDB</code> to be invoked by JBoss when a message is received on an ActiveMQ Topic.</p>
-<h3 id="InboundCommunication-TheBean">The Bean</h3>
-<p>In the <a shape="rect" href="inbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3249" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="ejb-jar.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">ejb-jar.xml</a> deployment descriptor, the <code>TopicDurableMDB</code> is declared as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ejb-jar.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h3>The Bean</h3>
+<p>In the <link><attachment ri:filename="ejb-jar.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>ejb-jar.xml</link-body></link> deployment descriptor, the <code>TopicDurableMDB</code> is declared as follows:</p>
+<structured-macro ac:macro-id="93b54ff4-22bf-4757-8139-2e2fd39d4021" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">ejb-jar.xml</parameter><plain-text-body>
<message-driven>
...
<ejb-name>TopicDurableMDB</ejb-name>
@@ -27,14 +26,12 @@
</activation-config>
...
</message-driven>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The <code>activation-config</code> element and it's child element, <code>activation-config-property</code>, are new elements for EJBs, so you might not be familiar with them. I won't go into to much detail about them, but it is important to understand that this is the first mechanism you use to link an MDB to a JCA. </p>
-<h3 id="InboundCommunication-TheConnector">The Connector</h3>
-<p>The two <code>activation-config-properties</code> shown above link to the following elements in the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml" rel="nofollow">ra.xml</a> file, which is contained within the <a shape="rect" href="jboss-integration.xml#JBossIntegration-rarfile">activemq-ra-1.2.rar</a> file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h3>The Connector</h3>
+<p>The two <code>activation-config-properties</code> shown above link to the following elements in the <a shape="rect" href="http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml">ra.xml</a> file, which is contained within the <link ac:anchor="rarfile" ac:tooltip="The ActiveMQ JCA"><page ri:content-title="JBoss Integration"></page><link-body>activemq-ra-1.2.rar</link-body></link> file:</p>
+<structured-macro ac:macro-id="7bf9366c-c37f-4f3a-8819-fc99e87c4104" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">ra.xml</parameter><plain-text-body>
<inbound-resourceadapter>
...
<activationspec>
@@ -48,54 +45,47 @@
</activationspec>
...
</inbound-resourceadapter>
-]]></script>
-</div></div>
-<p>In the <a shape="rect" href="inbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3249" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="ejb-jar.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">ejb-jar.xml</a> file section shown above, the value of the <code>Destination</code> property is set to <code>topic.testTopic</code>. This value is the physical name of the ActiveMQ destination the <code>TopicDurableMDB</code> will be receiving messages from and not a JNDI name. In other words, the value of the <code>Destination</code> property has no meaning to JBoss. It is purely an ActiveMQ setting. </p>
+</plain-text-body></structured-macro>
+<p>In the <link><attachment ri:filename="ejb-jar.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>ejb-jar.xml</link-body></link> file section shown above, the value of the <code>Destination</code> property is set to <code>topic.testTopic</code>. This value is the physical name of the ActiveMQ destination the <code>TopicDurableMDB</code> will be receiving messages from and not a JNDI name. In other words, the value of the <code>Destination</code> property has no meaning to JBoss. It is purely an ActiveMQ setting. </p>
-<h3 id="InboundCommunication-TheGlue">The Glue</h3>
-<p>In JBoss, the thing which connects an inbound JMS destination to an MDB is a JBoss container. To use ActiveMQ as the inbound message source for the <code>TopicDurableMDB</code> we must configure a new JBoss container. We do this in the <a shape="rect" href="inbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3251" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="jboss.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">jboss.xml</a> file.</p>
+<h3>The Glue</h3>
+<p>In JBoss, the thing which connects an inbound JMS destination to an MDB is a JBoss container. To use ActiveMQ as the inbound message source for the <code>TopicDurableMDB</code> we must configure a new JBoss container. We do this in the <link><attachment ri:filename="jboss.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>jboss.xml</link-body></link> file.</p>
-<p>Three things are needed in the <a shape="rect" href="inbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3251" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="jboss.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">jboss.xml</a> file in order to tie an MDB to a connector. They are:</p>
+<p>Three things are needed in the <link><attachment ri:filename="jboss.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>jboss.xml</link-body></link> file in order to tie an MDB to a connector. They are:</p>
<ol><li>Configure a new <code>invoker-proxy-binding</code> that declares <code>JBossMessageEndpointFactory</code> as the <code>proxy-factory</code></li><li>Configure a new MDB container which uses the new <code>invoker-proxy-binding</code></li><li>Declare which MDBs should go into the new container</li></ol>
<p>This first snippet configures a new <code>invoker-proxy-binding</code>:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>jboss.xml – invoker-proxy-binding</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b0c5918e-6353-42c5-8497-2dc26104f808" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">jboss.xml -- invoker-proxy-binding</parameter><plain-text-body>
<invoker-proxy-binding>
<name>activemq-message-driven-bean</name>
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory</proxy-factory>
...
</invoker-proxy-binding>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This second snippet configures a new MDB container which uses the <code>invoker-proxy-binding</code> configured above:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>jboss.xml – container-configuration</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f089de17-bdb2-4912-962b-802892187292" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">jboss.xml -- container-configuration</parameter><plain-text-body>
<container-configuration>
<container-name>ActiveMQ Message Driven Bean</container-name>
<call-logging>false</call-logging>
<invoker-proxy-binding-name>activemq-message-driven-bean</invoker-proxy-binding-name>
...
</container-configuration>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>This third snippet links the <code>TopicDurableMDB</code> to the <a shape="rect" href="jboss-integration.xml#JBossIntegration-rarfile">activemq-ra-1.2.rar</a> connector and tells JBoss to put instances of <code>TopicDurableMDB</code> into the new MDB container declared above:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>jboss.xml – TopicDurableMDB</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>This third snippet links the <code>TopicDurableMDB</code> to the <link ac:anchor="rarfile" ac:tooltip="The ActiveMQ JCA"><page ri:content-title="JBoss Integration"></page><link-body>activemq-ra-1.2.rar</link-body></link> connector and tells JBoss to put instances of <code>TopicDurableMDB</code> into the new MDB container declared above:</p>
+<structured-macro ac:macro-id="88e4dbc4-c3e3-40aa-a1d9-ccf9cd47297e" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">jboss.xml -- TopicDurableMDB</parameter><plain-text-body>
<message-driven>
<ejb-name>TopicDurableMDB</ejb-name>
<resource-adapter-name>activemq-ra-1.2-SNAPSHOT.rar</resource-adapter-name>
<configuration-name>ActiveMQ Message Driven Bean</configuration-name>
</message-driven>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The above examples highlight the key configuration settings needed to enable MDBs deployed in JBoss to process messages from an ActiveMQ destination. </p>
-<p>You can try the above example, plus a few more, by downloading the <a shape="rect" href="inbound-communication.data/activemq-jboss-test.zip?version=3&modificationDate=1117021355000&api=v2" data-linked-resource-id="3278" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="activemq-jboss-test.zip" data-nice-type="Zip Archive" data-linked-resource-content-type="application/zip" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">activemq-jboss-test.zip</a> file which contains the complete sample project.</p></div>
+<p>You can try the above example, plus a few more, by downloading the <link><attachment ri:filename="activemq-jboss-test.zip"><page ri:content-title="JBoss Integration"></page></attachment><link-body>activemq-jboss-test.zip</link-body></link> file which contains the complete sample project.</p></div>
diff --git a/index.xml b/index.xml
index a7b0cbd..0ab73ce 100644
--- a/index.xml
+++ b/index.xml
@@ -1,104 +1,2 @@
-<div class="wiki-content maincontent"><h3 id="Index-DownloadActiveMQ5.15.2Today!" style="text-align: center;"><a shape="rect" href="download.xml">Download ActiveMQ 5.15.2 Today!</a></h3><p><a shape="rect" class="external-link" href="http://activemq.apache.org/">Apache ActiveMQ</a> ™ is the most popular and powerful open source messaging and <a shape="rect" href="enterprise-integration-patterns.xml">Integration Patterns</a> server.</p><p>Apache ActiveMQ is fast, supports many <a shape="rect" href="cross-language-clients.xml">Cross Language Clients and Protocols</a>, comes with easy to use <a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> and many <a shape="rect" href="features.xml">advanced features</a> while fully supporting <a shape="rect" class="external-link" href="http://java.sun.com/products/jms/" rel="nofollow">JMS 1.1</a> and J2EE 1.4. Apache ActiveMQ is released under the <a shape="rect" class="external-link" href="http://www.apache.org/">Apache</a> <a shape="rect" class="external-link" href="http://www.apache.org/licenses/LICENSE-2.0.html">2.0 License</a></p><p>Grab yourself a <a shape="rect" href="download.xml">Download</a>, try our <a shape="rect" href="getting-started.xml">Getting Started Guide</a>, surf our <a shape="rect" href="faq.xml">FAQ</a> or start <a shape="rect" href="contributing.xml">Contributing</a> and join us on our <a shape="rect" href="discussion-forums.xml">Discussion Forums</a>.</p><h3 id="Index-Features">Features</h3><p></p><ul><li>Supports a variety of <a shape="rect" href="cross-language-clients.xml">Cross Language Clients and Protocols</a> from Java, C, C++, C#, Ruby, Perl, Python, PHP<ul><li><a shape="rect" href="openwire.xml">OpenWire</a> for high performance clients in Java, C, C++, C#</li><li><a shape="rect" href="stomp.xml">Stomp</a> support so that clients can be written easily in C, Ruby, Perl, Python, PHP, ActionScript/Flash, Smalltalk to talk to ActiveMQ as well as any other popular Message Broker</li><li><a shape="rect" href="amqp.xml">AMQP</a> v1.0 support</li><li><a shape="rect" href="mqtt.xml">MQTT</a> v3.1 support allowing for connections in an IoT environment.</li></ul></li><li>full support for the <a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> both in the JMS client and the Message Broker</li><li>Supports many <a shape="rect" href="features.xml">advanced features</a> such as <a shape="rect" href="message-groups.xml">Message Groups</a>, <a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a>, <a shape="rect" href="wildcards.xml">Wildcards</a> and <a shape="rect" href="composite-destinations.xml">Composite Destinations</a></li><li>Fully supports JMS 1.1 and J2EE 1.4 with support for transient, persistent, transactional and XA messaging</li><li><a shape="rect" href="spring-support.xml">Spring Support</a> so that ActiveMQ can be easily embedded into Spring applications and configured using Spring's XML configuration mechanism</li><li>Tested inside popular J2EE servers such as <a shape="rect" class="external-link" href="http://tomee.apache.org/">TomEE</a>, <a shape="rect" class="external-link" href="http://geronimo.apache.org/">Geronimo</a>, JBoss, GlassFish and WebLogic<ul><li>Includes <a shape="rect" href="resource-adapter.xml">JCA 1.5 resource adaptors</a> for inbound & outbound messaging so that ActiveMQ should auto-deploy in any J2EE 1.4 compliant server</li></ul></li><li>Supports pluggable <a shape="rect" href="uri-protocols.xml">transport protocols</a> such as <a shape="rect" href="how-do-i-use-activemq-using-in-jvm-messaging.xml">in-VM</a>, TCP, SSL, NIO, UDP, multicast, JGroups and JXTA transports</li><li>Supports very fast <a shape="rect" href="persistence.xml">persistence</a> using JDBC along with a high performance journal</li><li>Designed for high performance clustering, client-server, peer based communication</li><li><a shape="rect" href="rest.xml">REST</a> API to provide technology agnostic and language neutral web based API to messaging</li><li><a shape="rect" href="ajax.xml">Ajax</a> to support web streaming support to web browsers using pure DHTML, allowing web browsers to be part of the messaging fabric</li><li><a shape="rect" href="axis-and-cxf-support.xml">CXF and Axis Support</a> so that ActiveMQ can be easily dropped into either of these web service stacks to provide reliable messaging</li><li>Can be used as an in memory JMS provider, ideal for <a shape="rect" href="how-to-unit-test-jms-code.xml">unit testing JMS</a></li></ul><h3 id="Index-News">News</h3><p>
-
-
-
-</p><div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/10/23/apache-activemq-5152-released.xml">Apache ActiveMQ 5.15.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Oct 23, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5152-release.html">ActiveMQ 5.15.2</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/07/06/apache-activemq-5150-released.xml">Apache ActiveMQ 5.15.0 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Jul 06, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5150-release.html">ActiveMQ 5.15.0</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~dejanb">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: dejanb" title="dejanb">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/04/17/apache-activemq-5145-released.xml">Apache ActiveMQ 5.14.5 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~dejanb">Dejan Bosanac</a> posted on Apr 17, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <p>The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5145-release.html">ActiveMQ 5.14.5</a><br clear="none">A big thanks to everyone who contributed to this release.<br clear="none">We look forward to your feedback.</p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/03/03/apache-activemq-5144-released.xml">Apache ActiveMQ 5.14.4 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Mar 03, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5144-release.html">ActiveMQ 5.14.4</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/12/09/apache-activemq-5142-released.xml">Apache ActiveMQ 5.14.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Dec 09, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5142-release.html">ActiveMQ 5.14.2</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
- <h3 id="Index-MoreNews">More News</h3><ul><li><a shape="rect" href="news.xml">Get all the latest Apache ActiveMQ News Here!</a></li></ul></div>
+<div class="wiki-content maincontent"><h3 style="text-align: center;"><link><page ri:content-title="Download"></page><plain-text-link-body>Download ActiveMQ 5.15.2 Today!</plain-text-link-body></link></h3><p><a shape="rect" href="http://activemq.apache.org/">Apache ActiveMQ</a> ™ is the most popular and powerful open source messaging and <link><page ri:content-title="Enterprise Integration Patterns"></page><plain-text-link-body>Integration Patterns</plain-text-link-body></link> server.</p><p>Apache ActiveMQ is fast, supports many <link><page ri:content-title="Cross Language Clients"></page><plain-text-link-body>Cross Language Clients and Protocols</plain-text-link-body></link>, comes with easy to use <link><page ri:content-title="Enterprise Integration Patterns"></page></link> and many <link><page ri:content-title="Features"></page><plain-text-link-body>advanced features</plain-text-link-body></link> while fully supporting <a shape="rect" href="http://java.sun.com/products/jms/">JMS 1.1</a> and J2EE 1.4. Apache ActiveMQ is released under the <a shape="rect" href="http://www.apache.org/">Apache</a> <a shape="rect" href="http://www.apache.org/licenses/LICENSE-2.0.html">2.0 License</a></p><p>Grab yourself a <link><page ri:content-title="Download"></page></link>, try our <link><page ri:content-title="Getting Started"></page><plain-text-link-body>Getting Started Guide</plain-text-link-body></link>, surf our <link><page ri:content-title="FAQ"></page></link> or start <link><page ri:content-title="Contributing"></page></link> and join us on our <link><page ri:content-title="Discussion Forums"></page></link>.</p><h3>Features</h3><p><structured-macro ac:macro-id="73467dfb-df8a-4bae-991f-9caf3e783f7a" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Features Overview"></page></link></parameter></structured-macro></p><h3>News</h3><p><structured-macro ac:macro-id="94a71fa4-0ab1-4c68-bc99-53dfa96d7548" ac:name="blog-posts" ac:schema-version="1"><parameter ac:name="max">5</parameter><parameter ac:name="sort">modified</parameter><parameter ac:name="reverse">true</parameter></structured-macro></p><h3>More News</h3><ul><li><link><page ri:content-title="News"></page><plain-text-link-body>Get all the latest Apache ActiveMQ News Here!</plain-text-link-body></link></li></ul></div>
diff --git a/initial-configuration.xml b/initial-configuration.xml
index f5b6d0a..5818481 100644
--- a/initial-configuration.xml
+++ b/initial-configuration.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="InitialConfiguration-InitialConfiguration">Initial Configuration</h1><h2 id="InitialConfiguration-DocumentOrganization">Document Organization</h2><ul><li><a shape="rect" href="#InitialConfiguration-RequiredJARs">#Required JARs</a></li><li><a shape="rect" href="#InitialConfiguration-OptionalJARS">#Optional JARS</a></li><li><a shape="rect" href="#InitialConfiguration-PersistenceSupport">#Persistence Support</a></li><li><a shape="rect" href="#InitialConfiguration-Nextsteps">#Next steps</a></li><li><a shape="rect" href="#InitialConfiguration-AdditionalResources">#Additional Resources</a><ul><li><a shape="rect" href="#InitialConfiguration-RelatedReading">#Related Reading</a></li><li><a shape="rect" href="#InitialConfiguration-Specifications">#Specifications</a></li><li><a shape="rect" href="#InitialConfiguration-Relatedopensourceprojects">#Related open source projects</a></li></ul></li></ul><p>Firstly you need to add the jars to your classpath.</p><h2 id="InitialConfiguration-RequiredJARs">Required JARs</h2><p>To make ActiveMQ easy to use, the default <strong>activemq-all.jar</strong> comes complete with all the libraries required. If you prefer to have explicit control over all the jars used by ActiveMQ here is the full list of individual jars required</p><ul><li>activemq-broker.jar</li><li>activemq-client.jar</li><li>activeio-core.jar</li><li>activemq-kahadb-store.jar (if you wish to use persistence)</li><li>slf4j-api.jar</li><li>J2EE APIs which could be the j2ee.jar from Sun or your J2EE container or you could use Geronimo's freely distributable geronimo-spec-j2ee.jar. If you are inside a servlet container and being dependent on the j2ee.jar causes you troubles, the parts of the J2EE jar we are dependent on are as follows...<ul><li>geronimo-spec-jms.jar</li><li>geronimo-spec-jta.jar</li><li>geronimo-spec-j2ee-management.jar</li></ul></li></ul><p>If you want to grab a J2EE specification jar we recommend the Apache <a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/geronimo/">repository</a></p><h2 id="InitialConfiguration-OptionalJARS">Optional JARS</h2><ul><li>spring.jar - if you wish to use the XML configuration file for configuring the Message Broker</li></ul><ul><li>if you wish to use message persistence then you need to add a persistent jar to your classpath (see below). If you just want a lightweight message bus with no durability you can leave this step out but we highly recommend persistence for production deployments.</li></ul><h2 id="InitialConfiguration-PersistenceSupport">Persistence Support</h2><p>We support persistence via <a shape="rect" href="persistence.xml">Specialized KahaDB file system message store or JDBC</a>. For full explict control over configuration check out the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. If you wish to use KahaDB, include kahadb.jar in your classpath. In case of JDBC you'll need to include appropriate database driver.</p><p>If you're just doing some testing or in-VM SEDA based messaging you may wish to disable persistence. You can use the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> for this.</p><p>In 5.x you can do this by setting the <code>persistent=false</code> property to false either in the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> or on the <a shape="rect" href="configuring-transports.xml">broker URL</a>.</p><h2 id="InitialConfiguration-Nextsteps">Next steps</h2><p>One of the first things you might want to do is <a shape="rect" href="run-broker.xml">start a broker</a>. Once you have a broker running you could try some <a shape="rect" href="examples.xml">example programs</a></p><p>If you want to write your own application, you can just instantiate an <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a>, configure its properties directly and then you're ready to use the standard JMS API to create Connections, Sessions, MessageProducer and MessageConsumer instances.</p><p>You can also take a look at our <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/">unit tests</a> for more examples on how to use ActiveMQ.</p><h2 id="InitialConfiguration-AdditionalResources">Additional Resources</h2><h3 id="InitialConfiguration-RelatedReading">Related Reading</h3><ul><li>Sun's <a shape="rect" class="external-link" href="http://java.sun.com/products/jms/tutorial/" rel="nofollow">JMS Tutorial</a> is a handy place to start looking at how to use the JMS API directly</li><li>The ActiveMQ <a shape="rect" class="external-link" href="http://activemq.apache.org/">Website</a> for specifics on how to use ActiveMQ</li><li><a shape="rect" href="topologies.xml">ActiveMQ Topologies</a></li><li><a shape="rect" href="clustering.xml">ActiveMQ Clustering</a></li><li><a shape="rect" href="networks-of-brokers.xml">ActiveMQ Network of Brokers</a></li><li><a shape="rect" class="external-link" href="http://www.eecs.harvard.edu/~mdw/proj/seda/" rel="nofollow">Staged Event Driven Architecture (SEDA)</a></li></ul><h3 id="InitialConfiguration-Specifications">Specifications</h3><ul><li><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/" rel="nofollow">Java Connector Architecture 1.5</a></li><li><a shape="rect" class="external-link" href="http://java.sun.com/products/jms/index.jsp" rel="nofollow">Java Messaging Service</a></li></ul><h3 id="InitialConfiguration-Relatedopensourceprojects">Related open source projects</h3><ul><li><a shape="rect" class="external-link" href="http://camel.apache.org">Apache Camel</a></li><li><a shape="rect" class="external-link" href="http://geronimo.apache.org/">Apache Geronimo</a></li><li><a shape="rect" class="external-link" href="http://www.hermesjms.com/" rel="nofollow">Hermes JMS</a></li><li><a shape="rect" class="external-link" href="http://stomp.github.com/" rel="nofollow">Stomp</a> is an open wire protocol (similar to HTTP) for communicating with MOMs from different languages. It has clients for languages like C, C#, Python, Perl, Ruby etc.</li><li><a shape="rect" class="external-link" href="http://xbean.org/" rel="nofollow">XBean</a> is used as the default XML configuration mechanism for ActiveMQ</li></ul></div>
+<div class="wiki-content maincontent"><h1>Initial Configuration</h1><h2>Document Organization</h2><ul><li><link ac:anchor="Required JARs"><plain-text-link-body>#Required JARs</plain-text-link-body></link></li><li><link ac:anchor="Optional JARS"><plain-text-link-body>#Optional JARS</plain-text-link-body></link></li><li><link ac:anchor="Persistence Support"><plain-text-link-body>#Persistence Support</plain-text-link-body></link></li><li><link ac:anchor="Next steps"><plain-text-link-body>#Next steps</plain-text-link-body></link></li><li><link ac:anchor="Additional Resources"><plain-text-link-body>#Additional Resources</plain-text-link-body></link><ul><li><link ac:anchor="Related Reading"><plain-text-link-body>#Related Reading</plain-text-link-body></link></li><li><link ac:anchor="Specifications"><plain-text-link-body>#Specifications</plain-text-link-body></link></li><li><link ac:anchor="Related open source projects"><plain-text-link-body>#Related open source projects</plain-text-link-body></link></li></ul></li></ul><p>Firstly you need to add the jars to your classpath.</p><h2>Required JARs</h2><p>To make ActiveMQ easy to use, the default <strong>activemq-all.jar</strong> comes complete with all the libraries required. If you prefer to have explicit control over all the jars used by ActiveMQ here is the full list of individual jars required</p><ul><li>activemq-broker.jar</li><li>activemq-client.jar</li><li>activeio-core.jar</li><li>activemq-kahadb-store.jar (if you wish to use persistence)</li><li>slf4j-api.jar</li><li>J2EE APIs which could be the j2ee.jar from Sun or your J2EE container or you could use Geronimo's freely distributable geronimo-spec-j2ee.jar. If you are inside a servlet container and being dependent on the j2ee.jar causes you troubles, the parts of the J2EE jar we are dependent on are as follows...<ul><li>geronimo-spec-jms.jar</li><li>geronimo-spec-jta.jar</li><li>geronimo-spec-j2ee-management.jar</li></ul></li></ul><p>If you want to grab a J2EE specification jar we recommend the Apache <a shape="rect" href="https://dist.apache.org/repos/dist/release/geronimo/">repository</a></p><h2>Optional JARS</h2><ul><li>spring.jar - if you wish to use the XML configuration file for configuring the Message Broker</li></ul><ul><li>if you wish to use message persistence then you need to add a persistent jar to your classpath (see below). If you just want a lightweight message bus with no durability you can leave this step out but we highly recommend persistence for production deployments.</li></ul><h2>Persistence Support</h2><p>We support persistence via <link><page ri:content-title="Persistence"></page><plain-text-link-body>Specialized KahaDB file system message store or JDBC</plain-text-link-body></link>. For full explict control over configuration check out the <link><page ri:content-title="Xml Configuration"></page></link>. If you wish to use KahaDB, include kahadb.jar in your classpath. In case of JDBC you'll need to include appropriate database driver.</p><p>If you're just doing some testing or in-VM SEDA based messaging you may wish to disable persistence. You can use the <link><page ri:content-title="Xml Configuration"></page></link> for this.</p><p>In 5.x you can do this by setting the <code>persistent=false</code> property to false either in the <link><page ri:content-title="Xml Configuration"></page></link> or on the <link><page ri:content-title="Configuring Transports"></page><plain-text-link-body>broker URL</plain-text-link-body></link>.</p><h2>Next steps</h2><p>One of the first things you might want to do is <link><page ri:content-title="Run Broker"></page><plain-text-link-body>start a broker</plain-text-link-body></link>. Once you have a broker running you could try some <link><page ri:content-title="Examples"></page><plain-text-link-body>example programs</plain-text-link-body></link></p><p>If you want to write your own application, you can just instantiate an <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a>, configure its properties directly and then you're ready to use the standard JMS API to create Connections, Sessions, MessageProducer and MessageConsumer instances.</p><p>You can also take a look at our <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/">unit tests</a> for more examples on how to use ActiveMQ.</p><h2>Additional Resources</h2><h3>Related Reading</h3><ul><li>Sun's <a shape="rect" href="http://java.sun.com/products/jms/tutorial/">JMS Tutorial</a> is a handy place to start looking at how to use the JMS API directly</li><li>The ActiveMQ <a shape="rect" href="http://activemq.apache.org/">Website</a> for specifics on how to use ActiveMQ</li><li><link><page ri:content-title="Topologies"></page><plain-text-link-body>ActiveMQ Topologies</plain-text-link-body></link></li><li><link><page ri:content-title="Clustering"></page><plain-text-link-body>ActiveMQ Clustering</plain-text-link-body></link></li><li><link><page ri:content-title="Networks of Brokers"></page><plain-text-link-body>ActiveMQ Network of Brokers</plain-text-link-body></link></li><li><a shape="rect" href="http://www.eecs.harvard.edu/~mdw/proj/seda/">Staged Event Driven Architecture (SEDA)</a></li></ul><h3>Specifications</h3><ul><li><a shape="rect" href="http://java.sun.com/j2ee/connector/">Java Connector Architecture 1.5</a></li><li><a shape="rect" href="http://java.sun.com/products/jms/index.jsp">Java Messaging Service</a></li></ul><h3>Related open source projects</h3><ul><li><a shape="rect" href="http://camel.apache.org">Apache Camel</a></li><li><a shape="rect" href="http://geronimo.apache.org/">Apache Geronimo</a></li><li><a shape="rect" href="http://www.hermesjms.com/">Hermes JMS</a></li><li><a shape="rect" href="http://stomp.github.com/">Stomp</a> is an open wire protocol (similar to HTTP) for communicating with MOMs from different languages. It has clients for languages like C, C#, Python, Perl, Ruby etc.</li><li><a shape="rect" href="http://xbean.org/">XBean</a> is used as the default XML configuration mechanism for ActiveMQ</li></ul></div>
diff --git a/installation.xml b/installation.xml
index 0997c93..b8a84e2 100644
--- a/installation.xml
+++ b/installation.xml
@@ -1,22 +1,20 @@
<div class="wiki-content maincontent">
-<ul><li><a shape="rect" href="download.xml">Download</a> a binary distribution of ActiveMQ and unpack it into some directory.</li></ul>
+<ul><li><link><page ri:content-title="Download"></page></link> a binary distribution of ActiveMQ and unpack it into some directory.</li></ul>
<ul><li>To run an ActiveMQ broker, type the following commands from the directory in which you have just unpacked the ActiveMQ distribution.</li></ul>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0e55a374-0c49-4037-bf66-bffb0864ee9d" ac:name="code" ac:schema-version="1"><plain-text-body>
cd bin
activemq
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>The ActiveMQ broker should now run. You can configure the broker by specifying an <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> file as a parameter to the <em>activemq</em> command.</p>
+<p>The ActiveMQ broker should now run. You can configure the broker by specifying an <link><page ri:content-title="Xml Configuration"></page></link> file as a parameter to the <em>activemq</em> command.</p>
-<p>You can now run the <a shape="rect" href="examples.xml">Examples</a> using Ant.</p>
+<p>You can now run the <link><page ri:content-title="Examples"></page></link> using Ant.</p>
-<p>See the <a shape="rect" href="initial-configuration.xml">getting started guide</a> for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code</p>
+<p>See the <link><page ri:content-title="Initial Configuration"></page><link-body>getting started guide</link-body></link> for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code</p>
-<p>If you want to use JNDI to connect to your JMS provider then please view the <a shape="rect" href="jndi-support.xml">JNDI Support</a>. If you are a Spring user you should read about <a shape="rect" href="spring-support.xml">Spring Support</a></p></div>
+<p>If you want to use JNDI to connect to your JMS provider then please view the <link><page ri:content-title="JNDI Support"></page></link>. If you are a Spring user you should read about <link><page ri:content-title="Spring Support"></page></link></p></div>
diff --git a/integrating-apache-activemq-with-glassfish.xml b/integrating-apache-activemq-with-glassfish.xml
index 42cbc8b..4c33d7e 100644
--- a/integrating-apache-activemq-with-glassfish.xml
+++ b/integrating-apache-activemq-with-glassfish.xml
@@ -1,24 +1,14 @@
-<div class="wiki-content maincontent"><h1 id="IntegratingApacheActiveMQwithGlassfish-General">General</h1><p>See this article for a description of how to connect Glassfish 3 to an ActiveMQ 5 broker, and consume messages using a Message Driven Bean: <a shape="rect" class="external-link" href="http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/" rel="nofollow">http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/</a></p><h1 id="IntegratingApacheActiveMQwithGlassfish-Glassfish4.1">Glassfish 4.1</h1><p> </p><ol><li>Add resource adapter<br clear="none"><ol><li>Download the resource-adapter file suitable to your broker version:<br clear="none"><a shape="rect" class="external-link" href="http://repo1.maven.org/maven2/org/apache/activemq/activemq-rar/" rel="nofollow">http://repo1.maven.org/maven2/org/apache/activemq/activemq-rar/</a></li><li><p>Deploy the  resource adapter with the name "activemq-rar"</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/asadmin deploy --type rar --name activemq-rar /tmp/activemq-rar-5.11.1.rar]]></script>
-</div></div></li><li><p>Configure resource adapter <br clear="none">(Failover Setup)</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/asadmin create-resource-adapter-config \
- --property ServerUrl='failover\:(tcp\://broker-c1.foobar.local\:61616,tcp\://broker-c2.foobar.local\:61616,tcp\://broker-c3.foobar.local\:61616)?initialReconnectDelay\=2000&jms.useCompression\=true':UserName='admin':Password='admin' activemq-rar]]></script>
-</div></div></li></ol></li><li><p> Create connector connection pool</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/asadmin create-connector-connection-pool \
+<div class="wiki-content maincontent"><h1>General</h1><p>See this article for a description of how to connect Glassfish 3 to an ActiveMQ 5 broker, and consume messages using a Message Driven Bean: <a shape="rect" class="external-link" href="http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/" rel="nofollow">http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/</a></p><h1>Glassfish 4.1</h1><p> </p><ol><li>Add resource adapter<br clear="none"><ol><li>Download the resource-adapter file suitable to your broker version:<br clear="none"><a shape="rect" href="http://repo1.maven.org/maven2/org/apache/activemq/activemq-rar/">http://repo1.maven.org/maven2/org/apache/activemq/activemq-rar/</a></li><li><p>Deploy the  resource adapter with the name "activemq-rar"</p><structured-macro ac:macro-id="20855b14-bd0e-4956-afcd-f43690b8e104" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/asadmin deploy --type rar --name activemq-rar /tmp/activemq-rar-5.11.1.rar</plain-text-body></structured-macro></li><li><p>Configure resource adapter <br clear="none">(Failover Setup)</p><structured-macro ac:macro-id="ef4b601a-2fdc-447c-83df-8fa0e0de1745" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/asadmin create-resource-adapter-config \
+ --property ServerUrl='failover\:(tcp\://broker-c1.foobar.local\:61616,tcp\://broker-c2.foobar.local\:61616,tcp\://broker-c3.foobar.local\:61616)?initialReconnectDelay\=2000&jms.useCompression\=true':UserName='admin':Password='admin' activemq-rar</plain-text-body></structured-macro></li></ol></li><li><p> Create connector connection pool</p><structured-macro ac:macro-id="800ed343-3e5a-49cd-97a9-8ba10a1e12a8" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/asadmin create-connector-connection-pool \
--raname activemq-rar \
--connectiondefinition javax.jms.ConnectionFactory \
--ping true --isconnectvalidatereq true \
- jms/myConnectionPool]]></script>
-</div></div></li><li><p>Create a connector resource (JNDI-Mapping for connection pool)</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/asadmin create-connector-resource \
+ jms/myConnectionPool</plain-text-body></structured-macro></li><li><p>Create a connector resource (JNDI-Mapping for connection pool)</p><structured-macro ac:macro-id="e4c5b6ab-e476-4573-bb15-fad7672dcf6c" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/asadmin create-connector-resource \
--poolname jms/myConnectionPool \
- jms/myConnectionFactory]]></script>
-</div></div></li><li><p>Configure JNDI mapping for a queue</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/asadmin create-admin-object \
+ jms/myConnectionFactory</plain-text-body></structured-macro></li><li><p>Configure JNDI mapping for a queue</p><structured-macro ac:macro-id="30bcf588-ad7d-4eac-9d95-625de8800f76" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/asadmin create-admin-object \
--raname activemq-rar \
--restype javax.jms.Queue \
--property PhysicalName=MY.MAGIC.OUT \
jms/queue/MY.MAGIC.OUT
-]]></script>
-</div></div></li><li>Deploy your message driven beans and use the configured jndi names</li></ol></div>
+</plain-text-body></structured-macro></li><li>Deploy your message driven beans and use the configured jndi names</li></ol></div>
diff --git a/integrating-apache-activemq-with-jboss.xml b/integrating-apache-activemq-with-jboss.xml
index 4a5a397..53905a3 100644
--- a/integrating-apache-activemq-with-jboss.xml
+++ b/integrating-apache-activemq-with-jboss.xml
@@ -1,48 +1,43 @@
-<div class="wiki-content maincontent"><h1 id="IntegratingApacheActiveMQwithJBoss-IntegratingApacheActiveMQwithJBoss">Integrating Apache ActiveMQ with JBoss</h1>
+<div class="wiki-content maincontent"><h1>Integrating Apache ActiveMQ with JBoss</h1>
-<p>Integration with application servers is a common scenario in the enterprise Java world, especially when it comes to messaging. <a shape="rect" class="external-link" href="http://activemq.org/" rel="nofollow">ActiveMQ</a> is a JMS 1.1 compliant, open source, Apache Licensed, message oriented middleware (MOM) with <a shape="rect" class="external-link" href="http://activemq.org/site/changes-in-40.html" rel="nofollow">many</a>, <a shape="rect" class="external-link" href="http://activemq.org/site/new-features-in-41.html" rel="nofollow">many</a> features far beyond the JMS specification. ActiveMQ offers many different <a shape="rect" class="external-link" href="http://activemq.org/site/connectivity.html" rel="nofollow">points of connectivity</a>, many <a shape="rect" class="external-link" href="http://activemq.org/site/cross-language-clients.html" rel="nofollow">cross language clients</a> and many <a shape="rect" class="external-link" href="http://activemq.org/site/protocols.html" rel="nofollow">pluggable transport protocols</a> including integration with any J2EE 1.4 application server.</p>
+<p>Integration with application servers is a common scenario in the enterprise Java world, especially when it comes to messaging. <a shape="rect" href="http://activemq.org/">ActiveMQ</a> is a JMS 1.1 compliant, open source, Apache Licensed, message oriented middleware (MOM) with <a shape="rect" href="http://activemq.org/site/changes-in-40.html">many</a>, <a shape="rect" href="http://activemq.org/site/new-features-in-41.html">many</a> features far beyond the JMS specification. ActiveMQ offers many different <a shape="rect" href="http://activemq.org/site/connectivity.html">points of connectivity</a>, many <a shape="rect" href="http://activemq.org/site/cross-language-clients.html">cross language clients</a> and many <a shape="rect" href="http://activemq.org/site/protocols.html">pluggable transport protocols</a> including integration with any J2EE 1.4 application server.</p>
-<p>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 shape="rect" class="external-link" href="http://www.activemq.org/site/jboss-integration.html" rel="nofollow">a bit of documentation</a> 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.</p>
+<p>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 shape="rect" href="http://www.activemq.org/site/jboss-integration.html">a bit of documentation</a> 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.</p>
<p>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.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-Requirements">Requirements</h2>
+<h2>Requirements</h2>
<p>Below are the software requirements for this article with links to download each:</p>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.org/site/download.html" rel="nofollow">Apache ActiveMQ 4.0.1+</a></li><li><a shape="rect" class="external-link" href="http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591" rel="nofollow">JBoss 4.0.4+</a></li><li><a shape="rect" class="external-link" href="http://www.java.com/en/download/index.jsp" rel="nofollow">Sun Java 1.5+</a></li><li><a shape="rect" class="external-link" href="http://ant.apache.org/bindownload.cgi">Apache Ant 1.6+</a></li></ul>
+<ul><li><a shape="rect" href="http://activemq.org/site/download.html">Apache ActiveMQ 4.0.1+</a></li><li><a shape="rect" href="http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591">JBoss 4.0.4+</a></li><li><a shape="rect" href="http://www.java.com/en/download/index.jsp">Sun Java 1.5+</a></li><li><a shape="rect" href="http://ant.apache.org/bindownload.cgi">Apache Ant 1.6+</a></li></ul>
<p>Though this article is using Unix, the installation and integration will work on any platform running Sun Java. It is recommended that each piece of software be downloaded before working through the steps is this article. Once each piece of software has been downloaded, proceed to the first step.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-InstalltheJ2SE1.5">Install the J2SE 1.5</h2>
+<h2>Install the J2SE 1.5</h2>
<p>The first step in this process is to install Java 1.5 and verify that it runs correctly. Using the link above, find, download and install the correct version of Java for your platform. Once Java is installed and in the PATH, test it to see that it runs correctly using the following command:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9bc24ef3-40ca-44c4-8184-3dc2558516dc" ac:name="code" ac:schema-version="1"><plain-text-body>
$ java -version
-java version "1.5.0_06"
+java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Depending upon your platform and the exact build number of Java 1.5, your output may vary slightly. As long as it's Java 1.5 and the version information is output, you should be ready to proceed to the next step.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-InstallApacheAnt">Install Apache Ant</h2>
+<h2>Install Apache Ant</h2>
<p>The second step is to install Apache Ant. Simply download it using the link above, expand somewhere on your hard drive and place the <code>bin</code> directory in the PATH. This will allow you to test it quickly using the commands below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0b584001-7c6f-4418-a373-2baeaa6b5c3b" ac:name="code" ac:schema-version="1"><plain-text-body>
$ ant -version
Apache Ant version 1.6.2 compiled on July 16 2004
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>As long as you see the version output above, Ant should be usable. If you did not see the version output or received an error, consult the Ant documentation or mailing list archives to work out the issue. Please note that Ant is not used until the end of this whole exercise to test the integration.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-InstalltheJBossApplicationServer">Install the JBoss Application Server</h2>
+<h2>Install the JBoss Application Server</h2>
<p>The third step in this process is to install JBoss and make sure it runs correctly before installing and configuring ActiveMQ. Upon downloading JBoss-4.0.4, expand it in a place where it can create a directory. Next, run the server using the following commands:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ecdb3355-5bad-42a4-a5ee-0ba25b1d0b45" ac:name="code" ac:schema-version="1"><plain-text-body>
$ cd jboss-4.0.4.GA
$ ./bin/run.sh -c default
=========================================================================
@@ -74,19 +69,17 @@
...
15:35:17,360 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)]
Started in 22s:238ms
-]]></script>
-</div></div>
-<p>The first few lines of output from the JBoss startup indicates the configuration being used but the last line is the most important one. It tells you that JBoss has been started successfully on your system. For an extra measure of assurance, visit <a shape="rect" class="external-link" href="http://localhost:8080/web-console/" rel="nofollow">http://localhost:8080/web-console/</a> in a web browser to make sure you are able to see the JBoss web console. If you can see this console, everything should be ready to go.</p>
+</plain-text-body></structured-macro>
+<p>The first few lines of output from the JBoss startup indicates the configuration being used but the last line is the most important one. It tells you that JBoss has been started successfully on your system. For an extra measure of assurance, visit <a shape="rect" href="http://localhost:8080/web-console/">http://localhost:8080/web-console/</a> in a web browser to make sure you are able to see the JBoss web console. If you can see this console, everything should be ready to go.</p>
-<p>As a side note, the left-hand side of the web-console requires that the <a shape="rect" class="external-link" href="http://java.sun.com/products/plugin/" rel="nofollow">Java plugin</a> be properly installed. This is supposed to take place when installing the J2SE, so if it did not work correctly for you, I suggest that you consult some documentation about any errors you may be seeing. The Java plugin is not required for JBoss or ActiveMQ to function properly, it is simply for the JBoss web-console.</p>
+<p>As a side note, the left-hand side of the web-console requires that the <a shape="rect" href="http://java.sun.com/products/plugin/">Java plugin</a> be properly installed. This is supposed to take place when installing the J2SE, so if it did not work correctly for you, I suggest that you consult some documentation about any errors you may be seeing. The Java plugin is not required for JBoss or ActiveMQ to function properly, it is simply for the JBoss web-console.</p>
<p>Once JBoss is installed properly, shut it down using either the shutdown script or by simply typing ctrl-c to activate the shutdown hook. Once it is shut down, proceed to the next step.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-PrepareforIntegratingApacheActiveMQwiththeJBossApplicationServer">Prepare for Integrating Apache ActiveMQ with the JBoss Application Server</h2>
+<h2>Prepare for Integrating Apache ActiveMQ with the JBoss Application Server</h2>
<p>The fourth step is to prepare your environment for integrating ActiveMQ with JBoss. If you haven't done so already, download Apache ActiveMQ using the link above. As of the writing of this article, the latest released version is 4.0.2-RC4. Upon downloading this archive, expand it in a place where it can create a directory, preferably in the same location where JBoss was expanded. Verify that the ActiveMQ RAR file is included using the following commands:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3a69cbcd-8308-4e16-806b-e40caeb29677" ac:name="code" ac:schema-version="1"><plain-text-body>
$ cd ./incubator-activemq-4.0.2.tar.gz
$ jar tvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar
0 Mon Sep 25 19:00:50 MDT 2006 META-INF/
@@ -107,25 +100,20 @@
358085 Tue Aug 01 12:23:26 MDT 2006 log4j-1.2.12.jar
523 Mon Sep 25 19:00:50 MDT 2006 META-INF/DISCLAIMER.txt
11359 Mon Sep 25 19:00:50 MDT 2006 META-INF/LICENSE.txt
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This is simply a table of contents of the RAR file. There should only be one reason that this will fail - an incomplete download of the ActiveMQ tarball or zip file. Beyond that, depending on the version you download, some of the library versions may be slightly different.</p>
<p>Now go back to the JBoss installation and create a directory for ActiveMQ in the JBoss deploy directory for the default JBoss context. Below are the commands to achieve this task:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="dfbdd1ea-39da-4687-ad6a-a42d8947ab30" ac:name="code" ac:schema-version="1"><plain-text-body>
$ mkdir /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
$ cd /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
$ pwd
/opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-]]></script>
-</div></div>
-<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;">
-<p><strong><em>NOTE:</em></strong> The creation of a directory is not required but is the easiest way to set up the ActiveMQ RAR when you're just getting started. This is due to the flexibility it affords during the development phase for the configuration to be changed very easily. The alternative is to JAR up the directory as a RAR file once the configuration is solid enough that it no longer needs to be changed. But leaving everything in a directory during development is the easiest path.</p>
-</div></div>
+</plain-text-body></structured-macro>
+<structured-macro ac:macro-id="8b393505-f091-411a-ae01-7fa559ed289b" ac:name="panel" ac:schema-version="1"><parameter ac:name="bgColor">#ccccff</parameter><rich-text-body>
+<p><strong><em>NOTE:</em></strong> The creation of a directory is not required but is the easiest way to set up the ActiveMQ RAR when you're just getting started. This is due to the flexibility it affords during the development phase for the configuration to be changed very easily. The alternative is to JAR up the directory as a RAR file once the configuration is solid enough that it no longer needs to be changed. But leaving everything in a directory during development is the easiest path.</p></rich-text-body></structured-macro>
<p>Now expand the activemq-ra-4.0.2.rar into the current working directory:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b59168c6-1886-46c9-8b3b-c33ae6953b52" ac:name="code" ac:schema-version="1"><plain-text-body>
jar xvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar
created: META-INF/
inflated: META-INF/MANIFEST.MF
@@ -145,11 +133,9 @@
inflated: log4j-1.2.12.jar
inflated: META-INF/DISCLAIMER.txt
inflated: META-INF/LICENSE.txt
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Below is a quick listing of the contents of that directory:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="cd5b60d0-b463-4799-862a-2e6bef89f317" ac:name="code" ac:schema-version="1"><plain-text-body>
$ ls -l
total 12848
drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF
@@ -164,21 +150,18 @@
-rw-r--r-- 1 bsnyder bsnyder 358085 Oct 16 16:27 log4j-1.2.12.jar
-rw-r--r-- 1 bsnyder bsnyder 1901653 Oct 16 16:27 spring-1.2.6.jar
-rw-r--r-- 1 bsnyder bsnyder 94713 Oct 16 16:27 xbean-spring-2.2.jar
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Now it's time to configure ActiveMQ.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-ConfiguringApacheActiveMQ">Configuring Apache ActiveMQ</h2>
+<h2>Configuring Apache ActiveMQ</h2>
<p>The fifth step is to actually configure ActiveMQ for integration with JBoss. Remember that you should be sitting in the following directory:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ec3c4d38-41bf-40f1-9deb-3767135411c9" ac:name="code" ac:schema-version="1"><plain-text-body>
/opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>You may or may not have installed JBoss in <code>/opt</code>, that doesn't particularly matter. What does matter is that you're sitting in the directory that was created above to hold the contents of the expanded ActiveMQ RAR file.</p>
-<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;">
-<p><strong><em>NOTE:</em></strong> A RAR file is a Resource adapter ARchive (RAR). Resource adapters are a concept from the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/" rel="nofollow">J2EE Connector Architecture (JCA)</a> and are used to interface with Enterprise Information Systems (EIS), i.e., systems external to the application server (e.g., relational databases, mainframes, MOMs, accounting systems, etc.). Resource adapters are often referred to as J2EE connectors and are very similar to the concept of a device driver for, say, a printer in that they contain information specific to connecting to a particular system. The difference with JCA is that that connection has been formalized in specification for Java. So the overall concepts of JCA is for connection to any EIS, but what does that mean? JCA 1.5 provides connectivity and more via the following contracts:</p>
+<structured-macro ac:macro-id="c0800a73-554e-4dc9-9f81-d0fe7bd1cdfc" ac:name="panel" ac:schema-version="1"><parameter ac:name="bgColor">#ccccff</parameter><rich-text-body>
+<p><strong><em>NOTE:</em></strong> A RAR file is a Resource adapter ARchive (RAR). Resource adapters are a concept from the <a shape="rect" href="http://java.sun.com/j2ee/connector/">J2EE Connector Architecture (JCA)</a> and are used to interface with Enterprise Information Systems (EIS), i.e., systems external to the application server (e.g., relational databases, mainframes, MOMs, accounting systems, etc.). Resource adapters are often referred to as J2EE connectors and are very similar to the concept of a device driver for, say, a printer in that they contain information specific to connecting to a particular system. The difference with JCA is that that connection has been formalized in specification for Java. So the overall concepts of JCA is for connection to any EIS, but what does that mean? JCA 1.5 provides connectivity and more via the following contracts:</p>
<p>Version 1.0 Contracts</p>
@@ -192,45 +175,39 @@
<ul><li>Lifecycle Management Contract: Lets the application server manage the lifecycle – that is, the startup and shutdown functionality – of the resource adapter.</li><li>Work Management Contract: Allows the resource adapter to do work by submitting it to an application server for execution. Since the application server does the work for the resource adapter, the resource adapter needn't worry about thread management. Instead, the application server manages this aspect efficiently and can use thread pooling if necessary. Although the work management contract is not required (the resource adapter can choose to manage its own thread for work), it is definitely recommended.</li><li>Transaction Inflow Contract: Allows a resource adapter to propagate an imported transaction to an application server, as well as flow-in transaction completion and crash recovery initiated by an EIS.</li><li>Message Inflow Contract: Allows the resource adapter to synchronously or asynchronously deliver messages to endpoints in the application server, irrespective of message style, semantics, and infrastructure.</li></ul>
-<p><sub>Quoted from</sub> <sub><a shape="rect" class="external-link" href="http://java.sun.com/developer/technicalArticles/J2EE/connectorarch1_5/" rel="nofollow"><sub>What's New in the J2EE Connector Architecture 1.5</sub></a></sub></p>
+<p><sub>Quoted from</sub> <sub><a shape="rect" href="http://java.sun.com/developer/technicalArticles/J2EE/connectorarch1_5/"><sub>What's New in the J2EE Connector Architecture 1.5</sub></a></sub></p>
-<p>For more information about JCA, please consult the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/index.jsp" rel="nofollow">J2EE Connector Architecture documentation</a>.</p>
-</div></div>
+<p>For more information about JCA, please consult the <a shape="rect" href="http://java.sun.com/j2ee/connector/index.jsp">J2EE Connector Architecture documentation</a>.</p></rich-text-body></structured-macro>
<p>Open the <code>META-INF/ra.xml</code> file and look for the following section:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="60f6b9af-051c-4c7d-9266-2ceb2c9a4bbd" ac:name="code" ac:schema-version="1"><parameter ac:name="title">META-INF/ra.xml</parameter><plain-text-body>
<config-property>
<description>
The URL to the ActiveMQ server that you want this connection to connect to. If using
- an embedded broker, this value should be 'vm://localhost'.
+ an embedded broker, this value should be 'vm://localhost'.
</description>
<config-property-name>ServerUrl</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>tcp://localhost:61616</config-property-value>
<!-- <config-property-value>vm://localhost</config-property-value> -->
</config-property>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The section above is used to tell the ActiveMQ RAR where ActiveMQ is located. By default, the in-VM protocol is commented out in favor of the tcp protocol. This will find ActiveMQ running on any interface on the localhost on port 61616. It's ok to just leave this alone if you don't mind the inefficiency of communicating within the JVM via TCP. However, it is recommended that <code>vm://</code> transport be used for an embedded broker, so comment out the <code>tcp://</code> transport and uncomment the <code>vm://</code> transport. Below is an example of this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="fdda2ef7-5c59-424b-bb81-8fe635e3e14f" ac:name="code" ac:schema-version="1"><parameter ac:name="title">META-INF/ra.xml</parameter><plain-text-body>
<config-property>
<description>
The URL to the ActiveMQ server that you want this connection to connect to. If using
- an embedded broker, this value should be 'vm://localhost'.
+ an embedded broker, this value should be 'vm://localhost'.
</description>
<config-property-name>ServerUrl</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<!-- <config-property-value>tcp://localhost:61616</config-property-value> -->
<config-property-value>vm://localhost</config-property-value>
</config-property>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Because we're embedding ActiveMQ inside of JBoss, it is more efficient to use the <code>vm://</code> transport, rather than to perform messaging over the <code>tcp://</code> transport.</p>
<p>Now look further down the <code>META-INF/ra.xml</code> file and locate the following section:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b727474f-93c3-4537-8228-296b250ffc14" ac:name="code" ac:schema-version="1"><parameter ac:name="title">META-INF/ra.xml</parameter><plain-text-body>
<config-property>
<description>
Sets the XML configuration file used to configure the embedded ActiveMQ broker via
@@ -248,11 +225,9 @@
<config-property-value>xbean:broker-config.xml</config-property-value>
-->
</config-property>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The section above needs to be changed to uncomment the second to last line and remove/replace the empty element that is above it. Below is an example of how this should be changed:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="cc4ec3ed-0668-4861-b33c-d5be8a95225c" ac:name="code" ac:schema-version="1"><parameter ac:name="title">META-INF/ra.xml</parameter><plain-text-body>
<config-property>
<description>
Sets the XML configuration file used to configure the embedded ActiveMQ broker via
@@ -267,80 +242,67 @@
<config-property-type>java.lang.String</config-property-type>
<config-property-value>xbean:broker-config.xml</config-property-value>
</config-property>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This change tells the ActiveMQ RAR to read a configuration file named <code>broker-config.xml</code> (the <code>xbean:</code> that proceeds the filename is simply a hint to class doing the reading of the configuration file) which is located on the CLASSPATH. In this case, the <code>broker-config.xml</code> file is located in the <code>activemq-ra.rar</code> directory. Save the changes to that file and then open the <code>broker-config.xml</code> file.</p>
<p>The <code>broker-config.xml</code> file <em>is</em> the ActiveMQ configuration file. This is the file used to configure ActiveMQ. The default contents of this file are usable, but should be customized to suit your environment. There are several items of note about this configuration. The most prominent sections to note in this file are the <code><persistenceAdapter></code> element and the <code><transportConnectors></code> and <code><networkConnectors></code> elements as seen below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>broker-config.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<beans xmlns="http://activemq.org/config/1.0">
+<structured-macro ac:macro-id="af48af35-393f-417b-906d-f17f34eabda8" ac:name="code" ac:schema-version="1"><parameter ac:name="title">broker-config.xml</parameter><plain-text-body>
+<beans xmlns="http://activemq.org/config/1.0">
- <broker useJmx="true">
+ <broker useJmx="true">
...
<persistenceAdapter>
- <journaledJDBC journalLogFiles="5" dataDirectory="activemq-data"/>
+ <journaledJDBC journalLogFiles="5" dataDirectory="activemq-data"/>
<!-- To use a different datasource, use th following syntax : -->
<!--
- <journaledJDBC journalLogFiles="5" dataDirectory="../data" dataSource="#postgres-ds"/>
+ <journaledJDBC journalLogFiles="5" dataDirectory="../data" dataSource="#postgres-ds"/>
-->
</persistenceAdapter>
<transportConnectors>
<!-- prefixing a connector with discovery: causes the connector to be advertiesed over rendezvous -->
- <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
+ <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
</transportConnectors>
<networkConnectors>
<!-- by default just auto discover the other brokers -->
- <networkConnector uri="multicast://default"/>
+ <networkConnector uri="multicast://default"/>
<!--
- <networkConnector uri="static://(tcp://host1:61616,tcp://host2:61616)"/>
+ <networkConnector uri="static://(tcp://host1:61616,tcp://host2:61616)"/>
-->
</networkConnectors>
</broker>
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The first change to this file is to add the brokerName attribute to the broker element and provide a name:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker useJmx="true" brokerName="bruce.broker1">
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="03cf582d-73c3-45a2-bd0d-9b0ea96e191a" ac:name="code" ac:schema-version="1"><plain-text-body>
+<broker useJmx="true" brokerName="bruce.broker1">
+</plain-text-body></structured-macro>
<p>In addition, this same name is used further down the configuration to provide a name for the <code><transportConnector></code> element:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<transportConnector name="bruce.broker1" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="34a54822-38c1-464d-9596-05153a1be414" ac:name="code" ac:schema-version="1"><plain-text-body>
+<transportConnector name="bruce.broker1" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
+</plain-text-body></structured-macro>
<p>Now we'll tell ActiveMQ not to initialize JMX because we'll use the existing one that JBoss has:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6722ef5d-9c32-4fba-89a9-405bf8678a2c" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<!-- put the following as the first child of the broker tag -->
-<managementContext><!-- we'll use an existing one (JBoss) instead of creating one -->
- <managementContext createConnector="false"/>
+<managementContext><!-- we'll use an existing one (JBoss) instead of creating one -->
+ <managementContext createConnector="false"/>
</managementContext>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The <code><persistenceAdapter></code> element should be reconfigured to store its data in an appropriate place. On JBoss, that's most likely within the "data" directory of the server configuration you're using. We're going to set this dynamically using an XBean and Spring feature that allows us to inject system properties values into the configuration. First this needs to be enabled:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="808a9522-c308-4270-9e82-4374dd0ecebb" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<!-- put the following as the first child of the beans element -->
-<bean xmlns="" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
-]]></script>
-</div></div>
+<bean xmlns="" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+</plain-text-body></structured-macro>
<p>Now, modify the <code>dataDirectory</code> attribute of the <code>journaledJDBC</code> element to be the following: <code>${jboss.server.data.dir}/activemq</code>.</p>
-<p>The <code><transportConnectors></code> element is used to advertise the ActiveMQ broker for client-to-broker communications and the <code><networkConnectors></code> element advertises the ActiveMQ broker for broker-to-broker communications. The default configuration is to use the ActiveMQ <a shape="rect" class="external-link" href="http://www.activemq.org/site/multicast-transport-reference.html" rel="nofollow">multicast transport</a> 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.</p>
-<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;">
-<p><strong><em>NOTE:</em></strong> 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 <a shape="rect" class="external-link" href="http://www.activemq.org/site/xbean-xml-reference-41.html" rel="nofollow">ActiveMQ 4.1 XML Reference</a>.</p>
-</div></div>
+<p>The <code><transportConnectors></code> element is used to advertise the ActiveMQ broker for client-to-broker communications and the <code><networkConnectors></code> element advertises the ActiveMQ broker for broker-to-broker communications. The default configuration is to use the ActiveMQ <a shape="rect" href="http://www.activemq.org/site/multicast-transport-reference.html">multicast transport</a> 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.</p>
+<structured-macro ac:macro-id="b2fd7dca-0195-45f9-beaa-a35e3502a0e4" ac:name="panel" ac:schema-version="1"><parameter ac:name="bgColor">#ccccff</parameter><rich-text-body>
+<p><strong><em>NOTE:</em></strong> 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 <a shape="rect" href="http://www.activemq.org/site/xbean-xml-reference-41.html">ActiveMQ 4.1 XML Reference</a>.</p></rich-text-body></structured-macro>
<p>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:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="99275948-d5a3-4e82-9827-5827c1f58ed4" ac:name="code" ac:schema-version="1"><plain-text-body>
$ cd jboss-4.0.4.GA
$ ./bin/run.sh -c default
=========================================================================
@@ -372,20 +334,18 @@
...
15:35:17,360 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)]
Started in 28s:576ms
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>As long as JBoss comes up without error, you're ready to move on to the next step.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-ConfiguringJBoss">Configuring JBoss</h2>
+<h2>Configuring JBoss</h2>
-<p>The sixth step is to configure JBoss to initialize and start ActiveMQ whenever JBoss starts up. This is accomplished using an XML file that abides by the <a shape="rect" class="external-link" href="http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd" rel="nofollow">JBoss JCA DTD</a> for data sources. Like most other Java application servers on the market, the JBoss architecture uses the J2EE Connector Architecture to manage connections of any kind including JDBC, JMS, etc. and the JBoss JCA DTD denotes the allowed contents for creating an XML data source instance to configure JBoss JCA. Below is an example XML data source instance for use with JBoss:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>activemq-jms-ds.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
+<p>The sixth step is to configure JBoss to initialize and start ActiveMQ whenever JBoss starts up. This is accomplished using an XML file that abides by the <a shape="rect" href="http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd">JBoss JCA DTD</a> for data sources. Like most other Java application servers on the market, the JBoss architecture uses the J2EE Connector Architecture to manage connections of any kind including JDBC, JMS, etc. and the JBoss JCA DTD denotes the allowed contents for creating an XML data source instance to configure JBoss JCA. Below is an example XML data source instance for use with JBoss:</p>
+<structured-macro ac:macro-id="71943892-d21f-4db7-bcaf-463eb91e23d2" ac:name="code" ac:schema-version="1"><parameter ac:name="title">activemq-jms-ds.xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connection-factories
- PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
- "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd">
+ PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd">
<connection-factories>
@@ -423,26 +383,24 @@
<idle-timeout-minutes>3</idle-timeout-minutes>
</tx-connection-factory>
- <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
- <attribute name="JNDIName">activemq/queue/outbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
- <attribute name="Type">javax.jms.Queue</attribute>
- <attribute name="Properties">PhysicalName=queue.outbound</attribute>
+ <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
+ <attribute name="JNDIName">activemq/queue/outbound</attribute>
+ <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
+ <attribute name="Type">javax.jms.Queue</attribute>
+ <attribute name="Properties">PhysicalName=queue.outbound</attribute>
</mbean>
- <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.topic:name=inboundTopic">
- <attribute name="JNDIName">activemq/topic/inbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
- <attribute name="Type">javax.jms.Topic</attribute>
- <attribute name="Properties">PhysicalName=topic.inbound</attribute>
+ <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.topic:name=inboundTopic">
+ <attribute name="JNDIName">activemq/topic/inbound</attribute>
+ <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
+ <attribute name="Type">javax.jms.Topic</attribute>
+ <attribute name="Properties">PhysicalName=topic.inbound</attribute>
</mbean>
</connection-factories>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This XML instance configures a JMS <code>QueueConnectionFactory</code> and a JMS <code>TopicConnectionFactory</code> and makes them available via JNDI. Also defined in this file are some {{AdminObject}}s which are used to specify a topic and a queue. This file should be dropped into the JBoss deploy directory. Its name (*-ds.xml) will cause it to be picked up by the JBoss deployer upon startup. Speaking of which, once this file is in place, a quick smoke test can be performed by simply starting up the JBoss server. Below is an example of the output that should be seen:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4a3ffbcf-5e58-42dd-8c5f-1d77b501c805" ac:name="code" ac:schema-version="1"><plain-text-body>
=========================================================================
JBoss Bootstrap Environment
@@ -470,7 +428,7 @@
22:55:48,704 INFO [Server] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
22:55:48,706 INFO [Server] Root Deployment Filename: jboss-service.xml
22:55:49,092 INFO [ServerInfo] Java version: 1.5.0_06,Apple Computer, Inc.
-22:55:49,101 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-64,"Apple Computer, Inc."
+22:55:49,101 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-64,"Apple Computer, Inc."
22:55:49,102 INFO [ServerInfo] OS-System: Mac OS X 10.4.8,i386
22:55:49,803 INFO [Server] Core system initialized
22:55:53,379 INFO [WebService] Using RMI server codebase: http://rattlesnake:8083/
@@ -511,10 +469,10 @@
[org.apache.xbean.spring.context.ClassPathXmlApplicationContext;hashCode=13887543]
22:56:07,773 INFO [CollectionFactory] JDK 1.4+ collections available
22:56:07,778 INFO [ClassPathXmlApplicationContext] Unable to locate MessageSource with name
-'messageSource': using default
+'messageSource': using default
[org.springframework.context.support.DelegatingMessageSource@5fee96]
22:56:07,781 INFO [ClassPathXmlApplicationContext] Unable to locate ApplicationEventMulticaster
-with name 'applicationEventMulticaster': using default
+with name 'applicationEventMulticaster': using default
[org.springframework.context.event.SimpleApplicationEventMulticaster@78c714]
22:56:07,783 INFO [DefaultListableBeanFactory] Pre-instantiating singletons in factory
[org.springframework.beans.factory.support.DefaultListableBeanFactory
@@ -546,17 +504,17 @@
22:56:11,847 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
.../deploy/mail-ra.rar
22:56:12,251 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=activemq/QueueConnectionFactory' to
-JNDI name 'java:activemq/QueueConnectionFactory'
+'jboss.jca:service=ConnectionFactoryBinding,name=activemq/QueueConnectionFactory' to
+JNDI name 'java:activemq/QueueConnectionFactory'
22:56:12,258 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=activemq/TopicConnectionFactory' to
-JNDI name 'java:activemq/TopicConnectionFactory'
-22:56:12,265 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQQueue'
-at 'activemq/queue/outbound'
-22:56:12,330 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQTopic'
-at 'activemq/topic/inbound'
+'jboss.jca:service=ConnectionFactoryBinding,name=activemq/TopicConnectionFactory' to
+JNDI name 'java:activemq/TopicConnectionFactory'
+22:56:12,265 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQQueue'
+at 'activemq/queue/outbound'
+22:56:12,330 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQTopic'
+at 'activemq/topic/inbound'
22:56:13,246 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
-'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
+'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
22:56:13,842 INFO [A] Bound to JNDI name: queue/A
22:56:13,845 INFO [B] Bound to JNDI name: queue/B
22:56:13,846 INFO [C] Bound to JNDI name: queue/C
@@ -569,24 +527,22 @@
22:56:13,994 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
22:56:14,055 INFO [DLQ] Bound to JNDI name: queue/DLQ
22:56:14,375 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
+'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
22:56:14,525 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
22:56:14,991 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
22:56:15,071 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
22:56:15,082 INFO [JkMain] Jk running ID=0 time=0/25 config=null
22:56:15,108 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)]
Started in 26s:398ms
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Note the startup messages from both ActiveMQ and from the <code>AdminObject}}s creating an {{ActiveMQQueue</code> and an <code>ActiveMQTopic</code>. These are good indications that the configuration is correct, but needs to be verified a bit further. This is covered in the next section.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-TestingtheIntegration">Testing the Integration</h2>
+<h2>Testing the Integration</h2>
<p>The seventh and final step is to perform a slightly more comprehensive smoke test of the integration. This can be accomplished using Apache Ant via the examples that come with the ActiveMQ binary distribution. An Ant build.xml file is included which provides easy access to a simple consumer and a simple producer. The producer will be used to send messages that are received by the consumer. To proceed with this testing, just follow the steps below:</p>
<ol><li>In the first terminal, start up JBoss. The same startup script can be used here as was used above.</li><li>In the second terminal, use the commands below to run the ActiveMQ consumer:
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ cd /opt/incubator-activemq-4.0.2/examples #note in activemq v5 the directory is just "example" not "examples"
+<structured-macro ac:macro-id="83da24fc-8569-41f8-98e1-80cd0847b639" ac:name="code" ac:schema-version="1"><plain-text-body>
+$ cd /opt/incubator-activemq-4.0.2/examples #note in activemq v5 the directory is just "example" not "examples"
$ ant consumer
Buildfile: build.xml
@@ -603,10 +559,8 @@
[java] Consuming queue: TEST.FOO
[java] Using non-durable subscription
[java] We are about to wait until we consume: 10 message(s) then we will shutdown
-]]></script>
-</div></div></li><li>In the third terminal, use the commands below to run the ActiveMQ producer:
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+</plain-text-body></structured-macro></li><li>In the third terminal, use the commands below to run the ActiveMQ producer:
+<structured-macro ac:macro-id="b1fdb2dd-302a-4340-9223-be539c22f866" ac:name="code" ac:schema-version="1"><plain-text-body>
$ cd /opt/incubator-activemq-4.0.2/examples
$ ant producer
Buildfile: build.xml
@@ -680,8 +634,7 @@
[java] }
[java] }
[java] }
-]]></script>
-</div></div></li></ol>
+</plain-text-body></structured-macro></li></ol>
<p>Step 1 above just starts up JBoss. Step 2 above starts up a simple message consumer that comes with ActiveMQ. Step 3 above starts up a simple message producer that comes with ActiveMQ. Though the message consumer and message producer are simple utilities, the each one accepts many parameters making them extremely useful for testing ActiveMQ configurations.</p>
@@ -690,123 +643,12 @@
<p>After setting up one broker within one instance of JBoss, setting up another is made much easier, but requires another machine or operating system instance. But that's a whole separate article and something to address another day.</p>
-<h2 id="IntegratingApacheActiveMQwithJBoss-Conclusion">Conclusion</h2>
+<h2>Conclusion</h2>
-<p>What has been demonstrated here is the integration of ActiveMQ with the JBoss application server. This integration is quite common and performed by many enterprises. I hope that this was helpful to people interested in the integration of ActiveMQ with JBoss application server. If you have any questions or are interested in consulting services surrounding ActiveMQ, please <a shape="rect" class="external-link" href="http://www.logicblaze.com/contact.jsp" rel="nofollow">contact us</a> for more information.</p>
+<p>What has been demonstrated here is the integration of ActiveMQ with the JBoss application server. This integration is quite common and performed by many enterprises. I hope that this was helpful to people interested in the integration of ActiveMQ with JBoss application server. If you have any questions or are interested in consulting services surrounding ActiveMQ, please <a shape="rect" href="http://www.logicblaze.com/contact.jsp">contact us</a> for more information.</p>
-<h3 id="IntegratingApacheActiveMQwithJBoss-Resources">Resources</h3>
+<h3>Resources</h3>
<p>Below are the configurations for use with both Spring 1.x and Spring 2.x:</p>
-
-
-
-
-<div class="plugin_attachments_container">
- <div class="plugin_attachments_table_container">
- <fieldset class="hidden">
- <input type="hidden" class="plugin_attachments_macro_render_param" name="pageId" value="67786">
- <input type="hidden" name="deleteConfirmMessage" value="Are you sure you want to send the attached file " _0="_0" to="to" the="the" trash="trash" only="only" a="a" space="space" administrator="administrator" can="can" undo="undo" this="this" action.="action.">
- <input type="hidden" name="outputType" value="display">
- </fieldset>
-
-
-
-
-
-
-
-
-
-
-
-<table class="attachments aui"><thead><tr><th colspan="1" rowspan="1" class="expand-column attachment-summary-toggle"> </th><th colspan="1" rowspan="1" class="filename-column"> <a shape="rect" href="integrating-apache-activemq-with-jboss.xml?sortBy=name&sortOrder=ascending">File</a>
- </th><th colspan="1" rowspan="1" class="modified-column"> <span class="propersortedby $sortOrder"><a shape="rect" href="integrating-apache-activemq-with-jboss.xml?sortBy=date&sortOrder=descending">Modified</a></span>
- </th></tr></thead><tbody><tr class="attachment-row" id="attachment-59670763" data-attachment-id="59670763" data-attachment-idx="1"><td colspan="1" rowspan="1" class="attachment-summary-toggle">
- <span class="icon icon-section-closed" title="Show more info"></span>
- </td><td colspan="1" rowspan="1" class="filename-column">
-
-
-
-
-
-<span class="icon icon-file-unknown" title="File">File</span> <a shape="rect" class="filename" href="integrating-apache-activemq-with-jboss.data/amq-spring-1.2.6.tgz?api=v2" title="Download" data-filename="amq-spring-1.2.6.tgz" data-type="application/x-tar" data-linked-resource-container-id="67786">
- amq-spring-1.2.6.tgz
- </a>
- </td><td colspan="1" rowspan="1" class="attachment-created modified-column">
- <span>Oct 03, 2007</span>
- <span>by</span>
- <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~bsnyder">Bruce Snyder</a> </td></tr><tr class="attachment-summary attachment-summary-59670763 hidden" data-attachment-id="59670763" data-attachment-filename="amq-spring-1.2.6.tgz"><td colspan="1" rowspan="1" class="attachment-summary-toggle"></td><td colspan="2" rowspan="1" class="attachment-details-wrapper">
-
-
- <p class="attachment-labels">Labels</p>
-
-<div class="labels-section-content content-column" entityid="59670763" entitytype="attachment">
- <div class="labels-content">
-
- <ul class="label-list has-pen"><li class="no-labels-message">
- No labels
- </li><li class="labels-edit-container">
- <a shape="rect" class="show-labels-editor" href="#" title="Edit Labels">
- <span class="aui-icon aui-icon-small aui-iconfont-edit-small">Edit Labels</span>
- </a>
- </li></ul>
-
- </div>
-</div>
-
- <div class="attachment-history-wrapper"></div>
-
- <div class="attachment-buttons">
- <a shape="rect" class="aui-button previewAttachmentLink" data-filename="amq-spring-1.2.6.tgz" data-file-src="/confluence/download/attachments/67786/amq-spring-1.2.6.tgz?api=v2" data-linked-resource-default-alias="amq-spring-1.2.6.tgz" data-mime-type="application/x-tar" data-linked-resource-container-id="67786" data-linked-resource-id="59670763">Preview</a>
-
- </div>
- </td></tr><tr class="attachment-row" id="attachment-59670764" data-attachment-id="59670764" data-attachment-idx="2"><td colspan="1" rowspan="1" class="attachment-summary-toggle">
- <span class="icon icon-section-closed" title="Show more info"></span>
- </td><td colspan="1" rowspan="1" class="filename-column">
-
-
-
-
-
-<span class="icon icon-file-unknown" title="File">File</span> <a shape="rect" class="filename" href="integrating-apache-activemq-with-jboss.data/amq-spring-2.0.tgz?api=v2" title="Download" data-filename="amq-spring-2.0.tgz" data-type="application/x-tar" data-linked-resource-container-id="67786">
- amq-spring-2.0.tgz
- </a>
- </td><td colspan="1" rowspan="1" class="attachment-created modified-column">
- <span>Oct 03, 2007</span>
- <span>by</span>
- <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~bsnyder">Bruce Snyder</a> </td></tr><tr class="attachment-summary attachment-summary-59670764 hidden" data-attachment-id="59670764" data-attachment-filename="amq-spring-2.0.tgz"><td colspan="1" rowspan="1" class="attachment-summary-toggle"></td><td colspan="2" rowspan="1" class="attachment-details-wrapper">
-
-
- <p class="attachment-labels">Labels</p>
-
-<div class="labels-section-content content-column" entityid="59670764" entitytype="attachment">
- <div class="labels-content">
-
- <ul class="label-list has-pen"><li class="no-labels-message">
- No labels
- </li><li class="labels-edit-container">
- <a shape="rect" class="show-labels-editor" href="#" title="Edit Labels">
- <span class="aui-icon aui-icon-small aui-iconfont-edit-small">Edit Labels</span>
- </a>
- </li></ul>
-
- </div>
-</div>
-
- <div class="attachment-history-wrapper"></div>
-
- <div class="attachment-buttons">
- <a shape="rect" class="aui-button previewAttachmentLink" data-filename="amq-spring-2.0.tgz" data-file-src="/confluence/download/attachments/67786/amq-spring-2.0.tgz?api=v2" data-linked-resource-default-alias="amq-spring-2.0.tgz" data-mime-type="application/x-tar" data-linked-resource-container-id="67786" data-linked-resource-id="59670764">Preview</a>
-
- </div>
- </td></tr></tbody></table>
- </div>
- <div class="plugin_attachments_upload_container">
- </div>
-
- <div>
- <a shape="rect" class="download-all-link" href="/confluence/pages/downloadallattachments.action?pageId=67786" title="Download all the latest versions of attachments on this page as single zip file.">Download All</a>
- </div>
-</div>
-</div>
+<structured-macro ac:macro-id="eda15643-f616-42ea-bd14-d9b2d1397323" ac:name="attachments" ac:schema-version="1"></structured-macro></div>
diff --git a/integration-tests.xml b/integration-tests.xml
index 987a85a..152901e 100644
--- a/integration-tests.xml
+++ b/integration-tests.xml
@@ -1,73 +1,63 @@
<div class="wiki-content maincontent">
<p>The Integration Tests validate that ActiveMQ Resource Adapter operate correctly when deployed with a J2EE application running in an Application Server such as Apache Geronimo.</p>
-<h2 id="IntegrationTests-GettingReady">Getting Ready</h2>
+<h2>Getting Ready</h2>
<p>The instructions on this page reference a few directories that you will need to substitute appropriate values for:</p>
<ul><li><em>activemq-core</em> is where your ActiveMQ source code is located.</li><li><em>geronimo-home</em> is where your Geronimo home directory is located.</li></ul>
-<h2 id="IntegrationTests-BuildingtheActiveMQResourceAdapter">Building the ActiveMQ Resource Adapter</h2>
+<h2>Building the ActiveMQ Resource Adapter</h2>
<p>The ActiveMQ Resource Adapter allows a J2EE Application Server to provide transaction management, connection pooling and security to ActiveMQ connection when used by EJBs. The Resource Adapter is deployed in the client EAR that will be using the ActiveMQ.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ee6afd83-8b33-4daa-b68f-e794c0025e20" ac:name="code" ac:schema-version="1"><plain-text-body>
cd activemq-ra
maven rar:install-snapshot
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> </p>
<p> </p>
-<h2 id="IntegrationTests-BuildingtheIntegrationTestEJBmodule">Building the Integration Test EJB module</h2>
+<h2>Building the Integration Test EJB module</h2>
<p>The Integration Test EJB module provides a set of EJBs that the tests are run against.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d638161b-414d-4cf3-9e0d-dd21bc6c9245" ac:name="code" ac:schema-version="1"><plain-text-body>
cd systest/itests/ejb
maven
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> </p>
<p> </p>
-<h2 id="IntegrationTests-BuildingandDeployingtheIntegrationTestEARmodule">Building and Deploying the Integration Test EAR module</h2>
+<h2>Building and Deploying the Integration Test EAR module</h2>
<p>The EAR module packages up the Resource Adapter and the Integration Tests EJBs into a deployable EAR.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c636a44d-9d69-4691-8e51-4cefff3a8559" ac:name="code" ac:schema-version="1"><plain-text-body>
cd systest/itests/ear
maven -Dgeronimo.home=geronimo-home
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> </p>
<p> </p>
-<h2 id="IntegrationTests-StartingGeronimowiththeIntegrationTestEARconfiguration.">Starting Geronimo with the Integration Test EAR configuration.</h2>
+<h2>Starting Geronimo with the Integration Test EAR configuration.</h2>
<p>In a seperate console, issue the following commands</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2151b074-3e72-4b45-a729-2b872e261a7e" ac:name="code" ac:schema-version="1"><plain-text-body>
cd geronimo-home
java -jar bin/server.jar org/activemq/ear/itest
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> </p>
<p> </p>
-<h2 id="IntegrationTests-BuildingandrunningtheIntegrationTests.">Building and running the Integration Tests.</h2>
+<h2>Building and running the Integration Tests.</h2>
<p>The following builds and runs the integration tests:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="84c9c914-c765-4b10-83c9-008b0f80a189" ac:name="code" ac:schema-version="1"><plain-text-body>
cd systest/itests/client
maven
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> </p>
<p> </p></div>
diff --git a/interceptors.xml b/interceptors.xml
index fcd09d6..81b867c 100644
--- a/interceptors.xml
+++ b/interceptors.xml
@@ -1,27 +1,26 @@
-<div class="wiki-content maincontent"><p>ActiveMQ has a sophisticated <em>interceptor stack</em> so that you can attach whatever functionality you require into the broker in an easy way without complicating all of the other broker code. This has really helped us keep the code clean and modular while offering powerful extension points.</p><p>For an example of the kinds of things you can do with interceptors see the following pages</p><ul><li><a shape="rect" href="logging-interceptor.xml">Logging Interceptor</a></li><li><a shape="rect" href="security.xml">Security</a></li><li><a shape="rect" href="visualisation.xml">Visualisation</a></li><li><a shape="rect" href="timestampplugin.xml">TimeStamp on the Broker</a></li><li><a shape="rect" href="statisticsplugin.xml">Get Statistics via Messages</a></li><li><a shape="rect" href="destinations-plugin.xml">Destinations Plugin</a></li></ul><h3 id="Interceptors-Howpluginswork">How plugins work</h3><p>A plugin is an instance of the interface <a shape="rect" class="external-link" 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 shape="rect" class="external-link" 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>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="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<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
+<div class="wiki-content maincontent"><p>ActiveMQ has a sophisticated <em>interceptor stack</em> so that you can attach whatever functionality you require into the broker in an easy way without complicating all of the other broker code. This has really helped us keep the code clean and modular while offering powerful extension points.</p><p>For an example of the kinds of things you can do with interceptors see the following pages</p><ul><li><link><page ri:content-title="Logging Interceptor"></page></link></li><li><link><page ri:content-title="Security"></page></link></li><li><link><page ri:content-title="Visualisation"></page></link></li><li><link><page ri:content-title="TimeStampPlugin"></page><plain-text-link-body>TimeStamp on the Broker</plain-text-link-body></link></li><li><link><page ri:content-title="StatisticsPlugin"></page><plain-text-link-body>Get Statistics via Messages</plain-text-link-body></link></li><li><link><page ri:content-title="Destinations Plugin"></page></link></li></ul><h3>How plugins work</h3><p>A plugin is an instance of the interface <a shape="rect" 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 shape="rect" 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>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><structured-macro ac:macro-id="656129f8-6ff6-4792-be1a-034e4eb4bfa9" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><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
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.org/config/1.0
-http://activemq.apache.org/schema/activemq-core.xsd http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">
+http://activemq.apache.org/schema/activemq-core.xsd http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">
<!-- Allows us to use system properties as variables in this configuration file -->
-<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" />
+<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" />
- <broker xmlns="http://activemq.org/config/1.0" brokerName="localhost" dataDirectory="${activemq.base}/data" plugins="#myPlugin">
+ <broker xmlns="http://activemq.org/config/1.0" brokerName="localhost" dataDirectory="${activemq.base}/data" plugins="#myPlugin">
<!-- The transport connectors ActiveMQ will listen to -->
<transportConnectors>
- <transportConnector name="openwire" uri="tcp://localhost:61616" />
+ <transportConnector name="openwire" uri="tcp://localhost:61616" />
</transportConnectors>
</broker>
- <bean id="myPlugin" class="org.myorg.MyPlugin">
+ <bean id="myPlugin" class="org.myorg.MyPlugin">
<!-- You can reference one or more Spring beans in this file -->
- <property name="myMgr" ref="myManager"/>
+ <property name="myMgr" ref="myManager"/>
</bean>
- <bean id="myManager" class="org.myorg.MyManager">
- <property name="fooList">
+ <bean id="myManager" class="org.myorg.MyManager">
+ <property name="fooList">
<list>
<value>foo</value>
<value>foo2</value>
@@ -31,35 +30,31 @@
</beans>
-]]></script>
-</div></div><p>You can also define plugins from within the <plugin> element as this example illustrates.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<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
+</plain-text-body></structured-macro><p>You can also define plugins from within the <plugin> element as this example illustrates.</p><structured-macro ac:macro-id="4c7bdd02-d993-4579-9dd9-0f0aa25d6464" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><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
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.org/config/1.0
http://activemq.apache.org/schema/activemq-core.xsd http://activemq.apache.org/camel/schema/spring
-http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">
+http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" />
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" />
- <broker xmlns="http://activemq.org/config/1.0" brokerName="localhost" dataDirectory="${activemq.base}/data">
+ <broker xmlns="http://activemq.org/config/1.0" brokerName="localhost" dataDirectory="${activemq.base}/data">
<!-- The transport connectors ActiveMQ will listen to -->
<transportConnectors>
- <transportConnector name="openwire" uri="tcp://localhost:61616" />
+ <transportConnector name="openwire" uri="tcp://localhost:61616" />
</transportConnectors>
<plugins>
- <bean xmlns="http://www.springframework.org/schema/beans" id="myPlugin" class="org.myorg.MyPlugin"/>
+ <bean xmlns="http://www.springframework.org/schema/beans" id="myPlugin" class="org.myorg.MyPlugin"/>
</plugins>
</broker>
</beans>
-]]></script>
-</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 shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html">BrokerFilter</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[import org.apache.activemq.broker.Broker;
+</plain-text-body></structured-macro><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 shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html">BrokerFilter</a>.</p><structured-macro ac:macro-id="cf46422e-34b5-4b0a-9df2-52d5b5d113c6" ac:name="code" ac:schema-version="1"><plain-text-body>import org.apache.activemq.broker.Broker;
import org.apache.activemq.broker.BrokerPlugin;
public class MyPlugin implements BrokerPlugin {
@@ -69,9 +64,7 @@
}
}
-]]></script>
-</div></div><p>The BrokerFilter class is a convenience class that implements the <a shape="rect" class="external-link" 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 example of a class that extends BrokerFilter and intercepts/overrides the addConnection() and addSession() Broker methods/operations.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[import org.apache.activemq.broker.Broker;
+</plain-text-body></structured-macro><p>The BrokerFilter class is a convenience class that implements the <a shape="rect" 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 example of a class that extends BrokerFilter and intercepts/overrides the addConnection() and addSession() Broker methods/operations.</p><structured-macro ac:macro-id="f56ae2b6-9bb1-4c36-8e6a-521868d81a33" ac:name="code" ac:schema-version="1"><plain-text-body>import org.apache.activemq.broker.Broker;
import org.apache.activemq.broker.BrokerFilter;
import org.apache.activemq.broker.ConnectionContext;
import org.apache.activemq.command.ConnectionInfo;
@@ -103,6 +96,5 @@
-]]></script>
-</div></div><p>For more details see <a shape="rect" href="developing-plugins.xml">Developing Plugins</a></p></div>
+</plain-text-body></structured-macro><p>For more details see <link><page ri:content-title="Developing Plugins"></page></link></p></div>
diff --git a/ioexception-could-not-find-class-for-resource.xml b/ioexception-could-not-find-class-for-resource.xml
index ec41fd4..c7e2e9c 100644
--- a/ioexception-could-not-find-class-for-resource.xml
+++ b/ioexception-could-not-find-class-for-resource.xml
@@ -1,22 +1,20 @@
<div class="wiki-content maincontent"><p>If you get an exception looking like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5c09a37c-461c-400a-8682-4acaa5c967c4" ac:name="code" ac:schema-version="1"><plain-text-body>
Reason: java.io.exception : could not find class for resource: META-INF/services/org/apache/activemq/transport/tcp
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> </p>
-<h3 id="IOException-couldnotfindclassforresource-Cause">Cause</h3>
+<h3>Cause</h3>
<p>You are probably using the ActiveMQ source code without using the resources</p>
-<h3 id="IOException-couldnotfindclassforresource-Quickfix">Quick fix</h3>
+<h3>Quick fix</h3>
<p>Try one of these</p>
<ul><li>use one of the distribution jars for ActiveMQ</li><li>use Maven to run your program</li><li>try adding activemq/src/conf to your classpath</li></ul>
-<h3 id="IOException-couldnotfindclassforresource-Background">Background</h3>
+<h3>Background</h3>
<p>Then it means that the files in META-INF/services could not be found on the classpath. These files are used to support loose coupling on ActiveMQ with the transport protocols (e.g. to avoid a classpath dependency on JXTA) and to allow dynamic protocol enhancement without a change to the core.</p>
diff --git a/irc.xml b/irc.xml
index 2ff5a8e..9ed2f2f 100644
--- a/irc.xml
+++ b/irc.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Committers and contributors can often be found hanging out in IRC. <span style="line-height: 1.4285715;">Below is the information about the channel that we use: </span></p><p><strong>Server:</strong> irc.freenode.net</p><p><strong>Channel:</strong> #apache-activemq</p><p>There are many <a shape="rect" class="external-link" href="https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients" rel="nofollow">IRC clients</a> available out there depending on the operating system you are using. </p><p> </p><p>Note the IRC channel on codehaus is deprecated as of April 2015; please refrain from using that room.  Likewise, be aware there is a channel named #activemq on the freenode server - please avoid it as well.</p></div>
+<div class="wiki-content maincontent"><p>Committers and contributors can often be found hanging out in IRC. <span style="line-height: 1.4285715;">Below is the information about the channel that we use: </span></p><p><strong>Server:</strong> irc.freenode.net</p><p><strong>Channel:</strong> #apache-activemq</p><p>There are many <a shape="rect" href="https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients">IRC clients</a> available out there depending on the operating system you are using. </p><p> </p><p>Note the IRC channel on codehaus is deprecated as of April 2015; please refrain from using that room.  Likewise, be aware there is a channel named #activemq on the freenode server - please avoid it as well.</p></div>
diff --git a/j2ee.xml b/j2ee.xml
index b96734c..9869e48 100644
--- a/j2ee.xml
+++ b/j2ee.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>In J2EE 1.4 or later the standard way to integrate with a JMS provider is via JCA 1.5 and a <a shape="rect" href="resource-adapter.xml">Resource Adapter</a>.</p>
+<p>In J2EE 1.4 or later the standard way to integrate with a JMS provider is via JCA 1.5 and a <link><page ri:content-title="Resource Adapter"></page></link>.</p>
-<h2 id="J2EE-Introduction">Introduction</h2><p>ActiveMQ includes a Java Connector Architecture (JCA) 1.5 Resource Adapter. JCA 1.5 defines the contract between an J2EE application server and external resources such as databases and messaging middleware. It allows the application server to efficiently pool connections, control transactions and manage security. The Resource Adapter allows ActiveMQ to be used from any J2EE 1.4 application server. We have tested that the Resource Adapter works in the following J2EE 1.4 containers</p><ul><li><a shape="rect" class="external-link" href="http://tomee.apache.org/tomcat-jms.html">TomEE</a> 1</li><li>Geronimo 1</li><li>GlassFish</li><li>JBoss 4</li><li>WebLogic 9</li><li>WebSphere 6</li></ul><h2 id="J2EE-Features">Features</h2><ul><li>Inbound connection delivers messages to MDBs via XA or local transactions.</li><li>Outbound connections support standard container pooling or can reuse the inbound connection/session to avoid XA.</li><li>JTA support: Can be enlisted in XA and local transactions.</li><li>XA transaction recovery via XAResource.recover() supported.</li><li>When used outside a JTA transaction, session transaction settings retain normal JMS semantics so that it be used by your web-app tier.</li><li>Can configure and start up embedded broker.</li><li>Can connect to external ActiveMQ broker or embedded broker.</li><li>Inbound message delivery supports fine grain control of concurrency and prefetching.</li><li>Batching so that multiple messages can be delivered within the same transaction for optimal performances.</li></ul><h2 id="J2EE-DownloadingtheRAR">Downloading the RAR</h2><p>The RAR is available via <a shape="rect" class="external-link" href="http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22activemq-rar%22" rel="nofollow">maven central</a></p><p><span style="color: rgb(102,0,51);font-size: 20.0px;line-height: 1.5;">Deployment Guides</span></p><ul><li><a shape="rect" href="tomee.xml">TomEE</a></li><li><a shape="rect" href="geronimo.xml">Geronimo</a></li><li><a shape="rect" href="integrating-apache-activemq-with-glassfish.xml">Integrating Apache ActiveMQ with Glassfish</a></li><li><a shape="rect" href="jboss-integration.xml">JBoss Integration</a></li></ul><h2 id="J2EE-TheuseofanEmbeddedBroker">The use of an Embedded Broker</h2><p>The ActiveMQ Resource Adapter can connect to a remote broker using any of the available transports, or it can start up an embedded broker. As described in the <a shape="rect" href="resource-adapter-properties.xml">Resource Adapter Properties</a>, you can enable an embedded broker using the <strong>BrokerXmlConfig</strong> property.</p><h2 id="J2EE-ConfigurationReference">Configuration Reference</h2><ul><li><a shape="rect" href="resource-adapter-properties.xml">Resource Adapter Properties</a></li><li><a shape="rect" href="connection-factory-properties.xml">Connection Factory Properties</a></li><li><a shape="rect" href="activation-spec-properties.xml">Activation Spec Properties</a></li></ul></div>
+<structured-macro ac:macro-id="bb1a6e8d-0586-4002-8125-6273eff4fed3" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Resource Adapter"></page></link></parameter></structured-macro></div>
diff --git a/java-service-wrapper.xml b/java-service-wrapper.xml
index db2de76..8363825 100644
--- a/java-service-wrapper.xml
+++ b/java-service-wrapper.xml
@@ -1,11 +1,11 @@
<div class="wiki-content maincontent"><p>This page provides some useful information on running the ActiveMQ broker as a windows-NT service or a daemon thread in Linux or Unix systems.</p>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">64bit 4gb memory limit</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>The ActiveMQ distribution uses an older and free community release of the service wrapper library. This wrapper has a memory limit of 4gb when running on 64bit platforms. You can manually <a shape="rect" class="external-link" href="http://wrapper.tanukisoftware.com/doc/english/download.jsp" rel="nofollow">download a newer release</a> of the wrapper library that does not have this limit, from the vendors website at. It us not possible for Apache ActiveMQ to update and distribute a newer release of the service wrapper, as the vendor changed licensing terms, which does not comply with ASF licensing terms. Therefore out of the box the service wrapper is stuck on that older release.</p>
+<structured-macro ac:macro-id="927644e6-adf6-4e1b-8465-66bcb3401600" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">64bit 4gb memory limit</parameter><rich-text-body>
+<p>The ActiveMQ distribution uses an older and free community release of the service wrapper library. This wrapper has a memory limit of 4gb when running on 64bit platforms. You can manually <a shape="rect" href="http://wrapper.tanukisoftware.com/doc/english/download.jsp">download a newer release</a> of the wrapper library that does not have this limit, from the vendors website at. It us not possible for Apache ActiveMQ to update and distribute a newer release of the service wrapper, as the vendor changed licensing terms, which does not comply with ASF licensing terms. Therefore out of the box the service wrapper is stuck on that older release.</p>
-<p>However you can manually upgrade the library.</p></div></div>
+<p>However you can manually upgrade the library.</p></rich-text-body></structured-macro>
-<h3 id="JavaServiceWrapper-Windows-NTService">Windows-NT Service</h3>
+<h3>Windows-NT Service</h3>
<p>Here are the steps to install the ActiveMQ broker as an NT service:</p>
<ol><li>Download the windows binary distribution (i.e. apache-activemq-5.9.0.zip)</li><li>Go to ACTIVEMQ_HOME/bin/win32</li><li>Run InstallService.bat</li></ol>
@@ -21,7 +21,7 @@
<ol><li>Run UninstallService.bat</li></ol>
-<h3 id="JavaServiceWrapper-Linux/MacOSXDaemon">Linux/Mac OS X Daemon</h3>
+<h3>Linux/Mac OS X Daemon</h3>
<p>Here are the steps to run the ActiveMQ broker as a daemon in Linux or Unix systems:</p>
@@ -33,12 +33,12 @@
<ol><li>Go to ACTIVEMQ_HOME/linux for linux systems or ACTIVEMQ_HOME/macosx for Mac OS X systems.</li><li>Run ./activemq stop</li></ol>
-<h3 id="JavaServiceWrapper-ConfiguringtheJavaServiceWrapper"> Configuring the Java Service Wrapper</h3>
+<h3> Configuring the Java Service Wrapper</h3>
-<p>ActiveMQ uses the <a shape="rect" class="external-link" href="http://wrapper.tanukisoftware.org/doc/english/introduction.html" rel="nofollow">Java Service Wrapper</a> to run the broker. To configure how the Java Service Wrapper starts up, you can edit the wrapper.conf located in the bin/win32, bin/linux, or bin/macosx depending on which system you are running it. For more information on the different properties of the Java Service Wrapper, refer to this <a shape="rect" class="external-link" href="http://wrapper.tanukisoftware.org/doc/english/properties.html" rel="nofollow">page</a></p>
+<p>ActiveMQ uses the <a shape="rect" href="http://wrapper.tanukisoftware.org/doc/english/introduction.html">Java Service Wrapper</a> to run the broker. To configure how the Java Service Wrapper starts up, you can edit the wrapper.conf located in the bin/win32, bin/linux, or bin/macosx depending on which system you are running it. For more information on the different properties of the Java Service Wrapper, refer to this <a shape="rect" href="http://wrapper.tanukisoftware.org/doc/english/properties.html">page</a></p>
-<h3 id="JavaServiceWrapper-Troubleshooting"> Troubleshooting</h3>
+<h3> Troubleshooting</h3>
<p>If you are having problems running the service, turn on the wrapper debugging in the corresponding wrapper.conf file via (wrapper.debug=TRUE)</p>
diff --git a/javadocs.xml b/javadocs.xml
index 193c24f..69fcca3 100644
--- a/javadocs.xml
+++ b/javadocs.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="JavaDocs-JavaDocsforApacheActiveMQ">JavaDocs for Apache ActiveMQ</h2><p>Versioned JavaDocs for Apache ActiveMQ could be found at</p><p><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/">http://activemq.apache.org/maven/</a>x.y.z/apidocs/index.html kind of url, where <em>x.y.z</em> is broker version you're looking for.</p><p>For example <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.12.1/apidocs/index.html">http://activemq.apache.org/maven/5.12.1/apidocs/index.html</a> contains JavaDocs for <strong>5.12.1</strong>.</p><h2 id="JavaDocs-OtherJavaDocs">Other JavaDocs</h2><ul><li><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/package-summary.html" rel="nofollow">JMS API</a></li></ul><h2 id="JavaDocs-CMSandC++Documentation">CMS and C++ Documentation</h2><ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/cms/">CMS and ActiveMQ-CPP</a></li></ul><h2 id="JavaDocs-NMSandC#Documentation">NMS and C# Documentation</h2><ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/">NMS API</a></li></ul></div>
+<div class="wiki-content maincontent"><h2>JavaDocs for Apache ActiveMQ</h2><p>Versioned JavaDocs for Apache ActiveMQ could be found at</p><p><a shape="rect" href="http://activemq.apache.org/maven/">http://activemq.apache.org/maven/</a>x.y.z/apidocs/index.html kind of url, where <em>x.y.z</em> is broker version you're looking for.</p><p>For example <a shape="rect" href="http://activemq.apache.org/maven/5.12.1/apidocs/index.html">http://activemq.apache.org/maven/5.12.1/apidocs/index.html</a> contains JavaDocs for <strong>5.12.1</strong>.</p><h2>Other JavaDocs</h2><ul><li><a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/package-summary.html">JMS API</a></li></ul><h2>CMS and C++ Documentation</h2><ul><li><a shape="rect" href="http://activemq.apache.org/cms/">CMS and ActiveMQ-CPP</a></li></ul><h2>NMS and C# Documentation</h2><ul><li><a shape="rect" href="http://activemq.apache.org/nms/">NMS API</a></li></ul></div>
diff --git a/javaiointerruptedioexception.xml b/javaiointerruptedioexception.xml
index fcfaea3..88a4d3b 100644
--- a/javaiointerruptedioexception.xml
+++ b/javaiointerruptedioexception.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p> </p><p>The activemq client will throw an <a shape="rect" class="external-link" href="http://java.io" rel="nofollow">java.io</a>.InterruptedIOException if  the calling thread has been interrupted while the transport (ResponseCorrelator) is waiting for a response.</p><p>Thread interruption while waiting for a response is treated as an IOException and reported to the transport listener. For an ActiveMQConnection, this will force an async close of the transport, closing the underlying socket.</p><p>Because commands are not idempotent and with an interruption, it is not possible to know if the broker received the command, the only safe course of action is to close the connection.</p><p>If the thread has been interrupted before a request is attempted, the interrupted state is cleared and reset after the request has completed. This allows shutdown operations to complete in the interrupted state.</p></div>
+<div class="wiki-content maincontent"><p> </p><p>The activemq client will throw an <a shape="rect" href="http://java.io">java.io</a>.InterruptedIOException if  the calling thread has been interrupted while the transport (ResponseCorrelator) is waiting for a response.</p><p>Thread interruption while waiting for a response is treated as an IOException and reported to the transport listener. For an ActiveMQConnection, this will force an async close of the transport, closing the underlying socket.</p><p>Because commands are not idempotent and with an interruption, it is not possible to know if the broker received the command, the only safe course of action is to close the connection.</p><p>If the thread has been interrupted before a request is attempted, the interrupted state is cleared and reset after the request has completed. This allows shutdown operations to complete in the interrupted state.</p></div>
diff --git a/javaioioexception-failed-to-create-database-derbydb-see-the-next-exception-for-details.xml b/javaioioexception-failed-to-create-database-derbydb-see-the-next-exception-for-details.xml
index 0ca7c18..6fd23f9 100644
--- a/javaioioexception-failed-to-create-database-derbydb-see-the-next-exception-for-details.xml
+++ b/javaioioexception-failed-to-create-database-derbydb-see-the-next-exception-for-details.xml
@@ -1,13 +1,12 @@
<div class="wiki-content maincontent"><p>If you get an error like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9230e83c-a0c1-4e54-a69b-c47ed6c36b23" ac:name="code" ac:schema-version="1"><plain-text-body>
Jun 19, 2006 10:35:27 PM org.apache.activemq.broker.BrokerService getBroker
INFO: ActiveMQ 4.0 JMS Message Broker (localhost) is starting
Jun 19, 2006 10:35:27 PM org.apache.activemq.broker.BrokerService getBroker
INFO: For help or more information please see:
http://incubator.apache.org/activemq/
-java.io.IOException: Failed to create database 'derbydb', see the next
+java.io.IOException: Failed to create database 'derbydb', see the next
exception for details.
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:42)
@@ -34,7 +33,7 @@
at
com.ic.ntn.message.HelloWorld$HelloWorldBroker.run(HelloWorld.java:92)
at java.lang.Thread.run(Thread.java:595)
-Caused by: SQL Exception: Failed to create database 'derbydb', see the next
+Caused by: SQL Exception: Failed to create database 'derbydb', see the next
exception for details.
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
Source)
@@ -60,32 +59,28 @@
org.apache.activemq.store.jdbc.TransactionContext.getConnection(TransactionContext.java:54)
... 11 more
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Then the error is probably that the JDBC driver (Apache Derby by default) could not write to the persistent file area.</p>
-<h3 id="java.io.IOExceptionFailedtocreatedatabase'derbydb',seethenextexceptionfordetails-Workaround">Workaround</h3>
+<h3>Workaround</h3>
-<p>Create a directory for the broker to write its files. e.g. in Java code call <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerService.html#setDataDirectory(java.io.File)">setDataDirectory</a></p>
+<p>Create a directory for the broker to write its files. e.g. in Java code call <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerService.html#setDataDirectory(java.io.File)">setDataDirectory</a></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-File dir = new File("foo");
+<structured-macro ac:macro-id="ec2ce45d-ff66-4b44-86af-55df31e71c78" ac:name="code" ac:schema-version="1"><plain-text-body>
+File dir = new File("foo");
dir.mkdir();
broker.setDataDirectory(dir);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>or in XML use</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker dataDirectory="foo">...
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="4720743f-31fc-4604-844a-090611fa027b" ac:name="code" ac:schema-version="1"><plain-text-body>
+<broker dataDirectory="foo">...
+</plain-text-body></structured-macro>
-<h3 id="java.io.IOExceptionFailedtocreatedatabase'derbydb',seethenextexceptionfordetails-See">See</h3>
+<h3>See</h3>
-<ul><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li></ul></div>
+<ul><li><link><page ri:content-title="How do I embed a Broker inside a Connection"></page></link></li></ul>
+</div>
diff --git a/javalangnosuchmethoderror.xml b/javalangnosuchmethoderror.xml
index a1c4c5b..d501da2 100644
--- a/javalangnosuchmethoderror.xml
+++ b/javalangnosuchmethoderror.xml
@@ -1,31 +1,28 @@
<div class="wiki-content maincontent"><p>If you get an error like</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ad648f77-49f7-4ec9-bab0-a19e18153e66" ac:name="code" ac:schema-version="1"><plain-text-body>
java.lang.NoSuchMethodError:
javax.jms.Session.createConsumer(Ljavax/jms/Destination;)Ljavax/jms/MessageConsumer;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>or</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3b8768da-d141-4822-9ac3-66c88cf3df4d" ac:name="code" ac:schema-version="1"><plain-text-body>
java.lang.AbstractMethodError:
javax.jms.ConnectionFactory.createConnection()Ljavax/jms/Connection;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="java.lang.NoSuchMethodError-Fix">Fix</h3>
+<h3>Fix</h3>
<p>You probably have old JMS 1.0.2b versions of the JMS API on your classpath. This is because various methods were added in JMS 1.1 to work with destinations in a polymorphic way (such as to create a consumer from a Destination like the above stack trace).</p>
<p>Please add the JMS 1.1 jars to your container/classpath and try again. </p>
-<div class="confluence-information-macro confluence-information-macro-note"><p class="title">Add to the correct ClassPath</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>If the JMS 1.0.2b classes come from your application server you may need to add the JMS 1.1 to your boot classpath to ensure that the JMS 1.1 classes take precedence to the container supplied classes</p></div></div>
+<structured-macro ac:macro-id="84703f19-7c81-4f6a-8c2f-64ecb536de0f" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Add to the correct ClassPath</parameter><rich-text-body>
+<p>If the JMS 1.0.2b classes come from your application server you may need to add the JMS 1.1 to your boot classpath to ensure that the JMS 1.1 classes take precedence to the container supplied classes</p></rich-text-body></structured-macro>
<p>Note that to a user of the JMS API, JMS 1.1 is completely backwards compatible. The only issue with upgrading to JMS 1.1 is that any JMS provider which implements only JMS 1.0.2b and does not implement JMS 1.1 will not work; however if you're using ActiveMQ you should be fine.</p>
+
</div>
diff --git a/javalangnosuchmethodexception-orgactivemqraactivemqresourceadaptersetuseembeddedbroker.xml b/javalangnosuchmethodexception-orgactivemqraactivemqresourceadaptersetuseembeddedbroker.xml
index 9257713..cde862f 100644
--- a/javalangnosuchmethodexception-orgactivemqraactivemqresourceadaptersetuseembeddedbroker.xml
+++ b/javalangnosuchmethodexception-orgactivemqraactivemqresourceadaptersetuseembeddedbroker.xml
@@ -1,9 +1,8 @@
<div class="wiki-content maincontent"><p>If you get an error like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0dfcf27e-6364-483a-9709-288117d4b6b7" ac:name="code" ac:schema-version="1"><plain-text-body>
2005-08-14 17:18:45,618 ERROR [org.jboss.resource.deployment.RARDeployment]
-Starting failed jboss.jca:service=RARDeployment,name='activemq-ra-3.0.rar'
+Starting failed jboss.jca:service=RARDeployment,name='activemq-ra-3.0.rar'
org.jboss.deployment.DeploymentException: Error for resource adapter class
org.activemq.ra.ActiveMQResourceAdapter accessing property setter
ConfigPropertyMetaData@e62121[name=UseEmbeddedBroker type=java.lang.Boolean
@@ -29,10 +28,9 @@
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="java.lang.NoSuchMethodExceptionorg.activemq.ra.ActiveMQResourceAdapter.setUseEmbeddedBroker-Fix">Fix</h3>
+<h3>Fix</h3>
<p>You are using 3.0 of ActiveMQ. This bug is fixed in 3.1.x so use 3.1-M6 or later.</p></div>
diff --git a/javalangoutofmemory.xml b/javalangoutofmemory.xml
index 2108720..fdf8ff7 100644
--- a/javalangoutofmemory.xml
+++ b/javalangoutofmemory.xml
@@ -1,46 +1,45 @@
<div class="wiki-content maincontent"><p>Ok, this is manageable. It is possible to configure just about all of the memory utilisation of ActiveMQ. The first thing to determine is what part of the system is running out of memory. Is it the JVM, the broker, the consumers or the producers? </p>
-<div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>This entry refers to ActiveMQ versions 5.1.x and greater.</p></div></div>
+<structured-macro ac:macro-id="1e867ae9-192f-43d2-b551-5889fe88e50a" ac:name="note" ac:schema-version="1"><rich-text-body>
+<p>This entry refers to ActiveMQ versions 5.1.x and greater.</p></rich-text-body></structured-macro>
-<h4 id="java.lang.OutOfMemory-Memory">Memory</h4>
-<h5 id="java.lang.OutOfMemory-JVMMemory">JVM Memory </h5>
+<h4>Memory</h4>
+<h5>JVM Memory </h5>
<p>Try running the broker in a standalone JVM using <code>bin/activemq</code>. Note the default JVM heap size option that is passed to the Java executable by the script (the exact options may depend upon the JVM that you are using, the examples are for the Sun JVM).</p>
-<ul><li>-Xmx: If your OS has more available memory, consider increasing the total heap memory available to the broker JVM. Note that the JVM will require more memory than the -Xmx value. Thread stacks and the JMVs internal classes will consume additional memory.</li><li>-Xss: If you have <a shape="rect" href="#java.lang.OutOfMemory-NumberofThreads">massive numbers of threads</a> in the Broker JVM, consider reducing the default JVM stack size of each thread with the -Xss option.</li></ul>
+<ul><li>-Xmx: If your OS has more available memory, consider increasing the total heap memory available to the broker JVM. Note that the JVM will require more memory than the -Xmx value. Thread stacks and the JMVs internal classes will consume additional memory.</li><li>-Xss: If you have <link ac:anchor="Number of Threads"><link-body>massive numbers of threads</link-body></link> in the Broker JVM, consider reducing the default JVM stack size of each thread with the -Xss option.</li></ul>
<p>If you are running an embedded broker or in a third party container, ensure that the hosting JVM has appropriate values for the maximum heap and stack sizes.</p>
-<h5 id="java.lang.OutOfMemory-BrokerMemory">Broker Memory </h5>
-<p>The memory that the broker is allowed to use is not determined by the amount of memory allocated to the JVM. Although the broker is constrained by the amount of memory given to the JVM, the broker manages its memory independently. That is, the broker does not just simply use up all of the memory in the JVM and then die with an OutOfMemory exception. This is where you need to understand the <a shape="rect" href="producer-flow-control.xml#ProducerFlowControl-Systemusage">systemUsage</a> memory limit and the per destination memory limit. </p>
+<h5>Broker Memory </h5>
+<p>The memory that the broker is allowed to use is not determined by the amount of memory allocated to the JVM. Although the broker is constrained by the amount of memory given to the JVM, the broker manages its memory independently. That is, the broker does not just simply use up all of the memory in the JVM and then die with an OutOfMemory exception. This is where you need to understand the <link ac:anchor="System usage"><page ri:content-title="Producer Flow Control"></page><link-body>systemUsage</link-body></link> memory limit and the per destination memory limit. </p>
<p>The memory in ActiveMQ works in a tiered fashion that flows from the JVM -> Broker -> broker features. E.g., the total amount of destination memory limits placed cannot exceed the memory limit of the broker. </p>
-<h4 id="java.lang.OutOfMemory-Consumer">Consumer</h4>
-<p>Along with message size, the <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch limit</a> is main reason a consumer will <a shape="rect" href="what-is-the-prefetch-limit-for.xml#WhatisthePrefetchLimitFor?-RamversusPerformancetradeoff">run out of memory</a>. Reducing the prefetch value will reduce the amount of messages queued/stored in memory on the Consumer.</p>
+<h4>Consumer</h4>
+<p>Along with message size, the <link><page ri:content-title="What is the Prefetch Limit For?"></page><link-body>prefetch limit</link-body></link> is main reason a consumer will <link ac:anchor="Ram versus Performance tradeoff"><page ri:content-title="What is the Prefetch Limit For?"></page><link-body>run out of memory</link-body></link>. Reducing the prefetch value will reduce the amount of messages queued/stored in memory on the Consumer.</p>
-<h4 id="java.lang.OutOfMemory-Producer">Producer</h4>
-<p>Unless message size exceeds resource limits, a producer should not run out of memory. A producer may notice the effect of memory limit enforcement by the broker in the form of <a shape="rect" href="my-producer-blocks.xml">blocking</a>.</p>
+<h4>Producer</h4>
+<p>Unless message size exceeds resource limits, a producer should not run out of memory. A producer may notice the effect of memory limit enforcement by the broker in the form of <link><page ri:content-title="My Producer Blocks"></page><link-body>blocking</link-body></link>.</p>
-<h4 id="java.lang.OutOfMemory-Other">Other </h4>
+<h4>Other </h4>
-<h5 id="java.lang.OutOfMemory-SpoolingMessagestoDisk">Spooling Messages to Disk</h5>
+<h5>Spooling Messages to Disk</h5>
<p>Fast dispatch of messages is only possible when messages are stored in memory. When consumers are slow or absent, memory can quickly become exhausted. <br clear="none">
-The Broker (using <a shape="rect" href="message-cursors.xml">Message Cursors</a>) will spool non-persistent messages to disk when the default memory usage threshold for a destination is reached. This threshold value is specified to the Broker via the <memoryUsage> section of the <systemUsage> configuration in <a shape="rect" href="xml-configuration.xml">activemq.xml</a>. This feature allows producers to continue sending messages when there are slow consumers without exhausting available memory or reverting to <a shape="rect" href="producer-flow-control.xml">producer flow control</a>. In the case of multiple destinations, the combined default memory thresholds may be excessive and they may exceed available memory. In such a case it may make sense to reduce the memory usage 'limit' threshold at which messages are spooled to disk. An alternative option is to configure the 'precentUsage' rather than the absolute usage 'limit'. In this way, memory usage can be confined to a fixed percentage of available memory.</p>
+The Broker (using <link><page ri:content-title="Message Cursors"></page></link>) will spool non-persistent messages to disk when the default memory usage threshold for a destination is reached. This threshold value is specified to the Broker via the <memoryUsage> section of the <systemUsage> configuration in <link><page ri:content-title="XML Configuration"></page><link-body>activemq.xml</link-body></link>. This feature allows producers to continue sending messages when there are slow consumers without exhausting available memory or reverting to <link><page ri:content-title="Producer Flow Control"></page><link-body>producer flow control</link-body></link>. In the case of multiple destinations, the combined default memory thresholds may be excessive and they may exceed available memory. In such a case it may make sense to reduce the memory usage 'limit' threshold at which messages are spooled to disk. An alternative option is to configure the 'precentUsage' rather than the absolute usage 'limit'. In this way, memory usage can be confined to a fixed percentage of available memory.</p>
-<p>More specific per destination memoryUsage limits can be specified in <a shape="rect" href="xml-configuration.xml">activemq.xml</a> using <a shape="rect" href="per-destination-policies.xml">Per Destination Policies</a>. Some further examples of <destinationPolicy> map entries can be found in the <a shape="rect" href="message-cursors.xml">Message Cursors</a> reference.</p>
+<p>More specific per destination memoryUsage limits can be specified in <link><page ri:content-title="XML Configuration"></page><link-body>activemq.xml</link-body></link> using <link><page ri:content-title="Per Destination Policies"></page></link>. Some further examples of <destinationPolicy> map entries can be found in the <link><page ri:content-title="Message Cursors"></page></link> reference.</p>
-<h5 id="java.lang.OutOfMemory-NumberofThreads">Number of Threads</h5>
+<h5>Number of Threads</h5>
<p>By default, ActiveMQ uses a dedicated thread per destination. If there are large numbers of Destinations there will be a large number of threads and their associated memory resource usage. ActiveMQ can be configured to use a thread pool through the use of the system property: -Dorg.apache.activemq.UseDedicatedTaskRunner=false. This is currently specified in the activemq start script via ACTIVEMQ_OPTS. Using a thread pool can restrict the number of threads required by ActiveMQ and hence reduce memory usage.</p>
-<h5 id="java.lang.OutOfMemory-ReallyLargeMessages">Really Large Messages</h5>
-<p>When your message are really large such that you can only allow a few messages in memory at at time, the <a shape="rect" href="per-destination-policies.xml">Per Destination Policies</a> maxPageSize and lazyDispatch can help. maxPageSize controls the amount of messages that are paged into memory for dispatch while lazyDispatch augments that value using the prefetch capacity of the current consumer list. With a prefetch of 1, a single consumer and lazyDispatch, only one message at a time would be loaded into memory at a time.</p>
+<h5>Really Large Messages</h5>
+<p>When your message are really large such that you can only allow a few messages in memory at at time, the <link><page ri:content-title="Per Destination Policies"></page></link> maxPageSize and lazyDispatch can help. maxPageSize controls the amount of messages that are paged into memory for dispatch while lazyDispatch augments that value using the prefetch capacity of the current consumer list. With a prefetch of 1, a single consumer and lazyDispatch, only one message at a time would be loaded into memory at a time.</p>
-<h5 id="java.lang.OutOfMemory-LeakingJMSresources">Leaking JMS resources</h5>
-<p>This is the most obvious one for Consumers or Producers; repeatedly obtaining a Session or MessageProducer or MessageConsumer and not closing it. With a java.lang.OutOfMemory, verifying (again) that all not in use JMS resources are released, is worth the time. If you have multiple threads in your application, consider using the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/pool/PooledConnectionFactory.html">PooledConnectionFactory</a> as this will allow JMS resource to be safely shared among threads that follow the pattern: </p>
+<h5>Leaking JMS resources</h5>
+<p>This is the most obvious one for Consumers or Producers; repeatedly obtaining a Session or MessageProducer or MessageConsumer and not closing it. With a java.lang.OutOfMemory, verifying (again) that all not in use JMS resources are released, is worth the time. If you have multiple threads in your application, consider using the <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/pool/PooledConnectionFactory.html">PooledConnectionFactory</a> as this will allow JMS resource to be safely shared among threads that follow the pattern: </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="62a3f40f-6247-4ef1-9ebc-da66cc21ca35" ac:name="code" ac:schema-version="1"><plain-text-body>
obtainJmsResource();
try
@@ -49,8 +48,7 @@
} finally {
releaseJmsResource();
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>If you are using ActiveMQ via <a shape="rect" href="spring-support.xml">Spring Support</a> or with JMSTemplates, be sure to check you are not falling for any of the <a shape="rect" href="jmstemplate-gotchas.xml">JmsTemplate Gotchas</a>. It may also be worth recapping on <a shape="rect" href="how-do-i-use-jms-efficiently.xml">How do I use JMS efficiently</a>.</p></div>
+<p>If you are using ActiveMQ via <link><page ri:content-title="Spring Support"></page></link> or with JMSTemplates, be sure to check you are not falling for any of the <link><page ri:content-title="JmsTemplate Gotchas"></page></link>. It may also be worth recapping on <link><page ri:content-title="How do I use JMS efficiently"></page></link>.</p></div>
diff --git a/javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml b/javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml
index d5e8420..cdea178 100644
--- a/javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml
+++ b/javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml
@@ -1,34 +1,30 @@
<div class="wiki-content maincontent"><p>If you get exception like this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c7fff064-ddf6-4be8-b885-84e74304b951" ac:name="code" ac:schema-version="1"><plain-text-body>
javax.jms.JMSException: Wire format negociation timeout: peer did not send his wire format.
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:58)
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1185)
at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1263)
at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:449)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>it can mean one of three things:</p>
-<h1 id="javax.jms.JMSException-Wireformatnegociationtimeout-peerdidnotsendhiswireformat.-1.You'reconnectingtotheportnotusedbyActiveMQTCPtransport">1. You're connecting to the port not used by ActiveMQ TCP transport</h1>
+<h1>1. You're connecting to the port not used by ActiveMQ TCP transport</h1>
<p>Make sure to check that you're connecting to the appropriate <code>host:port</code></p>
-<h1 id="javax.jms.JMSException-Wireformatnegociationtimeout-peerdidnotsendhiswireformat.-2.You'reusinglog4jJMSappenderanddoesn'tfilteroutActiveMQlogmessages">2. You're using log4j JMS appender and doesn't filter out ActiveMQ log messages</h1>
+<h1>2. You're using log4j JMS appender and doesn't filter out ActiveMQ log messages</h1>
-<p>Be sure to read <a shape="rect" href="how-do-i-use-log4j-jms-appender-with-activemq.xml">How do I use log4j JMS appender with ActiveMQ</a> and more importantly to never send ActiveMQ log messages to JMS appender</p>
+<p>Be sure to read <link><page ri:content-title="How do I use log4j JMS appender with ActiveMQ"></page></link> and more importantly to never send ActiveMQ log messages to JMS appender</p>
-<h1 id="javax.jms.JMSException-Wireformatnegociationtimeout-peerdidnotsendhiswireformat.-3.Yourbrokerisprobablyunderheavyload(ornetworkconnectionisunreliable),soconnectionsetupcannotbecompletedinareasonabletime">3. Your broker is probably under heavy load (or network connection is unreliable), so connection setup cannot be completed in a reasonable time</h1>
+<h1>3. Your broker is probably under heavy load (or network connection is unreliable), so connection setup cannot be completed in a reasonable time</h1>
-<p>If you experience sporadic exceptions like this, the best solution is to use <a shape="rect" href="failover-transport-reference.xml">failover transport</a>, so that your clients can try connecting again if the first attempt fails. If you're getting these kind of exceptions more frequently you can also try extending wire format negotiation period (default 10 sec). You can do that by using <code>wireFormat.maxInactivityDurationInitalDelay</code> property on the connection URL in your client. For example</p>
+<p>If you experience sporadic exceptions like this, the best solution is to use <link><page ri:content-title="Failover Transport Reference"></page><link-body>failover transport</link-body></link>, so that your clients can try connecting again if the first attempt fails. If you're getting these kind of exceptions more frequently you can also try extending wire format negotiation period (default 10 sec). You can do that by using <code>wireFormat.maxInactivityDurationInitalDelay</code> property on the connection URL in your client. For example</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9d307573-86f2-48c2-887c-50dd112ec50d" ac:name="code" ac:schema-version="1"><plain-text-body>
tcp://localhost:61616?wireFormat.maxInactivityDurationInitalDelay=30000
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>will use 30 sec timeout.</p></div>
diff --git a/jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml b/jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml
index eda0fba..2538580 100644
--- a/jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml
+++ b/jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml
@@ -1,4 +1,5 @@
<div class="wiki-content maincontent"><p>When using JDK 6 (up to JDK 6 Update 3) to run ActiveMQ you can run into this exception. There are two solutions to this:</p>
-<ul><li>Upgrade to JDK to 1.6.0_04 or above, which includes JAXB 2.1</li><li>Copy JAXB 2.1 to <JAVA_HOME>/lib/endorsed to override the API jars that ship with the JDK</li></ul></div>
+<ul><li>Upgrade to JDK to 1.6.0_04 or above, which includes JAXB 2.1</li><li>Copy JAXB 2.1 to <JAVA_HOME>/lib/endorsed to override the API jars that ship with the JDK</li></ul>
+</div>
diff --git a/jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-xxx-needs-21-api.xml b/jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-xxx-needs-21-api.xml
index eda0fba..2538580 100644
--- a/jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-xxx-needs-21-api.xml
+++ b/jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-xxx-needs-21-api.xml
@@ -1,4 +1,5 @@
<div class="wiki-content maincontent"><p>When using JDK 6 (up to JDK 6 Update 3) to run ActiveMQ you can run into this exception. There are two solutions to this:</p>
-<ul><li>Upgrade to JDK to 1.6.0_04 or above, which includes JAXB 2.1</li><li>Copy JAXB 2.1 to <JAVA_HOME>/lib/endorsed to override the API jars that ship with the JDK</li></ul></div>
+<ul><li>Upgrade to JDK to 1.6.0_04 or above, which includes JAXB 2.1</li><li>Copy JAXB 2.1 to <JAVA_HOME>/lib/endorsed to override the API jars that ship with the JDK</li></ul>
+</div>
diff --git a/jboss-integration.xml b/jboss-integration.xml
index afc19be..16c619e 100644
--- a/jboss-integration.xml
+++ b/jboss-integration.xml
@@ -1,811 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="JBossIntegration-IntegratingApacheActiveMQwithJBoss">Integrating Apache ActiveMQ with JBoss</h1>
-
-<p>Integration with application servers is a common scenario in the enterprise Java world, especially when it comes to messaging. <a shape="rect" class="external-link" href="http://activemq.org/" rel="nofollow">ActiveMQ</a> is a JMS 1.1 compliant, open source, Apache Licensed, message oriented middleware (MOM) with <a shape="rect" class="external-link" href="http://activemq.org/site/changes-in-40.html" rel="nofollow">many</a>, <a shape="rect" class="external-link" href="http://activemq.org/site/new-features-in-41.html" rel="nofollow">many</a> features far beyond the JMS specification. ActiveMQ offers many different <a shape="rect" class="external-link" href="http://activemq.org/site/connectivity.html" rel="nofollow">points of connectivity</a>, many <a shape="rect" class="external-link" href="http://activemq.org/site/cross-language-clients.html" rel="nofollow">cross language clients</a> and many <a shape="rect" class="external-link" href="http://activemq.org/site/protocols.html" rel="nofollow">pluggable transport protocols</a> including integration with any J2EE 1.4 application server.</p>
-
-<p>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 shape="rect" class="external-link" href="http://www.activemq.org/site/jboss-integration.html" rel="nofollow">a bit of documentation</a> 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.</p>
-
-<p>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.</p>
-
-<h2 id="JBossIntegration-Requirements">Requirements</h2>
-
-<p>Below are the software requirements for this article with links to download each:</p>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.org/site/download.html" rel="nofollow">Apache ActiveMQ 4.0.1+</a></li><li><a shape="rect" class="external-link" href="http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591" rel="nofollow">JBoss 4.0.4+</a></li><li><a shape="rect" class="external-link" href="http://www.java.com/en/download/index.jsp" rel="nofollow">Sun Java 1.5+</a></li><li><a shape="rect" class="external-link" href="http://ant.apache.org/bindownload.cgi">Apache Ant 1.6+</a></li></ul>
-
-
-<p>Though this article is using Unix, the installation and integration will work on any platform running Sun Java. It is recommended that each piece of software be downloaded before working through the steps is this article. Once each piece of software has been downloaded, proceed to the first step.</p>
-
-<h2 id="JBossIntegration-InstalltheJ2SE1.5">Install the J2SE 1.5</h2>
-
-<p>The first step in this process is to install Java 1.5 and verify that it runs correctly. Using the link above, find, download and install the correct version of Java for your platform. Once Java is installed and in the PATH, test it to see that it runs correctly using the following command:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ java -version
-java version "1.5.0_06"
-Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
-Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)
-]]></script>
-</div></div>
-<p>Depending upon your platform and the exact build number of Java 1.5, your output may vary slightly. As long as it's Java 1.5 and the version information is output, you should be ready to proceed to the next step.</p>
-
-<h2 id="JBossIntegration-InstallApacheAnt">Install Apache Ant</h2>
-
-<p>The second step is to install Apache Ant. Simply download it using the link above, expand somewhere on your hard drive and place the <code>bin</code> directory in the PATH. This will allow you to test it quickly using the commands below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ ant -version
-Apache Ant version 1.6.2 compiled on July 16 2004
-]]></script>
-</div></div>
-<p>As long as you see the version output above, Ant should be usable. If you did not see the version output or received an error, consult the Ant documentation or mailing list archives to work out the issue. Please note that Ant is not used until the end of this whole exercise to test the integration.</p>
-
-<h2 id="JBossIntegration-InstalltheJBossApplicationServer">Install the JBoss Application Server</h2>
-
-<p>The third step in this process is to install JBoss and make sure it runs correctly before installing and configuring ActiveMQ. Upon downloading JBoss-4.0.4, expand it in a place where it can create a directory. Next, run the server using the following commands:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ cd jboss-4.0.4.GA
-$ ./bin/run.sh -c default
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss-4.0.4.GA
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss-4.0.4.GA/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-15:34:47,999 INFO [Server] Starting JBoss (MX MicroKernel)...
-15:34:48,001 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
-15:34:48,004 INFO [Server] Home Dir: /opt/jboss-4.0.4.GA
-15:34:48,005 INFO [Server] Home URL: file:/opt/jboss-4.0.4.GA/
-15:34:48,007 INFO [Server] Patch URL: null
-15:34:48,007 INFO [Server] Server Name: default
-15:34:48,007 INFO [Server] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-15:34:48,011 INFO [Server] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-15:34:48,012 INFO [Server] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-15:34:48,017 INFO [Server] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-15:34:48,022 INFO [Server] Root Deployment Filename: jboss-service.xml
-...
-15:35:17,360 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)]
-Started in 22s:238ms
-]]></script>
-</div></div>
-<p>The first few lines of output from the JBoss startup indicates the configuration being used but the last line is the most important one. It tells you that JBoss has been started successfully on your system. For an extra measure of assurance, visit <a shape="rect" class="external-link" href="http://localhost:8080/web-console/" rel="nofollow">http://localhost:8080/web-console/</a> in a web browser to make sure you are able to see the JBoss web console. If you can see this console, everything should be ready to go.</p>
-
-<p>As a side note, the left-hand side of the web-console requires that the <a shape="rect" class="external-link" href="http://java.sun.com/products/plugin/" rel="nofollow">Java plugin</a> be properly installed. This is supposed to take place when installing the J2SE, so if it did not work correctly for you, I suggest that you consult some documentation about any errors you may be seeing. The Java plugin is not required for JBoss or ActiveMQ to function properly, it is simply for the JBoss web-console.</p>
-
-<p>Once JBoss is installed properly, shut it down using either the shutdown script or by simply typing ctrl-c to activate the shutdown hook. Once it is shut down, proceed to the next step.</p>
-
-<h2 id="JBossIntegration-PrepareforIntegratingApacheActiveMQwiththeJBossApplicationServer">Prepare for Integrating Apache ActiveMQ with the JBoss Application Server</h2>
-
-<p>The fourth step is to prepare your environment for integrating ActiveMQ with JBoss. If you haven't done so already, download Apache ActiveMQ using the link above. As of the writing of this article, the latest released version is 4.0.2-RC4. Upon downloading this archive, expand it in a place where it can create a directory, preferably in the same location where JBoss was expanded. Verify that the ActiveMQ RAR file is included using the following commands:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ cd ./incubator-activemq-4.0.2.tar.gz
-$ jar tvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar
- 0 Mon Sep 25 19:00:50 MDT 2006 META-INF/
- 399 Mon Sep 25 19:00:48 MDT 2006 META-INF/MANIFEST.MF
- 523 Mon Sep 25 13:07:40 MDT 2006 META-INF/DISCLAIMER.txt
- 11359 Mon Sep 25 13:07:40 MDT 2006 META-INF/LICENSE.txt
- 20305 Mon Sep 25 13:07:40 MDT 2006 META-INF/ra.xml
- 2334 Mon Sep 25 13:07:40 MDT 2006 broker-config.xml
- 70023 Mon Sep 25 19:00:48 MDT 2006 activemq-ra-4.0.2.jar
-1351744 Mon Sep 25 19:00:14 MDT 2006 activemq-core-4.0.2.jar
-232107 Mon Sep 25 18:22:48 MDT 2006 activeio-core-3.0-beta4.jar
-2143211 Tue Aug 01 11:44:50 MDT 2006 derby-10.1.1.0.jar
-1901653 Tue Aug 01 11:47:08 MDT 2006 spring-1.2.6.jar
- 94713 Tue Aug 01 11:47:22 MDT 2006 xbean-spring-2.2.jar
- 52915 Tue Aug 01 12:22:16 MDT 2006 commons-logging-1.1.jar
- 16030 Tue Aug 01 12:22:32 MDT 2006 geronimo-j2ee-management_1.0_spec-1.0.jar
-329586 Tue Aug 01 12:22:54 MDT 2006 backport-util-concurrent-2.1.jar
-358085 Tue Aug 01 12:23:26 MDT 2006 log4j-1.2.12.jar
- 523 Mon Sep 25 19:00:50 MDT 2006 META-INF/DISCLAIMER.txt
- 11359 Mon Sep 25 19:00:50 MDT 2006 META-INF/LICENSE.txt
-]]></script>
-</div></div>
-<p>This is simply a table of contents of the RAR file. There should only be one reason that this will fail - an incomplete download of the ActiveMQ tarball or zip file. Beyond that, depending on the version you download, some of the library versions may be slightly different.</p>
-
-<p>Now go back to the JBoss installation and create a directory for ActiveMQ in the JBoss deploy directory for the default JBoss context. Below are the commands to achieve this task:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ mkdir /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-$ cd /opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-$ pwd
-/opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-]]></script>
-</div></div>
-<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;">
-<p><strong><em>NOTE:</em></strong> The creation of a directory is not required but is the easiest way to set up the ActiveMQ RAR when you're just getting started. This is due to the flexibility it affords during the development phase for the configuration to be changed very easily. The alternative is to JAR up the directory as a RAR file once the configuration is solid enough that it no longer needs to be changed. But leaving everything in a directory during development is the easiest path.</p>
-</div></div>
-<p>Now expand the activemq-ra-4.0.2.rar into the current working directory:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-jar xvf /opt/incubator-activemq-4.0.2/lib/optional/activemq-ra-4.0.2.rar
- created: META-INF/
- inflated: META-INF/MANIFEST.MF
- inflated: META-INF/DISCLAIMER.txt
- inflated: META-INF/LICENSE.txt
- inflated: META-INF/ra.xml
- inflated: broker-config.xml
- inflated: activemq-ra-4.0.2.jar
- inflated: activemq-core-4.0.2.jar
- inflated: activeio-core-3.0-beta4.jar
- inflated: derby-10.1.1.0.jar
- inflated: spring-1.2.6.jar
- inflated: xbean-spring-2.2.jar
- inflated: commons-logging-1.1.jar
- inflated: geronimo-j2ee-management_1.0_spec-1.0.jar
- inflated: backport-util-concurrent-2.1.jar
- inflated: log4j-1.2.12.jar
- inflated: META-INF/DISCLAIMER.txt
- inflated: META-INF/LICENSE.txt
-]]></script>
-</div></div>
-<p>Below is a quick listing of the contents of that directory:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ ls -l
-total 12848
-drwxr-xr-x 6 bsnyder bsnyder 204 Oct 16 16:27 META-INF
--rw-r--r-- 1 bsnyder bsnyder 232107 Oct 16 16:27 activeio-core-3.0-beta4.jar
--rw-r--r-- 1 bsnyder bsnyder 1351744 Oct 16 16:27 activemq-core-4.0.2.jar
--rw-r--r-- 1 bsnyder bsnyder 70023 Oct 16 16:27 activemq-ra-4.0.2.jar
--rw-r--r-- 1 bsnyder bsnyder 329586 Oct 16 16:27 backport-util-concurrent-2.1.jar
--rw-r--r-- 1 bsnyder bsnyder 2334 Oct 16 16:27 broker-config.xml
--rw-r--r-- 1 bsnyder bsnyder 52915 Oct 16 16:27 commons-logging-1.1.jar
--rw-r--r-- 1 bsnyder bsnyder 2143211 Oct 16 16:27 derby-10.1.1.0.jar
--rw-r--r-- 1 bsnyder bsnyder 16030 Oct 16 16:27 geronimo-j2ee-management_1.0_spec-1.0.jar
--rw-r--r-- 1 bsnyder bsnyder 358085 Oct 16 16:27 log4j-1.2.12.jar
--rw-r--r-- 1 bsnyder bsnyder 1901653 Oct 16 16:27 spring-1.2.6.jar
--rw-r--r-- 1 bsnyder bsnyder 94713 Oct 16 16:27 xbean-spring-2.2.jar
-]]></script>
-</div></div>
-<p>Now it's time to configure ActiveMQ.</p>
-
-<h2 id="JBossIntegration-ConfiguringApacheActiveMQ">Configuring Apache ActiveMQ</h2>
-
-<p>The fifth step is to actually configure ActiveMQ for integration with JBoss. Remember that you should be sitting in the following directory:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-/opt/jboss-4.0.4.GA/server/default/deploy/activemq-ra.rar
-]]></script>
-</div></div>
-<p>You may or may not have installed JBoss in <code>/opt</code>, that doesn't particularly matter. What does matter is that you're sitting in the directory that was created above to hold the contents of the expanded ActiveMQ RAR file.</p>
-<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;">
-<p><strong><em>NOTE:</em></strong> A RAR file is a Resource adapter ARchive (RAR). Resource adapters are a concept from the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/" rel="nofollow">J2EE Connector Architecture (JCA)</a> and are used to interface with Enterprise Information Systems (EIS), i.e., systems external to the application server (e.g., relational databases, mainframes, MOMs, accounting systems, etc.). Resource adapters are often referred to as J2EE connectors and are very similar to the concept of a device driver for, say, a printer in that they contain information specific to connecting to a particular system. The difference with JCA is that that connection has been formalized in specification for Java. So the overall concepts of JCA is for connection to any EIS, but what does that mean? JCA 1.5 provides connectivity and more via the following contracts:</p>
-
-<p>Version 1.0 Contracts</p>
-
-<p>In version 1.0 of the Connector Architecture, three contracts are defined to address the functions mentioned above:</p>
-<ul><li>Connection Management Contract: Lets applications connect to an EIS through the resource adapter. It also allows the application server to pool connection requests to the EIS.</li><li>Transaction Management Contract: Allows an application to manage and perform transactional access across one-to-many EIS resource managers.</li><li>Security Contract: Provides support for secure access to the EIS.</li></ul>
-
-
-<p>New Contracts in Version 1.5</p>
-
-<p>In version 1.5 of the J2EE Connector Architecture, there are more contracts that a resource adapter must support, as new functionality and features made their way into the specification. A resource adapter can support these four new contracts by implementing the required interfaces defined in the specification for each contract.</p>
-<ul><li>Lifecycle Management Contract: Lets the application server manage the lifecycle – that is, the startup and shutdown functionality – of the resource adapter.</li><li>Work Management Contract: Allows the resource adapter to do work by submitting it to an application server for execution. Since the application server does the work for the resource adapter, the resource adapter needn't worry about thread management. Instead, the application server manages this aspect efficiently and can use thread pooling if necessary. Although the work management contract is not required (the resource adapter can choose to manage its own thread for work), it is definitely recommended.</li><li>Transaction Inflow Contract: Allows a resource adapter to propagate an imported transaction to an application server, as well as flow-in transaction completion and crash recovery initiated by an EIS.</li><li>Message Inflow Contract: Allows the resource adapter to synchronously or asynchronously deliver messages to endpoints in the application server, irrespective of message style, semantics, and infrastructure.</li></ul>
-
-
-<p><sub>Quoted from</sub> <sub><a shape="rect" class="external-link" href="http://java.sun.com/developer/technicalArticles/J2EE/connectorarch1_5/" rel="nofollow"><sub>What's New in the J2EE Connector Architecture 1.5</sub></a></sub></p>
-
-<p>For more information about JCA, please consult the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/index.jsp" rel="nofollow">J2EE Connector Architecture documentation</a>.</p>
-</div></div>
-<p>Open the <code>META-INF/ra.xml</code> file and look for the following section:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<config-property>
- <description>
- The URL to the ActiveMQ server that you want this connection to connect to. If using
- an embedded broker, this value should be 'vm://localhost'.
- </description>
- <config-property-name>ServerUrl</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value>tcp://localhost:61616</config-property-value>
-<!-- <config-property-value>vm://localhost</config-property-value> -->
- </config-property>
-]]></script>
-</div></div>
-<p>The section above is used to tell the ActiveMQ RAR where ActiveMQ is located. By default, the in-VM protocol is commented out in favor of the tcp protocol. This will find ActiveMQ running on any interface on the localhost on port 61616. It's ok to just leave this alone if you don't mind the inefficiency of communicating within the JVM via TCP. However, it is recommended that <code>vm://</code> transport be used for an embedded broker, so comment out the <code>tcp://</code> transport and uncomment the <code>vm://</code> transport. Below is an example of this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<config-property>
- <description>
- The URL to the ActiveMQ server that you want this connection to connect to. If using
- an embedded broker, this value should be 'vm://localhost'.
- </description>
- <config-property-name>ServerUrl</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <!-- <config-property-value>tcp://localhost:61616</config-property-value> -->
- <config-property-value>vm://localhost</config-property-value>
- </config-property>
-]]></script>
-</div></div>
-<p>Because we're embedding ActiveMQ inside of JBoss, it is more efficient to use the <code>vm://</code> transport, rather than to perform messaging over the <code>tcp://</code> transport.</p>
-
-<p>Now look further down the <code>META-INF/ra.xml</code> file and locate the following section:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<config-property>
- <description>
- Sets the XML configuration file used to configure the embedded ActiveMQ broker via
- Spring if using embedded mode.
-
- BrokerXmlConfig is the filename which is assumed to be on the classpath unless
- a URL is specified. So a value of foo/bar.xml would be assumed to be on the
- classpath whereas file:dir/file.xml would use the file system.
- Any valid URL string is supported.
- </description>
- <config-property-name>BrokerXmlConfig</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value></config-property-value>
- <!--
- <config-property-value>xbean:broker-config.xml</config-property-value>
- -->
- </config-property>
-]]></script>
-</div></div>
-<p>The section above needs to be changed to uncomment the second to last line and remove/replace the empty element that is above it. Below is an example of how this should be changed:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>META-INF/ra.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<config-property>
- <description>
- Sets the XML configuration file used to configure the embedded ActiveMQ broker via
- Spring if using embedded mode.
-
- BrokerXmlConfig is the filename which is assumed to be on the classpath unless
- a URL is specified. So a value of foo/bar.xml would be assumed to be on the
- classpath whereas file:dir/file.xml would use the file system.
- Any valid URL string is supported.
- </description>
- <config-property-name>BrokerXmlConfig</config-property-name>
- <config-property-type>java.lang.String</config-property-type>
- <config-property-value>xbean:broker-config.xml</config-property-value>
- </config-property>
-]]></script>
-</div></div>
-<p>This change tells the ActiveMQ RAR to read a configuration file named <code>broker-config.xml</code> (the <code>xbean:</code> that proceeds the filename is simply a hint to class doing the reading of the configuration file) which is located on the CLASSPATH. In this case, the <code>broker-config.xml</code> file is located in the <code>activemq-ra.rar</code> directory. Save the changes to that file and then open the <code>broker-config.xml</code> file.</p>
-
-<p>The <code>broker-config.xml</code> file <em>is</em> the ActiveMQ configuration file. This is the file used to configure ActiveMQ. The default contents of this file are usable, but should be customized to suit your environment. There are several items of note about this configuration. The most prominent sections to note in this file are the <code><persistenceAdapter></code> element and the <code><transportConnectors></code> and <code><networkConnectors></code> elements as seen below:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>broker-config.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<beans xmlns="http://activemq.org/config/1.0">
-
- <broker useJmx="true">
- ...
- <persistenceAdapter>
- <journaledJDBC journalLogFiles="5" dataDirectory="activemq-data"/>
- <!-- To use a different datasource, use th following syntax : -->
- <!--
- <journaledJDBC journalLogFiles="5" dataDirectory="../data" dataSource="#postgres-ds"/>
- -->
- </persistenceAdapter>
-
- <transportConnectors>
- <!-- prefixing a connector with discovery: causes the connector to be advertiesed over rendezvous -->
- <transportConnector uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
- </transportConnectors>
-
- <networkConnectors>
- <!-- by default just auto discover the other brokers -->
- <networkConnector uri="multicast://default"/>
- <!--
- <networkConnector uri="static://(tcp://host1:61616,tcp://host2:61616)"/>
- -->
- </networkConnectors>
-
- </broker>
-
-</beans>
-]]></script>
-</div></div>
-<p>The first change to this file is to add the brokerName attribute to the broker element and provide a name:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker useJmx="true" brokerName="bruce.broker1">
-]]></script>
-</div></div>
-<p>In addition, this same name is used further down the configuration to provide a name for the <code><transportConnector></code> element:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<transportConnector name="bruce.broker1" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
-]]></script>
-</div></div>
-<p>Now we'll tell ActiveMQ not to initialize JMX because we'll use the existing one that JBoss has:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<!-- put the following as the first child of the broker tag -->
-<managementContext><!-- we'll use an existing one (JBoss) instead of creating one -->
- <managementContext createConnector="false"/>
-</managementContext>
-]]></script>
-</div></div>
-<p>The <code><persistenceAdapter></code> element should be reconfigured to store its data in an appropriate place. On JBoss, that's most likely within the "data" directory of the server configuration you're using. We're going to set this dynamically using an XBean and Spring feature that allows us to inject system properties values into the configuration. First this needs to be enabled:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<!-- put the following as the first child of the beans element -->
-<bean xmlns="" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
-]]></script>
-</div></div>
-<p>Now, modify the <code>dataDirectory</code> attribute of the <code>journaledJDBC</code> element to be the following: <code>${jboss.server.data.dir}/activemq</code>.</p>
-
-<p>The <code><transportConnectors></code> element is used to advertise the ActiveMQ broker for client-to-broker communications and the <code><networkConnectors></code> element advertises the ActiveMQ broker for broker-to-broker communications. The default configuration is to use the ActiveMQ <a shape="rect" class="external-link" href="http://www.activemq.org/site/multicast-transport-reference.html" rel="nofollow">multicast transport</a> 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.</p>
-<div class="panel" style="background-color: #ccccff;border-width: 1px;"><div class="panelContent" style="background-color: #ccccff;">
-<p><strong><em>NOTE:</em></strong> 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 <a shape="rect" class="external-link" href="http://www.activemq.org/site/xbean-xml-reference-41.html" rel="nofollow">ActiveMQ 4.1 XML Reference</a>.</p>
-</div></div>
-<p>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:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ cd jboss-4.0.4.GA
-$ ./bin/run.sh -c default
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss-4.0.4.GA
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss-4.0.4.GA/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-15:34:47,999 INFO [Server] Starting JBoss (MX MicroKernel)...
-15:34:48,001 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
-15:34:48,004 INFO [Server] Home Dir: /opt/jboss-4.0.4.GA
-15:34:48,005 INFO [Server] Home URL: file:/opt/jboss-4.0.4.GA/
-15:34:48,007 INFO [Server] Patch URL: null
-15:34:48,007 INFO [Server] Server Name: default
-15:34:48,007 INFO [Server] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-15:34:48,011 INFO [Server] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-15:34:48,012 INFO [Server] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-15:34:48,017 INFO [Server] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-15:34:48,022 INFO [Server] Root Deployment Filename: jboss-service.xml
-...
-15:35:17,360 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)]
-Started in 28s:576ms
-]]></script>
-</div></div>
-<p>As long as JBoss comes up without error, you're ready to move on to the next step.</p>
-
-<h2 id="JBossIntegration-ConfiguringJBoss">Configuring JBoss</h2>
-
-<p>The sixth step is to configure JBoss to initialize and start ActiveMQ whenever JBoss starts up. This is accomplished using an XML file that abides by the <a shape="rect" class="external-link" href="http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd" rel="nofollow">JBoss JCA DTD</a> for data sources. Like most other Java application servers on the market, the JBoss architecture uses the J2EE Connector Architecture to manage connections of any kind including JDBC, JMS, etc. and the JBoss JCA DTD denotes the allowed contents for creating an XML data source instance to configure JBoss JCA. Below is an example XML data source instance for use with JBoss:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>activemq-jms-ds.xml</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!DOCTYPE connection-factories
- PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
- "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd">
-
-<connection-factories>
-
- <tx-connection-factory>
- <jndi-name>activemq/QueueConnectionFactory</jndi-name>
- <xa-transaction/>
- <track-connection-by-tx/>
- <rar-name>activemq-ra.rar</rar-name>
- <connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
- <ServerUrl>vm://localhost</ServerUrl>
- <!--
- <UserName>sa</UserName>
- <Password></Password>
- -->
- <min-pool-size>1</min-pool-size>
- <max-pool-size>200</max-pool-size>
- <blocking-timeout-millis>30000</blocking-timeout-millis>
- <idle-timeout-minutes>3</idle-timeout-minutes>
- </tx-connection-factory>
-
- <tx-connection-factory>
- <jndi-name>activemq/TopicConnectionFactory</jndi-name>
- <xa-transaction/>
- <track-connection-by-tx/>
- <rar-name>activemq-ra.rar</rar-name>
- <connection-definition>javax.jms.TopicConnectionFactory</connection-definition>
- <ServerUrl>vm://localhost</ServerUrl>
- <!--
- <UserName>sa</UserName>
- <Password></Password>
- -->
- <min-pool-size>1</min-pool-size>
- <max-pool-size>200</max-pool-size>
- <blocking-timeout-millis>30000</blocking-timeout-millis>
- <idle-timeout-minutes>3</idle-timeout-minutes>
- </tx-connection-factory>
-
- <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
- <attribute name="JNDIName">activemq/queue/outbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
- <attribute name="Type">javax.jms.Queue</attribute>
- <attribute name="Properties">PhysicalName=queue.outbound</attribute>
- </mbean>
-
- <mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.topic:name=inboundTopic">
- <attribute name="JNDIName">activemq/topic/inbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra.rar'</depends>
- <attribute name="Type">javax.jms.Topic</attribute>
- <attribute name="Properties">PhysicalName=topic.inbound</attribute>
- </mbean>
-
-</connection-factories>
-]]></script>
-</div></div>
-<p>This XML instance configures a JMS <code>QueueConnectionFactory</code> and a JMS <code>TopicConnectionFactory</code> and makes them available via JNDI. Also defined in this file are some {{AdminObject}}s which are used to specify a topic and a queue. This file should be dropped into the JBoss deploy directory. Its name (*-ds.xml) will cause it to be picked up by the JBoss deployer upon startup. Speaking of which, once this file is in place, a quick smoke test can be performed by simply starting up the JBoss server. Below is an example of the output that should be seen:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-=========================================================================
-
- JBoss Bootstrap Environment
-
- JBOSS_HOME: /opt/jboss
-
- JAVA: java
-
- JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000
--Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
-
- CLASSPATH: /opt/jboss/bin/run.jar:/lib/tools.jar
-
-=========================================================================
-
-22:55:48,686 INFO [Server] Starting JBoss (MX MicroKernel)...
-22:55:48,688 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
-22:55:48,690 INFO [Server] Home Dir: /opt/jboss-4.0.4.GA
-22:55:48,692 INFO [Server] Home URL: file:/opt/jboss-4.0.4.GA/
-22:55:48,695 INFO [Server] Patch URL: null
-22:55:48,697 INFO [Server] Server Name: default
-22:55:48,698 INFO [Server] Server Home Dir: /opt/jboss-4.0.4.GA/server/default
-22:55:48,701 INFO [Server] Server Home URL: file:/opt/jboss-4.0.4.GA/server/default/
-22:55:48,702 INFO [Server] Server Log Dir: /opt/jboss-4.0.4.GA/server/default/log
-22:55:48,704 INFO [Server] Server Temp Dir: /opt/jboss-4.0.4.GA/server/default/tmp
-22:55:48,706 INFO [Server] Root Deployment Filename: jboss-service.xml
-22:55:49,092 INFO [ServerInfo] Java version: 1.5.0_06,Apple Computer, Inc.
-22:55:49,101 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-64,"Apple Computer, Inc."
-22:55:49,102 INFO [ServerInfo] OS-System: Mac OS X 10.4.8,i386
-22:55:49,803 INFO [Server] Core system initialized
-22:55:53,379 INFO [WebService] Using RMI server codebase: http://rattlesnake:8083/
-22:55:53,400 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
-22:55:54,034 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50,
-no client SocketFactory, Server SocketFactory=class
-org.jboss.net.sockets.DefaultSocketFactory
-22:55:58,475 INFO [Embedded] Catalina naming disabled
-22:55:58,566 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath.
-Will load the default rule set.
-22:55:58,569 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath.
-Will load the default rule set.
-22:55:59,110 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
-22:55:59,114 INFO [Catalina] Initialization processed in 545 ms
-22:55:59,116 INFO [StandardService] Starting service jboss.web
-22:55:59,121 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.17
-22:55:59,179 INFO [StandardHost] XML validation disabled
-22:55:59,221 INFO [Catalina] Server startup in 105 ms
-22:55:59,600 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
-22:55:59,874 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
-22:56:00,899 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
-22:56:01,700 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp60528jbossws-exp.war/
-22:56:01,891 INFO [SubscriptionManager] Bound event dispatcher to java:/EventDispatcher
-22:56:02,203 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil,
-warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
-22:56:04,546 INFO [TomcatDeployer] deploy, ctxPath=/web-console,
-warUrl=.../deploy/management/console-mgr.sar/web-console.war/
-22:56:05,690 INFO [MailService] Mail Service bound to java:/Mail
-22:56:07,215 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
-.../deploy/activemq-ra.rar/
-22:56:07,452 INFO [XBeanXmlBeanDefinitionReader] Loading XML bean definitions from class
-path resource [broker-config.xml]
-22:56:07,750 INFO [ClassPathXmlApplicationContext] Bean factory for application context
-[org.apache.xbean.spring.context.ClassPathXmlApplicationContext;hashCode=13887543]:
-org.springframework.beans.factory.support.DefaultListableBeanFactory defining
-beans [org.apache.activemq.xbean.XBeanBrokerService]; root of BeanFactory hierarchy
-22:56:07,765 INFO [ClassPathXmlApplicationContext] 1 beans defined in application context
-[org.apache.xbean.spring.context.ClassPathXmlApplicationContext;hashCode=13887543]
-22:56:07,773 INFO [CollectionFactory] JDK 1.4+ collections available
-22:56:07,778 INFO [ClassPathXmlApplicationContext] Unable to locate MessageSource with name
-'messageSource': using default
-[org.springframework.context.support.DelegatingMessageSource@5fee96]
-22:56:07,781 INFO [ClassPathXmlApplicationContext] Unable to locate ApplicationEventMulticaster
-with name 'applicationEventMulticaster': using default
-[org.springframework.context.event.SimpleApplicationEventMulticaster@78c714]
-22:56:07,783 INFO [DefaultListableBeanFactory] Pre-instantiating singletons in factory
- [org.springframework.beans.factory.support.DefaultListableBeanFactory
-defining beans [org.apache.activemq.xbean.XBeanBrokerService]; root of BeanFactory hierarchy]
-22:56:08,181 INFO [BrokerService] ActiveMQ 4.0.2 JMS Message Broker (bruce.broker1) is starting
-22:56:08,181 INFO [BrokerService] For help or more information please see:
-http://incubator.apache.org/activemq/
-22:56:09,989 INFO [JDBCPersistenceAdapter] Database driver recognized:
-[apache_derby_embedded_jdbc_driver]
-22:56:11,026 INFO [JournalPersistenceAdapter] Journal Recovery Started from: Active Journal:
-using 5 x 20.0 Megs at: /opt/jboss-4.0.4.GA/activemq-data/journal
-22:56:11,169 INFO [JournalPersistenceAdapter] Journal Recovered: 0 message(s) in transactions recovered.
-22:56:11,489 INFO [TransportServerThreadSupport] Listening for connections at: tcp://rattlesnake:61616
-22:56:11,491 WARN [MulticastDiscoveryAgent] brokerName not set
-22:56:11,519 INFO [TransportConnector] Connector bruce.broker1 Started
-22:56:11,522 INFO [NetworkConnector] Network Connector bridge Started
-22:56:11,522 INFO [BrokerService] ActiveMQ JMS Message Broker
-(bruce.broker1, ID:rattlesnake-59052-1161060967859-1:0) started
-22:56:11,556 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-ha-local-jdbc.rar
-22:56:11,599 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-ha-xa-jdbc.rar
-22:56:11,623 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-local-jdbc.rar
-22:56:11,647 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jboss-xa-jdbc.rar
-22:56:11,737 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
-.../deploy/jms/jms-ra.rar
-22:56:11,847 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in
-.../deploy/mail-ra.rar
-22:56:12,251 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=activemq/QueueConnectionFactory' to
-JNDI name 'java:activemq/QueueConnectionFactory'
-22:56:12,258 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=activemq/TopicConnectionFactory' to
-JNDI name 'java:activemq/TopicConnectionFactory'
-22:56:12,265 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQQueue'
-at 'activemq/queue/outbound'
-22:56:12,330 INFO [AdminObject] Bound admin object 'org.apache.activemq.command.ActiveMQTopic'
-at 'activemq/topic/inbound'
-22:56:13,246 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
-'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
-22:56:13,842 INFO [A] Bound to JNDI name: queue/A
-22:56:13,845 INFO [B] Bound to JNDI name: queue/B
-22:56:13,846 INFO [C] Bound to JNDI name: queue/C
-22:56:13,848 INFO [D] Bound to JNDI name: queue/D
-22:56:13,850 INFO [ex] Bound to JNDI name: queue/ex
-22:56:13,876 INFO [testTopic] Bound to JNDI name: topic/testTopic
-22:56:13,879 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
-22:56:13,880 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
-22:56:13,883 INFO [testQueue] Bound to JNDI name: queue/testQueue
-22:56:13,994 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
-22:56:14,055 INFO [DLQ] Bound to JNDI name: queue/DLQ
-22:56:14,375 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
-'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
-22:56:14,525 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
-22:56:14,991 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
-22:56:15,071 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
-22:56:15,082 INFO [JkMain] Jk running ID=0 time=0/25 config=null
-22:56:15,108 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)]
-Started in 26s:398ms
-]]></script>
-</div></div>
-<p>Note the startup messages from both ActiveMQ and from the <code>AdminObject}}s creating an {{ActiveMQQueue</code> and an <code>ActiveMQTopic</code>. These are good indications that the configuration is correct, but needs to be verified a bit further. This is covered in the next section.</p>
-
-<h2 id="JBossIntegration-TestingtheIntegration">Testing the Integration</h2>
-
-<p>The seventh and final step is to perform a slightly more comprehensive smoke test of the integration. This can be accomplished using Apache Ant via the examples that come with the ActiveMQ binary distribution. An Ant build.xml file is included which provides easy access to a simple consumer and a simple producer. The producer will be used to send messages that are received by the consumer. To proceed with this testing, just follow the steps below:</p>
-<ol><li>In the first terminal, start up JBoss. The same startup script can be used here as was used above.</li><li>In the second terminal, use the commands below to run the ActiveMQ consumer:
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ cd /opt/incubator-activemq-4.0.2/examples #note in activemq v5 the directory is just "example" not "examples"
-$ ant consumer
-Buildfile: build.xml
-
-init:
- [mkdir] Created dir: /opt/incubator-activemq-4.0.2/example/target/classes
- [mkdir] Created dir: /opt/incubator-activemq-4.0.2/example/src/ddl
-
-compile:
- [javac] Compiling 6 source files to /opt/incubator-activemq-4.0.2/example/target/classes
-
-consumer:
- [echo] Running consumer against server at $url = tcp://localhost:61616 for subject $subject = TEST.FOO
- [java] Connecting to URL: tcp://localhost:61616
- [java] Consuming queue: TEST.FOO
- [java] Using non-durable subscription
- [java] We are about to wait until we consume: 10 message(s) then we will shutdown
-]]></script>
-</div></div></li><li>In the third terminal, use the commands below to run the ActiveMQ producer:
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-$ cd /opt/incubator-activemq-4.0.2/examples
-$ ant producer
-Buildfile: build.xml
-
-init:
-
-compile:
-
-producer:
- [echo] Running producer against server at $url = tcp://localhost:61616 for subject $subject = TEST.FOO
- [java] Connecting to URL: tcp://localhost:61616
- [java] Publishing a Message with size 1000 to queue: TEST.FOO
- [java] Using non-durable publishing
- [java] Sleeping between publish 0 ms
- [java] Sending message: Message: 0 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 1 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 2 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 3 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 4 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 5 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 6 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 7 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 8 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Sending message: Message: 9 sent at: Mon Oct 16 23:21:08 MDT 2006 ...
- [java] Done.
- [java] connection {
- [java] session {
- [java] messageCount{ count: 10 unit: count startTime: 1161062468001 lastSampleTime:
-1161062468340 description: Number of messages exchanged }
- [java] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime: 31.5
-averageTimeExMinMax: 21.5 averagePerSecond: 31.746031746031747
-averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468002 lastSampleTime:
-1161062468340 description: Time taken to process a message (thoughtput rate) }
- [java] pendingMessageCount{ count: 0 unit: count startTime: 1161062468001 lastSampleTime:
-1161062468001 description: Number of pending messages }
- [java] expiredMessageCount{ count: 0 unit: count startTime: 1161062468001 lastSampleTime:
-1161062468001 description: Number of expired messages }
- [java] messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0
-averageTimeExMinMax: 0.0 averagePerSecond: 0.0
-averagePerSecondExMinMax: 0.0 unit: millis startTime: 1161062468002 lastSampleTime: 1161062468002
-description: Time spent by a message before being delivered }
- [java] durableSubscriptionCount{ count: 0 unit: count startTime: 1161062468002 lastSampleTime:
-1161062468002 description: The number of durable
-subscriptions }
-
- [java] producers {
- [java] producer queue://TEST.FOO {
- [java] messageCount{ count: 10 unit: count startTime: 1161062468025 lastSampleTime:
-1161062468340 description: Number of messages processed }
- [java] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime:
-31.5 averageTimeExMinMax: 21.5 averagePerSecond:
-31.746031746031747 averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468025
-lastSampleTime: 1161062468340 description: Time taken to
-process a message (thoughtput rate) }
- [java] pendingMessageCount{ count: 0 unit: count startTime: 1161062468025 lastSampleTime:
-1161062468025 description: Number of pending messages }
- [java] messageRateTime{ count: 10 maxTime: 142 minTime: 1 totalTime: 315 averageTime: 31.5
-averageTimeExMinMax: 21.5 averagePerSecond:
-31.746031746031747 averagePerSecondExMinMax: 46.51162790697674 unit: millis startTime: 1161062468025
-lastSampleTime: 1161062468340 description: Time taken to
-process a message (thoughtput rate) }
- [java] expiredMessageCount{ count: 0 unit: count startTime: 1161062468025 lastSampleTime:
-1161062468025 description: Number of expired messages }
- [java] messageWaitTime{ count: 0 maxTime: 0 minTime: 0 totalTime: 0 averageTime: 0.0
-averageTimeExMinMax: 0.0 averagePerSecond: 0.0
-averagePerSecondExMinMax: 0.0 unit: millis startTime: 1161062468025 lastSampleTime: 1161062468025
-description: Time spent by a message before being delivered }
- [java] }
- [java] }
- [java] consumers {
- [java] }
- [java] }
- [java] }
-]]></script>
-</div></div></li></ol>
-
-
-<p>Step 1 above just starts up JBoss. Step 2 above starts up a simple message consumer that comes with ActiveMQ. Step 3 above starts up a simple message producer that comes with ActiveMQ. Though the message consumer and message producer are simple utilities, the each one accepts many parameters making them extremely useful for testing ActiveMQ configurations.</p>
-
-<p>To paraphrase, what just happened was that the message producer sent 10 messages to the TEST.FOO destination and the message consumer received 10 messages from the TEST.FOO destination. Despite being a simple test, it does utilize the ActiveMQ broker, albeit only on a single machine. The next logical step is to set up a full network of ActiveMQ brokers.</p>
-
-<p>After setting up one broker within one instance of JBoss, setting up another is made much easier, but requires another machine or operating system instance. But that's a whole separate article and something to address another day.</p>
-
-<h2 id="JBossIntegration-Conclusion">Conclusion</h2>
-
-<p>What has been demonstrated here is the integration of ActiveMQ with the JBoss application server. This integration is quite common and performed by many enterprises. I hope that this was helpful to people interested in the integration of ActiveMQ with JBoss application server. If you have any questions or are interested in consulting services surrounding ActiveMQ, please <a shape="rect" class="external-link" href="http://www.logicblaze.com/contact.jsp" rel="nofollow">contact us</a> for more information.</p>
-
-<h3 id="JBossIntegration-Resources">Resources</h3>
-
-<p>Below are the configurations for use with both Spring 1.x and Spring 2.x:</p>
-
-
-
-
-<div class="plugin_attachments_container">
- <div class="plugin_attachments_table_container">
- <fieldset class="hidden">
- <input type="hidden" class="plugin_attachments_macro_render_param" name="pageId" value="67786">
- <input type="hidden" name="deleteConfirmMessage" value="Are you sure you want to send the attached file " _0="_0" to="to" the="the" trash="trash" only="only" a="a" space="space" administrator="administrator" can="can" undo="undo" this="this" action.="action.">
- <input type="hidden" name="outputType" value="display">
- </fieldset>
-
-
-
-
-
-
-
-
-
-
-
-<table class="attachments aui"><thead><tr><th colspan="1" rowspan="1" class="expand-column attachment-summary-toggle"> </th><th colspan="1" rowspan="1" class="filename-column"> <a shape="rect" href="integrating-apache-activemq-with-jboss.xml?sortBy=name&sortOrder=ascending">File</a>
- </th><th colspan="1" rowspan="1" class="modified-column"> <span class="propersortedby $sortOrder"><a shape="rect" href="integrating-apache-activemq-with-jboss.xml?sortBy=date&sortOrder=descending">Modified</a></span>
- </th></tr></thead><tbody><tr class="attachment-row" id="attachment-59670763" data-attachment-id="59670763" data-attachment-idx="1"><td colspan="1" rowspan="1" class="attachment-summary-toggle">
- <span class="icon icon-section-closed" title="Show more info"></span>
- </td><td colspan="1" rowspan="1" class="filename-column">
-
-
-
-
-
-<span class="icon icon-file-unknown" title="File">File</span> <a shape="rect" class="filename" href="jboss-integration.data/amq-spring-1.2.6.tgz?api=v2" title="Download" data-filename="amq-spring-1.2.6.tgz" data-type="application/x-tar" data-linked-resource-container-id="67786">
- amq-spring-1.2.6.tgz
- </a>
- </td><td colspan="1" rowspan="1" class="attachment-created modified-column">
- <span>Oct 03, 2007</span>
- <span>by</span>
- <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~bsnyder">Bruce Snyder</a> </td></tr><tr class="attachment-summary attachment-summary-59670763 hidden" data-attachment-id="59670763" data-attachment-filename="amq-spring-1.2.6.tgz"><td colspan="1" rowspan="1" class="attachment-summary-toggle"></td><td colspan="2" rowspan="1" class="attachment-details-wrapper">
-
-
- <p class="attachment-labels">Labels</p>
-
-<div class="labels-section-content content-column" entityid="59670763" entitytype="attachment">
- <div class="labels-content">
-
- <ul class="label-list has-pen"><li class="no-labels-message">
- No labels
- </li><li class="labels-edit-container">
- <a shape="rect" class="show-labels-editor" href="#" title="Edit Labels">
- <span class="aui-icon aui-icon-small aui-iconfont-edit-small">Edit Labels</span>
- </a>
- </li></ul>
-
- </div>
-</div>
-
- <div class="attachment-history-wrapper"></div>
-
- <div class="attachment-buttons">
- <a shape="rect" class="aui-button previewAttachmentLink" data-filename="amq-spring-1.2.6.tgz" data-file-src="/confluence/download/attachments/67786/amq-spring-1.2.6.tgz?api=v2" data-linked-resource-default-alias="amq-spring-1.2.6.tgz" data-mime-type="application/x-tar" data-linked-resource-container-id="67786" data-linked-resource-id="59670763">Preview</a>
-
- </div>
- </td></tr><tr class="attachment-row" id="attachment-59670764" data-attachment-id="59670764" data-attachment-idx="2"><td colspan="1" rowspan="1" class="attachment-summary-toggle">
- <span class="icon icon-section-closed" title="Show more info"></span>
- </td><td colspan="1" rowspan="1" class="filename-column">
-
-
-
-
-
-<span class="icon icon-file-unknown" title="File">File</span> <a shape="rect" class="filename" href="jboss-integration.data/amq-spring-2.0.tgz?api=v2" title="Download" data-filename="amq-spring-2.0.tgz" data-type="application/x-tar" data-linked-resource-container-id="67786">
- amq-spring-2.0.tgz
- </a>
- </td><td colspan="1" rowspan="1" class="attachment-created modified-column">
- <span>Oct 03, 2007</span>
- <span>by</span>
- <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~bsnyder">Bruce Snyder</a> </td></tr><tr class="attachment-summary attachment-summary-59670764 hidden" data-attachment-id="59670764" data-attachment-filename="amq-spring-2.0.tgz"><td colspan="1" rowspan="1" class="attachment-summary-toggle"></td><td colspan="2" rowspan="1" class="attachment-details-wrapper">
-
-
- <p class="attachment-labels">Labels</p>
-
-<div class="labels-section-content content-column" entityid="59670764" entitytype="attachment">
- <div class="labels-content">
-
- <ul class="label-list has-pen"><li class="no-labels-message">
- No labels
- </li><li class="labels-edit-container">
- <a shape="rect" class="show-labels-editor" href="#" title="Edit Labels">
- <span class="aui-icon aui-icon-small aui-iconfont-edit-small">Edit Labels</span>
- </a>
- </li></ul>
-
- </div>
-</div>
-
- <div class="attachment-history-wrapper"></div>
-
- <div class="attachment-buttons">
- <a shape="rect" class="aui-button previewAttachmentLink" data-filename="amq-spring-2.0.tgz" data-file-src="/confluence/download/attachments/67786/amq-spring-2.0.tgz?api=v2" data-linked-resource-default-alias="amq-spring-2.0.tgz" data-mime-type="application/x-tar" data-linked-resource-container-id="67786" data-linked-resource-id="59670764">Preview</a>
-
- </div>
- </td></tr></tbody></table>
- </div>
- <div class="plugin_attachments_upload_container">
- </div>
-
- <div>
- <a shape="rect" class="download-all-link" href="/confluence/pages/downloadallattachments.action?pageId=67786" title="Download all the latest versions of attachments on this page as single zip file.">Download All</a>
- </div>
-</div></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="bbc703bb-67f6-445e-be5e-58cf87290290" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Integrating Apache ActiveMQ with JBoss"></page></link></parameter></structured-macro></div>
diff --git a/jca-container.xml b/jca-container.xml
index 1973feb..260b5b3 100644
--- a/jca-container.xml
+++ b/jca-container.xml
@@ -1,22 +1,22 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-information"><p class="title">The JCA Container is moving</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="16f901d0-bd02-4fa3-9c19-e0c3ae27f48b" ac:name="info" ac:schema-version="1"><parameter ac:name="title">The JCA Container is moving</parameter><rich-text-body>
<p>We will continune to support the ActiveMQ JCA Container up until ActiveMQ 3.1.</p>
-<p>After that point we will be moving to <a shape="rect" class="external-link" href="http://jencks.codehaus.org/" rel="nofollow">Jencks</a> which is a migration of the ActiveMQ codebase together with code <a shape="rect" class="external-link" href="http://geronimo.apache.org">Geronimo</a> and from some other contributors.</p>
+<p>After that point we will be moving to <a shape="rect" href="http://jencks.codehaus.org/">Jencks</a> which is a migration of the ActiveMQ codebase together with code <a shape="rect" href="http://geronimo.apache.org">Geronimo</a> and from some other contributors.</p>
<p>Jencks is completely logically equivalent to the ActiveMQ JCA Container and migrating to it is pretty simple (mostly just a class name change for the JCA container) - though the benefits of Jencks are that it supports full XA recovery and works well with Geronimo's TransactionManager and WorkManager.</p>
-<p>So we do recommend you migrate to <a shape="rect" class="external-link" href="http://jencks.codehaus.org/" rel="nofollow">Jencks</a> whenever its easy for you to do so; projects such as <a shape="rect" class="external-link" href="http://lingo.codehaus.org/" rel="nofollow">Lingo</a> and <a shape="rect" class="external-link" href="http://servicemix.org/" rel="nofollow">ServiceMix</a> already have and it was an easy migration.</p></div></div>
+<p>So we do recommend you migrate to <a shape="rect" href="http://jencks.codehaus.org/">Jencks</a> whenever its easy for you to do so; projects such as <a shape="rect" href="http://lingo.codehaus.org/">Lingo</a> and <a shape="rect" href="http://servicemix.org/">ServiceMix</a> already have and it was an easy migration.</p></rich-text-body></structured-macro>
<p>We have a lightweight, easily embeddable Spring based JCA container which allows us to provide MDB like functionality inside any Java application without requiring a full EJB container.</p>
<p>This allows us to support <em>message driven pojos</em> using dependency injection for efficient JMS consumption together with pooling of the pojos using lightweight containers rather than relying on EJB.</p>
<p>The JCA container also makes it easy to programatically at runtime create new message driven pojos rather than relying on the fixed deployment-time only option with EJB.</p>
-<h2 id="JCAContainer-Example">Example</h2>
+<h2>Example</h2>
-<p>Here is <a shape="rect" class="external-link" href="http://docs.codehaus.org/download/attachments/23776/spring.xml" rel="nofollow">an example</a> of the Spring XML to deploy a pojo (EchoBean) on an inbound JMS subscription, on a topic in this particular example.</p>
+<p>Here is <a shape="rect" href="http://docs.codehaus.org/download/attachments/23776/spring.xml">an example</a> of the Spring XML to deploy a pojo (EchoBean) on an inbound JMS subscription, on a topic in this particular example.</p>
-<p>Firstly we can create as many JCAContainer instances as we need; currently we create one per JCA <a shape="rect" href="resource-adapter.xml">Resource Adapter</a> (i.e. JMS provider). The JCAContainer also uses a WorkManager which is JCA speak for a bunch of thread pools. We can share the WorkManager across JCAContainer instances or create one per JCAContainer.</p>
+<p>Firstly we can create as many JCAContainer instances as we need; currently we create one per JCA <link><page ri:content-title="Resource Adapter"></page></link> (i.e. JMS provider). The JCAContainer also uses a WorkManager which is JCA speak for a bunch of thread pools. We can share the WorkManager across JCAContainer instances or create one per JCAContainer.</p>
<p>Once we have a JCAContainer we can add as many JCAConnector instances to it, via the <strong>addConnector</strong> factory method, each one representing a JMS subscription and providing a pool of POJOs to process the message. The subscription details are specified by an activationSpec property which is a bean typically dependent on the JMS provider; this allows providers to add new extensions while leaving your application code pure JMS.</p>
@@ -24,19 +24,19 @@
<p><strong>Note</strong> you must set the <strong>singleton</strong> flag to false for the POJOs if they are not thread safe.</p>
-<h2 id="JCAContainer-Requirements">Requirements</h2>
+<h2>Requirements</h2>
<p>To be able to use the JCA container, you just need the following jars on your classpath</p>
-<ul><li><a shape="rect" href="initial-configuration.xml">required ActiveMQ jars</a> if you are using ActiveMQ as your JMS provider - or your provider's jars if not</li><li>activemq-container.jar</li><li>spring.jar</li><li>J2EE.jar (for the JCA APIs). If you are inside Tomcat, it doesn't like j2ee.jar on the classpath, so use the individual jars from Geronimo - e.g. geronimo-spec-j2ee-connector-*.jar for the JCA APIs</li><li>commons-collections.jar</li><li>commons-pool.jar</li><li>aopalliance.jar (a temporary dependency introduced by Spring's use of the TargetSource, we should be able to remove this dependency later on).</li></ul>
+<ul><li><link><page ri:content-title="Initial Configuration"></page><link-body>required ActiveMQ jars</link-body></link> if you are using ActiveMQ as your JMS provider - or your provider's jars if not</li><li>activemq-container.jar</li><li>spring.jar</li><li>J2EE.jar (for the JCA APIs). If you are inside Tomcat, it doesn't like j2ee.jar on the classpath, so use the individual jars from Geronimo - e.g. geronimo-spec-j2ee-connector-*.jar for the JCA APIs</li><li>commons-collections.jar</li><li>commons-pool.jar</li><li>aopalliance.jar (a temporary dependency introduced by Spring's use of the TargetSource, we should be able to remove this dependency later on).</li></ul>
<p><strong>Note</strong> the classes and resources in activemq-container.jar are not included in activemq.jar</p>
<p>To use the JCA Container please use the 2.x code release. Several problems were found and fixed with the 1.x branch of code.</p>
-<h2 id="JCAContainer-Thingstowatch">Things to watch</h2>
+<h2>Things to watch</h2>
-<p>By default the ActiveMQ <a shape="rect" href="resource-adapter.xml">Resource Adapter</a> will try to connect to a remote broker (ie. tcp://localhost:61616). Also if you want to set how the broker is configured via XML then try the <em>brokerXmlConfig</em> property.</p>
+<p>By default the ActiveMQ <link><page ri:content-title="Resource Adapter"></page></link> will try to connect to a remote broker (ie. tcp://localhost:61616). Also if you want to set how the broker is configured via XML then try the <em>brokerXmlConfig</em> property.</p>
<p><em>Note:</em> In AMQ 3.x the default behavior is the ActiveMQ resource adapter will create an embedded broker</p></div>
diff --git a/jdbc-master-slave.xml b/jdbc-master-slave.xml
index 721ea9a..3054e0a 100644
--- a/jdbc-master-slave.xml
+++ b/jdbc-master-slave.xml
@@ -1,60 +1,57 @@
-<div class="wiki-content maincontent"><h2 id="JDBCMasterSlave-JDBCMasterSlave">JDBC Master Slave</h2>
+<div class="wiki-content maincontent"><h2>JDBC Master Slave</h2>
<p>First supported in ActiveMQ version 4.1</p>
<p>If you are using pure JDBC and not using the high performance journal then you are generally relying on your database as your single point of failure and persistence engine. If you do not have really high performance requirements this approach can make a lot of sense as you have a single persistence engine to backup and manage etc.</p>
-<h3 id="JDBCMasterSlave-Startup">Startup</h3>
+<h3>Startup</h3>
<p>When using just JDBC as the data source you can use a Master Slave approach, running as many brokers as you wish as this diagram shows. On startup one master grabs an exclusive lock in the broker database - all other brokers are slaves and pause waiting for the exclusive lock.</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="jdbc-master-slave.data/Startup.png" data-image-src="/confluence/download/attachments/35908/Startup.png?version=1&modificationDate=1153463898000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3244" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Startup.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35908" data-linked-resource-container-version="19"></span></p>
+<p><image><attachment ri:filename="Startup.png"></attachment></image></p>
-<p>Clients should be using the <a shape="rect" href="failover-transport-reference.xml">Failover Transport</a> to connect to the available brokers. e.g. using a URL something like the following</p>
+<p>Clients should be using the <link><page ri:content-title="Failover Transport Reference"></page><link-body>Failover Transport</link-body></link> to connect to the available brokers. e.g. using a URL something like the following</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="db1beb4a-1c76-4570-a616-b7c6c06728ba" ac:name="code" ac:schema-version="1"><plain-text-body>
failover:(tcp://broker1:61616,tcp://broker2:61616,tcp://broker3:61616)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Only the master broker starts up its transport connectors and so the clients can only connect to the master.</p>
-<h3 id="JDBCMasterSlave-Masterfailure">Master failure</h3>
+<h3>Master failure</h3>
<p>If the master looses connection to the database or looses the exclusive lock then it immediately shuts down. If a master shuts down or fails, one of the other slaves will grab the lock and so the topology switches to the following diagram</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="jdbc-master-slave.data/MasterFailed.png" data-image-src="/confluence/download/attachments/35908/MasterFailed.png?version=1&modificationDate=1153463898000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3264" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="MasterFailed.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35908" data-linked-resource-container-version="19"></span></p>
+<p><image><attachment ri:filename="MasterFailed.png"></attachment></image></p>
<p>One of the other other slaves immediately grabs the exclusive lock on the database 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>
-<h3 id="JDBCMasterSlave-Masterrestart">Master restart</h3>
+<h3>Master restart</h3>
<p>At any time you can restart other brokers which join the cluster and start as slaves waiting to become a master if the master is shutdown or a failure occurs. So the following topology is created after a restart of an old master...</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="jdbc-master-slave.data/MasterRestarted.png" data-image-src="/confluence/download/attachments/35908/MasterRestarted.png?version=1&modificationDate=1153463898000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3252" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="MasterRestarted.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35908" data-linked-resource-container-version="19"></span></p>
+<p><image><attachment ri:filename="MasterRestarted.png"></attachment></image></p>
-<h3 id="JDBCMasterSlave-ConfiguringJDBCMasterSlave">Configuring JDBC Master Slave</h3>
+<h3>Configuring JDBC Master Slave</h3>
<p>By default if you use the <strong><jdbcPersistenceAdapter/></strong> to avoid the high performance journal you will be using JDBC Master Slave by default. You just need to run more than one broker and point the client side URIs to them to get master/slave. This works because they both try an acquire an exclusive lock on a shared table in the database and only one will succeed.</p>
<p>The following example shows how to configure the ActiveMQ broker in JDBC Master Slave mode</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="19af32e7-f11e-422b-be63-ffa96eff017b" ac:name="code" ac:schema-version="1"><plain-text-body>
<beans>
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker xmlns="http://activemq.apache.org/schema/core">
+ <broker xmlns="http://activemq.apache.org/schema/core">
<destinationPolicy>
<policyMap><policyEntries>
- <policyEntry topic="FOO.>">
+ <policyEntry topic="FOO.>">
<dispatchPolicy>
<strictOrderDispatchPolicy />
</dispatchPolicy>
@@ -68,15 +65,15 @@
<persistenceAdapter>
- <jdbcPersistenceAdapter dataDirectory="${activemq.base}/activemq-data"/>
+ <jdbcPersistenceAdapter dataDirectory="${activemq.base}/activemq-data"/>
<!--
- <jdbcPersistenceAdapter dataDirectory="activemq-data" dataSource="#oracle-ds"/>
+ <jdbcPersistenceAdapter dataDirectory="activemq-data" dataSource="#oracle-ds"/>
-->
</persistenceAdapter>
<transportConnectors>
- <transportConnector name="default" uri="tcp://localhost:61616"/>
+ <transportConnector name="default" uri="tcp://localhost:61616"/>
</transportConnectors>
</broker>
@@ -85,50 +82,50 @@
<!-- Postgres DataSource Sample Setup -->
<!--
- <bean id="postgres-ds" class="org.postgresql.ds.PGPoolingDataSource">
- <property name="serverName" value="localhost"/>
- <property name="databaseName" value="activemq"/>
- <property name="portNumber" value="0"/>
- <property name="user" value="activemq"/>
- <property name="password" value="activemq"/>
- <property name="dataSourceName" value="postgres"/>
- <property name="initialConnections" value="1"/>
- <property name="maxConnections" value="10"/>
+ <bean id="postgres-ds" class="org.postgresql.ds.PGPoolingDataSource">
+ <property name="serverName" value="localhost"/>
+ <property name="databaseName" value="activemq"/>
+ <property name="portNumber" value="0"/>
+ <property name="user" value="activemq"/>
+ <property name="password" value="activemq"/>
+ <property name="dataSourceName" value="postgres"/>
+ <property name="initialConnections" value="1"/>
+ <property name="maxConnections" value="10"/>
</bean>
-->
<!-- MySql DataSource Sample Setup -->
<!--
- <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
- <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
- <property name="url" value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
- <property name="username" value="activemq"/>
- <property name="password" value="activemq"/>
- <property name="poolPreparedStatements" value="true"/>
+ <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
+ <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
+ <property name="url" value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
+ <property name="username" value="activemq"/>
+ <property name="password" value="activemq"/>
+ <property name="poolPreparedStatements" value="true"/>
</bean>
-->
<!-- Oracle DataSource Sample Setup -->
<!--
- <bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
- <property name="driverClassName" value="oracle.jdbc.driver.OracleDriver"/>
- <property name="url" value="jdbc:oracle:thin:@localhost:1521:AMQDB"/>
- <property name="username" value="scott"/>
- <property name="password" value="tiger"/>
- <property name="poolPreparedStatements" value="true"/>
+ <bean id="oracle-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
+ <property name="driverClassName" value="oracle.jdbc.driver.OracleDriver"/>
+ <property name="url" value="jdbc:oracle:thin:@localhost:1521:AMQDB"/>
+ <property name="username" value="scott"/>
+ <property name="password" value="tiger"/>
+ <property name="poolPreparedStatements" value="true"/>
</bean>
-->
<!-- Embedded Derby DataSource Sample Setup -->
<!--
- <bean id="derby-ds" class="org.apache.derby.jdbc.EmbeddedDataSource">
- <property name="databaseName" value="derbydb"/>
- <property name="createDatabase" value="create"/>
+ <bean id="derby-ds" class="org.apache.derby.jdbc.EmbeddedDataSource">
+ <property name="databaseName" value="derbydb"/>
+ <property name="createDatabase" value="create"/>
</bean>
-->
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
+
</div>
diff --git a/jdbc-support.xml b/jdbc-support.xml
index f071449..41ce333 100644
--- a/jdbc-support.xml
+++ b/jdbc-support.xml
@@ -1,32 +1,24 @@
-<div class="wiki-content maincontent"><p>We support a range of SQL databases for message persistence such as</p><ul><li>Apache Derby</li><li>Axion</li><li>DB2</li><li>HSQL</li><li>Informix</li><li>MaxDB</li><li>MySQL</li><li>Oracle</li><li>Postgresql</li><li><a shape="rect" href="sqlserver.xml">SQLServer</a></li><li><a shape="rect" href="sybase.xml">Sybase</a></li></ul><p>as well as a number of generic JDBC providers.</p><h3 id="JDBCSupport-Auto-discoveryofyourJDBCprovider">Auto-discovery of your JDBC provider</h3><p>We try to auto-detect from the JDBC driver which JDBCAdapter to use via these <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tree;f=activemq-jdbc-store/src/main/resources/META-INF/services/org/apache/activemq/store/jdbc">config files</a> and the return string from the JDBC driver.</p><p>If you have a JDBC database which we don't support then please let us know what JDBC driver string you're getting and <a shape="rect" href="discussion-forums.xml">drop us a note</a> or raise an issue in our <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ">support database</a> and we'll fix it pretty quickly.</p><p>If your database is not in the above list it is normally a matter of tweaking the StatementProvider to ensure that the JDBCMessageStore uses the right flavour of SQL. So normally most databases support one of these providers...</p><ul><li>org.activemq.store.jdbc.adapter.BlobJDBCAdapter</li><li>org.activemq.store.jdbc.adapter.BytesJDBCAdapter</li><li>org.activemq.store.jdbc.adapter.DefaultJDBCAdapter</li><li>org.activemq.store.jdbc.adapter.ImageJDBCAdapter</li></ul><p>You can explicitly specify the JDBC adaptor using its xbean identifier, inside the activemq.xml...</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<jdbcPersistenceAdapter adapter="postgresql-jdbc-adapter"/>
-]]></script>
-</div></div><h3 id="JDBCSupport-CustomizingtheSQLDDL">Customizing the SQL DDL</h3><p>You can confiugure the various SQL datatypes - such as column sizes and so forth - using the statements element</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <broker useJmx="false">
+<div class="wiki-content maincontent"><p>We support a range of SQL databases for message persistence such as</p><ul><li>Apache Derby</li><li>Axion</li><li>DB2</li><li>HSQL</li><li>Informix</li><li>MaxDB</li><li>MySQL</li><li>Oracle</li><li>Postgresql</li><li><link><page ri:content-title="SQLServer"></page></link></li><li><link><page ri:content-title="Sybase"></page></link></li></ul><p>as well as a number of generic JDBC providers.</p><h3>Auto-discovery of your JDBC provider</h3><p>We try to auto-detect from the JDBC driver which JDBCAdapter to use via these <a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tree;f=activemq-jdbc-store/src/main/resources/META-INF/services/org/apache/activemq/store/jdbc">config files</a> and the return string from the JDBC driver.</p><p>If you have a JDBC database which we don't support then please let us know what JDBC driver string you're getting and <link><page ri:content-title="Discussion Forums"></page><plain-text-link-body>drop us a note</plain-text-link-body></link> or raise an issue in our <a shape="rect" href="http://issues.apache.org/activemq/browse/AMQ">support database</a> and we'll fix it pretty quickly.</p><p>If your database is not in the above list it is normally a matter of tweaking the StatementProvider to ensure that the JDBCMessageStore uses the right flavour of SQL. So normally most databases support one of these providers...</p><ul><li>org.activemq.store.jdbc.adapter.BlobJDBCAdapter</li><li>org.activemq.store.jdbc.adapter.BytesJDBCAdapter</li><li>org.activemq.store.jdbc.adapter.DefaultJDBCAdapter</li><li>org.activemq.store.jdbc.adapter.ImageJDBCAdapter</li></ul><p>You can explicitly specify the JDBC adaptor using its xbean identifier, inside the activemq.xml...</p><structured-macro ac:macro-id="45d22476-142f-4b05-8879-76bd163c8efe" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><jdbcPersistenceAdapter adapter="postgresql-jdbc-adapter"/>
+</plain-text-body></structured-macro><h3>Customizing the SQL DDL</h3><p>You can confiugure the various SQL datatypes - such as column sizes and so forth - using the statements element</p><structured-macro ac:macro-id="28fb77cc-b99c-46bb-a02a-5bb4f4df4f81" ac:name="code" ac:schema-version="1"><plain-text-body> <broker useJmx="false">
<persistenceAdapter>
- <journaledJDBC useJournal="false">
+ <journaledJDBC useJournal="false">
<statements>
- <statements stringIdDataType ="VARCHAR(128)"/>
+ <statements stringIdDataType ="VARCHAR(128)"/>
</statements>
</journaledJDBC>
</persistenceAdapter>
</broker>
-]]></script>
-</div></div><p>For more info on what attributes can be set on the statements element, see the <a shape="rect" class="external-link" 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.</p><h3 id="JDBCSupport-UsingMySQL">Using MySQL</h3><p>If you are using MySQL then you should set the <strong>relaxAutoCommit</strong> flag to be true. e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
- <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
- <property name="url" value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
- <property name="username" value="activemq"/>
- <property name="password" value="activemq"/>
- <property name="poolPreparedStatements" value="true"/>
+</plain-text-body></structured-macro><p>For more info on what attributes can be set on the statements element, see the <a shape="rect" 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.</p><h3>Using MySQL</h3><p>If you are using MySQL then you should set the <strong>relaxAutoCommit</strong> flag to be true. e.g.</p><structured-macro ac:macro-id="150457bb-9c29-40d2-b917-8bca8441f5d7" ac:name="code" ac:schema-version="1"><plain-text-body> <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
+ <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
+ <property name="url" value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
+ <property name="username" value="activemq"/>
+ <property name="password" value="activemq"/>
+ <property name="poolPreparedStatements" value="true"/>
</bean>
-]]></script>
-</div></div><p>To see this in action see the <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">default configuration file</a></p><h3 id="JDBCSupport-ForAMQ3.x">For AMQ 3.x</h3><p>In 3.x you can specify the adapter as follows</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<jdbcPersistence adapterClass="org.activemq.store.jdbc.adapter.ImageBasedJDBCAdaptor">
+</plain-text-body></structured-macro><p>To see this in action see the <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">default configuration file</a></p><h3>For AMQ 3.x</h3><p>In 3.x you can specify the adapter as follows</p><structured-macro ac:macro-id="8a41d054-c2d5-4b21-84f7-c430ace0b29c" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><jdbcPersistence adapterClass="org.activemq.store.jdbc.adapter.ImageBasedJDBCAdaptor">
...
</jdbcPersistence>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/jmeter-performance-tests.xml b/jmeter-performance-tests.xml
index c316dc8..aed4dcf 100644
--- a/jmeter-performance-tests.xml
+++ b/jmeter-performance-tests.xml
@@ -1,17 +1,17 @@
-<div class="wiki-content maincontent"><h3 id="JMeterPerformanceTests-JMeterperformancetest">JMeter performance test</h3>
+<div class="wiki-content maincontent"><h3>JMeter performance test</h3>
-<p>You can use JMeter to test the performance of your ActiveMQ Server. Please refer to the <a shape="rect" class="external-link" href="http://jakarta.apache.org/jmeter/">JMeter site</a> for detailed instructions on using this software.</p>
+<p>You can use JMeter to test the performance of your ActiveMQ Server. Please refer to the <a shape="rect" href="http://jakarta.apache.org/jmeter/">JMeter site</a> for detailed instructions on using this software.</p>
-<h3 id="JMeterPerformanceTests-DownloadingtheJMeterPerformanceTestBinary">Downloading the JMeter Performance Test Binary</h3>
+<h3>Downloading the JMeter Performance Test Binary</h3>
<p>You can download the latest activemq-jmeter-*.zip distribution from the following</p>
-<ul><li><a shape="rect" class="external-link" href="http://people.apache.org/repository/incubator-activemq/distributions/">Apache ActiveMQ versions</a></li><li><a shape="rect" class="external-link" href="http://dist.codehaus.org/activemq/distributions/" rel="nofollow">3.x versions of ActiveMQ</a>.</li></ul>
+<ul><li><a shape="rect" href="http://people.apache.org/repository/incubator-activemq/distributions/">Apache ActiveMQ versions</a></li><li><a shape="rect" href="http://dist.codehaus.org/activemq/distributions/">3.x versions of ActiveMQ</a>.</li></ul>
-<h3 id="JMeterPerformanceTests-BuildingtheJMeterPerformanceTestfromsource">Building the JMeter Performance Test from source</h3>
+<h3>Building the JMeter Performance Test from source</h3>
-<p>1. Check out the latest head version of ActiveMQ from <a shape="rect" href="source.xml">Source</a>. Build from source.</p>
+<p>1. Check out the latest head version of ActiveMQ from <link><page ri:content-title="Source"></page></link>. Build from source.</p>
<p>2. Run maven from the JMeter directory. This will build JMeter into the target directory.</p>
@@ -19,7 +19,7 @@
<p>4. There are sample Test Plans located at \bin\testfiles directory that you could open to test ActiveMQ.</p>
-<h3 id="JMeterPerformanceTests-BuildingaTestPlan">Building a Test Plan</h3>
+<h3>Building a Test Plan</h3>
<p>For a Producer Sampler<br clear="none">
1. Add a Thread Group.<br clear="none">
@@ -33,7 +33,7 @@
3. Highlight the Consumer Sampler then right click to add the consumer listener "View Consumer Results" from the Listener menu.<br clear="none">
4. Go to the Thread Group element and set the Number of Threads, Ramp-Up Period and Loop Count to 1.</p>
-<h3 id="JMeterPerformanceTests-TheJMeterPerformanceTestModuleconsistsof:">The JMeter Performance Test Module consists of:</h3>
+<h3>The JMeter Performance Test Module consists of:</h3>
<p>1. JMeter Producer Sampler</p>
<ul class="alternate"><li>A JMeter Sampler tells JMeter to send requests to the server. Pluggable Samplers allow unlimited testing capabilities.</li></ul>
@@ -57,5 +57,6 @@
<p>4. JMeter Consumer Listener</p>
-<ul class="alternate"><li>The Consumer Listener would provide statistics with the number of messages received and average messages per second.</li></ul></div>
+<ul class="alternate"><li>The Consumer Listener would provide statistics with the number of messages received and average messages per second.</li></ul>
+</div>
diff --git a/jmeter-system-tests.xml b/jmeter-system-tests.xml
index a3c62cc..275ac22 100644
--- a/jmeter-system-tests.xml
+++ b/jmeter-system-tests.xml
@@ -1,10 +1,10 @@
<div class="wiki-content maincontent">
-<h3 id="JMeterSystemTests-JMeterSystemTests">JMeter System Tests</h3>
+<h3>JMeter System Tests</h3>
<p>You can use JMeter to test your ActiveMQ Server. Please refer to the JMeter site for detailed instructions on using this software.<br clear="none">
The Test would check for duplicate messages and the order of messages received.</p>
-<h3 id="JMeterSystemTests-BuildingaTestPlan">Building a Test Plan</h3>
+<h3>Building a Test Plan</h3>
<p>For a Producer System Test Sampler<br clear="none">
1. Add a Thread Group.<br clear="none">
@@ -16,7 +16,7 @@
2. Highlight te Consumer Sampler then right click to add the consumer listener "View Producer System Test Results" from the Listener menu.</p>
-<h3 id="JMeterSystemTests-TheJMeterSystemTestModuleisconsistof:">The JMeter System Test Module is consist of:</h3>
+<h3>The JMeter System Test Module is consist of:</h3>
<p>1. JMeter Producer System Test Sampler</p>
<ul class="alternate"><li>A JMeter Sampler tells JMeter to send requests to the server. Pluggable Samplers allow unlimited testing capabilities.</li></ul>
@@ -46,5 +46,6 @@
<ul class="alternate"><li>Consumer Identifier - Identifies the Consumer that received the message.</li><li>Producer Name - Producer name that send the message.</li><li>Message - The message body received.</li><li>Message Count - The number of messages received.</li></ul>
+
</div>
diff --git a/jms-and-jdbc-operations-in-one-transaction.xml b/jms-and-jdbc-operations-in-one-transaction.xml
index e2a3b3f..80fcaa0 100644
--- a/jms-and-jdbc-operations-in-one-transaction.xml
+++ b/jms-and-jdbc-operations-in-one-transaction.xml
@@ -1,13 +1,12 @@
-<div class="wiki-content maincontent"><h3 id="JMSandJDBCoperationsinonetransaction-JMSandJDBCoperationsinonetransactionwithSpring/Jencks/ActiveMQ">JMS and JDBC operations in one transaction with Spring/Jencks/ActiveMQ</h3>
+<div class="wiki-content maincontent"><h3>JMS and JDBC operations in one transaction with Spring/Jencks/ActiveMQ</h3>
<p>Spring beans:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="131960d2-7879-4564-9ec8-932ad251d58d" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<beans>
<!-- ActiveMQ Broker -->
- <bean id="broker" class="org.apache.activemq.broker.BrokerService" init-method="start" destroy-method="stop">
- <property name="persistent" value="false"/>
- <property name="transportConnectorURIs">
+ <bean id="broker" class="org.apache.activemq.broker.BrokerService" init-method="start" destroy-method="stop">
+ <property name="persistent" value="false"/>
+ <property name="transportConnectorURIs">
<list>
<value>tcp://localhost:5000</value>
</list>
@@ -15,111 +14,109 @@
</bean>
<!-- Geronimo Transaction Manager -->
- <bean id="transactionContextManager" class="org.jencks.factory.TransactionContextManagerFactoryBean"/>
- <bean id="geronimo" class="org.jencks.factory.GeronimoTransactionManagerFactoryBean"/>
- <bean id="geronimoTransactionManager" class="org.springframework.transaction.jta.JtaTransactionManager">
- <property name="userTransaction" ref="geronimo" />
+ <bean id="transactionContextManager" class="org.jencks.factory.TransactionContextManagerFactoryBean"/>
+ <bean id="geronimo" class="org.jencks.factory.GeronimoTransactionManagerFactoryBean"/>
+ <bean id="geronimoTransactionManager" class="org.springframework.transaction.jta.JtaTransactionManager">
+ <property name="userTransaction" ref="geronimo" />
</bean>
<!-- Jencks Connection Manager -->
- <bean id="connectionManager" class="org.jencks.factory.ConnectionManagerFactoryBean">
- <property name="transactionSupport">
- <bean class="org.jencks.factory.XATransactionFactoryBean">
- <property name="useTransactionCaching" value="true"/>
- <property name="useThreadCaching" value="false"/>
+ <bean id="connectionManager" class="org.jencks.factory.ConnectionManagerFactoryBean">
+ <property name="transactionSupport">
+ <bean class="org.jencks.factory.XATransactionFactoryBean">
+ <property name="useTransactionCaching" value="true"/>
+ <property name="useThreadCaching" value="false"/>
</bean>
</property>
- <property name="poolingSupport">
- <bean class="org.jencks.factory.SinglePoolFactoryBean">
- <property name="maxSize" value="2"/>
- <property name="minSize" value="1"/>
- <property name="blockingTimeoutMilliseconds" value="60"/>
- <property name="idleTimeoutMinutes" value="60"/>
- <property name="matchOne" value="true"/>
- <property name="matchAll" value="true"/>
- <property name="selectOneAssumeMatch" value="true"/>
+ <property name="poolingSupport">
+ <bean class="org.jencks.factory.SinglePoolFactoryBean">
+ <property name="maxSize" value="2"/>
+ <property name="minSize" value="1"/>
+ <property name="blockingTimeoutMilliseconds" value="60"/>
+ <property name="idleTimeoutMinutes" value="60"/>
+ <property name="matchOne" value="true"/>
+ <property name="matchAll" value="true"/>
+ <property name="selectOneAssumeMatch" value="true"/>
</bean>
</property>
</bean>
<!-- ActiveMQ Connection -->
- <bean id="jmsResourceAdapter" class="org.apache.activemq.ra.ActiveMQResourceAdapter" depends-on="broker">
- <property name="serverUrl">
+ <bean id="jmsResourceAdapter" class="org.apache.activemq.ra.ActiveMQResourceAdapter" depends-on="broker">
+ <property name="serverUrl">
<value>tcp://localhost:5000</value>
</property>
</bean>
- <bean id="jmsManagedConnectionFactory" class="org.apache.activemq.ra.ActiveMQManagedConnectionFactory">
- <property name="resourceAdapter" ref="jmsResourceAdapter"/>
+ <bean id="jmsManagedConnectionFactory" class="org.apache.activemq.ra.ActiveMQManagedConnectionFactory">
+ <property name="resourceAdapter" ref="jmsResourceAdapter"/>
</bean>
- <bean id="jmsConnectionFactory" class="org.springframework.jca.support.LocalConnectionFactoryBean">
- <property name="managedConnectionFactory" ref="jmsManagedConnectionFactory"/>
- <property name="connectionManager" ref="connectionManager"/>
+ <bean id="jmsConnectionFactory" class="org.springframework.jca.support.LocalConnectionFactoryBean">
+ <property name="managedConnectionFactory" ref="jmsManagedConnectionFactory"/>
+ <property name="connectionManager" ref="connectionManager"/>
</bean>
<!-- Tranql JDBC Connection -->
<!--
- <bean id="tranqlManagedConnectionFactory" class="org.jencks.tranql.XAPoolDataSourceMCF">
- <property name="driverName" value="org.postgresql.Driver"/>
- <property name="url" value="jdbc:postgresql://ats-manager/activemq"/>
- <property name="user" value="activemq"/>
+ <bean id="tranqlManagedConnectionFactory" class="org.jencks.tranql.XAPoolDataSourceMCF">
+ <property name="driverName" value="org.postgresql.Driver"/>
+ <property name="url" value="jdbc:postgresql://ats-manager/activemq"/>
+ <property name="user" value="activemq"/>
</bean>
- <bean id="tranqlDataSource" class="org.springframework.jca.support.LocalConnectionFactoryBean">
- <property name="managedConnectionFactory" ref="tranqlManagedConnectionFactory"/>
- <property name="connectionManager" ref="connectionManager"/>
+ <bean id="tranqlDataSource" class="org.springframework.jca.support.LocalConnectionFactoryBean">
+ <property name="managedConnectionFactory" ref="tranqlManagedConnectionFactory"/>
+ <property name="connectionManager" ref="connectionManager"/>
</bean>
-->
<!-- Enhydra JDBC Connection -->
- <bean id="enhydraDataSource" class="org.enhydra.jdbc.pool.StandardXAPoolDataSource" destroy-method="shutdown">
- <property name="dataSource">
- <bean class="org.enhydra.jdbc.standard.StandardXADataSource" destroy-method="shutdown">
- <property name="transactionManager" ref="geronimo" />
- <property name="driverName" value="org.postgresql.Driver" />
- <property name="url" value="jdbc:postgresql://ats-manager/activemq" />
+ <bean id="enhydraDataSource" class="org.enhydra.jdbc.pool.StandardXAPoolDataSource" destroy-method="shutdown">
+ <property name="dataSource">
+ <bean class="org.enhydra.jdbc.standard.StandardXADataSource" destroy-method="shutdown">
+ <property name="transactionManager" ref="geronimo" />
+ <property name="driverName" value="org.postgresql.Driver" />
+ <property name="url" value="jdbc:postgresql://ats-manager/activemq" />
</bean>
</property>
- <property name="user" value="activemq"/>
+ <property name="user" value="activemq"/>
</bean>
- <bean id="jencksJCAContainer" class="org.jencks.JCAContainer">
- <property name="bootstrapContext">
- <bean class="org.jencks.factory.BootstrapContextFactoryBean">
- <property name="threadPoolSize" value="25"/>
+ <bean id="jencksJCAContainer" class="org.jencks.JCAContainer">
+ <property name="bootstrapContext">
+ <bean class="org.jencks.factory.BootstrapContextFactoryBean">
+ <property name="threadPoolSize" value="25"/>
</bean>
</property>
- <property name="resourceAdapter" ref="jmsResourceAdapter"/>
+ <property name="resourceAdapter" ref="jmsResourceAdapter"/>
</bean>
- <bean id="inboundConnector" class="org.jencks.JCAConnector">
- <property name="jcaContainer" ref="jencksJCAContainer" />
- <property name="activationSpec">
- <bean class="org.apache.activemq.ra.ActiveMQActivationSpec">
- <property name="destination" value="messages.input"/>
- <property name="destinationType" value="javax.jms.Queue"/>
+ <bean id="inboundConnector" class="org.jencks.JCAConnector">
+ <property name="jcaContainer" ref="jencksJCAContainer" />
+ <property name="activationSpec">
+ <bean class="org.apache.activemq.ra.ActiveMQActivationSpec">
+ <property name="destination" value="messages.input"/>
+ <property name="destinationType" value="javax.jms.Queue"/>
</bean>
</property>
- <property name="transactionManager" ref="geronimo"/>
- <property name="ref" value="echoBean"/>
+ <property name="transactionManager" ref="geronimo"/>
+ <property name="ref" value="echoBean"/>
</bean>
- <bean id="echoBean" class="transactions.EchoBean">
- <property name="jdbcTemplate">
- <bean class="org.springframework.jdbc.core.JdbcTemplate">
- <property name="dataSource" ref="enhydraDataSource"/>
+ <bean id="echoBean" class="transactions.EchoBean">
+ <property name="jdbcTemplate">
+ <bean class="org.springframework.jdbc.core.JdbcTemplate">
+ <property name="dataSource" ref="enhydraDataSource"/>
</bean>
</property>
- <property name="jmsTemplate">
- <bean class="org.springframework.jms.core.JmsTemplate">
- <property name="connectionFactory" ref="jmsConnectionFactory"/>
+ <property name="jmsTemplate">
+ <bean class="org.springframework.jms.core.JmsTemplate">
+ <property name="connectionFactory" ref="jmsConnectionFactory"/>
</bean>
</property>
</bean>
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Java code:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="cfe63126-2a2e-4b7b-8771-2ba6ff05ea6a" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
public class EchoBean implements MessageListener {
private Log log = LogFactory.getLog(getClass());
@@ -140,16 +137,15 @@
if (message instanceof TextMessage) {
try {
String messageText = ((TextMessage)message).getText();
- log.debug("execute JMS operation");
- jmsTemplate.convertAndSend("messages.ouptut", messageText);
- log.debug("execute JDBC operation");
- jdbcTemplate.execute("insert into t1 values('"+messageText+"')");
+ log.debug("execute JMS operation");
+ jmsTemplate.convertAndSend("messages.ouptut", messageText);
+ log.debug("execute JDBC operation");
+ jdbcTemplate.execute("insert into t1 values('"+messageText+"')");
} catch (JMSException e) {
e.printStackTrace();
}
}
}
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/jms-bridge-with-local-broker.xml b/jms-bridge-with-local-broker.xml
index 425e740..a3a6b3e 100644
--- a/jms-bridge-with-local-broker.xml
+++ b/jms-bridge-with-local-broker.xml
@@ -1,36 +1,34 @@
-<div class="wiki-content maincontent"><h3 id="JMSBridgeWithLocalBroker-ExampleofaconfigurationthatshowshowtouseaBridgeConnectortomakeaconnectiontothelocalActiveMQbroker.">Example of a configuration that shows how to use a BridgeConnector to make a connection to the local ActiveMQ broker.</h3>
+<div class="wiki-content maincontent"><h3>Example of a configuration that shows how to use a BridgeConnector to make a connection to the local ActiveMQ broker.</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4e5f3026-cbef-453b-ba5f-9746421eaa2d" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<beans>
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
- brokerName="localhost" dataDirectory="${activemq.base}/data">
+ <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
+ brokerName="localhost" dataDirectory="${activemq.base}/data">
<jmsBridgeConnectors>
- <jmsQueueConnector outboundQueueConnectionFactory="#localBroker">
+ <jmsQueueConnector outboundQueueConnectionFactory="#localBroker">
<inboundQueueBridges>
<inboundQueueBridge
- inboundQueueName = "queue.ping"
- localQueueName = "queue.incomingMsgs.ping"
- selector = "JMSType LIKE 'foo%'"/>
+ inboundQueueName = "queue.ping"
+ localQueueName = "queue.incomingMsgs.ping"
+ selector = "JMSType LIKE 'foo%'"/>
</inboundQueueBridges>
<outboundQueueBridges>
<outboundQueueBridge
- localQueueName = "queue.incomingMsgs.ping"
- outboundQueueName = "queue.pong"
- selector = "JMSType LIKE 'foo%'"/>
+ localQueueName = "queue.incomingMsgs.ping"
+ outboundQueueName = "queue.pong"
+ selector = "JMSType LIKE 'foo%'"/>
</outboundQueueBridges>
</jmsQueueConnector>
</jmsBridgeConnectors>
</broker>
<!-- JMS ConnectionFactory to use for local bridging -->
- <bean id="localBroker" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="vm://localhost:61616" />
+ <bean id="localBroker" class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="vm://localhost:61616" />
</bean>
</beans>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/jms-bridge-with-oracle-aq.xml b/jms-bridge-with-oracle-aq.xml
index ff89c94..5aab871 100644
--- a/jms-bridge-with-oracle-aq.xml
+++ b/jms-bridge-with-oracle-aq.xml
@@ -1,117 +1,113 @@
-<div class="wiki-content maincontent"><h3 id="JMSBridgeWithOracleAQ-ExampleofaconfigurationthatshowshowtoconnecttoOracleAQqueuesandtopics.">Example of a configuration that shows how to connect to Oracle AQ queues and topics.</h3>
+<div class="wiki-content maincontent"><h3>Example of a configuration that shows how to connect to Oracle AQ queues and topics.</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4cf21870-0ab2-4f52-a906-fabf122f573a" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<beans>
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
- brokerName="localhost" dataDirectory="${activemq.base}/data" >
+ <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
+ brokerName="localhost" dataDirectory="${activemq.base}/data" >
</broker>
- <camelContext id="camel" xmlns="http://activemq.apache.org/camel/schema/spring">
+ <camelContext id="camel" xmlns="http://activemq.apache.org/camel/schema/spring">
<!-- Dependencies: ojdbc.jar and aqjms.jar must be in the activemq lib directory -->
<!-- this camel route will read incoming messages from Oracle -->
<route>
- <from uri="oracleQueue:queue:ORACLE_QUEUE">
- <to uri="activemq:queue:queue.inboundOracleAQqueue" >
+ <from uri="oracleQueue:queue:ORACLE_QUEUE">
+ <to uri="activemq:queue:queue.inboundOracleAQqueue" >
</route>
<route>
<!-- NOTE: I have had success with a topic using ActiveMQ 5.3, but not 5.1 -->
- <from uri="oracleTopic:topic:ORACLE_TOPIC">
- <to uri="activemq:queue:queue.inboundOracleAQtopic" >
+ <from uri="oracleTopic:topic:ORACLE_TOPIC">
+ <to uri="activemq:queue:queue.inboundOracleAQtopic" >
</route>
<!-- these camel routes will log the messages to the console .... replace them with something more useful!! -->
<route>
- <from uri="activemq:queue:queue.inboundOracleAQqueue" >
- <to uri="log:oracleAQ.inbound.got_a_queue_message?level=ERROR">
+ <from uri="activemq:queue:queue.inboundOracleAQqueue" >
+ <to uri="log:oracleAQ.inbound.got_a_queue_message?level=ERROR">
</route>
<route>
- <from uri="activemq:queue:queue.inboundOracleAQtopic" >
- <to uri="log:oracleAQ.inbound.got_a_topic_message?level=ERROR">
+ <from uri="activemq:queue:queue.inboundOracleAQtopic" >
+ <to uri="log:oracleAQ.inbound.got_a_topic_message?level=ERROR">
</route>
</camelContext>
<!-- without the following bean instantiation, we will get an oracle.jms.AQjmsException with each and every received message -->
- <bean id="requiredBeanForOracleAq" class="org.apache.activemq.ActiveMQConnectionFactory" />
+ <bean id="requiredBeanForOracleAq" class="org.apache.activemq.ActiveMQConnectionFactory" />
- <bean id="connectionFactoryOracleAQQueue" class="oracle.jms.AQjmsFactory" factory-method="getQueueConnectionFactory">
- <constructor-arg index="0">
+ <bean id="connectionFactoryOracleAQQueue" class="oracle.jms.AQjmsFactory" factory-method="getQueueConnectionFactory">
+ <constructor-arg index="0">
<value>jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST ....... (SERVICE_NAME = myDbService)))</value>
</constructor-arg>
- <constructor-arg index="1" type="java.util.Properties">
+ <constructor-arg index="1" type="java.util.Properties">
<value></value>
</constructor-arg>
</bean>
- <bean id="connectionFactoryOracleAQTopic" class="oracle.jms.AQjmsFactory"
- factory-method="getQueueConnectionFactory">
- <constructor-arg index="0">
+ <bean id="connectionFactoryOracleAQTopic" class="oracle.jms.AQjmsFactory"
+ factory-method="getQueueConnectionFactory">
+ <constructor-arg index="0">
<value>jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST ....... (SERVICE_NAME = myDbService)))</value>
</constructor-arg>
- <constructor-arg index="1" type="java.util.Properties">
+ <constructor-arg index="1" type="java.util.Properties">
<value></value>
</constructor-arg>
</bean>
- <bean id="oracleQueueCredentials" class="org.springframework.jms.connection.UserCredentialsConnectionFactoryAdapter">
- <property name="targetConnectionFactory">
- <ref bean="connectionFactoryOracleAQQueue">
+ <bean id="oracleQueueCredentials" class="org.springframework.jms.connection.UserCredentialsConnectionFactoryAdapter">
+ <property name="targetConnectionFactory">
+ <ref bean="connectionFactoryOracleAQQueue">
</property>
- <property name="username">
+ <property name="username">
<value>foo</value>
</property>
- <property name="password">
+ <property name="password">
<value>bar</value>
</property>
</bean>
- <bean id="oracleTopicCredentials" class="org.springframework.jms.connection.UserCredentialsConnectionFactoryAdapter">
- <property name="targetConnectionFactory">
- <ref bean="connectionFactoryOracleAQTopic">
+ <bean id="oracleTopicCredentials" class="org.springframework.jms.connection.UserCredentialsConnectionFactoryAdapter">
+ <property name="targetConnectionFactory">
+ <ref bean="connectionFactoryOracleAQTopic">
</property>
- <property name="username">
+ <property name="username">
<value>foo</value>
</property>
- <property name="password">
+ <property name="password">
<value>bar</value>
</property>
</bean>
- <bean id="oracleQueue" class="org.apache.camel.component.jms.JmsComponent">
- <property name="connectionFactory" ref="oracleQueueCredentials">
+ <bean id="oracleQueue" class="org.apache.camel.component.jms.JmsComponent">
+ <property name="connectionFactory" ref="oracleQueueCredentials">
</bean>
- <bean id="oracleTopic" class="org.apache.camel.component.jms.JmsComponent">
- <property name="connectionFactory" ref="oracleTopicCredentials">
+ <bean id="oracleTopic" class="org.apache.camel.component.jms.JmsComponent">
+ <property name="connectionFactory" ref="oracleTopicCredentials">
</bean>
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>If you run in an OSGi environment such as <a shape="rect" class="external-link" href="http://servicemix.apache.org">ServiceMix 4</a> then take a look at <a shape="rect" class="external-link" href="http://servicemix.396122.n5.nabble.com/ServiceMix-4-2-Camel-OracleAQ-td421214.html#a421214" rel="nofollow">this discussion</a> how to install the OracleAQ Client in the OSGi container.</p>
+<p>If you run in an OSGi environment such as <a shape="rect" href="http://servicemix.apache.org">ServiceMix 4</a> then take a look at <a shape="rect" href="http://servicemix.396122.n5.nabble.com/ServiceMix-4-2-Camel-OracleAQ-td421214.html#a421214">this discussion</a> how to install the OracleAQ Client in the OSGi container.</p>
-<h4 id="JMSBridgeWithOracleAQ-OracleSQLcode">Oracle SQL code</h4>
+<h4>Oracle SQL code</h4>
<p>You may need to setup OracleAQ, and here is a sample code</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="efdb1a06-1164-41a6-86ee-ce8b6fc792b7" ac:name="code" ac:schema-version="1"><plain-text-body>
BEGIN
- DBMS_AQADM.CREATE_QUEUE_TABLE( queue_table => 'queue_message_table', queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE');
+ DBMS_AQADM.CREATE_QUEUE_TABLE( queue_table => 'queue_message_table', queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE');
END;
BEGIN
- DBMS_AQADM.CREATE_QUEUE( queue_name => 'ORACLE_QUEUE', queue_table => 'queue_message_table');
+ DBMS_AQADM.CREATE_QUEUE( queue_name => 'ORACLE_QUEUE', queue_table => 'queue_message_table');
END;
BEGIN
- DBMS_AQADM.START_QUEUE(queue_name => 'ORACLE_QUEUE');
+ DBMS_AQADM.START_QUEUE(queue_name => 'ORACLE_QUEUE');
END;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>You can also find more information about OracleAQ and using JMS at: <a shape="rect" class="external-link" href="http://docs.oracle.com/cd/B13789_01/server.101/b10785/jm_exmpl.htm" rel="nofollow">http://docs.oracle.com/cd/B13789_01/server.101/b10785/jm_exmpl.htm</a></p></div>
+<p>You can also find more information about OracleAQ and using JMS at: <a shape="rect" href="http://docs.oracle.com/cd/B13789_01/server.101/b10785/jm_exmpl.htm">http://docs.oracle.com/cd/B13789_01/server.101/b10785/jm_exmpl.htm</a></p></div>
diff --git a/jms-bridge-with-remote-broker.xml b/jms-bridge-with-remote-broker.xml
index 8294efd..7551833 100644
--- a/jms-bridge-with-remote-broker.xml
+++ b/jms-bridge-with-remote-broker.xml
@@ -1,36 +1,34 @@
-<div class="wiki-content maincontent"><h3 id="JMSBridgeWithRemoteBroker-ExampleofaconfigurationthatshowshowtouseaBridgeConnectortomakeaconnectiontoaremoteActiveMQbroker.">Example of a configuration that shows how to use a BridgeConnector to make a connection to a remote ActiveMQ broker.</h3>
+<div class="wiki-content maincontent"><h3>Example of a configuration that shows how to use a BridgeConnector to make a connection to a remote ActiveMQ broker.</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="841c501d-dd07-4c45-9354-bdbcb93ff0cc" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<beans>
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
- brokerName="localhost" dataDirectory="${activemq.base}/data">
+ <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
+ brokerName="localhost" dataDirectory="${activemq.base}/data">
<jmsBridgeConnectors>
- <jmsQueueConnector outboundQueueConnectionFactory="#remoteBroker">
+ <jmsQueueConnector outboundQueueConnectionFactory="#remoteBroker">
<inboundQueueBridges>
<inboundQueueBridge
- inboundQueueName = "queue.ping"
- localQueueName = "queue.incomingMsgs.ping"
- selector = "JMSType LIKE 'foo%'"/>
+ inboundQueueName = "queue.ping"
+ localQueueName = "queue.incomingMsgs.ping"
+ selector = "JMSType LIKE 'foo%'"/>
</inboundQueueBridges>
<outboundQueueBridges>
<outboundQueueBridge
- outboundQueueName = "queue.pong"
- localQueueName = "queue.incomingMsgs.ping"
- selector = "JMSType LIKE 'foo%'"/>
+ outboundQueueName = "queue.pong"
+ localQueueName = "queue.incomingMsgs.ping"
+ selector = "JMSType LIKE 'foo%'"/>
</outboundQueueBridges>
</jmsQueueConnector>
</jmsBridgeConnectors>
</broker>
<!-- JMS ConnectionFactory to use for remote bridging -->
- <bean id="remoteBroker" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="failover:(tcp://remote_activemq:61616)" />
+ <bean id="remoteBroker" class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="failover:(tcp://remote_activemq:61616)" />
</bean>
</beans>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/jms-bridge-with-remote-tibco-broker.xml b/jms-bridge-with-remote-tibco-broker.xml
index 726a494..0cd5a71 100644
--- a/jms-bridge-with-remote-tibco-broker.xml
+++ b/jms-bridge-with-remote-tibco-broker.xml
@@ -1,40 +1,38 @@
-<div class="wiki-content maincontent"><h3 id="JMSBridgeWithRemoteTIBCOBroker-ExampleofaconfigurationthatshowshowtouseaBridgeConnectortomakeaconnectiontoaremoteTIBCOEMSbroker.">Example of a configuration that shows how to use a BridgeConnector to make a connection to a remote TIBCO EMS broker.</h3>
+<div class="wiki-content maincontent"><h3>Example of a configuration that shows how to use a BridgeConnector to make a connection to a remote TIBCO EMS broker.</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="77975890-00a2-41e6-9b62-df2e59352b0e" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<beans>
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
- brokerName="localhost" dataDirectory="${activemq.base}/data">
+ <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
+ brokerName="localhost" dataDirectory="${activemq.base}/data">
<!-- Dependencies: tibjms.jar must be in the activemq lib directory -->
<!-- bridging definitions for traffic to/from remote activemq instance -->
<jmsBridgeConnectors>
- <jmsQueueConnector outboundQueueConnectionFactory="#tibco">
+ <jmsQueueConnector outboundQueueConnectionFactory="#tibco">
<inboundQueueBridges>
<inboundQueueBridge
- inboundQueueName = "queue.ping"
- localQueueName = "queue.incomingMsgs.ping"
- selector = "JMSType LIKE 'foo%'"/>
+ inboundQueueName = "queue.ping"
+ localQueueName = "queue.incomingMsgs.ping"
+ selector = "JMSType LIKE 'foo%'"/>
</inboundQueueBridges>
<outboundQueueBridges>
<outboundQueueBridge
- outboundQueueName = "queue.pong"
- localQueueName = "queue.incomingMsgs.ping"
- selector = "JMSType LIKE 'foo%'"/>
+ outboundQueueName = "queue.pong"
+ localQueueName = "queue.incomingMsgs.ping"
+ selector = "JMSType LIKE 'foo%'"/>
</outboundQueueBridges>
</jmsQueueConnector>
</jmsBridgeConnectors>
</broker>
<!-- JMS ConnectionFactory to use for local bridging -->
- <bean id="tibco" class="com.tibco.tibjms.TibjmsQueueConnectionFactory">
- <property name="serverUrl" value="tcp://remote_tibco:7222" />
+ <bean id="tibco" class="com.tibco.tibjms.TibjmsQueueConnectionFactory">
+ <property name="serverUrl" value="tcp://remote_tibco:7222" />
</bean>
</beans>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/jms-streams.xml b/jms-streams.xml
index e75c722..47dd537 100644
--- a/jms-streams.xml
+++ b/jms-streams.xml
@@ -1,60 +1,57 @@
<div class="wiki-content maincontent"><p><strong>deprecated</strong></p>
-<div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>This feature is deprecated, and end users is encouraged to <strong>not</strong> use it. This feature will be removed in a later ActiveMQ release.</p></div></div>
+<structured-macro ac:macro-id="88cf66c6-a3ba-4c16-afbf-0ef5c8fed79a" ac:name="warning" ac:schema-version="1"><rich-text-body>
+<p>This feature is deprecated, and end users is encouraged to <strong>not</strong> use it. This feature will be removed in a later ActiveMQ release.</p></rich-text-body></structured-macro>
<p>Sometimes you need to send truly massive files (many Gb) around the network in a reliable manner. The JMS API expects JMS clients to be able to keep a message in memory at one time, so sending > 1Gb messages around ends up using way too much RAM on the client side.</p>
-<p>To solve this problem ActiveMQ supports regular <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/api/java/io/InputStream.html" rel="nofollow">InputStream</a> and <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/api/java/io/OutputStream.html" rel="nofollow">OutputStream</a> abstractions which work with regular JMS producers and consumers.</p>
+<p>To solve this problem ActiveMQ supports regular <a shape="rect" href="http://java.sun.com/j2se/1.4.2/docs/api/java/io/InputStream.html">InputStream</a> and <a shape="rect" href="http://java.sun.com/j2se/1.4.2/docs/api/java/io/OutputStream.html">OutputStream</a> abstractions which work with regular JMS producers and consumers.</p>
-<p>This allows you to use the familar streams from Java to send or receive messages of any size at all (providing your file system can handle them <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"> while keeping a low memory overhead.</p>
+<p>This allows you to use the familar streams from Java to send or receive messages of any size at all (providing your file system can handle them <emoticon ac:name="smile"></emoticon> while keeping a low memory overhead.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">For Users of 4.2</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>If you are using 4.2 onwards of ActiveMQ we highly recommend you try out <a shape="rect" href="blob-messages.xml">Blob Messages</a> which offers a more flexible mechanism for dealing wtih massive files and fully supports out-of-band transfer using HTTP/FTP as well as allowing external resources to be sent around the JMS network.</p></div></div>
+<structured-macro ac:macro-id="3849c84e-3152-47d0-8075-de533a4015af" ac:name="info" ac:schema-version="1"><parameter ac:name="title">For Users of 4.2</parameter><rich-text-body>
+<p>If you are using 4.2 onwards of ActiveMQ we highly recommend you try out <link><page ri:content-title="Blob Messages"></page></link> which offers a more flexible mechanism for dealing wtih massive files and fully supports out-of-band transfer using HTTP/FTP as well as allowing external resources to be sent around the JMS network.</p></rich-text-body></structured-macro>
-<h3 id="JMSStreams-UsingJMSStreams">Using JMS Streams</h3>
+<h3>Using JMS Streams</h3>
-<p>To use the streams just create an input or output stream depending on if you are reading or writing using the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html#createInputStream(javax.jms.Destination)">connection.createInputStream()</a> or<br clear="none">
-<a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html#createOutputStream(javax.jms.Destination)">connection.createOutputStream()</a> methods.</p>
+<p>To use the streams just create an input or output stream depending on if you are reading or writing using the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html#createInputStream(javax.jms.Destination)">connection.createInputStream()</a> or<br clear="none">
+<a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html#createOutputStream(javax.jms.Destination)">connection.createOutputStream()</a> methods.</p>
<p>e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0a3d4912-0a8c-4072-8031-2972c28d04ab" ac:name="code" ac:schema-version="1"><plain-text-body>
ActiveMQConnection connection = ...;
-Destination destination = new ActiveMQQueue("FOO.BAR");
+Destination destination = new ActiveMQQueue("FOO.BAR");
OutputStream out = connection.createOutputStream(destination);
// write the file to out
out.close();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Or to consume a large message</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e351d85f-34c6-4d59-b017-d9489e64f04f" ac:name="code" ac:schema-version="1"><plain-text-body>
ActiveMQConnection connection = ...;
-Destination destination = new ActiveMQQueue("FOO.BAR");
+Destination destination = new ActiveMQQueue("FOO.BAR");
InputStream in = connection.createInputStream(destination)
// read the stream...
in.close();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>There are overloaded createInputStream/createOutputStream methods which support additional paramateres to be passed.</p>
<p>For further reference see the javadoc.</p>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQInputStream.html">ActiveMQInputStream </a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQOutputStream.html">ActiveMQOutputStream </a></li></ul>
+<ul><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQInputStream.html">ActiveMQInputStream </a></li><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQOutputStream.html">ActiveMQOutputStream </a></li></ul>
<p><em>Note:</em><br clear="none">
The counterpart classes in AMQ 3.x are :</p>
-<ul><li>JMSInputStream</li><li>JMSOutputStream</li></ul></div>
+<ul><li>JMSInputStream</li><li>JMSOutputStream</li></ul>
+</div>
diff --git a/jms-to-jms-bridge.xml b/jms-to-jms-bridge.xml
index 3bd7a46..dc046cb 100644
--- a/jms-to-jms-bridge.xml
+++ b/jms-to-jms-bridge.xml
@@ -1,104 +1,97 @@
-<div class="wiki-content maincontent"><h3 id="JMStoJMSBridge-Introduction">Introduction</h3><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning, try Camel first!</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Note that we recommend you look at using <a shape="rect" class="external-link" href="http://camel.apache.org/">Apache Camel</a> for bridging ActiveMQ to or from any message broker (or indeed <a shape="rect" class="external-link" href="http://camel.apache.org/components.html">any other technology, protocol or middleware</a>) as its much easier to:</p><ul><li>keep things flexible; its very easy to map different queue/topic to one or more queues or topics on the other provider</li><li>perform content based routing, filtering and other <a shape="rect" class="external-link" href="http://camel.apache.org/enterprise-integration-patterns.html">Enterprise Integration Patterns</a></li><li>allows you to work with <a shape="rect" class="external-link" href="http://camel.apache.org/components.html">any technology, protocol or middleware</a>, not just JMS providers</li></ul><p>e.g. in your Spring XML file just add:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<camelContext xmlns="http://camel.apache.org/schema/spring">
+<div class="wiki-content maincontent"><h3>Introduction</h3><structured-macro ac:macro-id="8f3d34a6-d2b2-4ae6-9592-7af58f76c70a" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning, try Camel first!</parameter><rich-text-body><p>Note that we recommend you look at using <a shape="rect" href="http://camel.apache.org/">Apache Camel</a> for bridging ActiveMQ to or from any message broker (or indeed <a shape="rect" href="http://camel.apache.org/components.html">any other technology, protocol or middleware</a>) as its much easier to:</p><ul><li>keep things flexible; its very easy to map different queue/topic to one or more queues or topics on the other provider</li><li>perform content based routing, filtering and other <a shape="rect" href="http://camel.apache.org/enterprise-integration-patterns.html">Enterprise Integration Patterns</a></li><li>allows you to work with <a shape="rect" href="http://camel.apache.org/components.html">any technology, protocol or middleware</a>, not just JMS providers</li></ul><p>e.g. in your Spring XML file just add:</p><structured-macro ac:macro-id="1c8e34e4-e50f-4c2e-8f5f-b474b46eb8ce" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><camelContext xmlns="http://camel.apache.org/schema/spring">
<route>
- <from uri="mqseries:Foo.Bar"/>
- <to uri="activemq:Cheese"/>
+ <from uri="mqseries:Foo.Bar"/>
+ <to uri="activemq:Cheese"/>
</route>
</camelContext>
-]]></script>
-</div></div></div></div><p>ActiveMQ provides bridging functionality to other JMS providers that implement the JMS 1.0.2 and above specification.<br clear="none"> A JMS bridge can be co-located with an ActiveMQ broker or run remotely.<br clear="none"> In order to support JMS 1.0.2 there is seperation between Queues and Topics.</p><p>temporary destinations and replyTo destinations in the inbound message exchanges are automatically handled, enabling an ActiveMQ service to handle a foreign JMS TopicRequestor or QueueResquestor exchanges.</p><h3 id="JMStoJMSBridge-properties">properties</h3><p><strong>JMS Bridge Topic Connector</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property 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>localTopicConnection</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used to connect to ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>localTopicConnectionFactory</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>used to initialize the ActiveMQ JMS Connection if localTopicConnection is not set</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>localClientId</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set the id of the local connection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundClientId</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set the id of the outbound connection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>jndiLocalTemplate</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Spring default template</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>used for locating the Connection Factory for the ActiveMQ Connection if the localTopicConnection or localTopicConnectionFactory is not set</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundTopicConnection</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used to connect to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundTopicConnectionFactory</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>used to initialize the foreign JMS Connection if outboundTopicConnection is not set</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>jndiOutboundTemplate</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Spring default template</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>used for locating the Connection Factory for the ActiveMQ Connection if the localTopicConnection or localTopicConnectionFactory is not set</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>localUsername</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for authentication to the ActiveMQ JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>localPassword</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for authentication to the ActiveMQ JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundUsername</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for authentication to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundPassword</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for authentication to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>inboundMessageConvertor</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for converting foreign JMS Messages to a format for ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundMessageConvertor</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for converting ActiveMQ messages to a format for the foriegn JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>inboundTopicBridges</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>an array of InboundTopicBridge instances - used for defining inbound (subscribe to) traffic from the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundTopicBridges</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>an array of OutboundTopicBridge instances - used for defining destinations that will be published to the foreign JMS provider</p></td></tr></tbody></table></div><p><strong>JMS Bridge Queue Connector</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property 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>localQueueConnection</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used to connect to ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>localQueueConnectionFactory</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>used to initialize the ActiveMQ JMS Connection if localQueueConnection is not set</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>localClientId</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set the id of the local connection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundClientId</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>set the id of the outbound connection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>jndiLocalTemplate</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Spring default template</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>used for locating the Connection Factory for the ActiveMQ Connection if the localQueueConnection or localQueueConnectionFactory is not set</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundQueueConnection</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used to connect to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundQueueConnectionFactory</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>used to initialize the foreign JMS Connection if localQueueConnection is not set</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>jndiOutboundTemplate</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Spring default template</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>used for locating the Connection Factory for the ActiveMQ Connection if the localQueueConnection or localQueueConnectionFactory is not set</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>localUsername</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for authentication to the ActiveMQ JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>localPassword</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for authentication to the ActiveMQ JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundUsername</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for authentication to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundPassword</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for authentication to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>inboundMessageConvertor</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for converting foreign JMS Messages to a format for ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundMessageConvertor</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will be used for converting ActiveMQ messages to a format for the foriegn JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>inboundQueueBridges</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>an array of InboundQueueBridge instances - used for defining inbound (subscribe to) traffic from the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundQueueBridges</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>an array of OutboundQueueBridge instances - used for defining destinations that will be forwarded to the foreign JMS provider</p></td></tr></tbody></table></div><div class="sectionColumnWrapper"><div class="sectionMacroWithBorder"><div class="sectionMacroRow"><div class="columnMacro" style="width:50%;min-width:50%;max-width:50%;"><h4 id="JMStoJMSBridge-TopicBridges">Topic Bridges</h4><p><strong>InboundTopicBridge</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property 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>localTopicName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the name of the local ActiveMQ Queue</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>inboundTopicName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the foreign topic name to subscribe to</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>selector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>selector to use - if any</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if set will create a durable consumer</p></td></tr></tbody></table></div><p><strong>OutboundTopicBridge</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property 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>localTopicName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the name of the local ActiveMQ Queue</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundTopicName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the foreign topic name to publish to</p></td></tr></tbody></table></div></div><div class="columnMacro" style="width:50%;min-width:50%;max-width:50%;"><h4 id="JMStoJMSBridge-QueueBridges">Queue Bridges</h4><p><strong>InboundQueueBridge</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property 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>localQueueName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the name of the local ActiveMQ Queue</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>inboundQueueName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the foreign queue name to receive from</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>selector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>selector to use - if any</p></td></tr></tbody></table></div><p><br clear="none" class="atl-forced-newline"> <strong>OutboundQueueBridge</strong></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property 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>localQueueName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the name of the local ActiveMQ Queue</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>outboundQueueName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the foreign queue name to send to</p></td></tr></tbody></table></div></div></div></div></div><h3 id="JMStoJMSBridge-ExampleXBeanConfiguration">Example XBean Configuration</h3><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/network/jms/queue-xbean.xml">example config file</a> shows how to use the regular <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> to configure a JMS to JMS bridge.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <broker xmlns="http://activemq.apache.org/schema/core" id="localbroker"
- brokerName="localBroker" persistent="false">
+</plain-text-body></structured-macro></rich-text-body></structured-macro><p>ActiveMQ provides bridging functionality to other JMS providers that implement the JMS 1.0.2 and above specification.<br clear="none"> A JMS bridge can be co-located with an ActiveMQ broker or run remotely.<br clear="none"> In order to support JMS 1.0.2 there is seperation between Queues and Topics.</p><p>temporary destinations and replyTo destinations in the inbound message exchanges are automatically handled, enabling an ActiveMQ service to handle a foreign JMS TopicRequestor or QueueResquestor exchanges.</p><h3>properties</h3><p><strong>JMS Bridge Topic Connector</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>localTopicConnection</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used to connect to ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>localTopicConnectionFactory</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>used to initialize the ActiveMQ JMS Connection if localTopicConnection is not set</p></td></tr><tr><td colspan="1" rowspan="1"><p>localClientId</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>set the id of the local connection</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundClientId</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>set the id of the outbound connection</p></td></tr><tr><td colspan="1" rowspan="1"><p>jndiLocalTemplate</p></td><td colspan="1" rowspan="1"><p>Spring default template</p></td><td colspan="1" rowspan="1"><p>used for locating the Connection Factory for the ActiveMQ Connection if the localTopicConnection or localTopicConnectionFactory is not set</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundTopicConnection</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used to connect to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundTopicConnectionFactory</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>used to initialize the foreign JMS Connection if outboundTopicConnection is not set</p></td></tr><tr><td colspan="1" rowspan="1"><p>jndiOutboundTemplate</p></td><td colspan="1" rowspan="1"><p>Spring default template</p></td><td colspan="1" rowspan="1"><p>used for locating the Connection Factory for the ActiveMQ Connection if the localTopicConnection or localTopicConnectionFactory is not set</p></td></tr><tr><td colspan="1" rowspan="1"><p>localUsername</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for authentication to the ActiveMQ JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>localPassword</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for authentication to the ActiveMQ JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundUsername</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for authentication to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundPassword</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for authentication to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>inboundMessageConvertor</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for converting foreign JMS Messages to a format for ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundMessageConvertor</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for converting ActiveMQ messages to a format for the foriegn JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>inboundTopicBridges</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>an array of InboundTopicBridge instances - used for defining inbound (subscribe to) traffic from the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundTopicBridges</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>an array of OutboundTopicBridge instances - used for defining destinations that will be published to the foreign JMS provider</p></td></tr></tbody></table><p><strong>JMS Bridge Queue Connector</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>localQueueConnection</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used to connect to ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>localQueueConnectionFactory</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>used to initialize the ActiveMQ JMS Connection if localQueueConnection is not set</p></td></tr><tr><td colspan="1" rowspan="1"><p>localClientId</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>set the id of the local connection</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundClientId</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>set the id of the outbound connection</p></td></tr><tr><td colspan="1" rowspan="1"><p>jndiLocalTemplate</p></td><td colspan="1" rowspan="1"><p>Spring default template</p></td><td colspan="1" rowspan="1"><p>used for locating the Connection Factory for the ActiveMQ Connection if the localQueueConnection or localQueueConnectionFactory is not set</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundQueueConnection</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used to connect to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundQueueConnectionFactory</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>used to initialize the foreign JMS Connection if localQueueConnection is not set</p></td></tr><tr><td colspan="1" rowspan="1"><p>jndiOutboundTemplate</p></td><td colspan="1" rowspan="1"><p>Spring default template</p></td><td colspan="1" rowspan="1"><p>used for locating the Connection Factory for the ActiveMQ Connection if the localQueueConnection or localQueueConnectionFactory is not set</p></td></tr><tr><td colspan="1" rowspan="1"><p>localUsername</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for authentication to the ActiveMQ JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>localPassword</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for authentication to the ActiveMQ JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundUsername</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for authentication to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundPassword</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for authentication to the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>inboundMessageConvertor</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for converting foreign JMS Messages to a format for ActiveMQ</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundMessageConvertor</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will be used for converting ActiveMQ messages to a format for the foriegn JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>inboundQueueBridges</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>an array of InboundQueueBridge instances - used for defining inbound (subscribe to) traffic from the foreign JMS provider</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundQueueBridges</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>an array of OutboundQueueBridge instances - used for defining destinations that will be forwarded to the foreign JMS provider</p></td></tr></tbody></table><structured-macro ac:macro-id="fc5033ca-749d-4ac3-be79-ed9adc8602dc" ac:name="section" ac:schema-version="1"><parameter ac:name="border">true</parameter><rich-text-body><structured-macro ac:macro-id="f6b52566-a480-48f4-9ef9-a166aa599cc0" ac:name="column" ac:schema-version="1"><parameter ac:name="width">50%</parameter><rich-text-body><h4>Topic Bridges</h4><p><strong>InboundTopicBridge</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>localTopicName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>the name of the local ActiveMQ Queue</p></td></tr><tr><td colspan="1" rowspan="1"><p>inboundTopicName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>the foreign topic name to subscribe to</p></td></tr><tr><td colspan="1" rowspan="1"><p>selector</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>selector to use - if any</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumerName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>if set will create a durable consumer</p></td></tr></tbody></table><p><strong>OutboundTopicBridge</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>localTopicName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>the name of the local ActiveMQ Queue</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundTopicName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>the foreign topic name to publish to</p></td></tr></tbody></table></rich-text-body></structured-macro><structured-macro ac:macro-id="d88262df-141e-4074-b048-13eeadb6cadf" ac:name="column" ac:schema-version="1"><parameter ac:name="width">50%</parameter><rich-text-body><h4>Queue Bridges</h4><p><strong>InboundQueueBridge</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>localQueueName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>the name of the local ActiveMQ Queue</p></td></tr><tr><td colspan="1" rowspan="1"><p>inboundQueueName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>the foreign queue name to receive from</p></td></tr><tr><td colspan="1" rowspan="1"><p>selector</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>selector to use - if any</p></td></tr></tbody></table><p><br clear="none" class="atl-forced-newline"> <strong>OutboundQueueBridge</strong></p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>localQueueName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>the name of the local ActiveMQ Queue</p></td></tr><tr><td colspan="1" rowspan="1"><p>outboundQueueName</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>the foreign queue name to send to</p></td></tr></tbody></table></rich-text-body></structured-macro></rich-text-body></structured-macro><h3>Example XBean Configuration</h3><p>The following <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/network/jms/queue-xbean.xml">example config file</a> shows how to use the regular <link><page ri:content-title="Xml Configuration"></page></link> to configure a JMS to JMS bridge.</p><structured-macro ac:macro-id="e7254210-9de0-4ff4-9b7c-e66ccb0f342d" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <broker xmlns="http://activemq.apache.org/schema/core" id="localbroker"
+ brokerName="localBroker" persistent="false">
<jmsBridgeConnectors>
<jmsQueueConnector
- outboundQueueConnectionFactory="#remoteFactory">
+ outboundQueueConnectionFactory="#remoteFactory">
<inboundQueueBridges>
<inboundQueueBridge
- inboundQueueName="org.apache.activemq.network.jms.QueueBridgeXBeanTest" />
+ inboundQueueName="org.apache.activemq.network.jms.QueueBridgeXBeanTest" />
</inboundQueueBridges>
</jmsQueueConnector>
</jmsBridgeConnectors>
<transportConnectors>
- <transportConnector uri="tcp://localhost:61234" />
+ <transportConnector uri="tcp://localhost:61234" />
</transportConnectors>
</broker>
<!-- JMS ConnectionFactory to use remote -->
- <bean id="remoteFactory"
- class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61666" />
+ <bean id="remoteFactory"
+ class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="tcp://localhost:61666" />
</bean>
-]]></script>
-</div></div><h3 id="JMStoJMSBridge-ExamplepureSpringConfiguration">Example pure Spring Configuration</h3><p>The following example shows how to use raw Spring XML to wire together a broker - bridging to a Foreign JMS provider</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<!-- local broker with embedded Jms to Jms bridge (ok - it's contrived) -->
- <bean id="localbroker" class="org.apache.activemq.broker.BrokerService"
- init-method="start">
- <property name="brokerName" value = "localBroker"/>
- <property name="persistent" value = "false"/>
- <property name="transportConnectorURIs">
+</plain-text-body></structured-macro><h3>Example pure Spring Configuration</h3><p>The following example shows how to use raw Spring XML to wire together a broker - bridging to a Foreign JMS provider</p><structured-macro ac:macro-id="efa48821-6721-4f88-980e-9a707b669bec" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><!-- local broker with embedded Jms to Jms bridge (ok - it's contrived) -->
+ <bean id="localbroker" class="org.apache.activemq.broker.BrokerService"
+ init-method="start">
+ <property name="brokerName" value = "localBroker"/>
+ <property name="persistent" value = "false"/>
+ <property name="transportConnectorURIs">
<list>
<value>tcp://localhost:61234</value>
</list>
</property>
- <property name="jmsBridgeConnectors">
+ <property name="jmsBridgeConnectors">
<list>
- <ref bean="jmsConnector"/>
+ <ref bean="jmsConnector"/>
</list>
</property>
</bean>
<!-- JMS ConnectionFactory to use local broker (the one with the bridge) -->
- <bean id="localFactory"
- class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61234" />
+ <bean id="localFactory"
+ class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="tcp://localhost:61234" />
</bean>
<!--JmsTopicConnector - the Jms bridge -->
- <bean id="jmsConnector"
- class="org.apache.activemq.network.jms.JmsTopicConnector">
- <property name = "outboundTopicConnectionFactory" ref = "remoteFactory"/>
+ <bean id="jmsConnector"
+ class="org.apache.activemq.network.jms.JmsTopicConnector">
+ <property name = "outboundTopicConnectionFactory" ref = "remoteFactory"/>
- <property name = "inboundTopicBridges">
+ <property name = "inboundTopicBridges">
<list>
- <ref bean="InboundTopicBridge" />
+ <ref bean="InboundTopicBridge" />
</list>
</property>
</bean>
- <bean id ="InboundTopicBridge" class="org.apache.activemq.network.jms.InboundTopicBridge">
- <property name = "inboundTopicName" value = "org.apache.activemq.network.jms.TopicBridgeSpringTest"/>
+ <bean id ="InboundTopicBridge" class="org.apache.activemq.network.jms.InboundTopicBridge">
+ <property name = "inboundTopicName" value = "org.apache.activemq.network.jms.TopicBridgeSpringTest"/>
</bean>
</beans>
-]]></script>
-</div></div><h3 id="JMStoJMSBridge-ExampleXBeanConfigurationtoBridgeActiveMQtoProviderWithNoURLSetter">Example XBean Configuration to Bridge ActiveMQ to Provider With No URL Setter</h3><p>Some JMS providers, WebLogic for instance, do not expose a setter for connection properties like host and port (setBrokerUrl) on their ConnectionFactory object. In this case you need to set outboundQueueConnectionFactoryName and jndiOutboundTemplate in your activemq.xml config file.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<!-- START SNIPPET: example -->
+</plain-text-body></structured-macro><h3>Example XBean Configuration to Bridge ActiveMQ to Provider With No URL Setter</h3><p>Some JMS providers, WebLogic for instance, do not expose a setter for connection properties like host and port (setBrokerUrl) on their ConnectionFactory object. In this case you need to set outboundQueueConnectionFactoryName and jndiOutboundTemplate in your activemq.xml config file.</p><structured-macro ac:macro-id="9ab28010-3e37-4a07-9f51-a419b333462f" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><!-- START SNIPPET: example -->
<beans>
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" xmlns="http://activemq.org/config/1.0">
+ <broker useJmx="true" xmlns="http://activemq.org/config/1.0">
<persistenceAdapter>
- <journaledJDBC journalLogFiles="5" dataDirectory="${activemq.home}/activemq-data"/>
+ <journaledJDBC journalLogFiles="5" dataDirectory="${activemq.home}/activemq-data"/>
</persistenceAdapter>
<transportConnectors>
- <transportConnector name="default" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
- <transportConnector name="stomp" uri="stomp://localhost:61613"/>
+ <transportConnector name="default" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
+ <transportConnector name="stomp" uri="stomp://localhost:61613"/>
</transportConnectors>
<networkConnectors>
- <networkConnector name="default" uri="multicast://default"/>
+ <networkConnector name="default" uri="multicast://default"/>
</networkConnectors>
<jmsBridgeConnectors>
- <jmsQueueConnector name="JreportRequestBridge-Inbound"
- jndiOutboundTemplate="#remoteJndi"
- outboundQueueConnectionFactoryName="jms/ConnectionFactory"
- localQueueConnectionFactory="#localFactory">
+ <jmsQueueConnector name="JreportRequestBridge-Inbound"
+ jndiOutboundTemplate="#remoteJndi"
+ outboundQueueConnectionFactoryName="jms/ConnectionFactory"
+ localQueueConnectionFactory="#localFactory">
<inboundQueueBridges>
- <inboundQueueBridge inboundQueueName="jms/queue/jreport/request"/>
+ <inboundQueueBridge inboundQueueName="jms/queue/jreport/request"/>
</inboundQueueBridges>
</jmsQueueConnector>
</jmsBridgeConnectors>
@@ -106,62 +99,60 @@
</broker>
<!-- Set up the template for connecting to Weblogic -->
- <bean id="remoteJndi" class="org.springframework.jndi.JndiTemplate">
- <property name="environment">
+ <bean id="remoteJndi" class="org.springframework.jndi.JndiTemplate">
+ <property name="environment">
<props>
- <prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
- <prop key="java.naming.provider.url">t3://<your ip here>:7001</prop>
+ <prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
+ <prop key="java.naming.provider.url">t3://<your ip here>:7001</prop>
</props>
</property>
</bean>
- <bean id="localFactory"
- class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61616" />
+ <bean id="localFactory"
+ class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="tcp://localhost:61616" />
</bean>
- <bean id="localQueue" class="org.apache.activemq.command.ActiveMQQueue">
- <constructor-arg value="dynamic/jms.queue.jreport.request"/>
+ <bean id="localQueue" class="org.apache.activemq.command.ActiveMQQueue">
+ <constructor-arg value="dynamic/jms.queue.jreport.request"/>
</bean>
</beans>
<!-- END SNIPPET: xbean -->
-]]></script>
-</div></div><h3 id="JMStoJMSBridge-ExamplepureSpringConfigurationforsendingmessagestoexternalActiveMQdestinationthroughbridge">Example pure Spring Configuration for sending messages to external ActiveMQ destination through bridge</h3><p>Spring beans:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
+</plain-text-body></structured-macro><h3>Example pure Spring Configuration for sending messages to external ActiveMQ destination through bridge</h3><p>Spring beans:</p><structured-macro ac:macro-id="cbcd3077-34d7-42fc-a2fc-b21579cd26b5" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
- <bean id="mainBroker" class="org.apache.activemq.broker.BrokerService" init-method="start" destroy-method="stop">
- <property name="brokerName" value = "mainBroker"/>
- <property name="persistent" value="false"/>
- <property name="transportConnectorURIs">
+ <bean id="mainBroker" class="org.apache.activemq.broker.BrokerService" init-method="start" destroy-method="stop">
+ <property name="brokerName" value = "mainBroker"/>
+ <property name="persistent" value="false"/>
+ <property name="transportConnectorURIs">
<list>
<value>tcp://localhost:7000</value>
</list>
</property>
</bean>
- <bean id="bridgedBroker" class="org.apache.activemq.broker.BrokerService" init-method="start" destroy-method="stop">
- <property name="brokerName" value = "bridgedBroker"/>
- <property name="persistent" value="false"/>
- <property name="transportConnectorURIs">
+ <bean id="bridgedBroker" class="org.apache.activemq.broker.BrokerService" init-method="start" destroy-method="stop">
+ <property name="brokerName" value = "bridgedBroker"/>
+ <property name="persistent" value="false"/>
+ <property name="transportConnectorURIs">
<list>
<value>tcp://localhost:7001</value>
</list>
</property>
- <property name="jmsBridgeConnectors">
+ <property name="jmsBridgeConnectors">
<list>
- <bean class="org.apache.activemq.network.jms.JmsQueueConnector">
- <property name="outboundQueueConnectionFactory">
- <bean class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:7000" />
+ <bean class="org.apache.activemq.network.jms.JmsQueueConnector">
+ <property name="outboundQueueConnectionFactory">
+ <bean class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="tcp://localhost:7000" />
</bean>
</property>
- <property name="outboundQueueBridges">
+ <property name="outboundQueueBridges">
<list>
- <bean class="org.apache.activemq.network.jms.OutboundQueueBridge">
- <constructor-arg value="messages.input"/>
+ <bean class="org.apache.activemq.network.jms.OutboundQueueBridge">
+ <constructor-arg value="messages.input"/>
</bean>
</list>
</property>
@@ -171,34 +162,32 @@
</bean>
</beans>
-]]></script>
-</div></div><p>Java code:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[public class BridgeTest {
+</plain-text-body></structured-macro><p>Java code:</p><structured-macro ac:macro-id="ccd7cc10-d4e9-4405-829a-17a18774ab9f" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>public class BridgeTest {
public BridgeTest() throws Exception {
Log log = LogFactory.getLog(getClass());
- new ClassPathXmlApplicationContext("bridge/context-bridge.xml");
+ new ClassPathXmlApplicationContext("bridge/context-bridge.xml");
- ActiveMQConnection connection = ActiveMQConnection.makeConnection("tcp://localhost:7001");
+ ActiveMQConnection connection = ActiveMQConnection.makeConnection("tcp://localhost:7001");
connection.start();
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
- Destination destination = session.createQueue("messages.input");
+ Destination destination = session.createQueue("messages.input");
MessageProducer producer = session.createProducer(destination);
- producer.send(session.createTextMessage("Test Message"));
- log.debug("send message");
+ producer.send(session.createTextMessage("Test Message"));
+ log.debug("send message");
session.close();
connection.close();
- connection = ActiveMQConnection.makeConnection("tcp://localhost:7000");
+ connection = ActiveMQConnection.makeConnection("tcp://localhost:7000");
connection.start();
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
- destination = session.createQueue("messages.input");
+ destination = session.createQueue("messages.input");
MessageConsumer consumer = session.createConsumer(destination);
- log.debug("receive message");
+ log.debug("receive message");
Message message = consumer.receive(5000);
- log.debug("Received: " + message);
+ log.debug("Received: " + message);
session.close();
connection.close();
}
@@ -208,6 +197,5 @@
}
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/jms.xml b/jms.xml
index 8d0ae10..63a9f43 100644
--- a/jms.xml
+++ b/jms.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>Questions on using the JMS API and <a shape="rect" href="mom.xml">MOM</a> in general</p>
+<p>Questions on using the JMS API and <link ac:tooltip="Message Orientated Middleware"><page ri:content-title="MOM"></page><link-body>MOM</link-body></link> in general</p>
-<ul class="childpages-macro"><li><a shape="rect" href="can-i-modify-messages-on-a-queue.xml">Can I modify messages on a queue</a></li><li><a shape="rect" href="can-i-send-and-receive-messages-concurrently-on-one-jms-connection.xml">Can I send and receive messages concurrently on one JMS Connection</a></li><li><a shape="rect" href="can-you-browse-a-topic.xml">Can you browse a topic</a></li><li><a shape="rect" href="how-do-durable-queues-and-topics-work.xml">How do durable queues and topics work</a></li><li><a shape="rect" href="how-does-a-queue-compare-to-a-topic.xml">How does a Queue compare to a Topic</a></li><li><a shape="rect" href="how-does-connectionfactory-relate-to-the-broker.xml">How does ConnectionFactory relate to the Broker</a></li><li><a shape="rect" href="how-does-jms-compare-with-email.xml">How does JMS compare with email</a></li><li><a shape="rect" href="how-do-i-consume-a-specific-message.xml">How do I consume a specific message</a></li><li><a shape="rect" href="how-do-i-get-started-with-jms.xml">How do I get started with JMS</a></li><li><a shape="rect" href="how-do-i-make-messages-durable.xml">How do I make messages durable</a></li><li><a shape="rect" href="how-do-i-send-messages-to-different-destinations-from-a-single-messageproducer.xml">How do I send messages to different Destinations from a single MessageProducer</a></li><li><a shape="rect" href="how-do-i-use-jms-efficiently.xml">How do I use JMS efficiently</a></li><li><a shape="rect" href="how-should-i-implement-request-response-with-jms.xml">How should I implement request response with JMS</a></li><li><a shape="rect" href="how-to-unit-test-jms-code.xml">How To Unit Test JMS Code</a></li><li><a shape="rect" href="multiple-consumers-on-a-queue.xml">Multiple consumers on a queue</a></li><li><a shape="rect" href="should-i-use-transactions.xml">Should I use transactions</a></li><li><a shape="rect" href="should-i-use-xa.xml">Should I use XA</a></li><li><a shape="rect" href="what-are-administered-objects.xml">What are administered objects</a></li></ul></div>
+<structured-macro ac:macro-id="e46b407d-1d1b-4200-8a01-c1974f0207eb" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/jmstemplate-gotchas.xml b/jmstemplate-gotchas.xml
index b6c13fa..c8bef49 100644
--- a/jmstemplate-gotchas.xml
+++ b/jmstemplate-gotchas.xml
@@ -1,18 +1,19 @@
<div class="wiki-content maincontent"><p>The thing to remember is JmsTemplate is designed for use in EJBs using the EJB containers JMS pooling abstraction. So every method will typically create a connection, session, producer or consumer, do something, then close them all down again. The idea being that this will use the J2EE containers pooling mechanism to pool the JMS resources under the covers. Without using a pooled JMS provider from the EJB container this is the worst possible way of working with JMS; since typically each create/close of a connection, producer/consumer results in a request-response with the JMS broker.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">User Story</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>We had a bug once in ActiveMQ where if you created 65535 MessageProducer instances within the space of a few seconds, we'd get an exception thrown in the broker. Its a kinda silly thing to do, to create that many producers in a small space of time (one for each message to be sent) - JMS is designed for resources like producers and consumers to be created up front and reused across many message exchanges. The bug was highlighted by a user using JmsTemplate without a JMS pool underneath. Well at least it helped find our bug which I'm glad to say is now fixed, but it didn't help their performance too much <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p></div></div>
+<structured-macro ac:macro-id="b1b7138d-6479-4785-b123-cb2f14d691e6" ac:name="info" ac:schema-version="1"><parameter ac:name="title">User Story</parameter><rich-text-body>
+<p>We had a bug once in ActiveMQ where if you created 65535 MessageProducer instances within the space of a few seconds, we'd get an exception thrown in the broker. Its a kinda silly thing to do, to create that many producers in a small space of time (one for each message to be sent) - JMS is designed for resources like producers and consumers to be created up front and reused across many message exchanges. The bug was highlighted by a user using JmsTemplate without a JMS pool underneath. Well at least it helped find our bug which I'm glad to say is now fixed, but it didn't help their performance too much <emoticon ac:name="smile"></emoticon></p></rich-text-body></structured-macro>
-<p>You should only use JmsTemplate with a pooled JMS provider. In J2EE 1.4 or later that typically means a JCA based JMS ConnectionFactory. If you are in an EJB then make sure you use your J2EE containers ConnectionFactory, never a plain-old-connection factory. If you are not inside an EJB Then you should use our <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/pool/PooledConnectionFactory.html">PooledConnectionFactory</a>, then things will be nicely pooled. If you need to take part in XA transactions then look into our spring based <a shape="rect" href="jca-container.xml">JCA Container</a>.</p>
+<p>You should only use JmsTemplate with a pooled JMS provider. In J2EE 1.4 or later that typically means a JCA based JMS ConnectionFactory. If you are in an EJB then make sure you use your J2EE containers ConnectionFactory, never a plain-old-connection factory. If you are not inside an EJB Then you should use our <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/pool/PooledConnectionFactory.html">PooledConnectionFactory</a>, then things will be nicely pooled. If you need to take part in XA transactions then look into our spring based <link><page ri:content-title="JCA Container"></page></link>.</p>
-<p>Another gotcha I've seen folks do is to create a MessageConsumer inside one of the SessionCallback methods then wonder why messages are not being received. After the SessionCallback is called, the session will be closed; which will close your consumers too <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">. So if you want to create a MessageConsumer you should create a connection, session and consumer yourself.</p>
+<p>Another gotcha I've seen folks do is to create a MessageConsumer inside one of the SessionCallback methods then wonder why messages are not being received. After the SessionCallback is called, the session will be closed; which will close your consumers too <emoticon ac:name="smile"></emoticon>. So if you want to create a MessageConsumer you should create a connection, session and consumer yourself.</p>
-<p>Another problem I've seen is folks using the JmsTemplate.receive() method; as I've said above if you're not in an EJB using the J2EE containers ConnnectionFactory, a connection, session & consumer will be create and closed for each receive() method. This is all fine and well - if painfully slow unless you are using pooling - but be aware that this mechanism, without pooling, may well miss messages. If you are consuming on a topic which has messages sent with NON_PERSISTENT delivery mode then chances are you will miss messages, since each receive() call is a brand new consumer which will not receive any messages sent before the consumer existed. To receive messages efficiently you should use Spring's <a shape="rect" class="external-link" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-mdp" rel="nofollow">MessageListenerContainer</a>.</p>
+<p>Another problem I've seen is folks using the JmsTemplate.receive() method; as I've said above if you're not in an EJB using the J2EE containers ConnnectionFactory, a connection, session & consumer will be create and closed for each receive() method. This is all fine and well - if painfully slow unless you are using pooling - but be aware that this mechanism, without pooling, may well miss messages. If you are consuming on a topic which has messages sent with NON_PERSISTENT delivery mode then chances are you will miss messages, since each receive() call is a brand new consumer which will not receive any messages sent before the consumer existed. To receive messages efficiently you should use Spring's <a shape="rect" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-mdp">MessageListenerContainer</a>.</p>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">New in 4.x</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>In ActiveMQ <a shape="rect" href="changes-in-40.xml">4.x</a> we have a new feature called <a shape="rect" href="subscription-recovery-policy.xml">Subscription Recovery Policy</a> which even in non-durable delivery mode allows a new consumer to go back in time and receive messages delivered within a window (a fixed amount of RAM or time window). e.g. if your broker dies you have 2 minutes to reconnect to another broker and not miss any messages - even without durable delivery.</p></div></div>
+<structured-macro ac:macro-id="c93967d2-f5ce-4be6-8fa0-91d117d43290" ac:name="info" ac:schema-version="1"><parameter ac:name="title">New in 4.x</parameter><rich-text-body>
+<p>In ActiveMQ <link><page ri:content-title="Changes in 4.0"></page><link-body>4.x</link-body></link> we have a new feature called <link><page ri:content-title="Subscription Recovery Policy"></page></link> which even in non-durable delivery mode allows a new consumer to go back in time and receive messages delivered within a window (a fixed amount of RAM or time window). e.g. if your broker dies you have 2 minutes to reconnect to another broker and not miss any messages - even without durable delivery.</p></rich-text-body></structured-macro>
-<h3 id="JmsTemplateGotchas-RecommendationsforusingJmsTemplate">Recommendations for using JmsTemplate</h3>
+<h3>Recommendations for using JmsTemplate</h3>
-<ul><li>Never use a regular ConnectionFactory unless you are totally sure it does all the pooling you need</li><li>If using in an EJB ensure you use the EJB containers ConnectionFactory</li><li>If you are only publishing messages and you are not in an EJB container and you are using ActiveMQ, then you can use either the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/apidocs/org/activemq/pool/PooledConnectionFactory.html" rel="nofollow">PooledConnectionFactory</a> or the <a shape="rect" class="external-link" href="http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/jms/connection/CachingConnectionFactory.html" rel="nofollow">Spring CachingConnectionFactory</a></li><li>If you are consuming messages its probably simpler & more efficient & less likely to lose messages to avoid using the receive() method and use Spring's <a shape="rect" class="external-link" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-mdp" rel="nofollow">MessageListenerContainer</a> instead</li><li>See also <a shape="rect" class="external-link" href="http://bsnyderblog.blogspot.com/2010/02/using-spring-jmstemplate-to-send-jms.html" rel="nofollow">Using Spring to Send JMS Messages</a> and <a shape="rect" class="external-link" href="http://bsnyderblog.blogspot.com/2010/02/using-spring-to-receive-jms-messages.html" rel="nofollow">Using Spring to Receive JMS Messages</a></li></ul></div>
+<ul><li>Never use a regular ConnectionFactory unless you are totally sure it does all the pooling you need</li><li>If using in an EJB ensure you use the EJB containers ConnectionFactory</li><li>If you are only publishing messages and you are not in an EJB container and you are using ActiveMQ, then you can use either the <a shape="rect" href="http://activemq.codehaus.org/maven/apidocs/org/activemq/pool/PooledConnectionFactory.html">PooledConnectionFactory</a> or the <a shape="rect" href="http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/jms/connection/CachingConnectionFactory.html">Spring CachingConnectionFactory</a></li><li>If you are consuming messages its probably simpler & more efficient & less likely to lose messages to avoid using the receive() method and use Spring's <a shape="rect" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-mdp">MessageListenerContainer</a> instead</li><li>See also <a shape="rect" href="http://bsnyderblog.blogspot.com/2010/02/using-spring-jmstemplate-to-send-jms.html">Using Spring to Send JMS Messages</a> and <a shape="rect" href="http://bsnyderblog.blogspot.com/2010/02/using-spring-to-receive-jms-messages.html">Using Spring to Receive JMS Messages</a></li></ul>
+</div>
diff --git a/jmsxuserid.xml b/jmsxuserid.xml
index 4c12574..74d7408 100644
--- a/jmsxuserid.xml
+++ b/jmsxuserid.xml
@@ -1,32 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="JMSXUserID-JMSXUserIDsupport">JMSXUserID support</h2>
+<div class="wiki-content maincontent"><h2>JMSXUserID support</h2>
<p>It is sometimes useful to know the authenticated username of the sender of a message. This is not added by default but you can enable it by setting the <strong>populateJMSXUserID</strong> property on the broker via Java code</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b5da1390-e2d9-495f-b57d-445b3748f0a7" ac:name="code" ac:schema-version="1"><plain-text-body>
BrokerService broker = new BrokerService();
broker.setPopulateJMSXUserID(true);
broker.start();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>Or via the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a></p>
+<p>Or via the <link><page ri:content-title="Xml Configuration"></page></link></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker xmlns="http://activemq.org/config/1.0" populateJMSXUserID="true">
+<structured-macro ac:macro-id="2c740d5e-cee9-4294-9c5f-2128b841dbb8" ac:name="code" ac:schema-version="1"><plain-text-body>
+<broker xmlns="http://activemq.org/config/1.0" populateJMSXUserID="true">
...
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>Or via the <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a>.</p>
+<p>Or via the <link><page ri:content-title="Broker Configuration URI"></page></link>.</p>
<p>Once enabled this feature adds the JMS property <strong>JMSXUserID</strong> to each JMS message so that a consumer can know exactly who the sender was using the broker's authentication policy. i.e. it is not possibile for a producer to spoof this value if this feature is enabled since the broker attaches the property to the message after the senders connection is authenticated.</p>
<p>If you allow anonymous access, you MUST also add the </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[useAuthenticatedPrincipalForJMSXUserID="true"]]></script>
-</div></div>
+<structured-macro ac:macro-id="467587ab-74a0-4e73-bfbe-091d09bd2305" ac:name="code" ac:schema-version="1"><plain-text-body>useAuthenticatedPrincipalForJMSXUserID="true"</plain-text-body></structured-macro>
<p> property of the broker element. Otherwise, anonymous clients can spoof identities by setting the JMSXUserID property on from the client. This property is available in version 5.5 or 5.5-SNAPSHOT > March 12th. Note, though, that for SSL certificate based authentication, e.g., when using TextFileCertificateLoginModule JAAS module, this will change the semantics of the broker-provided JMSXUserID. Instead of returning the DN of the certificate, it will provide the name the DN is mapped to by the JAAS module.</p></div>
diff --git a/jmx-support.xml b/jmx-support.xml
index b5523c1..5ff0e41 100644
--- a/jmx-support.xml
+++ b/jmx-support.xml
@@ -1,15 +1,15 @@
<div class="wiki-content maincontent">
<p>This page describes the JMX management requirements.</p>
-<h2 id="JMXSupport-RequiredMBeans">Required MBeans</h2>
+<h2>Required MBeans</h2>
-<h3 id="JMXSupport-BrokerMBeans">Broker MBeans</h3>
+<h3>Broker MBeans</h3>
<p>We need MBeans for the core Broker types in the activemq.broker package to allow folks to see a broker's configuration, its connectors, currently connected clients & disconnect clients etc.</p>
<p>e.g. MBeans for </p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>MBean</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Broker/BrokerContainer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The Message Broker itself</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>BrokerConnector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The inbound connector listening to new client connections</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>BrokerClient</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A specific client connection</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>MBean</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>Broker/BrokerContainer</p></td><td colspan="1" rowspan="1"><p>The Message Broker itself</p></td></tr><tr><td colspan="1" rowspan="1"><p>BrokerConnector</p></td><td colspan="1" rowspan="1"><p>The inbound connector listening to new client connections</p></td></tr><tr><td colspan="1" rowspan="1"><p>BrokerClient</p></td><td colspan="1" rowspan="1"><p>A specific client connection</p></td></tr></tbody></table>
<p>We have an old BrokerAdmin interface we should replace with proper MBeans ASAP.</p>
@@ -18,11 +18,11 @@
<p>So we'll need some way of viewing and looking up of thesse MC MBeans as they are created dynamically as users start using different destionations.</p>
-<h3 id="JMXSupport-Statistics">Statistics</h3>
+<h3>Statistics</h3>
<p>We implement J2EE Management Stats which add stats to each JMS resource; Connection, Session, Consumer, Producer (and we've added support to Destination too). So we need to expose those somehow in JMX so users can watch/view stats for JMS clients</p>
-<h2 id="JMXSupport-Usecases">Use cases</h2>
+<h2>Use cases</h2>
<p>Here's a list of end user use cases we need to support easily...</p>
@@ -33,9 +33,10 @@
<ul><li>viewing contents of queues/topics</li><li>starting/stopping remote brokers</li></ul>
-<h2 id="JMXSupport-Issues">Issues</h2>
+<h2>Issues</h2>
<ul><li>do we need/want an MBean per JMS Connection/Session/Producer/Consumer? Am not sure why other than a way to grab stats; if so maybe some kinda stats MBean instead?</li></ul>
+
</div>
diff --git a/jmx.xml b/jmx.xml
index d2520b1..c1048d7 100644
--- a/jmx.xml
+++ b/jmx.xml
@@ -1,37 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="JMX-JMX">JMX</h2><p>Apache ActiveMQ has extensive support for JMX to allow you to monitor and control the behavior of the broker via the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/jmx/package-summary.html">JMX MBeans</a>.</p><h3 id="JMX-UsingJMXtomonitorApacheActiveMQ">Using JMX to monitor Apache ActiveMQ</h3><p>You can enable/disable JMX support as follows...</p><p>1. <a shape="rect" href="run-broker.xml">Run a broker</a> setting the broker property useJmx to true (enabled by default) i.e.</p><p>For xbean configuration</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker useJmx="true" brokerName="BROKER1">
+<div class="wiki-content maincontent"><h2>JMX</h2><p>Apache ActiveMQ has extensive support for JMX to allow you to monitor and control the behavior of the broker via the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/jmx/package-summary.html">JMX MBeans</a>.</p><h3>Using JMX to monitor Apache ActiveMQ</h3><p>You can enable/disable JMX support as follows...</p><p>1. <link><page ri:content-title="Run Broker"></page><plain-text-link-body>Run a broker</plain-text-link-body></link> setting the broker property useJmx to true (enabled by default) i.e.</p><p>For xbean configuration</p><structured-macro ac:macro-id="ffdf8aca-7895-4a18-91a1-5d432b672168" ac:name="code" ac:schema-version="1"><plain-text-body><broker useJmx="true" brokerName="BROKER1">
...
</broker>
-]]></script>
-</div></div><p>2. Run a JMX console</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ jconsole ]]></script>
-</div></div><p>3. The ActiveMQ broker should appear in the list of local connections, if you are running JConsole on the same host as ActiveMQ.</p><p><strong style="color: rgb(102,0,51);font-size: 16.0px;"><br clear="none"></strong></p><p><strong style="color: rgb(102,0,51);font-size: 16.0px;">JMX remote access</strong></p><p>Remote connections to JMX are not enabled by default in the activemq.xml for security reasons. Please refer to <a shape="rect" class="external-link" href="http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html" rel="nofollow">Java Management guide</a> to configure the broker for remote management.</p><p> </p><p><span style="line-height: 1.4285715;">Using the Apache ActiveMQ version on OS X it appears as follows:</span></p><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="jmx.data/activemq-jmx.png" data-image-src="/confluence/download/attachments/35976/activemq-jmx.png?version=1&modificationDate=1181607318000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="4495" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="activemq-jmx.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35976" data-linked-resource-container-version="39"></span><br clear="none">  </p><h3 id="JMX-ActiveMQMBeansReference">ActiveMQ MBeans Reference</h3><p>For additional references provided below is a brief hierarchy of the mbeans and a listing of the properties, attributes, and operations of each mbeans.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Mbean Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Properties / ObjectName </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Attributes </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Operations </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Broker</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<broker identifier></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>BrokerId</li><li>TotalEnqueueCount</li><li>TotalDequeueCount</li><li>TotalConsumerCount</li><li>TotalMessageCount</li><li>TotalConnectionsCount</li><li>TotalConsumerCount</li><li>TotalProducerCount</li><li>MemoryLimit</li><li>MemoryPercentUsage</li><li>StoreLimit</li><li>StorePercentUsage</li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>start</li><li>stop</li><li>terminateJVM</li><li>resetStatistics</li><li>gc</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Destination</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<name of broker></li><li><strong>destinationType</strong>=Queue|Topic</li><li><strong>destinationName</strong>=<name></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>AverageEnqueueTime</li><li><span style="line-height: 1.4285715;">ConsumerCount</span></li><li><span style="line-height: 1.4285715;">DequeueCount</span></li><li>EnqueueCount</li><li>ExpiredCount</li><li>InFlightCount</li><li><span style="line-height: 1.4285715;">MemoryLimit</span></li><li>MemoryPercentUsage</li><li>Name</li><li><span style="line-height: 1.4285715;">QueueSize (queues only)</span></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>browseMessages</li><li>gc</li><li>purge</li><li>resetStatistics</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> NetworkConnector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<name of broker></li><li><strong>connector</strong>=networkConnectors</li><li><strong>networkConnectorName</strong>=<connector identifier></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>Name</li><li>Duplex</li><li>DynamicOnly</li><li>BridgeTempDestinations</li><li>ConduitSubscriptions</li><li>DecreaseNetworkConsumerPriority</li><li>DispatchAsync</li><li>DynamicOnly</li><li>NetworkTTL</li><li>Password</li><li>PrefetchSize</li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>start</li><li>stop</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Connector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<name of broker></li><li><strong>connector</strong>=clientConnectors</li><li><strong>ConnectorName</strong>=<connector identifier></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>StatisticsEnabled</li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>start</li><li>stop</li><li>resetStatistics</li><li>enableStatistics</li><li>disableStatistics</li><li>connectionCount</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Connection</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<name of broker></li><li><strong>connectionViewType</strong>=clientId</li><li><strong>connectionName</strong>=<connection identifier></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>DispatchQueueSize</li><li>Active</li><li>Blocked</li><li>Connected</li><li>Slow</li><li>Consumers</li><li>Producers</li><li>RemoteAddress</li><li>UserName</li><li>ClientId</li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>start</li><li>stop</li><li>resetStatistics</li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>  PersistenceAdapter</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<broker name></li><li><strong>Service</strong>=PersistenceAdapter</li><li><strong>InstanceName</strong>=<adapter identifier></li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>Name</li><li>Size</li><li>Data</li><li>Transactions</li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Health</p></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<broker name></li><li><strong>Service</strong>=Health</li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>CurrentStatus</li></ul></td><td colspan="1" rowspan="1" class="confluenceTd"><ul><li>health</li></ul></td></tr></tbody></table></div><p>Command line utilities are also available to let you monitor ActiveMQ. Refer to <a shape="rect" href="activemq-command-line-tools-reference.xml">ActiveMQ Command Line Tools Reference</a> for usage information.</p><p>JMX API is also exposed via <a shape="rect" href="rest.xml#REST-RestManagement">REST management API </a></p><h3 id="JMX-PasswordProtectingtheJMXConnector">Password Protecting the JMX Connector</h3><p>(For Java 1.5+)</p><p>1. Make sure JMX is enabled, but tell ActiveMQ <strong>not</strong> create its own connector so that it will use the default JVM JMX connector.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker xmlns="http://activemq.org/config/1.0" brokerName="localhost"useJmx="true">
+</plain-text-body></structured-macro><p>2. Run a JMX console</p><structured-macro ac:macro-id="171443e0-69a0-46f4-b507-386689ea89ad" ac:name="code" ac:schema-version="1"><plain-text-body>$ jconsole </plain-text-body></structured-macro><p>3. The ActiveMQ broker should appear in the list of local connections, if you are running JConsole on the same host as ActiveMQ.</p><p><strong style="color: rgb(102,0,51);font-size: 16.0px;"><br clear="none"></strong></p><p><strong style="color: rgb(102,0,51);font-size: 16.0px;">JMX remote access</strong></p><p>Remote connections to JMX are not enabled by default in the activemq.xml for security reasons. Please refer to <a shape="rect" href="http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html">Java Management guide</a> to configure the broker for remote management.</p><p> </p><p><span style="line-height: 1.4285715;">Using the Apache ActiveMQ version on OS X it appears as follows:</span></p><p><image><attachment ri:filename="activemq-jmx.png"></attachment></image><br clear="none">  </p><h3>ActiveMQ MBeans Reference</h3><p>For additional references provided below is a brief hierarchy of the mbeans and a listing of the properties, attributes, and operations of each mbeans.</p><table><tbody><tr><th colspan="1" rowspan="1"><p> Mbean Type</p></th><th colspan="1" rowspan="1"><p>Properties / ObjectName </p></th><th colspan="1" rowspan="1"><p>Attributes </p></th><th colspan="1" rowspan="1"><p>Operations </p></th></tr><tr><td colspan="1" rowspan="1"><p> Broker</p></td><td colspan="1" rowspan="1"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<broker identifier></li></ul></td><td colspan="1" rowspan="1"><ul><li>BrokerId</li><li>TotalEnqueueCount</li><li>TotalDequeueCount</li><li>TotalConsumerCount</li><li>TotalMessageCount</li><li>TotalConnectionsCount</li><li>TotalConsumerCount</li><li>TotalProducerCount</li><li>MemoryLimit</li><li>MemoryPercentUsage</li><li>StoreLimit</li><li>StorePercentUsage</li></ul></td><td colspan="1" rowspan="1"><ul><li>start</li><li>stop</li><li>terminateJVM</li><li>resetStatistics</li><li>gc</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p> Destination</p></td><td colspan="1" rowspan="1"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<name of broker></li><li><strong>destinationType</strong>=Queue|Topic</li><li><strong>destinationName</strong>=<name></li></ul></td><td colspan="1" rowspan="1"><ul><li>AverageEnqueueTime</li><li><span style="line-height: 1.4285715;">ConsumerCount</span></li><li><span style="line-height: 1.4285715;">DequeueCount</span></li><li>EnqueueCount</li><li>ExpiredCount</li><li>InFlightCount</li><li><span style="line-height: 1.4285715;">MemoryLimit</span></li><li>MemoryPercentUsage</li><li>Name</li><li><span style="line-height: 1.4285715;">QueueSize (queues only)</span></li></ul></td><td colspan="1" rowspan="1"><ul><li>browseMessages</li><li>gc</li><li>purge</li><li>resetStatistics</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p> NetworkConnector</p></td><td colspan="1" rowspan="1"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<name of broker></li><li><strong>connector</strong>=networkConnectors</li><li><strong>networkConnectorName</strong>=<connector identifier></li></ul></td><td colspan="1" rowspan="1"><ul><li>Name</li><li>Duplex</li><li>DynamicOnly</li><li>BridgeTempDestinations</li><li>ConduitSubscriptions</li><li>DecreaseNetworkConsumerPriority</li><li>DispatchAsync</li><li>DynamicOnly</li><li>NetworkTTL</li><li>Password</li><li>PrefetchSize</li></ul></td><td colspan="1" rowspan="1"><ul><li>start</li><li>stop</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p> Connector</p></td><td colspan="1" rowspan="1"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<name of broker></li><li><strong>connector</strong>=clientConnectors</li><li><strong>ConnectorName</strong>=<connector identifier></li></ul></td><td colspan="1" rowspan="1"><ul><li>StatisticsEnabled</li></ul></td><td colspan="1" rowspan="1"><ul><li>start</li><li>stop</li><li>resetStatistics</li><li>enableStatistics</li><li>disableStatistics</li><li>connectionCount</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p> Connection</p></td><td colspan="1" rowspan="1"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<name of broker></li><li><strong>connectionViewType</strong>=clientId</li><li><strong>connectionName</strong>=<connection identifier></li></ul></td><td colspan="1" rowspan="1"><ul><li>DispatchQueueSize</li><li>Active</li><li>Blocked</li><li>Connected</li><li>Slow</li><li>Consumers</li><li>Producers</li><li>RemoteAddress</li><li>UserName</li><li>ClientId</li></ul></td><td colspan="1" rowspan="1"><ul><li>start</li><li>stop</li><li>resetStatistics</li></ul></td></tr><tr><td colspan="1" rowspan="1"><p>  PersistenceAdapter</p></td><td colspan="1" rowspan="1"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<broker name></li><li><strong>Service</strong>=PersistenceAdapter</li><li><strong>InstanceName</strong>=<adapter identifier></li></ul></td><td colspan="1" rowspan="1"><ul><li>Name</li><li>Size</li><li>Data</li><li>Transactions</li></ul></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Health</p></td><td colspan="1" rowspan="1"><ul><li><strong>type</strong>=Broker</li><li><strong>brokerName</strong>=<broker name></li><li><strong>Service</strong>=Health</li></ul></td><td colspan="1" rowspan="1"><ul><li>CurrentStatus</li></ul></td><td colspan="1" rowspan="1"><ul><li>health</li></ul></td></tr></tbody></table><p>Command line utilities are also available to let you monitor ActiveMQ. Refer to <link><page ri:content-title="ActiveMQ Command Line Tools Reference"></page></link> for usage information.</p><p>JMX API is also exposed via <link ac:anchor="Rest Management"><page ri:content-title="REST"></page><plain-text-link-body>REST management API </plain-text-link-body></link></p><h3>Password Protecting the JMX Connector</h3><p>(For Java 1.5+)</p><p>1. Make sure JMX is enabled, but tell ActiveMQ <strong>not</strong> create its own connector so that it will use the default JVM JMX connector.</p><structured-macro ac:macro-id="8464c71e-56cc-4fb0-aec3-7d93bfb2ffe2" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><broker xmlns="http://activemq.org/config/1.0" brokerName="localhost"useJmx="true">
...
<managementContext>
- <managementContext createConnector="false"/>
+ <managementContext createConnector="false"/>
</managementContext>
...
</broker>
-]]></script>
-</div></div><p>2. Create access and password files</p><p>conf/jmx.access:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[# The "monitorRole" role has readonly access.
-# The "controlRole" role has readwrite access.
+</plain-text-body></structured-macro><p>2. Create access and password files</p><p>conf/jmx.access:</p><structured-macro ac:macro-id="f5545277-e779-4925-8de7-bf2a9c5b5fde" ac:name="code" ac:schema-version="1"><plain-text-body># The "monitorRole" role has readonly access.
+# The "controlRole" role has readwrite access.
monitorRole readonly
controlRole readwrite
-]]></script>
-</div></div><p>conf/jmx.password:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[# The "monitorRole" role has password "abc123".
-# The "controlRole" role has password "abcd1234".
+</plain-text-body></structured-macro><p>conf/jmx.password:</p><structured-macro ac:macro-id="b0ea5924-d5f5-4ce1-98d3-0aebdcde6ff3" ac:name="code" ac:schema-version="1"><plain-text-body># The "monitorRole" role has password "abc123".
+# The "controlRole" role has password "abcd1234".
monitorRole abc123
controlRole abcd1234
-]]></script>
-</div></div><p>(Make sure both files are not world readable - more info can be find <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html#auth" rel="nofollow">here</a> to protect files)</p><p>For more details you can see the <a shape="rect" class="external-link" href="http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html">Monitoring Tomcat Document</a></p><p>3. Modify the "activemq" startup script (in bin) to enable the Java 1.5+ JMX connector</p><p>Find the "ACTIVEMQ_SUNJMX_START=" line and change it too the following: (note that in previous versions of ActiveMQ this property was called SUNJMX in some scripts.  As of v5.12.0 all scripts use ACTIVEMQ_SUNJMX_START):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[1. Windows
+</plain-text-body></structured-macro><p>(Make sure both files are not world readable - more info can be find <a shape="rect" href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html#auth">here</a> to protect files)</p><p>For more details you can see the <a shape="rect" href="http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html">Monitoring Tomcat Document</a></p><p>3. Modify the "activemq" startup script (in bin) to enable the Java 1.5+ JMX connector</p><p>Find the "ACTIVEMQ_SUNJMX_START=" line and change it too the following: (note that in previous versions of ActiveMQ this property was called SUNJMX in some scripts.  As of v5.12.0 all scripts use ACTIVEMQ_SUNJMX_START):</p><structured-macro ac:macro-id="54f2c4ab-bea5-48aa-b626-9084c0f0c664" ac:name="code" ac:schema-version="1"><plain-text-body>1. Windows
ACTIVEMQ_SUNJMX_START=-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.password.file=%ACTIVEMQ_BASE%/conf/jmx.password \
@@ -39,12 +28,10 @@
2. Unix
- ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
+ ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_BASE}/conf/jmx.password \
- -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_BASE}/conf/jmx.access"
-]]></script>
-</div></div><p>This could be set in /etc/activemq.conf instead (if you have root access):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[1. Windows
+ -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_BASE}/conf/jmx.access"
+</plain-text-body></structured-macro><p>This could be set in /etc/activemq.conf instead (if you have root access):</p><structured-macro ac:macro-id="2e3f12e0-d7a0-413f-98b2-efdc6d92f08f" ac:name="code" ac:schema-version="1"><plain-text-body>1. Windows
ACTIVEMQ_HOME=DRIVE_LETTER:/where/ActiveMQ/is/installed
ACTIVEMQ_BASE=%ACTIVEMQ_HOME%
@@ -56,18 +43,13 @@
ACTIVEMQ_HOME=DRIVE_LETTER:/where/ActiveMQ/is/installed
ACTIVEMQ_BASE=${ACTIVEMQ_HOME}
-ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
+ACTIVEMQ_SUNJMX_START="-Dcom.sun.management.jmxremote.port=1616 -Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.password.file=${ACTIVEMQ_BASE}/conf/jmx.password \
- -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_BASE}/conf/jmx.access"
-]]></script>
-</div></div><p>4. Start ActiveMQ</p><p>You should be able to connect to JMX on the JMX URL</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[service:jmx:rmi:///jndi/rmi://<your hostname>:1616/jmxrmi
-]]></script>
-</div></div><p>And you will be forced to login.</p><h3 id="JMX-SelectiveMBeanregistration">Selective MBean registration</h3><p>In situations where you need to scale your broker to large number of connections, destinations and consumers it can become very expensive to keep JMX MBeans for all those objects. Instead of turning off JMX completely, starting with 5.12.0, you can selectively suppress registration of some types of MBeans and thus help your broker scale, while still having a basic view of the broker state.</p><p>For example, the following configuration will exclude all dynamic producers, consumers, connections and advisory topics from registering their MBeans</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<managementContext>
-<managementContext
- suppressMBean="endpoint=dynamicProducer,endpoint=Consumer,connectionName=*,destinationName=ActiveMQ.Advisory.*"
+ -Dcom.sun.management.jmxremote.access.file=${ACTIVEMQ_BASE}/conf/jmx.access"
+</plain-text-body></structured-macro><p>4. Start ActiveMQ</p><p>You should be able to connect to JMX on the JMX URL</p><structured-macro ac:macro-id="5703fa7f-962a-4044-87c8-41d1d828d15c" ac:name="code" ac:schema-version="1"><plain-text-body>service:jmx:rmi:///jndi/rmi://<your hostname>:1616/jmxrmi
+</plain-text-body></structured-macro><p>And you will be forced to login.</p><h3>Selective MBean registration</h3><p>In situations where you need to scale your broker to large number of connections, destinations and consumers it can become very expensive to keep JMX MBeans for all those objects. Instead of turning off JMX completely, starting with 5.12.0, you can selectively suppress registration of some types of MBeans and thus help your broker scale, while still having a basic view of the broker state.</p><p>For example, the following configuration will exclude all dynamic producers, consumers, connections and advisory topics from registering their MBeans</p><structured-macro ac:macro-id="72278916-ebd3-4827-b0d7-89db4f39b1be" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><managementContext>
+<managementContext 
+ suppressMBean="endpoint=dynamicProducer,endpoint=Consumer,connectionName=*,destinationName=ActiveMQ.Advisory.*"
/>
-</managementContext>]]></script>
-</div></div><p> </p><h4 id="JMX-ManagementContextPropertiesReference">ManagementContext Properties Reference</h4><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property 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>useMBeanServer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true then it avoids creating a new MBean server if a MBeanServer has already been created in the JVM</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>jmxDomainName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>org.apache.activemq</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The jmx domain that all objects names will use</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>createMBeanServer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If we should create the MBeanServer is none is found.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>createConnector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(119,119,119);"><span style="color: rgb(0,0,0);">Please refer to</span> </span><a shape="rect" class="external-link" href="http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html" rel="nofollow">Java Management guide</a><span style="color: rgb(119,119,119);"> <span style="color: rgb(0,0,0);">to configure the server for remote management and lock down the endpoint serialisation with an appropriate <a shape="rect" class="external-link" href="http://openjdk.java.net/jeps/290" rel="nofollow"> jdk.serialFilter</a></span></span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectorPort</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1099</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The port that the JMX connector will use</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectorHost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>localhost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The host that the JMX connector and RMI server (if rmiServerPort>0) will use</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>rmiServerPort</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The RMI server port, handy if port usage needs to be restricted behind a firewall</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectorPath</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>/jmxrmi</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The path that JMX connector will be registered under</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>findTigerMBeanServer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables/disables the searching for the Java 5 platform MBeanServer</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>suppressMBean</p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd">List of MBean name patters to ignore</td></tr></tbody></table></div></div>
+</managementContext></plain-text-body></structured-macro><p> </p><h4>ManagementContext Properties Reference</h4><table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>useMBeanServer</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If true then it avoids creating a new MBean server if a MBeanServer has already been created in the JVM</p></td></tr><tr><td colspan="1" rowspan="1"><p>jmxDomainName</p></td><td colspan="1" rowspan="1"><p>org.apache.activemq</p></td><td colspan="1" rowspan="1"><p>The jmx domain that all objects names will use</p></td></tr><tr><td colspan="1" rowspan="1"><p>createMBeanServer</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If we should create the MBeanServer is none is found.</p></td></tr><tr><td colspan="1" rowspan="1"><p>createConnector</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p><span style="color: rgb(119,119,119);"><span style="color: rgb(0,0,0);">Please refer to</span> </span><a shape="rect" href="http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html">Java Management guide</a><span style="color: rgb(119,119,119);"> <span style="color: rgb(0,0,0);">to configure the server for remote management and lock down the endpoint serialisation with an appropriate <a shape="rect" href="http://openjdk.java.net/jeps/290"> jdk.serialFilter</a></span></span></p></td></tr><tr><td colspan="1" rowspan="1"><p>connectorPort</p></td><td colspan="1" rowspan="1"><p>1099</p></td><td colspan="1" rowspan="1"><p>The port that the JMX connector will use</p></td></tr><tr><td colspan="1" rowspan="1"><p>connectorHost</p></td><td colspan="1" rowspan="1"><p>localhost</p></td><td colspan="1" rowspan="1"><p>The host that the JMX connector and RMI server (if rmiServerPort>0) will use</p></td></tr><tr><td colspan="1" rowspan="1"><p>rmiServerPort</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>The RMI server port, handy if port usage needs to be restricted behind a firewall</p></td></tr><tr><td colspan="1" rowspan="1"><p>connectorPath</p></td><td colspan="1" rowspan="1"><p>/jmxrmi</p></td><td colspan="1" rowspan="1"><p>The path that JMX connector will be registered under</p></td></tr><tr><td colspan="1" rowspan="1"><p>findTigerMBeanServer</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Enables/disables the searching for the Java 5 platform MBeanServer</p></td></tr><tr><td colspan="1" rowspan="1"><p>suppressMBean</p></td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1">List of MBean name patters to ignore</td></tr></tbody></table></div>
diff --git a/jndi-support.xml b/jndi-support.xml
index 9514884..68bd0e6 100644
--- a/jndi-support.xml
+++ b/jndi-support.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>ActiveMQ will work with any JNDI provider capable of storing Java objects. However it is common to require a JNDI initial context to be able to run many JMS example programs, like <a shape="rect" class="external-link" href="http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/jms_tutorialTOC.html" rel="nofollow">Sun's JMS tutorial.</a></p><p>So we provide a simple JNDI <strong><code>InitialContextFactory</code></strong> which can be used to lookup JMS connection factory objects as well as Destination objects. For example if you place this <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/jndi.properties">jndi.properties</a> file on your classpath, you can look inside the <strong><code>InitialContext</code></strong> and lookup <strong><code>ConnectionFactory</code></strong> objects and <strong><code>Destinations</code></strong> etc.</p><plain-text-body>java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory
+<div class="wiki-content maincontent"><p>ActiveMQ will work with any JNDI provider capable of storing Java objects. However it is common to require a JNDI initial context to be able to run many JMS example programs, like <a shape="rect" href="http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/jms_tutorialTOC.html">Sun's JMS tutorial.</a></p><p>So we provide a simple JNDI <strong><code>InitialContextFactory</code></strong> which can be used to lookup JMS connection factory objects as well as Destination objects. For example if you place this <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/jndi.properties">jndi.properties</a> file on your classpath, you can look inside the <strong><code>InitialContext</code></strong> and lookup <strong><code>ConnectionFactory</code></strong> objects and <strong><code>Destinations</code></strong> etc.</p><plain-text-body>java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory
# Use the following property to configure the default connector
java.naming.provider.url = vm://localhost
@@ -13,7 +13,7 @@
# Register some topics in JNDI using the form:
# topic.[jndiName] = [physicalName]
-topic.MyTopic = example.MyTopic</plain-text-body><p>You can edit the <strong><code>jndi.properties</code></strong> file to configure the <strong><code>ActiveMQConnectionFactory</code></strong>'s properties such as <strong><code>brokerURL</code></strong> and whether or not there should be an embedded broker etc. See <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">how to embed a broker in a connection</a> for more details.</p><h3 id="JNDISupport-ActiveMQJNDITutorial">ActiveMQ JNDI Tutorial</h3><p>This is a quick one page tutorial on how to setup and use JNDI to create a connection to ActiveMQ. The first thing is ActiveMQ does not provide a full JNDI server. This means JMS clients need to use properties files to create a JNDI <strong><code>IntialContextFactory</code></strong>. If you need an example properties file, you can look the source distribution <a shape="rect" class="external-link" href="https://github.com/apache/activemq/blob/master/activemq-unit-tests/src/test/resources/jndi.properties" rel="nofollow">https://github.com/apache/activemq/blob/master/activemq-unit-tests/src/test/resources/jndi.properties</a>. Before we proceed, here are the properties.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>java.naming.factory.initial</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>org.apache.activemq.jndi.ActiveMQInitialContextFactory</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>java.naming.provider.url</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>tcp://hostname:61616</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>topic.MyTopic</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>example.MyTopic</code></p></td></tr></tbody></table></div><p>Make sure to add <strong><code>activemq-<em><version></em>.jar</code></strong> and <strong><code>spring-1.x.jar</code></strong> to your classpath. If the libraries are not in the classpath, you will get a <strong><code>ClassNotFoundException</code></strong> at runtime. If you get <strong><code>ClassNotFoundException</code></strong>, try printing out the classpath and check it is present. You can also run ActiveMQ with <strong><code>-verbose</code></strong> option to verify the jar was loaded correctly.</p><p><strong>Sample Code</strong></p><parameter ac:name="language">java</parameter><plain-text-body>// Create a new intial context, which loads from jndi.properties file:
+topic.MyTopic = example.MyTopic</plain-text-body><p>You can edit the <strong><code>jndi.properties</code></strong> file to configure the <strong><code>ActiveMQConnectionFactory</code></strong>'s properties such as <strong><code>brokerURL</code></strong> and whether or not there should be an embedded broker etc. See <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>how to embed a broker in a connection</plain-text-link-body></link> for more details.</p><h3>ActiveMQ JNDI Tutorial</h3><p>This is a quick one page tutorial on how to setup and use JNDI to create a connection to ActiveMQ. The first thing is ActiveMQ does not provide a full JNDI server. This means JMS clients need to use properties files to create a JNDI <strong><code>IntialContextFactory</code></strong>. If you need an example properties file, you can look the source distribution <a shape="rect" href="https://github.com/apache/activemq/blob/master/activemq-unit-tests/src/test/resources/jndi.properties">https://github.com/apache/activemq/blob/master/activemq-unit-tests/src/test/resources/jndi.properties</a>. Before we proceed, here are the properties.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Name</p></th><th colspan="1" rowspan="1"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>java.naming.factory.initial</code></p></td><td colspan="1" rowspan="1"><p><code>org.apache.activemq.jndi.ActiveMQInitialContextFactory</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>java.naming.provider.url</code></p></td><td colspan="1" rowspan="1"><p><code>tcp://hostname:61616</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>topic.MyTopic</code></p></td><td colspan="1" rowspan="1"><p><code>example.MyTopic</code></p></td></tr></tbody></table><p>Make sure to add <strong><code>activemq-<em><version></em>.jar</code></strong> and <strong><code>spring-1.x.jar</code></strong> to your classpath. If the libraries are not in the classpath, you will get a <strong><code>ClassNotFoundException</code></strong> at runtime. If you get <strong><code>ClassNotFoundException</code></strong>, try printing out the classpath and check it is present. You can also run ActiveMQ with <strong><code>-verbose</code></strong> option to verify the jar was loaded correctly.</p><p><strong>Sample Code</strong></p><parameter ac:name="language">java</parameter><plain-text-body>// Create a new intial context, which loads from jndi.properties file:
javax.naming.Context ctx = new javax.naming.InitialContext();
// Lookup the connection factory:
@@ -30,14 +30,14 @@
// Create a new subscriber to receive messages:
javax.jms.TopicSubscriber subscriber = session.createSubscriber(mytopic);
-</plain-text-body><p>Notice the name of the topic in the sample is <strong><code>MyTopic</code></strong>. ActiveMQ will read the <strong><code>jndi.properties</code></strong> files and creates the topics and queues in a lazy fashion. The prefix topic and queue is stripped, so the JNDI name begins after the prefix.</p><p>Once you have the <strong><code>jndi.properties</code></strong> edited and ready, it needs to be accessible to your application. The easiest way is to add <strong><code>jndi.properties</code></strong> to a jar file. When <strong><code>new InitialContext()</code></strong> is called, it will scan the resources and find the file. If you get <strong><code>javax.naming.NamingException</code></strong>, it usually means the <strong><code>jndi.properties</code></strong> file is not accessible.</p><p>You can also try to create a new initial context using either an instance of properties file or a map. For example, the approach recommended by JMS specification will work just fine.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Example Recommended by Specification</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><parameter ac:name="language">java</parameter><plain-text-body>Properties props = new Properties();
+</plain-text-body><p>Notice the name of the topic in the sample is <strong><code>MyTopic</code></strong>. ActiveMQ will read the <strong><code>jndi.properties</code></strong> files and creates the topics and queues in a lazy fashion. The prefix topic and queue is stripped, so the JNDI name begins after the prefix.</p><p>Once you have the <strong><code>jndi.properties</code></strong> edited and ready, it needs to be accessible to your application. The easiest way is to add <strong><code>jndi.properties</code></strong> to a jar file. When <strong><code>new InitialContext()</code></strong> is called, it will scan the resources and find the file. If you get <strong><code>javax.naming.NamingException</code></strong>, it usually means the <strong><code>jndi.properties</code></strong> file is not accessible.</p><p>You can also try to create a new initial context using either an instance of properties file or a map. For example, the approach recommended by JMS specification will work just fine.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Example Recommended by Specification</p></th></tr><tr><td colspan="1" rowspan="1"><parameter ac:name="language">java</parameter><plain-text-body>Properties props = new Properties();
props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
props.setProperty(Context.PROVIDER_URL,"tcp://hostname:61616");
javax.naming.Context ctx = new InitialContext(props);||
-</plain-text-body></td></tr></tbody></table></div><p>If ActiveMQ is embedded within an EJB container, you will need to look at the containers documentation for the correct JNDI values.</p><h3 id="JNDISupport-DynamicallyCreatingDestinations">Dynamically Creating Destinations</h3><p>For the easiest possible configuration with JNDI based programs, there are two dynamic contexts, namely:</p><ul><li><strong><code>dynamicQueues</code></strong></li><li><strong><code>dynamicTopics</code></strong></li></ul><p>These allow you to lookup queues and topics using JNDI without any configuration.</p><p>For example, if you use the following name to lookup into JNDI:</p><plain-text-body>dynamicQueues/FOO.BAR
-</plain-text-body><p>you will get back an <strong><code>ActiveMQQueue</code></strong> of the name <strong><code>FOO.BAR</code></strong>. This can be very handy if you can easily reconfigure the JNDI name to use to lookup something in JNDI, but don't want to have to double configure a <strong><code>jndi.properties</code></strong> to match.</p><h3 id="JNDISupport-WorkingWithEmbeddedBrokers">Working With Embedded Brokers</h3><p>It is often useful to use an embedded broker in the same JVM as the JMS client. For this see <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a>.</p><p>If you want to use an embedded broker with your JNDI provider you can just use the <a shape="rect" href="vm-transport-reference.xml">VM Transport</a> to connect to the broker in your URL. e.g. to create a purely in JVM broker use this URI</p><plain-text-body>vm://locahost
+</plain-text-body></td></tr></tbody></table><p>If ActiveMQ is embedded within an EJB container, you will need to look at the containers documentation for the correct JNDI values.</p><h3>Dynamically Creating Destinations</h3><p>For the easiest possible configuration with JNDI based programs, there are two dynamic contexts, namely:</p><ul><li><strong><code>dynamicQueues</code></strong></li><li><strong><code>dynamicTopics</code></strong></li></ul><p>These allow you to lookup queues and topics using JNDI without any configuration.</p><p>For example, if you use the following name to lookup into JNDI:</p><plain-text-body>dynamicQueues/FOO.BAR
+</plain-text-body><p>you will get back an <strong><code>ActiveMQQueue</code></strong> of the name <strong><code>FOO.BAR</code></strong>. This can be very handy if you can easily reconfigure the JNDI name to use to lookup something in JNDI, but don't want to have to double configure a <strong><code>jndi.properties</code></strong> to match.</p><h3>Working With Embedded Brokers</h3><p>It is often useful to use an embedded broker in the same JVM as the JMS client. For this see <link><page ri:content-title="How do I embed a Broker inside a Connection"></page></link>.</p><p>If you want to use an embedded broker with your JNDI provider you can just use the <link><page ri:content-title="VM Transport Reference"></page><plain-text-link-body>VM Transport</plain-text-link-body></link> to connect to the broker in your URL. e.g. to create a purely in JVM broker use this URI</p><plain-text-body>vm://locahost
</plain-text-body><p>If you want to customize the broker use something like this:</p><plain-text-body>vm:broker:(tcp://localhost:61616)
-</plain-text-body><p>More options are available in the <a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a></p><h3 id="JNDISupport-ExampleJavaCode">Example Java Code</h3><p>Once you have configured JNDI on the classpath you can run any normal JMS application such as the following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/demo/SimpleProducer.java">example</a>. Notice that the Java code just uses pure JMS APIs and is not in any way ActiveMQ specific</p><parameter ac:name="language">java</parameter><plain-text-body>/**
+</plain-text-body><p>More options are available in the <link><page ri:content-title="VM Transport Reference"></page></link></p><h3>Example Java Code</h3><p>Once you have configured JNDI on the classpath you can run any normal JMS application such as the following <a shape="rect" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/demo/SimpleProducer.java">example</a>. Notice that the Java code just uses pure JMS APIs and is not in any way ActiveMQ specific</p><parameter ac:name="language">java</parameter><plain-text-body>/**
* The SimpleQueueSender class consists only of a main method,
* which sends several messages to a queue.
*
diff --git a/journal-is-already-opened-by-this-application.xml b/journal-is-already-opened-by-this-application.xml
index b03ca81..7b4637c 100644
--- a/journal-is-already-opened-by-this-application.xml
+++ b/journal-is-already-opened-by-this-application.xml
@@ -1,9 +1,8 @@
-<div class="wiki-content maincontent"><h3 id="Journalisalreadyopenedbythisapplication-Error">Error</h3>
+<div class="wiki-content maincontent"><h3>Error</h3>
<p>You get something like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="775cffc6-08c3-4a76-9070-7f6a96b8d64e" ac:name="code" ac:schema-version="1"><plain-text-body>
java.io.IOException: Journal is already opened by this application.
at
org.apache.activeio.journal.active.ControlFile.lock(ControlFile.java:71)
@@ -17,10 +16,9 @@
org.apache.activemq.store.DefaultPersistenceAdapterFactory.createJournal(DefaultPersistenceAdapterFactory.java:198)
at
org.apache.activemq.store.DefaultPersistenceAdapterFactory.getJournal(DefaultPersistenceAdapterFactory.java:134)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="Journalisalreadyopenedbythisapplication-Description">Description</h3>
+<h3>Description</h3>
<p>Each broker needs to have its own directory to store its journal files etc. The error indicates that you have 2 brokers sharing the same files.</p>
@@ -28,8 +26,8 @@
<p>Another cause of this problem is if you are using the vm://localhost style transport in a JMS client with the JMS connection starting before you have initialised your broker. If you create a vm transport connection, it will auto-create a broker if there is not one running already; so you can end up creating 2 brokers by accident. The work around is to make sure that the JMS connection factory you are using depends on the broker you are configuring (e.g. in Spring use a <strong>depends-on</strong> attribute on the connection factory to make it depend on the broker). This will ensure that the broker is initialized first before the connection factory.</p>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Be careful with broker names and URIs</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Make sure you do not use any strange characters in the names of brokers as they are converted to URIs which <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html" rel="nofollow">do not allow things like underscores</a> in them etc.</p></div></div>
+<structured-macro ac:macro-id="04388450-4760-44b0-9ebe-9c4de4a6b01f" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Be careful with broker names and URIs</parameter><rich-text-body>
+<p>Make sure you do not use any strange characters in the names of brokers as they are converted to URIs which <a shape="rect" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html">do not allow things like underscores</a> in them etc.</p></rich-text-body></structured-macro>
-<p>This problem could also be caused by <a shape="rect" href="the-broker-will-not-start.xml">a bad OS and JVM combination</a></p></div>
+<p>This problem could also be caused by <link><page ri:content-title="The Broker will not start"></page><link-body>a bad OS and JVM combination</link-body></link></p></div>
diff --git a/junit-reports.xml b/junit-reports.xml
index e45ede7..6adaaa3 100644
--- a/junit-reports.xml
+++ b/junit-reports.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The latest test reports are visible via the <a shape="rect" class="external-link" href="https://hudson.apache.org/hudson/job/ActiveMQ/">Hudson ActiveMQ continuous integration builds</a></p></div>
+<div class="wiki-content maincontent"><p>The latest test reports are visible via the <a shape="rect" href="https://hudson.apache.org/hudson/job/ActiveMQ/">Hudson ActiveMQ continuous integration builds</a></p></div>
diff --git a/kaha-persistence.xml b/kaha-persistence.xml
index f036e7b..1cacdba 100644
--- a/kaha-persistence.xml
+++ b/kaha-persistence.xml
@@ -1,41 +1,37 @@
-<div class="wiki-content maincontent"><h2 id="KahaPersistence-KahaPersistence">Kaha Persistence</h2>
+<div class="wiki-content maincontent"><h2>Kaha Persistence</h2>
<p>Kaha Peristence is a storage solution written especially for message persistence and is part of the ActiveMQ project. It's tuned to provide optimal performance for typical message usage patterns, which involves writing/reading and discarding messages that are persisted very quickly.</p>
<p>Data stored in Kaha is appended to data logs - the log files are discarded once there is no longer interest in the data contained in the log.</p>
-<h3 id="KahaPersistence-ConfiguringKahaPersistence">Configuring Kaha Persistence</h3>
+<h3>Configuring Kaha Persistence</h3>
<p>In the broker XML specify the persistence adaptor to be Kaha e.g.</p>
<p>ActiveMQ 5.0 and above:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <broker brokerName="broker" persistent="true" useShutdownHook="false">
+<structured-macro ac:macro-id="f1210018-4a80-4011-a088-a6da3b1db3bc" ac:name="code" ac:schema-version="1"><plain-text-body>
+ <broker brokerName="broker" persistent="true" useShutdownHook="false">
<transportConnectors>
- <transportConnector uri="tcp://localhost:61616"/>
+ <transportConnector uri="tcp://localhost:61616"/>
</transportConnectors>
<persistenceAdapter>
- <kahaPersistenceAdapter directory="activemq-data" maxDataFileLength="33554432"/>
+ <kahaPersistenceAdapter directory="activemq-data" maxDataFileLength="33554432"/>
</persistenceAdapter>
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>ActiveMQ 4.1 and earlier:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <broker brokerName="broker" persistent="true" useShutdownHook="false">
+<structured-macro ac:macro-id="a53390c5-5c6b-4155-b84d-be230563faf1" ac:name="code" ac:schema-version="1"><plain-text-body>
+ <broker brokerName="broker" persistent="true" useShutdownHook="false">
<transportConnectors>
- <transportConnector uri="tcp://localhost:61616"/>
+ <transportConnector uri="tcp://localhost:61616"/>
</transportConnectors>
<persistenceAdapter>
- <kahaPersistenceAdapter dir="activemq-data" maxDataFileLength="33554432"/>
+ <kahaPersistenceAdapter dir="activemq-data" maxDataFileLength="33554432"/>
</persistenceAdapter>
</broker>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/kahadb-replication-experimental.xml b/kahadb-replication-experimental.xml
index 0c5b898..0b306d3 100644
--- a/kahadb-replication-experimental.xml
+++ b/kahadb-replication-experimental.xml
@@ -1,3 +1,3 @@
-<div class="wiki-content maincontent"><parameter ac:name="title">Note</parameter><rich-text-body><p>This is under review - and not currently supported.</p></rich-text-body><h2 id="KahaDBReplication(Experimental)-Overview">Overview</h2><p>The new KahaDB store supports a very fast and flexible replication system. It features:</p><ul><li>Journal level replication (The translates into lower overhead to the master to replicate records).</li><li>Support for multiple slaves.</li><li>Support to dynamically add slaves at runtime.</li><li>Uses multiple concurrent data transfer sessions to do an initial slave synchronization.</li><li>Big slave synchronizations can be resumed so synchronization progress is not lost if a slave is restarted.</li><li>A configurable minimum number of replicas allows you to pause processing until the data has been guaranteed to be replicated enough times.</li></ul><h2 id="KahaDBReplication(Experimental)-MasterElection">Master Election</h2><p>KahaDB supports a pluggable Master Election algorithm but the only current implementation is one based on <a shape="rect" class="external-link" href="http://hadoop.apache.org/zookeeper">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 shape="rect" class="external-link" 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><h2 id="KahaDBReplication(Experimental)-ConfiguringaBroker:">Configuring a Broker:</h2><p>The ActiveMQ binary distribution includes a KahaDB HA broker configuration at <strong>$ACTIVEMQ_HOME/conf/ha.xml</strong>.</p><p>It it setup to look for a ZooKeeper 3.0.0 server on localhost at port 2181. Edit the configuration if this is not where you are running your ZooKeeper server.</p><p>Start the configuation up by running:</p><plain-text-body>prompt> $ACTIVEMQ_HOME/bin/activemq xbean:ha.xml
-</plain-text-body><p>The actual contents of the configuration file follows:<plain-text-body>{snippet:lang=xml|id=example|url=activemq/trunk/assembly/src/release/conf/ha.xml}</plain-text-body></p><h2 id="KahaDBReplication(Experimental)-UnderstandingthekahadbReplicationXMLelement">Understanding the kahadbReplication XML element</h2><h3 id="KahaDBReplication(Experimental)-ThebrokerURIAttribute">The brokerURI Attribute</h3><p>Notice that the the brokerURI attribute points at another broker configuration file. The ha-broker.xml contains the actual broker configuration that the broker uses when the node take over as master. The ha-broker.xml configuration file is a standard broker configuration except in these aspects:</p><ul><li>It MUST set the start="false" attribute on the broker element.</li><li>It MUST not configure a persistenceAdapter.</li></ul><p>The above rules allows the replication system to inject the replicated KahaDB store into the Master when it's starting up.</p><h3 id="KahaDBReplication(Experimental)-TheminimumReplicasAttribute">The minimumReplicas Attribute</h3><p>The minimumReplicas specifies how many copies of the database are required before synchronous update operations are deemed successful. Setting this to 0 allows a broker to continue operating even if there are no slaves attached. If the value is set to 1 or greater, and there are no slaves attached, the brokers persistent message processing will be suspended until the minimum number of slaves are attached and the data synchronized.</p><h3 id="KahaDBReplication(Experimental)-TheuriAttribute">The uri Attribute</h3><p>The uri attribute should always be configured with a <strong>kdbr://</strong> based URI. KDBR stands for 'KahaDB Replication' and this is the replication protocol used between the masters and the slaves. The master binds the specified port with slaves subsequently connect to and establish replication sessions. The host name in the uri MUST get updated to the actual machine's host name since this is also used to identify the nodes in the cluster.</p><h3 id="KahaDBReplication(Experimental)-ThedirectoryAttribute">The directory Attribute</h3><p>This is the data directory where the KahaDB will store it's persistence files.</p></div>
+<div class="wiki-content maincontent"><parameter ac:name="title">Note</parameter><rich-text-body><p>This is under review - and not currently supported.</p></rich-text-body><h2>Overview</h2><p>The new KahaDB store supports a very fast and flexible replication system. It features:</p><ul><li>Journal level replication (The translates into lower overhead to the master to replicate records).</li><li>Support for multiple slaves.</li><li>Support to dynamically add slaves at runtime.</li><li>Uses multiple concurrent data transfer sessions to do an initial slave synchronization.</li><li>Big slave synchronizations can be resumed so synchronization progress is not lost if a slave is restarted.</li><li>A configurable minimum number of replicas allows you to pause processing until the data has been guaranteed to be replicated enough times.</li></ul><h2>Master Election</h2><p>KahaDB supports a pluggable Master Election algorithm but the only current implementation is one based on <a shape="rect" href="http://hadoop.apache.org/zookeeper">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 shape="rect" 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><h2>Configuring a Broker:</h2><p>The ActiveMQ binary distribution includes a KahaDB HA broker configuration at <strong>$ACTIVEMQ_HOME/conf/ha.xml</strong>.</p><p>It it setup to look for a ZooKeeper 3.0.0 server on localhost at port 2181. Edit the configuration if this is not where you are running your ZooKeeper server.</p><p>Start the configuation up by running:</p><plain-text-body>prompt> $ACTIVEMQ_HOME/bin/activemq xbean:ha.xml
+</plain-text-body><p>The actual contents of the configuration file follows:<plain-text-body>{snippet:lang=xml|id=example|url=activemq/trunk/assembly/src/release/conf/ha.xml}</plain-text-body></p><h2>Understanding the kahadbReplication XML element</h2><h3>The brokerURI Attribute</h3><p>Notice that the the brokerURI attribute points at another broker configuration file. The ha-broker.xml contains the actual broker configuration that the broker uses when the node take over as master. The ha-broker.xml configuration file is a standard broker configuration except in these aspects:</p><ul><li>It MUST set the start="false" attribute on the broker element.</li><li>It MUST not configure a persistenceAdapter.</li></ul><p>The above rules allows the replication system to inject the replicated KahaDB store into the Master when it's starting up.</p><h3>The minimumReplicas Attribute</h3><p>The minimumReplicas specifies how many copies of the database are required before synchronous update operations are deemed successful. Setting this to 0 allows a broker to continue operating even if there are no slaves attached. If the value is set to 1 or greater, and there are no slaves attached, the brokers persistent message processing will be suspended until the minimum number of slaves are attached and the data synchronized.</p><h3>The uri Attribute</h3><p>The uri attribute should always be configured with a <strong>kdbr://</strong> based URI. KDBR stands for 'KahaDB Replication' and this is the replication protocol used between the masters and the slaves. The master binds the specified port with slaves subsequently connect to and establish replication sessions. The host name in the uri MUST get updated to the actual machine's host name since this is also used to identify the nodes in the cluster.</p><h3>The directory Attribute</h3><p>This is the data directory where the KahaDB will store it's persistence files.</p></div>
diff --git a/kahadb.xml b/kahadb.xml
index 0acef08..2d8f265 100644
--- a/kahadb.xml
+++ b/kahadb.xml
@@ -1,34 +1,27 @@
-<div class="wiki-content maincontent"><p>KahaDB is a file based persistence database that is local to the message broker that is using it. It has been optimized for fast persistence. It is the the default storage mechanism since <strong>ActiveMQ 5.4</strong>. KahaDB uses less file descriptors and provides faster recovery than its predecessor, the <a shape="rect" href="amq-message-store.xml">AMQ Message Store</a>.</p><h2 id="KahaDB-Configuration">Configuration</h2><p>To use KahaDB as the broker's persistence adapter configure ActiveMQ as follows (example):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <broker brokerName="broker">
+<div class="wiki-content maincontent"><p>KahaDB is a file based persistence database that is local to the message broker that is using it. It has been optimized for fast persistence. It is the the default storage mechanism since <strong>ActiveMQ 5.4</strong>. KahaDB uses less file descriptors and provides faster recovery than its predecessor, the <link><page ri:content-title="AMQ Message Store"></page></link>.</p><h2>Configuration</h2><p>To use KahaDB as the broker's persistence adapter configure ActiveMQ as follows (example):</p><structured-macro ac:macro-id="a0af1d7a-4046-45b9-85f4-416664b14042" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body> <broker brokerName="broker">
<persistenceAdapter>
- <kahaDB directory="activemq-data" journalMaxFileLength="32mb"/>
+ <kahaDB directory="activemq-data" journalMaxFileLength="32mb"/>
</persistenceAdapter>
</broker>
-]]></script>
-</div></div><h3 id="KahaDB-KahaDBProperties">KahaDB Properties</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>archiveCorruptedIndex</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, corrupted indexes found at startup will be archived (not deleted).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>archiveDataLogs</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, will move a message data log to the archive directory instead of deleting it.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>checkForCorruptJournalFiles</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, will check for corrupt journal files on startup and try and recover them.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>checkpointInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time (ms) before check-pointing the journal.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>checksumJournalFiles</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Create a checksum for a journal file. The presence of a checksum is required in order for the persistence adapter to be able to detect corrupt journal files.</p><p>Before <strong>ActiveMQ 5.9.0</strong>: the default is <strong><code>false</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cleanupInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The interval (in ms) between consecutive checks that determine which journal files, if any, are eligible for removal from the message store. An eligible journal file is one that has no outstanding references.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>compactAcksAfterNoGC</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>From <strong>ActiveMQ 5.14.0</strong>: when the acknowledgement compaction feature is enabled this value controls how many store GC cycles must be completed with no other files being cleaned up before the compaction logic is triggered to possibly compact older acknowledgements spread across journal files into a new log file.  The lower the value set the faster the compaction may occur which can impact performance if it runs to often.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>compactAcksIgnoresStoreGrowth</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>From <strong>ActiveMQ 5.14.0</strong>: when the acknowledgement compaction feature is enabled this value controls whether compaction is run when the store is still growing or if it should only occur when the store has stopped growing (either due to idle or store limits reached).  If enabled the compaction runs regardless of the store still having room or being active which can decrease overall performance but reclaim space faster. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>concurrentStoreAndDispatchQueues</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enable the dispatching of Queue messages to interested clients to happen concurrently with message storage.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>concurrentStoreAndDispatchTopics</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enable the dispatching of Topic messages to interested clients to happen concurrently with message storage</p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Enabling this property is not recommended.</p></div></div></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>directory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq-data</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The path to the directory to use to store the message store data and log files.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>directoryArchive</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Define the directory to move data logs to when they all the messages they contain have been consumed.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>enableAckCompaction</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>From <strong>ActiveMQ 5.14.0</strong>: this setting controls whether the store will perform periodic compaction of older journal log files that contain only Message acknowledgements. By compacting these older acknowledgements into new journal log files the older files can be removed freeing space and allowing the message store to continue to operate without hitting store size limits.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>enableIndexWriteAsync</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, the index is updated asynchronously.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>enableJournalDiskSyncs</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span>Ensure every journal write is followed by a disk sync (JMS durability requirement).</span></p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This property is deprecated as of <strong>ActiveMQ</strong> <strong>5.14.0</strong>.</p><p>From <strong>ActiveMQ</strong> <strong>5.14.0</strong>: see <span style="color: rgb(34,34,34);"><strong><code>journalDiskSyncStrategy</code></strong>.</span></p></div></div></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ignoreMissingJournalfiles</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong>, reports of missing journal files are ignored.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexCacheSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of index pages cached in memory.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexDirectory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><p><span>From <strong>ActiveMQ 5.10.0</strong>: If set, configures where the KahaDB index files (<strong><code>db.data</code></strong> and <strong><code>db.redo</code></strong>) will be stored. If not set, the index files are stored in the directory specified by the <strong><code>directory</code></strong> attribute.</span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexWriteBatchSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of indexes written in a batch.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code><span>journalDiskSyncInterval</span></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Interval (ms) for when to perform a disk sync when <strong><code>journalDiskSyncStrategy=periodic</code></strong>. A sync will only be performed if a write has occurred to the journal since the last disk sync or when the journal rolls over to a new journal file.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code><span>journalDiskSyncStrategy</span></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>always</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>From <strong>ActiveMQ 5.14.0</strong>: this setting configures the disk sync policy. The list of available sync strategies are (in order of decreasing safety, and increasing performance):</p><ul><li><p><strong><code>always</code></strong> <span>Ensure every journal write is followed by a disk sync (JMS durability requirement). This is the safest option but is also the slowest because it requires a sync after every message write. This is equivalent to the deprecated property <strong><code>enableJournalDiskSyncs=true</code></strong>.</span></p></li><li><p><strong><code>periodic</code></strong> <span style="color: rgb(34,34,34);">The disk will be synced at set intervals (if a write has occurred) instead of after every journal write which will reduce the load on the disk and should improve throughput</span>. The disk will also be synced when rolling over to a new journal file. The default interval is 1 second. The default interval offers very good performance, whilst being safer than <strong><code>never</code></strong> disk syncing, as data loss is limited to a maximum of 1 second's worth. See <strong><code>journalDiskSyncInterval</code></strong> to change the frequency of disk syncs.</p></li><li><p><strong><code>never</code></strong> A sync will never be explicitly called and it will be up to the operating system to flush to disk. This is equivalent to setting the deprecated property <strong><code>enableJournalDiskSyncs=false</code></strong>. This is the fastest option but is the least safe as there's no guarantee as to when data is flushed to disk. Consequently message loss <em>can</em> occur on broker failure.</p></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>journalMaxFileLength</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>32mb</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A hint to set the maximum size of the message data logs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxAsyncJobs</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of asynchronous messages that will be queued awaiting storage (should be the same as the number of concurrent MessageProducers).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>preallocationScope</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>entire_journal</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>From <strong>ActiveMQ 5.14.0</strong>: this setting configures how journal data files are preallocated. The default strategy preallocates the journal file on first use using the appender thread. </p><ul><li><p><strong><code>entire_journal_async</code></strong> will use preallocate ahead of time in a separate thread.</p></li><li><p><strong><code>none</code></strong> disables preallocation.</p></li></ul><p>On SSD, using <strong><code>entire_journal_async</code></strong> avoids delaying writes pending preallocation on first use.</p><p><strong>Note</strong>: on HDD the additional thread contention for disk has a negative impact. Therefore use the default.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>preallocationStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>sparse_file</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>From <strong>ActiveMQ 5.12.0</strong>: This setting configures how the broker will try to preallocate the journal files when a new journal file is needed.</p><ul><li><p><strong><code>sparse_file</code></strong> - sets the file length, but does not populate it with any data.</p></li><li><p><strong><code>os_kernel_copy</code></strong> - delegates the preallocation to the Operating System.</p></li><li><p><strong><code>zeros</code></strong>  - each preallocated journal file contains nothing but <strong><code>0x00</code></strong> throughout.</p></li></ul></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>storeOpenWireVersion</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>11</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Determines the version of OpenWire commands that are marshaled to the KahaDB journal. </p><p>Before <strong>ActiveMQ 5.12.0</strong>: the default value is <strong><code>6</code></strong>.</p><p>Some features of the broker depend on information stored in the OpenWire commands from newer protocol revisions and these may not work correctly if the store version is set to a lower value.  KahaDB stores from broker versions greater than 5.9.0 will in many cases still be readable by the broker but will cause the broker to continue using the older store version meaning newer features may not work as intended. </p><p>For KahaDB stores that were created in versions prior to <strong>ActiveMQ 5.9.0</strong> it will be necessary to manually set <strong><code>storeOpenWireVersion="6"</code></strong> in order to start a broker without error.</p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>For tuning locking properties see the options listed at <a shape="rect" href="pluggable-storage-lockers.xml">Pluggable storage lockers.</a></p></div></div><p> </p><h3 id="KahaDB-SlowFileSystemAccessDiagnosticLogging">Slow File System Access Diagnostic Logging</h3><p>You can configure a non zero threshold in milliseconds for database updates. If database operation is slower than that threshold (for example if you set it to <strong><code>500</code></strong>), you may see messages like:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><code>Slow KahaDB access: cleanup took 1277 | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker</code></p>
-</div></div><p>You can configure a threshold used to log these messages by using a system property and adjust it to your disk speed so that you can easily pick up runtime anomalies.</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><code>-Dorg.apache.activemq.store.kahadb.LOG_SLOW_ACCESS_TIME=1500</code></p>
-</div></div><h1 id="KahaDB-Multi(m)kahaDBPersistenceAdapter">Multi(m) kahaDB Persistence Adapter</h1><p>From <strong>ActiveMQ 5.6</strong>: it's possible to distribute destinations stores across multiple kahdb persistence adapters. When would you do this? If you have one fast producer/consumer destination and another periodic producer destination that has irregular batch consumption then disk usage can grow out of hand as unconsumed messages become distributed across multiple journal files. Having a separate journal for each ensures minimal journal usage. Also, some destination may be critical and require disk synchronization while others may not. In these cases you can use the <strong><code>mKahaDB</code></strong> persistence adapter and filter destinations using wildcards, just like with destination policy entries.</p><h3 id="KahaDB-Transactions">Transactions</h3><p>Transactions can span multiple journals if the destinations are distributed. This means that two phase completion is necessary, which does impose a performance (additional disk sync) penalty to record the commit outcome. This penalty is only imposed if more than one journal is involved in a transaction.</p><h3 id="KahaDB-Configuration.1">Configuration</h3><p>Each instance of <strong><code>kahaDB</code></strong> can be configured independently. If no destination is supplied to a <strong><code>filteredKahaDB</code></strong>, the implicit default value will match any destination, queue or topic. This is a handy catch all. If no matching persistence adapter can be found, destination creation will fail with an exception. The <strong><code>filteredKahaDB</code></strong> shares its wildcard matching rules with <a shape="rect" href="per-destination-policies.xml">Per Destination Policies</a>.</p><p>From ActiveMQ 5.15, <strong><code>filteredKahaDB</code></strong> support a StoreUsage attribute named <strong><code>usage</code></strong>. This allows individual disk limits to be imposed on matching queues.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker brokerName="broker">
+</plain-text-body></structured-macro><h3>KahaDB Properties</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Property</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>archiveCorruptedIndex</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, corrupted indexes found at startup will be archived (not deleted).</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>archiveDataLogs</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, will move a message data log to the archive directory instead of deleting it.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>checkForCorruptJournalFiles</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, will check for corrupt journal files on startup and try and recover them.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>checkpointInterval</code></p></td><td colspan="1" rowspan="1"><p><code>5000</code></p></td><td colspan="1" rowspan="1"><p>Time (ms) before check-pointing the journal.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>checksumJournalFiles</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Create a checksum for a journal file. The presence of a checksum is required in order for the persistence adapter to be able to detect corrupt journal files.</p><p>Before <strong>ActiveMQ 5.9.0</strong>: the default is <strong><code>false</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>cleanupInterval</code></p></td><td colspan="1" rowspan="1"><p><code>30000</code></p></td><td colspan="1" rowspan="1"><p>The interval (in ms) between consecutive checks that determine which journal files, if any, are eligible for removal from the message store. An eligible journal file is one that has no outstanding references.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>compactAcksAfterNoGC</code></p></td><td colspan="1" rowspan="1"><p><code>10</code></p></td><td colspan="1" rowspan="1"><p>From <strong>ActiveMQ 5.14.0</strong>: when the acknowledgement compaction feature is enabled this value controls how many store GC cycles must be completed with no other files being cleaned up before the compaction logic is triggered to possibly compact older acknowledgements spread across journal files into a new log file.  The lower the value set the faster the compaction may occur which can impact performance if it runs to often.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>compactAcksIgnoresStoreGrowth</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>From <strong>ActiveMQ 5.14.0</strong>: when the acknowledgement compaction feature is enabled this value controls whether compaction is run when the store is still growing or if it should only occur when the store has stopped growing (either due to idle or store limits reached).  If enabled the compaction runs regardless of the store still having room or being active which can decrease overall performance but reclaim space faster. </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>concurrentStoreAndDispatchQueues</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Enable the dispatching of Queue messages to interested clients to happen concurrently with message storage.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>concurrentStoreAndDispatchTopics</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Enable the dispatching of Topic messages to interested clients to happen concurrently with message storage</p><structured-macro ac:macro-id="4e4928d2-fe18-4cc6-ad80-1f090b4d82a8" ac:name="warning" ac:schema-version="1"><rich-text-body><p>Enabling this property is not recommended.</p></rich-text-body></structured-macro></td></tr><tr><td colspan="1" rowspan="1"><p><code>directory</code></p></td><td colspan="1" rowspan="1"><p><code>activemq-data</code></p></td><td colspan="1" rowspan="1"><p>The path to the directory to use to store the message store data and log files.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>directoryArchive</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>Define the directory to move data logs to when they all the messages they contain have been consumed.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>enableAckCompaction</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>From <strong>ActiveMQ 5.14.0</strong>: this setting controls whether the store will perform periodic compaction of older journal log files that contain only Message acknowledgements. By compacting these older acknowledgements into new journal log files the older files can be removed freeing space and allowing the message store to continue to operate without hitting store size limits.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>enableIndexWriteAsync</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, the index is updated asynchronously.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>enableJournalDiskSyncs</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p><span>Ensure every journal write is followed by a disk sync (JMS durability requirement).</span></p><structured-macro ac:macro-id="a7c9e966-543c-477f-9948-c3fa4ac1c224" ac:name="warning" ac:schema-version="1"><rich-text-body><p>This property is deprecated as of <strong>ActiveMQ</strong> <strong>5.14.0</strong>.</p><p>From <strong>ActiveMQ</strong> <strong>5.14.0</strong>: see <span style="color: rgb(34,34,34);"><strong><code>journalDiskSyncStrategy</code></strong>.</span></p></rich-text-body></structured-macro></td></tr><tr><td colspan="1" rowspan="1"><p><code>ignoreMissingJournalfiles</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong>, reports of missing journal files are ignored.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexCacheSize</code></p></td><td colspan="1" rowspan="1"><p><code>10000</code></p></td><td colspan="1" rowspan="1"><p>Number of index pages cached in memory.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexDirectory</code></p></td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1"><p><span>From <strong>ActiveMQ 5.10.0</strong>: If set, configures where the KahaDB index files (<strong><code>db.data</code></strong> and <strong><code>db.redo</code></strong>) will be stored. If not set, the index files are stored in the directory specified by the <strong><code>directory</code></strong> attribute.</span></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexWriteBatchSize</code></p></td><td colspan="1" rowspan="1"><p><code>1000</code></p></td><td colspan="1" rowspan="1"><p>Number of indexes written in a batch.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code><span>journalDiskSyncInterval</span></code></p></td><td colspan="1" rowspan="1"><p><code>1000</code></p></td><td colspan="1" rowspan="1"><p>Interval (ms) for when to perform a disk sync when <strong><code>journalDiskSyncStrategy=periodic</code></strong>. A sync will only be performed if a write has occurred to the journal since the last disk sync or when the journal rolls over to a new journal file.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code><span>journalDiskSyncStrategy</span></code></p></td><td colspan="1" rowspan="1"><p><code>always</code></p></td><td colspan="1" rowspan="1"><p>From <strong>ActiveMQ 5.14.0</strong>: this setting configures the disk sync policy. The list of available sync strategies are (in order of decreasing safety, and increasing performance):</p><ul><li><p><strong><code>always</code></strong> <span>Ensure every journal write is followed by a disk sync (JMS durability requirement). This is the safest option but is also the slowest because it requires a sync after every message write. This is equivalent to the deprecated property <strong><code>enableJournalDiskSyncs=true</code></strong>.</span></p></li><li><p><strong><code>periodic</code></strong> <span style="color: rgb(34,34,34);">The disk will be synced at set intervals (if a write has occurred) instead of after every journal write which will reduce the load on the disk and should improve throughput</span>. The disk will also be synced when rolling over to a new journal file. The default interval is 1 second. The default interval offers very good performance, whilst being safer than <strong><code>never</code></strong> disk syncing, as data loss is limited to a maximum of 1 second's worth. See <strong><code>journalDiskSyncInterval</code></strong> to change the frequency of disk syncs.</p></li><li><p><strong><code>never</code></strong> A sync will never be explicitly called and it will be up to the operating system to flush to disk. This is equivalent to setting the deprecated property <strong><code>enableJournalDiskSyncs=false</code></strong>. This is the fastest option but is the least safe as there's no guarantee as to when data is flushed to disk. Consequently message loss <em>can</em> occur on broker failure.</p></li></ul></td></tr><tr><td colspan="1" rowspan="1"><p><code>journalMaxFileLength</code></p></td><td colspan="1" rowspan="1"><p><code>32mb</code></p></td><td colspan="1" rowspan="1"><p>A hint to set the maximum size of the message data logs.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxAsyncJobs</code></p></td><td colspan="1" rowspan="1"><p><code>10000</code></p></td><td colspan="1" rowspan="1"><p>The maximum number of asynchronous messages that will be queued awaiting storage (should be the same as the number of concurrent MessageProducers).</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>preallocationScope</code></p></td><td colspan="1" rowspan="1"><p><code>entire_journal</code></p></td><td colspan="1" rowspan="1"><p>From <strong>ActiveMQ 5.14.0</strong>: this setting configures how journal data files are preallocated. The default strategy preallocates the journal file on first use using the appender thread. </p><ul><li><p><strong><code>entire_journal_async</code></strong> will use preallocate ahead of time in a separate thread.</p></li><li><p><strong><code>none</code></strong> disables preallocation.</p></li></ul><p>On SSD, using <strong><code>entire_journal_async</code></strong> avoids delaying writes pending preallocation on first use.</p><p><strong>Note</strong>: on HDD the additional thread contention for disk has a negative impact. Therefore use the default.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>preallocationStrategy</code></p></td><td colspan="1" rowspan="1"><p><code>sparse_file</code></p></td><td colspan="1" rowspan="1"><p>From <strong>ActiveMQ 5.12.0</strong>: This setting configures how the broker will try to preallocate the journal files when a new journal file is needed.</p><ul><li><p><strong><code>sparse_file</code></strong> - sets the file length, but does not populate it with any data.</p></li><li><p><strong><code>os_kernel_copy</code></strong> - delegates the preallocation to the Operating System.</p></li><li><p><strong><code>zeros</code></strong>  - each preallocated journal file contains nothing but <strong><code>0x00</code></strong> throughout.</p></li></ul></td></tr><tr><td colspan="1" rowspan="1"><p><code>storeOpenWireVersion</code></p></td><td colspan="1" rowspan="1"><p><code>11</code></p></td><td colspan="1" rowspan="1"><p>Determines the version of OpenWire commands that are marshaled to the KahaDB journal. </p><p>Before <strong>ActiveMQ 5.12.0</strong>: the default value is <strong><code>6</code></strong>.</p><p>Some features of the broker depend on information stored in the OpenWire commands from newer protocol revisions and these may not work correctly if the store version is set to a lower value.  KahaDB stores from broker versions greater than 5.9.0 will in many cases still be readable by the broker but will cause the broker to continue using the older store version meaning newer features may not work as intended. </p><p>For KahaDB stores that were created in versions prior to <strong>ActiveMQ 5.9.0</strong> it will be necessary to manually set <strong><code>storeOpenWireVersion="6"</code></strong> in order to start a broker without error.</p></td></tr></tbody></table><structured-macro ac:macro-id="476ef0cf-45ca-4c53-a5ab-0647f124b076" ac:name="info" ac:schema-version="1"><rich-text-body><p>For tuning locking properties see the options listed at <link><page ri:content-title="Pluggable storage lockers"></page><plain-text-link-body>Pluggable storage lockers.</plain-text-link-body></link></p></rich-text-body></structured-macro><p> </p><h3>Slow File System Access Diagnostic Logging</h3><p>You can configure a non zero threshold in milliseconds for database updates. If database operation is slower than that threshold (for example if you set it to <strong><code>500</code></strong>), you may see messages like:</p><structured-macro ac:macro-id="a5de5cad-c071-444d-8715-af3cc04de0da" ac:name="panel" ac:schema-version="1"><rich-text-body><p><code>Slow KahaDB access: cleanup took 1277 | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker</code></p></rich-text-body></structured-macro><p>You can configure a threshold used to log these messages by using a system property and adjust it to your disk speed so that you can easily pick up runtime anomalies.</p><structured-macro ac:macro-id="ab3467ef-2fbe-425b-a490-3f4b35e3efe9" ac:name="panel" ac:schema-version="1"><rich-text-body><p><code>-Dorg.apache.activemq.store.kahadb.LOG_SLOW_ACCESS_TIME=1500</code></p></rich-text-body></structured-macro><h1>Multi(m) kahaDB Persistence Adapter</h1><p>From <strong>ActiveMQ 5.6</strong>: it's possible to distribute destinations stores across multiple kahdb persistence adapters. When would you do this? If you have one fast producer/consumer destination and another periodic producer destination that has irregular batch consumption then disk usage can grow out of hand as unconsumed messages become distributed across multiple journal files. Having a separate journal for each ensures minimal journal usage. Also, some destination may be critical and require disk synchronization while others may not. In these cases you can use the <strong><code>mKahaDB</code></strong> persistence adapter and filter destinations using wildcards, just like with destination policy entries.</p><h3>Transactions</h3><p>Transactions can span multiple journals if the destinations are distributed. This means that two phase completion is necessary, which does impose a performance (additional disk sync) penalty to record the commit outcome. This penalty is only imposed if more than one journal is involved in a transaction.</p><h3>Configuration</h3><p>Each instance of <strong><code>kahaDB</code></strong> can be configured independently. If no destination is supplied to a <strong><code>filteredKahaDB</code></strong>, the implicit default value will match any destination, queue or topic. This is a handy catch all. If no matching persistence adapter can be found, destination creation will fail with an exception. The <strong><code>filteredKahaDB</code></strong> shares its wildcard matching rules with <link><page ri:content-title="Per Destination Policies"></page></link>.</p><p>From ActiveMQ 5.15, <strong><code>filteredKahaDB</code></strong> support a StoreUsage attribute named <strong><code>usage</code></strong>. This allows individual disk limits to be imposed on matching queues.</p><structured-macro ac:macro-id="c93a5072-2518-4272-aabd-abc2404ef483" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><broker brokerName="broker">
- <persistenceAdapter>
- <mKahaDB directory="${activemq.base}/data/kahadb">
+ <persistenceAdapter>
+ <mKahaDB directory="${activemq.base}/data/kahadb">
<filteredPersistenceAdapters>
<!-- match all queues -->
- <filteredKahaDB queue=">">
+ <filteredKahaDB queue=">">
<usage>
- <storeUsage limit="1g" />
+ <storeUsage limit="1g" />
</usage>
<persistenceAdapter>
- <kahaDB journalMaxFileLength="32mb"/>
+ <kahaDB journalMaxFileLength="32mb"/>
</persistenceAdapter>
</filteredKahaDB>
<!-- match all destinations -->
<filteredKahaDB>
<persistenceAdapter>
- <kahaDB enableJournalDiskSyncs="false"/>
+ <kahaDB enableJournalDiskSyncs="false"/>
</persistenceAdapter>
</filteredKahaDB>
</filteredPersistenceAdapters>
@@ -36,17 +29,15 @@
</persistenceAdapter>
</broker>
-]]></script>
-</div></div><h3 id="KahaDB-AutomaticPerDestinationPersistenceAdapter">Automatic Per Destination Persistence Adapter</h3><p>Set <strong><code>perDestination="true"</code></strong> on the catch all, i.e., when no explicit destination is set, <strong><code>filteredKahaDB</code></strong> entry. Each matching destination will be assigned its own <strong><code>kahaDB</code></strong> instance.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker brokerName="broker">
+</plain-text-body></structured-macro><h3>Automatic Per Destination Persistence Adapter</h3><p>Set <strong><code>perDestination="true"</code></strong> on the catch all, i.e., when no explicit destination is set, <strong><code>filteredKahaDB</code></strong> entry. Each matching destination will be assigned its own <strong><code>kahaDB</code></strong> instance.</p><structured-macro ac:macro-id="5ac58703-9a86-478c-97e4-e9ac828cc113" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><broker brokerName="broker">
- <persistenceAdapter>
- <mKahaDB directory="${activemq.base}/data/kahadb">
+ <persistenceAdapter>
+ <mKahaDB directory="${activemq.base}/data/kahadb">
<filteredPersistenceAdapters>
<!-- kahaDB per destinations -->
- <filteredKahaDB perDestination="true">
+ <filteredKahaDB perDestination="true">
<persistenceAdapter>
- <kahaDB journalMaxFileLength="32mb"/>
+ <kahaDB journalMaxFileLength="32mb"/>
</persistenceAdapter>
</filteredKahaDB>
</filteredPersistenceAdapters>
@@ -54,6 +45,5 @@
</persistenceAdapter>
</broker>
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Specifying both <strong><code>perDestination="true"</code></strong> <em>and</em> <strong><code>queue=">"</code></strong> on the same <strong><code>filteredKahaDB</code></strong> entry has not been tested. It <em> may</em> result in the following exception being raised:</p><p><code>Reason: java.io.IOException: File '/opt/java/apache-activemq-5.9.0/data/mKahaDB/lock' could not be locked as lock is already held for this jvm</code></p></div></div></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="efcc5f10-3f89-42e4-8573-cda652359bac" ac:name="info" ac:schema-version="1"><rich-text-body><p>Specifying both <strong><code>perDestination="true"</code></strong> <em>and</em> <strong><code>queue=">"</code></strong> on the same <strong><code>filteredKahaDB</code></strong> entry has not been tested. It <em> may</em> result in the following exception being raised:</p><p><code>Reason: java.io.IOException: File '/opt/java/apache-activemq-5.9.0/data/mKahaDB/lock' could not be locked as lock is already held for this jvm</code></p></rich-text-body></structured-macro></div>
diff --git a/known-bad-os-and-jvm-combinations.xml b/known-bad-os-and-jvm-combinations.xml
index b5b1aa4..dd188bc 100644
--- a/known-bad-os-and-jvm-combinations.xml
+++ b/known-bad-os-and-jvm-combinations.xml
@@ -1,3 +1,4 @@
<div class="wiki-content maincontent">
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Operating System</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Java Virtual Machine</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Problem description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Red Hat Linux Advanced Server release 2.1AS (Pensacola) kernel 2.4.9-e.62smp</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>j2sdk1.4.0_01</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Broker could not start up due to error with journal</p></td></tr></tbody></table></div></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Operating System</p></th><th colspan="1" rowspan="1"><p>Java Virtual Machine</p></th><th colspan="1" rowspan="1"><p>Problem description</p></th></tr><tr><td colspan="1" rowspan="1"><p>Red Hat Linux Advanced Server release 2.1AS (Pensacola) kernel 2.4.9-e.62smp</p></td><td colspan="1" rowspan="1"><p>j2sdk1.4.0_01</p></td><td colspan="1" rowspan="1"><p>Broker could not start up due to error with journal</p></td></tr></tbody></table>
+</div>
diff --git a/ldap-broker-discovery-mechanism.xml b/ldap-broker-discovery-mechanism.xml
index 47d7294..8655f45 100644
--- a/ldap-broker-discovery-mechanism.xml
+++ b/ldap-broker-discovery-mechanism.xml
@@ -1,76 +1,51 @@
<div class="wiki-content maincontent"><p>Configuring network topologies can be quite tedious when the number of brokers in the system is large. To help ease the configuration overhead for these types of situations, a broker can be configured to look up its broker connections using a LDAP v3 directory server.</p>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Note</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>The basic feature was added to satisfy <span style="text-decoration: line-through;"><a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ-358">AMQ-358</a></span>. There are known problems and limitations with this implementation. These deficiencies have been addressed in <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ-1587">AMQ-1587</a>. The features discussed on this page require the patch attached to JIRA issue <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ-1587">AMQ-1587</a>. This patch should apply cleanly to the ActiveMQ 5.0.0 release or the current development trunk.</p></div></div>
+<structured-macro ac:macro-id="a427293d-0b2e-4268-92e2-8d6aad9fa8a3" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Note</parameter><rich-text-body>
+<p>The basic feature was added to satisfy <span style="text-decoration: line-through;"><a shape="rect" href="https://issues.apache.org/activemq/browse/AMQ-358">AMQ-358</a></span>. There are known problems and limitations with this implementation. These deficiencies have been addressed in <a shape="rect" href="https://issues.apache.org/activemq/browse/AMQ-1587">AMQ-1587</a>. The features discussed on this page require the patch attached to JIRA issue <a shape="rect" href="https://issues.apache.org/activemq/browse/AMQ-1587">AMQ-1587</a>. This patch should apply cleanly to the ActiveMQ 5.0.0 release or the current development trunk.</p></rich-text-body></structured-macro>
-<h2 id="LDAPBrokerDiscoveryMechanism-LDAPv3DirectoryServerCompliance">LDAP v3 Directory Server Compliance</h2>
+<h2>LDAP v3 Directory Server Compliance</h2>
-<p>The following table lists a known subset of directory servers and their compliance to work with the LDAP discovery feature. Most LDAP v3 directory servers will support this feature if they properly implement the <a shape="rect" class="external-link" href="http://www.ietf.org/rfc/rfc2307.txt" rel="nofollow">RFC2307</a> schemas. In order to support the persistent search capabilities the server must implement the extension defined in <a shape="rect" class="external-link" href="http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-ldapext-psearch-03.txt" rel="nofollow">draft-ietf-ldapext-psearch-03.txt</a>.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Vendor </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Product </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> <a shape="rect" class="external-link" href="http://www.ietf.org/rfc/rfc2307.txt" rel="nofollow">RFC2307</a> </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> <a shape="rect" class="external-link" href="http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-ldapext-psearch-03.txt" rel="nofollow">draft-ietf-ldapext-psearch-03.txt</a> </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> ApacheDS </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.0.x </p></td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></div>
- </td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></div>
- </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Microsoft </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Active Directory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Windows 2000 <br clear="none" class="atl-forced-newline">
-Windows 2003 </p></td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-warning" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/warning.png" data-emoticon-name="warning" alt="(warning)"></div>
- </td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-cross" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/error.png" data-emoticon-name="cross" alt="(error)"></div>
- </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Microsoft </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Active Directory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Windows 2003 R2 </p></td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></div>
- </td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-cross" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/error.png" data-emoticon-name="cross" alt="(error)"></div>
- </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Sun </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> OpenDS </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0.9.x </p></td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></div>
- </td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></div>
- </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> OpenLDAP </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> OpenLDAP </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 2.3.x <br clear="none" class="atl-forced-newline">
-2.4.x </p></td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></div>
- </td><td colspan="1" rowspan="1" class="confluenceTd">
-<div class="cfm-align-center" style="text-align: center;"><img class="emoticon emoticon-cross" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/error.png" data-emoticon-name="cross" alt="(error)"></div>
- </td></tr></tbody></table></div>
+<p>The following table lists a known subset of directory servers and their compliance to work with the LDAP discovery feature. Most LDAP v3 directory servers will support this feature if they properly implement the <a shape="rect" href="http://www.ietf.org/rfc/rfc2307.txt">RFC2307</a> schemas. In order to support the persistent search capabilities the server must implement the extension defined in <a shape="rect" href="http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-ldapext-psearch-03.txt">draft-ietf-ldapext-psearch-03.txt</a>.</p>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Vendor </p></th><th colspan="1" rowspan="1"><p> Product </p></th><th colspan="1" rowspan="1"><p> Version </p></th><th colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.ietf.org/rfc/rfc2307.txt">RFC2307</a> </p></th><th colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-ldapext-psearch-03.txt">draft-ietf-ldapext-psearch-03.txt</a> </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache </p></td><td colspan="1" rowspan="1"><p> ApacheDS </p></td><td colspan="1" rowspan="1"><p> 1.0.x </p></td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="753b737b-68f8-4f04-8e20-24ee5df10c28" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="tick"></emoticon></rich-text-body></structured-macro> </td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="75eeb37f-8cde-434b-a7ac-336f8355fc45" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="tick"></emoticon></rich-text-body></structured-macro> </td></tr><tr><td colspan="1" rowspan="1"><p> Microsoft </p></td><td colspan="1" rowspan="1"><p> Active Directory </p></td><td colspan="1" rowspan="1"><p> Windows 2000 <br clear="none" class="atl-forced-newline">
+Windows 2003 </p></td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="99755497-54df-4641-bc37-d65c40c4a94a" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="warning"></emoticon></rich-text-body></structured-macro> </td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="bfc77587-566e-4a55-810c-b3d21a4517f8" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="cross"></emoticon></rich-text-body></structured-macro> </td></tr><tr><td colspan="1" rowspan="1"><p> Microsoft </p></td><td colspan="1" rowspan="1"><p> Active Directory </p></td><td colspan="1" rowspan="1"><p> Windows 2003 R2 </p></td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="2a2ef9b4-240a-4ed8-acfd-f76aa4f5a41b" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="tick"></emoticon></rich-text-body></structured-macro> </td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="06af8861-aedf-481a-a354-d84aa9e7247f" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="cross"></emoticon></rich-text-body></structured-macro> </td></tr><tr><td colspan="1" rowspan="1"><p> Sun </p></td><td colspan="1" rowspan="1"><p> OpenDS </p></td><td colspan="1" rowspan="1"><p> 0.9.x </p></td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="1076701b-fc3e-4674-9c82-ca56e0af1144" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="tick"></emoticon></rich-text-body></structured-macro> </td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="46fa0e57-7082-47c7-98bc-b4b7fd1c67de" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="tick"></emoticon></rich-text-body></structured-macro> </td></tr><tr><td colspan="1" rowspan="1"><p> OpenLDAP </p></td><td colspan="1" rowspan="1"><p> OpenLDAP </p></td><td colspan="1" rowspan="1"><p> 2.3.x <br clear="none" class="atl-forced-newline">
+2.4.x </p></td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="bf789dde-30f1-47f2-a50c-3a688f61230c" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="tick"></emoticon></rich-text-body></structured-macro> </td><td colspan="1" rowspan="1"> <structured-macro ac:macro-id="1b3c8833-380a-4766-82aa-1939c194ab94" ac:name="center" ac:schema-version="1"><rich-text-body><emoticon ac:name="cross"></emoticon></rich-text-body></structured-macro> </td></tr></tbody></table>
-<p><img class="emoticon emoticon-warning" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/warning.png" data-emoticon-name="warning" alt="(warning)"> LDAP v3 directory server which do not support <a shape="rect" class="external-link" href="http://www.ietf.org/rfc/rfc2307.txt" rel="nofollow">RFC2307</a> by default. Support can be added by manually importing them. See vendor specific setup requirements on how to do this.<br clear="none">
-<img class="emoticon emoticon-cross" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/error.png" data-emoticon-name="cross" alt="(error)"> LDAP v3 directory servers which do not support the <a shape="rect" class="external-link" href="http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-ldapext-psearch-03.txt" rel="nofollow">draft-ietf-ldapext-psearch-03.txt</a>.</p>
+<p><emoticon ac:name="warning"></emoticon> LDAP v3 directory server which do not support <a shape="rect" href="http://www.ietf.org/rfc/rfc2307.txt">RFC2307</a> by default. Support can be added by manually importing them. See vendor specific setup requirements on how to do this.<br clear="none">
+<emoticon ac:name="cross"></emoticon> LDAP v3 directory servers which do not support the <a shape="rect" href="http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-ldapext-psearch-03.txt">draft-ietf-ldapext-psearch-03.txt</a>.</p>
-<h2 id="LDAPBrokerDiscoveryMechanism-LDAPNetworkConnectorProperties">LDAP Network Connector Properties</h2>
+<h2>LDAP Network Connector Properties</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Required </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> uri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Yes</strong> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The URI of the LDAP v3 Server to connect to (i.e. ldap://host:port, failover://(ldap://host1:port,ldap://host2:port). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> base </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Yes</strong> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The RDN base used as the root for the search criteria. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> user </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Yes</strong>, if not using anonymousAuthentication </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The username needed to bind to the server. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Yes</strong>, if not using anonymousAuthentication </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The password needed to bind to the server. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> anonymousAuthentication </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <strong>Yes</strong>, if not using user/password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Enable if you want to bind to the server anonymously. This is recommended over using user/password properties since your login credentials will not be stored in an unencrypted XML file. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> searchEventListener </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Enable if you want the broker to stay in sync with changes made to entries matching the search criteria. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> searchScope </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> ONELEVEL_SCOPE </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Can be any of search scopes defined by javax.naming.directory.SearchControls class. <br clear="none" class="atl-forced-newline">
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Required </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> uri </p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> <strong>Yes</strong> </p></td><td colspan="1" rowspan="1"><p> The URI of the LDAP v3 Server to connect to (i.e. ldap://host:port, failover://(ldap://host1:port,ldap://host2:port). </p></td></tr><tr><td colspan="1" rowspan="1"><p> base </p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> <strong>Yes</strong> </p></td><td colspan="1" rowspan="1"><p> The RDN base used as the root for the search criteria. </p></td></tr><tr><td colspan="1" rowspan="1"><p> user </p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> <strong>Yes</strong>, if not using anonymousAuthentication </p></td><td colspan="1" rowspan="1"><p> The username needed to bind to the server. </p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> <strong>Yes</strong>, if not using anonymousAuthentication </p></td><td colspan="1" rowspan="1"><p> The password needed to bind to the server. </p></td></tr><tr><td colspan="1" rowspan="1"><p> anonymousAuthentication </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> <strong>Yes</strong>, if not using user/password </p></td><td colspan="1" rowspan="1"><p> Enable if you want to bind to the server anonymously. This is recommended over using user/password properties since your login credentials will not be stored in an unencrypted XML file. </p></td></tr><tr><td colspan="1" rowspan="1"><p> searchEventListener </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> No </p></td><td colspan="1" rowspan="1"><p> Enable if you want the broker to stay in sync with changes made to entries matching the search criteria. </p></td></tr><tr><td colspan="1" rowspan="1"><p> searchScope </p></td><td colspan="1" rowspan="1"><p> ONELEVEL_SCOPE </p></td><td colspan="1" rowspan="1"><p> No </p></td><td colspan="1" rowspan="1"><p> Can be any of search scopes defined by javax.naming.directory.SearchControls class. <br clear="none" class="atl-forced-newline">
OBJECT_SCOPE - search the named object defined by base. <br clear="none" class="atl-forced-newline">
ONELEVEL_SCOPE - search one level of the base. <br clear="none" class="atl-forced-newline">
- SUBTREE_SCOPE - search entire subtree rooted at the base. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> searchFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (&(objectClass=ipHost)(objectClass=ipService)) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> No </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Can be any filter that conforms to <a shape="rect" class="external-link" href="http://www.ietf.org/rfc/rfc2254.txt" rel="nofollow">RFC2254</a>. If a custom one is specified the actual search filter used will be (&(&(objectClass=ipHost)(objectClass=ipService))(USER CUSTOM)) </p></td></tr></tbody></table></div>
+ SUBTREE_SCOPE - search entire subtree rooted at the base. </p></td></tr><tr><td colspan="1" rowspan="1"><p> searchFilter </p></td><td colspan="1" rowspan="1"><p> (&(objectClass=ipHost)(objectClass=ipService)) </p></td><td colspan="1" rowspan="1"><p> No </p></td><td colspan="1" rowspan="1"><p> Can be any filter that conforms to <a shape="rect" href="http://www.ietf.org/rfc/rfc2254.txt">RFC2254</a>. If a custom one is specified the actual search filter used will be (&(&(objectClass=ipHost)(objectClass=ipService))(USER CUSTOM)) </p></td></tr></tbody></table>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Other Properties</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>All of the properties defined in <a shape="rect" class="external-link" href="http://activemq.apache.org/networks-of-brokers.html">Networks of Brokers</a> are also available to the ldapNetworkConnector. Any of the properties defined for a normal networkConnector will be used as connection parameters to any discovered brokers matching the search criteria.</p></div></div>
+<structured-macro ac:macro-id="28339d06-babf-4416-be4a-ce171185c755" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Other Properties</parameter><rich-text-body>
+<p>All of the properties defined in <a shape="rect" href="http://activemq.apache.org/networks-of-brokers.html">Networks of Brokers</a> are also available to the ldapNetworkConnector. Any of the properties defined for a normal networkConnector will be used as connection parameters to any discovered brokers matching the search criteria.</p></rich-text-body></structured-macro>
-<h2 id="LDAPBrokerDiscoveryMechanism-Example1:SimpleNetworkofBrokers">Example 1: Simple Network of Brokers</h2>
-
-<div class="cfm-align-center" style="text-align: center;">
-<h3 id="LDAPBrokerDiscoveryMechanism-NetworkConfiguration">Network Configuration</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Topology </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>LDAP v3 Directory Structure</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Entry</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="ldap-broker-discovery-mechanism.data/Example1-Topology.jpg" data-image-src="/confluence/download/attachments/77126/Example1-Topology.jpg?version=4&modificationDate=1203881427000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59671452" data-linked-resource-version="4" data-linked-resource-type="attachment" data-linked-resource-default-alias="Example1-Topology.jpg" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="77126" data-linked-resource-container-version="21"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="ldap-broker-discovery-mechanism.data/Example1-DirectoryStructure.jpg" data-image-src="/confluence/download/attachments/77126/Example1-DirectoryStructure.jpg?version=1&modificationDate=1203881557000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59671497" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Example1-DirectoryStructure.jpg" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="77126" data-linked-resource-container-version="21"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="ldap-broker-discovery-mechanism.data/Example1-Entry.jpg" data-image-src="/confluence/download/attachments/77126/Example1-Entry.jpg?version=1&modificationDate=1203881408000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59671496" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Example1-Entry.jpg" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="77126" data-linked-resource-container-version="21"></span></p></td></tr></tbody></table></div>
+<h2>Example 1: Simple Network of Brokers</h2>
+<structured-macro ac:macro-id="2ba452b0-259d-462c-a82c-c21d12695445" ac:name="center" ac:schema-version="1"><rich-text-body>
+<h3>Network Configuration</h3>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Topology </p></th><th colspan="1" rowspan="1"><p>LDAP v3 Directory Structure</p></th><th colspan="1" rowspan="1"><p>Entry</p></th></tr><tr><td colspan="1" rowspan="1"><p><image><attachment ri:filename="Example1-Topology.jpg"></attachment></image></p></td><td colspan="1" rowspan="1"><p><image><attachment ri:filename="Example1-DirectoryStructure.jpg"></attachment></image></p></td><td colspan="1" rowspan="1"><p><image><attachment ri:filename="Example1-Entry.jpg"></attachment></image></p></td></tr></tbody></table>
-<h3 id="LDAPBrokerDiscoveryMechanism-ActiveMQConfiguration(activemq.xml)">ActiveMQ Configuration (activemq.xml)</h3></div>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>srv-a.mydomain.com</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker brokerName="srv-a.mydomain.com" ...>
+<h3>ActiveMQ Configuration (activemq.xml)</h3></rich-text-body></structured-macro>
+<structured-macro ac:macro-id="c2087f81-3628-461b-badf-a57819ee0219" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">srv-a.mydomain.com</parameter><plain-text-body>
+<broker brokerName="srv-a.mydomain.com" ...>
...
<networkConnectors>
- <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"
- base="dc=brokers,dc=mydomain,dc=com"
- anonymousAuthentication="true"
- searchFilter="(cn=*)"
- searchScope="SUBTREE_SCOPE"
+ <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"
+ base="dc=brokers,dc=mydomain,dc=com"
+ anonymousAuthentication="true"
+ searchFilter="(cn=*)"
+ searchScope="SUBTREE_SCOPE"
/>
</networkConnectors>
...
</broker>
-]]></script>
-</div></div>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>srv-b.mydomain.com</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker brokerName="srv-b.mydomain.com" ...>
+</plain-text-body></structured-macro>
+<structured-macro ac:macro-id="a7e01047-93ed-43e5-adb8-3643dc1192bd" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">srv-b.mydomain.com</parameter><plain-text-body>
+<broker brokerName="srv-b.mydomain.com" ...>
...
<networkConnectors/>
@@ -79,58 +54,50 @@
...
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="LDAPBrokerDiscoveryMechanism-Example2:LargerNetworkofBrokers">Example 2: Larger Network of Brokers</h2>
-
-<div class="cfm-align-center" style="text-align: center;">
-<h3 id="LDAPBrokerDiscoveryMechanism-NetworkConfiguration.1">Network Configuration</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Topology </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>LDAP v3 Directory Structure</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="ldap-broker-discovery-mechanism.data/Example2-Topology.jpg" data-image-src="/confluence/download/attachments/77126/Example2-Topology.jpg?version=2&modificationDate=1203881712000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59671455" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="Example2-Topology.jpg" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="77126" data-linked-resource-container-version="21"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="ldap-broker-discovery-mechanism.data/Example2-DirectoryStructure.jpg" data-image-src="/confluence/download/attachments/77126/Example2-DirectoryStructure.jpg?version=1&modificationDate=1203882106000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59671498" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Example2-DirectoryStructure.jpg" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="77126" data-linked-resource-container-version="21"></span></p></td></tr></tbody></table></div>
+<h2>Example 2: Larger Network of Brokers</h2>
+<structured-macro ac:macro-id="808671ba-f099-4d44-92a2-0e089dcb7809" ac:name="center" ac:schema-version="1"><rich-text-body>
+<h3>Network Configuration</h3>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Topology </p></th><th colspan="1" rowspan="1"><p>LDAP v3 Directory Structure</p></th></tr><tr><td colspan="1" rowspan="1"><p><image><attachment ri:filename="Example2-Topology.jpg"></attachment></image></p></td><td colspan="1" rowspan="1"><p><image><attachment ri:filename="Example2-DirectoryStructure.jpg"></attachment></image></p></td></tr></tbody></table>
-<h3 id="LDAPBrokerDiscoveryMechanism-ActiveMQConfiguration(activemq.xml).1">ActiveMQ Configuration (activemq.xml)</h3></div>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>srv-a.mydomain.com</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker brokerName="srv-a.mydomain.com" ...>
+<h3>ActiveMQ Configuration (activemq.xml)</h3></rich-text-body></structured-macro>
+<structured-macro ac:macro-id="f91be329-8554-4135-bef1-0c8b93c5c6e4" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">srv-a.mydomain.com</parameter><plain-text-body>
+<broker brokerName="srv-a.mydomain.com" ...>
...
<networkConnectors>
- <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"
- base="dc=brokers-for-srv-a,dc=mydomain,dc=com"
- anonymousAuthentication="true"
- searchFilter="(cn=*)"
- searchScope="SUBTREE_SCOPE"
- networkTTL="2"
+ <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"
+ base="dc=brokers-for-srv-a,dc=mydomain,dc=com"
+ anonymousAuthentication="true"
+ searchFilter="(cn=*)"
+ searchScope="SUBTREE_SCOPE"
+ networkTTL="2"
/>
<!-- networkTTL=2 since we want messages to flow from srv-a to srv-c -->
</networkConnectors>
...
</broker>
-]]></script>
-</div></div>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>srv-b.mydomain.com</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker brokerName="srv-b.mydomain.com" ...>
+</plain-text-body></structured-macro>
+<structured-macro ac:macro-id="7f686481-2d28-4f23-ad44-af7bfe3b14fe" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">srv-b.mydomain.com</parameter><plain-text-body>
+<broker brokerName="srv-b.mydomain.com" ...>
...
<networkConnectors/>
- <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"
- base="dc=brokers-other,dc=mydomain,dc=com"
- anonymousAuthentication="true"
- searchFilter="(cn=*)"
- searchScope="SUBTREE_SCOPE"
+ <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"
+ base="dc=brokers-other,dc=mydomain,dc=com"
+ anonymousAuthentication="true"
+ searchFilter="(cn=*)"
+ searchScope="SUBTREE_SCOPE"
/>
</networkConnectors>
...
</broker>
-]]></script>
-</div></div>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>srv-c.mydomain.com</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker brokerName="srv-c.mydomain.com" ...>
+</plain-text-body></structured-macro>
+<structured-macro ac:macro-id="e3f54c10-ecca-4470-aa05-ba87834c7177" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">srv-c.mydomain.com</parameter><plain-text-body>
+<broker brokerName="srv-c.mydomain.com" ...>
...
<networkConnectors/>
@@ -139,24 +106,21 @@
...
</broker>
-]]></script>
-</div></div>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>srv-d.mydomain.com</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker brokerName="srv-d.mydomain.com" ...>
+</plain-text-body></structured-macro>
+<structured-macro ac:macro-id="4c53b2b9-48d8-44a4-a8fe-736fcfe3392b" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">srv-d.mydomain.com</parameter><plain-text-body>
+<broker brokerName="srv-d.mydomain.com" ...>
...
<networkConnectors/>
- <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"
- base="dc=brokers-other,dc=mydomain,dc=com"
- anonymousAuthentication="true"
- searchFilter="(cn=*)"
- searchScope="SUBTREE_SCOPE"
+ <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"
+ base="dc=brokers-other,dc=mydomain,dc=com"
+ anonymousAuthentication="true"
+ searchFilter="(cn=*)"
+ searchScope="SUBTREE_SCOPE"
/>
</networkConnectors>
...
</broker>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/leveldb-store.xml b/leveldb-store.xml
index 5e9f228..89627b9 100644
--- a/leveldb-store.xml
+++ b/leveldb-store.xml
@@ -1,11 +1,9 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The LevelDB store has been deprecated and is no longer supported or recommended for use. The recommended store is <a shape="rect" href="kahadb.xml">KahaDB</a></p></div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Version Compatibility</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Available in ActiveMQ 5.8.0 and newer</p></div></div><p>The LevelDB Store is a file based persistence database that is local to the message broker that is using it. It has been optimized to provide even faster persistence than KahaDB. It's similar to KahahDB but instead of using a custom B-Tree implementation to index the write ahead logs, it uses <a shape="rect" class="external-link" href="https://code.google.com/p/leveldb/" rel="nofollow">LevelDB</a> based indexes which have several nice properties due to the 'append only' files access patterns :</p><ul><li>Fast updates (No need to do random disk updates)</li><li>Concurrent reads</li><li>Fast index snapshots using hard links</li></ul><p>Both KahaDB and the LevelDB store have to do periodic garbage collection cycles to determine which log files can deleted. In the case of KahaDB, this can be quite expensive as you increase the amount of data stored and can cause read/write stalls while the collection occurs. The LevelDB store uses a much cheaper algorithm to determine when log files can be collected and avoids those stalls.</p><h2 id="LevelDBStore-Configuration">Configuration</h2><p>You can configure ActiveMQ to use LevelDB for its persistence adapter - like below :</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <broker brokerName="broker" ... >
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="835b8a22-754e-4802-be3d-f79767a2fd2c" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>The LevelDB store has been deprecated and is no longer supported or recommended for use. The recommended store is <link><page ri:content-title="KahaDB"></page></link></p></rich-text-body></structured-macro><structured-macro ac:macro-id="4241afc9-4931-47c2-a2a5-6bd1bd1f3e90" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Version Compatibility</parameter><rich-text-body><p>Available in ActiveMQ 5.8.0 and newer</p></rich-text-body></structured-macro><p>The LevelDB Store is a file based persistence database that is local to the message broker that is using it. It has been optimized to provide even faster persistence than KahaDB. It's similar to KahahDB but instead of using a custom B-Tree implementation to index the write ahead logs, it uses <a shape="rect" href="https://code.google.com/p/leveldb/">LevelDB</a> based indexes which have several nice properties due to the 'append only' files access patterns :</p><ul><li>Fast updates (No need to do random disk updates)</li><li>Concurrent reads</li><li>Fast index snapshots using hard links</li></ul><p>Both KahaDB and the LevelDB store have to do periodic garbage collection cycles to determine which log files can deleted. In the case of KahaDB, this can be quite expensive as you increase the amount of data stored and can cause read/write stalls while the collection occurs. The LevelDB store uses a much cheaper algorithm to determine when log files can be collected and avoids those stalls.</p><h2>Configuration</h2><p>You can configure ActiveMQ to use LevelDB for its persistence adapter - like below :</p><structured-macro ac:macro-id="bc167008-ff01-4629-b82f-c04e071d6683" ac:name="code" ac:schema-version="1"><plain-text-body> <broker brokerName="broker" ... >
...
<persistenceAdapter>
- <levelDB directory="activemq-data"/>
+ <levelDB directory="activemq-data"/>
</persistenceAdapter>
...
</broker>
-]]></script>
-</div></div><h3 id="LevelDBStore-LevelDBProperties">LevelDB Properties</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>directory</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>"LevelDB"</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The directory which the store will use to hold it's data files. The store will create the directory if it does not already exist.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sync</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If set to false, then the store does not sync logging operations to disk</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>104857600 (100 MB)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The max size (in bytes) of each data log file before log file rotation occurs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>verifyChecksums</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Set to true to force checksum verification of all data that is read from the file system.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>paranoidChecks</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Make the store error out as soon as possible if it detects internal corruption.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexFactory</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>org.fusesource.leveldbjni.JniDBFactory, org.iq80.leveldb.impl.Iq80DBFactory</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The factory classes to use when creating the LevelDB indexes</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexMaxOpenFiles</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of open files that can be used by the index.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexBlockRestartInterval</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>16</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number keys between restart points for delta encoding of keys.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexWriteBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>6291456 (6 MB)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Amount of index data to build up in memory before converting to a sorted on-disk file.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexBlockSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>4096 (4 K)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The size of index data packed per block.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexCacheSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>268435456 (256 MB)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum amount of off-heap memory to use to cache index blocks.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>indexCompression</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>snappy</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The type of compression to apply to the index blocks. Can be snappy or none.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logCompression</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>none</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The type of compression to apply to the log records. Can be snappy or none.</p></td></tr></tbody></table></div><p>For tuning locking properties please take a look at <a shape="rect" href="pluggable-storage-lockers.xml">Pluggable storage lockers</a></p><h2 id="LevelDBStore-AlsoSee">Also See</h2><ul><li><a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a> An extended version of this store which self replicates to other broker nodes to increase message availability.</li></ul></div>
+</plain-text-body></structured-macro><h3>LevelDB Properties</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1"><p>directory</p></td><td colspan="1" rowspan="1"><p>"LevelDB"</p></td><td colspan="1" rowspan="1"><p>The directory which the store will use to hold it's data files. The store will create the directory if it does not already exist.</p></td></tr><tr><td colspan="1" rowspan="1"><p>sync</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If set to false, then the store does not sync logging operations to disk</p></td></tr><tr><td colspan="1" rowspan="1"><p>logSize</p></td><td colspan="1" rowspan="1"><p>104857600 (100 MB)</p></td><td colspan="1" rowspan="1"><p>The max size (in bytes) of each data log file before log file rotation occurs.</p></td></tr><tr><td colspan="1" rowspan="1"><p>verifyChecksums</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Set to true to force checksum verification of all data that is read from the file system.</p></td></tr><tr><td colspan="1" rowspan="1"><p>paranoidChecks</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Make the store error out as soon as possible if it detects internal corruption.</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexFactory</p></td><td colspan="1" rowspan="1"><p>org.fusesource.leveldbjni.JniDBFactory, org.iq80.leveldb.impl.Iq80DBFactory</p></td><td colspan="1" rowspan="1"><p>The factory classes to use when creating the LevelDB indexes</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexMaxOpenFiles</p></td><td colspan="1" rowspan="1"><p>1000</p></td><td colspan="1" rowspan="1"><p>Number of open files that can be used by the index.</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexBlockRestartInterval</p></td><td colspan="1" rowspan="1"><p>16</p></td><td colspan="1" rowspan="1"><p>Number keys between restart points for delta encoding of keys.</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexWriteBufferSize</p></td><td colspan="1" rowspan="1"><p>6291456 (6 MB)</p></td><td colspan="1" rowspan="1"><p>Amount of index data to build up in memory before converting to a sorted on-disk file.</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexBlockSize</p></td><td colspan="1" rowspan="1"><p>4096 (4 K)</p></td><td colspan="1" rowspan="1"><p>The size of index data packed per block.</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexCacheSize</p></td><td colspan="1" rowspan="1"><p>268435456 (256 MB)</p></td><td colspan="1" rowspan="1"><p>The maximum amount of off-heap memory to use to cache index blocks.</p></td></tr><tr><td colspan="1" rowspan="1"><p>indexCompression</p></td><td colspan="1" rowspan="1"><p>snappy</p></td><td colspan="1" rowspan="1"><p>The type of compression to apply to the index blocks. Can be snappy or none.</p></td></tr><tr><td colspan="1" rowspan="1"><p>logCompression</p></td><td colspan="1" rowspan="1"><p>none</p></td><td colspan="1" rowspan="1"><p>The type of compression to apply to the log records. Can be snappy or none.</p></td></tr></tbody></table><p>For tuning locking properties please take a look at <link><page ri:content-title="Pluggable storage lockers"></page></link></p><h2>Also See</h2><ul><li><link><page ri:content-title="Replicated LevelDB Store"></page></link> An extended version of this store which self replicates to other broker nodes to increase message availability.</li></ul></div>
diff --git a/life-cycle.xml b/life-cycle.xml
index db2409d..008d9ac 100644
--- a/life-cycle.xml
+++ b/life-cycle.xml
@@ -1,36 +1,31 @@
-<div class="wiki-content maincontent"><h2 id="LifeCycle-LifecycleofChannels">Life cycle of Channels</h2>
+<div class="wiki-content maincontent"><h2>Life cycle of Channels</h2>
<p>Blaze Channels are in one of five states:</p>
-<h3 id="LifeCycle-Constructed-theChannelisn'tinitializedorhasbeenshutDown">Constructed - the Channel isn't initialized or has been shutDown</h3>
+<h3>Constructed - the Channel isn't initialized or has been shutDown</h3>
-<h3 id="LifeCycle-initialized-">initialized - </h3>
+<h3>initialized - </h3>
<p> you can explicitly initialize a Channel by invoking its init() method. At this point its Configuration is set</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4cf10daf-4687-4230-9b72-42f430b54a68" ac:name="code" ac:schema-version="1"><plain-text-body>
BlazeChannelFactory factory = new BlazeChannelFactory();
BlazeChannel channel = factory.createChannel();
channel.init();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="LifeCycle-started-">started - </h3>
+<h3>started - </h3>
<p> this will implicitly initialize the channel and start the Channel's underlying communication with its peers:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4b16db1d-9359-4600-8d74-4fc58d51bec0" ac:name="code" ac:schema-version="1"><plain-text-body>
BlazeChannelFactory factory = new BlazeChannelFactory();
BlazeChannel channel = factory.createChannel();
channel.start();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="LifeCycle-stopped-">stopped - </h3>
+<h3>stopped - </h3>
<p> this will stop communication - however you are able to re-start the channel at a latter point</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="268ac83c-3aac-47ec-a2bb-82fb9c7ef9e6" ac:name="code" ac:schema-version="1"><plain-text-body>
BlazeChannelFactory factory = new BlazeChannelFactory();
BlazeChannel channel = factory.createChannel();
channel.stop();
@@ -38,22 +33,19 @@
...
//re-start
channel.start();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="LifeCycle-shutdown">shut down</h3>
+<h3>shut down</h3>
<ul class="alternate"><li>this will implicitly call stop() - and de-construct the channel. It is possible to re-initialize the channel again - and it is recommend that to apply configuration changes to the channel - it be shut down and re-started - e.g.</li></ul>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="55b98ba8-4a80-4e63-a194-c7293ce12552" ac:name="code" ac:schema-version="1"><plain-text-body>
BlazeChannelFactory factory = new BlazeChannelFactory();
BlazeChannel channel = factory.createChannel();
channel.shutDown();
// change the congiguration
- channel.getConfiguration().setBroadcastURI("tcp://localhost:60661");
+ channel.getConfiguration().setBroadcastURI("tcp://localhost:60661");
//re-start
channel.start();
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/load-testing-with-camel.xml b/load-testing-with-camel.xml
index c82c345..5791516 100644
--- a/load-testing-with-camel.xml
+++ b/load-testing-with-camel.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="LoadTestingwithCamel-LoadTestingwithCamel">Load Testing with Camel</h2>
+<div class="wiki-content maincontent"><h2>Load Testing with Camel</h2>
<p>It is preferable at the time of writing to check out the source of ActiveMQ and Camel and perform local builds first.</p>
@@ -6,11 +6,9 @@
<p>Now to run a load test type</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b1dce596-fa06-41a0-8d09-7759435d21d7" ac:name="code" ac:schema-version="1"><plain-text-body>
activemq/activemq-camel-loadtest> mvn test -Dtest=LocalBrokerParallelProducerLoadTest
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>If you want to tinker with the configuration of ActiveMQ and Camel then edit the LocalBrokerParallelProducerLoadTest-context.xml file.</p></div>
diff --git a/log4j-warn-no-appenders-could-be-found-for-logger.xml b/log4j-warn-no-appenders-could-be-found-for-logger.xml
index ba66911..e302b6b 100644
--- a/log4j-warn-no-appenders-could-be-found-for-logger.xml
+++ b/log4j-warn-no-appenders-could-be-found-for-logger.xml
@@ -1,14 +1,12 @@
-<div class="wiki-content maincontent"><h2 id="log4j-WARNNoappenderscouldbefoundforlogger-Error">Error</h2>
+<div class="wiki-content maincontent"><h2>Error</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c4664765-80a4-4619-a4d4-ce6c8df38398" ac:name="code" ac:schema-version="1"><plain-text-body>
log4j:WARN No appenders could be found for logger
(org.activemq.transport.tcp.TcpTransportChannel).
log4j:WARN Please initialize the log4j system properly.
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="log4j-WARNNoappenderscouldbefoundforlogger-Solution">Solution</h2>
+<h2>Solution</h2>
-<p>You have not initialised log4j properly. Try reading the <a shape="rect" class="external-link" href="http://logging.apache.org/log4j/docs/manual.html">online log4j manual</a> or by adding a log4j.properties file to your classpath (to a directory which is on the classpath to be precise).</p></div>
+<p>You have not initialised log4j properly. Try reading the <a shape="rect" href="http://logging.apache.org/log4j/docs/manual.html">online log4j manual</a> or by adding a log4j.properties file to your classpath (to a directory which is on the classpath to be precise).</p></div>
diff --git a/logging-a-warning-if-you-forget-to-start-a-connection.xml b/logging-a-warning-if-you-forget-to-start-a-connection.xml
index 7b6bf4f..4491747 100644
--- a/logging-a-warning-if-you-forget-to-start-a-connection.xml
+++ b/logging-a-warning-if-you-forget-to-start-a-connection.xml
@@ -1,8 +1,9 @@
-<div class="wiki-content maincontent"><h2 id="LoggingawarningifyouforgettostartaConnection-LoggingawarningifyouforgettostartaConnection">Logging a warning if you forget to start a Connection</h2>
+<div class="wiki-content maincontent"><h2>Logging a warning if you forget to start a Connection</h2>
-<p>A <em>very</em> common gotcha when working with JMS is forgetting to start the JMS connection, creating a consumer and not having it receive any messages. I myself have tripped up over this one many many times! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>A <em>very</em> common gotcha when working with JMS is forgetting to start the JMS connection, creating a consumer and not having it receive any messages. I myself have tripped up over this one many many times! <emoticon ac:name="smile"></emoticon></p>
-<p>To try and help diagnose this mistake and give you an early warning by default ActiveMQ 4.2 detects this and generates a handy warning message telling you to call the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#start()" rel="nofollow">Connection.start() method</a> on the JMS connection.</p>
+<p>To try and help diagnose this mistake and give you an early warning by default ActiveMQ 4.2 detects this and generates a handy warning message telling you to call the <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#start()">Connection.start() method</a> on the JMS connection.</p>
-<p>For more details on <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ-1253">this feature</a> see the discussion of the <strong>warnAboutUnstartedConnectionTimeout</strong> property on the <a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a></p></div>
+<p>For more details on <a shape="rect" href="https://issues.apache.org/activemq/browse/AMQ-1253">this feature</a> see the discussion of the <strong>warnAboutUnstartedConnectionTimeout</strong> property on the <link><page ri:content-title="Connection Configuration URI"></page></link></p>
+</div>
diff --git a/logging-interceptor.xml b/logging-interceptor.xml
index 0175cb9..d22f999 100644
--- a/logging-interceptor.xml
+++ b/logging-interceptor.xml
@@ -1,22 +1,20 @@
-<div class="wiki-content maincontent"><h2 id="LoggingInterceptor-LoggingInterceptor">Logging Interceptor</h2><p>The Logging Interceptor is a pretty trivial <a shape="rect" href="interceptors.xml">Interceptor</a> which just logs to <a shape="rect" class="external-link" href="http://jakarta.apache.org/commons/logging/">Jakarta Commons Logging</a> or <a shape="rect" class="external-link" href="http://logging.apache.org/log4j/docs/">log4j</a> as messages are sent or acknowledged on a broker.</p><p>The default logging level used is <strong>INFO</strong>. If you want to increase/reduce the logging you can use <a shape="rect" href="how-do-i-change-the-logging.xml">change it via commons logging or log4j</a>.</p><p>As of version 5.3 the logging Interceptor is more configurable. The idea is to log all events but be able to turn off logging for certain event groups by configuration.</p><p>Currently the following groups are supported:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p><strong>Attribute</strong></p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><strong>Description</strong></p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><strong>Default Value</strong></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logAll</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Log all Events</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logConnectionEvents</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Events related to connections and sessions</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logTransactionEvents</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Events related to transaction handling</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logConsumerEvents</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Events related to consuming messages</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logProducerEvents</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Events related to producing messages</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logInternalEvents</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Events normally not of Interest for users like failover, querying internal objects etc</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>logSessionEvents</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Events related to adding and removing sessions</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td></tr></tbody></table></div><p>Only connection events logging is enabled by default.</p><p>You can enable the logging interceptor using the following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/util/plugin-broker.xml">XML configuration</a>. This example enables all logging and disables the connection event logging:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans
- xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="false" persistent="false" xmlns="http://activemq.apache.org/schema/core">
+<div class="wiki-content maincontent"><h2>Logging Interceptor</h2><p>The Logging Interceptor is a pretty trivial <link><page ri:content-title="Interceptors"></page><plain-text-link-body>Interceptor</plain-text-link-body></link> which just logs to <a shape="rect" href="http://jakarta.apache.org/commons/logging/">Jakarta Commons Logging</a> or <a shape="rect" href="http://logging.apache.org/log4j/docs/">log4j</a> as messages are sent or acknowledged on a broker.</p><p>The default logging level used is <strong>INFO</strong>. If you want to increase/reduce the logging you can use <link><page ri:content-title="How do I change the logging"></page><plain-text-link-body>change it via commons logging or log4j</plain-text-link-body></link>.</p><p>As of version 5.3 the logging Interceptor is more configurable. The idea is to log all events but be able to turn off logging for certain event groups by configuration.</p><p>Currently the following groups are supported:</p><table><tbody><tr><th colspan="1" rowspan="1"><p><strong>Attribute</strong></p></th><th colspan="1" rowspan="1"><p><strong>Description</strong></p></th><th colspan="1" rowspan="1"><p><strong>Default Value</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p>logAll</p></td><td colspan="1" rowspan="1"><p>Log all Events</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>logConnectionEvents</p></td><td colspan="1" rowspan="1"><p>Events related to connections and sessions</p></td><td colspan="1" rowspan="1"><p>true</p></td></tr><tr><td colspan="1" rowspan="1"><p>logTransactionEvents</p></td><td colspan="1" rowspan="1"><p>Events related to transaction handling</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>logConsumerEvents</p></td><td colspan="1" rowspan="1"><p>Events related to consuming messages</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>logProducerEvents</p></td><td colspan="1" rowspan="1"><p>Events related to producing messages</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>logInternalEvents</p></td><td colspan="1" rowspan="1"><p>Events normally not of Interest for users like failover, querying internal objects etc</p></td><td colspan="1" rowspan="1"><p>false</p></td></tr><tr><td colspan="1" rowspan="1"><p>logSessionEvents</p></td><td colspan="1" rowspan="1"><p>Events related to adding and removing sessions</p></td><td colspan="1" rowspan="1"><p>true</p></td></tr></tbody></table><p>Only connection events logging is enabled by default.</p><p>You can enable the logging interceptor using the following <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/util/plugin-broker.xml">XML configuration</a>. This example enables all logging and disables the connection event logging:</p><structured-macro ac:macro-id="79ddd82e-0753-4eaf-87e4-2f3d0904296c" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><beans
+ xmlns="http://www.springframework.org/schema/beans"
+ xmlns:amq="http://activemq.apache.org/schema/core"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+ http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <broker useJmx="false" persistent="false" xmlns="http://activemq.apache.org/schema/core">
<plugins>
<!-- lets enable detailed logging in the broker but ignore ConnectionEvents -->
- <loggingBrokerPlugin logAll="true" logConnectionEvents="false"/>
+ <loggingBrokerPlugin logAll="true" logConnectionEvents="false"/>
- <timeStampingBrokerPlugin zeroExpirationOverride="1000" ttlCeiling="60000" futureOnly="true"/>
+ <timeStampingBrokerPlugin zeroExpirationOverride="1000" ttlCeiling="60000" futureOnly="true"/>
<traceBrokerPathPlugin/>
</plugins>
</broker>
-</beans>]]></script>
-</div></div></div>
+</beans></plain-text-body></structured-macro></div>
diff --git a/mailing-lists.xml b/mailing-lists.xml
index 9e1119a..a87aec0 100644
--- a/mailing-lists.xml
+++ b/mailing-lists.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The following mailing lists are available. Before posting you might want to read the <a shape="rect" href="tips-for-getting-help.xml">Tips for getting help</a>.</p><h2 id="MailingLists-ApacheMailingLists">Apache Mailing Lists</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>List Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Subscribe</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Unsubscribe</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Archive</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Nabble (Online Forums)</p></th><th colspan="1" rowspan="1" class="confluenceTh">MarkMail (searchable via UI)</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>ActiveMQ User List</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:users-subscribe@activemq.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:users-unsubscribe@activemq.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://mail-archives.apache.org/mod_mbox/activemq-users/">Archive</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="user-forum.xml">Nabble</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://activemq-users.markmail.org/" rel="nofollow">ActiveMQ Users</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>ActiveMQ Developer List</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:dev-subscribe@activemq.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:dev-unsubscribe@activemq.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://mail-archives.apache.org/mod_mbox/activemq-dev/">Archive</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="developer-forum.xml">Nabble</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://activemq-dev.markmail.org/" rel="nofollow">ActiveMQ Dev</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>ActiveMQ SCM List</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:commits-subscribe@activemq.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:commits-unsubscribe@activemq.apache.org" rel="nofollow">Unsubscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://mail-archives.apache.org/mod_mbox/activemq-commits/">Archive</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://activemq-commits.markmail.org/" rel="nofollow">ActiveMQ SCM</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>ActiveMQ Issues List</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:issues-subscribe@activemq.apache.org" rel="nofollow">Subscribe</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:issues-unsubscribe@activemq.apache.org" rel="nofollow">Unsubscribe</a><a shape="rect" class="external-link" href="mailto:commits-unsubscribe@activemq.apache.org" rel="nofollow" style="text-decoration: underline;"></a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://mail-archives.apache.org/mod_mbox/activemq-issues/">Archive</a><a shape="rect" class="external-link" href="http://mail-archives.apache.org/mod_mbox/activemq-commits/" style="text-decoration: underline;"></a></p></td><td colspan="1" rowspan="1" class="confluenceTd"> </td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://activemq-issues.markmail.org/" rel="nofollow">ActiveMQ Issues</a></td></tr></tbody></table></div><h3 id="MailingLists-DiscussionForums">Discussion Forums</h3><p>If you prefer you could use our <a shape="rect" href="discussion-forums.xml">Discussion Forums</a> which are sync'd with the above mailing lists.</p></div>
+<div class="wiki-content maincontent"><p>The following mailing lists are available. Before posting you might want to read the <link><page ri:content-title="Tips for getting help"></page></link>.</p><h2>Apache Mailing Lists</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>List Name</p></th><th colspan="1" rowspan="1"><p>Subscribe</p></th><th colspan="1" rowspan="1"><p>Unsubscribe</p></th><th colspan="1" rowspan="1"><p>Archive</p></th><th colspan="1" rowspan="1"><p>Nabble (Online Forums)</p></th><th colspan="1" rowspan="1">MarkMail (searchable via UI)</th></tr><tr><td colspan="1" rowspan="1"><p>ActiveMQ User List</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:users-subscribe@activemq.apache.org">Subscribe</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:users-unsubscribe@activemq.apache.org">Unsubscribe</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://mail-archives.apache.org/mod_mbox/activemq-users/">Archive</a></p></td><td colspan="1" rowspan="1"><p><link><page ri:content-title="User Forum"></page><plain-text-link-body>Nabble</plain-text-link-body></link></p></td><td colspan="1" rowspan="1"><a shape="rect" href="http://activemq-users.markmail.org/">ActiveMQ Users</a></td></tr><tr><td colspan="1" rowspan="1"><p>ActiveMQ Developer List</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:dev-subscribe@activemq.apache.org">Subscribe</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:dev-unsubscribe@activemq.apache.org">Unsubscribe</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://mail-archives.apache.org/mod_mbox/activemq-dev/">Archive</a></p></td><td colspan="1" rowspan="1"><p><link><page ri:content-title="Developer Forum"></page><plain-text-link-body>Nabble</plain-text-link-body></link></p></td><td colspan="1" rowspan="1"><a shape="rect" href="http://activemq-dev.markmail.org/">ActiveMQ Dev</a></td></tr><tr><td colspan="1" rowspan="1"><p>ActiveMQ SCM List</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:commits-subscribe@activemq.apache.org">Subscribe</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:commits-unsubscribe@activemq.apache.org">Unsubscribe</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://mail-archives.apache.org/mod_mbox/activemq-commits/">Archive</a></p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><a shape="rect" href="http://activemq-commits.markmail.org/">ActiveMQ SCM</a></td></tr><tr><td colspan="1" rowspan="1"><p>ActiveMQ Issues List</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:issues-subscribe@activemq.apache.org">Subscribe</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:issues-unsubscribe@activemq.apache.org">Unsubscribe</a><a shape="rect" href="mailto:commits-unsubscribe@activemq.apache.org" style="text-decoration: underline;"></a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://mail-archives.apache.org/mod_mbox/activemq-issues/">Archive</a><a shape="rect" href="http://mail-archives.apache.org/mod_mbox/activemq-commits/" style="text-decoration: underline;"></a></p></td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1"><a shape="rect" href="http://activemq-issues.markmail.org/">ActiveMQ Issues</a></td></tr></tbody></table><h3>Discussion Forums</h3><p>If you prefer you could use our <link><page ri:content-title="Discussion Forums"></page></link> which are sync'd with the above mailing lists.</p></div>
diff --git a/manage-durable-subscribers.xml b/manage-durable-subscribers.xml
index eb8cd7a..3f7e284 100644
--- a/manage-durable-subscribers.xml
+++ b/manage-durable-subscribers.xml
@@ -1,31 +1,27 @@
-<div class="wiki-content maincontent"><p><a shape="rect" href="how-do-durable-queues-and-topics-work.xml">Durable topic subscribers</a> that are offline for a long period of time are usually not desired in the system. The reason for that is that broker needs to keep all the messages sent to those topics for the said subscribers. And this message piling can over time exhaust broker store limits for example and lead to the overall slowdown of the system.</p>
+<div class="wiki-content maincontent"><p><link><page ri:content-title="how do durable queues and topics work"></page><link-body>Durable topic subscribers</link-body></link> that are offline for a long period of time are usually not desired in the system. The reason for that is that broker needs to keep all the messages sent to those topics for the said subscribers. And this message piling can over time exhaust broker store limits for example and lead to the overall slowdown of the system.</p>
-<p>You can always manually unsubscribe inactive durable subscriber using management tools like <a shape="rect" href="jmx.xml">JConsole</a> or <a shape="rect" href="web-console.xml">Web Console</a>, but clearly there's more that can be done to help manage systems that use durable subscribers (perhaps coming from environments that they don't control) </p>
+<p>You can always manually unsubscribe inactive durable subscriber using management tools like <link><page ri:content-title="JMX"></page><link-body>JConsole</link-body></link> or <link><page ri:content-title="Web Console"></page></link>, but clearly there's more that can be done to help manage systems that use durable subscribers (perhaps coming from environments that they don't control) </p>
<p>Staring with version 5.6 we introduced a few improvements in this area.</p>
-<h3 id="ManageDurableSubscribers-Expiringmessages">Expiring messages</h3>
+<h3>Expiring messages</h3>
-<p>Some applications send message with specified time to live. If those messages are kept on the broker for the offline durable subscriber we need to remove them when they reach their expiry time. Just as we do with queues, now we check for those messages every 30 seconds by default, which can be tuned with the appropriate <a shape="rect" href="per-destination-policies.xml">destination policy</a>. For example, the following entry</p>
+<p>Some applications send message with specified time to live. If those messages are kept on the broker for the offline durable subscriber we need to remove them when they reach their expiry time. Just as we do with queues, now we check for those messages every 30 seconds by default, which can be tuned with the appropriate <link><page ri:content-title="Per Destination Policies"></page><link-body>destination policy</link-body></link>. For example, the following entry</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<policyEntry topic=">" expireMessagesPeriod="300000"/>]]></script>
-</div></div>
+<structured-macro ac:macro-id="557bd2f0-c204-4fa3-909e-97e2891d3442" ac:name="code" ac:schema-version="1"><plain-text-body><policyEntry topic=">" expireMessagesPeriod="300000"/></plain-text-body></structured-macro>
<p>will configure the broker to check for expired messages every 5 minutes.</p>
-<h3 id="ManageDurableSubscribers-Removinginactivesubscribers">Removing inactive subscribers</h3>
+<h3>Removing inactive subscribers</h3>
<p>The other thing we can do is to automatically unsubscribe durable subscribers that are not active for some period of time. For that purpose we introduced two new broker properties:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>offlineDurableSubscriberTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Amount of time (in milliseconds) after which we remove inactive durable subs. Default -1, means don't remove them</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>offlineDurableSubscriberTaskSchedule</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>300000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>How often we check (in milliseconds)</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>property</p></th><th colspan="1" rowspan="1"><p>default</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>offlineDurableSubscriberTimeout</p></td><td colspan="1" rowspan="1"><p>-1</p></td><td colspan="1" rowspan="1"><p>Amount of time (in milliseconds) after which we remove inactive durable subs. Default -1, means don't remove them</p></td></tr><tr><td colspan="1" rowspan="1"><p>offlineDurableSubscriberTaskSchedule</p></td><td colspan="1" rowspan="1"><p>300000</p></td><td colspan="1" rowspan="1"><p>How often we check (in milliseconds)</p></td></tr></tbody></table>
<p>An example configuration could look like</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker name="localhost" offlineDurableSubscriberTimeout="86400000" offlineDurableSubscriberTaskSchedule="3600000">]]></script>
-</div></div>
+<structured-macro ac:macro-id="11fbff41-33b8-4d9e-b8f7-3dcd3a3c8aae" ac:name="code" ac:schema-version="1"><plain-text-body><broker name="localhost" offlineDurableSubscriberTimeout="86400000" offlineDurableSubscriberTaskSchedule="3600000"></plain-text-body></structured-macro>
<p>which means that we check every hour and remove subscriber that has been offline for a day.</p></div>
diff --git a/masterslave.xml b/masterslave.xml
index 3232da0..0537847 100644
--- a/masterslave.xml
+++ b/masterslave.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="MasterSlave-IntroductiontoMaster/Slave">Introduction to Master / Slave</h2>
+<div class="wiki-content maincontent"><h2>Introduction to Master / Slave</h2>
<p>The following are the different kinds of Master/Slave configurations available:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Master Slave Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Requirements </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Pros </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Cons </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="shared-file-system-master-slave.xml">Shared File System Master Slave</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A shared file system such as a SAN </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Run as many slaves as required. Automatic recovery of old masters </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Requires shared file system </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="jdbc-master-slave.xml">JDBC Master Slave</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> A Shared database </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Run as many slaves as required. Automatic recovery of old masters </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Requires a shared database. Also relatively slow as it cannot use the high performance journal </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> ZooKeeper Server </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Run as many slaves as required. Automatic recovery of old masters. Very fast. </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Requires a ZooKeeper server. </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Master Slave Type </p></th><th colspan="1" rowspan="1"><p> Requirements </p></th><th colspan="1" rowspan="1"><p> Pros </p></th><th colspan="1" rowspan="1"><p> Cons </p></th></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Shared File System Master Slave"></page></link> </p></td><td colspan="1" rowspan="1"><p> A shared file system such as a SAN </p></td><td colspan="1" rowspan="1"><p> Run as many slaves as required. Automatic recovery of old masters </p></td><td colspan="1" rowspan="1"><p> Requires shared file system </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="JDBC Master Slave"></page></link> </p></td><td colspan="1" rowspan="1"><p> A Shared database </p></td><td colspan="1" rowspan="1"><p> Run as many slaves as required. Automatic recovery of old masters </p></td><td colspan="1" rowspan="1"><p> Requires a shared database. Also relatively slow as it cannot use the high performance journal </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Replicated LevelDB Store"></page></link> </p></td><td colspan="1" rowspan="1"><p> ZooKeeper Server </p></td><td colspan="1" rowspan="1"><p> Run as many slaves as required. Automatic recovery of old masters. Very fast. </p></td><td colspan="1" rowspan="1"><p> Requires a ZooKeeper server. </p></td></tr></tbody></table>
-<p>If you are using a shared network file system such as a SAN we recommend a <a shape="rect" href="shared-file-system-master-slave.xml">Shared File System Master Slave</a>. If you are happy to dispense with the high performance journal and are using pure JDBC as your persistence engine then you should use <a shape="rect" href="jdbc-master-slave.xml">JDBC Master Slave</a> instead. For those willing to try out new tech, the <a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a> gives speeds similar to a SAN solution without the hassle of having to setup a highly available shared file system.</p></div>
+<p>If you are using a shared network file system such as a SAN we recommend a <link><page ri:content-title="Shared File System Master Slave"></page></link>. If you are happy to dispense with the high performance journal and are using pure JDBC as your persistence engine then you should use <link><page ri:content-title="JDBC Master Slave"></page></link> instead. For those willing to try out new tech, the <link><page ri:content-title="Replicated LevelDB Store"></page></link> gives speeds similar to a SAN solution without the hassle of having to setup a highly available shared file system.</p></div>
diff --git a/maven-snapshot-repository-in-your-pom.xml b/maven-snapshot-repository-in-your-pom.xml
index f8f2c7a..a5014f4 100644
--- a/maven-snapshot-repository-in-your-pom.xml
+++ b/maven-snapshot-repository-in-your-pom.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><p>ActiveMQ</p><p>In your pom.xml file you can add the Maven 2 snapshot repository if you want to try out the SNAPSHOT versions:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <repository>
+<div class="wiki-content maincontent"><p>ActiveMQ</p><p>In your pom.xml file you can add the Maven 2 snapshot repository if you want to try out the SNAPSHOT versions:</p><structured-macro ac:macro-id="b7a6fefa-d5d0-4f40-a1ba-42014d975b83" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <repository>
<id>apache.snapshots</id>
<name>Apache Development Snapshot Repository</name>
<url>https://repository.apache.org/content/repositories/snapshots/</url>
@@ -10,13 +9,10 @@
<enabled>true</enabled>
</snapshots>
</repository>
-]]></script>
-</div></div><p>Then you can use the SNAPSHOT version of ActiveMQ in your <code>pom.xml</code>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <dependency>
+</plain-text-body></structured-macro><p>Then you can use the SNAPSHOT version of ActiveMQ in your <code>pom.xml</code>:</p><structured-macro ac:macro-id="dd3509ee-553a-4aa7-9080-bea16a3d344a" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-broker</artifactId>
<version>5.14.0-SNAPSHOT</version>
</dependency>
-]]></script>
-</div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache ActiveMQ SNAPSHOTS</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://repository.apache.org/content/repositories/snapshots/">https://repository.apache.org/content/repositories/snapshots/</a></p></td></tr></tbody></table></div></div>
+</plain-text-body></structured-macro><table><tbody><tr><td colspan="1" rowspan="1"><p>Apache ActiveMQ SNAPSHOTS</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://repository.apache.org/content/repositories/snapshots/">https://repository.apache.org/content/repositories/snapshots/</a></p></td></tr></tbody></table></div>
diff --git a/maven2-activemq-broker-plugin.xml b/maven2-activemq-broker-plugin.xml
index 6c861f0..d91359e 100644
--- a/maven2-activemq-broker-plugin.xml
+++ b/maven2-activemq-broker-plugin.xml
@@ -1,35 +1,30 @@
<div class="wiki-content maincontent"><p>ActiveMQ provides a Maven2 plugin to easily startup a JMS broker. It is useful to quickly boot up a message broker in your Maven2 project for debugging or for doing integration tests.</p>
-<h3 id="Maven2ActiveMQBrokerPlugin-HowtoUse"> How to Use</h3>
+<h3> How to Use</h3>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Be Careful</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>The maven plugins in ActiveMQ have been renamed in version 5.8.0+ to better follow the Maven plugin naming conventions. The ActiveMQ Broker plugin has changed from 'maven-activemq-plugin' to 'activemq-maven-plugin'.</p></div></div>
+<structured-macro ac:macro-id="dddd5c9b-0b05-4664-a0e1-2f85cf8e904b" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Be Careful</parameter><rich-text-body>
+<p>The maven plugins in ActiveMQ have been renamed in version 5.8.0+ to better follow the Maven plugin naming conventions. The ActiveMQ Broker plugin has changed from 'maven-activemq-plugin' to 'activemq-maven-plugin'.</p></rich-text-body></structured-macro>
<blockquote><p>Replace the 5.7.0 version string with the version of your choosing, eg: 5.6.0, 5.8-SNAPSHOT</p></blockquote>
<p>In your Maven2 project, or using a minimal pom.xml like the following:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+<structured-macro ac:macro-id="74be901c-fa78-4225-8536-0118f832f63a" ac:name="code" ac:schema-version="1"><plain-text-body><?xml version="1.0" encoding="UTF-8"?>
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>com.acme</groupId>
<artifactId>run-amq</artifactId>
<version>1.0-SNAPSHOT</version>
-</project>]]></script>
-</div></div>
+</project></plain-text-body></structured-macro>
<p>just type:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="be7378b3-e88a-478f-8eb0-cc12f92dc3a7" ac:name="code" ac:schema-version="1"><plain-text-body>
mvn org.apache.activemq.tooling:maven-activemq-plugin:5.1:run
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This will download the 5.7.0 version of the plugin, and spin up a broker using a simple configuration url of the form <code>broker:(tcp://localhost:61616)?useJmx=false&persistent=false</code>. The necessary ActiveMQ jars will automatically be downloaded by Maven.</p>
<p>To configure log4j, provide the <code>-Dlog4j.configuration=<a shape="rect" class="external-link" href="file:///" rel="nofollow">file:///</a><full path to log4j.properties></code> system property on the mvn command line.</p>
<p>If you require a more advanced configuration with spring support, the jetty webconsole or with embedded camel you can add the plugin in your pom.xml and provide the required optional dependencies. For the default <code>conf/activemq.xml</code>, the following dependencies are required :</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a8cfc138-e1f3-4868-b986-7dafb111f494" ac:name="code" ac:schema-version="1"><plain-text-body>
<build>
<plugins>
<plugin>
@@ -70,19 +65,16 @@
</plugin>
</plugins>
</build>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p> and run it using:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="8b564575-8cc6-4315-85c6-d53147b3df62" ac:name="code" ac:schema-version="1"><plain-text-body>
mvn activemq:run
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="Maven2ActiveMQBrokerPlugin-ConfigurationOptions"> Configuration Options</h3>
+<h3> Configuration Options</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> configUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> broker:(tcp://localhost:61616)?useJmx=false&persistent=false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The broker configuration URI that will be use to startup the broker. For more information, refer <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">here</a><br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> fork </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If true, start up the broker in a separate thread, enabling maven to continue processing (Useful for integration testing).<br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> systemProperties </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> none </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Additional system properties that will be set.<br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> configUri </p></td><td colspan="1" rowspan="1"><p> broker:(tcp://localhost:61616)?useJmx=false&persistent=false </p></td><td colspan="1" rowspan="1"><p> The broker configuration URI that will be use to startup the broker. For more information, refer <link ac:tooltip="How do I embed a Broker inside a Connection"><page ri:content-title="How do I embed a Broker inside a Connection"></page><link-body>here</link-body></link><br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> fork </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> If true, start up the broker in a separate thread, enabling maven to continue processing (Useful for integration testing).<br clear="none" class="atl-forced-newline"> </p></td></tr><tr><td colspan="1" rowspan="1"><p> systemProperties </p></td><td colspan="1" rowspan="1"><p> none </p></td><td colspan="1" rowspan="1"><p> Additional system properties that will be set.<br clear="none" class="atl-forced-newline"> </p></td></tr></tbody></table>
<p> Note: By default, the broker plugin will set activemq.base, activemq.home, org.apache.activemq.default.directory.prefix, derby.system.home to ./target/. This means that all data folders will be created there, hence will easily be deleted by running mvn clean.</p></div>
diff --git a/mdc-logging.xml b/mdc-logging.xml
index d331f91..21a54df 100644
--- a/mdc-logging.xml
+++ b/mdc-logging.xml
@@ -1,7 +1,4 @@
-<div class="wiki-content maincontent"><p>ActiveMQ uses <a shape="rect" class="external-link" href="http://www.slf4j.org/" rel="nofollow">slf4j</a> as its logging framework. This allows ActiveMQ to support <a shape="rect" class="external-link" href="http://www.slf4j.org/api/org/slf4j/MDC.html" rel="nofollow">MDC logging</a>. For more information about about MDC logging see the <a shape="rect" class="external-link" href="http://logback.qos.ch/manual/mdc.html" rel="nofollow">logback manual</a>.</p><p>Currently ActiveMQ adds three keys to the diagnostic context:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Key</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.broker</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Name of the broker logging event.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.connector</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Address of the connector which is serving the request.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.destination</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Name of the target destination of a message.</p></td></tr></tbody></table></div><p>For example, if you've defined a log appender to use the following <strong><code>ConversionPattern</code></strong>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[log4j.appender.stdout.layout.ConversionPattern=%d [%-15.15t] - %-5p %-30.30c{1} - %-10.10X{activemq.broker} %-20.20X{activemq.connector} %-20.20X{activemq.destination} - %m%n]]></script>
-</div></div><p>then in an environment where multiple brokers use the same log (like unit tests), the log output will take this general form:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: text; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[2011-03-23 13:51:04,919 [127.0.0.1:58146] - TRACE Queue - broker-3B tcp://localhost:6111 - Message ID:dejan-bosanacs-macbook-pro....
+<div class="wiki-content maincontent"><p>ActiveMQ uses <a shape="rect" href="http://www.slf4j.org/">slf4j</a> as its logging framework. This allows ActiveMQ to support <a shape="rect" href="http://www.slf4j.org/api/org/slf4j/MDC.html">MDC logging</a>. For more information about about MDC logging see the <a shape="rect" href="http://logback.qos.ch/manual/mdc.html">logback manual</a>.</p><p>Currently ActiveMQ adds three keys to the diagnostic context:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Key</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>activemq.broker</code></p></td><td colspan="1" rowspan="1"><p>Name of the broker logging event.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>activemq.connector</code></p></td><td colspan="1" rowspan="1"><p>Address of the connector which is serving the request.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>activemq.destination</code></p></td><td colspan="1" rowspan="1"><p>Name of the target destination of a message.</p></td></tr></tbody></table><p>For example, if you've defined a log appender to use the following <strong><code>ConversionPattern</code></strong>:</p><structured-macro ac:macro-id="01b2beaa-403c-4dc0-80e2-5c22f07d902e" ac:name="code" ac:schema-version="1"><parameter ac:name="language">text</parameter><plain-text-body>log4j.appender.stdout.layout.ConversionPattern=%d [%-15.15t] - %-5p %-30.30c{1} - %-10.10X{activemq.broker} %-20.20X{activemq.connector} %-20.20X{activemq.destination} - %m%n</plain-text-body></structured-macro><p>then in an environment where multiple brokers use the same log (like unit tests), the log output will take this general form:</p><structured-macro ac:macro-id="3ac0444e-9ea9-4670-9006-edc3618a4bdf" ac:name="code" ac:schema-version="1"><parameter ac:name="language">text</parameter><plain-text-body>2011-03-23 13:51:04,919 [127.0.0.1:58146] - TRACE Queue - broker-3B tcp://localhost:6111 - Message ID:dejan-bosanacs-macbook-pro....
2011-03-23 13:51:04,935 [oker-3B] Task-1] - DEBUG Queue - broker-3B tcp://localhost:6111 PROD.FUSESOURCE.3.B - PROD.FUSESOURCE.3.B toPageIn: 1, Inflight...
2011-03-23 13:51:04,763 [oker-2A] Task-1] - TRACE AbstractStoreCursor - broker-2A vm://broker-2A PROD.FUSESOURCE.3.B - QueueStorePrefetch611939300 - fillBatch
2011-03-23 13:51:04,759 [127.0.0.1:58118] - TRACE Queue - broker-3A tcp://localhost:6110 - Message ID:dejan-bosanacs-macbook-pro.l...
@@ -9,6 +6,5 @@
2011-03-23 13:51:04,936 [oker-3B] Task-1] - TRACE AbstractStoreCursor - broker-3B tcp://localhost:6111 PROD.FUSESOURCE.3.B - QueueStorePrefetch2047424752 - fillBatch
2011-03-23 13:51:04,941 [oker-2A] Task-2] - DEBUG DemandForwardingBridgeSupport - broker-2A - bridging (broker-2A -> broker-1B, consu...
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/message-cursors.xml b/message-cursors.xml
index 959d34d..7651e55 100644
--- a/message-cursors.xml
+++ b/message-cursors.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="MessageCursors-MessageCursors">Message Cursors</h2>
+<div class="wiki-content maincontent"><h2>Message Cursors</h2>
-<p>A common problem in previous versions of ActiveMQ was <a shape="rect" href="my-producer-blocks.xml">running out of RAM buffer</a> when using non-persistent messaging.</p>
+<p>A common problem in previous versions of ActiveMQ was <link><page ri:content-title="My producer blocks"></page><link-body>running out of RAM buffer</link-body></link> when using non-persistent messaging.</p>
<p>Beginning with ActiveMQ 5.0.0, there is a new memory model that allows messages to be paged in from storage when space is available (using Store cursors for persistent messages).</p>
@@ -10,43 +10,42 @@
<p>ActiveMQ 5.0 takes a hybrid approach, allowing messages to pass from producer to consumer directly (after the messages have been persisted), but switches back to using cursors if the consumer(s) fall behind.</p>
-<p>When Message Consumers are both active and fast - keeping up with the Message Producer(s) - messages are stored and then passed to a dispatch queue in the broker associated with the Consumer: <span class="confluence-embedded-file-wrapper image-center-wrapper"><img class="confluence-embedded-image image-center" src="message-cursors.data/DispatchFastConsumers.png" data-image-src="/confluence/download/attachments/48811/DispatchFastConsumers.png?version=1&modificationDate=1193437635000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59670893" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="DispatchFastConsumers.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="48811" data-linked-resource-container-version="16"></span><br clear="none">
-If a Consumer becomes active after messages are pending from the store for it, or it's slower than the producer, then messages are paged in to the dispatch queue from a pending cursor: <span class="confluence-embedded-file-wrapper image-center-wrapper"><img class="confluence-embedded-image image-center" src="message-cursors.data/DispatchSlowConsumers.png" data-image-src="/confluence/download/attachments/48811/DispatchSlowConsumers.png?version=1&modificationDate=1193437656000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59670895" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="DispatchSlowConsumers.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="48811" data-linked-resource-container-version="16"></span></p>
+<p>When Message Consumers are both active and fast - keeping up with the Message Producer(s) - messages are stored and then passed to a dispatch queue in the broker associated with the Consumer: <image ac:align="center"><attachment ri:filename="DispatchFastConsumers.png"></attachment></image><br clear="none">
+If a Consumer becomes active after messages are pending from the store for it, or it's slower than the producer, then messages are paged in to the dispatch queue from a pending cursor: <image ac:align="center"><attachment ri:filename="DispatchSlowConsumers.png"></attachment></image></p>
-<h3 id="MessageCursors-TypesofCursor">Types of Cursor</h3>
+<h3>Types of Cursor</h3>
<p>The default message cursor type in ActiveMQ 5.0 is Store based.  It behaves as above. There are two additional types of cursor that could be used: <strong>VM Cursor</strong> and <strong>File based Cursor</strong>, described below.</p>
-<h4 id="MessageCursors-VMCursor">VM Cursor</h4>
+<h4>VM Cursor</h4>
-<p>The VM Cursor is how ActiveMQ 4.x works: references to a message are held in memory, and passed to the dispatch queue when needed. This can be very fast, but also has the downside of not being able to handle very slow consumers or consumers that have been inactive for a long time: <span class="confluence-embedded-file-wrapper image-center-wrapper"><img class="confluence-embedded-image image-center" src="message-cursors.data/VMCursor.png" data-image-src="/confluence/download/attachments/48811/VMCursor.png?version=1&modificationDate=1193439154000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59670900" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="VMCursor.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="48811" data-linked-resource-container-version="16"></span></p>
+<p>The VM Cursor is how ActiveMQ 4.x works: references to a message are held in memory, and passed to the dispatch queue when needed. This can be very fast, but also has the downside of not being able to handle very slow consumers or consumers that have been inactive for a long time: <image ac:align="center"><attachment ri:filename="VMCursor.png"></attachment></image></p>
-<h4 id="MessageCursors-FilebasedCursor">File based Cursor</h4>
+<h4>File based Cursor</h4>
-<p>The File based Cursor is dervied from the VM Cursor.  When memory in the broker reaches its limit, it can page messages to temporary files on disk. This type of cursor can be used when the message store might be relatively slow, but consumers are generally fast. By buffering to disk, it allows the message broker to handle message bursts from producers without resorting to paging in from slow storage: <span class="confluence-embedded-file-wrapper image-center-wrapper"><img class="confluence-embedded-image image-center" src="message-cursors.data/FileCursor.png" data-image-src="/confluence/download/attachments/48811/FileCursor.png?version=1&modificationDate=1193438877000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59670898" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="FileCursor.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="48811" data-linked-resource-container-version="16"></span></p>
+<p>The File based Cursor is dervied from the VM Cursor.  When memory in the broker reaches its limit, it can page messages to temporary files on disk. This type of cursor can be used when the message store might be relatively slow, but consumers are generally fast. By buffering to disk, it allows the message broker to handle message bursts from producers without resorting to paging in from slow storage: <image ac:align="center"><attachment ri:filename="FileCursor.png"></attachment></image></p>
-<h4 id="MessageCursors-PagingforNon-PersistentMessages">Paging for Non-Persistent Messages</h4>
+<h4>Paging for Non-Persistent Messages</h4>
-<p>The store based cursor also handles cursors for non-persistent messages, which are not stored in the message store. Non-persistent messages are passed directly to the cursor, so the store based cursor embeds a file based cursor just for these types of messages: <span class="confluence-embedded-file-wrapper image-center-wrapper"><img class="confluence-embedded-image image-center" src="message-cursors.data/NonPersistentMsgs.png" data-image-src="/confluence/download/attachments/48811/NonPersistentMsgs.png?version=1&modificationDate=1193445319000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="59670902" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="NonPersistentMsgs.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="48811" data-linked-resource-container-version="16"></span></p>
+<p>The store based cursor also handles cursors for non-persistent messages, which are not stored in the message store. Non-persistent messages are passed directly to the cursor, so the store based cursor embeds a file based cursor just for these types of messages: <image ac:align="center"><attachment ri:filename="NonPersistentMsgs.png"></attachment></image></p>
-<h3 id="MessageCursors-ConfiguringCursors">Configuring Cursors</h3>
+<h3>Configuring Cursors</h3>
<p>By default, Store based cursors are used, but it is possible to configure different cursors depending on the destination.</p>
-<h4 id="MessageCursors-Topicsubscribers">Topic subscribers</h4>
+<h4>Topic subscribers</h4>
<p>For Topics there is a dispatch queue and pending cursor for every subscriber.  It's possible to configure different policies for durable subscribers and transient subscribers - e.g:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="8ad8f4ca-d565-4697-9780-4747a4fff7d5" ac:name="code" ac:schema-version="1"><plain-text-body>
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry topic="org.apache.>" producerFlowControl="false" memoryLimit="1mb">
+ <policyEntry topic="org.apache.>" producerFlowControl="false" memoryLimit="1mb">
<dispatchPolicy>
<strictOrderDispatchPolicy />
</dispatchPolicy>
<deadLetterStrategy>
- <individualDeadLetterStrategy topicPrefix="Test.DLQ." />
+ <individualDeadLetterStrategy topicPrefix="Test.DLQ." />
</deadLetterStrategy>
<pendingSubscriberPolicy>
<vmCursor />
@@ -58,22 +57,20 @@
</policyEntries>
</policyMap>
</destinationPolicy>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Valid Subscriber types are <strong><em>vmCursor</em></strong> and <strong><em>fileCursor.</em></strong> The default is the store based cursor.<br clear="none">
Valid Durable Subscriber cursor types are <strong><em>storeDurableSubscriberCursor</em></strong>, <strong><em>vmDurableCursor</em></strong> and <strong><em>fileDurableSubscriberCursor.</em></strong> The default is the store based cursor</p>
-<h4 id="MessageCursors-Queues">Queues</h4>
+<h4>Queues</h4>
<p>For Queues there is a single dispatch Queue and pending Queue for every destination, so configuration is slightly different:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1098531a-eb10-4e33-bfbf-bc93b3c6f05b" ac:name="code" ac:schema-version="1"><plain-text-body>
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue="org.apache.>">
+ <policyEntry queue="org.apache.>">
<deadLetterStrategy>
- <individualDeadLetterStrategy queuePrefix="Test.DLQ."/>
+ <individualDeadLetterStrategy queuePrefix="Test.DLQ."/>
</deadLetterStrategy>
<pendingQueuePolicy>
<vmQueueCursor />
@@ -82,11 +79,11 @@
</policyEntries>
</policyMap>
</destinationPolicy>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Valid Queue cursor types are <strong><em>storeCursor</em></strong>, <strong><em>vmQueueCursor</em></strong> and <strong><em>fileQueueCursor.</em></strong> The default is the store based cursor</p>
-<h3 id="MessageCursors-SeeAlso">See Also</h3>
+<h3>See Also</h3>
-<ul><li><a shape="rect" href="producer-flow-control.xml">Producer Flow Control</a></li></ul></div>
+<ul><li><link><page ri:content-title="Producer Flow Control"></page></link></li></ul>
+</div>
diff --git a/message-dispatching-features.xml b/message-dispatching-features.xml
index 96d0bff..b4bfc2a 100644
--- a/message-dispatching-features.xml
+++ b/message-dispatching-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="async-sends.xml">Async Sends</a></li><li><a shape="rect" href="dispatch-policies.xml">Dispatch Policies</a></li><li><a shape="rect" href="message-cursors.xml">Message Cursors</a></li><li><a shape="rect" href="optimized-acknowledgement.xml">Optimized Acknowledgement</a></li><li><a shape="rect" href="producer-flow-control.xml">Producer Flow Control</a></li><li><a shape="rect" href="total-ordering.xml">Total Ordering</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="7e4ec00c-b00f-47ab-bb03-2495a040ae56" ac:name="children" ac:schema-version="1"><parameter ac:name="">all</parameter></structured-macro></div>
diff --git a/message-features.xml b/message-features.xml
index a1dfa80..4589a2e 100644
--- a/message-features.xml
+++ b/message-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="activemq-message-properties.xml">ActiveMQ Message Properties</a></li><li><a shape="rect" href="advisory-message.xml">Advisory Message</a></li><li><a shape="rect" href="blob-messages.xml">Blob Messages</a></li><li><a shape="rect" href="delay-and-schedule-message-delivery.xml">Delay and Schedule Message Delivery</a></li><li><a shape="rect" href="jms-streams.xml">JMS Streams</a></li><li><a shape="rect" href="message-transformation.xml">Message Transformation</a></li><li><a shape="rect" href="objectmessage.xml">ObjectMessage</a></li><li><a shape="rect" href="structured-message-properties-and-mapmessages.xml">Structured Message Properties and MapMessages</a></li></ul></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="d212482f-a1b9-444e-ade7-4a8b484b0a43" ac:name="children" ac:schema-version="1"><parameter ac:name="">all</parameter></structured-macro></p></div>
diff --git a/message-groups.xml b/message-groups.xml
index 44fae23..ff609e1 100644
--- a/message-groups.xml
+++ b/message-groups.xml
@@ -1,56 +1,36 @@
-<div class="wiki-content maincontent"><h2 id="MessageGroups-MessageGroups">Message Groups</h2><p>Message Groups are an enhancement to the <a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a> feature. They provide:</p><ul><li>Guaranteed ordering of the processing of related messages across a single queue.</li><li>Load balancing of the processing of messages across multiple consumers.</li><li>High availability / auto-failover to other consumers if a JVM goes down.</li></ul><p>So logically Message Groups are like a parallel <a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a>. Rather than all messages going to a single consumer, the standard JMS header <strong><code>JMSXGroupID</code></strong> is used to define which <em>message group</em> the message belongs to. The Message Group feature then ensures that all messages for the <em>same</em> message group will be sent to the <em>same</em> JMS consumer - whilst that consumer stays alive. As soon as the consumer dies another will be chosen.</p><p>Another way of explaining Message Groups is that it provides sticky load balancing of messages across consumers; where the <strong><code>JMSXGroupID</code></strong> is kinda like a HTTP session ID or cookie value and the message broker is acting like a HTTP load balancer.</p><h3 id="MessageGroups-ExampleUseCase">Example Use Case</h3><p>Lets say we are doing some kind of order matching system where people are buying and selling things (stocks, shares, placing online bets, whatever). You want to have consumers who match bids and offers for different items (stocks / bets) so they want to keep in RAM for performance a sub-set of the data set. Therefore set the <strong><code>JMSXGroupID</code></strong> to be <strong><code>MSFT</code></strong>, <strong><code>IBM</code></strong>, <strong><code>SUNW</code></strong> and so forth to use the stock symbol to define the message group. (It can be any string whatsoever; maybe combining trading book, trading exchange, date and so forth - the more specific the group ID, the more concurrent you can run). Assume we are buying and selling <strong><code>MSFT</code>, <code>IBM</code>, <code>SUNW</code></strong> shares; the Message Groups feature guarantees that all the <strong><code>MSFT</code></strong> messages will be processed in order by the same consumer; ditto for <strong><code>IBM</code></strong> and <strong><code>SUNW</code></strong>.</p><h3 id="MessageGroups-HowMessageGroupsWork">How Message Groups Work</h3><p>When a message is being dispatched to a consumer, the <strong><code>JMSXGroupID</code></strong> is checked. If one is present then the broker checks to see if a consumer owns that message group. Since there could be a large number of message groups hash buckets are used rather than the actual <strong><code>JMSXGroupID</code></strong> string.</p><p>If no consumer is associated with a message group a consumer is chosen. Said JMS <strong><code>MessageConsumer</code></strong> will receive all further messages with the same <strong><code>JMSXGroupID</code></strong> value until:</p><ul><li>the consumer closes (or the client which created the consumer dies etc).</li><li>someone closes the message group by sending a message with a negative value for <strong><code>JMSXGroupSeq</code></strong> (see below for more details).</li></ul><p><strong>Note</strong>: as with message selector matching, grouping based on <strong><code>JMSXGroupID</code></strong> occurs before dispatch on messages in memory. With the default <strong><code>maxPageSize</code></strong> option, large backlogs of messages destined for one group can block receipt of messages to other groups if they don't all fit in memory. You can change the default <strong><code>maxPageSize</code></strong> setting for destinations as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<destinationPolicy>
+<div class="wiki-content maincontent"><h2>Message Groups</h2><p>Message Groups are an enhancement to the <link><page ri:content-title="Exclusive Consumer"></page></link> feature. They provide:</p><ul><li>Guaranteed ordering of the processing of related messages across a single queue.</li><li>Load balancing of the processing of messages across multiple consumers.</li><li>High availability / auto-failover to other consumers if a JVM goes down.</li></ul><p>So logically Message Groups are like a parallel <link><page ri:content-title="Exclusive Consumer"></page></link>. Rather than all messages going to a single consumer, the standard JMS header <strong><code>JMSXGroupID</code></strong> is used to define which <em>message group</em> the message belongs to. The Message Group feature then ensures that all messages for the <em>same</em> message group will be sent to the <em>same</em> JMS consumer - whilst that consumer stays alive. As soon as the consumer dies another will be chosen.</p><p>Another way of explaining Message Groups is that it provides sticky load balancing of messages across consumers; where the <strong><code>JMSXGroupID</code></strong> is kinda like a HTTP session ID or cookie value and the message broker is acting like a HTTP load balancer.</p><h3>Example Use Case</h3><p>Lets say we are doing some kind of order matching system where people are buying and selling things (stocks, shares, placing online bets, whatever). You want to have consumers who match bids and offers for different items (stocks / bets) so they want to keep in RAM for performance a sub-set of the data set. Therefore set the <strong><code>JMSXGroupID</code></strong> to be <strong><code>MSFT</code></strong>, <strong><code>IBM</code></strong>, <strong><code>SUNW</code></strong> and so forth to use the stock symbol to define the message group. (It can be any string whatsoever; maybe combining trading book, trading exchange, date and so forth - the more specific the group ID, the more concurrent you can run). Assume we are buying and selling <strong><code>MSFT</code>, <code>IBM</code>, <code>SUNW</code></strong> shares; the Message Groups feature guarantees that all the <strong><code>MSFT</code></strong> messages will be processed in order by the same consumer; ditto for <strong><code>IBM</code></strong> and <strong><code>SUNW</code></strong>.</p><h3>How Message Groups Work</h3><p>When a message is being dispatched to a consumer, the <strong><code>JMSXGroupID</code></strong> is checked. If one is present then the broker checks to see if a consumer owns that message group. Since there could be a large number of message groups hash buckets are used rather than the actual <strong><code>JMSXGroupID</code></strong> string.</p><p>If no consumer is associated with a message group a consumer is chosen. Said JMS <strong><code>MessageConsumer</code></strong> will receive all further messages with the same <strong><code>JMSXGroupID</code></strong> value until:</p><ul><li>the consumer closes (or the client which created the consumer dies etc).</li><li>someone closes the message group by sending a message with a negative value for <strong><code>JMSXGroupSeq</code></strong> (see below for more details).</li></ul><p><strong>Note</strong>: as with message selector matching, grouping based on <strong><code>JMSXGroupID</code></strong> occurs before dispatch on messages in memory. With the default <strong><code>maxPageSize</code></strong> option, large backlogs of messages destined for one group can block receipt of messages to other groups if they don't all fit in memory. You can change the default <strong><code>maxPageSize</code></strong> setting for destinations as follows:</p><structured-macro ac:macro-id="c68cfc0c-ec1f-4186-bd74-ac0385e58234" ac:name="code" ac:schema-version="1"><plain-text-body><destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue=">" maxPageSize="1000"/>
+ <policyEntry queue=">" maxPageSize="1000"/>
</policyEntries>
</policyMap>
-</destinationPolicy>]]></script>
-</div></div><h3 id="MessageGroups-UsingMessageGroups">Using Message Groups</h3><p>You just need to change your JMS producers to fill in the <strong><code>JMSXGroupID</code></strong> message header with some <strong><code>String</code></strong> value of your choice.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Mesasge message = session.createTextMessage("<foo>hey</foo>");
-message.setStringProperty("JMSXGroupID", "IBM_NASDAQ_20/4/05");
+</destinationPolicy></plain-text-body></structured-macro><h3>Using Message Groups</h3><p>You just need to change your JMS producers to fill in the <strong><code>JMSXGroupID</code></strong> message header with some <strong><code>String</code></strong> value of your choice.</p><p>Example:</p><structured-macro ac:macro-id="447b2ec1-3555-4159-8fe4-1b97b6f5ebca" ac:name="code" ac:schema-version="1"><plain-text-body>Mesasge message = session.createTextMessage("<foo>hey</foo>");
+message.setStringProperty("JMSXGroupID", "IBM_NASDAQ_20/4/05");
...
producer.send(message);
-]]></script>
-</div></div><h3 id="MessageGroups-ClosingaMessageGroup">Closing a Message Group</h3><p>You generally don't need to close a message group; just keep using it. However if you really do want to close a group you can add a negative sequence number.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Mesasge message = session.createTextMessage("<foo>hey</foo>");
-message.setStringProperty("JMSXGroupID", "IBM_NASDAQ_20/4/05");
-message.setIntProperty("JMSXGroupSeq", -1);
+</plain-text-body></structured-macro><h3>Closing a Message Group</h3><p>You generally don't need to close a message group; just keep using it. However if you really do want to close a group you can add a negative sequence number.</p><p>Example:</p><structured-macro ac:macro-id="3044d0fa-d149-4a00-b2b2-f21a4b83e088" ac:name="code" ac:schema-version="1"><plain-text-body>Mesasge message = session.createTextMessage("<foo>hey</foo>");
+message.setStringProperty("JMSXGroupID", "IBM_NASDAQ_20/4/05");
+message.setIntProperty("JMSXGroupSeq", -1);
...
producer.send(message);
-]]></script>
-</div></div><p>This then <em>closes</em> the message group so if another message is sent in the future with the same message group ID it will be reassigned to a new consumer.</p><h3 id="MessageGroups-Implications">Implications</h3><p>Message Groups mean you get the power of <strong>grid</strong> processing of messages across a cluster of consumers with reliability, auto-failover, load balancing but you can also order the processing of messages too. So its the best of both worlds. However using the above example, what Message Groups actually do is to partition your work load across consumers using a user definable partition strategy - the <strong><code>JMSXGroupID</code></strong> value.</p><p>The neat thing about this is that you can do neat things like use lots of RAM caching; keep the order for <strong><code>MSFT</code></strong> in RAM in the <strong><code>MSFT</code></strong> consumer; keep the <strong><code>IBM</code></strong> orders in RAM in the <strong><code>IBM</code></strong> consumer - since the message broker is partitioning for you, you do not have to rely on a distributed cache with inter-cache synchronization and locking to take advantage of caching.</p><p>The great thing is - to the application developer, it looks like a simple 1 consumer world where you process messages and do your job; leaving the broker to do all the hard stuff for you</p><ul><li>partitioning the traffic</li><li>load balancing of message groups across consumers</li><li>auto-failover of groups to different consumers as consumers come and go</li></ul><p>In summary; if ordering or per-message caching and synchronization are in any way important to you then we highly recommend you use message groups to partition your traffic.</p><h3 id="MessageGroups-GettingNotifiedofOwnershipChangesofMessageGroups">Getting Notified of Ownership Changes of Message Groups</h3><p>ActiveMQ support a boolean header called <strong><code>JMSXGroupFirstForConsumer</code></strong>. This header is set on the first message sent to a consumer for a particular message group.</p><p>If the JMS connection is using <strong><code>failover:</code></strong> and a temporary network error occurs so that the connection disconnects from the broker and reconnects some time later, a new consumer instance will be created under the covers of the JMS client leading to the possibility of another message with this header being set for the same message group.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[String groupId = message.getStringProperty("JMSXGroupId");
+</plain-text-body></structured-macro><p>This then <em>closes</em> the message group so if another message is sent in the future with the same message group ID it will be reassigned to a new consumer.</p><h3>Implications</h3><p>Message Groups mean you get the power of <strong>grid</strong> processing of messages across a cluster of consumers with reliability, auto-failover, load balancing but you can also order the processing of messages too. So its the best of both worlds. However using the above example, what Message Groups actually do is to partition your work load across consumers using a user definable partition strategy - the <strong><code>JMSXGroupID</code></strong> value.</p><p>The neat thing about this is that you can do neat things like use lots of RAM caching; keep the order for <strong><code>MSFT</code></strong> in RAM in the <strong><code>MSFT</code></strong> consumer; keep the <strong><code>IBM</code></strong> orders in RAM in the <strong><code>IBM</code></strong> consumer - since the message broker is partitioning for you, you do not have to rely on a distributed cache with inter-cache synchronization and locking to take advantage of caching.</p><p>The great thing is - to the application developer, it looks like a simple 1 consumer world where you process messages and do your job; leaving the broker to do all the hard stuff for you</p><ul><li>partitioning the traffic</li><li>load balancing of message groups across consumers</li><li>auto-failover of groups to different consumers as consumers come and go</li></ul><p>In summary; if ordering or per-message caching and synchronization are in any way important to you then we highly recommend you use message groups to partition your traffic.</p><h3>Getting Notified of Ownership Changes of Message Groups</h3><p>ActiveMQ support a boolean header called <strong><code>JMSXGroupFirstForConsumer</code></strong>. This header is set on the first message sent to a consumer for a particular message group.</p><p>If the JMS connection is using <strong><code>failover:</code></strong> and a temporary network error occurs so that the connection disconnects from the broker and reconnects some time later, a new consumer instance will be created under the covers of the JMS client leading to the possibility of another message with this header being set for the same message group.</p><p>Example:</p><structured-macro ac:macro-id="210ada08-a4bc-4e86-a3fc-4bb1bd553bc9" ac:name="code" ac:schema-version="1"><plain-text-body>String groupId = message.getStringProperty("JMSXGroupId");
-if (message.getBooleanProperty("JMSXGroupFirstForConsumer")) {
+if (message.getBooleanProperty("JMSXGroupFirstForConsumer")) {
// flush cache for groupId
}
-]]></script>
-</div></div><p>To flush caches to ensure consistent state when faced with network errors.</p><h3 id="MessageGroups-AddingNewConsumers">Adding New Consumers</h3><p>If you have existing messages in the broker and add consumers at a later stage, it is a good idea to delay message dispatch start until all consumers are present (or at least to give enough time for them to subscribe). If you don't do that the first consumer will probably acquire all message groups and all messages will be dispatched to it. You can achieve this by using <strong><code>consumersBeforeDispatchStarts</code></strong> and <strong><code>timeBeforeDispatchStarts</code></strong> <a shape="rect" href="per-destination-policies.xml">destination policies</a>.</p><p>When both <strong>consumersBeforeDispatchStarts</strong> and <strong>timeBeforeDispatchStarts</strong> are set to a value greater than zero, the dispatching will start as soon as the required number of consumers are present or the timeBeforeDispatchStarts timeout expires. If only consumersBeforeDispatchStarts is set then the timeout for consumers to connect is 1 second. If all consumers disconnect then message dispatch delay will be applied again at the next consumer connection.</p><p> </p><p>Here's the example of the destination policy that delays dispatch for <strong><code>200ms</code></strong>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<destinationPolicy>
+</plain-text-body></structured-macro><p>To flush caches to ensure consistent state when faced with network errors.</p><h3>Adding New Consumers</h3><p>If you have existing messages in the broker and add consumers at a later stage, it is a good idea to delay message dispatch start until all consumers are present (or at least to give enough time for them to subscribe). If you don't do that the first consumer will probably acquire all message groups and all messages will be dispatched to it. You can achieve this by using <strong><code>consumersBeforeDispatchStarts</code></strong> and <strong><code>timeBeforeDispatchStarts</code></strong> <link><page ri:content-title="Per Destination Policies"></page><plain-text-link-body>destination policies</plain-text-link-body></link>.</p><p>When both <strong>consumersBeforeDispatchStarts</strong> and <strong>timeBeforeDispatchStarts</strong> are set to a value greater than zero, the dispatching will start as soon as the required number of consumers are present or the timeBeforeDispatchStarts timeout expires. If only consumersBeforeDispatchStarts is set then the timeout for consumers to connect is 1 second. If all consumers disconnect then message dispatch delay will be applied again at the next consumer connection.</p><p> </p><p>Here's the example of the destination policy that delays dispatch for <strong><code>200ms</code></strong>:</p><structured-macro ac:macro-id="3856f630-e874-40dc-93de-d575522593c9" ac:name="code" ac:schema-version="1"><plain-text-body><destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue=">" timeBeforeDispatchStarts="200"/>
+ <policyEntry queue=">" timeBeforeDispatchStarts="200"/>
</policyEntries>
</policyMap>
</destinationPolicy>
-]]></script>
-</div></div><p>The following code snippet shows how to wait for two consumers (or two seconds) before dispatch starts:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<destinationPolicy>
+</plain-text-body></structured-macro><p>The following code snippet shows how to wait for two consumers (or two seconds) before dispatch starts:</p><structured-macro ac:macro-id="3ddeb2fd-8e1c-4bff-a14e-ae3cabef85d0" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue=">" consumersBeforeDispatchStarts="2" timeBeforeDispatchStarts="2000"/>
+ <policyEntry queue=">" consumersBeforeDispatchStarts="2" timeBeforeDispatchStarts="2000"/>
</policyEntries>
</policyMap>
</destinationPolicy>
-]]></script>
-</div></div><p>As <a shape="rect" class="external-link" href="https://github.com/apache/activemq/blob/master/activemq-unit-tests/src/test/java/org/apache/activemq/usecases/MessageGroupDelayedTest.java" rel="nofollow">the appropriate test case</a> shows, adding a small time pause before dispatching or setting a minimum consumer number, ensures equal message group distribution.</p><p> </p><h3 id="MessageGroups-Competingdemandsofmemoryconsumption,loadbalancing,complexity,etc."><span style="color: rgb(33,33,33);">Competing demands of memory consumption, load balancing, complexity, etc.</span></h3><p>The default behavior which is limited to 1024 message groups in an LRU cache may not match you expectation w.r.t message order... some detail to explain:</p><p>MessageGroupHashBucket and SimpleMessageGroupMap message groups work by associating each group with a consumer.</p><p>SimpleMessageGroupMap keeps track of every group but suffers from unbounded memory use.</p><p>MessageGroupHashBucked keeps track of every group and has bounded memory use.</p><p>CachedMessageGroupMap has bounded memory use, but only keeps track of up to 1024 (or the maximum configured size) groups, then loses track of any groups older than the newest 1024.</p><p>In this way, if there are more groups than the maximum, <strong>ordering will be lost for the oldest groups</strong>.</p><p>Typically users would close groups such that the in memory set can be retained below the configured limits. Some usefull discussion at [
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-6851?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/bug.png">AMQ-6851</a>
- -
- <span class="summary">Messages using Message Groups can arrive out of order when using CachedMessageGroupMap</span>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
-]</p><h3 id="MessageGroups-See">See</h3><ul><li><a shape="rect" href="how-do-message-groups-compare-to-selectors.xml">How do Message Groups compare to Selectors</a></li></ul></div>
+</plain-text-body></structured-macro><p>As <a shape="rect" href="https://github.com/apache/activemq/blob/master/activemq-unit-tests/src/test/java/org/apache/activemq/usecases/MessageGroupDelayedTest.java">the appropriate test case</a> shows, adding a small time pause before dispatching or setting a minimum consumer number, ensures equal message group distribution.</p><p> </p><h3><span style="color: rgb(33,33,33);">Competing demands of memory consumption, load balancing, complexity, etc.</span></h3><p>The default behavior which is limited to 1024 message groups in an LRU cache may not match you expectation w.r.t message order... some detail to explain:</p><p>MessageGroupHashBucket and SimpleMessageGroupMap message groups work by associating each group with a consumer.</p><p>SimpleMessageGroupMap keeps track of every group but suffers from unbounded memory use.</p><p>MessageGroupHashBucked keeps track of every group and has bounded memory use.</p><p>CachedMessageGroupMap has bounded memory use, but only keeps track of up to 1024 (or the maximum configured size) groups, then loses track of any groups older than the newest 1024.</p><p>In this way, if there are more groups than the maximum, <strong>ordering will be lost for the oldest groups</strong>.</p><p>Typically users would close groups such that the in memory set can be retained below the configured limits. Some usefull discussion at [<structured-macro ac:macro-id="1f6b985f-9d17-4448-8eca-9c79c84028c9" ac:name="jira" ac:schema-version="1"><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-6851</parameter></structured-macro>]</p><h3>See</h3><ul><li><link><page ri:content-title="How do Message Groups compare to Selectors"></page></link></li></ul></div>
diff --git a/message-redelivery-and-dlq-handling.xml b/message-redelivery-and-dlq-handling.xml
index 2471aca..e479341 100644
--- a/message-redelivery-and-dlq-handling.xml
+++ b/message-redelivery-and-dlq-handling.xml
@@ -1,24 +1,21 @@
-<div class="wiki-content maincontent"><h3 id="MessageRedeliveryandDLQHandling-Overview">Overview</h3><p>Messages are redelivered to a client when <strong>any</strong> of the following occurs:</p><ol><li>A transacted session is used and <strong><code>rollback()</code></strong> is called.</li><li>A transacted session is closed before <strong><code>commit()</code></strong> is called.</li><li>A session is using <strong><code>CLIENT_ACKNOWLEDGE</code></strong> and <strong><code>Session.recover()</code></strong> is called.</li><li>A client connection times out (perhaps the code being executed takes longer than the configured time-out period).</li></ol><p>The broker transmits the default delivery policy that he prefers to a client connection in his <strong><code>BrokerInfo</code></strong> command packet. But the client can override the policy settings by using the <strong><code>ActiveMQConnection.getRedeliveryPolicy()</code></strong> method:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[RedeliveryPolicy policy = connection.getRedeliveryPolicy();
+<div class="wiki-content maincontent"><h3>Overview</h3><p>Messages are redelivered to a client when <strong>any</strong> of the following occurs:</p><ol><li>A transacted session is used and <strong><code>rollback()</code></strong> is called.</li><li>A transacted session is closed before <strong><code>commit()</code></strong> is called.</li><li>A session is using <strong><code>CLIENT_ACKNOWLEDGE</code></strong> and <strong><code>Session.recover()</code></strong> is called.</li><li>A client connection times out (perhaps the code being executed takes longer than the configured time-out period).</li></ol><p>The broker transmits the default delivery policy that he prefers to a client connection in his <strong><code>BrokerInfo</code></strong> command packet. But the client can override the policy settings by using the <strong><code>ActiveMQConnection.getRedeliveryPolicy()</code></strong> method:</p><structured-macro ac:macro-id="dd38acae-bc3e-4105-babf-3fcfc4a791ad" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>RedeliveryPolicy policy = connection.getRedeliveryPolicy();
policy.setInitialRedeliveryDelay(500);
policy.setBackOffMultiplier(2);
policy.setUseExponentialBackOff(true);
policy.setMaximumRedeliveries(2);
-]]></script>
-</div></div><p>Once a message's redelivery attempts exceeds the <strong><code>maximumRedeliveries</code></strong> configured for the <a shape="rect" href="redelivery-policy.xml">Redelivery Policy</a>, a "Poison ACK" is sent back to the broker letting him know that the message was considered a poison pill. The Broker then takes the message and sends it to a Dead Letter Queue so that it can be analyzed later on.</p><p>The default Dead Letter Queue in ActiveMQ is called <strong><code>ActiveMQ.DLQ</code></strong>; all un-deliverable messages will get sent to this queue and this can be difficult to manage. So, you can set an <strong><code>individualDeadLetterStrategy</code></strong> in the destination policy map of the <strong><code>activemq.xml</code></strong> configuration file, which allows you to specify a specific dead letter queue prefix for a given queue or topic. You can apply this strategy using wild card if you like so that all queues get their own dead-letter queue, as is shown in the example below.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
+</plain-text-body></structured-macro><p>Once a message's redelivery attempts exceeds the <strong><code>maximumRedeliveries</code></strong> configured for the <link><page ri:content-title="Redelivery Policy"></page></link>, a "Poison ACK" is sent back to the broker letting him know that the message was considered a poison pill. The Broker then takes the message and sends it to a Dead Letter Queue so that it can be analyzed later on.</p><p>The default Dead Letter Queue in ActiveMQ is called <strong><code>ActiveMQ.DLQ</code></strong>; all un-deliverable messages will get sent to this queue and this can be difficult to manage. So, you can set an <strong><code>individualDeadLetterStrategy</code></strong> in the destination policy map of the <strong><code>activemq.xml</code></strong> configuration file, which allows you to specify a specific dead letter queue prefix for a given queue or topic. You can apply this strategy using wild card if you like so that all queues get their own dead-letter queue, as is shown in the example below.</p><structured-macro ac:macro-id="f2c2bbc8-1e76-442a-9ef3-e5cf3e3ce3ce" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><broker>
<destinationPolicy>
<policyMap>
<policyEntries>
- <!-- Set the following policy on all queues using the '>' wildcard -->
- <policyEntry queue=">">
+ <!-- Set the following policy on all queues using the '>' wildcard -->
+ <policyEntry queue=">">
<deadLetterStrategy>
<!--
- Use the prefix 'DLQ.' for the destination name, and make
+ Use the prefix 'DLQ.' for the destination name, and make
the DLQ a queue rather than a topic
-->
- <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true"/>
+ <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true"/>
</deadLetterStrategy>
</policyEntry>
</policyEntries>
@@ -26,22 +23,20 @@
</destinationPolicy>
</broker>
-]]></script>
-</div></div><p>See the <a shape="rect" href="redelivery-policy.xml">Redelivery Policy</a> section for some more detail on the policy options.</p><h3 id="MessageRedeliveryandDLQHandling-AutomaticallyDiscardExpiredMessages">Automatically Discard Expired Messages</h3><p>Some folks simply need expired messages to be discarded instead of sent to the DLQ i.e., skip the DLQ entirely. This simplifies the management of the DLQ so that you're not sifting through loads of expired messages to find messages with real problems. To tell ActiveMQ to just discard expired messages, configure the <strong><code>processExpired</code></strong> property to false on a dead letter strategy:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
+</plain-text-body></structured-macro><p>See the <link><page ri:content-title="Redelivery Policy"></page></link> section for some more detail on the policy options.</p><h3>Automatically Discard Expired Messages</h3><p>Some folks simply need expired messages to be discarded instead of sent to the DLQ i.e., skip the DLQ entirely. This simplifies the management of the DLQ so that you're not sifting through loads of expired messages to find messages with real problems. To tell ActiveMQ to just discard expired messages, configure the <strong><code>processExpired</code></strong> property to false on a dead letter strategy:</p><structured-macro ac:macro-id="a20b65dd-1508-4672-9196-d47d24e52f57" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><broker>
<destinationPolicy>
<policyMap>
<policyEntries>
- <!-- Set the following policy on all queues using the '>' wildcard -->
- <policyEntry queue=">">
+ <!-- Set the following policy on all queues using the '>' wildcard -->
+ <policyEntry queue=">">
<!--
Tell the dead letter strategy not to process expired messages
so that they will just be discarded instead of being sent to
the DLQ
-->
<deadLetterStrategy>
- <sharedDeadLetterStrategy processExpired="false" />
+ <sharedDeadLetterStrategy processExpired="false" />
</deadLetterStrategy>
</policyEntry>
</policyEntries>
@@ -49,21 +44,19 @@
</destinationPolicy>
</broker>
-]]></script>
-</div></div><h3 id="MessageRedeliveryandDLQHandling-PlaceNon-PersistentMessagesOntoTheDead-LetterQueue">Place Non-Persistent Messages Onto The Dead-Letter Queue</h3><p>By default, ActiveMQ will not place undeliverable <em>non-persistent</em> messages on the dead-letter queue. The rationale for this behavior is that if the application doesn't care enough to make the message persistent, then there is little or no value in recording that the message was undeliverable. If you do want to place non-persistent messages on the dead-letter queue, then you should set <strong><code>processNonPersistent="true"</code></strong> on the dead-letter strategy.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
+</plain-text-body></structured-macro><h3>Place Non-Persistent Messages Onto The Dead-Letter Queue</h3><p>By default, ActiveMQ will not place undeliverable <em>non-persistent</em> messages on the dead-letter queue. The rationale for this behavior is that if the application doesn't care enough to make the message persistent, then there is little or no value in recording that the message was undeliverable. If you do want to place non-persistent messages on the dead-letter queue, then you should set <strong><code>processNonPersistent="true"</code></strong> on the dead-letter strategy.</p><structured-macro ac:macro-id="0b7a7c68-1ca5-4778-9f9f-a8580aba6632" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><broker>
- <destinationPolicy>
+  <destinationPolicy>
<policyMap>
<policyEntries>
- <!-- Set the following policy on all queues using the '>' wildcard -->
- <policyEntry queue=">">
+ <!-- Set the following policy on all queues using the '>' wildcard -->
+ <policyEntry queue=">">
<!--
Tell the dead letter strategy to also place non-persisted messages
- onto the dead-letter queue if they can't be delivered.
+ onto the dead-letter queue if they can't be delivered.
-->
<deadLetterStrategy>
- <sharedDeadLetterStrategy processNonPersistent="true" />
+ <sharedDeadLetterStrategy processNonPersistent="true" />
</deadLetterStrategy>
</policyEntry>
</policyEntries>
@@ -71,16 +64,14 @@
</destinationPolicy>
</broker>
-]]></script>
-</div></div><h3 id="MessageRedeliveryandDLQHandling-SettingExpirationonMessagesintheDLQ">Setting Expiration on Messages in the DLQ</h3><p>By default, ActiveMQ will <strong><em>never</em></strong> expire messages sent to the DLQ. However, from ActiveMQ 5.12 the <strong><code>deadLetterStrategy</code></strong> supports an <strong><code>expiration</code></strong> attribute whose value is given in milliseconds.</p><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Be selective in how this is applied. In particular do not apply expiration to your DLQ destinations by setting expiration on a default or inclusive wildcard policy entry.</p><p>If a DLQ entry expires and forwards to the same or another DLQ with expiry, you will introduce a loop that can be problematic if the strategy audit is disabled or it's sliding window is exceeded.</p></div></div><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker>
+</plain-text-body></structured-macro><h3>Setting Expiration on Messages in the DLQ</h3><p>By default, ActiveMQ will <strong><em>never</em></strong> expire messages sent to the DLQ. However, from ActiveMQ 5.12 the <strong><code>deadLetterStrategy</code></strong> supports an <strong><code>expiration</code></strong> attribute whose value is given in milliseconds.</p><structured-macro ac:macro-id="4d8ba42f-e662-4222-97f7-f97a8ca7f4a8" ac:name="warning" ac:schema-version="1"><rich-text-body><p>Be selective in how this is applied. In particular do not apply expiration to your DLQ destinations by setting expiration on a default or inclusive wildcard policy entry.</p><p>If a DLQ entry expires and forwards to the same or another DLQ with expiry, you will introduce a loop that can be problematic if the strategy audit is disabled or it's sliding window is exceeded.</p></rich-text-body></structured-macro><structured-macro ac:macro-id="7dcdda11-0905-4f49-8dcd-62c25e68ee99" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><broker>
- <destinationPolicy>
+  <destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue="QueueWhereItIsOkToExpireDLQEntries">
+ <policyEntry queue="QueueWhereItIsOkToExpireDLQEntries">
<deadLetterStrategy>
- <.... expiration="300000"/>
+ <.... expiration="300000"/>
</deadLetterStrategy>
</policyEntry>
</policyEntries>
@@ -88,64 +79,53 @@
</destinationPolicy>
</broker>
-]]></script>
-</div></div><h3 id="MessageRedeliveryandDLQHandling-Messageaudit">Message audit</h3><p>The dead letter strategy has an message audit that is enabled by default. This prevents duplicate messages from being added to the configured DLQ. From 5.15.0, the limits of the audit can configured via the</p><p><strong>maxProducersToAudit</strong> and <strong>maxAuditDepth</strong> attributes. The audit can be disabled using <strong>enableAudit</strong>="false"</p><p> </p><h3 id="MessageRedeliveryandDLQHandling-TheDiscardingDLQPlugin">The Discarding DLQ Plugin</h3><p> </p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>From ActiveMQ 5.9 - a destination <strong><code>policyEntry</code></strong> supports a <strong><code>deadLetterStrategy</code></strong> of discarding:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<deadLetterStrategy>
+</plain-text-body></structured-macro><h3>Message audit</h3><p>The dead letter strategy has an message audit that is enabled by default. This prevents duplicate messages from being added to the configured DLQ. From 5.15.0, the limits of the audit can configured via the</p><p><strong>maxProducersToAudit</strong> and <strong>maxAuditDepth</strong> attributes. The audit can be disabled using <strong>enableAudit</strong>="false"</p><p> </p><h3>The Discarding DLQ Plugin</h3><p> </p><structured-macro ac:macro-id="4fbc1d0d-3641-4077-ae32-8ac0950ec85a" ac:name="info" ac:schema-version="1"><rich-text-body><p>From ActiveMQ 5.9 - a destination <strong><code>policyEntry</code></strong> supports a <strong><code>deadLetterStrategy</code></strong> of discarding:</p><structured-macro ac:macro-id="c13e0c78-330b-40b9-b200-4752f496c450" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><deadLetterStrategy>
<discarding/>
-</deadLetterStrategy>]]></script>
-</div></div><p>This does the same thing as the plugin but on a per destination basis. The matching based on regular expressions of the plugin is a bit more powerful than destination matching so the plugin may still be useful in some cases.</p></div></div><p> </p><p>A very simple yet very useful plugin to the broker. This plugin allows the configuration of queues and topics, all or matched based on <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html" rel="nofollow">Java SE regular expressions</a>, to drop messages that have been sent to the DLQ. This is extremely useful when using <a shape="rect" href="slow-consumer-handling.xml#SlowConsumerHandling-ConstantPendingMessageLimitStrategy">constant pending message limit strategy</a> or the other eviction rules, but you don't want to incur the overhead of yet another consumer to clear the DLQ.</p><p>Below is an example of a basic configuration to drop everything:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans>
+</deadLetterStrategy></plain-text-body></structured-macro><p>This does the same thing as the plugin but on a per destination basis. The matching based on regular expressions of the plugin is a bit more powerful than destination matching so the plugin may still be useful in some cases.</p></rich-text-body></structured-macro><p> </p><p>A very simple yet very useful plugin to the broker. This plugin allows the configuration of queues and topics, all or matched based on <a shape="rect" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html">Java SE regular expressions</a>, to drop messages that have been sent to the DLQ. This is extremely useful when using <link ac:anchor="ConstantPendingMessageLimitStrategy"><page ri:content-title="Slow Consumer Handling"></page><plain-text-link-body>constant pending message limit strategy</plain-text-link-body></link> or the other eviction rules, but you don't want to incur the overhead of yet another consumer to clear the DLQ.</p><p>Below is an example of a basic configuration to drop everything:</p><structured-macro ac:macro-id="c4908a79-8cb6-43fa-912d-11362ed46321" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><beans>
<broker>
<plugins>
- <discardingDLQBrokerPlugin dropAll="true" dropTemporaryTopics="true" dropTemporaryQueues="true"/>
+ <discardingDLQBrokerPlugin dropAll="true" dropTemporaryTopics="true" dropTemporaryQueues="true"/>
</plugins>
</broker>
</beans>
-]]></script>
-</div></div><p>Below is a slightly more complex example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans>
+</plain-text-body></structured-macro><p>Below is a slightly more complex example:</p><structured-macro ac:macro-id="41570c5e-ab56-436f-b2a9-e37fd96c4b76" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><beans>
<broker>
<plugins>
- <discardingDLQBrokerPlugin dropOnly="MY.EXAMPLE.TOPIC.29 MY.EXAMPLE.QUEUE.87" reportInterval="1000"/>
+ <discardingDLQBrokerPlugin dropOnly="MY.EXAMPLE.TOPIC.29 MY.EXAMPLE.QUEUE.87" reportInterval="1000"/>
</plugins>
</broker>
</beans>
-]]></script>
-</div></div><ul><li>Notice that destination names are space delimited.</li><li>The <strong><code>reportInterval</code></strong> property is used to denote how frequently do we output how many messages we have dropped - use <strong><code>0</code></strong> to disable.</li></ul><p>Below is an even more complex example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans>
+</plain-text-body></structured-macro><ul><li>Notice that destination names are space delimited.</li><li>The <strong><code>reportInterval</code></strong> property is used to denote how frequently do we output how many messages we have dropped - use <strong><code>0</code></strong> to disable.</li></ul><p>Below is an even more complex example:</p><structured-macro ac:macro-id="0283648e-4110-4864-a6ad-ecde61a2bde9" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><beans>
<broker>
<plugins>
- <discardingDLQBrokerPlugin dropOnly="MY.EXAMPLE.TOPIC.[0-9]{3} MY.EXAMPLE.QUEUE.[0-9]{3}" reportInterval="3000"/>
+ <discardingDLQBrokerPlugin dropOnly="MY.EXAMPLE.TOPIC.[0-9]{3} MY.EXAMPLE.QUEUE.[0-9]{3}" reportInterval="3000"/>
</plugins>
</broker>
</beans>
-]]></script>
-</div></div><ul><li>Notice that the destination names use regular expressions. These match the number <strong><code>000..999</code></strong> at the end of each destination name.</li></ul><p>For more information, see the source code for the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/plugin/DiscardingDLQBrokerPlugin.java">DiscardingDLQBrokerPlugin</a> and the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/plugin/DiscardingDLQBroker.java">DiscardingDLQBroker</a></p><h3 id="MessageRedeliveryandDLQHandling-BrokerRedelivery(v5.7)">Broker Redelivery (v5.7)</h3><p>Typically a consumer handles redelivery so that it can maintain message order while a message appears as inflight on the broker. This means that redelivery is limited to a single consumer unless that consumer terminates. In this way the broker is unaware of redelivery. With broker redelivery, it is possible to have the broker redeliver a message after a delay using a resend. This is implemented by a broker plugin that handles dead letter processing by redelivery via the scheduler. This is useful when total message order is not important and where through put and load distribution among consumers is. With broker redelivery, messages that fail delivery to a given consumer can get immediately re-dispatched.</p><p><br clear="none"> The feature is enabled via XML configuration as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker schedulerSupport="true">
+</plain-text-body></structured-macro><ul><li>Notice that the destination names use regular expressions. These match the number <strong><code>000..999</code></strong> at the end of each destination name.</li></ul><p>For more information, see the source code for the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/plugin/DiscardingDLQBrokerPlugin.java">DiscardingDLQBrokerPlugin</a> and the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/plugin/DiscardingDLQBroker.java">DiscardingDLQBroker</a></p><h3>Broker Redelivery (v5.7)</h3><p>Typically a consumer handles redelivery so that it can maintain message order while a message appears as inflight on the broker. This means that redelivery is limited to a single consumer unless that consumer terminates. In this way the broker is unaware of redelivery. With broker redelivery, it is possible to have the broker redeliver a message after a delay using a resend. This is implemented by a broker plugin that handles dead letter processing by redelivery via the scheduler. This is useful when total message order is not important and where through put and load distribution among consumers is. With broker redelivery, messages that fail delivery to a given consumer can get immediately re-dispatched.</p><p><br clear="none"> The feature is enabled via XML configuration as follows:</p><structured-macro ac:macro-id="e54406f7-804d-4f49-b2c6-223c722e968f" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><broker schedulerSupport="true">
<plugins>
- <redeliveryPlugin fallbackToDeadLetter="true"
- sendToDlqIfMaxRetriesExceeded="true">
+ <redeliveryPlugin fallbackToDeadLetter="true"
+ sendToDlqIfMaxRetriesExceeded="true">
<redeliveryPolicyMap>
<redeliveryPolicyMap>
<redeliveryPolicyEntries>
<!-- a destination specific policy -->
- <redeliveryPolicy queue="SpecialQueue"
- maximumRedeliveries="4"
- redeliveryDelay="10000"/>
+ <redeliveryPolicy queue="SpecialQueue"
+ maximumRedeliveries="4"
+ redeliveryDelay="10000"/>
</redeliveryPolicyEntries>
-
+  
<defaultEntry>
<!-- the fallback policy for all other destinations -->
- <redeliveryPolicy maximumRedeliveries="4"
- initialRedeliveryDelay="5000"
- redeliveryDelay="10000"/>
+   <redeliveryPolicy maximumRedeliveries="4"
+ initialRedeliveryDelay="5000"
+ redeliveryDelay="10000"/>
</defaultEntry>
</redeliveryPolicyMap>
</redeliveryPolicyMap>
</redeliveryPlugin>
</plugins>
-</broker> ]]></script>
-</div></div><p>The familiar <a shape="rect" href="redelivery-policy.xml">Redelivery Policy</a> has been extended to take a matching destination. <strong><code>fallbackToDeadLetter</code></strong>controls the action when there is no matching redeliver policy for a destination. Defaults to <strong><code>true</code></strong> so regular DLQ processing ensues. <strong><code>sendToDlqIfMaxRetriesExceeded</code></strong> controls the action when the retry limit is exceeded. Defaults to true so regular DLQ processing ensues. When <strong><code>false</code></strong>, the message is dropped.</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">ActiveMQ's <strong><code>schedulerSupport</code></strong> must be enabled for this feature to work.</div></div></div>
+</broker> </plain-text-body></structured-macro><p>The familiar <link><page ri:content-title="Redelivery Policy"></page></link> has been extended to take a matching destination. <strong><code>fallbackToDeadLetter</code></strong>controls the action when there is no matching redeliver policy for a destination. Defaults to <strong><code>true</code></strong> so regular DLQ processing ensues. <strong><code>sendToDlqIfMaxRetriesExceeded</code></strong> controls the action when the retry limit is exceeded. Defaults to true so regular DLQ processing ensues. When <strong><code>false</code></strong>, the message is dropped.</p><structured-macro ac:macro-id="8f9318e9-8196-4788-a17e-f66a932c612f" ac:name="info" ac:schema-version="1"><rich-text-body>ActiveMQ's <strong><code>schedulerSupport</code></strong> must be enabled for this feature to work.</rich-text-body></structured-macro></div>
diff --git a/message-transformation.xml b/message-transformation.xml
index 06f3dca..7d6a9b2 100644
--- a/message-transformation.xml
+++ b/message-transformation.xml
@@ -1,21 +1,21 @@
-<div class="wiki-content maincontent"><h2 id="MessageTransformation-MessageTransformation">Message Transformation</h2>
+<div class="wiki-content maincontent"><h2>Message Transformation</h2>
<p>It is sometimes useful to transform a message inside the JMS provider. For example you may have an application that has been live for some time that uses ObjectMessage messages, but that you wish to convert to use XML payloads (to protect yourself from serialization issues).</p>
-<p>So ActiveMQ in 4.2 onwards comes with a pluggable strategy called the <a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/MessageTransformer.html">MessageTransformer</a> interface. This allows you to</p>
+<p>So ActiveMQ in 4.2 onwards comes with a pluggable strategy called the <a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/MessageTransformer.html">MessageTransformer</a> interface. This allows you to</p>
<ul><li>enrich or transform a message before it is sent to the message bus within the JMS provider</li><li>enrich or transform a message as it is received from the message bus but before it is dispatched to the consumer</li></ul>
-<p>So this allows you to turn an ObjectMessage into a TextMessage containing XML using some kind of XML marshalling technology like <a shape="rect" class="external-link" href="http://xstream.codehaus.org/" rel="nofollow">XStream</a> or <a shape="rect" class="external-link" href="http://java.sun.com/webservices/jaxb/" rel="nofollow">JAXB2</a>.</p>
+<p>So this allows you to turn an ObjectMessage into a TextMessage containing XML using some kind of XML marshalling technology like <a shape="rect" href="http://xstream.codehaus.org/">XStream</a> or <a shape="rect" href="http://java.sun.com/webservices/jaxb/">JAXB2</a>.</p>
<p>For example there is the <strong>XStreamMessageTransformer</strong> which when it is configured on a ConnectionFactory will cause all ObjectMessage instances to be silently transformed to and from TextMessage instances on the wire. This can be very useful if you have non-Java clients wishing to communicate with your Java messages.</p>
-<h3 id="MessageTransformation-UsingaMessageTransformer">Using a MessageTransformer</h3>
+<h3>Using a MessageTransformer</h3>
<p>To use a MessageTransformer you can install it on one of the following classes via the <strong>setTransformer()</strong> method</p>
-<ul><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnectionFactory</a></li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a></li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQSession.html">ActiveMQSession</a></li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQMessageConsumer.html">ActiveMQMessageConsumer</a></li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQMessageProducer.html">ActiveMQMessageProducer</a></li></ul>
+<ul><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnectionFactory</a></li><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html">ActiveMQConnection</a></li><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQSession.html">ActiveMQSession</a></li><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQMessageConsumer.html">ActiveMQMessageConsumer</a></li><li><a shape="rect" href="http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQMessageProducer.html">ActiveMQMessageProducer</a></li></ul>
<p>The transformer is inherited on child objects; so you can install a particular transformer on a connection factory and it will be inherited on all connections, sessions, producers, consumers</p></div>
diff --git a/mirrored-queues.xml b/mirrored-queues.xml
index a7f52fc..2dc4f64 100644
--- a/mirrored-queues.xml
+++ b/mirrored-queues.xml
@@ -1,40 +1,39 @@
-<div class="wiki-content maincontent"><h2 id="MirroredQueues-MirroredQueues">Mirrored Queues</h2>
+<div class="wiki-content maincontent"><h2>Mirrored Queues</h2>
-<p>Queues provide an excellent reliable and high performance <a shape="rect" href="how-does-a-queue-compare-to-a-topic.xml">load balancing mechanism</a>. Each message placed on a queue can only be successfully processed by a single consumer. This is a good thing! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">. However sometimes you want to monitor what messages flow between the producers and consumers on a queue. </p>
+<p>Queues provide an excellent reliable and high performance <link><page ri:content-title="How does a Queue compare to a Topic"></page><link-body>load balancing mechanism</link-body></link>. Each message placed on a queue can only be successfully processed by a single consumer. This is a good thing! <emoticon ac:name="smile"></emoticon>. However sometimes you want to monitor what messages flow between the producers and consumers on a queue. </p>
-<p>To do this you can use <a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a> to setup a virtual Queue which forwards the message to multiple physical queues. However enabling this for every single queue in your system can be painful.</p>
+<p>To do this you can use <link><page ri:content-title="Virtual Destinations"></page></link> to setup a virtual Queue which forwards the message to multiple physical queues. However enabling this for every single queue in your system can be painful.</p>
-<p>So to make it easy to monitor queues, we have added a feature we call <em>Mirrored Queues</em>. Mirrored Queues are kinda like a zero-configuration <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/wire-tap.html">Wire Tap</a> on all of your queues inside your Message Broker.</p>
+<p>So to make it easy to monitor queues, we have added a feature we call <em>Mirrored Queues</em>. Mirrored Queues are kinda like a zero-configuration <a shape="rect" href="http://activemq.apache.org/camel/wire-tap.html">Wire Tap</a> on all of your queues inside your Message Broker.</p>
-<h3 id="MirroredQueues-Example">Example</h3>
+<h3>Example</h3>
<p>For example imagine we have a number of producers sending to queue <strong>Foo.Bar</strong> and consumers consuming from queue <strong>Foo.Bar</strong> and we want to monitor or view activity. </p>
<p>If you enable Mirrored Queues then by default you can subscribe to the topic <strong>VirtualTopic.Mirror.Foo.Bar</strong> and receive all the messages that are sent to the queue <strong>Foo.Bar</strong>. Since its a topic as many consumers can subscribe to this topic as are required.</p>
-<p>If you want you can use this feature with <a shape="rect" href="virtual-destinations.xml">Virtual Topics</a>; so that you can define a logical consumer; say called A. Then you can subscribe to the queue <strong>Consumer.A.VirtualTopic.Mirror.Foo.Bar</strong> to receive all the messages sent to queue <strong>Foo.Bar</strong> for the consumer A. You can then run multiple instances of this consumer who can then load balance among each other.</p>
+<p>If you want you can use this feature with <link><page ri:content-title="Virtual Destinations"></page><link-body>Virtual Topics</link-body></link>; so that you can define a logical consumer; say called A. Then you can subscribe to the queue <strong>Consumer.A.VirtualTopic.Mirror.Foo.Bar</strong> to receive all the messages sent to queue <strong>Foo.Bar</strong> for the consumer A. You can then run multiple instances of this consumer who can then load balance among each other.</p>
-<p>This combination of Mirrored Queues and <a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a> can be extremely useful for monitoring transaction flows; for example with <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/bam.html">Business Activity Monitoring (BAM)</a>.</p>
+<p>This combination of Mirrored Queues and <link><page ri:content-title="Virtual Destinations"></page></link> can be extremely useful for monitoring transaction flows; for example with <a shape="rect" href="http://activemq.apache.org/camel/bam.html">Business Activity Monitoring (BAM)</a>.</p>
-<h3 id="MirroredQueues-HowMirroredQueueswork">How Mirrored Queues work</h3>
+<h3>How Mirrored Queues work</h3>
<p>When enabled, mirrored queues causes every message sent to a queue to also be sent to a topic of a similar name; so that folks who are interested in watching message exchanges on a queue can consume from the mirrored queue topic.</p>
-<p>When coupled with <a shape="rect" href="virtual-destinations.xml">Virtual Topics</a> on this topic as described in the above example, you can actually end up creating new queues which are mirrors of a given queue dynamically at runtime!</p>
+<p>When coupled with <link><page ri:content-title="Virtual Destinations"></page><link-body>Virtual Topics</link-body></link> on this topic as described in the above example, you can actually end up creating new queues which are mirrors of a given queue dynamically at runtime!</p>
-<h3 id="MirroredQueues-EnablingMirroredQueues">Enabling Mirrored Queues</h3>
+<h3>Enabling Mirrored Queues</h3>
<p>By default Mirrored Queues is disabled; as enabling it will cause a virtual topic to be created for each queue you use.</p>
-<p>To enable Mirrored Queues, set the <strong>useMirroredQueues</strong> property on <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerService.html">BrokerService</a> or add the following inside the <broker> element in the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>:</p>
+<p>To enable Mirrored Queues, set the <strong>useMirroredQueues</strong> property on <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerService.html">BrokerService</a> or add the following inside the <broker> element in the <link><page ri:content-title="Xml Configuration"></page></link>:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e151574b-2698-4924-882f-aebcb96befd4" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<destinationInterceptors>
- <mirroredQueue copyMessage = "true" postfix=".qmirror" prefix=""/>
+ <mirroredQueue copyMessage = "true" postfix=".qmirror" prefix=""/>
</destinationInterceptors>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>This would make a topic named "*.qmirror" for each queue on your Broker.</p></div>
+<p>This would make a topic named "*.qmirror" for each queue on your Broker.</p>
+</div>
diff --git a/monitoring-activemq.xml b/monitoring-activemq.xml
index 51ce618..9375a8d 100644
--- a/monitoring-activemq.xml
+++ b/monitoring-activemq.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>You can monitor ActiveMQ using the <a shape="rect" href="web-console.xml">Web Console</a> by pointing your browser at</p><p><a shape="rect" class="external-link" href="http://localhost:8161/admin" rel="nofollow">http://localhost:8161/admin</a></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>From ActiveMQ 5.8 onwards the web apps is secured out of the box.<br clear="none"> The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.</p></div></div><p>Or you can use the <a shape="rect" href="jmx.xml">JMX</a> support to view the running state of ActiveMQ.</p><p>For more information see the file <code>docs/WebConsole-README.txt</code> in the distribution.</p></div>
+<div class="wiki-content maincontent"><p>You can monitor ActiveMQ using the <link><page ri:content-title="Web Console"></page></link> by pointing your browser at</p><p><a shape="rect" class="external-link" href="http://localhost:8161/admin" rel="nofollow">http://localhost:8161/admin</a></p><structured-macro ac:macro-id="d8ae687d-5080-43db-ad1d-f50f80302f07" ac:name="info" ac:schema-version="1"><parameter ac:name="">login</parameter><rich-text-body><p>From ActiveMQ 5.8 onwards the web apps is secured out of the box.<br clear="none"> The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.</p></rich-text-body></structured-macro><p>Or you can use the <link><page ri:content-title="JMX"></page></link> support to view the running state of ActiveMQ.</p><p>For more information see the file <code>docs/WebConsole-README.txt</code> in the distribution.</p></div>
diff --git a/mqtt.xml b/mqtt.xml
index b7d340e..7e02e46 100644
--- a/mqtt.xml
+++ b/mqtt.xml
@@ -1,21 +1,7 @@
-<div class="wiki-content maincontent"><p>ActiveMQ supports the <a shape="rect" class="external-link" href="http://mqtt.org/" rel="nofollow">MQTT</a> protocol and will automatically map between JMS/NMS and MQTT clients. MQTT is a machine-to-machine (M2M) publish/subscribe messaging transport.</p><p>Please see the <a shape="rect" class="external-link" href="http://mqtt.org/" rel="nofollow">MQTT site</a> for more details</p><h3 id="MQTT-EnablingtheActiveMQBrokerforMQTT">Enabling the ActiveMQ Broker for MQTT</h3><p>Its very easy to enable ActiveMQ for MQTT. Just add a connector to the broker using the MQTT URL.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnectors>
- <transportConnector name="mqtt" uri="mqtt://localhost:1883"/>
+<div class="wiki-content maincontent"><p>ActiveMQ supports the <a shape="rect" href="http://mqtt.org/">MQTT</a> protocol and will automatically map between JMS/NMS and MQTT clients. MQTT is a machine-to-machine (M2M) publish/subscribe messaging transport.</p><p>Please see the <a shape="rect" href="http://mqtt.org/">MQTT site</a> for more details</p><h3>Enabling the ActiveMQ Broker for MQTT</h3><p>Its very easy to enable ActiveMQ for MQTT. Just add a connector to the broker using the MQTT URL.</p><structured-macro ac:macro-id="5ca47482-4078-4d5b-8aa5-c5d38fd2ce38" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnectors>
+ <transportConnector name="mqtt" uri="mqtt://localhost:1883"/>
</transportConnectors>
-]]></script>
-</div></div><h3 id="MQTT-TheMQTTWireFormat">The MQTT Wire Format</h3><p>MQTT uses a compact binary format that can be configured with the following options.  All options can be configured on a Brokers transport bind URI.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter 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>maxFrameSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>268435456</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(v5.12.0) Maximum frame size that can be sent. The protocol limit is 256 megabytes and his value cannot be set higher. Can help help prevent OOM DOS attacks</p></td></tr></tbody></table></div><p>All options must be prepended with <code>wireFormat</code> in order to take effect. Without this proper formatting, the option will have zero effect.</p><h4 id="MQTT-ExampleWireFormatConfiguration">Example Wire Format Configuration<br clear="none"> </h4><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="mqtt" uri="mqtt://localhost:61612?wireFormat.maxFrameSize=100000"/>]]></script>
-</div></div><h3 id="MQTT-Security">Security</h3><p>The ActiveMQ MQTT Transport implementation fully supports an <a shape="rect" href="security.xml">ActiveMQ security</a> mechanism. Also, the authorization policies will be applied when you try to access (read/write) certain destinations.</p><h3 id="MQTT-EnablingMQTToverNIO">Enabling MQTT over NIO</h3><p>For better scalability (and performance) you might want to run the MQTT protocol over NIO transport. To do that just use <code>mqtt+nio</code> transport prefix instead of <code>matt</code>. For example, add the following transport configuration in your XML file</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="mqtt+nio" uri="mqtt+nio://localhost:1883"/>
-]]></script>
-</div></div><p>This transport use <a shape="rect" class="external-link" href="http://activemq.apache.org/configuring-transports.html#ConfiguringTransports-TheNIOTransport">NIO transport</a> underneath and will generally use much less threads than standard connector.</p><h3 id="MQTT-EnablingMQTToverNIO+SSL">Enabling MQTT over NIO + SSL</h3><p>The MQTT transport also supports using NIO and SSL. To enable this option, use the mqtt+nio+ssl protocol - e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <transportConnector name="mqtt+nio" uri="mqtt+nio+ssl://localhost:1883"/>
-]]></script>
-</div></div><ul><li>For more details on using SSL with ActiveMQ see the following article (<a shape="rect" class="external-link" href="http://activemq.apache.org/how-do-i-use-ssl.html">How do I use SSL</a>).</li></ul><h3 id="MQTT-WorkingwithDestinationswithMQTT">Working with Destinations with MQTT</h3><p>MQTT supports hierarchies and wildcards, though the delimiters and characters are different: - Here's the mapping:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>function</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>ActiveMQ</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>MQTT</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>separator</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>.</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>/</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>element</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>+<br clear="none"></code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>sub tree</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>#<br clear="none"></code></p></td></tr></tbody></table></div><p>These values are automatically transposed between clients using JMS/NMS/Stomp and clients using MQTTT. For example - a client subscribing to "foo/#/bar" would receive messages published on a JMS Topic of foo.blah.bar.</p><h3 id="MQTT-Messagetransformations">Message transformations</h3><p>MQTT messages are transformed into an JMS ByteMessage. Conversely, the body of any JMS Message is converted to a byte buffer to be the payload of an MQTT message.</p><h3 id="MQTT-KeepAlive">Keep Alive</h3><p>When a client connects, it will send a keep-alive duration, usually defaulting to 10s. ActiveMQ will honor the keep-alive duration by setting up an Inactivity Monitor that allows a grace period of 1.5 * duration. After that grace period duration elapses a connection could be closed if there is no activity. A broker receiving a PINGREQ and sending PINGRESP is considered activity to keep the connection opened.</p><p>If a client sends a keep-alive value of 0, ActiveMQ will not set up an <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-inactivitymonitor.html">Inactivity Monitor</a> and connections will not be auto-shutdown due to inactivity. This however can lead to potentially leaky connections, so a default keep alive can be set on the server side (by an admin, for example) to not allow inactive connections to hang. This default keep alive would only be used if specified and if the client requests a keep-alive value of 0. The unit for the keep-alive value is milliseconds.</p><p>To enable a default, server-side MQTT keep alive:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="mqtt" uri="mqtt://localhost:1883?transport.defaultKeepAlive=60000"/>]]></script>
-</div></div><h3 id="MQTT-MessagePrefetch">Message Prefetch</h3><p>When MQTT client connects, it locally create JMS-like consumer to the broker. In older versions this consumer was created with the prefetch size of 1 (message prefetching is explained <a shape="rect" href="what-is-the-prefetch-limit-for.xml">here</a> in more details). Starting with 5.11.0 release, the prefetch size is adjusted to the default value for the appropriate JMS subscription. QoS=0 subscriptions have default prefetch of regular non-persistent topic subscriptions, while QoS=1 and QoS=2 are assigned prefetch size of durable subscribers or the queue subscriptions depending on the subscription strategy used (see the next section for more details). Default prefetch values are listed <a shape="rect" href="what-is-the-prefetch-limit-for.xml">here</a>.</p><p>To change default value of the prefetch size, you can use <em>activeMQSubscriptionPrefetch</em> transport option, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="mqtt" uri="mqtt://localhost:1883?transport.activeMQSubscriptionPrefetch=32766"/>]]></script>
-</div></div><h3 id="MQTT-SubscriptionStrategy">Subscription Strategy</h3><p>ActiveMQ is a JMS broker in its core, so there needs to be some mapping between MQTT subscriptions and JMS semantics. Subscriptions with QoS=0 (At Most Once) are directly mapped to plain JMS non-persistent topics. For reliable messaging, QoS=1 and QoS=2, by default subscriptions are transformed to JMS durable topic subscribers. This behaviour is desired in most scenarios. For some use cases, it is useful to map these subscriptions to <a shape="rect" href="virtual-destinations.xml">virtual topics</a>. Virtual topics provide a better scalability and are generally better solution if you want to use you MQTT subscribers over network of brokers. To change subscription strategy to use virtual topic, use the following settings:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="mqtt" uri="mqtt://localhost:1883?transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions"/>]]></script>
-</div></div><h3 id="MQTT-RetainedMessages">Retained Messages</h3><p>If a message has been published with the <em>retain</em> flag set, then the message will be 'remembered' by the topic so that if a new subscription arrives, the last retained message is sent to the subscription. Underneath, the broker uses <a shape="rect" href="subscription-recovery-policy.xml">retained message subscription recovery policy</a> to retain messages with <em>ActiveMQ.Retain</em> property set. During the message conversion, MQTT messages with retain flag become JMS message with the <em>ActiveMQ.Retain </em>property set and retained by the broker.</p></div>
+</plain-text-body></structured-macro><h3>The MQTT Wire Format</h3><p>MQTT uses a compact binary format that can be configured with the following options.  All options can be configured on a Brokers transport bind URI.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Parameter Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>maxFrameSize</p></td><td colspan="1" rowspan="1"><p>268435456</p></td><td colspan="1" rowspan="1"><p>(v5.12.0) Maximum frame size that can be sent. The protocol limit is 256 megabytes and his value cannot be set higher. Can help help prevent OOM DOS attacks</p></td></tr></tbody></table><p>All options must be prepended with <code>wireFormat</code> in order to take effect. Without this proper formatting, the option will have zero effect.</p><h4>Example Wire Format Configuration<br clear="none"> </h4><structured-macro ac:macro-id="f4b97772-e19f-4dcd-953f-1e24e1cdcddb" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="mqtt" uri="mqtt://localhost:61612?wireFormat.maxFrameSize=100000"/></plain-text-body></structured-macro><h3>Security</h3><p>The ActiveMQ MQTT Transport implementation fully supports an <link><page ri:content-title="Security"></page><plain-text-link-body>ActiveMQ security</plain-text-link-body></link> mechanism. Also, the authorization policies will be applied when you try to access (read/write) certain destinations.</p><h3>Enabling MQTT over NIO</h3><p>For better scalability (and performance) you might want to run the MQTT protocol over NIO transport. To do that just use <code>mqtt+nio</code> transport prefix instead of <code>matt</code>. For example, add the following transport configuration in your XML file</p><structured-macro ac:macro-id="3f6debc9-051a-489c-8da4-bf2aa33a92e6" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="mqtt+nio" uri="mqtt+nio://localhost:1883"/>
+</plain-text-body></structured-macro><p>This transport use <a shape="rect" href="http://activemq.apache.org/configuring-transports.html#ConfiguringTransports-TheNIOTransport">NIO transport</a> underneath and will generally use much less threads than standard connector.</p><h3>Enabling MQTT over NIO + SSL</h3><p>The MQTT transport also supports using NIO and SSL. To enable this option, use the mqtt+nio+ssl protocol - e.g.</p><structured-macro ac:macro-id="83b650b0-944c-44ec-b16f-b19f9a4d7a91" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <transportConnector name="mqtt+nio" uri="mqtt+nio+ssl://localhost:1883"/>
+</plain-text-body></structured-macro><ul><li>For more details on using SSL with ActiveMQ see the following article (<a shape="rect" href="http://activemq.apache.org/how-do-i-use-ssl.html">How do I use SSL</a>).</li></ul><h3>Working with Destinations with MQTT</h3><p>MQTT supports hierarchies and wildcards, though the delimiters and characters are different: - Here's the mapping:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>function</p></th><th colspan="1" rowspan="1"><p>ActiveMQ</p></th><th colspan="1" rowspan="1"><p>MQTT</p></th></tr><tr><td colspan="1" rowspan="1"><p>separator</p></td><td colspan="1" rowspan="1"><p><code>.</code></p></td><td colspan="1" rowspan="1"><p><code>/</code></p></td></tr><tr><td colspan="1" rowspan="1"><p>element</p></td><td colspan="1" rowspan="1"><p><code>*</code></p></td><td colspan="1" rowspan="1"><p><code>+<br clear="none"></code></p></td></tr><tr><td colspan="1" rowspan="1"><p>sub tree</p></td><td colspan="1" rowspan="1"><p><code>></code></p></td><td colspan="1" rowspan="1"><p><code>#<br clear="none"></code></p></td></tr></tbody></table><p>These values are automatically transposed between clients using JMS/NMS/Stomp and clients using MQTTT. For example - a client subscribing to "foo/#/bar" would receive messages published on a JMS Topic of foo.blah.bar.</p><h3>Message transformations</h3><p>MQTT messages are transformed into an JMS ByteMessage. Conversely, the body of any JMS Message is converted to a byte buffer to be the payload of an MQTT message.</p><h3>Keep Alive</h3><p>When a client connects, it will send a keep-alive duration, usually defaulting to 10s. ActiveMQ will honor the keep-alive duration by setting up an Inactivity Monitor that allows a grace period of 1.5 * duration. After that grace period duration elapses a connection could be closed if there is no activity. A broker receiving a PINGREQ and sending PINGRESP is considered activity to keep the connection opened.</p><p>If a client sends a keep-alive value of 0, ActiveMQ will not set up an <a shape="rect" href="http://activemq.apache.org/activemq-inactivitymonitor.html">Inactivity Monitor</a> and connections will not be auto-shutdown due to inactivity. This however can lead to potentially leaky connections, so a default keep alive can be set on the server side (by an admin, for example) to not allow inactive connections to hang. This default keep alive would only be used if specified and if the client requests a keep-alive value of 0. The unit for the keep-alive value is milliseconds.</p><p>To enable a default, server-side MQTT keep alive:</p><structured-macro ac:macro-id="a20c277a-bf57-4cc0-99b0-0cd758bd8ba0" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnector name="mqtt" uri="mqtt://localhost:1883?transport.defaultKeepAlive=60000"/></plain-text-body></structured-macro><h3>Message Prefetch</h3><p>When MQTT client connects, it locally create JMS-like consumer to the broker. In older versions this consumer was created with the prefetch size of 1 (message prefetching is explained <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>here</plain-text-link-body></link> in more details). Starting with 5.11.0 release, the prefetch size is adjusted to the default value for the appropriate JMS subscription. QoS=0 subscriptions have default prefetch of regular non-persistent topic subscriptions, while QoS=1 and QoS=2 are assigned prefetch size of durable subscribers or the queue subscriptions depending on the subscription strategy used (see the next section for more details). Default prefetch values are listed <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>here</plain-text-link-body></link>.</p><p>To change default value of the prefetch size, you can use <em>activeMQSubscriptionPrefetch</em> transport option, like</p><structured-macro ac:macro-id="69dfafe2-0ff1-4fdd-9d14-90f22a1fd44f" ac:name="code" ac:schema-version="1"><plain-text-body><transportConnector name="mqtt" uri="mqtt://localhost:1883?transport.activeMQSubscriptionPrefetch=32766"/></plain-text-body></structured-macro><h3>Subscription Strategy</h3><p>ActiveMQ is a JMS broker in its core, so there needs to be some mapping between MQTT subscriptions and JMS semantics. Subscriptions with QoS=0 (At Most Once) are directly mapped to plain JMS non-persistent topics. For reliable messaging, QoS=1 and QoS=2, by default subscriptions are transformed to JMS durable topic subscribers. This behaviour is desired in most scenarios. For some use cases, it is useful to map these subscriptions to <link><page ri:content-title="Virtual Destinations"></page><plain-text-link-body>virtual topics</plain-text-link-body></link>. Virtual topics provide a better scalability and are generally better solution if you want to use you MQTT subscribers over network of brokers. To change subscription strategy to use virtual topic, use the following settings:</p><structured-macro ac:macro-id="cd76f597-a8ac-46b9-94ed-9ea6ed141e6b" ac:name="code" ac:schema-version="1"><plain-text-body><transportConnector name="mqtt" uri="mqtt://localhost:1883?transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions"/></plain-text-body></structured-macro><h3>Retained Messages</h3><p>If a message has been published with the <em>retain</em> flag set, then the message will be 'remembered' by the topic so that if a new subscription arrives, the last retained message is sent to the subscription. Underneath, the broker uses <link><page ri:content-title="Subscription Recovery Policy"></page><plain-text-link-body>retained message subscription recovery policy</plain-text-link-body></link> to retain messages with <em>ActiveMQ.Retain</em> property set. During the message conversion, MQTT messages with retain flag become JMS message with the <em>ActiveMQ.Retain </em>property set and retained by the broker.</p></div>
diff --git a/multicast-transport-reference.xml b/multicast-transport-reference.xml
index 8387e87..25d37d6 100644
--- a/multicast-transport-reference.xml
+++ b/multicast-transport-reference.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><h3 id="MulticastTransportReference-TheMulticastTransport">The Multicast Transport</h3>
+<div class="wiki-content maincontent"><h3>The Multicast Transport</h3>
<p>The Multicast transport allows clients to connect to a remote ActiveMQ broker using multicast</p>
<p>Note that by default Multicast is not reliable; datagrams can be lost so you should add a reliability layer to ensure the JMS contract can be implemented on a non-reliable transport.</p>
-<h4 id="MulticastTransportReference-ConfigurationSyntax">Configuration Syntax</h4>
+<h4>Configuration Syntax</h4>
<p><strong>multicast://address:port?transportOptions</strong></p>
-<h5 id="MulticastTransportReference-TransportOptions">Transport Options</h5>
+<h5>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> group </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> default </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> specify a unique group name that can segregate multicast traffic</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> minmumWireFormatVersion </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The minimum version wireformat that is allowed </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> trace </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Causes all commands that are sent over the transport to be logged </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useLocalHost </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When true, it causes the local machines name to resolve to "localhost". </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> datagramSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 4 * 1024 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the size of a datagram </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> timeToLive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> -1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The time to live of datagrams. Set greater than 1 to send packets beyond the local network. (<strong>NOTE:</strong> This won't work for IPv4 addresses without setting the property <code>java.net.preferIPv4Stack=true</code>. For more info see the <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/guide/net/ipv6_guide/index.html" rel="nofollow">IPv6 User Guide for JDK</a>) </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> loopBackMode </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should loopback mode be used </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> default </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The name of the WireFormat to use </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> All the properties with this prefix are used to configure the wireFormat. See <a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a> for more information </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default Value </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> group </p></td><td colspan="1" rowspan="1"><p> default </p></td><td colspan="1" rowspan="1"><p> specify a unique group name that can segregate multicast traffic</p></td></tr><tr><td colspan="1" rowspan="1"><p> minmumWireFormatVersion </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> The minimum version wireformat that is allowed </p></td></tr><tr><td colspan="1" rowspan="1"><p> trace </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Causes all commands that are sent over the transport to be logged </p></td></tr><tr><td colspan="1" rowspan="1"><p> useLocalHost </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> When true, it causes the local machines name to resolve to "localhost". </p></td></tr><tr><td colspan="1" rowspan="1"><p> datagramSize </p></td><td colspan="1" rowspan="1"><p> 4 * 1024 </p></td><td colspan="1" rowspan="1"><p> Specifies the size of a datagram </p></td></tr><tr><td colspan="1" rowspan="1"><p> timeToLive </p></td><td colspan="1" rowspan="1"><p> -1 </p></td><td colspan="1" rowspan="1"><p> The time to live of datagrams. Set greater than 1 to send packets beyond the local network. (<strong>NOTE:</strong> This won't work for IPv4 addresses without setting the property <code>java.net.preferIPv4Stack=true</code>. For more info see the <a shape="rect" href="http://java.sun.com/j2se/1.5.0/docs/guide/net/ipv6_guide/index.html">IPv6 User Guide for JDK</a>) </p></td></tr><tr><td colspan="1" rowspan="1"><p> loopBackMode </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should loopback mode be used </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat </p></td><td colspan="1" rowspan="1"><p> default </p></td><td colspan="1" rowspan="1"><p> The name of the WireFormat to use </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.* </p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p> All the properties with this prefix are used to configure the wireFormat. See <link><page ri:content-title="Configuring Wire Formats"></page></link> for more information </p></td></tr></tbody></table>
-<h5 id="MulticastTransportReference-ExampleURIs">Example URIs</h5>
+<h5>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 shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/transport/discovery/multicast/MulticastDiscoveryAgent.html#DEFAULT_DISCOVERY_URI_STRING">MulticastDiscoveryAgent</a> use</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>multicast://default
-</pre>
-</div></div>
+<p>To use the default value of "multicast://239.255.2.3:6155" with a default multicast group name of "default" from <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/transport/discovery/multicast/MulticastDiscoveryAgent.html#DEFAULT_DISCOVERY_URI_STRING">MulticastDiscoveryAgent</a> use</p>
+<structured-macro ac:macro-id="beb72716-5581-4aa8-aa3b-b4ba539bc46b" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+multicast://default
+</plain-text-body></structured-macro>
<p>To specify the IP address and port use</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>multicast://224.1.2.3:6255
-</pre>
-</div></div>
+<structured-macro ac:macro-id="337fa52e-2268-47df-8144-af7d474ee78a" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+multicast://224.1.2.3:6255
+</plain-text-body></structured-macro>
<p>To specify a multicast group name other than the default name of "default" use</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>multicast://224.1.2.3:6255?group=mygroupname
-</pre>
-</div></div></div>
+<structured-macro ac:macro-id="5c85602f-728c-4657-b2c5-a1e3bd745860" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+multicast://224.1.2.3:6255?group=mygroupname
+</plain-text-body></structured-macro></div>
diff --git a/multicast-transport.xml b/multicast-transport.xml
index 87ec73f..32b7e13 100644
--- a/multicast-transport.xml
+++ b/multicast-transport.xml
@@ -8,8 +8,9 @@
<p>So the brokers communicate with a kind of Bridge which uses the multicast/UDP transports underneath.</p>
-<h3 id="MulticastTransport-Brokerkeep-alive">Broker keep-alive</h3>
+<h3>Broker keep-alive</h3>
<p>Each broker will repeatedly send its own BrokerInfo to the cloud. The MulticastBridge will receive them and keep that broker alive; brokers which don't send the brokerInfo within the heartbeat window are logically considered to have closed.</p>
+
</div>
diff --git a/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.xml b/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.xml
index 7828aad..ee822b7 100644
--- a/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.xml
+++ b/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.xml
@@ -4,19 +4,17 @@
<p>As a default, on the Linux platform, if you have IPV6 support enabled in your kernel, the Java Runtime (since 1.4 version) will use IPV6 sockets to communicate. That's perfectly fine, except that your network may not be configured for IPV6. So everything will be dropped...and nothing will ever be received on the consumer side (which maybe even does not support IPV6).</p>
<p>There's a solution to this problem: Force IPV4 stack to be used by the Java Runtime. This can be done using a system property: </p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre> -Djava.net.preferIPv4Stack=true
-</pre>
-</div></div>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Networking IPv6 User Guide</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This information and much more details can be found in the Java Documentation <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/guide/net/ipv6_guide/" rel="nofollow">Networking IPv6 User Guide</a> and in <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/guide/net/properties.html" rel="nofollow">Networking Properties</a></p></div></div>
+<structured-macro ac:macro-id="1c0cafa5-1514-43f4-b48d-8461d2cf0f1f" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+ -Djava.net.preferIPv4Stack=true
+</plain-text-body></structured-macro>
+<structured-macro ac:macro-id="d8e30721-de21-4f39-88da-e191e438968c" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Networking IPv6 User Guide</parameter><rich-text-body><p>This information and much more details can be found in the Java Documentation <a shape="rect" href="http://java.sun.com/j2se/1.5.0/docs/guide/net/ipv6_guide/">Networking IPv6 User Guide</a> and in <a shape="rect" href="http://java.sun.com/j2se/1.5.0/docs/guide/net/properties.html">Networking Properties</a></p></rich-text-body></structured-macro>
<p>Alternatively you can disable IPV6 support on your Linux machine by adding the following line <strong>at the end of /etc/modprobe.conf</strong> (<em>as its name suggests immediately, net-pf-10 is the IPV6 networking module</em>)</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>alias net-pf-10 off # disable IPV6
-</pre>
-</div></div>
+<structured-macro ac:macro-id="2bb86ce9-ca68-4e3e-a722-0f56cf4cc916" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+alias net-pf-10 off # disable IPV6
+</plain-text-body></structured-macro>
<p>If you have very knowledgeable sysadmins that are used to these problems (like in a TV or Radio company for instance where they use multicast a lot), they will be able to tell you immediately if IPV6 is supported on the network (alternatively they will be able to tell you as well if multicast is supported and on which address/port you can multicast), this is a plus and will help you tremendously.</p>
-<p>In some more frequent cases, your sysadmin will be as lost as you are as they are not dealing with these issues very frequently. So good luck for finding out problems. You will need to have a very strict approach to eliminate uncertainties. For this you will need at least a tool like <a shape="rect" class="external-link" href="http://www.ethereal.com" rel="nofollow">ethereal</a> (works on unix, linux and windows)</p></div>
+<p>In some more frequent cases, your sysadmin will be as lost as you are as they are not dealing with these issues very frequently. So good luck for finding out problems. You will need to have a very strict approach to eliminate uncertainties. For this you will need at least a tool like <a shape="rect" href="http://www.ethereal.com">ethereal</a> (works on unix, linux and windows)</p></div>
diff --git a/my-producer-blocks.xml b/my-producer-blocks.xml
index 43a69f1..64ccddd 100644
--- a/my-producer-blocks.xml
+++ b/my-producer-blocks.xml
@@ -1,22 +1,23 @@
-<div class="wiki-content maincontent"><h2 id="Myproducerblocks-WhatcanIdoifmyproducerblockssendingamessage?">What can I do if my producer blocks sending a message?</h2>
+<div class="wiki-content maincontent"><h2>What can I do if my producer blocks sending a message?</h2>
-<p>This relates to <a shape="rect" href="producer-flow-control.xml">Producer Flow Control</a>.</p>
+<p>This relates to <link><page ri:content-title="Producer Flow Control"></page></link>.</p>
-<h3 id="Myproducerblocks-Active4.x">Active 4.x</h3>
+<h3>Active 4.x</h3>
<p>In ActiveMQ 4.x, all in transit messages are held in memory. If you have a slow consumer, to avoid exausting the JVM memory and getting an out of memory error, ActiveMQ has a configurable limit of how many in transit messages it will hold. Once it is reached, producers will be slowed down / blocked.</p>
-<p>A quick fix is just to bump up the setting in your <strong>usageManager</strong> in your <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. The default that ships with ActiveMQ is pretty low, only 20Mb of RAM, so try setting it to something large, say 512Mb.</p>
+<p>A quick fix is just to bump up the setting in your <strong>usageManager</strong> in your <link><page ri:content-title="Xml Configuration"></page></link>. The default that ships with ActiveMQ is pretty low, only 20Mb of RAM, so try setting it to something large, say 512Mb.</p>
<p>An alternative approach is to set individual usageManager limits on different destinations and for producers versus consumers.</p>
-<p>You might also want to use the <a shape="rect" href="jmx.xml">JMX</a> support or <a shape="rect" href="web-console.xml">Web Console</a> to look at what destinations are being used and what producers & consumers you have to see whats going on.</p>
+<p>You might also want to use the <link><page ri:content-title="JMX"></page></link> support or <link><page ri:content-title="Web Console"></page></link> to look at what destinations are being used and what producers & consumers you have to see whats going on.</p>
-<h3 id="Myproducerblocks-Active5.xandLater">Active 5.x and Later</h3>
+<h3>Active 5.x and Later</h3>
-<p>As of 5.x of ActiveMQ there is support for <a shape="rect" href="message-cursors.xml">Message Cursors</a> which by default move messages out of memory and onto disk. So this problem will not be seen unless you fill up the max allocated disk space for message storage which typically is an order of magnitude larger.</p>
+<p>As of 5.x of ActiveMQ there is support for <link><page ri:content-title="Message Cursors"></page></link> which by default move messages out of memory and onto disk. So this problem will not be seen unless you fill up the max allocated disk space for message storage which typically is an order of magnitude larger.</p>
-<h3 id="Myproducerblocks-SeeAlso">See Also</h3>
+<h3>See Also</h3>
-<ul><li><a shape="rect" href="producer-flow-control.xml">Producer Flow Control</a></li><li><a shape="rect" href="message-cursors.xml">Message Cursors</a></li></ul></div>
+<ul><li><link><page ri:content-title="Producer Flow Control"></page></link></li><li><link><page ri:content-title="Message Cursors"></page></link></li></ul>
+</div>
diff --git a/navigation.xml b/navigation.xml
index 5f4e2fc..fd1f831 100644
--- a/navigation.xml
+++ b/navigation.xml
@@ -1,12 +1,12 @@
-<div class="wiki-content maincontent"><h3 id="Navigation-Overview"><a shape="rect" href="overview.xml">Overview</a></h3><ul class="alternate"><li><a shape="rect" href="index.xml">Index</a></li><li><a shape="rect" href="news.xml">News</a></li><li><a shape="rect" href="new-features.xml">New Features</a></li><li><a shape="rect" href="getting-started.xml">Getting Started</a></li><li><a shape="rect" href="faq.xml">FAQ</a></li><li><a shape="rect" href="articles.xml">Articles</a></li><li><a shape="rect" href="books.xml">Books</a></li><li><a shape="rect" href="download.xml">Download</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/licenses/">License</a></li></ul><h3 id="Navigation-Search">Search</h3><div>
-<form enctype="application/x-www-form-urlencoded" method="get" action="http://www.google.com/search" style="font-size: 10px;">
-<input type="hidden" name="ie" value="UTF-8">
-<input type="hidden" name="oe" value="UTF-8">
- <input maxlength="255" type="text" name="q" size="15" value="value"><br clear="none">
- <input type="submit" name="btnG" value="Search">
- <input type="hidden" name="domains" value="activemq.apache.org">
- <input type="hidden" name="sitesearch" value="activemq.apache.org">
-</form>
-</div>
-<h3 id="Navigation-SubProjects">Sub Projects</h3><ul class="alternate"><li><a shape="rect" class="external-link" href="http://activemq.apache.org/artemis/">Artemis</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/apollo" title="ActiveMQ Apollo">Apollo</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/cms/">CMS</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/" title="NMS is the .Net Messaging API">NMS</a></li></ul><h3 id="Navigation-Community"><a shape="rect" href="community.xml">Community</a></h3><ul class="alternate"><li><a shape="rect" href="support.xml">Support</a></li><li><a shape="rect" href="contributing.xml">Contributing</a></li><li><a shape="rect" href="discussion-forums.xml">Discussion Forums</a></li><li><a shape="rect" href="mailing-lists.xml">Mailing Lists</a></li><li><a shape="rect" href="irc.xml">IRC</a></li><li><a shape="rect" class="external-link" href="http://javabot.evanchooly.com/logs/%23apache-activemq/today" rel="nofollow">IRC Log</a></li><li><a shape="rect" href="security-advisories.xml">Security Advisories</a></li><li><a shape="rect" href="site.xml">Site</a></li><li><a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a shape="rect" href="projects-using-activemq.xml">Projects Using ActiveMQ</a></li><li><a shape="rect" href="users.xml">Users</a></li><li><a shape="rect" href="team.xml">Team</a></li><li><a shape="rect" href="thanks.xml">Thanks</a></li></ul><h3 id="Navigation-Features"><a shape="rect" href="features.xml">Features</a></h3><ul class="alternate"><li><a shape="rect" href="advisory-message.xml">Advisory Message</a></li><li><a shape="rect" href="clustering.xml">Clustering</a></li><li><a shape="rect" href="cross-language-clients.xml">Cross Language Clients</a></li><li><a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a></li><li><a shape="rect" href="jmx.xml">JMX</a></li><li><a shape="rect" href="jms-to-jms-bridge.xml">JMS to JMS Bridge</a></li><li><a shape="rect" href="masterslave.xml">MasterSlave</a></li><li><a shape="rect" href="message-groups.xml">Message Groups</a></li><li><a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a></li><li><a shape="rect" href="performance.xml">Performance</a></li><li><a shape="rect" href="persistence.xml">Persistence</a></li><li><a shape="rect" href="security.xml">Security</a></li><li><a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a></li><li><a shape="rect" href="visualisation.xml">Visualisation</a></li><li><a shape="rect" href="features.xml">More ...</a></li></ul><h3 id="Navigation-Connectivity"><a shape="rect" href="connectivity.xml">Connectivity</a></h3><ul class="alternate"><li><a shape="rect" href="ajax.xml">Ajax</a></li><li><a shape="rect" href="amqp.xml">AMQP</a></li><li><a shape="rect" href="axis-and-cxf-support.xml">Axis and CXF Support</a></li><li><a shape="rect" href="c-integration.xml">C Integration</a></li><li><a shape="rect" href="activemq-c-clients.xml">C++</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/">C# and .Net Integration</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/cms/">CMS</a></li><li><a shape="rect" href="j2ee.xml">J2EE</a></li><li><a shape="rect" href="jboss-integration.xml">JBoss Integration</a></li><li><a shape="rect" class="external-link" href="http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ" rel="nofollow">Jetty</a></li><li><a shape="rect" href="jndi-support.xml">JNDI Support</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/" title="NMS is the .Net Messaging API">NMS</a></li><li><a shape="rect" href="rest.xml">REST</a></li><li><a shape="rect" href="rss-and-atom.xml">RSS and Atom</a></li><li><a shape="rect" href="spring-support.xml">Spring Support</a></li><li><a shape="rect" href="stomp.xml">Stomp</a></li><li><a shape="rect" href="tomcat.xml">Tomcat</a></li><li><a shape="rect" href="unix-service.xml">Unix Service</a></li><li><a shape="rect" href="weblogic-integration.xml">WebLogic Integration</a></li><li><a shape="rect" href="xmpp.xml">XMPP</a></li><li><a shape="rect" href="connectivity.xml">More ...</a></li></ul><h3 id="Navigation-UsingActiveMQ5"><a shape="rect" href="using-activemq-5.xml">Using ActiveMQ 5</a></h3><ul class="alternate"><li><a shape="rect" href="version-5-getting-started.xml">Getting Started</a></li><li><a shape="rect" href="version-5-initial-configuration.xml">Initial Configuration</a></li><li><a shape="rect" href="version-5-run-broker.xml">Running a Broker</a></li><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">Embedded Brokers</a></li><li><a shape="rect" href="activemq-command-line-tools-reference.xml">Command Line Tools</a></li><li><a shape="rect" href="configuring-version-5-transports.xml">Configuring Transports</a></li><li><a shape="rect" href="version-5-examples.xml">Examples</a></li><li><a shape="rect" href="version-5-web-samples.xml">Web Samples</a></li><li><a shape="rect" href="how-can-i-monitor-activemq.xml">Monitoring the Broker</a></li><li><a shape="rect" href="version-5-xml-configuration.xml">Xml Configuration</a></li><li><a shape="rect" href="xml-reference.xml">Xml Reference</a></li><li><a shape="rect" href="using-activemq-5.xml">More ...</a></li></ul><h3 id="Navigation-Tools"><a shape="rect" href="tools.xml">Tools</a></h3><ul class="alternate"><li><a shape="rect" href="web-console.xml">Web Console</a></li><li><a shape="rect" href="activemq-performance-module-users-manual.xml">Maven2 Performance Plugin</a></li></ul><h3 id="Navigation-Support"><a shape="rect" href="support.xml">Support</a></h3><ul class="alternate"><li><a shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/AMQ">Issues</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel">Roadmap</a></li><li><a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel">Change log</a></li></ul><h3 id="Navigation-Developers"><a shape="rect" href="developers.xml">Developers</a></h3><ul class="alternate"><li><a shape="rect" href="source.xml">Source</a></li><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="developer-guide.xml">Developer Guide</a></li><li><a shape="rect" href="becoming-a-committer.xml">Becoming a committer</a></li><li><a shape="rect" href="code-overview.xml">Code Overview</a></li><li><a shape="rect" href="wire-protocol.xml">Wire Protocol</a></li><li><a shape="rect" href="release-guide.xml">Release Guide</a></li></ul><h3 id="Navigation-Tests">Tests</h3><ul class="alternate"><li><a shape="rect" href="activemq-performance-module-users-manual.xml">Maven2 Performance Plugin</a></li><li><a shape="rect" href="benchmark-tests.xml">Benchmark Tests</a></li><li><a shape="rect" href="jmeter-system-tests.xml">JMeter System Tests</a></li><li><a shape="rect" href="jmeter-performance-tests.xml">JMeter Performance Tests</a></li><li><a shape="rect" href="integration-tests.xml">Integration Tests</a></li></ul><h3 id="Navigation-ProjectReports">Project Reports</h3><ul class="alternate"><li><a shape="rect" href="junit-reports.xml">JUnit Reports</a></li><li><a shape="rect" href="source-xref.xml">Source XRef</a></li><li><a shape="rect" href="test-source-xref.xml">Test Source XRef</a></li><li><a shape="rect" href="xml-reference.xml">Xml Reference</a></li></ul></div>
+<div class="wiki-content maincontent"><h3><link><page ri:content-title="Overview"></page></link></h3><ul class="alternate"><li><link><page ri:content-title="Index"></page></link></li><li><link><page ri:content-title="News"></page></link></li><li><link><page ri:content-title="New Features"></page></link></li><li><link><page ri:content-title="Getting Started"></page></link></li><li><link><page ri:content-title="FAQ"></page></link></li><li><link><page ri:content-title="Articles"></page></link></li><li><link><page ri:content-title="Books"></page></link></li><li><link><page ri:content-title="Download"></page></link></li><li><a shape="rect" href="http://www.apache.org/licenses/">License</a></li></ul><h3>Search</h3><structured-macro ac:macro-id="e6a5dbbd-5233-4ecd-ba0b-e7e6c6bc863a" ac:name="html" ac:schema-version="1"><parameter ac:name="atlassian-macro-output-type">BLOCK</parameter><plain-text-body><DIV>
+<FORM action="http://www.google.com/search" method="get" style="font-size: 10px;">
+<INPUT name="ie" type="hidden" value="UTF-8"></INPUT>
+<INPUT name="oe" type="hidden" value="UTF-8"></INPUT>
+ <INPUT maxlength="255" name="q" size="15" type="text" value></INPUT><BR></BR>
+ <INPUT name="btnG" type="submit" value="Search"></INPUT>
+ <INPUT name="domains" type="hidden" value="activemq.apache.org"></INPUT>
+ <INPUT name="sitesearch" type="hidden" value="activemq.apache.org"></INPUT>
+</FORM>
+</DIV>
+</plain-text-body></structured-macro><h3>Sub Projects</h3><ul class="alternate"><li><a shape="rect" href="http://activemq.apache.org/artemis/">Artemis</a></li><li><a shape="rect" href="http://activemq.apache.org/apollo" title="ActiveMQ Apollo">Apollo</a></li><li><a shape="rect" href="http://activemq.apache.org/cms/">CMS</a></li><li><a shape="rect" href="http://activemq.apache.org/nms/" title="NMS is the .Net Messaging API">NMS</a></li></ul><h3><link><page ri:content-title="Community"></page></link></h3><ul class="alternate"><li><link><page ri:content-title="Support"></page></link></li><li><link><page ri:content-title="Contributing"></page></link></li><li><link><page ri:content-title="Discussion Forums"></page></link></li><li><link><page ri:content-title="Mailing Lists"></page></link></li><li><link><page ri:content-title="IRC"></page></link></li><li><a shape="rect" href="http://javabot.evanchooly.com/logs/%23apache-activemq/today">IRC Log</a></li><li><link><page ri:content-title="Security Advisories"></page></link></li><li><link><page ri:content-title="Site"></page></link></li><li><a shape="rect" href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><link><page ri:content-title="Projects Using ActiveMQ"></page></link></li><li><link><page ri:content-title="Users"></page></link></li><li><link><page ri:content-title="Team"></page></link></li><li><link><page ri:content-title="Thanks"></page></link></li></ul><h3><link><page ri:content-title="Features"></page></link></h3><ul class="alternate"><li><link><page ri:content-title="Advisory Message"></page></link></li><li><link><page ri:content-title="Clustering"></page></link></li><li><link><page ri:content-title="Cross Language Clients"></page></link></li><li><link><page ri:content-title="Enterprise Integration Patterns"></page></link></li><li><link><page ri:content-title="JMX"></page></link></li><li><link><page ri:content-title="JMS to JMS Bridge"></page></link></li><li><link><page ri:content-title="MasterSlave"></page></link></li><li><link><page ri:content-title="Message Groups"></page></link></li><li><link><page ri:content-title="Networks of Brokers"></page></link></li><li><link><page ri:content-title="Performance"></page></link></li><li><link><page ri:content-title="Persistence"></page></link></li><li><link><page ri:content-title="Security"></page></link></li><li><link><page ri:content-title="Virtual Destinations"></page></link></li><li><link><page ri:content-title="Visualisation"></page></link></li><li><link><page ri:content-title="Features"></page><plain-text-link-body>More ...</plain-text-link-body></link></li></ul><h3><link><page ri:content-title="Connectivity"></page></link></h3><ul class="alternate"><li><link><page ri:content-title="Ajax"></page></link></li><li><link><page ri:content-title="AMQP"></page></link></li><li><link><page ri:content-title="Axis and CXF Support"></page></link></li><li><link><page ri:content-title="C Integration"></page></link></li><li><link><page ri:content-title="ActiveMQ C++ Clients"></page><plain-text-link-body>C++</plain-text-link-body></link></li><li><a shape="rect" href="http://activemq.apache.org/nms/">C# and .Net Integration</a></li><li><a shape="rect" href="http://activemq.apache.org/cms/">CMS</a></li><li><link><page ri:content-title="J2EE"></page></link></li><li><link><page ri:content-title="JBoss Integration"></page></link></li><li><a shape="rect" href="http://docs.codehaus.org/display/JETTY/Integrating+with+ActiveMQ">Jetty</a></li><li><link><page ri:content-title="JNDI Support"></page></link></li><li><a shape="rect" href="http://activemq.apache.org/nms/" title="NMS is the .Net Messaging API">NMS</a></li><li><link><page ri:content-title="REST"></page></link></li><li><link><page ri:content-title="RSS and Atom"></page></link></li><li><link><page ri:content-title="Spring Support"></page></link></li><li><link><page ri:content-title="Stomp"></page></link></li><li><link><page ri:content-title="Tomcat"></page></link></li><li><link><page ri:content-title="Unix Service"></page></link></li><li><link><page ri:content-title="WebLogic Integration"></page></link></li><li><link><page ri:content-title="XMPP"></page></link></li><li><link><page ri:content-title="Connectivity"></page><plain-text-link-body>More ...</plain-text-link-body></link></li></ul><h3><link><page ri:content-title="Using ActiveMQ 5"></page></link></h3><ul class="alternate"><li><link><page ri:content-title="Version 5 Getting Started"></page><plain-text-link-body>Getting Started</plain-text-link-body></link></li><li><link><page ri:content-title="Version 5 Initial Configuration"></page><plain-text-link-body>Initial Configuration</plain-text-link-body></link></li><li><link><page ri:content-title="Version 5 Run Broker"></page><plain-text-link-body>Running a Broker</plain-text-link-body></link></li><li><link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>Embedded Brokers</plain-text-link-body></link></li><li><link><page ri:content-title="ActiveMQ Command Line Tools Reference"></page><plain-text-link-body>Command Line Tools</plain-text-link-body></link></li><li><link><page ri:content-title="Configuring Version 5 Transports"></page><plain-text-link-body>Configuring Transports</plain-text-link-body></link></li><li><link><page ri:content-title="Version 5 Examples"></page><plain-text-link-body>Examples</plain-text-link-body></link></li><li><link><page ri:content-title="Version 5 Web Samples"></page><plain-text-link-body>Web Samples</plain-text-link-body></link></li><li><link><page ri:content-title="How can I monitor ActiveMQ"></page><plain-text-link-body>Monitoring the Broker</plain-text-link-body></link></li><li><link><page ri:content-title="Version 5 XML Configuration"></page><plain-text-link-body>Xml Configuration</plain-text-link-body></link></li><li><link><page ri:content-title="Xml Reference"></page></link></li><li><link><page ri:content-title="Using ActiveMQ 5"></page><plain-text-link-body>More ...</plain-text-link-body></link></li></ul><h3><link><page ri:content-title="Tools"></page></link></h3><ul class="alternate"><li><link><page ri:content-title="Web Console"></page></link></li><li><link><page ri:content-title="ActiveMQ Performance Module Users Manual"></page><plain-text-link-body>Maven2 Performance Plugin</plain-text-link-body></link></li></ul><h3><link><page ri:content-title="Support"></page></link></h3><ul class="alternate"><li><a shape="rect" href="http://issues.apache.org/jira/browse/AMQ">Issues</a></li><li><a shape="rect" href="http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel">Roadmap</a></li><li><a shape="rect" href="http://issues.apache.org/activemq/browse/AMQ?report=com.atlassian.jira.plugin.system.project:changelog-panel">Change log</a></li></ul><h3><link><page ri:content-title="Developers"></page></link></h3><ul class="alternate"><li><link><page ri:content-title="Source"></page></link></li><li><link><page ri:content-title="Building"></page></link></li><li><link><page ri:content-title="Developer Guide"></page></link></li><li><link><page ri:content-title="Becoming a committer"></page></link></li><li><link><page ri:content-title="Code Overview"></page></link></li><li><link><page ri:content-title="Wire Protocol"></page></link></li><li><link><page ri:content-title="Release Guide"></page></link></li></ul><h3>Tests</h3><ul class="alternate"><li><link><page ri:content-title="ActiveMQ Performance Module Users Manual"></page><plain-text-link-body>Maven2 Performance Plugin</plain-text-link-body></link></li><li><link><page ri:content-title="Benchmark Tests"></page></link></li><li><link><page ri:content-title="JMeter System Tests"></page></link></li><li><link><page ri:content-title="JMeter Performance Tests"></page></link></li><li><link><page ri:content-title="Integration Tests"></page></link></li></ul><h3>Project Reports</h3><ul class="alternate"><li><link><page ri:content-title="JUnit Reports"></page></link></li><li><link><page ri:content-title="Source XRef"></page></link></li><li><link><page ri:content-title="Test Source XRef"></page></link></li><li><link><page ri:content-title="Xml Reference"></page></link></li></ul></div>
diff --git a/networks-of-brokers.xml b/networks-of-brokers.xml
index 9e4f3e0..784489b 100644
--- a/networks-of-brokers.xml
+++ b/networks-of-brokers.xml
@@ -1,11 +1,10 @@
-<div class="wiki-content maincontent"><p>To provide massive scalability of a large messaging fabric you typically want to allow many brokers to be connected together into a network so that you can have as many clients as you wish all logically connected together - and running as many message brokers as you need based on your number of clients and network topology.</p><p>If you are using <a shape="rect" href="topologies.xml">client/server or hub/spoke style topology</a> then the broker you connect to becomes a single point of failure which is another reason for wanting a network (or cluster) of brokers so that you can survive failure of any particular broker, machine or subnet.</p><p>From 1.1 onwards of ActiveMQ supports <em>networks of brokers</em> which allows us to support <a shape="rect" href="how-do-distributed-queues-work.xml">distributed queues and topics</a> across a network of brokers.</p><p>This allows a client to connect to any broker in the network - and fail over to another broker if there is a failure - providing from the clients perspective a <a shape="rect" href="ha.xml">HA</a> cluster of brokers.</p><p><strong>N.B.</strong> By default a network connection is one way only - the broker that establishes the connection <em>passes messages to</em> the broker(s) its connected to. From version 5.x of ActiveMQ, a network connection can be optionally enabled to be duplex, which can be useful for hub and spoke architectures, where the hub is behind a firewall etc.</p><h2 id="NetworksofBrokers-Configuringanetworkofbrokers">Configuring a network of brokers</h2><p>The easiest way to configure a network of brokers is via the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. There are two main ways to create a network of brokers</p><ul><li>use a hard coded list of networkConnector elements.</li></ul><ul><li>use Discovery to detect brokers (multicast or rendezvous).</li></ul><h3 id="NetworksofBrokers-ExamplewithafixedlistofURIs">Example with a fixed list of URIs</h3><p>Here is an example of using the fixed list of URIs</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+<div class="wiki-content maincontent"><p>To provide massive scalability of a large messaging fabric you typically want to allow many brokers to be connected together into a network so that you can have as many clients as you wish all logically connected together - and running as many message brokers as you need based on your number of clients and network topology.</p><p>If you are using <link><page ri:content-title="Topologies"></page><plain-text-link-body>client/server or hub/spoke style topology</plain-text-link-body></link> then the broker you connect to becomes a single point of failure which is another reason for wanting a network (or cluster) of brokers so that you can survive failure of any particular broker, machine or subnet.</p><p>From 1.1 onwards of ActiveMQ supports <em>networks of brokers</em> which allows us to support <link><page ri:content-title="How do distributed queues work"></page><plain-text-link-body>distributed queues and topics</plain-text-link-body></link> across a network of brokers.</p><p>This allows a client to connect to any broker in the network - and fail over to another broker if there is a failure - providing from the clients perspective a <link><page ri:content-title="HA"></page></link> cluster of brokers.</p><p><strong>N.B.</strong> By default a network connection is one way only - the broker that establishes the connection <em>passes messages to</em> the broker(s) its connected to. From version 5.x of ActiveMQ, a network connection can be optionally enabled to be duplex, which can be useful for hub and spoke architectures, where the hub is behind a firewall etc.</p><h2>Configuring a network of brokers</h2><p>The easiest way to configure a network of brokers is via the <link><page ri:content-title="Xml Configuration"></page></link>. There are two main ways to create a network of brokers</p><ul><li>use a hard coded list of networkConnector elements.</li></ul><ul><li>use Discovery to detect brokers (multicast or rendezvous).</li></ul><h3>Example with a fixed list of URIs</h3><p>Here is an example of using the fixed list of URIs</p><structured-macro ac:macro-id="130b1860-d573-4ab5-8eff-3ff52285a612" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<beans xmlns="http://activemq.org/config/1.0">
- <broker brokerName="receiver" persistent="false" useJmx="false">
+ <broker brokerName="receiver" persistent="false" useJmx="false">
<networkConnectors>
- <networkConnector uri="static:(tcp://localhost:62001)"/>
+ <networkConnector uri="static:(tcp://localhost:62001)"/>
</networkConnectors>
<persistenceAdapter>
@@ -13,20 +12,18 @@
</persistenceAdapter>
<transportConnectors>
- <transportConnector uri="tcp://localhost:62002"/>
+ <transportConnector uri="tcp://localhost:62002"/>
</transportConnectors>
</broker>
</beans>
-]]></script>
-</div></div><p>ActiveMQ also supports other transports than tcp to be used for the network connector such as http.</p><h3 id="NetworksofBrokers-Exampleusingmulticastdiscovery">Example using multicast discovery</h3><p>This example uses multicast <a shape="rect" class="external-link" href="http://activemq.apache.org/discovery.html">discovery</a></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+</plain-text-body></structured-macro><p>ActiveMQ also supports other transports than tcp to be used for the network connector such as http.</p><h3>Example using multicast discovery</h3><p>This example uses multicast <a shape="rect" href="http://activemq.apache.org/discovery.html">discovery</a></p><structured-macro ac:macro-id="b19c8492-4cd3-4bf9-8f67-2750a7b376e0" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<beans xmlns="http://activemq.org/config/1.0">
- <broker name="sender" persistent="false" useJmx="false">
+ <broker name="sender" persistent="false" useJmx="false">
<networkConnectors>
- <networkConnector uri="multicast://default"/>
+ <networkConnector uri="multicast://default"/>
</networkConnectors>
<persistenceAdapter>
@@ -34,169 +31,130 @@
</persistenceAdapter>
<transportConnectors>
- <transportConnector uri="tcp://localhost:0" discoveryUri="multicast://default"/>
+ <transportConnector uri="tcp://localhost:0" discoveryUri="multicast://default"/>
</transportConnectors>
</broker>
</beans>
-]]></script>
-</div></div><h2 id="NetworksofBrokers-Startingnetworkconnectors">Starting network connectors</h2><p>By default, network connectors are initiated serially as part of the broker start up sequence. When some networks are slow, they prevent other networks from starting in a timely manner. Version 5.5 supports the broker attribute networkConnectorStartAsync="true" which will cause the broker to use an executor to start network connectors in parallel, asynchronous to a broker start.</p><h2 id="NetworksofBrokers-Staticdiscovery">Static discovery</h2><p>With <code>static:</code> discovery you can hard code the list of broker URLs. A network connector will be created for each one.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <networkConnectors>
- <networkConnector uri="static:(tcp://host1:61616,tcp://host2:61616,tcp://..)"/>
+</plain-text-body></structured-macro><h2>Starting network connectors</h2><p>By default, network connectors are initiated serially as part of the broker start up sequence. When some networks are slow, they prevent other networks from starting in a timely manner. Version 5.5 supports the broker attribute networkConnectorStartAsync="true" which will cause the broker to use an executor to start network connectors in parallel, asynchronous to a broker start.</p><h2>Static discovery</h2><p>With <code>static:</code> discovery you can hard code the list of broker URLs. A network connector will be created for each one.</p><structured-macro ac:macro-id="930870f3-f252-41cc-8056-2cf08b8fdcb1" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <networkConnectors>
+ <networkConnector uri="static:(tcp://host1:61616,tcp://host2:61616,tcp://..)"/>
</networkConnectors>
-]]></script>
-</div></div><p>There are some useful properties you can set on a static network connector for retries:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default</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>1000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>time(ms) to wait before attempting a reconnect (if useExponentialBackOff is false)</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>time(ms) to wait before attempting to re-connect</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useExponentialBackOff</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>increases time between reconnect for every failure in a reconnect sequence</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>backOffMultiplier</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>multipler used to increase the wait time if using exponential back off</p></td></tr></tbody></table></div><p>e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[uri="static:(tcp://host1:61616,tcp://host2:61616)?maxReconnectDelay=5000&useExponentialBackOff=false"
-]]></script>
-</div></div><h2 id="NetworksofBrokers-MasterSlaveDiscovery">MasterSlave Discovery</h2><p>A common configuration option for a network of brokers is to establish a network bridge between a broker and an n+1 broker pair (master/slave). Typical configurations involve using the <code>failover:</code> transport, but there are a some other non-intuitive options that must be configured for it to work as desired. For this reason, ActiveMQ v5.6+ has a convenience discovery agent that can be specified with the <code>masterslave:</code> transport prefix:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <networkConnectors>
- <networkConnector uri="masterslave:(tcp://host1:61616,tcp://host2:61616,tcp://..)"/>
+</plain-text-body></structured-macro><p>There are some useful properties you can set on a static network connector for retries:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>property</p></th><th colspan="1" rowspan="1"><p>default</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>initialReconnectDelay</p></td><td colspan="1" rowspan="1"><p>1000</p></td><td colspan="1" rowspan="1"><p>time(ms) to wait before attempting a reconnect (if useExponentialBackOff is false)</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxReconnectDelay</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>time(ms) to wait before attempting to re-connect</p></td></tr><tr><td colspan="1" rowspan="1"><p>useExponentialBackOff</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>increases time between reconnect for every failure in a reconnect sequence</p></td></tr><tr><td colspan="1" rowspan="1"><p>backOffMultiplier</p></td><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>multipler used to increase the wait time if using exponential back off</p></td></tr></tbody></table><p>e.g.</p><structured-macro ac:macro-id="0746e17d-d27c-4ccb-aae0-06e909e73d54" ac:name="code" ac:schema-version="1"><plain-text-body>uri="static:(tcp://host1:61616,tcp://host2:61616)?maxReconnectDelay=5000&useExponentialBackOff=false"
+</plain-text-body></structured-macro><h2>MasterSlave Discovery</h2><p>A common configuration option for a network of brokers is to establish a network bridge between a broker and an n+1 broker pair (master/slave). Typical configurations involve using the <code>failover:</code> transport, but there are a some other non-intuitive options that must be configured for it to work as desired. For this reason, ActiveMQ v5.6+ has a convenience discovery agent that can be specified with the <code>masterslave:</code> transport prefix:</p><structured-macro ac:macro-id="b27cc60f-1de1-4535-9919-889c614c1de2" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <networkConnectors>
+ <networkConnector uri="masterslave:(tcp://host1:61616,tcp://host2:61616,tcp://..)"/>
</networkConnectors>
-]]></script>
-</div></div><p>The URIs are listed in order for: MASTER,SLAVE1,SLAVE2...SLAVE<img class="emoticon emoticon-thumbs-down" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/thumbs_down.png" data-emoticon-name="thumbs-down" alt="(thumbs down)"></p><p>The same configuration options for <code>static:</code> are available for <code>masterslave:</code></p><h2 id="NetworksofBrokers-NetworkConnectorProperties">NetworkConnector Properties</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>name</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>bridge</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>name of the network - for more than one network connector between the same two brokers - use different names</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>dynamicOnly</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if true, only activate a networked durable subscription when a corresponding durable subscription reactivates, by default they are activated on startup.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>decreaseNetworkConsumerPriority</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if true, starting at priority -5, decrease the priority for dispatching to a network Queue consumer the further away it is (in network hops) from the producer. When false all network consumers use same default priority(0) as local consumers</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>networkTTL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>the number of brokers in the network that messages and subscriptions can pass through (sets both message&consumer -TTL)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>messageTTL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(version 5.9) the number of brokers in the network that messages can pass through</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumerTTL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(version 5.9) the number of brokers in the network that subscriptions can pass through (keep to 1 in a mesh)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>conduitSubscriptions</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>multiple consumers subscribing to the same destination are treated as one consumer by the network</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>excludedDestinations</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>empty</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>destinations matching this list won't be forwarded across the network (this only applies to <span>dynamicallyIncludedDestinations)</span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>dynamicallyIncludedDestinations</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>empty</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>destinations that match this list <strong>will</strong> be forwarded across the network <strong>n.b.</strong> an empty list means all destinations not in the exluded list will be forwarded</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>useVirtualDestSubs</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if true, the network connection will listen to advisory messages for virtual destination consumers</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>staticallyIncludedDestinations</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>empty</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>destinations that match will always be passed across the network - even if no consumers have ever registered an interest</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>duplex</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>if true, a network connection will be used to both produce <strong><em>AND</em></strong> Consume messages. This is useful for hub and spoke scenarios when the hub is behind a firewall etc.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>prefetchSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch size</a> on the network connector's consumer. It must be > 0 because network consumers do not poll for messages</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>suppressDuplicateQueueSubscriptions</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(from 5.3) if true, duplicate subscriptions in the network that arise from network intermediaries will be suppressed. For example, given brokers A,B and C, networked via multicast discovery. A consumer on A will give rise to a networked consumer on B and C. In addition, C will network to B (based on the network consumer from A) and B will network to C. When true, the network bridges between C and B (being duplicates of their existing network subscriptions to A) will be suppressed. Reducing the routing choices in this way provides determinism when producers or consumers migrate across the network as the potential for dead routes (stuck messages) are eliminated. networkTTL needs to match or exceed the broker count to require this intervention.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>bridgeTempDestinations</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether to broadcast advisory messages for created temp destinations in the network of brokers or not. Temp destinations are typically created for request-reply messages. Broadcasting the information about temp destinations is turned on by default so that consumers of a request-reply message can be connected to another broker in the network and still send back the reply on the temporary destination specified in the JMSReplyTo header. In an application scenario where most/all messages use request-reply pattern, this will generate additional traffic on the broker network as every message typically sets a unique JMSReplyTo address (which causes a new temp destination to be created and broadcasted via an advisory message in the network of brokers). <br clear="none"> When disabling this feature such network traffic can be reduced but then producer and consumers of a request-reply message need to be connected to the same broker. Remote consumers (i.e. connected via another broker in your network) won't be able to send the reply message but instead raise a "temp destination does not exist" exception.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>alwaysSyncSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(version 5.6) When true, non persistent messages are sent to the remote broker using request/reply in place of a oneway. This setting treats both persistent and non-persistent messages the same.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>staticBridge</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(version 5.6) If set to true, broker will not dynamically respond to new consumers. It will only use <code>staticallyIncludedDestinations</code> to create demand subscriptions</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">userName</td><td colspan="1" rowspan="1" class="confluenceTd">null</td><td colspan="1" rowspan="1" class="confluenceTd">The username to authenticate against the remote broker</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">password</td><td colspan="1" rowspan="1" class="confluenceTd">null</td><td colspan="1" rowspan="1" class="confluenceTd">The password for the username to authenticate against the remote broker</td></tr></tbody></table></div><h4 id="NetworksofBrokers-Reliability">Reliability</h4><p>Networks of brokers do reliable store and forward of messages. If the source is durable, persistent messages on a queue or a durable topic subscription, a network will retain the durability guarantee. <br clear="none"> However networks cannot add durability when the source is non durable. Non durable topic subscriptions and temporary destinations (both queues and topics) are non durable by definition. When non durable<br clear="none"> sources are networked, in the event of a failure, inflight messages can be lost.</p><h4 id="NetworksofBrokers-Ordering">Ordering</h4><p>Total message ordering is not preserved with networks of brokers. Total ordering <a shape="rect" href="how-do-i-preserve-order-of-messages.xml">works with a single consumer</a> but a networkBridge introduces a second consumer. In addition, network bridge consumers forward messages via producer.send(..), so they go from the head of the queue on the forwarding broker to the tail of the queue on the target. If single consumer moves between networked brokers, total order may be preserved if all messages always follow the consumer but this can be difficult to guarantee with large message backlogs.</p><h4 id="NetworksofBrokers-WhentouseandnotuseConduitsubscriptions">When to use and not use Conduit subscriptions</h4><p>ActiveMQ relies on information about active consumers (subscriptions) to pass messages around the network. A broker interprets a subscription from a remote (networked) broker in the same way as it would a subscription from a local client connection and routes a copy of any relevant message to each subscription. With Topic subscriptions and with more than one remote subscription, a remote broker would interpret each message copy as valid, so when it in turns routes the messages to its own local connections, duplicates would occur. Hence default conduit behavior consolidates all matching subscription information to prevent duplicates flowing around the network. With this default behaviour, N subscriptions on a remote broker look like a single subscription to the networked broker.</p><p>However - duplicate subscriptions is a useful feature to exploit if you are only using Queues. As the load balancing algorithm will attempt to share message load evenly, consumers across a network will equally share the message load only if the flag <code>conduitSubscriptions=false</code>. Here's an example. Suppose you have two brokers, A and B, that are connected to one another via a forwarding bridge. Connected to broker A, you have a consumer that subscribes to a queue called <code>Q.TEST</code>. Connected to broker B, you have two consumers that also subscribe to <code>Q.TEST</code>. All consumers have equal priority. Then you start a producer on broker A that writes 30 messages to <code>Q.TEST</code>. By default, (<code>conduitSubscriptions=true</code>), 15 messages will be sent to the consumer on broker A and the resulting 15 messages will be sent to the two consumers on broker B. The message load has not been equally spread across all three consumers because, by default, broker A views the two subscriptions on broker B as one. If you had set <code>conduitSubscriptions</code> to <code>false</code>, then each of the three consumers would have been given 10 messages.</p><h4 id="NetworksofBrokers-Duplexnetworkconnectors">Duplex network connectors</h4><p>By default a network bridge forwards messages on demand in one direction over a single connection. When <code>duplex=true</code>, the same connection is used for a network bridge in the opposite directions, resulting in a bi-directional bridge. The network bridge configuration is propagated to the other broker so the duplex bridge is an exact replica or the original.</p><p><br clear="none"> Given two brokers, broker A and broker B, a duplex bridge on A to B is the same as a default bridge on A to B and a default bridge on B to A.</p><p><br clear="none"> Note, if you want to configure more than one duplex network bridge between two brokers, to increase throughput or to partition topics and queues, you must provide unique names for each:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnectors>
- <networkConnector name="SYSTEM1" duplex="true" uri="static:(tcp://10.x.x.x:61616)">
+</plain-text-body></structured-macro><p>The URIs are listed in order for: MASTER,SLAVE1,SLAVE2...SLAVE<emoticon ac:name="thumbs-down"></emoticon></p><p>The same configuration options for <code>static:</code> are available for <code>masterslave:</code></p><h2>NetworkConnector Properties</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>property</p></th><th colspan="1" rowspan="1"><p>default</p></th><th colspan="1" rowspan="1"><p>description</p></th></tr><tr><td colspan="1" rowspan="1"><p>name</p></td><td colspan="1" rowspan="1"><p>bridge</p></td><td colspan="1" rowspan="1"><p>name of the network - for more than one network connector between the same two brokers - use different names</p></td></tr><tr><td colspan="1" rowspan="1"><p>dynamicOnly</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>if true, only activate a networked durable subscription when a corresponding durable subscription reactivates, by default they are activated on startup.</p></td></tr><tr><td colspan="1" rowspan="1"><p>decreaseNetworkConsumerPriority</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>if true, starting at priority -5, decrease the priority for dispatching to a network Queue consumer the further away it is (in network hops) from the producer. When false all network consumers use same default priority(0) as local consumers</p></td></tr><tr><td colspan="1" rowspan="1"><p>networkTTL</p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>the number of brokers in the network that messages and subscriptions can pass through (sets both message&consumer -TTL)</p></td></tr><tr><td colspan="1" rowspan="1"><p>messageTTL</p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>(version 5.9) the number of brokers in the network that messages can pass through</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumerTTL</p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>(version 5.9) the number of brokers in the network that subscriptions can pass through (keep to 1 in a mesh)</p></td></tr><tr><td colspan="1" rowspan="1"><p>conduitSubscriptions</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>multiple consumers subscribing to the same destination are treated as one consumer by the network</p></td></tr><tr><td colspan="1" rowspan="1"><p>excludedDestinations</p></td><td colspan="1" rowspan="1"><p>empty</p></td><td colspan="1" rowspan="1"><p>destinations matching this list won't be forwarded across the network (this only applies to <span>dynamicallyIncludedDestinations)</span></p></td></tr><tr><td colspan="1" rowspan="1"><p>dynamicallyIncludedDestinations</p></td><td colspan="1" rowspan="1"><p>empty</p></td><td colspan="1" rowspan="1"><p>destinations that match this list <strong>will</strong> be forwarded across the network <strong>n.b.</strong> an empty list means all destinations not in the exluded list will be forwarded</p></td></tr><tr><td colspan="1" rowspan="1"><p>useVirtualDestSubs</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>if true, the network connection will listen to advisory messages for virtual destination consumers</p></td></tr><tr><td colspan="1" rowspan="1"><p>staticallyIncludedDestinations</p></td><td colspan="1" rowspan="1"><p>empty</p></td><td colspan="1" rowspan="1"><p>destinations that match will always be passed across the network - even if no consumers have ever registered an interest</p></td></tr><tr><td colspan="1" rowspan="1"><p>duplex</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>if true, a network connection will be used to both produce <strong><em>AND</em></strong> Consume messages. This is useful for hub and spoke scenarios when the hub is behind a firewall etc.</p></td></tr><tr><td colspan="1" rowspan="1"><p>prefetchSize</p></td><td colspan="1" rowspan="1"><p>1000</p></td><td colspan="1" rowspan="1"><p>Sets the <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>prefetch size</plain-text-link-body></link> on the network connector's consumer. It must be > 0 because network consumers do not poll for messages</p></td></tr><tr><td colspan="1" rowspan="1"><p>suppressDuplicateQueueSubscriptions</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>(from 5.3) if true, duplicate subscriptions in the network that arise from network intermediaries will be suppressed. For example, given brokers A,B and C, networked via multicast discovery. A consumer on A will give rise to a networked consumer on B and C. In addition, C will network to B (based on the network consumer from A) and B will network to C. When true, the network bridges between C and B (being duplicates of their existing network subscriptions to A) will be suppressed. Reducing the routing choices in this way provides determinism when producers or consumers migrate across the network as the potential for dead routes (stuck messages) are eliminated. networkTTL needs to match or exceed the broker count to require this intervention.</p></td></tr><tr><td colspan="1" rowspan="1"><p>bridgeTempDestinations</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Whether to broadcast advisory messages for created temp destinations in the network of brokers or not. Temp destinations are typically created for request-reply messages. Broadcasting the information about temp destinations is turned on by default so that consumers of a request-reply message can be connected to another broker in the network and still send back the reply on the temporary destination specified in the JMSReplyTo header. In an application scenario where most/all messages use request-reply pattern, this will generate additional traffic on the broker network as every message typically sets a unique JMSReplyTo address (which causes a new temp destination to be created and broadcasted via an advisory message in the network of brokers). <br clear="none"> When disabling this feature such network traffic can be reduced but then producer and consumers of a request-reply message need to be connected to the same broker. Remote consumers (i.e. connected via another broker in your network) won't be able to send the reply message but instead raise a "temp destination does not exist" exception.</p></td></tr><tr><td colspan="1" rowspan="1"><p>alwaysSyncSend</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>(version 5.6) When true, non persistent messages are sent to the remote broker using request/reply in place of a oneway. This setting treats both persistent and non-persistent messages the same.</p></td></tr><tr><td colspan="1" rowspan="1"><p>staticBridge</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>(version 5.6) If set to true, broker will not dynamically respond to new consumers. It will only use <code>staticallyIncludedDestinations</code> to create demand subscriptions</p></td></tr><tr><td colspan="1" rowspan="1">userName</td><td colspan="1" rowspan="1">null</td><td colspan="1" rowspan="1">The username to authenticate against the remote broker</td></tr><tr><td colspan="1" rowspan="1">password</td><td colspan="1" rowspan="1">null</td><td colspan="1" rowspan="1">The password for the username to authenticate against the remote broker</td></tr></tbody></table><h4>Reliability</h4><p>Networks of brokers do reliable store and forward of messages. If the source is durable, persistent messages on a queue or a durable topic subscription, a network will retain the durability guarantee. <br clear="none"> However networks cannot add durability when the source is non durable. Non durable topic subscriptions and temporary destinations (both queues and topics) are non durable by definition. When non durable<br clear="none"> sources are networked, in the event of a failure, inflight messages can be lost.</p><h4>Ordering</h4><p>Total message ordering is not preserved with networks of brokers. Total ordering <link><page ri:content-title="How do I preserve order of messages"></page><plain-text-link-body>works with a single consumer</plain-text-link-body></link> but a networkBridge introduces a second consumer. In addition, network bridge consumers forward messages via producer.send(..), so they go from the head of the queue on the forwarding broker to the tail of the queue on the target. If single consumer moves between networked brokers, total order may be preserved if all messages always follow the consumer but this can be difficult to guarantee with large message backlogs.</p><h4>When to use and not use Conduit subscriptions</h4><p>ActiveMQ relies on information about active consumers (subscriptions) to pass messages around the network. A broker interprets a subscription from a remote (networked) broker in the same way as it would a subscription from a local client connection and routes a copy of any relevant message to each subscription. With Topic subscriptions and with more than one remote subscription, a remote broker would interpret each message copy as valid, so when it in turns routes the messages to its own local connections, duplicates would occur. Hence default conduit behavior consolidates all matching subscription information to prevent duplicates flowing around the network. With this default behaviour, N subscriptions on a remote broker look like a single subscription to the networked broker.</p><p>However - duplicate subscriptions is a useful feature to exploit if you are only using Queues. As the load balancing algorithm will attempt to share message load evenly, consumers across a network will equally share the message load only if the flag <code>conduitSubscriptions=false</code>. Here's an example. Suppose you have two brokers, A and B, that are connected to one another via a forwarding bridge. Connected to broker A, you have a consumer that subscribes to a queue called <code>Q.TEST</code>. Connected to broker B, you have two consumers that also subscribe to <code>Q.TEST</code>. All consumers have equal priority. Then you start a producer on broker A that writes 30 messages to <code>Q.TEST</code>. By default, (<code>conduitSubscriptions=true</code>), 15 messages will be sent to the consumer on broker A and the resulting 15 messages will be sent to the two consumers on broker B. The message load has not been equally spread across all three consumers because, by default, broker A views the two subscriptions on broker B as one. If you had set <code>conduitSubscriptions</code> to <code>false</code>, then each of the three consumers would have been given 10 messages.</p><h4>Duplex network connectors</h4><p>By default a network bridge forwards messages on demand in one direction over a single connection. When <code>duplex=true</code>, the same connection is used for a network bridge in the opposite directions, resulting in a bi-directional bridge. The network bridge configuration is propagated to the other broker so the duplex bridge is an exact replica or the original.</p><p><br clear="none"> Given two brokers, broker A and broker B, a duplex bridge on A to B is the same as a default bridge on A to B and a default bridge on B to A.</p><p><br clear="none"> Note, if you want to configure more than one duplex network bridge between two brokers, to increase throughput or to partition topics and queues, you must provide unique names for each:</p><structured-macro ac:macro-id="1f2ae005-df9c-498c-8111-a7e5665fd971" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><networkConnectors>
+ <networkConnector name="SYSTEM1" duplex="true" uri="static:(tcp://10.x.x.x:61616)">
<dynamicallyIncludedDestinations>
- <topic physicalName="outgoing.System1" />
+ <topic physicalName="outgoing.System1" />
</dynamicallyIncludedDestinations>
</networkConnector>
- <networkConnector name="SYSTEM2" duplex="true" uri="static:(tcp://10.x.x.x:61616)">
+ <networkConnector name="SYSTEM2" duplex="true" uri="static:(tcp://10.x.x.x:61616)">
<dynamicallyIncludedDestinations>
- <topic physicalName="outgoing.System2"/>
+ <topic physicalName="outgoing.System2"/>
</dynamicallyIncludedDestinations>
</networkConnector>
- </networkConnectors>]]></script>
-</div></div><h4 id="NetworksofBrokers-Conduitsubscriptionsandconsumerselectors">Conduit subscriptions and consumer selectors</h4><p>Conduit subscriptions ignore consumer selectors on the local broker and send all messages to the remote one. Selectors are then parsed on the remote brokers before messages are dispatched to consumers. This concept could create some problems with consuming on queues using selectors in a multi-broker network. Imagine a situation when you have a producing broker forwarding messages to two receiving brokers and each of these two brokers have a consumer with different selector. Since no selectors are evaluated on the producer broker side, you can end up with all messages going to only one of the brokers, so messages with certain property will not be consumed. If you need to support this use case, please turn off <code>conduitSubscription</code> feature.</p><h4 id="NetworksofBrokers-ConfigurationPitfalls">Configuration Pitfalls</h4><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Networks do not work as expected (they cannot dynamically respond to new consumers) if the <code>advisorySupport</code> broker property is disabled. A fully statically configured network is the only option if <code>advisorySupport</code> is disabled. Read more about it in the following section.</p></div></div><h3 id="NetworksofBrokers-Networksofbrokersandadvisories">Networks of brokers and advisories</h3><p>Network of brokers relies heavily on advisory messages, as they are used under the hood to express interest in new consumers on the remote end. By default, when network connector starts it defines one consumer on the following topic <code>ActiveMQ.Advisory.Consumer.></code> (let's ignore temporary destination for the moment). In this way, when consumer connects (or disconnects) to the remote broker, the local broker will get notified and will treat it as one more consumer it had to deal with.</p><p>This is all fine and well in small networks and environments whit small number of destinations and consumers. But as things starts to grow a default model (listen to everything, share everything) won't scale well. That's why there are many ways you can use to filter destinations that will be shared between brokers.</p><h4 id="NetworksofBrokers-Dynamicnetworks">Dynamic networks</h4><p>Let's start with dynamically configured networks. This means that we only want to send messages to the remote broker when there's a consumer there. If we want to limit this behavior only on certain destinations we will use <code>dynamicallyIncludedDestinations</code>, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnector uri="static:(tcp://host)">
+ </networkConnectors></plain-text-body></structured-macro><h4>Conduit subscriptions and consumer selectors</h4><p>Conduit subscriptions ignore consumer selectors on the local broker and send all messages to the remote one. Selectors are then parsed on the remote brokers before messages are dispatched to consumers. This concept could create some problems with consuming on queues using selectors in a multi-broker network. Imagine a situation when you have a producing broker forwarding messages to two receiving brokers and each of these two brokers have a consumer with different selector. Since no selectors are evaluated on the producer broker side, you can end up with all messages going to only one of the brokers, so messages with certain property will not be consumed. If you need to support this use case, please turn off <code>conduitSubscription</code> feature.</p><h4>Configuration Pitfalls</h4><structured-macro ac:macro-id="2d3a18bd-173c-4ea9-8852-7e57cded973c" ac:name="warning" ac:schema-version="1"><rich-text-body><p>Networks do not work as expected (they cannot dynamically respond to new consumers) if the <code>advisorySupport</code> broker property is disabled. A fully statically configured network is the only option if <code>advisorySupport</code> is disabled. Read more about it in the following section.</p></rich-text-body></structured-macro><h3>Networks of brokers and advisories</h3><p>Network of brokers relies heavily on advisory messages, as they are used under the hood to express interest in new consumers on the remote end. By default, when network connector starts it defines one consumer on the following topic <code>ActiveMQ.Advisory.Consumer.></code> (let's ignore temporary destination for the moment). In this way, when consumer connects (or disconnects) to the remote broker, the local broker will get notified and will treat it as one more consumer it had to deal with.</p><p>This is all fine and well in small networks and environments whit small number of destinations and consumers. But as things starts to grow a default model (listen to everything, share everything) won't scale well. That's why there are many ways you can use to filter destinations that will be shared between brokers.</p><h4>Dynamic networks</h4><p>Let's start with dynamically configured networks. This means that we only want to send messages to the remote broker when there's a consumer there. If we want to limit this behavior only on certain destinations we will use <code>dynamicallyIncludedDestinations</code>, like</p><structured-macro ac:macro-id="4ac4b5a1-081f-44b0-94f7-b64792e7f134" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><networkConnector uri="static:(tcp://host)">
<dynamicallyIncludedDestinations>
- <queue physicalName="include.test.foo"/>
- <topic physicalName="include.test.bar"/>
+ <queue physicalName="include.test.foo"/>
+ <topic physicalName="include.test.bar"/>
</dynamicallyIncludedDestinations>
-</networkConnector>]]></script>
-</div></div><p>In versions of ActiveMQ prior to 5.6, the broker would still use the same advisory filter and express interest in all consumers on the remote broker. The actual filtering will be done during message dispatch. This is suboptimal solution in huge networks as it creates a lot of "advisory" traffic and load on the brokers. Starting with version 5.6, the broker will automatically create an appropriate advisory filter and express interest only in dynamically included destinations. For our example it will be "<code>ActiveMQ.Advisory.Consumer.Queue.include.test.foo,ActiveMQ.Advisory.Consumer.Topic.include.test.bar</code>". This can dramatically improve behavior of the network in complex and high-load environments.</p><p>In older broker versions we can achieve the same thing with a slightly more complicated configuration. The actual advisory filter that controls in which consumers we are interested is defined with the <code>destinationFilter</code> connector property. Its default value is ">", which is concatenated to the <code>"ActiveMQ.Advisory.Consumer."</code> prefix. So to achieve the same thing, we would need to do the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnector uri="static:(tcp://host)" destinationFilter="Queue.include.test.foo,ActiveMQ.Advisory.Consumer.Topic.include.test.bar">
+</networkConnector></plain-text-body></structured-macro><p>In versions of ActiveMQ prior to 5.6, the broker would still use the same advisory filter and express interest in all consumers on the remote broker. The actual filtering will be done during message dispatch. This is suboptimal solution in huge networks as it creates a lot of "advisory" traffic and load on the brokers. Starting with version 5.6, the broker will automatically create an appropriate advisory filter and express interest only in dynamically included destinations. For our example it will be "<code>ActiveMQ.Advisory.Consumer.Queue.include.test.foo,ActiveMQ.Advisory.Consumer.Topic.include.test.bar</code>". This can dramatically improve behavior of the network in complex and high-load environments.</p><p>In older broker versions we can achieve the same thing with a slightly more complicated configuration. The actual advisory filter that controls in which consumers we are interested is defined with the <code>destinationFilter</code> connector property. Its default value is ">", which is concatenated to the <code>"ActiveMQ.Advisory.Consumer."</code> prefix. So to achieve the same thing, we would need to do the following:</p><structured-macro ac:macro-id="b22607b8-6df7-4e5d-bdb3-aa5081570fa4" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><networkConnector uri="static:(tcp://host)" destinationFilter="Queue.include.test.foo,ActiveMQ.Advisory.Consumer.Topic.include.test.bar">
<dynamicallyIncludedDestinations>
- <queue physicalName="include.test.foo"/>
- <topic physicalName="include.test.bar"/>
+ <queue physicalName="include.test.foo"/>
+ <topic physicalName="include.test.bar"/>
</dynamicallyIncludedDestinations>
-</networkConnector>]]></script>
-</div></div><p>Note that first destination does not have the prefix because it's already implied. It's a bit more complicated to set and maintain, but it will work. And if you're using 5.6 or newer version of the broker just including desired destinations with <code>dynamicallyIncludedDestinations</code> should suffice.</p><p>This also explains why dynamic networks do not work if you turn off advisory support on the brokers. The brokers in this case cannot dynamically respond to new consumers.</p><h4 id="NetworksofBrokers-Purestaticnetworks">Pure static networks</h4><p>If you wish to completely protect the broker from any influence of consumers on the remote broker, or if you wish to use the brokers as a simple proxy and forward all messages to the remote side no matter if there are consumers there or not, static networks are something you should consider.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnector uri="static:(tcp://host)" staticBridge="true">
+</networkConnector></plain-text-body></structured-macro><p>Note that first destination does not have the prefix because it's already implied. It's a bit more complicated to set and maintain, but it will work. And if you're using 5.6 or newer version of the broker just including desired destinations with <code>dynamicallyIncludedDestinations</code> should suffice.</p><p>This also explains why dynamic networks do not work if you turn off advisory support on the brokers. The brokers in this case cannot dynamically respond to new consumers.</p><h4>Pure static networks</h4><p>If you wish to completely protect the broker from any influence of consumers on the remote broker, or if you wish to use the brokers as a simple proxy and forward all messages to the remote side no matter if there are consumers there or not, static networks are something you should consider.</p><structured-macro ac:macro-id="a3232ba0-b260-4303-930c-1fccf3f9f4cd" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><networkConnector uri="static:(tcp://host)" staticBridge="true">
<staticallyIncludedDestinations>
- <queue physicalName="always.include.queue"/>
+ <queue physicalName="always.include.queue"/>
</staticallyIncludedDestinations>
-</networkConnector>]]></script>
-</div></div><p>The <code>staticBridge</code> parameter is available since version 5.6 and it means that the local broker will not subscribe to any advisory topics on the remote broker, meaning it is not interested in whether there are any consumers there. Additionally, you need to add a list of destinations to <code>staticallyIncludedDestinations</code>. This will have the same effect as having an additional consumer on the destinations so messages will be forwarded to the remote broker as well. As there is no <code>staticBridge</code> parameter in the earlier versions of ActiveMQ, you can trick the broker by setting <code>destinationFilter</code> to listen to an unused advisory topic, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnector uri="static:(tcp://host)" destinationFilter="NO_DESTINATION">
+</networkConnector></plain-text-body></structured-macro><p>The <code>staticBridge</code> parameter is available since version 5.6 and it means that the local broker will not subscribe to any advisory topics on the remote broker, meaning it is not interested in whether there are any consumers there. Additionally, you need to add a list of destinations to <code>staticallyIncludedDestinations</code>. This will have the same effect as having an additional consumer on the destinations so messages will be forwarded to the remote broker as well. As there is no <code>staticBridge</code> parameter in the earlier versions of ActiveMQ, you can trick the broker by setting <code>destinationFilter</code> to listen to an unused advisory topic, like</p><structured-macro ac:macro-id="3c495026-e279-4fb3-8761-9ab67cf7aaa7" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><networkConnector uri="static:(tcp://host)" destinationFilter="NO_DESTINATION">
<staticallyIncludedDestinations>
- <queue physicalName="always.include.queue"/>
+ <queue physicalName="always.include.queue"/>
</staticallyIncludedDestinations>
-</networkConnector>]]></script>
-</div></div><p>If configured like this, broker will try to listen for new consumers on <code>ActiveMQ.Advisory.Consumer.NO_DESTINATION</code>, which will never have messages so it will be protected from information on remote broker consumers.</p><h3 id="NetworksofBrokers-virtualconsumersDynamicnetworksandVirtualDestinations(Newfor5.13.0)"><span class="confluence-anchor-link" id="NetworksofBrokers-virtualconsumers"></span>Dynamic networks and Virtual Destinations (New for 5.13.0)</h3><p>As described above, a network of brokers can be configured to only send messages to a remote broker when there's a consumer on an included destination.  However, let's consider some cases of how dynamic flow occurs when <a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a> are in use.</p><h4 id="NetworksofBrokers-VirtualDestinationconsumersandCompositeDestinations">Virtual Destination consumers and Composite Destinations</h4><p>Here is an example of two brokers networked together.  The Local Broker contains the network connector configured with a <code>dynamicallyIncludedDestination</code> and the Remote Broker is configured with a CompositeTopic:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Local Broker</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnector uri="static:(tcp://host)">
+</networkConnector></plain-text-body></structured-macro><p>If configured like this, broker will try to listen for new consumers on <code>ActiveMQ.Advisory.Consumer.NO_DESTINATION</code>, which will never have messages so it will be protected from information on remote broker consumers.</p><h3><structured-macro ac:macro-id="72009f9e-4c23-4f3d-8834-196c93f9cc8a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">virtualconsumers</parameter></structured-macro>Dynamic networks and Virtual Destinations (New for 5.13.0)</h3><p>As described above, a network of brokers can be configured to only send messages to a remote broker when there's a consumer on an included destination.  However, let's consider some cases of how dynamic flow occurs when <link><page ri:content-title="Virtual Destinations"></page></link> are in use.</p><h4>Virtual Destination consumers and Composite Destinations</h4><p>Here is an example of two brokers networked together.  The Local Broker contains the network connector configured with a <code>dynamicallyIncludedDestination</code> and the Remote Broker is configured with a CompositeTopic:</p><structured-macro ac:macro-id="4cab5c8f-e7ba-48ee-9acf-8f4304a1a0ad" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Local Broker</parameter><plain-text-body><networkConnector uri="static:(tcp://host)">
<dynamicallyIncludedDestinations>
- <topic physicalName="include.bar"/>
+ <topic physicalName="include.bar"/>
</dynamicallyIncludedDestinations>
-</networkConnector>]]></script>
-</div></div><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Remote Broker</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<compositeTopic name="include.bar" forwardOnly="false">
+</networkConnector></plain-text-body></structured-macro><structured-macro ac:macro-id="493d5a52-c269-432a-89f1-b00f2f06050e" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Remote Broker</parameter><plain-text-body><compositeTopic name="include.bar" forwardOnly="false">
<forwardTo>
- <queue physicalName="include.bar.forward" />
+ <queue physicalName="include.bar.forward" />
</forwardTo>
-</compositeTopic >]]></script>
-</div></div><p>In this example, let's consider a single consumer on the Remote Broker on the queue <code>include.bar.forward</code>.  If a message is sent directly to the Remote Broker on the topic <code>include.bar</code>, it will be forwarded to the queue <code>include.bar.forward</code> and the consumer will receive it.  However, if a message is published to the same topic on the Local Broker, this message will not be forwarded to the Remote Broker.</p><p>The message is not forwarded because a consumer on the <code>queue include.bar.forward</code> would not be detected as part of the <code>dynamicallyIncludedDestinations</code> list in the Local Broker.  Messages would not be forwarded to the Remote Broker unless there was a consumer on the original topic as well (in this case <code>include.bar</code>).  This can be fixed by configuring the Local Broker to listen for Virtual Destination Subscriptions.  </p><p>First, we need to configure the Remote Broker to send advisory messages when consumers subscribe to a destination that matches a Virtual Destination.  In this case, internally a match is determined through the use of a Destination Filter that determines whether one destination forwards to another destination.  To enable this, set the property <code>useVirtualDestSubs</code> on the Remote Broker to <code>true</code>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Remote Broker</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+</compositeTopic ></plain-text-body></structured-macro><p>In this example, let's consider a single consumer on the Remote Broker on the queue <code>include.bar.forward</code>.  If a message is sent directly to the Remote Broker on the topic <code>include.bar</code>, it will be forwarded to the queue <code>include.bar.forward</code> and the consumer will receive it.  However, if a message is published to the same topic on the Local Broker, this message will not be forwarded to the Remote Broker.</p><p>The message is not forwarded because a consumer on the <code>queue include.bar.forward</code> would not be detected as part of the <code>dynamicallyIncludedDestinations</code> list in the Local Broker.  Messages would not be forwarded to the Remote Broker unless there was a consumer on the original topic as well (in this case <code>include.bar</code>).  This can be fixed by configuring the Local Broker to listen for Virtual Destination Subscriptions.  </p><p>First, we need to configure the Remote Broker to send advisory messages when consumers subscribe to a destination that matches a Virtual Destination.  In this case, internally a match is determined through the use of a Destination Filter that determines whether one destination forwards to another destination.  To enable this, set the property <code>useVirtualDestSubs</code> on the Remote Broker to <code>true</code>:</p><structured-macro ac:macro-id="d63e43ed-c8f7-40db-8e27-0a9339b9d6a5" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Remote Broker</parameter><plain-text-body><?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<beans xmlns="http://activemq.org/config/1.0">
- <broker name="remoteBroker" useVirtualDestSubs="true">
+ <broker name="remoteBroker" useVirtualDestSubs="true">
.....
</broker>
</beans>
-]]></script>
-</div></div><p><br clear="none">Next, the network connector on the Local Broker needs to be configured to listen for the new advisory messages by setting the <code>useVirtualDestSubs</code> property to <code>true</code>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Local Broker</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnector uri="static:(tcp://host)" useVirtualDestSubs="true">
+</plain-text-body></structured-macro><p><br clear="none">Next, the network connector on the Local Broker needs to be configured to listen for the new advisory messages by setting the <code>useVirtualDestSubs</code> property to <code>true</code>:</p><structured-macro ac:macro-id="d689f9f7-af5e-4956-987a-5f57fd207c8b" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Local Broker</parameter><plain-text-body><networkConnector uri="static:(tcp://host)" useVirtualDestSubs="true">
<dynamicallyIncludedDestinations>
- <topic physicalName="include.bar"/>
+ <topic physicalName="include.bar"/>
</dynamicallyIncludedDestinations>
-</networkConnector>]]></script>
-</div></div><p>Now, if a consumer comes subscribes to the queue <code>include.bar.forward</code> on the Remote Broker, the Local Broker will forward messages that are sent to the topic <code>include.bar.</code></p><h4 id="NetworksofBrokers-VirtualDestinationConsumersonDestinationCreation">Virtual Destination Consumers on Destination Creation</h4><p>Now let's consider the use case above where there is the same composite topic but no consumers on the queue.<br clear="none"> </p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Remote Broker</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<compositeTopic name="include.bar" forwardOnly="false">
+</networkConnector></plain-text-body></structured-macro><p>Now, if a consumer comes subscribes to the queue <code>include.bar.forward</code> on the Remote Broker, the Local Broker will forward messages that are sent to the topic <code>include.bar.</code></p><h4>Virtual Destination Consumers on Destination Creation</h4><p>Now let's consider the use case above where there is the same composite topic but no consumers on the queue.<br clear="none"> </p><structured-macro ac:macro-id="8c7c9560-f4ac-4fb2-b0a6-0f1f32df9fec" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Remote Broker</parameter><plain-text-body><compositeTopic name="include.bar" forwardOnly="false">
<forwardTo>
- <queue physicalName="include.bar.forward" />
+ <queue physicalName="include.bar.forward" />
</forwardTo>
-</compositeTopic >]]></script>
-</div></div><p>There is a Composite Topic configured on the Remote Broker, and the Local Broker is networked to it.  </p><p>Even though we have enabled <code>useVirtualDestSubs</code>, messages will not be forwarded to the Remote Broker unless a consumer subscribes to the forwarded queue.  Without a consumer, messages would be dropped as they are sent to a topic on the Local Broker (<code>include.bar</code>).  In this situation it is desirable to have messages forwarded based on the existence of a virtual destination that forwards to:</p><ul><li>one or more queues; or</li><li>topics that have durable subscriptions.</li></ul><p> </p><p>Both of these conditions are considered as emitting demand for messages to the Local Broker, despite there being no active consumers on those destinations.</p><p> </p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Remote Broker</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+</compositeTopic ></plain-text-body></structured-macro><p>There is a Composite Topic configured on the Remote Broker, and the Local Broker is networked to it.  </p><p>Even though we have enabled <code>useVirtualDestSubs</code>, messages will not be forwarded to the Remote Broker unless a consumer subscribes to the forwarded queue.  Without a consumer, messages would be dropped as they are sent to a topic on the Local Broker (<code>include.bar</code>).  In this situation it is desirable to have messages forwarded based on the existence of a virtual destination that forwards to:</p><ul><li>one or more queues; or</li><li>topics that have durable subscriptions.</li></ul><p> </p><p>Both of these conditions are considered as emitting demand for messages to the Local Broker, despite there being no active consumers on those destinations.</p><p> </p><structured-macro ac:macro-id="8d005178-18f5-4298-886f-f554b3f81c23" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Remote Broker</parameter><plain-text-body><?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<beans xmlns="http://activemq.org/config/1.0">
- <broker name="remoteBroker" useVirtualDestSubs="true" useVirtualDestSubsOnCreation="true">
+ <broker name="remoteBroker" useVirtualDestSubs="true" useVirtualDestSubsOnCreation="true">
.....
</broker>
-</beans>]]></script>
-</div></div><p>With this configuration, when the queue <code>include.bar.forward</code> is created, a Virtual Destination consumer advisory will be sent to the Local Broker so that it knows to forward messages based on the existence of the Composite Topic that forwards to a queue.</p><h4 id="NetworksofBrokers-CompositeDestinationconsumersandVirtualTopics">Composite Destination consumers and Virtual Topics </h4><p>The above examples show how to configure a Composite Destination but a Virtual Topic will also work.  In the example below, a consumer on a queue for a Virtual Topic on the Remote Broker will now cause demand and messages will be sent across a network from the Local Broker.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Local Broker</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnector uri="static:(tcp://host)">
+</beans></plain-text-body></structured-macro><p>With this configuration, when the queue <code>include.bar.forward</code> is created, a Virtual Destination consumer advisory will be sent to the Local Broker so that it knows to forward messages based on the existence of the Composite Topic that forwards to a queue.</p><h4>Composite Destination consumers and Virtual Topics </h4><p>The above examples show how to configure a Composite Destination but a Virtual Topic will also work.  In the example below, a consumer on a queue for a Virtual Topic on the Remote Broker will now cause demand and messages will be sent across a network from the Local Broker.</p><structured-macro ac:macro-id="9416bf2d-1da1-4e0f-8d2e-fd42401b6f39" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Local Broker</parameter><plain-text-body><networkConnector uri="static:(tcp://host)">
<dynamicallyIncludedDestinations>
- <topic physicalName="VirtualTopic.>"/>
+ <topic physicalName="VirtualTopic.>"/>
</dynamicallyIncludedDestinations>
-</networkConnector>]]></script>
-</div></div><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Remote Broker</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
+</networkConnector></plain-text-body></structured-macro><structured-macro ac:macro-id="df4f4215-dd4e-475c-9e72-feaaa1f1d9bb" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><parameter ac:name="title">Remote Broker</parameter><plain-text-body><?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<beans xmlns="http://activemq.org/config/1.0">
- <broker name="remoteBroker" useVirtualDestSubs="true" >
+ <broker name="remoteBroker" useVirtualDestSubs="true" >
.....
</broker>
-</beans>]]></script>
-</div></div><h3 id="NetworksofBrokers-ExampleConfigurationusingNetworkConnectorproperties">Example Configuration using NetworkConnector properties</h3><p>This part of an example configuration for a Broker</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnectors>
- <networkConnector uri="static:(tcp://localhost:61617)"
- name="bridge"
- conduitSubscriptions="true"
- decreaseNetworkConsumerPriority="false">
+</beans></plain-text-body></structured-macro><h3>Example Configuration using NetworkConnector properties</h3><p>This part of an example configuration for a Broker</p><structured-macro ac:macro-id="5ee27478-9e11-4b8e-a2a7-6bf226ae703b" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><networkConnectors>
+ <networkConnector uri="static:(tcp://localhost:61617)"
+ name="bridge"
+ conduitSubscriptions="true"
+ decreaseNetworkConsumerPriority="false">
<dynamicallyIncludedDestinations>
- <queue physicalName="include.test.foo"/>
- <topic physicalName="include.test.bar"/>
+ <queue physicalName="include.test.foo"/>
+ <topic physicalName="include.test.bar"/>
</dynamicallyIncludedDestinations>
<excludedDestinations>
- <queue physicalName="exclude.test.foo"/>
- <topic physicalName="exclude.test.bar"/>
+ <queue physicalName="exclude.test.foo"/>
+ <topic physicalName="exclude.test.bar"/>
</excludedDestinations>
<staticallyIncludedDestinations>
- <queue physicalName="always.include.queue"/>
- <topic physicalName="always.include.topic"/>
+ <queue physicalName="always.include.queue"/>
+ <topic physicalName="always.include.topic"/>
</staticallyIncludedDestinations>
</networkConnector>
</networkConnectors>
-]]></script>
-</div></div><p>Note that at the moment <code>excludedDestinations</code> property doesn't affect <code>staticallyIncludedDestinations</code>.</p><p>It is possible to have more than one network connector between two brokers. Each network connector uses one underlying transport connection, so you may wish to do this to increase throughput, or have a more flexible configuration.</p><p><br clear="none"> For example, if using distributed queues, you may wish to have equivalent weighting to queue receivers across the network, but only when the receivers are active - e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<networkConnectors>
- <networkConnector uri="static:(tcp://localhost:61617)"
- name="queues_only"
- conduitSubscriptions="false"
- decreaseNetworkConsumerPriority="false">
+</plain-text-body></structured-macro><p>Note that at the moment <code>excludedDestinations</code> property doesn't affect <code>staticallyIncludedDestinations</code>.</p><p>It is possible to have more than one network connector between two brokers. Each network connector uses one underlying transport connection, so you may wish to do this to increase throughput, or have a more flexible configuration.</p><p><br clear="none"> For example, if using distributed queues, you may wish to have equivalent weighting to queue receivers across the network, but only when the receivers are active - e.g.</p><structured-macro ac:macro-id="c7412d67-afbd-4dba-a147-a89424d0ccf6" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><networkConnectors>
+ <networkConnector uri="static:(tcp://localhost:61617)"
+ name="queues_only"
+ conduitSubscriptions="false"
+ decreaseNetworkConsumerPriority="false">
<excludedDestinations>
- <topic physicalName=">"/>
+ <topic physicalName=">"/>
</excludedDestinations>
</networkConnector>
</networkConnectors>
-]]></script>
-</div></div><p><strong>N.B.</strong> You can only use <a shape="rect" href="wildcards.xml">wildcards</a> in the <code>excludedDestinations</code> and <code>dynamicallyIncludedDestinations</code> properties.<br clear="none"> <strong>N.B.</strong> <strong>Do not</strong> change the name of the bridge or the name of the Broker if you are using durable topic subscribers across the network. Internally ActiveMQ uses the network name and broker name to build a unique but repeatable durable subscriber name for the network.</p><h3 id="NetworksofBrokers-StuckMessages(version5.6)">Stuck Messages (version 5.6)</h3><p>By default, it is not permissible for a message to be replayed back to the broker from which it came. This ensures that messages do not loop when duplex or by directional network connectors are configured. Occasionally it is desirable to allow replay for queues. Consider a scenario where a bidirectional bridge exists between a broker pair. Producers and Consumers get to randomly choose a broker using the failover transport. If one broker is restarted for maintenance, messages accumulated on that broker, that crossed the network bridge, will not be available to consumers till they reconnect to the broker. One solution to this problem is to force a client reconnect using <a shape="rect" class="external-link" href="http://activemq.apache.org/failover-transport-reference.html#FailoverTransportReference-BrokersideOptionsforFailover">rebalanceClusterClients</a>. Another, is to allow replay of messages back to the origin as there is no local consumer on that broker.<br clear="none"> There is a destination policy that allows this behavior for queues by configuring a <code>conditionalNetworkBridgeFilterFactory</code> with <code>replayWhenNoConsumers=true</code>. The <code>conditionalNetworkBridgeFilterFactory</code> provides an optional <code>replayDelay</code> based on the broker-in time.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <destinationPolicy>
+</plain-text-body></structured-macro><p><strong>N.B.</strong> You can only use <link><page ri:content-title="Wildcards"></page><plain-text-link-body>wildcards</plain-text-link-body></link> in the <code>excludedDestinations</code> and <code>dynamicallyIncludedDestinations</code> properties.<br clear="none"> <strong>N.B.</strong> <strong>Do not</strong> change the name of the bridge or the name of the Broker if you are using durable topic subscribers across the network. Internally ActiveMQ uses the network name and broker name to build a unique but repeatable durable subscriber name for the network.</p><h3>Stuck Messages (version 5.6)</h3><p>By default, it is not permissible for a message to be replayed back to the broker from which it came. This ensures that messages do not loop when duplex or by directional network connectors are configured. Occasionally it is desirable to allow replay for queues. Consider a scenario where a bidirectional bridge exists between a broker pair. Producers and Consumers get to randomly choose a broker using the failover transport. If one broker is restarted for maintenance, messages accumulated on that broker, that crossed the network bridge, will not be available to consumers till they reconnect to the broker. One solution to this problem is to force a client reconnect using <a shape="rect" href="http://activemq.apache.org/failover-transport-reference.html#FailoverTransportReference-BrokersideOptionsforFailover">rebalanceClusterClients</a>. Another, is to allow replay of messages back to the origin as there is no local consumer on that broker.<br clear="none"> There is a destination policy that allows this behavior for queues by configuring a <code>conditionalNetworkBridgeFilterFactory</code> with <code>replayWhenNoConsumers=true</code>. The <code>conditionalNetworkBridgeFilterFactory</code> provides an optional <code>replayDelay</code> based on the broker-in time.</p><structured-macro ac:macro-id="647eee17-8fe0-44be-8292-5e1917c16bac" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body> <destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue="TEST.>" enableAudit="false">
+ <policyEntry queue="TEST.>" enableAudit="false">
<networkBridgeFilterFactory>
- <conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true"/>
+  <conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true"/>
</networkBridgeFilterFactory>
</policyEntry>
</policyEntries>
</policyMap>
- </destinationPolicy>]]></script>
-</div></div><p><strong>N.B.:</strong> When using <code>replayWhenNoConsumers=true</code> for versions < 5.9, it is necessary to also disable the cursors duplicate detection using <code><strong>enableAudit=false</strong></code> as the cursor could mark the replayed messages as duplicates (depending on the time window between playing and replaying these messages over the network bridge). The problem is fully explained in this <a shape="rect" class="external-link" href="http://tmielke.blogspot.de/2012/03/i-have-messages-on-queue-but-they-dont.html" rel="nofollow">blog post</a>.</p><h4 id="NetworksofBrokers-Throttlinganetworkconsumer">Throttling a network consumer</h4><p>The <code>conditionalNetworkBridgeFilterFactory</code> factory allows a rate limit to be specified for a destination, such that network consumer can be throttled. Prefetch for a network consumer is largely negated by the fact that a network consumer relays a message typically acks very quickly so even with a low prefetch and decreased priority a network consumer can starve a modestly quick local consumer. Throttling provides a remedy for this.</p></div>
+ </destinationPolicy></plain-text-body></structured-macro><p><strong>N.B.:</strong> When using <code>replayWhenNoConsumers=true</code> for versions < 5.9, it is necessary to also disable the cursors duplicate detection using <code><strong>enableAudit=false</strong></code> as the cursor could mark the replayed messages as duplicates (depending on the time window between playing and replaying these messages over the network bridge). The problem is fully explained in this <a shape="rect" href="http://tmielke.blogspot.de/2012/03/i-have-messages-on-queue-but-they-dont.html">blog post</a>.</p><h4>Throttling a network consumer</h4><p>The <code>conditionalNetworkBridgeFilterFactory</code> factory allows a rate limit to be specified for a destination, such that network consumer can be throttled. Prefetch for a network consumer is largely negated by the fact that a network consumer relays a message typically acks very quickly so even with a low prefetch and decreased priority a network consumer can starve a modestly quick local consumer. Throttling provides a remedy for this.</p></div>
diff --git a/new-features-in-41.xml b/new-features-in-41.xml
index 04aa803..f32b3fd 100644
--- a/new-features-in-41.xml
+++ b/new-features-in-41.xml
@@ -1,4 +1,5 @@
-<div class="wiki-content maincontent"><h2 id="NewFeaturesin4.1-NewFeaturesinApacheActiveMQ4.1">New Features in Apache ActiveMQ 4.1</h2>
+<div class="wiki-content maincontent"><h2>New Features in Apache ActiveMQ 4.1</h2>
-<ul><li><a shape="rect" href="shared-file-system-master-slave.xml">Shared File System Master Slave</a></li><li><a shape="rect" href="jdbc-master-slave.xml">JDBC Master Slave</a></li><li><a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a></li><li><a shape="rect" href="configure-startup-destinations.xml">Configure Startup Destinations</a></li><li><a shape="rect" href="structured-message-properties-and-mapmessages.xml">Structured Message Properties and MapMessages</a></li></ul></div>
+<ul><li><link><page ri:content-title="Shared File System Master Slave"></page></link></li><li><link><page ri:content-title="JDBC Master Slave"></page></link></li><li><link><page ri:content-title="Virtual Destinations"></page></link></li><li><link><page ri:content-title="Configure Startup Destinations"></page></link></li><li><link><page ri:content-title="Structured Message Properties and MapMessages"></page></link></li></ul>
+</div>
diff --git a/new-features-in-50.xml b/new-features-in-50.xml
index c6f4f06..464ae86 100644
--- a/new-features-in-50.xml
+++ b/new-features-in-50.xml
@@ -1,6 +1,7 @@
-<div class="wiki-content maincontent"><h2 id="NewFeaturesin5.0-NewFeaturesin5.0">New Features in 5.0</h2>
+<div class="wiki-content maincontent"><h2>New Features in 5.0</h2>
<p>In the 5.0 release of Apache ActiveMQ there are the following new features:</p>
-<ul><li><a shape="rect" href="amq-message-store.xml">AMQ Message Store</a> (Faster Persistence!)</li><li><a shape="rect" href="message-cursors.xml">Message Cursors</a> (To handle very large number of stored messages)</li><li><a shape="rect" href="blob-messages.xml">Blob Messages</a></li><li><a shape="rect" href="command-agent.xml">Command Agent</a></li><li><a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> via <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Camel Integration</a></li><li><a shape="rect" href="logging-a-warning-if-you-forget-to-start-a-connection.xml">Logging a warning if you forget to start a Connection</a></li><li><a shape="rect" href="message-transformation.xml">Message Transformation</a></li><li><a shape="rect" href="mirrored-queues.xml">Mirrored Queues</a></li><li><a shape="rect" href="producer-flow-control.xml">Producer Flow Control</a></li></ul></div>
+<ul><li><link><page ri:content-title="AMQ Message Store"></page></link> (Faster Persistence!)</li><li><link><page ri:content-title="Message Cursors"></page></link> (To handle very large number of stored messages)</li><li><link><page ri:content-title="Blob Messages"></page></link></li><li><link><page ri:content-title="Command Agent"></page></link></li><li><link><page ri:content-title="Enterprise Integration Patterns"></page></link> via <a shape="rect" href="http://activemq.apache.org/camel/">Camel Integration</a></li><li><link><page ri:content-title="Logging a warning if you forget to start a Connection"></page></link></li><li><link><page ri:content-title="Message Transformation"></page></link></li><li><link><page ri:content-title="Mirrored Queues"></page></link></li><li><link><page ri:content-title="Producer Flow Control"></page></link></li></ul>
+</div>
diff --git a/new-features-in-51.xml b/new-features-in-51.xml
index fd6b766..e8624c6 100644
--- a/new-features-in-51.xml
+++ b/new-features-in-51.xml
@@ -1,9 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="NewFeaturesin5.1-NewFeaturesin5.1">New Features in 5.1</h2>
+<div class="wiki-content maincontent"><h2>New Features in 5.1</h2>
<p>In the 5.1.x release of Apache ActiveMQ there are the following new features:</p>
-<ul><li>You can use the new <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/DestinationSource.html">DestinationSource</a> on an ActiveMQConnection to access the available queues or topics or listen to queues/topics being created or deleted.
-<h2 id="NewFeaturesin5.1-NewFeaturesin5.1.1">New Features in 5.1</h2></li><li>Support for more graceful handling of <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ-1517">timeouts within MessageProducer.send</a></li><li>Add the option for a <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ-1572">backup channel that is already connected for the Failover transport</a></li><li>ActiveMQ configuration can now validate against an XSD which means that it can be embedded in a spring configuration file.</li><li>Stomp can now handle delivering Map and Object messages.</li></ul>
+<ul><li>You can use the new <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/DestinationSource.html">DestinationSource</a> on an ActiveMQConnection to access the available queues or topics or listen to queues/topics being created or deleted.
+<h2>New Features in 5.1</h2></li><li>Support for more graceful handling of <a shape="rect" href="http://issues.apache.org/activemq/browse/AMQ-1517">timeouts within MessageProducer.send</a></li><li>Add the option for a <a shape="rect" href="http://issues.apache.org/activemq/browse/AMQ-1572">backup channel that is already connected for the Failover transport</a></li><li>ActiveMQ configuration can now validate against an XSD which means that it can be embedded in a spring configuration file.</li><li>Stomp can now handle delivering Map and Object messages.</li></ul>
+
</div>
diff --git a/new-features-in-511.xml b/new-features-in-511.xml
index aadd89f..05c6c82 100644
--- a/new-features-in-511.xml
+++ b/new-features-in-511.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="NewFeaturesin5.11-NewFeaturesin5.11.0">New Features in 5.11.0</h2><ul class="alternate"><li><span style="line-height: 1.4285715;">Destination import/export for lock down mode <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5218">AMQ-5218</a></span></li><li><p>Dynamic camel root loading <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5351">AMQ-5351</a></p></li><li><p>MQTT - QOS2 mapped to virtual topics <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5290">AMQ-5290</a></p></li><li>start scripts simplification <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5378">AMQ-5378</a></li><li>Recover scheduler database option <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3758">AMQ-3758</a></li><li>Jetty 8</li><li>Karaf 2.4.1</li></ul></div>
+<div class="wiki-content maincontent"><h2>New Features in 5.11.0</h2><ul class="alternate"><li><span style="line-height: 1.4285715;">Destination import/export for lock down mode <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5218">AMQ-5218</a></span></li><li><p>Dynamic camel root loading <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5351">AMQ-5351</a></p></li><li><p>MQTT - QOS2 mapped to virtual topics <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5290">AMQ-5290</a></p></li><li>start scripts simplification <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5378">AMQ-5378</a></li><li>Recover scheduler database option <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-3758">AMQ-3758</a></li><li>Jetty 8</li><li>Karaf 2.4.1</li></ul></div>
diff --git a/new-features-in-513.xml b/new-features-in-513.xml
index c66e01b..9cff79c 100644
--- a/new-features-in-513.xml
+++ b/new-features-in-513.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="NewFeaturesin5.13-NewFeaturesin5.13.0">New Features in 5.13.0</h2><ul class="alternate"><li><span>New transport protocol, <a shape="rect" href="auto.xml">AUTO</a> <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5889">AMQ-5889</a></span></li><li><p>Dynamic network support for virtual consumers, <a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a> <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-6027">AMQ-6027</a></p></li><li><p>Pending message size metrics <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5923">AMQ-5923</a></p></li><li>New Java API for runtime configuration changes, <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5915"></a><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/plugin/java/JavaRuntimeConfigurationBroker.html"></a><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5915">J</a>avaRuntimeConfigurationBroker to compliment the current <a shape="rect" class="external-link" href="http://XML Runtime Plugin" rel="nofollow">http://activemq.apache.org/runtime-configuration.html</a>  <a shape="rect" class="external-link" 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 shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-5957">AMQ-5957</a><br clear="none"><br clear="none"></li></ul></div>
+<div class="wiki-content maincontent"><h2>New Features in 5.13.0</h2><ul class="alternate"><li><span>New transport protocol, <link><page ri:content-title="AUTO"></page></link> <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5889">AMQ-5889</a></span></li><li><p>Dynamic network support for virtual consumers, <link><page ri:content-title="Networks of Brokers"></page></link> <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-6027">AMQ-6027</a></p></li><li><p>Pending message size metrics <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5923">AMQ-5923</a></p></li><li>New Java API for runtime configuration changes, <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5915"></a><a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/plugin/java/JavaRuntimeConfigurationBroker.html"></a><a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5915">J</a>avaRuntimeConfigurationBroker to compliment the current <a shape="rect" href="http://XML Runtime Plugin">http://activemq.apache.org/runtime-configuration.html</a>  <a shape="rect" 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 shape="rect" href="https://issues.apache.org/jira/browse/AMQ-5957">AMQ-5957</a><br clear="none"><br clear="none"></li></ul></div>
diff --git a/new-features-in-52.xml b/new-features-in-52.xml
index 9d1826b..fc1656a 100644
--- a/new-features-in-52.xml
+++ b/new-features-in-52.xml
@@ -1,10 +1,8 @@
-<div class="wiki-content maincontent"><p>Apache ActiveMQ 5.2 is primarily a maintenance release which <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11841">resolves</a> </p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
-.
+<div class="wiki-content maincontent"><p>Apache ActiveMQ 5.2 is primarily a maintenance release which <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11841">resolves</a> <structured-macro ac:macro-id="e49737eb-d85e-4eea-be31-1555b5a39a91" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="count">true</parameter><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=10520&fixfor=11841&sorter/field=priority&sorter/order=DESC&tempMax=1000"></url></parameter></structured-macro>.</p>
-<h2 id="NewFeaturesin5.2-NewFeaturesin5.2">New Features in 5.2</h2>
+<h2>New Features in 5.2</h2>
<p>The new features and enhancements in this release include:</p>
-<ul><li><a shape="rect" href="advisory-message.xml">Additional advisory messages</a> for messages delivered/consumed fast producers/slow consumers, Usage limits, Slaves become masters etc.</li><li>Enhanced ssl context configuration through spring/xbean</li><li>New individual acknowledge mode for message consumption</li><li>Ability to configure the automatic discarding of the items being sent to the dead letter queue</li><li>Ability to limit the maximum number of connections to a Broker</li><li>Ability to configure <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/AMQ-1244">separate lock</a> Datasource for JDBC Master slave.</li><li>activemq-camel and activemq-connection-pool now have their own modules, no longer in activemq-core</li><li>The default <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> brokerUrl now uses the <a shape="rect" href="failover-transport-reference.xml">failover transport</a>.</li><li>Uses Apache Camel <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/camel-150-release.html">1.5</a>.</li></ul></div>
+<ul><li><link><page ri:content-title="Advisory Message"></page><link-body>Additional advisory messages</link-body></link> for messages delivered/consumed fast producers/slow consumers, Usage limits, Slaves become masters etc.</li><li>Enhanced ssl context configuration through spring/xbean</li><li>New individual acknowledge mode for message consumption</li><li>Ability to configure the automatic discarding of the items being sent to the dead letter queue</li><li>Ability to limit the maximum number of connections to a Broker</li><li>Ability to configure <a shape="rect" href="https://issues.apache.org/activemq/browse/AMQ-1244">separate lock</a> Datasource for JDBC Master slave.</li><li>activemq-camel and activemq-connection-pool now have their own modules, no longer in activemq-core</li><li>The default <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> brokerUrl now uses the <link><page ri:content-title="Failover Transport Reference"></page><link-body>failover transport</link-body></link>.</li><li>Uses Apache Camel <a shape="rect" href="http://activemq.apache.org/camel/camel-150-release.html">1.5</a>.</li></ul>
+</div>
diff --git a/new-features-in-53.xml b/new-features-in-53.xml
index 0c345ba..cd68cd4 100644
--- a/new-features-in-53.xml
+++ b/new-features-in-53.xml
@@ -1,7 +1,8 @@
-<div class="wiki-content maincontent"><p>Apache ActiveMQ 5.3 is primarily a maintenance release which <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11914&styleName=Html&projectId=10520">resolves</a> 334 issues.</p>
+<div class="wiki-content maincontent"><p>Apache ActiveMQ 5.3 is primarily a maintenance release which <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11914&styleName=Html&projectId=10520">resolves</a> 334 issues.</p>
-<h2 id="NewFeaturesin5.3-NewFeaturesin5.3">New Features in 5.3</h2>
+<h2>New Features in 5.3</h2>
<p>The new features and enhancements in this release include:</p>
-<ul><li>New <a shape="rect" href="kahadb.xml">KahaDB</a> persistent storage</li><li><a shape="rect" class="external-link" href="http://camel.apache.org">Camel 2.0.0</a> along with its web console</li><li>stomp over SSL and NIO support</li><li>Improved configuration - default one production oriented and a lot of use case configuration examples (like scalability and throughput)</li><li>Ability to query broker for statistics from non-Java clients (by sending a message)</li><li>More broker plugins included to help tracing messages in networks, improving logging, etc.</li><li>FTP support for blob messages</li><li>Improved activemq-admin to lookup for local processes if possible</li><li>... and much more</li></ul></div>
+<ul><li>New <link><page ri:content-title="KahaDB"></page></link> persistent storage</li><li><a shape="rect" href="http://camel.apache.org">Camel 2.0.0</a> along with its web console</li><li>stomp over SSL and NIO support</li><li>Improved configuration - default one production oriented and a lot of use case configuration examples (like scalability and throughput)</li><li>Ability to query broker for statistics from non-Java clients (by sending a message)</li><li>More broker plugins included to help tracing messages in networks, improving logging, etc.</li><li>FTP support for blob messages</li><li>Improved activemq-admin to lookup for local processes if possible</li><li>... and much more</li></ul>
+</div>
diff --git a/new-features-in-54.xml b/new-features-in-54.xml
index 3adc977..0dfbf98 100644
--- a/new-features-in-54.xml
+++ b/new-features-in-54.xml
@@ -1,9 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="NewFeaturesin5.4-NewFeaturesin5.4.1">New Features in 5.4.1</h2>
-<ul><li><a shape="rect" href="encrypted-passwords.xml">Encrypted passwords</a></li><li>Added selector support in <a shape="rect" href="ajax.xml">Ajax</a></li></ul>
+<div class="wiki-content maincontent"><h2>New Features in 5.4.1</h2>
+<ul><li><link><page ri:content-title="Encrypted passwords"></page></link></li><li>Added selector support in <link><page ri:content-title="Ajax"></page></link></li></ul>
-<h2 id="NewFeaturesin5.4-NewFeaturesin5.4">New Features in 5.4</h2>
+<h2>New Features in 5.4</h2>
-<ul><li><a shape="rect" href="delay-and-schedule-message-delivery.xml">Delay and Schedule Message Delivery</a></li><li>Message Priority</li><li><a shape="rect" href="websockets.xml">WebSockets</a></li><li><a shape="rect" href="osgi-integration.xml">Better OSGi support</a></li><li>Broker side options for updating failover clients automatically of new brokers joining and leaving the cluster - see <a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></li><li><a shape="rect" href="unix-shell-script.xml">Enhanced Shell Script</a> - for starting, stopping and managing the broker in a Unix environment</li><li><a shape="rect" href="web-console.xml#WebConsole-SecuringWebConsole">Easy way to configure Web Console</a></li><li><a shape="rect" href="rest.xml#REST-Consumingwithselectors">Selectors for Ajax and REST consumers</a></li><li>JaasDualAuthentcationPlugin</li><li><a shape="rect" href="security.xml#Security-Anonymousaccess">Anonymous users</a></li><li>Ajax Adapters</li><li>... and much more</li></ul>
+<ul><li><link><page ri:content-title="Delay and Schedule Message Delivery"></page></link></li><li>Message Priority</li><li><link><page ri:content-title="WebSockets"></page></link></li><li><link><page ri:content-title="OSGi Integration"></page><link-body>Better OSGi support</link-body></link></li><li>Broker side options for updating failover clients automatically of new brokers joining and leaving the cluster - see <link><page ri:content-title="Failover Transport Reference"></page></link></li><li><link><page ri:content-title="Unix Shell Script"></page><link-body>Enhanced Shell Script</link-body></link> - for starting, stopping and managing the broker in a Unix environment</li><li><link ac:anchor="SecuringWebConsole"><page ri:content-title="Web console"></page><link-body>Easy way to configure Web Console</link-body></link></li><li><link ac:anchor="Consumingwithselectors"><page ri:content-title="REST"></page><link-body>Selectors for Ajax and REST consumers</link-body></link></li><li>JaasDualAuthentcationPlugin</li><li><link ac:anchor="Anonymousaccess"><page ri:content-title="Security"></page><link-body>Anonymous users</link-body></link></li><li>Ajax Adapters</li><li>... and much more</li></ul>
+
</div>
diff --git a/new-features-in-55.xml b/new-features-in-55.xml
index 95b923e..4e4f44d 100644
--- a/new-features-in-55.xml
+++ b/new-features-in-55.xml
@@ -1,9 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="NewFeaturesin5.5-NewFeaturesin5.5.0">New Features in 5.5.0</h2>
-<ul><li>Dependency on Java 1.6 (java 1.5 is no longer supported)</li><li>MDC logging (<a shape="rect" class="external-link" href="http://slf4j.org/" rel="nofollow">SLF4J</a>)</li><li>Upgrade to camel 2.7.0</li><li>DLQ processing per durable subscription</li><li>New network connector MBeans</li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/configurable-ioexception-handling.html">IOExceptionHandler</a> for JDBC store</li><li>Added support for <a shape="rect" class="external-link" href="http://commons.apache.org/daemon/">Apache Commons Daemon</a></li></ul>
+<div class="wiki-content maincontent"><h2>New Features in 5.5.0</h2>
+<ul><li>Dependency on Java 1.6 (java 1.5 is no longer supported)</li><li>MDC logging (<a shape="rect" href="http://slf4j.org/">SLF4J</a>)</li><li>Upgrade to camel 2.7.0</li><li>DLQ processing per durable subscription</li><li>New network connector MBeans</li><li><a shape="rect" href="http://activemq.apache.org/configurable-ioexception-handling.html">IOExceptionHandler</a> for JDBC store</li><li>Added support for <a shape="rect" href="http://commons.apache.org/daemon/">Apache Commons Daemon</a></li></ul>
-<h2 id="NewFeaturesin5.5-Improvementsin5.5.0">Improvements in 5.5.0</h2>
+<h2>Improvements in 5.5.0</h2>
<ul><li>Improved support for recovery of durable subscribers with priority support</li><li>Improved performance for offline durable subscriptions with large message backlogs (JDBC store)</li><li>better support for Guest login via JAAS</li></ul>
+
</div>
diff --git a/new-features-in-56.xml b/new-features-in-56.xml
index a675865..c20d98a 100644
--- a/new-features-in-56.xml
+++ b/new-features-in-56.xml
@@ -1,4 +1,5 @@
-<div class="wiki-content maincontent"><h2 id="NewFeaturesin5.6-NewFeaturesin5.6.0">New Features in 5.6.0</h2>
+<div class="wiki-content maincontent"><h2>New Features in 5.6.0</h2>
-<ul class="alternate"><li>LevelDB Store</li><li>MQTT transport</li><li>New LDAP security module</li><li>Stomp 1.1 support</li><li>stomp+nio+ssl transport</li><li>Multi KahaDB persistence</li><li>Priority Failover URIs</li><li>Automatic client rebalance in broker cluster</li></ul></div>
+<ul class="alternate"><li>LevelDB Store</li><li>MQTT transport</li><li>New LDAP security module</li><li>Stomp 1.1 support</li><li>stomp+nio+ssl transport</li><li>Multi KahaDB persistence</li><li>Priority Failover URIs</li><li>Automatic client rebalance in broker cluster</li></ul>
+</div>
diff --git a/new-features-in-57.xml b/new-features-in-57.xml
index 2956cfe..ada5e7c 100644
--- a/new-features-in-57.xml
+++ b/new-features-in-57.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><ul><li>Java 7 support (compiled with jdk6 and validated with jdk7)</li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/websockets.html#WebSockets-SecureWebSockets">Secure WebSockets (wss) transport </a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/message-redelivery-and-dlq-handling.html#MessageRedeliveryandDLQHandling-BrokerRedelivery%28v5.7%29">Broker Based Redelivery</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/pluggable-storage-lockers.html">Pluggable Store Lockers</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/pluggable-storage-lockers.html#Pluggablestoragelockers-LeaseDatabaseLocker">Lease based database locker</a></li><li>Set a <a shape="rect" class="external-link" href="http://activemq.apache.org/redelivery-policy.html#RedeliveryPolicy-RedeliveryPolicyperDestination">RedeliveryPolicy per destination</a></li><li>Includes <a shape="rect" class="external-link" href="http://camel.apache.org/camel-2100-release.html">Apache Camel 2.10</a></li></ul></div>
+<div class="wiki-content maincontent"><ul><li>Java 7 support (compiled with jdk6 and validated with jdk7)</li><li><a shape="rect" href="http://activemq.apache.org/websockets.html#WebSockets-SecureWebSockets">Secure WebSockets (wss) transport </a></li><li><a shape="rect" href="http://activemq.apache.org/message-redelivery-and-dlq-handling.html#MessageRedeliveryandDLQHandling-BrokerRedelivery%28v5.7%29">Broker Based Redelivery</a></li><li><a shape="rect" href="http://activemq.apache.org/pluggable-storage-lockers.html">Pluggable Store Lockers</a></li><li><a shape="rect" href="http://activemq.apache.org/pluggable-storage-lockers.html#Pluggablestoragelockers-LeaseDatabaseLocker">Lease based database locker</a></li><li>Set a <a shape="rect" href="http://activemq.apache.org/redelivery-policy.html#RedeliveryPolicy-RedeliveryPolicyperDestination">RedeliveryPolicy per destination</a></li><li>Includes <a shape="rect" href="http://camel.apache.org/camel-2100-release.html">Apache Camel 2.10</a></li></ul>
+</div>
diff --git a/new-features-in-58.xml b/new-features-in-58.xml
index def77ff..1d018c3 100644
--- a/new-features-in-58.xml
+++ b/new-features-in-58.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><ul><li><a shape="rect" href="amqp.xml">AMQP</a></li><li>new feature modules and activemq-client module allowing smaller foorprint</li><li>management via <a shape="rect" href="rest.xml#REST-REST-RestManagement">REST</a> with <a shape="rect" class="external-link" href="http://www.jolokia.org/" rel="nofollow">jolokia</a> jmx to http bridge</li><li>Includes <a shape="rect" class="external-link" href="http://camel.apache.org/camel-2103-release.html">Apache Camel 2.10.3</a></li><li>Java 7 support (compiled with jdk6 and validated with jdk7)</li><li><a shape="rect" href="pure-master-slave.xml">Pure Master Slave</a> no longer supported</li></ul></div>
+<div class="wiki-content maincontent"><ul><li><link><page ri:content-title="amqp"></page><link-body>AMQP</link-body></link></li><li>new feature modules and activemq-client module allowing smaller foorprint</li><li>management via <link ac:anchor="REST-RestManagement"><page ri:content-title="rest"></page><link-body>REST</link-body></link> with <a shape="rect" href="http://www.jolokia.org/">jolokia</a> jmx to http bridge</li><li>Includes <a shape="rect" href="http://camel.apache.org/camel-2103-release.html">Apache Camel 2.10.3</a></li><li>Java 7 support (compiled with jdk6 and validated with jdk7)</li><li><link><page ri:content-title="Pure Master Slave"></page></link> no longer supported</li></ul>
+</div>
diff --git a/new-features-in-59.xml b/new-features-in-59.xml
index 78ce285..7a2f162 100644
--- a/new-features-in-59.xml
+++ b/new-features-in-59.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul><li><a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a> for shared nothing Master/Slave.</li><li><a shape="rect" href="runtime-configuration.xml">Runtime Configuration</a></li><li>Generic JMS XA connection pool in activemq-jms-pool module (has no ActiveMQ dependency)</li><li>MQTT over WebSockets support</li><li><a shape="rect" href="broker-camel-component.xml"><strong>broker</strong></a> Apache Camel component</li><li>Broker auto-restart upon losing master status</li><li>AMQP Hardening</li><li>LevelDB Hardening</li></ul></div>
+<div class="wiki-content maincontent"><ul><li><link><page ri:content-title="Replicated LevelDB Store"></page></link> for shared nothing Master/Slave.</li><li><link><page ri:content-title="Runtime Configuration"></page></link></li><li>Generic JMS XA connection pool in activemq-jms-pool module (has no ActiveMQ dependency)</li><li>MQTT over WebSockets support</li><li><link><page ri:content-title="Broker Camel Component"></page><link-body><strong>broker</strong></link-body></link> Apache Camel component</li><li>Broker auto-restart upon losing master status</li><li>AMQP Hardening</li><li>LevelDB Hardening</li></ul></div>
diff --git a/new-features-in-60.xml b/new-features-in-60.xml
index 9da99b9..c47163b 100644
--- a/new-features-in-60.xml
+++ b/new-features-in-60.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>At one point, if you were interested in Version 6, you could take a look at <a shape="rect" class="external-link" href="http://activemq.apache.org/apollo/">Apollo subproject</a> as it was expected to be the core of the 6.0 broker.  However, as of July 2015, Apollo is being unofficially declared dead.  There is currently no official decision about the path forward for 6.0, though it's possible that the <a shape="rect" class="external-link" href="https://activemq.apache.org/artemis/">Artemis subproject</a> will instead become 6.0 at some point.</p></div>
+<div class="wiki-content maincontent"><p>At one point, if you were interested in Version 6, you could take a look at <a shape="rect" href="http://activemq.apache.org/apollo/">Apollo subproject</a> as it was expected to be the core of the 6.0 broker.  However, as of July 2015, Apollo is being unofficially declared dead.  There is currently no official decision about the path forward for 6.0, though it's possible that the <a shape="rect" href="https://activemq.apache.org/artemis/">Artemis subproject</a> will instead become 6.0 at some point.</p></div>
diff --git a/new-features.xml b/new-features.xml
index 70199e3..3dc33d9 100644
--- a/new-features.xml
+++ b/new-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="NewFeatures-NewFeatures">New Features</h2><p>This page documents the various new features we add in each major release</p><ul><li><a shape="rect" href="new-features-in-60.xml">New Features in 6.0</a></li><li><a shape="rect" href="new-features-in-513.xml">New Features in 5.13</a></li><li><a shape="rect" href="new-features-in-511.xml">New Features in 5.11</a></li><li><a shape="rect" href="new-features-in-56.xml">New Features in 5.6</a></li><li><a shape="rect" href="new-features-in-55.xml">New Features in 5.5</a></li><li><a shape="rect" href="new-features-in-54.xml">New Features in 5.4</a></li><li><a shape="rect" href="new-features-in-52.xml">New Features in 5.2</a></li><li><a shape="rect" href="new-features-in-51.xml">New Features in 5.1</a></li><li><a shape="rect" href="new-features-in-50.xml">New Features in 5.0</a></li><li><a shape="rect" href="new-features-in-41.xml">New Features in 4.1</a></li><li><a shape="rect" href="changes-in-40.xml">New Features in 4.0</a></li></ul></div>
+<div class="wiki-content maincontent"><h2>New Features</h2><p>This page documents the various new features we add in each major release</p><ul><li><link><page ri:content-title="New Features in 6.0"></page></link></li><li><link><page ri:content-title="New Features in 5.13"></page></link></li><li><link><page ri:content-title="New Features in 5.11"></page></link></li><li><link><page ri:content-title="New Features in 5.6"></page></link></li><li><link><page ri:content-title="New Features in 5.5"></page></link></li><li><link><page ri:content-title="New Features in 5.4"></page></link></li><li><link><page ri:content-title="New Features in 5.2"></page></link></li><li><link><page ri:content-title="New Features in 5.1"></page></link></li><li><link><page ri:content-title="New Features in 5.0"></page></link></li><li><link><page ri:content-title="New Features in 4.1"></page></link></li><li><link><page ri:content-title="Changes in 4.0"></page><plain-text-link-body>New Features in 4.0</plain-text-link-body></link></li></ul></div>
diff --git a/news.xml b/news.xml
index ce47164..155702a 100644
--- a/news.xml
+++ b/news.xml
@@ -1,204 +1,3 @@
-<div class="wiki-content maincontent">
-
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/10/23/apache-activemq-5152-released.xml">Apache ActiveMQ 5.15.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Oct 23, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5152-release.html">ActiveMQ 5.15.2</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/07/06/apache-activemq-5150-released.xml">Apache ActiveMQ 5.15.0 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Jul 06, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5150-release.html">ActiveMQ 5.15.0</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~dejanb">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: dejanb" title="dejanb">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/04/17/apache-activemq-5145-released.xml">Apache ActiveMQ 5.14.5 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~dejanb">Dejan Bosanac</a> posted on Apr 17, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <p>The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5145-release.html">ActiveMQ 5.14.5</a><br clear="none">A big thanks to everyone who contributed to this release.<br clear="none">We look forward to your feedback.</p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2017/03/03/apache-activemq-5144-released.xml">Apache ActiveMQ 5.14.4 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Mar 03, 2017</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5144-release.html">ActiveMQ 5.14.4</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/12/09/apache-activemq-5142-released.xml">Apache ActiveMQ 5.14.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Dec 09, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5142-release.html">ActiveMQ 5.14.2</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/10/03/apache-activemq-5141-released.xml">Apache ActiveMQ 5.14.1 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Oct 03, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5141-release.html">ActiveMQ 5.14.1</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/08/08/apache-activemq-5140-released.xml">Apache ActiveMQ 5.14.0 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Aug 08, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5140-release.html">ActiveMQ 5.14.0</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/07/21/apache-activemq-5134-released.xml">Apache ActiveMQ 5.13.4 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Jul 21, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of </span><a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5134-release.html">ActiveMQ 5.13.4</a></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/05/03/apache-activemq-5133-released.xml">Apache ActiveMQ 5.13.3 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on May 03, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5133-release.html">ActiveMQ 5.13.3</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~cshannon">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: cshannon" title="cshannon">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/03/07/apache-activemq-5132-released.xml">Apache ActiveMQ 5.13.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~cshannon">Christopher L. Shannon</a> posted on Mar 07, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <p><span style="color: rgb(34,34,34);">The ActiveMQ team is pleased to announce the release of <a shape="rect" class="external-link" href="http://activemq.apache.org/activemq-5132-release.html">ActiveMQ 5.13.2</a></span></p><p><span style="color: rgb(34,34,34);">A big thanks to everyone who contributed to this release.</span></p><p><span style="color: rgb(34,34,34);">We look forward to your feedback.</span></p>
- </div>
-
-
- </div>
- </div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="7699ca8b-9d4b-48bb-bdb4-f10a1ae25a0a" ac:name="blog-posts" ac:schema-version="1"><parameter ac:name="">10</parameter></structured-macro>
+</div>
diff --git a/nio-transport-reference.xml b/nio-transport-reference.xml
index 57846dd..deacb0c 100644
--- a/nio-transport-reference.xml
+++ b/nio-transport-reference.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><p>NIO Transport is very similar to the regular <a shape="rect" href="tcp-transport-reference.xml">TCP transport</a>. The difference is that it is implemented using NIO API which can help with performance and scalability. NIO is a server side transport option only. Trying to use it on the client side will instantiate the regular TCP transport.</p><h4 id="NIOTransportReference-ConfigurationSyntax">Configuration Syntax</h4><p><code><strong>nio://hostname:port?key=value</strong></code></p><p>Configuration options are the same as for the <a shape="rect" href="tcp-transport-reference.xml">TCP transport</a>.</p><p>Note that the original NIO transport is a replacement for the tcp transport that uses OpenWire protocol. Other network protocols, such AMQP, MQTT, Stomp, etc also have their own NIO transport implementations. It configured usually, by adding "+nio" suffix to the protocol prefix, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mqtt+nio://localhost:1883]]></script>
-</div></div><p>All protocol specific configuration should be applicable to the NIO version of the transport as well.</p><h3 id="NIOTransportReference-TuningNIOtransportthreadusage">Tuning NIO transport thread usage</h3><p>One of the main advantages of using NIO instead of the regular versions of the transport is that it can scale better and support larger number of connections. The main limit in this scenario is the number of threads the system in using. In blocking implementations of the transports, one thread is used per connection. In the NIO implementation, there's a shared pool of threads that will take the load, so that number of connections are not directly related to the number of threads used in the system.</p><p>You can tune the number of threads used by the transport using the following system properties (available since <strong>5.15.0</strong>)</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Property</th><th colspan="1" rowspan="1" class="confluenceTh">Default value</th><th colspan="1" rowspan="1" class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org.apache.activemq.transport.nio.SelectorManager.corePoolSize</td><td colspan="1" rowspan="1" class="confluenceTd">10</td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of threads to keep in the pool, even if they are idle</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org.apache.activemq.transport.nio.SelectorManager.maximumPoolSize</td><td colspan="1" rowspan="1" class="confluenceTd">1024</td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of threads to allow in the pool</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>org.apache.activemq.transport.nio.SelectorManager.workQueueCapacity</p></td><td colspan="1" rowspan="1" class="confluenceTd"> 0</td><td colspan="1" rowspan="1" class="confluenceTd"> The max work queue depth before growing the pool</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><span>org.apache.activemq.transport.nio.SelectorManager.rejectWork</span></td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">Allow work to be rejected with an IOException when capacity is reached such that existing QOS can be preserved</td></tr></tbody></table></div><p>If you want to scale your broker to support thousands of connections to it, you need to first find the limits of number of threads JVM process is allowed to create. Then you can set these properties to some value below that (broker need more threads to operate normally). For more information on thread usage by destinations and how to limit those, please take a look at <a shape="rect" href="scaling-queues.xml">Scaling Queues</a> or <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/sample-conf/activemq-scalability.xml">this configuration file</a>. For example you can add the following</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS -Dorg.apache.activemq.transport.nio.SelectorManager.corePoolSize=2000 -Dorg.apache.activemq.transport.nio.SelectorManager.maximumPoolSize=2000 -Dorg.apache.activemq.transport.nio.SelectorManager.workQueueCapacity=1024"]]></script>
-</div></div><p>to the startup script (<code>${ACTIVEMQ_HOME}/bin/env</code> for example) to have a constant pool of 2000 threads handling connections. With the setting like this, the broker should be able to accept the number of connections up to the system limits. Of course, accepting connections is just one part of the story, so there are other limits to vertically scaling the broker.</p><p> </p></div>
+<div class="wiki-content maincontent"><p>NIO Transport is very similar to the regular <link><page ri:content-title="TCP Transport Reference"></page><plain-text-link-body>TCP transport</plain-text-link-body></link>. The difference is that it is implemented using NIO API which can help with performance and scalability. NIO is a server side transport option only. Trying to use it on the client side will instantiate the regular TCP transport.</p><h4>Configuration Syntax</h4><p><code><strong>nio://hostname:port?key=value</strong></code></p><p>Configuration options are the same as for the <link><page ri:content-title="TCP Transport Reference"></page><plain-text-link-body>TCP transport</plain-text-link-body></link>.</p><p>Note that the original NIO transport is a replacement for the tcp transport that uses OpenWire protocol. Other network protocols, such AMQP, MQTT, Stomp, etc also have their own NIO transport implementations. It configured usually, by adding "+nio" suffix to the protocol prefix, like</p><structured-macro ac:macro-id="3509a8ac-d55b-40b8-81b3-cd22c109132a" ac:name="code" ac:schema-version="1"><plain-text-body>mqtt+nio://localhost:1883</plain-text-body></structured-macro><p>All protocol specific configuration should be applicable to the NIO version of the transport as well.</p><h3>Tuning NIO transport thread usage</h3><p>One of the main advantages of using NIO instead of the regular versions of the transport is that it can scale better and support larger number of connections. The main limit in this scenario is the number of threads the system in using. In blocking implementations of the transports, one thread is used per connection. In the NIO implementation, there's a shared pool of threads that will take the load, so that number of connections are not directly related to the number of threads used in the system.</p><p>You can tune the number of threads used by the transport using the following system properties (available since <strong>5.15.0</strong>)</p><table><tbody><tr><th colspan="1" rowspan="1">Property</th><th colspan="1" rowspan="1">Default value</th><th colspan="1" rowspan="1">Description</th></tr><tr><td colspan="1" rowspan="1">org.apache.activemq.transport.nio.SelectorManager.corePoolSize</td><td colspan="1" rowspan="1">10</td><td colspan="1" rowspan="1"><p>The number of threads to keep in the pool, even if they are idle</p></td></tr><tr><td colspan="1" rowspan="1">org.apache.activemq.transport.nio.SelectorManager.maximumPoolSize</td><td colspan="1" rowspan="1">1024</td><td colspan="1" rowspan="1"><p>The maximum number of threads to allow in the pool</p></td></tr><tr><td colspan="1" rowspan="1"><p>org.apache.activemq.transport.nio.SelectorManager.workQueueCapacity</p></td><td colspan="1" rowspan="1"> 0</td><td colspan="1" rowspan="1"> The max work queue depth before growing the pool</td></tr><tr><td colspan="1" rowspan="1"><span>org.apache.activemq.transport.nio.SelectorManager.rejectWork</span></td><td colspan="1" rowspan="1">false</td><td colspan="1" rowspan="1">Allow work to be rejected with an IOException when capacity is reached such that existing QOS can be preserved</td></tr></tbody></table><p>If you want to scale your broker to support thousands of connections to it, you need to first find the limits of number of threads JVM process is allowed to create. Then you can set these properties to some value below that (broker need more threads to operate normally). For more information on thread usage by destinations and how to limit those, please take a look at <link><page ri:content-title="Scaling Queues"></page></link> or <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/sample-conf/activemq-scalability.xml">this configuration file</a>. For example you can add the following</p><structured-macro ac:macro-id="90590c40-d24b-413e-bf65-bb4b0099cdeb" ac:name="code" ac:schema-version="1"><plain-text-body>ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS -Dorg.apache.activemq.transport.nio.SelectorManager.corePoolSize=2000 -Dorg.apache.activemq.transport.nio.SelectorManager.maximumPoolSize=2000 -Dorg.apache.activemq.transport.nio.SelectorManager.workQueueCapacity=1024"</plain-text-body></structured-macro><p>to the startup script (<code>${ACTIVEMQ_HOME}/bin/env</code> for example) to have a constant pool of 2000 threads handling connections. With the setting like this, the broker should be able to accept the number of connections up to the system limits. Of course, accepting connections is just one part of the story, so there are other limits to vertically scaling the broker.</p><p> </p></div>
diff --git a/nms/2011/11/18/apachenmsactivemq-v152-released.xml b/nms/2011/11/18/apachenmsactivemq-v152-released.xml
index 9cfaedd..d531f29 100644
--- a/nms/2011/11/18/apachenmsactivemq-v152-released.xml
+++ b/nms/2011/11/18/apachenmsactivemq-v152-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>A new release of Apache.NMS.ActiveMQ is out v1.5.2. This release has several important bug fixes in it, grab the binary distro <a shape="rect" href="../../../../nms/apachenmsactivemq-v152.xml">here</a>:</p></div>
+<div class="wiki-content maincontent"><p>A new release of Apache.NMS.ActiveMQ is out v1.5.2. This release has several important bug fixes in it, grab the binary distro <link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.2"></page><link-body>here</link-body></link>:</p></div>
diff --git a/nms/2012/01/28/apachenmsactivemq-v153-released.xml b/nms/2012/01/28/apachenmsactivemq-v153-released.xml
index 596596f..e3c2795 100644
--- a/nms/2012/01/28/apachenmsactivemq-v153-released.xml
+++ b/nms/2012/01/28/apachenmsactivemq-v153-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>A new release of Apache.NMS.ActiveMQ is out v1.5.3. This release has several important bug fixes in it, grab the binary distro on the <a shape="rect" href="../../../../nms/apachenmsactivemq-v153.xml">Apache.NMS.ActiveMQ Downloads page</a>:</p></div>
+<div class="wiki-content maincontent"><p>A new release of Apache.NMS.ActiveMQ is out v1.5.3. This release has several important bug fixes in it, grab the binary distro on the <link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.3"></page><link-body>Apache.NMS.ActiveMQ Downloads page</link-body></link>:</p></div>
diff --git a/nms/2012/04/13/apachenmsactivemq-v154-released.xml b/nms/2012/04/13/apachenmsactivemq-v154-released.xml
index 457611f..4dcfe50 100644
--- a/nms/2012/04/13/apachenmsactivemq-v154-released.xml
+++ b/nms/2012/04/13/apachenmsactivemq-v154-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>A new release of Apache.NMS.ActiveMQ is out v1.5.4. This release has several important bug fixes in it, grab the binary distro on the <a shape="rect" href="../../../../nms/activemq-downloads.xml">Apache.NMS.ActiveMQ Downloads</a> page:</p></div>
+<div class="wiki-content maincontent"><p>A new release of Apache.NMS.ActiveMQ is out v1.5.4. This release has several important bug fixes in it, grab the binary distro on the <link><page ri:content-title="ActiveMQ Downloads"></page><link-body>Apache.NMS.ActiveMQ Downloads</link-body></link> page:</p></div>
diff --git a/nms/2012/05/04/apachenmsactivemq-v155-released.xml b/nms/2012/05/04/apachenmsactivemq-v155-released.xml
index e894ebe..7c98b74 100644
--- a/nms/2012/05/04/apachenmsactivemq-v155-released.xml
+++ b/nms/2012/05/04/apachenmsactivemq-v155-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>A new release of Apache.NMS.ActiveMQ is out v1.5.5. This release has several important bug fixes in it, grab the binary distro on the <a shape="rect" href="../../../../nms/download.xml">Apache.NMS.ActiveMQ Downloads</a> page:</p></div>
+<div class="wiki-content maincontent"><p>A new release of Apache.NMS.ActiveMQ is out v1.5.5. This release has several important bug fixes in it, grab the binary distro on the <link><page ri:content-title="Download"></page><link-body>Apache.NMS.ActiveMQ Downloads</link-body></link> page:</p></div>
diff --git a/nms/2012/08/31/apachenmsstomp-v153-released.xml b/nms/2012/08/31/apachenmsstomp-v153-released.xml
index 602f8b8..58e023a 100644
--- a/nms/2012/08/31/apachenmsstomp-v153-released.xml
+++ b/nms/2012/08/31/apachenmsstomp-v153-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>A new release of Apache.NMS.Stomp is out v1.5.3. This release has several important bug fixes in it, grab the binary distro on the <a shape="rect" href="../../../../nms/stomp-downloads.xml">Apache.NMS.Stomp</a> Downloads page:</p></div>
+<div class="wiki-content maincontent"><p>A new release of Apache.NMS.Stomp is out v1.5.3. This release has several important bug fixes in it, grab the binary distro on the <link><page ri:content-title="Stomp Downloads"></page><link-body>Apache.NMS.Stomp</link-body></link> Downloads page:</p></div>
diff --git a/nms/2013/06/10/apachenmsactivemq-v160-released.xml b/nms/2013/06/10/apachenmsactivemq-v160-released.xml
index f6d15b0..18445da 100644
--- a/nms/2013/06/10/apachenmsactivemq-v160-released.xml
+++ b/nms/2013/06/10/apachenmsactivemq-v160-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>After almost a year we've <a shape="rect" class="external-link" href="http://activemq.apache.org/nms/apachenmsactivemq-v160.html">released v1.6.0</a> of Apache.NMS.ActiveMQ. This version offers many new features and fixes many issues that were found over the course of the last year. The release implement the Apache.NMS API v1.6.0</p></div>
+<div class="wiki-content maincontent"><p>After almost a year we've <a shape="rect" href="http://activemq.apache.org/nms/apachenmsactivemq-v160.html">released v1.6.0</a> of Apache.NMS.ActiveMQ. This version offers many new features and fixes many issues that were found over the course of the last year. The release implement the Apache.NMS API v1.6.0</p></div>
diff --git a/nms/2013/10/25/apachenmsactivemq-v161-released.xml b/nms/2013/10/25/apachenmsactivemq-v161-released.xml
index 65946ba..bb6c466 100644
--- a/nms/2013/10/25/apachenmsactivemq-v161-released.xml
+++ b/nms/2013/10/25/apachenmsactivemq-v161-released.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>A new bug fix release of the Apache.NMS.ActiveMQ library has been <a shape="rect" href="../../../../nms/activemq-downloads.xml">released</a>. In this version we improved the discovery transport quite a bit and added in HTTP based discovery support. </p></div>
+<div class="wiki-content maincontent"><p>A new bug fix release of the Apache.NMS.ActiveMQ library has been <link><page ri:content-title="ActiveMQ Downloads"></page><link-body>released</link-body></link>. In this version we improved the discovery transport quite a bit and added in HTTP based discovery support. </p></div>
diff --git a/nms/activemq-advanced-features.xml b/nms/activemq-advanced-features.xml
index d5fd0d7..40aeffd 100644
--- a/nms/activemq-advanced-features.xml
+++ b/nms/activemq-advanced-features.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>The NMS.ActiveMQ client provides several features in addition to fully implementing the NMS API. The features are documented here.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="activemq-consumer-features.xml">ActiveMQ Consumer Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-consumer-dispatch-async.xml">ActiveMQ Consumer Dispatch Async</a></li><li><a shape="rect" href="activemq-consumer-priority.xml">ActiveMQ Consumer Priority</a></li><li><a shape="rect" href="activemq-exclusive-consumers.xml">ActiveMQ Exclusive Consumers</a></li><li><a shape="rect" href="activemq-retroactive-consumers.xml">ActiveMQ Retroactive Consumers</a></li></ul></li><li><a shape="rect" href="activemq-destination-features.xml">ActiveMQ Destination Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-destination-management.xml">ActiveMQ Destination Management</a></li><li><a shape="rect" href="activemq-destination-options.xml">ActiveMQ Destination Options</a></li><li><a shape="rect" href="activemq-mirrored-queues.xml">ActiveMQ Mirrored Queues</a></li><li><a shape="rect" href="activemq-virtual-destinations.xml">ActiveMQ Virtual Destinations</a></li><li><a shape="rect" href="activemq-wildcards.xml">ActiveMQ Wildcards</a></li></ul></li><li><a shape="rect" href="activemq-message-dispatching-features.xml">ActiveMQ Message Dispatching Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-async-sends.xml">ActiveMQ Async Sends</a></li></ul></li><li><a shape="rect" href="activemq-message-features.xml">ActiveMQ Message Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-delay-and-schedule-message-feature.xml">ActiveMQ Delay and Schedule Message Feature</a></li></ul></li></ul> </div>
+<structured-macro ac:macro-id="59f3cd01-64b4-47a6-8c4f-2fda228c0f88" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro> </div>
diff --git a/nms/activemq-advisory-message-examples.xml b/nms/activemq-advisory-message-examples.xml
index 91e0d08..e95baea 100644
--- a/nms/activemq-advisory-message-examples.xml
+++ b/nms/activemq-advisory-message-examples.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="activemq-enumerate-destination-using-advisory-messages.xml">ActiveMQ Enumerate Destination using Advisory Messages</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="e5b77a32-d764-4850-86bf-17154e7f17ac" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/activemq-async-sends.xml b/nms/activemq-async-sends.xml
index 379c9b3..fa0927e 100644
--- a/nms/activemq-async-sends.xml
+++ b/nms/activemq-async-sends.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQAsyncSends-Background">Background</h2>
+<div class="wiki-content maincontent"><h2>Background</h2>
<p>Apache.NMS.ActiveMQ supports sending messages to a broker in sync or async mode. The mode used has a huge impact in the latency of the send call. Since latency is typically a huge factor in the throughput that can achieved by producer, using async sends can increase the performance of your system dramatically.</p>
@@ -9,39 +9,34 @@
<p>Many high performance applications are designed to be tolerate a small amount of message loss in failure scenarios. If your application has been designed in this fashion, you can enable the use of async sends to increase throughput even when using persistent messages. </p>
-<h3 id="ActiveMQAsyncSends-ConfiguringAsyncSendusingaConnectionURI">Configuring Async Send using a Connection URI</h3>
+<h3>Configuring Async Send using a Connection URI</h3>
-<p>You can use the <a shape="rect" href="activemq-uri-configuration.xml">Connection Configuration URI</a> to configure async sends as follows</p>
+<p>You can use the <link><page ri:content-title="ActiveMQ URI Configuration"></page><link-body>Connection Configuration URI</link-body></link> to configure async sends as follows</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-var cf = new ConnectionFactory("tcp://locahost:61616?nms.AsyncSend=true");
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="b3a0e289-625b-4aed-9ab3-cc5cdf99d18c" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
+var cf = new ConnectionFactory("tcp://locahost:61616?nms.AsyncSend=true");
+</plain-text-body></structured-macro>
-<h3 id="ActiveMQAsyncSends-ConfiguringAsyncSendattheConnectionFactoryLevel">Configuring Async Send at the ConnectionFactory Level</h3>
+<h3>Configuring Async Send at the ConnectionFactory Level</h3>
<p>You can enable this feature on the Apache.NMS.ActiveMQ.ConnectionFactory object using the property.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1741da20-a213-40d9-a7ef-8db5aecf9e62" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
((ConnectionFactory)connectionFactory).AsyncSend = true;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="ActiveMQAsyncSends-ConfiguringAsyncDispatchattheConnectionLevel">Configuring Async Dispatch at the Connection Level</h3>
+<h3>Configuring Async Dispatch at the Connection Level</h3>
<p>Configuring the async send setting at this level overrides the settings at the connection factory level.</p>
<p>You can enable this feature on the Apache.NMS.ActiveMQ.Connection object using the property.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="bc65a582-06f1-4c26-a8ea-a5c8cf5f75b1" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
((Apache.NMS.ActiveMQ.Connection)connection).AsyncSend = true;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="ActiveMQAsyncSends-Alsosee">Also see</h3>
+<h3>Also see</h3>
-<ul><li><a shape="rect" href="activemq-uri-configuration.xml">Connection Configuration URI</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/should-i-use-transactions.html">Should I use transactions</a></li><li><a shape="rect" href="activemq-consumer-dispatch-async.xml">Consumer Dispatch Async</a></li></ul></div>
+<ul><li><link><page ri:content-title="ActiveMQ URI Configuration"></page><link-body>Connection Configuration URI</link-body></link></li><li><a shape="rect" href="http://activemq.apache.org/should-i-use-transactions.html">Should I use transactions</a></li><li><link><page ri:content-title="ActiveMQ Consumer Dispatch Async"></page><link-body>Consumer Dispatch Async</link-body></link></li></ul>
+</div>
diff --git a/nms/activemq-consumer-dispatch-async.xml b/nms/activemq-consumer-dispatch-async.xml
index a03130d..134bcf6 100644
--- a/nms/activemq-consumer-dispatch-async.xml
+++ b/nms/activemq-consumer-dispatch-async.xml
@@ -1,37 +1,31 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQConsumerDispatchAsync-Overview">Overview</h2>
+<div class="wiki-content maincontent"><h2>Overview</h2>
-<p>In AMQ4 onwards, the choice of a broker performing synchronous or asynchronous dispatch to a consumer has become more configurable. It is now configured as a default value on the <a shape="rect" href="activemq-uri-configuration.xml">connection URI, Connection and ConnectionFactory</a> together with being customizable on a per consumer basis via the <a shape="rect" href="activemq-uri-configuration.xml">Destination Options</a> instead previously just being a transport server setting. </p>
+<p>In AMQ4 onwards, the choice of a broker performing synchronous or asynchronous dispatch to a consumer has become more configurable. It is now configured as a default value on the <link><page ri:content-title="ActiveMQ URI Configuration"></page><link-body>connection URI, Connection and ConnectionFactory</link-body></link> together with being customizable on a per consumer basis via the <link><page ri:content-title="ActiveMQ URI Configuration"></page><link-body>Destination Options</link-body></link> instead previously just being a transport server setting. </p>
<p>This makes more sense since you want to do async message delivery to slower consumers, but do sync message delivery to faster consumers (to avoid the synchronization and context switching costs of adding another seda queue). The downside to using sync message delivery is that the producer is more likely to block if there is a slow consumer that he is dispatching messages to.</p>
<p>The default setting is dispatchAsync=true which is the best setting for high performance. If you want to deal better with slow consumers you will want to enable this setting. If you want better thoughput and the chances of having a slow consumer are low, you may want to change this to false.</p>
-<h3 id="ActiveMQConsumerDispatchAsync-ConfiguringAsyncDispatchattheConnectionFactoryLevel">Configuring Async Dispatch at the ConnectionFactory Level</h3>
+<h3>Configuring Async Dispatch at the ConnectionFactory Level</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4d4bcd44-e58f-45c5-94f0-545947128914" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
connectionFactory.DispatchAsync = false;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="ActiveMQConsumerDispatchAsync-ConfiguringDispatchAsyncattheConnectionLevel">Configuring Dispatch Async at the Connection Level</h3>
+<h3>Configuring Dispatch Async at the Connection Level</h3>
<p>Configuring the dispatchAsync setting at this level overrides the settings at the connection factory level.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="f1692ce2-9d67-467e-8c7a-5d8a6372a67d" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
connection.DispatchAsync = false;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="ActiveMQConsumerDispatchAsync-ConfiguringDispatchAsyncattheConsumerLevelusingtheDestinationURI">Configuring Dispatch Async at the Consumer Level using the Destination URI</h3>
+<h3>Configuring Dispatch Async at the Consumer Level using the Destination URI</h3>
-<p>Configuring the dispatchAsync using <a shape="rect" href="activemq-uri-configuration.xml">Destination Options</a> overrides the settings at the connection and connection factory level.</p>
+<p>Configuring the dispatchAsync using <link><page ri:content-title="ActiveMQ URI Configuration"></page><link-body>Destination Options</link-body></link> overrides the settings at the connection and connection factory level.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-var queue = new ActiveMQQueue("TEST.QUEUE?consumer.dispatchAsync=false");
+<structured-macro ac:macro-id="02520a75-e25c-4984-9cf3-5e6c2a4278a9" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
+var queue = new ActiveMQQueue("TEST.QUEUE?consumer.dispatchAsync=false");
var consumer = session.CreateConsumer(queue);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/nms/activemq-consumer-priority.xml b/nms/activemq-consumer-priority.xml
index 8b28739..9df5e6d 100644
--- a/nms/activemq-consumer-priority.xml
+++ b/nms/activemq-consumer-priority.xml
@@ -1,19 +1,17 @@
-<div class="wiki-content maincontent"><h3 id="ActiveMQConsumerPriority-Background">Background</h3>
+<div class="wiki-content maincontent"><h3>Background</h3>
<p>As well as having a pluggable dispatch policy (e.g. round robin etc), we now support consumer priorities.</p>
<p>This allows us to weight consumers to optimise network hops. For example, you typically want a broker to send messages to regular NMS consumers rather than to other brokers; there's no need to make unnecessary broker-to-broker hops if there are available consumers.</p>
-<h3 id="ActiveMQConsumerPriority-Example">Example</h3>
+<h3>Example</h3>
-<p>The priority for a consumer is set using <a shape="rect" href="activemq-uri-configuration.xml">Destination Options</a> as follows:</p>
+<p>The priority for a consumer is set using <link><page ri:content-title="ActiveMQ URI Configuration"></page><link-body>Destination Options</link-body></link> as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-var queue = session.GetQueue("TEST.QUEUE?consumer.priority=10");
+<structured-macro ac:macro-id="91f62f32-07fc-46ae-b30f-86646d2f98e6" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
+var queue = session.GetQueue("TEST.QUEUE?consumer.priority=10");
var consumer = session.CreateConsumer(queue);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The range for assigning priority numbers is from 0 to 127, with 127 being the highest priority and 0 being the default priority.<br clear="none">
The way it works is that the broker will simply order any queue consumers according to their priorities and send messages to the highest priority consumers first. <br clear="none">
diff --git a/nms/activemq-delay-and-schedule-message-feature.xml b/nms/activemq-delay-and-schedule-message-feature.xml
index 98b3b20..fe145d8 100644
--- a/nms/activemq-delay-and-schedule-message-feature.xml
+++ b/nms/activemq-delay-and-schedule-message-feature.xml
@@ -1,60 +1,52 @@
-<div class="wiki-content maincontent"><p>ActiveMQ from version <strong>5.4</strong> has an optional persistent scheduler built into the ActiveMQ message broker. It is enabled by setting the broker <strong>schedulerSupport</strong> attribute to true in the <a shape="rect" class="unresolved" href="#">xml configuration</a>. <br clear="none">
+<div class="wiki-content maincontent"><p>ActiveMQ from version <strong>5.4</strong> has an optional persistent scheduler built into the ActiveMQ message broker. It is enabled by setting the broker <strong>schedulerSupport</strong> attribute to true in the <link><page ri:content-title="xml configuration"></page></link>. <br clear="none">
An ActiveMQ client can take advantage of a delayed delivery by using the following message properties:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_DELAY</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> long </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The time in milliseconds that a message will wait before being scheduled to be delivered by the broker</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_PERIOD </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>long </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The time in milliseconds to wait after the start time to wait before scheduling the message again</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_REPEAT </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>int </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The number of times to repeat scheduling a message for delivery</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_CRON </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use a Cron entry to set the schedule</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Property name</p></th><th colspan="1" rowspan="1"><p>type </p></th><th colspan="1" rowspan="1"><p> description </p></th></tr><tr><td colspan="1" rowspan="1"><p>AMQ_SCHEDULED_DELAY</p></td><td colspan="1" rowspan="1"><p> long </p></td><td colspan="1" rowspan="1"><p> The time in milliseconds that a message will wait before being scheduled to be delivered by the broker</p></td></tr><tr><td colspan="1" rowspan="1"><p>AMQ_SCHEDULED_PERIOD </p></td><td colspan="1" rowspan="1"><p>long </p></td><td colspan="1" rowspan="1"><p> The time in milliseconds to wait after the start time to wait before scheduling the message again</p></td></tr><tr><td colspan="1" rowspan="1"><p>AMQ_SCHEDULED_REPEAT </p></td><td colspan="1" rowspan="1"><p>int </p></td><td colspan="1" rowspan="1"><p> The number of times to repeat scheduling a message for delivery</p></td></tr><tr><td colspan="1" rowspan="1"><p>AMQ_SCHEDULED_CRON </p></td><td colspan="1" rowspan="1"><p>String </p></td><td colspan="1" rowspan="1"><p> Use a Cron entry to set the schedule</p></td></tr></tbody></table>
<p>For example, to have a message scheduled for delivery in 60 seconds - you would need to set the <em>AMQ_SCHEDULED_DELAY</em> property:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="23d3c5d1-1f3d-476b-ade8-6c477b6647a8" ac:name="code" ac:schema-version="1"><plain-text-body>
IMessageProducer producer = session.CreateProducer(destination);
- ITextMessage message = session.CreateTextMessage("test msg");
+ ITextMessage message = session.CreateTextMessage("test msg");
long time = 60 * 1000;
- message.Properties["AMQ_SCHEDULED_DELAY"] = time;
+ message.Properties["AMQ_SCHEDULED_DELAY"] = time;
producer.Send(message);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>You can set a message to wait with an initial delay, and the repeat delivery 10 times, waiting 10 seconds between each re-delivery:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2a059a1e-bbf7-46b3-9429-eabbda397b89" ac:name="code" ac:schema-version="1"><plain-text-body>
IMessageProducer producer = session.CreateProducer(destination);
- ITextMessage message = session.CreateTextMessage("test msg");
+ ITextMessage message = session.CreateTextMessage("test msg");
long delay = 30 * 1000;
long period = 10 * 1000;
int repeat = 9;
- message.Properties["AMQ_SCHEDULED_DELAY"] = delay;
- message.Properties["AMQ_SCHEDULED_PERIOD"] = period;
- message.Properties["AMQ_SCHEDULED_REPEAT"] = repeat;
+ message.Properties["AMQ_SCHEDULED_DELAY"] = delay;
+ message.Properties["AMQ_SCHEDULED_PERIOD"] = period;
+ message.Properties["AMQ_SCHEDULED_REPEAT"] = repeat;
producer.Send(message);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>You can also use <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Cron" rel="nofollow">CRON</a> to schedule a message, for example, if you want a message scheduled to be delivered every hour, you would need to set the CRON entry to be - <em>0 * * * *</em> - e.g.</p>
+<p>You can also use <a shape="rect" href="http://en.wikipedia.org/wiki/Cron">CRON</a> to schedule a message, for example, if you want a message scheduled to be delivered every hour, you would need to set the CRON entry to be - <em>0 * * * *</em> - e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ab4ffcde-e93e-4041-9440-5375bd6361a7" ac:name="code" ac:schema-version="1"><plain-text-body>
IMessageProducer producer = session.CreateProducer(destination);
- ITextMessage message = session.CreateTextMessage("test msg");
- message.Properties["AMQ_SCHEDULED_CRON"] = "0 * * * *";
+ ITextMessage message = session.CreateTextMessage("test msg");
+ message.Properties["AMQ_SCHEDULED_CRON"] = "0 * * * *";
producer.Send(message);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>CRON scheduling takes priority over using message delay - however, if a repeat and period is set with a CRON entry, the ActiveMQ scheduler will schedule delivery of the message for every time the CRON entry fires. Easier to explain with an example. Supposing that you want a message to be delivered 10 times, with a one second delay between each message - and you wanted this to happen every hour - you'd do this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a071b052-b175-4e4e-a6eb-1055fb8cf033" ac:name="code" ac:schema-version="1"><plain-text-body>
IMessageProducer producer = session.CreateProducer(destination);
- ITextMessage message = session.CreateTextMessage("test msg");
- message.Properties["AMQ_SCHEDULED_CRON"] = "0 * * * *";
- message.Properties["AMQ_SCHEDULED_DELAY"] = 1000;
- message.Properties["AMQ_SCHEDULED_PERIOD"] = 1000;
- message.Properties["AMQ_SCHEDULED_REPEAT"] = 9;
+ ITextMessage message = session.CreateTextMessage("test msg");
+ message.Properties["AMQ_SCHEDULED_CRON"] = "0 * * * *";
+ message.Properties["AMQ_SCHEDULED_DELAY"] = 1000;
+ message.Properties["AMQ_SCHEDULED_PERIOD"] = 1000;
+ message.Properties["AMQ_SCHEDULED_REPEAT"] = 9;
producer.Send(message);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/nms/activemq-destination-features.xml b/nms/activemq-destination-features.xml
index ae890f1..947d7eb 100644
--- a/nms/activemq-destination-features.xml
+++ b/nms/activemq-destination-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="activemq-destination-management.xml">ActiveMQ Destination Management</a></li><li><a shape="rect" href="activemq-destination-options.xml">ActiveMQ Destination Options</a></li><li><a shape="rect" href="activemq-mirrored-queues.xml">ActiveMQ Mirrored Queues</a></li><li><a shape="rect" href="activemq-virtual-destinations.xml">ActiveMQ Virtual Destinations</a></li><li><a shape="rect" href="activemq-wildcards.xml">ActiveMQ Wildcards</a></li></ul></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="4a4597fb-3a50-4e5e-8cba-ce0cfc94ef6c" ac:name="children" ac:schema-version="1"></structured-macro></p></div>
diff --git a/nms/activemq-destination-management.xml b/nms/activemq-destination-management.xml
index 69e72f1..67c8eb2 100644
--- a/nms/activemq-destination-management.xml
+++ b/nms/activemq-destination-management.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><p>The Apache.NMS.ActiveMQ client provides some additional features beyond the standard NMS API.  One such feature is the ability to delete a given destination on the Broker.  This can be useful during testing when you want to start the test with a destination in a known state, empty or otherwise.  You can delete the destination and then the next send to that destination would recreate it at the Broker side.  Deleting a destination is as simple as the following:</p><p> </p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Delete a destination</b></div><div class="codeContent panelContent pdl">
-<script class="brush: c#; gutter: true; theme: Eclipse" type="syntaxhighlighter"><![CDATA[protected static void DeleteDestination()
+<div class="wiki-content maincontent"><p>The Apache.NMS.ActiveMQ client provides some additional features beyond the standard NMS API.  One such feature is the ability to delete a given destination on the Broker.  This can be useful during testing when you want to start the test with a destination in a known state, empty or otherwise.  You can delete the destination and then the next send to that destination would recreate it at the Broker side.  Deleting a destination is as simple as the following:</p><p> </p><structured-macro ac:macro-id="1d7e38db-152c-47ca-8a28-d6a97a0ce97c" ac:name="code" ac:schema-version="1"><parameter ac:name="theme">Eclipse</parameter><parameter ac:name="language">c#</parameter><parameter ac:name="title">Delete a destination</parameter><parameter ac:name="linenumbers">true</parameter><plain-text-body>protected static void DeleteDestination()
{
IConnectionFactory factory = new ConnectionFactory(ReplaceEnvVar(connectionURI));
using (Connection connection = factory.CreateConnection() as Connection)
@@ -16,6 +15,5 @@
}
}
}
-} ]]></script>
-</div></div><p> </p><p> </p></div>
+} </plain-text-body></structured-macro><p> </p><p> </p></div>
diff --git a/nms/activemq-destination-options.xml b/nms/activemq-destination-options.xml
index 5e3fedb..2186bdb 100644
--- a/nms/activemq-destination-options.xml
+++ b/nms/activemq-destination-options.xml
@@ -1,6 +1,4 @@
-<div class="wiki-content maincontent"><h3 id="ActiveMQDestinationOptions-Background">Background</h3><p>Destination Options are a way to provide extended configuration options to a NMS consumer without having to extend the NMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on.</p><h3 id="ActiveMQDestinationOptions-ConsumerOptions">Consumer Options</h3><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>consumer.prefetchSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>variable</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of message the consumer will <a shape="rect" class="unresolved" href="#">prefetch</a>.  <strong>Removed in NMS.ActiveMQ v1.7.0 use the PrefetchPolicy isntead.</strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.maximumPendingMessageLimit</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use to control if messages for non-durable topics are dropped if a <a shape="rect" class="unresolved" href="#">slow consumer</a> situation exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.noLocal</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.dispatchAsync</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker <a shape="rect" class="unresolved" href="#">dispatch messages asynchronously</a> to the consumer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Is this a <a shape="rect" class="unresolved" href="#">Retroactive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.selector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>NMS Selector used with the consumer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.exclusive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Is this an <a shape="rect" class="unresolved" href="#">Exclusive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.priority</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows you to configure a <a shape="rect" class="unresolved" href="#">Consumer Priority</a>.</p></td></tr></tbody></table></div><h3 id="ActiveMQDestinationOptions-Example">Example</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[var queue = session.GetQueue("TEST.QUEUE?consumer.dispatchAsync=false&consumer.prefetchSize=10");
+<div class="wiki-content maincontent"><h3>Background</h3><p>Destination Options are a way to provide extended configuration options to a NMS consumer without having to extend the NMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on.</p><h3>Consumer Options</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>consumer.prefetchSize</p></td><td colspan="1" rowspan="1"><p>variable</p></td><td colspan="1" rowspan="1"><p>The number of message the consumer will <link><page ri:content-title="What is the prefetch limit for"></page><plain-text-link-body>prefetch</plain-text-link-body></link>.  <strong>Removed in NMS.ActiveMQ v1.7.0 use the PrefetchPolicy isntead.</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.maximumPendingMessageLimit</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Use to control if messages for non-durable topics are dropped if a <link><page ri:content-title="Slow Consumer Handling"></page><plain-text-link-body>slow consumer</plain-text-link-body></link> situation exists.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.noLocal</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.dispatchAsync</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should the broker <link><page ri:content-title="Consumer Dispatch Async"></page><plain-text-link-body>dispatch messages asynchronously</plain-text-link-body></link> to the consumer.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Is this a <link><page ri:content-title="Retroactive Consumer"></page><plain-text-link-body>Retroactive Consumer</plain-text-link-body></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.selector</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>NMS Selector used with the consumer.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.exclusive</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Is this an <link><page ri:content-title="Exclusive Consumer"></page><plain-text-link-body>Exclusive Consumer</plain-text-link-body></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.priority</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Allows you to configure a <link><page ri:content-title="Consumer Priority"></page><plain-text-link-body>Consumer Priority</plain-text-link-body></link>.</p></td></tr></tbody></table><h3>Example</h3><structured-macro ac:macro-id="d40cc8cd-2b72-4323-85a1-aabddd8c3228" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>var queue = session.GetQueue("TEST.QUEUE?consumer.dispatchAsync=false&consumer.prefetchSize=10");
var consumer = session.CreateConsumer(queue);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/nms/activemq-downloads.xml b/nms/activemq-downloads.xml
index 633dd2d..990b116 100644
--- a/nms/activemq-downloads.xml
+++ b/nms/activemq-downloads.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Release Date</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>NMS API Rev</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v172.xml">Apache.NMS.ActiveMQ v1.7.2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>04/07/2016</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.7.1</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v171.xml">Apache.NMS.ActiveMQ v1.7.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10/05/2015</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.7.1</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v170.xml">Apache.NMS.ActiveMQ v1.7.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/16/2015</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.7.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v165.xml">Apache.NMS.ActiveMQ v1.6.5</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>02/05/2015</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v164.xml">Apache.NMS.ActiveMQ v1.6.4</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>09/14/2014</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v163.xml">Apache.NMS.ActiveMQ v1.6.3</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/21/2014</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v162.xml">Apache.NMS.ActiveMQ v1.6.2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>12/23/2013</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v161.xml">Apache.NMS.ActiveMQ v1.6.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10/19/2013</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v160.xml">Apache.NMS.ActiveMQ v1.6.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>06/06/2013</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v156.xml">Apache.NMS.ActiveMQ v1.5.6</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/12/2012</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.1</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v155.xml">Apache.NMS.ActiveMQ v1.5.5</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>05/03/2012</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v154.xml">Apache.NMS.ActiveMQ v1.5.4</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>04/13/2012</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v153.xml">Apache.NMS.ActiveMQ v1.5.3</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/27/2012</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v152.xml">Apache.NMS.ActiveMQ v1.5.2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>11/18/2011</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v151.xml">Apache.NMS.ActiveMQ v1.5.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>06/04/2011</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v150.xml">Apache.NMS.ActiveMQ v1.5.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>02/17/2011</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v141.xml">Apache.NMS.ActiveMQ v1.4.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10/04/2010</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.4.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v140.xml">Apache.NMS.ActiveMQ v1.4.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>09/17/2010</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.4.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v130.xml">Apache.NMS.ActiveMQ v1.3.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>05/21/2010</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.3.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v120.xml">Apache.NMS.ActiveMQ v1.2.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>02/12/2010</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.2.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-activemq-v110.xml">Apache.NMS ActiveMQ v1.1.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/12/2009</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.1.0</p></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Release Date</p></th><th colspan="1" rowspan="1"><p>NMS API Rev</p></th></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.7.2"></page></link></p></td><td colspan="1" rowspan="1"><p>04/07/2016</p></td><td colspan="1" rowspan="1"><p>v1.7.1</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.7.1"></page></link></p></td><td colspan="1" rowspan="1"><p>10/05/2015</p></td><td colspan="1" rowspan="1"><p>v1.7.1</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.7.0"></page></link></p></td><td colspan="1" rowspan="1"><p>01/16/2015</p></td><td colspan="1" rowspan="1"><p>v1.7.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.6.5"></page></link></p></td><td colspan="1" rowspan="1"><p>02/05/2015</p></td><td colspan="1" rowspan="1"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.6.4"></page></link></p></td><td colspan="1" rowspan="1"><p>09/14/2014</p></td><td colspan="1" rowspan="1"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.6.3"></page></link></p></td><td colspan="1" rowspan="1"><p>07/21/2014</p></td><td colspan="1" rowspan="1"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.6.2"></page></link></p></td><td colspan="1" rowspan="1"><p>12/23/2013</p></td><td colspan="1" rowspan="1"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.6.1"></page></link></p></td><td colspan="1" rowspan="1"><p>10/19/2013</p></td><td colspan="1" rowspan="1"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.6.0"></page></link></p></td><td colspan="1" rowspan="1"><p>06/06/2013</p></td><td colspan="1" rowspan="1"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.6"></page></link></p></td><td colspan="1" rowspan="1"><p>07/12/2012</p></td><td colspan="1" rowspan="1"><p>v1.5.1</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.5"></page></link></p></td><td colspan="1" rowspan="1"><p>05/03/2012</p></td><td colspan="1" rowspan="1"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.4"></page></link></p></td><td colspan="1" rowspan="1"><p>04/13/2012</p></td><td colspan="1" rowspan="1"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.3"></page></link></p></td><td colspan="1" rowspan="1"><p>01/27/2012</p></td><td colspan="1" rowspan="1"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.2"></page></link></p></td><td colspan="1" rowspan="1"><p>11/18/2011</p></td><td colspan="1" rowspan="1"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.1"></page></link></p></td><td colspan="1" rowspan="1"><p>06/04/2011</p></td><td colspan="1" rowspan="1"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.5.0"></page></link></p></td><td colspan="1" rowspan="1"><p>02/17/2011</p></td><td colspan="1" rowspan="1"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.4.1"></page></link></p></td><td colspan="1" rowspan="1"><p>10/04/2010</p></td><td colspan="1" rowspan="1"><p>v1.4.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.4.0"></page></link></p></td><td colspan="1" rowspan="1"><p>09/17/2010</p></td><td colspan="1" rowspan="1"><p>v1.4.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.3.0"></page></link></p></td><td colspan="1" rowspan="1"><p>05/21/2010</p></td><td colspan="1" rowspan="1"><p>v1.3.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS.ActiveMQ v1.2.0"></page></link></p></td><td colspan="1" rowspan="1"><p>02/12/2010</p></td><td colspan="1" rowspan="1"><p>v1.2.0</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS ActiveMQ v1.1.0"></page></link></p></td><td colspan="1" rowspan="1"><p>07/12/2009</p></td><td colspan="1" rowspan="1"><p>v1.1.0</p></td></tr></tbody></table></div>
diff --git a/nms/activemq-enumerate-destination-using-advisory-messages.xml b/nms/activemq-enumerate-destination-using-advisory-messages.xml
index 13ef441..e7e4130 100644
--- a/nms/activemq-enumerate-destination-using-advisory-messages.xml
+++ b/nms/activemq-enumerate-destination-using-advisory-messages.xml
@@ -1,21 +1,20 @@
-<div class="wiki-content maincontent"><h3 id="ActiveMQEnumerateDestinationusingAdvisoryMessages-EnumeratingAvailableDestinationsusingAdvisoryMessages">Enumerating Available Destinations using Advisory Messages</h3>
+<div class="wiki-content maincontent"><h3>Enumerating Available Destinations using Advisory Messages</h3>
<p>This example shows you how to consume Advisory Messages from the Broker to enumerate various destination types.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="21364869-22f0-4f1a-81c3-a4567a1cb475" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
+ * (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
+ * distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
@@ -34,14 +33,14 @@
private IConnection connection;
private ISession session;
- public const String QUEUE_ADVISORY_DESTINATION = "ActiveMQ.Advisory.Queue";
- public const String TOPIC_ADVISORY_DESTINATION = "ActiveMQ.Advisory.Topic";
- public const String TEMPQUEUE_ADVISORY_DESTINATION = "ActiveMQ.Advisory.TempQueue";
- public const String TEMPTOPIC_ADVISORY_DESTINATION = "ActiveMQ.Advisory.TempTopic";
+ public const String QUEUE_ADVISORY_DESTINATION = "ActiveMQ.Advisory.Queue";
+ public const String TOPIC_ADVISORY_DESTINATION = "ActiveMQ.Advisory.Topic";
+ public const String TEMPQUEUE_ADVISORY_DESTINATION = "ActiveMQ.Advisory.TempQueue";
+ public const String TEMPTOPIC_ADVISORY_DESTINATION = "ActiveMQ.Advisory.TempTopic";
- public const String ALLDEST_ADVISORY_DESTINATION = QUEUE_ADVISORY_DESTINATION + "," +
- TOPIC_ADVISORY_DESTINATION + "," +
- TEMPQUEUE_ADVISORY_DESTINATION + "," +
+ public const String ALLDEST_ADVISORY_DESTINATION = QUEUE_ADVISORY_DESTINATION + "," +
+ TOPIC_ADVISORY_DESTINATION + "," +
+ TEMPQUEUE_ADVISORY_DESTINATION + "," +
TEMPTOPIC_ADVISORY_DESTINATION;
AdvisoryExample()
@@ -55,7 +54,7 @@
void EnumerateQueues()
{
- Console.WriteLine("Listing all Queues on Broker:");
+ Console.WriteLine("Listing all Queues on Broker:");
IDestination dest = session.GetTopic(QUEUE_ADVISORY_DESTINATION);
@@ -72,17 +71,17 @@
DestinationInfo info = amqMsg.DataStructure as DestinationInfo;
if(info != null)
{
- Console.WriteLine(" Queue: " + info.Destination.ToString() );
+ Console.WriteLine(" Queue: " + info.Destination.ToString() );
}
}
}
}
- Console.WriteLine("Listing Complete.");
+ Console.WriteLine("Listing Complete.");
}
void EnumerateTopics()
{
- Console.WriteLine("Listing all Topics on Broker:");
+ Console.WriteLine("Listing all Topics on Broker:");
IDestination dest = session.GetTopic(TOPIC_ADVISORY_DESTINATION);
@@ -99,17 +98,17 @@
DestinationInfo info = amqMsg.DataStructure as DestinationInfo;
if(info != null)
{
- Console.WriteLine(" Topic: " + info.Destination.ToString() );
+ Console.WriteLine(" Topic: " + info.Destination.ToString() );
}
}
}
}
- Console.WriteLine("Listing Complete.");
+ Console.WriteLine("Listing Complete.");
}
void EnumerateDestinations()
{
- Console.WriteLine("Listing all Destinations on Broker:");
+ Console.WriteLine("Listing all Destinations on Broker:");
IDestination dest = session.GetTopic(ALLDEST_ADVISORY_DESTINATION);
@@ -126,14 +125,14 @@
DestinationInfo info = amqMsg.DataStructure as DestinationInfo;
if(info != null)
{
- string destType = info.Destination.IsTopic ? "Topic" : "Qeue";
- destType = info.Destination.IsTemporary ? "Temporary" + destType : destType;
- Console.WriteLine(" " + destType + ": " + info.Destination.ToString() );
+ string destType = info.Destination.IsTopic ? "Topic" : "Qeue";
+ destType = info.Destination.IsTemporary ? "Temporary" + destType : destType;
+ Console.WriteLine(" " + destType + ": " + info.Destination.ToString() );
}
}
}
}
- Console.WriteLine("Listing Complete.");
+ Console.WriteLine("Listing Complete.");
}
void ShutDown()
@@ -154,6 +153,5 @@
}
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/nms/activemq-examples.xml b/nms/activemq-examples.xml
index cca371a..cf5cfce 100644
--- a/nms/activemq-examples.xml
+++ b/nms/activemq-examples.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="activemq-advisory-message-examples.xml">ActiveMQ Advisory Message Examples</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-enumerate-destination-using-advisory-messages.xml">ActiveMQ Enumerate Destination using Advisory Messages</a></li></ul></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="6703d9a9-438e-4ed2-a234-4b36c5b36fc5" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro></div>
diff --git a/nms/activemq-exclusive-consumers.xml b/nms/activemq-exclusive-consumers.xml
index 67daa53..b83fcc0 100644
--- a/nms/activemq-exclusive-consumers.xml
+++ b/nms/activemq-exclusive-consumers.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h3 id="ActiveMQExclusiveConsumers-ExclusiveConsumer">Exclusive Consumer</h3>
+<div class="wiki-content maincontent"><h3>Exclusive Consumer</h3>
<p>We have a new feature in version 4.x and above called Exclusive Consumer or Exclusive Queues which avoids the end user having to <em>pin</em> anything. The broker will pick a single MessageConsumer to get all the messages for a queue to ensure ordering. If that consumer fails, the broker will auto failover and choose another consumer.</p>
@@ -6,14 +6,12 @@
<p>For those who've struggled with pinning NMS consumers in clusters you'll immediately realize how useful this is to making clustered, high available distributed services.</p>
-<h3 id="ActiveMQExclusiveConsumers-Example">Example</h3>
+<h3>Example</h3>
-<p>An Exclusive Consumer is created using <a shape="rect" href="activemq-uri-configuration.xml">ActiveMQ URI Configuration</a> as follows:</p>
+<p>An Exclusive Consumer is created using <link><page ri:content-title="ActiveMQ URI Configuration"></page></link> as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-var queue = session.GetQueue("TEST.QUEUE?consumer.exclusive=true");
+<structured-macro ac:macro-id="6d35e79c-c27e-418a-b6ef-c047f55c2af0" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
+var queue = session.GetQueue("TEST.QUEUE?consumer.exclusive=true");
var consumer = session.CreateConsumer(queue);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/nms/activemq-message-dispatching-features.xml b/nms/activemq-message-dispatching-features.xml
index 1a31d79..ee689ae 100644
--- a/nms/activemq-message-dispatching-features.xml
+++ b/nms/activemq-message-dispatching-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="activemq-async-sends.xml">ActiveMQ Async Sends</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="caeec70b-78f9-4153-abd0-b09a567a3e3c" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/activemq-message-features.xml b/nms/activemq-message-features.xml
index 75ba8ee..185f090 100644
--- a/nms/activemq-message-features.xml
+++ b/nms/activemq-message-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="activemq-delay-and-schedule-message-feature.xml">ActiveMQ Delay and Schedule Message Feature</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="d19accf9-c63f-465f-81c8-8bdf74915300" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/activemq-mirrored-queues.xml b/nms/activemq-mirrored-queues.xml
index 64e8008..f524130 100644
--- a/nms/activemq-mirrored-queues.xml
+++ b/nms/activemq-mirrored-queues.xml
@@ -1,40 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQMirroredQueues-MirroredQueues">Mirrored Queues</h2>
-
-<p>Queues provide an excellent reliable and high performance <a shape="rect" href="../how-does-a-queue-compare-to-a-topic.xml">load balancing mechanism</a>. Each message placed on a queue can only be successfully processed by a single consumer. This is a good thing! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)">. However sometimes you want to monitor what messages flow between the producers and consumers on a queue. </p>
-
-<p>To do this you can use <a shape="rect" href="../virtual-destinations.xml">Virtual Destinations</a> to setup a virtual Queue which forwards the message to multiple physical queues. However enabling this for every single queue in your system can be painful.</p>
-
-<p>So to make it easy to monitor queues, we have added a feature we call <em>Mirrored Queues</em>. Mirrored Queues are kinda like a zero-configuration <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/wire-tap.html">Wire Tap</a> on all of your queues inside your Message Broker.</p>
-
-<h3 id="ActiveMQMirroredQueues-Example">Example</h3>
-
-<p>For example imagine we have a number of producers sending to queue <strong>Foo.Bar</strong> and consumers consuming from queue <strong>Foo.Bar</strong> and we want to monitor or view activity. </p>
-
-<p>If you enable Mirrored Queues then by default you can subscribe to the topic <strong>VirtualTopic.Mirror.Foo.Bar</strong> and receive all the messages that are sent to the queue <strong>Foo.Bar</strong>. Since its a topic as many consumers can subscribe to this topic as are required.</p>
-
-<p>If you want you can use this feature with <a shape="rect" href="../virtual-destinations.xml">Virtual Topics</a>; so that you can define a logical consumer; say called A. Then you can subscribe to the queue <strong>Consumer.A.VirtualTopic.Mirror.Foo.Bar</strong> to receive all the messages sent to queue <strong>Foo.Bar</strong> for the consumer A. You can then run multiple instances of this consumer who can then load balance among each other.</p>
-
-<p>This combination of Mirrored Queues and <a shape="rect" href="../virtual-destinations.xml">Virtual Destinations</a> can be extremely useful for monitoring transaction flows; for example with <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/bam.html">Business Activity Monitoring (BAM)</a>.</p>
-
-<h3 id="ActiveMQMirroredQueues-HowMirroredQueueswork">How Mirrored Queues work</h3>
-
-<p>When enabled, mirrored queues causes every message sent to a queue to also be sent to a topic of a similar name; so that folks who are interested in watching message exchanges on a queue can consume from the mirrored queue topic.</p>
-
-<p>When coupled with <a shape="rect" href="../virtual-destinations.xml">Virtual Topics</a> on this topic as described in the above example, you can actually end up creating new queues which are mirrors of a given queue dynamically at runtime!</p>
-
-<h3 id="ActiveMQMirroredQueues-EnablingMirroredQueues">Enabling Mirrored Queues</h3>
-
-<p>By default Mirrored Queues is disabled; as enabling it will cause a virtual topic to be created for each queue you use.</p>
-
-<p>To enable Mirrored Queues, set the <strong>useMirroredQueues</strong> property on <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/BrokerService.html">BrokerService</a> or add the following inside the <broker> element in the <a shape="rect" href="../xml-configuration.xml">Xml Configuration</a>:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <destinationInterceptors>
- <mirroredQueue copyMessage = "true" postfix=".qmirror" prefix=""/>
- </destinationInterceptors>
-]]></script>
-</div></div>
-
-<p>This would make a topic named "*.qmirror" for each queue on your Broker.</p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="df711ef0-d34a-43af-89fd-80e29253d479" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Mirrored Queues" ri:space-key="ACTIVEMQ"></page></link></parameter></structured-macro></div>
diff --git a/nms/activemq-net-110-release.xml b/nms/activemq-net-110-release.xml
index 6cc5367..f85e407 100644
--- a/nms/activemq-net-110-release.xml
+++ b/nms/activemq-net-110-release.xml
@@ -1,37 +1,31 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ.NET1.1.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release:</p>
<ul><li>Support for Failover Transport</li><li>Support for Discovery protocol.</li><li>Support for Windows Communication Foundation (WCF).</li><li>Improved API Documentation.</li><li>Many bug fixes.</li></ul>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p>
-</div></div>
+<structured-macro ac:macro-id="59ad4801-241d-4bc5-b572-e85503ccedb8" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ.NET1.1.0Release-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="ActiveMQ.NET1.1.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-src.zip">Apache.NMS-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-src.zip.asc">Apache.NMS-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-bin.zip">Apache.NMS-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-bin.zip.asc">Apache.NMS-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-src.zip">Apache.NMS.ActiveMQ-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-src.zip.asc">Apache.NMS.ActiveMQ-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-bin.zip">Apache.NMS.ActiveMQ-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-src.zip">Apache.NMS.EMS-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-src.zip.asc">Apache.NMS.EMS-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-bin.zip">Apache.NMS.EMS-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-bin.zip.asc">Apache.NMS.EMS-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-src.zip">Apache.NMS.MSMQ-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-src.zip.asc">Apache.NMS.MSMQ-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-bin.zip">Apache.NMS.MSMQ-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-bin.zip.asc">Apache.NMS.MSMQ-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-src.zip">Apache.NMS.WCF-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-src.zip.asc">Apache.NMS.WCF-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-bin.zip">Apache.NMS.WCF-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-bin.zip.asc">Apache.NMS.WCF-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-src.zip">Apache.NMS-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-src.zip.asc">Apache.NMS-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-bin.zip">Apache.NMS-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-bin.zip.asc">Apache.NMS-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-src.zip">Apache.NMS.ActiveMQ-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-src.zip.asc">Apache.NMS.ActiveMQ-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-bin.zip">Apache.NMS.ActiveMQ-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-src.zip">Apache.NMS.EMS-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-src.zip.asc">Apache.NMS.EMS-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-bin.zip">Apache.NMS.EMS-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-bin.zip.asc">Apache.NMS.EMS-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-src.zip">Apache.NMS.MSMQ-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-src.zip.asc">Apache.NMS.MSMQ-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-bin.zip">Apache.NMS.MSMQ-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-bin.zip.asc">Apache.NMS.MSMQ-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-src.zip">Apache.NMS.WCF-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-src.zip.asc">Apache.NMS.WCF-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-bin.zip">Apache.NMS.WCF-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-bin.zip.asc">Apache.NMS.WCF-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr></tbody></table>
<p><strong><em>NOTE:</em></strong> <em>In order to use the</em> <strong>Apache.NMS.EMS</strong> <em>project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application.</em></p>
-<h2 id="ActiveMQ.NET1.1.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ea69ed75-16c7-4f31-96ad-0450b2519c90" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-net/tags/1.1.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ.NET1.1.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a><br clear="none">
+<structured-macro ac:macro-id="883e1f26-5792-4600-98ba-0018ef297692" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11010&fixfor=11814&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/nms/activemq-net-120-release.xml b/nms/activemq-net-120-release.xml
index 06eaed8..b80206d 100644
--- a/nms/activemq-net-120-release.xml
+++ b/nms/activemq-net-120-release.xml
@@ -1,52 +1,46 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ.NET1.2.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.1.0 release.  Some highlights for this release.</p>
<ul><li>Addition of ConnectionMeteData to the Connection API.</li><li>Addition of QueueBrowser to the Session API.</li><li>Addition of an Individual Acknowledge Mode.</li><li>Improvements to the Failover Transport.</li><li>Improved API Documentation.</li><li>New IStreamMessage interface.</li><li>New IRedeliveryPolicy interface.</li><li>Expanded IByteMessage interface to read/write primitive types.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="ActiveMQ.NET1.2.0Release-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="ActiveMQ.NET1.2.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-src.zip">Apache.NMS-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-src.zip.asc">Apache.NMS-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1836 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-bin.zip">Apache.NMS-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-bin.zip.asc">Apache.NMS-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1836 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-src.zip">Apache.NMS-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-src.zip.asc">Apache.NMS-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1836 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-bin.zip">Apache.NMS-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-bin.zip.asc">Apache.NMS-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1836 </p></td></tr></tbody></table>
-<h2 id="ActiveMQ.NET1.2.0Release-Apache.NMSClientDownloads">Apache.NMS Client Downloads</h2>
+<h2>Apache.NMS Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-src.zip">Apache.NMS.Stomp-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-src.zip.asc">Apache.NMS.Stomp-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1858 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-bin.zip">Apache.NMS.Stomp-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-bin.zip.asc">Apache.NMS.Stomp-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1858 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-src.zip">Apache.NMS.ActiveMQ-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-src.zip.asc">Apache.NMS.ActiveMQ-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1864 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-bin.zip">Apache.NMS.ActiveMQ-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1864 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-src.zip">Apache.NMS.Stomp-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-src.zip.asc">Apache.NMS.Stomp-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1858 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-bin.zip">Apache.NMS.Stomp-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-bin.zip.asc">Apache.NMS.Stomp-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1858 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-src.zip">Apache.NMS.ActiveMQ-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-src.zip.asc">Apache.NMS.ActiveMQ-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1864 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-bin.zip">Apache.NMS.ActiveMQ-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1864 </p></td></tr></tbody></table>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">The NMS 1.2.0 Client Releases are still in progress</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<structured-macro ac:macro-id="dee3ab71-95fc-442d-bb53-738d5ae5eab6" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">The NMS 1.2.0 Client Releases are still in progress</parameter><rich-text-body>
<p> While the Apache.NMS API 1.2.0 has been released some of the client libraries are still in the process of being released.</p>
<p> Release Candidate 1 of the EMS, MSMQ and WCF NMS Clients are here:<br clear="none">
- <a shape="rect" class="external-link" href="http://people.apache.org/~tabish/nms-1.2.0-RC1">http://people.apache.org/~tabish/nms-1.2.0-RC1</a></p></div></div>
+ <a shape="rect" href="http://people.apache.org/~tabish/nms-1.2.0-RC1">http://people.apache.org/~tabish/nms-1.2.0-RC1</a></p></rich-text-body></structured-macro>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.EMS-1.2.0-src.zip">Apache.NMS.EMS-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.EMS-1.2.0-src.zip.asc">Apache.NMS.EMS-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.EMS-1.2.0-bin.zip">Apache.NMS.EMS-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.EMS-1.2.0-bin.zip.asc">Apache.NMS.EMS-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.MSMQ-1.2.0-src.zip">Apache.NMS.MSMQ-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.MSMQ-1.2.0-src.zip.asc">Apache.NMS.MSMQ-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.MSMQ-1.2.0-bin.zip">Apache.NMS.MSMQ-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.MSMQ-1.2.0-bin.zip.asc">Apache.NMS.MSMQ-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.WCF-1.2.0-src.zip">Apache.NMS.WCF-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.WCF-1.2.0-src.zip.asc">Apache.NMS.WCF-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.WCF-1.2.0-bin.zip">Apache.NMS.WCF-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.WCF-1.2.0-bin.zip.asc">Apache.NMS.WCF-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1794 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.EMS-1.2.0-src.zip">Apache.NMS.EMS-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.EMS-1.2.0-src.zip.asc">Apache.NMS.EMS-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.EMS-1.2.0-bin.zip">Apache.NMS.EMS-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.EMS-1.2.0-bin.zip.asc">Apache.NMS.EMS-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.MSMQ-1.2.0-src.zip">Apache.NMS.MSMQ-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.MSMQ-1.2.0-src.zip.asc">Apache.NMS.MSMQ-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.MSMQ-1.2.0-bin.zip">Apache.NMS.MSMQ-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.MSMQ-1.2.0-bin.zip.asc">Apache.NMS.MSMQ-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.WCF-1.2.0-src.zip">Apache.NMS.WCF-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.WCF-1.2.0-src.zip.asc">Apache.NMS.WCF-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.WCF-1.2.0-bin.zip">Apache.NMS.WCF-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.WCF-1.2.0-bin.zip.asc">Apache.NMS.WCF-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1794 </p></td></tr></tbody></table>
<p><strong><em>NOTE:</em></strong> <em>In order to use the</em> <strong>Apache.NMS.EMS</strong> <em>project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application.</em></p>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p>
-</div></div>
+<structured-macro ac:macro-id="9aa025c3-a58e-4ebb-96a5-c6e403b0637d" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ.NET1.2.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a78dfcc8-1dfe-4530-a2dc-0bb2eab1d133" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/tags/1.2.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ.NET1.2.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11815">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11815">release notes</a><br clear="none">
+<structured-macro ac:macro-id="06c5ad47-286d-4b00-8b82-8ab67ee2fd66" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11010&fixfor=11815&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/nms/activemq-net-130-release.xml b/nms/activemq-net-130-release.xml
index 7711b5c..b96d114 100644
--- a/nms/activemq-net-130-release.xml
+++ b/nms/activemq-net-130-release.xml
@@ -1,48 +1,42 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ.NET1.3.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.2.0 release.  Some highlights for this release.</p>
<ul><li>Addition of QueueBrowser support to NMS.ActiveMQ</li><li>Addition of SSL Support for NMS.ActiveMQ and NMS.Stomp</li><li>Improvements to the Failover Transport.</li><li>Improved API Documentation.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="ActiveMQ.NET1.3.0Release-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="ActiveMQ.NET1.3.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-src.zip">Apache.NMS-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-src.zip.asc">Apache.NMS-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1959 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-bin.zip">Apache.NMS-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-bin.zip.asc">Apache.NMS-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1959 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-src.zip">Apache.NMS-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-src.zip.asc">Apache.NMS-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1959 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-bin.zip">Apache.NMS-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-bin.zip.asc">Apache.NMS-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1959 </p></td></tr></tbody></table>
-<h2 id="ActiveMQ.NET1.3.0Release-Apache.NMSClientDownloads">Apache.NMS Client Downloads</h2>
+<h2>Apache.NMS Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-src.zip">Apache.NMS.ActiveMQ-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-src.zip.asc">Apache.NMS.ActiveMQ-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1965 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-bin.zip">Apache.NMS.ActiveMQ-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1965 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-src.zip">Apache.NMS.Stomp-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-src.zip.asc">Apache.NMS.Stomp-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1969 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-bin.zip">Apache.NMS.Stomp-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-bin.zip.asc">Apache.NMS.Stomp-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1969 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-src.zip">Apache.NMS.ActiveMQ-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-src.zip.asc">Apache.NMS.ActiveMQ-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1965 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-bin.zip">Apache.NMS.ActiveMQ-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1965 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-src.zip">Apache.NMS.Stomp-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-src.zip.asc">Apache.NMS.Stomp-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1969 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-bin.zip">Apache.NMS.Stomp-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-bin.zip.asc">Apache.NMS.Stomp-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1969 </p></td></tr></tbody></table>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">The NMS 1.3.0 Client Releases are still in progress the NMS below providers will be released following a release the NMS 1.3.0 API based on availability of providers maintainers.</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"></div></div>
+<structured-macro ac:macro-id="fe9f8b8f-26cc-45ac-88a0-fdef3927ccb6" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">The NMS 1.3.0 Client Releases are still in progress the NMS below providers will be released following a release the NMS 1.3.0 API based on availability of providers maintainers.</parameter></structured-macro>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.EMS-1.3.0-src.zip">Apache.NMS.EMS-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.EMS-1.3.0-src.zip.asc">Apache.NMS.EMS-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.EMS-1.3.0-bin.zip">Apache.NMS.EMS-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.EMS-1.3.0-bin.zip.asc">Apache.NMS.EMS-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.MSMQ-1.3.0-src.zip">Apache.NMS.MSMQ-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.MSMQ-1.3.0-src.zip.asc">Apache.NMS.MSMQ-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.MSMQ-1.3.0-bin.zip">Apache.NMS.MSMQ-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.MSMQ-1.3.0-bin.zip.asc">Apache.NMS.MSMQ-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.WCF-1.3.0-src.zip">Apache.NMS.WCF-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.WCF-1.3.0-src.zip.asc">Apache.NMS.WCF-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.WCF-1.3.0-bin.zip">Apache.NMS.WCF-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.WCF-1.3.0-bin.zip.asc">Apache.NMS.WCF-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1794 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.EMS-1.3.0-src.zip">Apache.NMS.EMS-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.EMS-1.3.0-src.zip.asc">Apache.NMS.EMS-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.EMS-1.3.0-bin.zip">Apache.NMS.EMS-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.EMS-1.3.0-bin.zip.asc">Apache.NMS.EMS-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.MSMQ-1.3.0-src.zip">Apache.NMS.MSMQ-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.MSMQ-1.3.0-src.zip.asc">Apache.NMS.MSMQ-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.MSMQ-1.3.0-bin.zip">Apache.NMS.MSMQ-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.MSMQ-1.3.0-bin.zip.asc">Apache.NMS.MSMQ-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.WCF-1.3.0-src.zip">Apache.NMS.WCF-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.WCF-1.3.0-src.zip.asc">Apache.NMS.WCF-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1794 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.WCF-1.3.0-bin.zip">Apache.NMS.WCF-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.WCF-1.3.0-bin.zip.asc">Apache.NMS.WCF-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1794 </p></td></tr></tbody></table>
<p><strong><em>NOTE:</em></strong> <em>In order to use the</em> <strong>Apache.NMS.EMS</strong> <em>project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application.</em></p>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p>
-</div></div>
+<structured-macro ac:macro-id="5a8db40d-96c3-4788-a98b-31fc13265fa9" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ.NET1.3.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="7a1f1395-3f6d-4240-98cc-97eae3f32aad" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/tags/1.3.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ.NET1.3.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12150">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12150">release notes</a><br clear="none">
+<structured-macro ac:macro-id="03fe7ec4-7bb1-40e4-bac5-e85ec7f1910a" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11010&fixfor=12150&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/nms/activemq-net-140-release.xml b/nms/activemq-net-140-release.xml
index 3782904..fabfdde 100644
--- a/nms/activemq-net-140-release.xml
+++ b/nms/activemq-net-140-release.xml
@@ -1,48 +1,42 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQ.NET1.4.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.3.0 release.  Some highlights for this release.</p>
<ul><li>Improved URI handling in all NMS clients.</li><li>Improved handling of Request Timeout settings.</li><li>Added a new SetBytes method to IMapMessage.</li><li>Added a new MessageTransformer API.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="ActiveMQ.NET1.4.0Release-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="ActiveMQ.NET1.4.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-src.zip">Apache.NMS-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-src.zip.asc">Apache.NMS-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-bin.zip">Apache.NMS-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-bin.zip.asc">Apache.NMS-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-src.zip">Apache.NMS-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-src.zip.asc">Apache.NMS-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-bin.zip">Apache.NMS-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-bin.zip.asc">Apache.NMS-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr></tbody></table>
-<h2 id="ActiveMQ.NET1.4.0Release-Apache.NMSClientDownloads">Apache.NMS Client Downloads</h2>
+<h2>Apache.NMS Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-src.zip">Apache.NMS.ActiveMQ-1.4.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-src.zip.asc">Apache.NMS.ActiveMQ-1.4.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.1.2098 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-bin.zip">Apache.NMS.ActiveMQ-1.4.1-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.4.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.1.2098 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-src.zip">Apache.NMS.Stomp-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-src.zip.asc">Apache.NMS.Stomp-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2077 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-bin.zip">Apache.NMS.Stomp-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-bin.zip.asc">Apache.NMS.Stomp-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2077 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-src.zip">Apache.NMS.ActiveMQ-1.4.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-src.zip.asc">Apache.NMS.ActiveMQ-1.4.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.1.2098 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-bin.zip">Apache.NMS.ActiveMQ-1.4.1-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.4.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.1.2098 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-src.zip">Apache.NMS.Stomp-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-src.zip.asc">Apache.NMS.Stomp-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2077 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-bin.zip">Apache.NMS.Stomp-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-bin.zip.asc">Apache.NMS.Stomp-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2077 </p></td></tr></tbody></table>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">The NMS 1.4.0 Client Releases are still in progress the NMS below providers will be released following a release the NMS 1.4.0 API based on availability of providers maintainers.</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"></div></div>
+<structured-macro ac:macro-id="2742fb43-51c3-47f0-87f6-3e251283bf12" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">The NMS 1.4.0 Client Releases are still in progress the NMS below providers will be released following a release the NMS 1.4.0 API based on availability of providers maintainers.</parameter></structured-macro>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.EMS-1.4.0-src.zip">Apache.NMS.EMS-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.EMS-1.4.0-src.zip.asc">Apache.NMS.EMS-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.EMS-1.4.0-bin.zip">Apache.NMS.EMS-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.EMS-1.4.0-bin.zip.asc">Apache.NMS.EMS-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.MSMQ-1.4.0-src.zip">Apache.NMS.MSMQ-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.MSMQ-1.4.0-src.zip.asc">Apache.NMS.MSMQ-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.MSMQ-1.4.0-bin.zip">Apache.NMS.MSMQ-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.MSMQ-1.4.0-bin.zip.asc">Apache.NMS.MSMQ-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.WCF-1.4.0-src.zip">Apache.NMS.WCF-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.WCF-1.4.0-src.zip.asc">Apache.NMS.WCF-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.WCF-1.4.0-bin.zip">Apache.NMS.WCF-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.WCF-1.4.0-bin.zip.asc">Apache.NMS.WCF-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.EMS-1.4.0-src.zip">Apache.NMS.EMS-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.EMS-1.4.0-src.zip.asc">Apache.NMS.EMS-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.EMS-1.4.0-bin.zip">Apache.NMS.EMS-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.EMS-1.4.0-bin.zip.asc">Apache.NMS.EMS-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.MSMQ-1.4.0-src.zip">Apache.NMS.MSMQ-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.MSMQ-1.4.0-src.zip.asc">Apache.NMS.MSMQ-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.MSMQ-1.4.0-bin.zip">Apache.NMS.MSMQ-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.MSMQ-1.4.0-bin.zip.asc">Apache.NMS.MSMQ-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.WCF-1.4.0-src.zip">Apache.NMS.WCF-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.WCF-1.4.0-src.zip.asc">Apache.NMS.WCF-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.WCF-1.4.0-bin.zip">Apache.NMS.WCF-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.WCF-1.4.0-bin.zip.asc">Apache.NMS.WCF-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr></tbody></table>
<p><strong><em>NOTE:</em></strong> <em>In order to use the</em> <strong>Apache.NMS.EMS</strong> <em>project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application.</em></p>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p>
-</div></div>
+<structured-macro ac:macro-id="63283744-5e6a-473f-bc6a-bacfb95d0d23" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro>
-<h2 id="ActiveMQ.NET1.4.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="44f10c52-f131-4ed5-b631-7035c87894fc" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/tags/1.4.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQ.NET1.4.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a><br clear="none">
+<structured-macro ac:macro-id="1ba8a86e-cf65-4666-8697-61270272517d" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="http://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=11010&fixfor=12188&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/nms/activemq-retroactive-consumers.xml b/nms/activemq-retroactive-consumers.xml
index c690a2e..d7bf27e 100644
--- a/nms/activemq-retroactive-consumers.xml
+++ b/nms/activemq-retroactive-consumers.xml
@@ -1,21 +1,19 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQRetroactiveConsumers-Background">Background</h2>
+<div class="wiki-content maincontent"><h2>Background</h2>
<p>A retroactive consumer is just a regular NMS consumer who indicates that at the start of a subscription every attempt should be used to go back in time and send any old messages (or the last message sent on that topic) that the consumer may have missed.</p>
-<p>See the <a shape="rect" href="../subscription-recovery-policy.xml">Subscription Recovery Policy</a> for more detail.</p>
+<p>See the <link><page ri:content-title="Subscription Recovery Policy" ri:space-key="ACTIVEMQ"></page></link> for more detail.</p>
-<h3 id="ActiveMQRetroactiveConsumers-Example">Example</h3>
+<h3>Example</h3>
<p>You mark a Consumer as being retroactive as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-var topic = session.GetTopic("TEST.Topic?consumer.retroactive=true");
+<structured-macro ac:macro-id="ba59700d-4562-492c-a54b-67abdf21067a" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
+var topic = session.GetTopic("TEST.Topic?consumer.retroactive=true");
var consumer = session.CreateConsumer(topic);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="ActiveMQRetroactiveConsumers-Limitations">Limitations</h2>
+<h2>Limitations</h2>
<p>Retroactive consumer will not consistently work when used across a network of brokers.</p>
diff --git a/nms/activemq-uri-configuration.xml b/nms/activemq-uri-configuration.xml
index 28c8b5b..14499fa 100644
--- a/nms/activemq-uri-configuration.xml
+++ b/nms/activemq-uri-configuration.xml
@@ -1,13 +1,7 @@
-<div class="wiki-content maincontent"><h2 id="ActiveMQURIConfiguration-ConfiguringNMS.ActiveMQ">Configuring NMS.ActiveMQ</h2><p>All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every facet of your NMS.ActiveMQ client. The tables below show the comprehensive set of parameters.</p><h3 id="ActiveMQURIConfiguration-ConnectionURIParameters"><strong>Connection URI Parameters</strong></h3><h5 id="ActiveMQURIConfiguration-ExampleConfiguration"> Example Configuration</h5><p>Using the Generic NMSConnectionFactory class would look as follows:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>var cf = new NMSConnectionFactory(
+<div class="wiki-content maincontent"><h2>Configuring NMS.ActiveMQ</h2><p>All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every facet of your NMS.ActiveMQ client. The tables below show the comprehensive set of parameters.</p><h3><strong>Connection URI Parameters</strong></h3><h5> Example Configuration</h5><p>Using the Generic NMSConnectionFactory class would look as follows:</p><structured-macro ac:macro-id="e1f01dc1-8328-4511-ad26-deef9612f4ed" ac:name="noformat" ac:schema-version="1"><plain-text-body>var cf = new NMSConnectionFactory(
"activemq:tcp://localhost:61616?wireFormat.tightEncodingEnabled=true");
-</pre>
-</div></div><p>You can also use the ActiveMQ ConecctionFactory implementation directory:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>var cf = new Apache.NMS.ActiveMQ.ConnectionFactory(
+</plain-text-body></structured-macro><p>You can also use the ActiveMQ ConecctionFactory implementation directory:</p><structured-macro ac:macro-id="0ca94639-950e-4d60-9fac-b15b45b5731e" ac:name="noformat" ac:schema-version="1"><plain-text-body>var cf = new Apache.NMS.ActiveMQ.ConnectionFactory(
"tcp://localhost:61616?wireFormat.tightEncodingEnabled=true");
-</pre>
-</div></div><h3 id="ActiveMQURIConfiguration-ProtocolOptions">Protocol Options</h3><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>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>tcp</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses TCP/IP Sockets to connect to the Broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>ssl</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses TCP/IP Sockets to connect to the Broker with an added SSL layer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>discovery</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses The Discovery Transport to find a Broker</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>failover</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses the Failover Transport to connect and reconnect to one or more Brokers</p></td></tr></tbody></table></div><h4 id="ActiveMQURIConfiguration-TransportOptions"><strong>Transport Options</strong></h4><h5 id="ActiveMQURIConfiguration-TCPTransportOptions"><strong>TCP Transport Options</strong></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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.useLogging</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Log data that is sent across the Transport.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.receiveBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>8192</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Amount of Data to buffer from the Socket</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.sendBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>8192</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Amount of Data to buffer before writing to the Socket</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.receiveTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time to wait for more data, zero means wait infinitely</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.sendTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Timeout on sends, 0 means wait forever for completion</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.requestTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time to wait before a Request Command is considered to have failed</p></td></tr></tbody></table></div><h5 id="ActiveMQURIConfiguration-DiscoveryTransportOptions">Discovery Transport Options</h5><h5 id="ActiveMQURIConfiguration-FailoverTransportOptions">Failover Transport Options</h5><p>Prior to NMS.ActiveMQ v1.4.0 the failover transport options did not use the transport.* prefix.</p><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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.timeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time that a send operation blocks before failing.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.initialReconnectDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Time in Milliseconds that the transport waits before attempting to reconnect the first time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.maxReconnectDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The max time in Milliseconds that the transport will wait before attempting to reconnect.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.backOffMultiplier</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The amount by which the reconnect delay will be multiplied by if useExponentialBackOff is enabled.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.useExponentialBackOff</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the delay between connection attempt grow on each try up to the max reconnect delay.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.randomize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the Uri to connect to be chosen at random from the list of available Uris.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.maxReconnectAttempts</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Maximum number of time the transport will attempt to reconnect before failing (0 means infinite retries)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.startupMaxReconnectAttempts</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Maximum number of time the transport will attempt to reconnect before failing when there has never been a connection made. (0 means infinite retries) <strong>(included in NMS.ActiveMQ v1.5.0+)</strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.reconnectDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The delay in milliseconds that the transport waits before attempting a reconnection.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.backup</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the Failover transport maintain hot backups.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.backupPoolSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If enabled, how many hot backup connections are made.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.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>transport.maxCacheSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>256</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of messages that are cached if trackMessages is enabled.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>transport.updateURIsSupported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Update the list of known brokers based on BrokerInfo messages sent to the client.</p></td></tr></tbody></table></div><h4 id="ActiveMQURIConfiguration-ConnectionOptions"><strong>Connection Options</strong></h4><p>Connection options can either be set via the connection.* prefix or the nms.* prefix similar to the java client's jms.* prefix settings.</p><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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.AsyncSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Are message sent Asynchronously.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.AsyncClose</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the close command be sent Asynchronously</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.AlwaysSyncSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Causes all messages a Producer sends to be sent Asynchronously.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.CopyMessageOnSend</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Copies the Message objects a Producer sends so that the client can reuse Message objects without affecting an in-flight message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.ProducerWindowSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The ProducerWindowSize is the maximum number of bytes in memory that a producer will transmit to a broker before waiting for acknowledgement messages from the broker that it has accepted the previously sent messages. In other words, this how you configure the producer flow control window that is used for async sends where the client is responsible for managing memory usage. The default value of 0 means no flow control at the client. See also <a shape="rect" class="external-link" href="http://activemq.apache.org/producer-flow-control.html">Producer Flow Control</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.useCompression</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should message bodies be compressed before being sent.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.sendAcksAsync</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should message acks be sent asynchronously</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.messagePrioritySupported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should messages be delivered to the client based on the value of the Message Priority header.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.dispatchAsync</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the connection's consumers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connection.watchTopicAdvisories</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the client watch for advisory messages from the broker to track the creation and deletion of temporary destinations.</p></td></tr></tbody></table></div><h5 id="ActiveMQURIConfiguration-OpenWireOptions"><strong>OpenWire Options</strong></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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.stackTraceEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the stack trace of exception that occur on the broker be sent to the client? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.cacheEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should commonly repeated values be cached so that less marshalling occurs? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.tcpNoDelayEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Does not affect the wire format, but provides a hint to the peer that TCP nodelay should be enabled on the communications Socket. Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.sizePrefixDisabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should serialized messages include a payload length prefix? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.tightEncodingEnabled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should wire size be optimized over CPU usage? Only used by the openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.maxInactivityDuration</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum inactivity duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to appear to die, so we allow the broker to kill connections if they are inactive for a period of time. Use by some transports to enable a keep alive heart beat feature. Set to a value <= 0 to disable inactivity monitoring.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxInactivityDurationInitalDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The initial delay in starting the maximum inactivity checks (and, yes, the word 'Inital' is supposed to be misspelled like that)</p></td></tr></tbody></table></div><h3 id="ActiveMQURIConfiguration-DestinationURIParameters"><strong>Destination URI Parameters</strong></h3><h5 id="ActiveMQURIConfiguration-ExampleConfiguration.1">Example Configuration</h5><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>d = session.CreateTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
-</pre>
-</div></div><h4 id="ActiveMQURIConfiguration-GeneralOptions"><strong>General Options</strong></h4><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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.prefetchSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of message the consumer will <a shape="rect" class="external-link" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch</a>.  <strong>Removed in v1.7.0 use connection prefetch policy instead.</strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.maximumPendingMessageLimit</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use to control if messages are dropped if a <a shape="rect" class="external-link" href="http://activemq.apache.org/slow-consumer-handling.html">slow consumer</a> situation exists.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.noLocal</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.dispatchAsync</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the consumer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Is this a <a shape="rect" class="external-link" href="http://activemq.apache.org/retroactive-consumer.html">Retroactive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.selector</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>JMS Selector used with the consumer.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.exclusive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Is this an <a shape="rect" class="external-link" href="http://activemq.apache.org/exclusive-consumer.html">Exclusive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.priority</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Allows you to configure a <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-priority.html">Consumer Priority</a>.</p></td></tr></tbody></table></div><h4 id="ActiveMQURIConfiguration-OpenWire-onlyOptions"><strong>OpenWire-only Options</strong></h4><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</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.browser</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.networkSubscription</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.optimizedAcknowledge</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables an optimised acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode for the consumers which can often be faster. <strong>WARNING</strong> enabling this issue could cause some issues with auto-acknowledgement on reconnection</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.noRangeAcks</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started.</p></td></tr></tbody></table></div></div>
+</plain-text-body></structured-macro><h3>Protocol Options</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>tcp</p></td><td colspan="1" rowspan="1"><p>Uses TCP/IP Sockets to connect to the Broker.</p></td></tr><tr><td colspan="1" rowspan="1"><p>ssl</p></td><td colspan="1" rowspan="1"><p>Uses TCP/IP Sockets to connect to the Broker with an added SSL layer.</p></td></tr><tr><td colspan="1" rowspan="1"><p>discovery</p></td><td colspan="1" rowspan="1"><p>Uses The Discovery Transport to find a Broker</p></td></tr><tr><td colspan="1" rowspan="1"><p>failover</p></td><td colspan="1" rowspan="1"><p>Uses the Failover Transport to connect and reconnect to one or more Brokers</p></td></tr></tbody></table><h4><strong>Transport Options</strong></h4><h5><strong>TCP Transport Options</strong></h5><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>transport.useLogging</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Log data that is sent across the Transport.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.receiveBufferSize</p></td><td colspan="1" rowspan="1"><p>8192</p></td><td colspan="1" rowspan="1"><p>Amount of Data to buffer from the Socket</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.sendBufferSize</p></td><td colspan="1" rowspan="1"><p>8192</p></td><td colspan="1" rowspan="1"><p>Amount of Data to buffer before writing to the Socket</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.receiveTimeout</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Time to wait for more data, zero means wait infinitely</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.sendTimeout</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Timeout on sends, 0 means wait forever for completion</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.requestTimeout</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Time to wait before a Request Command is considered to have failed</p></td></tr></tbody></table><h5>Discovery Transport Options</h5><h5>Failover Transport Options</h5><p>Prior to NMS.ActiveMQ v1.4.0 the failover transport options did not use the transport.* prefix.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>transport.timeout</p></td><td colspan="1" rowspan="1"><p>-1</p></td><td colspan="1" rowspan="1"><p>Time that a send operation blocks before failing.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.initialReconnectDelay</p></td><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>Time in Milliseconds that the transport waits before attempting to reconnect the first time.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.maxReconnectDelay</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>The max time in Milliseconds that the transport will wait before attempting to reconnect.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.backOffMultiplier</p></td><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>The amount by which the reconnect delay will be multiplied by if useExponentialBackOff is enabled.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.useExponentialBackOff</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should the delay between connection attempt grow on each try up to the max reconnect delay.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.randomize</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should the Uri to connect to be chosen at random from the list of available Uris.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.maxReconnectAttempts</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Maximum number of time the transport will attempt to reconnect before failing (0 means infinite retries)</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.startupMaxReconnectAttempts</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Maximum number of time the transport will attempt to reconnect before failing when there has never been a connection made. (0 means infinite retries) <strong>(included in NMS.ActiveMQ v1.5.0+)</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.reconnectDelay</p></td><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>The delay in milliseconds that the transport waits before attempting a reconnection.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.backup</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should the Failover transport maintain hot backups.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.backupPoolSize</p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>If enabled, how many hot backup connections are made.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.trackMessages</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><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"><p>transport.maxCacheSize</p></td><td colspan="1" rowspan="1"><p>256</p></td><td colspan="1" rowspan="1"><p>Number of messages that are cached if trackMessages is enabled.</p></td></tr><tr><td colspan="1" rowspan="1"><p>transport.updateURIsSupported</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Update the list of known brokers based on BrokerInfo messages sent to the client.</p></td></tr></tbody></table><h4><strong>Connection Options</strong></h4><p>Connection options can either be set via the connection.* prefix or the nms.* prefix similar to the java client's jms.* prefix settings.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>connection.AsyncSend</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Are message sent Asynchronously.</p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.AsyncClose</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should the close command be sent Asynchronously</p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.AlwaysSyncSend</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Causes all messages a Producer sends to be sent Asynchronously.</p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.CopyMessageOnSend</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Copies the Message objects a Producer sends so that the client can reuse Message objects without affecting an in-flight message.</p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.ProducerWindowSize</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>The ProducerWindowSize is the maximum number of bytes in memory that a producer will transmit to a broker before waiting for acknowledgement messages from the broker that it has accepted the previously sent messages. In other words, this how you configure the producer flow control window that is used for async sends where the client is responsible for managing memory usage. The default value of 0 means no flow control at the client. See also <a shape="rect" href="http://activemq.apache.org/producer-flow-control.html">Producer Flow Control</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.useCompression</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should message bodies be compressed before being sent.</p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.sendAcksAsync</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should message acks be sent asynchronously</p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.messagePrioritySupported</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should messages be delivered to the client based on the value of the Message Priority header.</p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.dispatchAsync</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should the broker <a shape="rect" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the connection's consumers.</p></td></tr><tr><td colspan="1" rowspan="1"><p>connection.watchTopicAdvisories</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>Should the client watch for advisory messages from the broker to track the creation and deletion of temporary destinations.</p></td></tr></tbody></table><h5><strong>OpenWire Options</strong></h5><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.stackTraceEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should the stack trace of exception that occur on the broker be sent to the client? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.cacheEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should commonly repeated values be cached so that less marshalling occurs? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.tcpNoDelayEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Does not affect the wire format, but provides a hint to the peer that TCP nodelay should be enabled on the communications Socket. Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.sizePrefixDisabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should serialized messages include a payload length prefix? Only used by openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.tightEncodingEnabled</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should wire size be optimized over CPU usage? Only used by the openwire protocol.</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.maxInactivityDuration</p></td><td colspan="1" rowspan="1"><p>30000</p></td><td colspan="1" rowspan="1"><p>The maximum inactivity duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to appear to die, so we allow the broker to kill connections if they are inactive for a period of time. Use by some transports to enable a keep alive heart beat feature. Set to a value <= 0 to disable inactivity monitoring.</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxInactivityDurationInitalDelay</p></td><td colspan="1" rowspan="1"><p>10000</p></td><td colspan="1" rowspan="1"><p>The initial delay in starting the maximum inactivity checks (and, yes, the word 'Inital' is supposed to be misspelled like that)</p></td></tr></tbody></table><h3><strong>Destination URI Parameters</strong></h3><h5>Example Configuration</h5><structured-macro ac:macro-id="f2b94df0-4839-4b0f-ab6f-365c063fba47" ac:name="noformat" ac:schema-version="1"><plain-text-body>d = session.CreateTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
+</plain-text-body></structured-macro><h4><strong>General Options</strong></h4><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>consumer.prefetchSize</p></td><td colspan="1" rowspan="1"><p>1000</p></td><td colspan="1" rowspan="1"><p>The number of message the consumer will <a shape="rect" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch</a>.  <strong>Removed in v1.7.0 use connection prefetch policy instead.</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.maximumPendingMessageLimit</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Use to control if messages are dropped if a <a shape="rect" href="http://activemq.apache.org/slow-consumer-handling.html">slow consumer</a> situation exists.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.noLocal</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.dispatchAsync</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Should the broker <a shape="rect" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the consumer.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Is this a <a shape="rect" href="http://activemq.apache.org/retroactive-consumer.html">Retroactive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.selector</p></td><td colspan="1" rowspan="1"><p>null</p></td><td colspan="1" rowspan="1"><p>JMS Selector used with the consumer.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.exclusive</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Is this an <a shape="rect" href="http://activemq.apache.org/exclusive-consumer.html">Exclusive Consumer</a>.</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.priority</p></td><td colspan="1" rowspan="1"><p>0</p></td><td colspan="1" rowspan="1"><p>Allows you to configure a <a shape="rect" href="http://activemq.apache.org/consumer-priority.html">Consumer Priority</a>.</p></td></tr></tbody></table><h4><strong>OpenWire-only Options</strong></h4><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>consumer.browser</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.networkSubscription</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.optimizedAcknowledge</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Enables an optimised acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode for the consumers which can often be faster. <strong>WARNING</strong> enabling this issue could cause some issues with auto-acknowledgement on reconnection</p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.noRangeAcks</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>consumer.retroactive</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started.</p></td></tr></tbody></table></div>
diff --git a/nms/activemq-virtual-destinations.xml b/nms/activemq-virtual-destinations.xml
index e1056cf..13487d8 100644
--- a/nms/activemq-virtual-destinations.xml
+++ b/nms/activemq-virtual-destinations.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><em>Virtual Destinations</em> allow us to create logical destinations that clients can use to produce and consume from but which map onto one or more <em>physical destinations</em>. It allows us to provide more flexible loosely coupled messaging configurations.<h2 id="ActiveMQVirtualDestinations-VirtualTopics">Virtual Topics</h2><p>The idea behind <em>publish subscribe</em> is a great one. Allow producers to be decoupled from consumers so that they do not even know how many consumers are interested in the messages they publish. The JMS specification defines support for durable topics however they have limitations as we will describe...</p><h3 id="ActiveMQVirtualDestinations-ThelimitationsofJMSdurabletopics">The limitations of JMS durable topics</h3><p>A JMS durable subscriber MessageConsumer is created with a unique JMS clientID and durable subscriber name. To be JMS compliant only one JMS connection can be active at any point in time for one JMS clientID, and only one consumer can be active for a clientID and subscriber name. i.e., only <strong>one</strong> thread can be actively consuming from a given logical topic subscriber. This means we cannot implement</p><ul><li>load balancing of messages.</li><li>fast failover of the subscriber if that one process running that one consumer thread dies.</li></ul><p>Now <em>queue</em> semantics in JMS offer the ability to load balance work across a number of consumers in a reliable way - allowing many threads, processes and machines to be used to process messages. Then we have sophisticated sticky load balancing techniques like <a shape="rect" href="../message-groups.xml">Message Groups</a> to load balance and parallelise work while maintaining ordering.</p><p>Another added benefit of having physical queues for each logical topic subscriber is we can them monitor the queue depths via <a shape="rect" href="../jmx.xml">JMX</a> to monitor system performance together with being able to browse these physical queues.</p><h3 id="ActiveMQVirtualDestinations-VirtualTopicstotherescue">Virtual Topics to the rescue</h3><p>The idea behind virtual topics is that producers send to a topic in the usual JMS way. Consumers can continue to use the Topic semantics in the JMS specification. However if the topic is virtual, consumer can consume from a physical queue for a logical topic subscription, allowing many consumers to be running on many machines & threads to load balance the load.</p><p>E.g., let's say we have a topic called <strong>VirtualTopic.Orders</strong>. (Where the prefix VirtualTopic. indicates its a virtual topic). And we logically want to send orders to systems A and B. Now with regular durable topics we'd create a JMS consumer for clientID_A and "A" along with clientID_B and "B".</p><p>With virtual topics we can just go right ahead and consume to queue <strong>Consumer.A.VirtualTopic.Orders</strong> to be a consumer for system A or consume to <strong>Consumer.B.VirtualTopic.Orders</strong> to be a consumer for system B.</p><p>We can now have a pool of consumers for each system which then compete for messages for systems A or B such that all the messages for system A are processed exactly once and similarly for system B.</p><h3 id="ActiveMQVirtualDestinations-Customizingtheout-of-the-boxdefaults">Customizing the out-of-the-box defaults</h3><p>The out-of-the-box defaults are described above. Namely that the only virtual topics available must be within the <strong>VirtualTopic.></strong> namespace and that the consumer queues are named <strong>Consumer.*.VirtualTopic.></strong>.</p><p>You can configure this to use whatever naming convention you wish. The following <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/broker/virtual/global-virtual-topics.xml">example</a> shows how to make all topics virtual topics. The example below is using the name <strong>></strong> to indicate 'match all topics'. You could use this wildcard to apply different virtual topic policies in different hierarchies.</p><pre><span style="color: rgb(0,0,0);"><destinationInterceptors> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualTopic name=">" prefix="VirtualTopicConsumers.*." selectorAware="false"/> </span> </pre><pre> </virtualDestinations></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"></destinationInterceptors></span></pre><p> </p><p>Note that making a topic virtual does add a small CPU overhead when sending messages to the topic but it is fairly small.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Option</th><th colspan="1" rowspan="1" class="confluenceTh">Default</th><th colspan="1" rowspan="1" class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">selectorAware</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">only messages that match one of the existing subscribers are actually dispatched. Using this option prevents the build up of unmatched messages when selectors are used by exclusive consumers</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">local</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, don't fan out messages that were received over a network</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">concurrentSend</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, use an executor to fanout such that sends occur in parallel. This allows the journal to batch writes which will reduce disk io (5.12)</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">transactedSend</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, use a transaction for fanout sends such that there is a single disk sync. A local broker transaction will be created if there is no client transaction (5.13)</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><span>dropOnResourceLimit</span></td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, ignore any ResourceAllocationException thrown during fanout (see: sendFailIfNoSpace policy entry) (5.16)</td></tr></tbody></table></div><p> </p><h2 id="ActiveMQVirtualDestinations-CompositeDestinations">Composite Destinations</h2><p>Composite Destinations allow for one-to-many relationships on individual destinations; the main use case is for <em>composite queues</em>. For example when a message is sent to queue A you may want to forward it also to queues B and C and topic D. Composite destinations are then a mapping from a virtual destination to a collection of other physical destinations. In this case the mapping is broker side and the client is unaware of the mapping between the destinations. This is different from client side <a shape="rect" href="../composite-destinations.xml">Composite Destinations</a> where the client uses a URL notation to specify the actual physical destinations that a message must be sent to.</p><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/broker/virtual/composite-queue.xml">example</a> shows how to set up a <strong><compositeQueue/></strong> element in the XML configuration so that when a message is sent to <code>MY.QUEUE</code> then it is really forwarded to the physical queue <code>FOO</code> and the topic <code>BAR</code>.</p><pre><span style="color: rgb(0,0,0);"><destinationInterceptors></span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <compositeQueue name="MY.QUEUE"></span></pre><pre><span style="color: rgb(0,0,0);"> <forwardTo></span></pre><pre><span style="color: rgb(0,0,0);"> <queue physicalName="FOO" /> </span></pre><pre><span style="color: rgb(0,0,0);"> <topic physicalName="BAR" /></span></pre><pre><span style="color: rgb(0,0,0);"> </forwardTo></span></pre><pre><span style="color: rgb(0,0,0);"> </compositeQueue></span></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinations></span></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinationInterceptor></span></pre><pre><span style="color: rgb(0,0,0);"></destinationInterceptors></span></pre><p> </p><p>By default, subscribers cannot consume messages directly from a composite queue or topic - it is a logical construct only. Given the configuration above, subscribers can only consume messages from <code>FOO</code> and <code>BAR</code>; but not <code>MY.QUEUE</code>.</p><p>This behaviour can be altered to implement use cases such as watching a queue by sending the same messages to a notification topic (wire tapping), by setting the optionally set <code>forwardOnly</code> attribute to false.</p><pre><compositeQueue name="IncomingOrders" forwardOnly="false"> </pre><pre> <forwardTo></pre><pre> <topic physicalName="Notifications" /></pre><pre> </forwardTo></pre><pre> </compositeQueue></pre><p> </p><p>Messages sent to <code>IncomingOrders</code> will all be copied and forwarded to <code>Notifications</code>, before being placed on the physical <code>IncomingOrders</code> queue for consumption by subscribers.</p><p>Where the <code>forwardOnly</code> attribute is not defined or is set to <code>true</code>, there is no logical difference between a <code>compositeQueue</code> and a <code>compositeTopic</code> - they can be used interchangeably. It is only when a composite destination is made physical through the use of <code>forwardOnly</code> that the choice of <code>compositeTopic</code>/<code>compositeQueue</code> has an impact on behavior.</p><h3 id="ActiveMQVirtualDestinations-Usingfiltereddestinations">Using filtered destinations</h3><p>From Apache ActiveMQ <strong>4.2</strong> onwards you can now use selectors to define virtual destinations.</p><p>You may wish to create a virtual destination which forwards messages to multiple destinations but applying a selector first to decide if the message really does have to go to a particular destination.</p><p>The following example shows how a message sent to the virtual destination <strong>MY.QUEUE</strong> will be forwarded to <strong>FOO</strong> and <strong>BAR</strong> if the selectors match</p><pre><destinationInterceptors> <virtualDestinationInterceptor> <virtualDestinations> </pre><pre> <compositeQueue name="MY.QUEUE"></pre><pre> <forwardTo></pre><pre> <filteredDestination selector="odd = 'yes'" queue="FOO"/></pre><pre> <filteredDestination selector="i = 5" topic="BAR"/></pre><pre> </forwardTo></pre><pre> </compositeQueue></pre><pre></virtualDestinations> </virtualDestinationInterceptor> </destinationInterceptors></pre><p> </p><h2 id="ActiveMQVirtualDestinations-AvoidingDuplicateMessageinaNetworkofBrokers">Avoiding Duplicate Message in a Network of Brokers</h2><p>You have to make sure that the messages sent to the <strong>Consumer.*.VirtualTopic.></strong> destination are not forwarded when you're using both queue-based and non-queue based subscribers to the virtual topic (that is, if you have normal topic subscribers to the virtual topic). If you use Virtual Topics in a network of brokers, it is likely you will get duplicate messages if you use the default network configuration. This is because a network node will not only forward message sent to the virtual topic, but also the associated physical queues. To fix this, you should disable forwarding messages on the associated physical queues.</p><p>Here is an example of how to do that:</p><pre><span style="color: rgb(0,0,0);"><networkConnectors> <networkConnector uri="static://(<a shape="rect" href="tcp://localhost:61617" rel="nofollow">tcp://localhost:61617</a>)"></span></pre><pre><span style="color: rgb(0,0,0);"> <excludedDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <queue physicalName="Consumer.*.VirtualTopic.>"/> </span></pre><pre><span style="color: rgb(0,0,0);"> </excludedDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"></networkConnector> </networkConnectors></span></pre><p> </p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="a948cbd6-a385-4923-ae34-6eb70ccb6d87" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Virtual Destinations" ri:space-key="ACTIVEMQ"></page></link></parameter></structured-macro></div>
diff --git a/nms/activemq-wildcards.xml b/nms/activemq-wildcards.xml
index 821c89c..1603a32 100644
--- a/nms/activemq-wildcards.xml
+++ b/nms/activemq-wildcards.xml
@@ -1,8 +1,2 @@
-<div class="wiki-content maincontent">We support destination wildcards to provide easy support for federated name hierarchies. This concept has been popular in financial market data for some time as a way of organizing events (such as price changes) into hierarchies and to use wildcards for easy subscription of the range of information you're interested in.<p>For example imagine you are sending price messages from a stock exchange feed. You might use some kind of destination such as</p><ul><li><code>PRICE.STOCK.NASDAQ.ORCL</code> to publish Oracle Corporation's price on NASDAQ and</li><li><code>PRICE.STOCK.NYSE.IBM</code> to publish IBM's price on the New York Stock Exchange</li></ul><p>A subscriber could then use exact destinations to subscribe to exactly the prices it requires. Or it could use wildcards to define hierarchical pattern matches to the destinations to subscribe from.</p><h3 id="ActiveMQWildcards-Wildcardssupported">Wildcards supported</h3><p>We support the following wildcards which are fairly standard practice; wildcards are not part of the JMS specification so are custom enhancements.</p><ul><li><code>.</code> is used to separate names in a path</li><li><code>*</code> is used to match any name in a path</li><li><code>></code> is used to recursively match any destination starting from this name</li></ul><p>For example using the example above, these subscriptions are possible</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Subscription</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Meaning</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>PRICE.></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any price for any product on any exchange</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>PRICE.STOCK.></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any price for a stock on any exchange</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>PRICE.STOCK.NASDAQ.*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any stock price on NASDAQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>PRICE.STOCK.*.IBM</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any IBM stock price on any exchange</p></td></tr></tbody></table></div><p><strong>Note:</strong> Don't specify any string after '>' on your wildcard expression, it will be ignored. E.g. using a wildcard <code>PRICE.>.IBM</code> will also match <code>PRICE.STOCK.NASDAQ.FB.</code> Using '>' really matches everything till the end of the destination name.</p><h3 id="ActiveMQWildcards-Custompathseparator">Custom path separator</h3><p>As of version 5.5.0 we support <a shape="rect" class="external-link" href="http://activemq.apache.org/interceptors.html">plugin</a> that allows clients to use customer path separator. So instead of</p><p><code>FOO.BAR.*</code></p><p>you can use</p><p><code>FOO/BAR/*</code></p><p>To</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <plugins>
- .....
- <destinationPathSeparatorPlugin/>
- </plugins>
-]]></script>
-</div></div><p>Please note that you should add this plugin as last if you want it to work properly with other plugins (such as <a shape="rect" class="external-link" href="http://activemq.apache.org/security.html">security</a> for example).</p><p>A default path separator this plugin will use is <code>/</code>. You can customize it further using <code>pathSeparator</code> property.</p></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="a5a79832-2fff-46b0-8a26-f8b9f27e712f" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Wildcards" ri:space-key="ACTIVEMQ"></page></link></parameter></structured-macro></div>
diff --git a/nms/amqp-build-notes.xml b/nms/amqp-build-notes.xml
index b37d224..5738042 100644
--- a/nms/amqp-build-notes.xml
+++ b/nms/amqp-build-notes.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="AMQPBuildNotes-Defaultbuild">Default build</h1><p>Executing <strong>nant</strong> in the project home directory will produce two builds:</p><ul><li>Debug/Release .NET 2.0 x86 in the \net-2.0 folder built with Visual Studio 2008</li><li>Debug/Release .NET 4.0 x86 in the \net-4.0 folder built with Visual Studio 2010</li></ul><p>Your build system must have Visual Studio 2008, Visual Studio 2010, or both to produce the desired build.</p><h1 id="AMQPBuildNotes-Dependenciesandrestrictions">Dependencies and restrictions</h1><p>The version dependencies on Visual Studio and the x86-only restrictions are artefacts of the delivery mechanism for the vendor\QPid\Apache.QPID support libraries. These restrictions are important to understand for using this provider and for packaging this provider for your application.</p><h2 id="AMQPBuildNotes-Supportlibrarycomponents(x86only)">Support library components (x86 only)</h2><p>The support libraries consist of two parts:</p><ul><li>Native C++ Qpid Messaging (qpid*.dll, boost*.dll)</li><li>.NET interop binding between .NET and the native C++ code (org.apache.qpid.messaging.dll)</li></ul><p>The C++ support libraries are compiled with specific versions of Visual Studio and linked to the corresponding MSVC runtime libraries. In this release of Apache.NMS.AMQP only the x86 versions of Apache.QPID are provided.</p><p>Running the Apache.NMS.AMQP provider in an x64 environment or in a .NET application choosing AnyCPU will not work correctly. Please choose <strong>x86</strong> for your application <em>Platform target</em>.</p><h2 id="AMQPBuildNotes-Runtimelibrarystaging">Run time library staging</h2><p>When your application runs make sure that all of the Apache.QPID support library dll files are copied to the final execution directory. When the support library files are not in same folder as <em>org.apache.qpid.messaging.dll</em> then the Apache.NMS.AMQP provider may not load correctly. Having the support files on your application's PATH is not sufficient for successful loading.</p><p> </p></div>
+<div class="wiki-content maincontent"><h1>Default build</h1><p>Executing <strong>nant</strong> in the project home directory will produce two builds:</p><ul><li>Debug/Release .NET 2.0 x86 in the \net-2.0 folder built with Visual Studio 2008</li><li>Debug/Release .NET 4.0 x86 in the \net-4.0 folder built with Visual Studio 2010</li></ul><p>Your build system must have Visual Studio 2008, Visual Studio 2010, or both to produce the desired build.</p><h1>Dependencies and restrictions</h1><p>The version dependencies on Visual Studio and the x86-only restrictions are artefacts of the delivery mechanism for the vendor\QPid\Apache.QPID support libraries. These restrictions are important to understand for using this provider and for packaging this provider for your application.</p><h2>Support library components (x86 only)</h2><p>The support libraries consist of two parts:</p><ul><li>Native C++ Qpid Messaging (qpid*.dll, boost*.dll)</li><li>.NET interop binding between .NET and the native C++ code (org.apache.qpid.messaging.dll)</li></ul><p>The C++ support libraries are compiled with specific versions of Visual Studio and linked to the corresponding MSVC runtime libraries. In this release of Apache.NMS.AMQP only the x86 versions of Apache.QPID are provided.</p><p>Running the Apache.NMS.AMQP provider in an x64 environment or in a .NET application choosing AnyCPU will not work correctly. Please choose <strong>x86</strong> for your application <em>Platform target</em>.</p><h2>Run time library staging</h2><p>When your application runs make sure that all of the Apache.QPID support library dll files are copied to the final execution directory. When the support library files are not in same folder as <em>org.apache.qpid.messaging.dll</em> then the Apache.NMS.AMQP provider may not load correctly. Having the support files on your application's PATH is not sufficient for successful loading.</p><p> </p></div>
diff --git a/nms/amqp-examples.xml b/nms/amqp-examples.xml
index e9d4031..b9aaca1 100644
--- a/nms/amqp-examples.xml
+++ b/nms/amqp-examples.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="AMQPExamples-HelloWorld.cs">HelloWorld.cs</h1><p>The source kit for the Apache.NMS.AMQP provider includes a HelloWorld project.</p><p>HelloWorld requires an AMQP 1.0 broker (either ActiveMQ or Qpidd) to be running on localhost:5672. Of course you may specify a different URI to select any broker.</p><h1 id="AMQPExamples-NUnittestcases">NUnit test cases</h1><p>Please refer to the <em>amqp-test</em> project test case source code for examples of acceptable values for this provider.</p><p> </p><p> </p></div>
+<div class="wiki-content maincontent"><h1>HelloWorld.cs</h1><p>The source kit for the Apache.NMS.AMQP provider includes a HelloWorld project.</p><p>HelloWorld requires an AMQP 1.0 broker (either ActiveMQ or Qpidd) to be running on localhost:5672. Of course you may specify a different URI to select any broker.</p><h1>NUnit test cases</h1><p>Please refer to the <em>amqp-test</em> project test case source code for examples of acceptable values for this provider.</p><p> </p><p> </p></div>
diff --git a/nms/apachenms-150-release.xml b/nms/apachenms-150-release.xml
index a4a31c6..dd6415c 100644
--- a/nms/apachenms-150-release.xml
+++ b/nms/apachenms-150-release.xml
@@ -1,67 +1,61 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS1.5.0Release-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.4.0 release.  Some highlights for this release.</p>
-<h5 id="Apache.NMS1.5.0Release-NMSAPI">NMS API</h5>
+<h5>NMS API</h5>
<ul><li>New Optional .NET Transaction Specific Connection classes that allow a client to offer support for operations within MS .NET Distributed Transactions.</li></ul>
-<h5 id="Apache.NMS1.5.0Release-ActiveMQClient.">ActiveMQ Client.</h5>
+<h5>ActiveMQ Client.</h5>
-<h5 id="Apache.NMS1.5.0Release-StompClient.">Stomp Client.</h5>
+<h5>Stomp Client.</h5>
-<h6 id="Apache.NMS1.5.0Release-v1.5.0">v1.5.0</h6>
+<h6>v1.5.0</h6>
<ul><li>Support for the current changes in the Stomp 1.1 draft specification.</li><li>Improved Inactivity Monitoring with two way heartbeats when used with a Stomp v1.1 broker.</li><li>New startupMaxReconnectAttempts option in the failover transport.</li><li>Several other bugfixes for issues found since v1.4.0 was released.</li></ul>
-<h6 id="Apache.NMS1.5.0Release-v1.5.1">v1.5.1</h6>
+<h6>v1.5.1</h6>
<ul><li>Fixed a memory leak in the Inactivity Monitoring code.</li><li>Fixed a bug that could cause the Failover to not work.</li><li>Fixed a bug that caused SSL Certs to not be loaded in some cases.</li><li>Fixed a bug that was causing major performance issues for synchronous consumers.</li><li>Fixed issues found with the Stomp v1.1 support.</li></ul>
-<h2 id="Apache.NMS1.5.0Release-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS1.5.0Release-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-src.zip">Apache.NMS-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-src.zip.asc">Apache.NMS-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2194 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-bin.zip">Apache.NMS-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-bin.zip.asc">Apache.NMS-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2194 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-src.zip">Apache.NMS-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-src.zip.asc">Apache.NMS-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2194 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-bin.zip">Apache.NMS-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-bin.zip.asc">Apache.NMS-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2194 </p></td></tr></tbody></table>
-<h2 id="Apache.NMS1.5.0Release-Apache.NMSClientDownloads">Apache.NMS Client Downloads</h2>
+<h2>Apache.NMS Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-src.zip">Apache.NMS.Stomp-1.5.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-src.zip.asc">Apache.NMS.Stomp-1.5.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2216 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip">Apache.NMS.Stomp-1.5.1-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip.asc">Apache.NMS.Stomp-1.5.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2216 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-src.zip">Apache.NMS.Stomp-1.5.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-src.zip.asc">Apache.NMS.Stomp-1.5.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2216 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip">Apache.NMS.Stomp-1.5.1-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip.asc">Apache.NMS.Stomp-1.5.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2216 </p></td></tr></tbody></table>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">The NMS 1.5.0 Client Releases are still in progress the NMS below providers will be released following a release the NMS 1.5.0 API based on availability of providers maintainers.</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"></div></div>
+<structured-macro ac:macro-id="ce660269-9d9b-4cb9-b6e9-b629cbd56730" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">The NMS 1.5.0 Client Releases are still in progress the NMS below providers will be released following a release the NMS 1.5.0 API based on availability of providers maintainers.</parameter></structured-macro>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-src.zip">Apache.NMS.ActiveMQ-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-src.zip.asc">Apache.NMS.ActiveMQ-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2194 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-bin.zip">Apache.NMS.ActiveMQ-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2194 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-src.zip">Apache.NMS.ActiveMQ-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-src.zip.asc">Apache.NMS.ActiveMQ-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2194 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-bin.zip">Apache.NMS.ActiveMQ-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2194 </p></td></tr></tbody></table>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">The NMS 1.5.0 Client Releases are still in progress the NMS below providers will be released following a release the NMS 1.5.0 API based on availability of providers maintainers.</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"></div></div>
+<structured-macro ac:macro-id="27c41747-f95d-4240-af4c-db99cd656e01" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">The NMS 1.5.0 Client Releases are still in progress the NMS below providers will be released following a release the NMS 1.5.0 API based on availability of providers maintainers.</parameter></structured-macro>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.EMS-1.5.0-src.zip">Apache.NMS.EMS-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.EMS-1.5.0-src.zip.asc">Apache.NMS.EMS-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.EMS-1.5.0-bin.zip">Apache.NMS.EMS-1..0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.EMS-1.5.0-bin.zip.asc">Apache.NMS.EMS-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.MSMQ-1.5.0-src.zip">Apache.NMS.MSMQ-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.MSMQ-1.5.0-src.zip.asc">Apache.NMS.MSMQ-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.MSMQ-1.5.0-bin.zip">Apache.NMS.MSMQ-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.MSMQ-1.5.0-bin.zip.asc">Apache.NMS.MSMQ-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.WCF-1.5.0-src.zip">Apache.NMS.WCF-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.WCF-1.5.0-src.zip.asc">Apache.NMS.WCF-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.WCF-1.5.0-bin.zip">Apache.NMS.WCF-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.WCF-1.5.0-bin.zip.asc">Apache.NMS.WCF-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2075 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.EMS-1.5.0-src.zip">Apache.NMS.EMS-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.EMS-1.5.0-src.zip.asc">Apache.NMS.EMS-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.EMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.EMS-1.5.0-bin.zip">Apache.NMS.EMS-1..0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.EMS-1.5.0-bin.zip.asc">Apache.NMS.EMS-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.MSMQ-1.5.0-src.zip">Apache.NMS.MSMQ-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.MSMQ-1.5.0-src.zip.asc">Apache.NMS.MSMQ-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.MSMQ-1.5.0-bin.zip">Apache.NMS.MSMQ-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.MSMQ-1.5.0-bin.zip.asc">Apache.NMS.MSMQ-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.WCF-1.5.0-src.zip">Apache.NMS.WCF-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.WCF-1.5.0-src.zip.asc">Apache.NMS.WCF-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.WCF Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.WCF-1.5.0-bin.zip">Apache.NMS.WCF-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.WCF-1.5.0-bin.zip.asc">Apache.NMS.WCF-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2075 </p></td></tr></tbody></table>
<p><strong><em>NOTE:</em></strong> <em>In order to use the</em> <strong>Apache.NMS.EMS</strong> <em>project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application.</em></p>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p>
-</div></div>
+<structured-macro ac:macro-id="698d65e1-5f6b-49aa-bb57-f6f723ee3259" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS1.5.0Release-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5647a97d-e33c-46f1-89a9-b82ecd7f99df" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/tags/1.5.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS1.5.0Release-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a><br clear="none">
-</p><div class="aui-message warning jim-inline-block">
- <span class="aui-icon icon-warning"></span>JIRA Issues Macro: Data cannot be retrieved due to an unexpected error
-</div>
- </div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a><br clear="none">
+<structured-macro ac:macro-id="74d2c27b-da77-448f-ba0d-878d5f269820" ac:name="jiraissues" ac:schema-version="1"><parameter ac:name="url"><url ri:value="https://issues.apache.org/activemq/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&p2id=12311201&fixfor=12315640&sorter/field=issuekey&sorter/order=DESC"></url></parameter></structured-macro> </p></div>
diff --git a/nms/apachenms-activemq-v110.xml b/nms/apachenms-activemq-v110.xml
index b1f2da4..cfe6dca 100644
--- a/nms/apachenms-activemq-v110.xml
+++ b/nms/apachenms-activemq-v110.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSActiveMQv1.1.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS.ActiveMQ project, and all provider implementation projects. Following are some highlights of this release:</p>
@@ -6,28 +6,25 @@
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p>
-</div></div>
+<structured-macro ac:macro-id="33540a39-72f9-4c63-a0d2-5a0d054b8e62" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMSActiveMQv1.1.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMSActiveMQv1.1.0-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-src.zip">Apache.NMS.ActiveMQ-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-src.zip.asc">Apache.NMS.ActiveMQ-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-bin.zip">Apache.NMS.ActiveMQ-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-src.zip">Apache.NMS.ActiveMQ-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-src.zip.asc">Apache.NMS.ActiveMQ-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-bin.zip">Apache.NMS.ActiveMQ-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.ActiveMQ-1.1.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr></tbody></table>
-<h2 id="Apache.NMSActiveMQv1.1.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2985ac04-3b0d-4e2b-b719-8bcf3ae9d83c" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-net/Apache.NMS.ActiveMQ/tags/1.1.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMSActiveMQv1.1.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
diff --git a/nms/apachenms-api-v110.xml b/nms/apachenms-api-v110.xml
index ae858f4..678fce6 100644
--- a/nms/apachenms-api-v110.xml
+++ b/nms/apachenms-api-v110.xml
@@ -1,28 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSAPIv1.1.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release:</p>
<ul><li>Improved API Documentation.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMSAPIv1.1.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMSAPIv1.1.0-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-src.zip">Apache.NMS-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-src.zip.asc">Apache.NMS-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-bin.zip">Apache.NMS-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-bin.zip.asc">Apache.NMS-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-src.zip">Apache.NMS-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-src.zip.asc">Apache.NMS-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-bin.zip">Apache.NMS-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS-1.1.0-bin.zip.asc">Apache.NMS-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr></tbody></table>
-<h2 id="Apache.NMSAPIv1.1.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5d2c9eca-93cf-430c-8f17-604564256c0e" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-net/Apache.NMS/tags/1.1.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMSAPIv1.1.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
diff --git a/nms/apachenms-api-v120.xml b/nms/apachenms-api-v120.xml
index 097d519..314b436 100644
--- a/nms/apachenms-api-v120.xml
+++ b/nms/apachenms-api-v120.xml
@@ -1,28 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSAPIv1.2.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS API and fixes several bugs found in the 1.1.0 release.  Some highlights for this release.</p>
<ul><li>Addition of IConnectionMeteData to the Connection API.</li><li>Addition of IQueueBrowser to the Session API.</li><li>Improved API Documentation.</li><li>New IStreamMessage interface.</li><li>New IRedeliveryPolicy interface.</li><li>Expanded IByteMessage interface to read/write primitive types.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMSAPIv1.2.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMSAPIv1.2.0-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-src.zip">Apache.NMS-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-src.zip.asc">Apache.NMS-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1836 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-bin.zip">Apache.NMS-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-bin.zip.asc">Apache.NMS-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1836 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-src.zip">Apache.NMS-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-src.zip.asc">Apache.NMS-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1836 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-bin.zip">Apache.NMS-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS-1.2.0-bin.zip.asc">Apache.NMS-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1836 </p></td></tr></tbody></table>
-<h2 id="Apache.NMSAPIv1.2.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="645e8242-db98-444c-92c9-79ebab0b5e75" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.2.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMSAPIv1.2.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11815">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11815">release notes</a></p></div>
diff --git a/nms/apachenms-api-v130.xml b/nms/apachenms-api-v130.xml
index 1bb756c..9b13d39 100644
--- a/nms/apachenms-api-v130.xml
+++ b/nms/apachenms-api-v130.xml
@@ -1,28 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSAPIv1.3.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS API and fixes several bugs found in the 1.2.0 release.  Some highlights for this release.</p>
<ul><li>Improved API Documentation.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMSAPIv1.3.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMSAPIv1.3.0-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-src.zip">Apache.NMS-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-src.zip.asc">Apache.NMS-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1959 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-bin.zip">Apache.NMS-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-bin.zip.asc">Apache.NMS-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1959 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-src.zip">Apache.NMS-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-src.zip.asc">Apache.NMS-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1959 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-bin.zip">Apache.NMS-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://archive.apache.org/dist/activemq/apache-nms/1.3.0/Apache.NMS-1.3.0-bin.zip.asc">Apache.NMS-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1959 </p></td></tr></tbody></table>
-<h2 id="Apache.NMSAPIv1.3.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="712ba404-7fe3-4cac-847a-0ca10b24bbb2" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.3.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMSAPIv1.3.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12150">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12150">release notes</a></p></div>
diff --git a/nms/apachenms-api-v140.xml b/nms/apachenms-api-v140.xml
index 6b6c50d..8c7d56c 100644
--- a/nms/apachenms-api-v140.xml
+++ b/nms/apachenms-api-v140.xml
@@ -1,28 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSAPIv1.4.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS API and fixes several bugs found in the 1.3.0 release.  Some highlights for this release.</p>
<ul><li>Improved URI handling in all NMS clients.</li><li>Added a new SetBytes method to IMapMessage.</li><li>Added a new MessageTransformer API.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMSAPIv1.4.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMSAPIv1.4.0-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-src.zip">Apache.NMS-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-src.zip.asc">Apache.NMS-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-bin.zip">Apache.NMS-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-bin.zip.asc">Apache.NMS-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2075 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-src.zip">Apache.NMS-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-src.zip.asc">Apache.NMS-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-bin.zip">Apache.NMS-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS-1.4.0-bin.zip.asc">Apache.NMS-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2075 </p></td></tr></tbody></table>
-<h2 id="Apache.NMSAPIv1.4.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c1354e5d-6741-4db7-849f-048b7e7f9ad9" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.4.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMSAPIv1.4.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a></p></div>
diff --git a/nms/apachenms-api-v150.xml b/nms/apachenms-api-v150.xml
index 8862dbb..6aab91a 100644
--- a/nms/apachenms-api-v150.xml
+++ b/nms/apachenms-api-v150.xml
@@ -1,30 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSAPIv1.5.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS API.</p>
-<h5 id="Apache.NMSAPIv1.5.0-NMSAPIUpdates">NMS API Updates</h5>
+<h5>NMS API Updates</h5>
<ul><li>New Optional .NET Transaction Specific Connection classes that allow a client to offer support for operations within MS .NET Distributed Transactions.</li></ul>
-<h2 id="Apache.NMSAPIv1.5.0-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMSAPIv1.5.0-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-src.zip">Apache.NMS-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-src.zip.asc">Apache.NMS-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2194 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-bin.zip">Apache.NMS-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-bin.zip.asc">Apache.NMS-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2194 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-src.zip">Apache.NMS-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-src.zip.asc">Apache.NMS-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2194 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-bin.zip">Apache.NMS-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.0-bin.zip.asc">Apache.NMS-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2194 </p></td></tr></tbody></table>
-<h2 id="Apache.NMSAPIv1.5.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c0de458d-2f72-44dc-85bb-b3bdd79cd1b6" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.5.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMSAPIv1.5.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
diff --git a/nms/apachenms-api-v151.xml b/nms/apachenms-api-v151.xml
index 0b61861..957bbb4 100644
--- a/nms/apachenms-api-v151.xml
+++ b/nms/apachenms-api-v151.xml
@@ -1,30 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSAPIv1.5.1-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is a bugfix release of the NMS API there are no API changes in this release.</p>
-<h5 id="Apache.NMSAPIv1.5.1-NMSfixes">NMS fixes</h5>
+<h5>NMS fixes</h5>
<ul><li>Fixes a bug that can cause the Message properties object to marshal to a byte array that is much larger than needed which adds unwanted overhead on the wire for marshaled Messages.</li></ul>
-<h2 id="Apache.NMSAPIv1.5.1-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMSAPIv1.5.1-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.1-src.zip">Apache.NMS-1.5.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.1-src.zip.asc">Apache.NMS-1.5.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2739 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.1-bin.zip">Apache.NMS-1.5.1-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.1-bin.zip.asc">Apache.NMS-1.5.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2739 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.1-src.zip">Apache.NMS-1.5.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.1-src.zip.asc">Apache.NMS-1.5.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2739 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.1-bin.zip">Apache.NMS-1.5.1-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS-1.5.1-bin.zip.asc">Apache.NMS-1.5.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2739 </p></td></tr></tbody></table>
-<h2 id="Apache.NMSAPIv1.5.1-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b1ae45ba-0213-4d45-8c14-e4dab0b14997" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.5.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMSAPIv1.5.1-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
diff --git a/nms/apachenms-api-v160.xml b/nms/apachenms-api-v160.xml
index d29ff36..bfb7d36 100644
--- a/nms/apachenms-api-v160.xml
+++ b/nms/apachenms-api-v160.xml
@@ -1,5 +1,3 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSAPIv1.6.0-NewandNoteworthy">New and Noteworthy</h2><p>This is a major release of the NMS API which adds some new APIs and fixes some minor bugs in the NMS API libraries common code.</p><ul><li>Added Recover method to ISession.</li><li>Added new events to ISession for Transaction begin, commit and rollback.</li><li>Added method in IConnection to purge created Temp Destinations.</li></ul><h2 id="Apache.NMSAPIv1.6.0-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMSAPIv1.6.0-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS-1.6.0-src.zip">Apache.NMS-1.6.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS-1.6.0-src.zip.asc">Apache.NMS-1.6.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.0.3061</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS-1.6.0-bin.zip">Apache.NMS-1.6.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS-1.6.0-bin.zip.asc">Apache.NMS-1.6.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.0.3061</p></td></tr></tbody></table></div><h2 id="Apache.NMSAPIv1.6.0-SVNTagCheckout">SVN Tag Checkout</h2><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.6.0/
-]]></script>
-</div></div><h2 id="Apache.NMSAPIv1.6.0-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315987">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a major release of the NMS API which adds some new APIs and fixes some minor bugs in the NMS API libraries common code.</p><ul><li>Added Recover method to ISession.</li><li>Added new events to ISession for Transaction begin, commit and rollback.</li><li>Added method in IConnection to purge created Temp Destinations.</li></ul><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS-1.6.0-src.zip">Apache.NMS-1.6.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS-1.6.0-src.zip.asc">Apache.NMS-1.6.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.0.3061</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS-1.6.0-bin.zip">Apache.NMS-1.6.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS-1.6.0-bin.zip.asc">Apache.NMS-1.6.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.0.3061</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="1911ad64-f0bd-43ab-b79d-e629c766c841" ac:name="code" ac:schema-version="1"><plain-text-body>svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.6.0/
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315987">release notes</a></p></div>
diff --git a/nms/apachenms-api-v170.xml b/nms/apachenms-api-v170.xml
index 6876459..80639a8 100644
--- a/nms/apachenms-api-v170.xml
+++ b/nms/apachenms-api-v170.xml
@@ -1,5 +1,3 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSAPIv1.7.0-NewandNoteworthy">New and Noteworthy</h2><p>This is a major release of the NMS API which adds some new APIs and fixes some minor bugs in the NMS API libraries common code.</p><ul><li>Added IDisposable as a base of IDestination.</li><li>Added some improvements to the Unit tests framework.</li><li>Added some new provider names (AMQP and MQTT) to allow for future clients.</li></ul><h2 id="Apache.NMSAPIv1.7.0-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMSAPIv1.7.0-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.0-src.zip">Apache.NMS-1.7.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.0-src.zip.asc">Apache.NMS-1.7.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.0.3635</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.0-bin.zip">Apache.NMS-1.7.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.0-bin.zip.asc">Apache.NMS-1.7.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.0.3635</p></td></tr></tbody></table></div><h2 id="Apache.NMSAPIv1.7.0-SVNTagCheckout">SVN Tag Checkout</h2><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.7.0/
-]]></script>
-</div></div><h2 id="Apache.NMSAPIv1.7.0-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12325350">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a major release of the NMS API which adds some new APIs and fixes some minor bugs in the NMS API libraries common code.</p><ul><li>Added IDisposable as a base of IDestination.</li><li>Added some improvements to the Unit tests framework.</li><li>Added some new provider names (AMQP and MQTT) to allow for future clients.</li></ul><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.0-src.zip">Apache.NMS-1.7.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.0-src.zip.asc">Apache.NMS-1.7.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.0.3635</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.0-bin.zip">Apache.NMS-1.7.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.0-bin.zip.asc">Apache.NMS-1.7.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.0.3635</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="63401cb5-f4c9-47cf-85b1-ab4adbfae2a7" ac:name="code" ac:schema-version="1"><plain-text-body>svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.7.0/
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12325350">release notes</a></p></div>
diff --git a/nms/apachenms-api-v171.xml b/nms/apachenms-api-v171.xml
index 5d77e8d..a4f3830 100644
--- a/nms/apachenms-api-v171.xml
+++ b/nms/apachenms-api-v171.xml
@@ -1,5 +1,3 @@
-<div class="wiki-content maincontent"><p> </p><h2 id="Apache.NMSAPIv1.7.1-NewandNoteworthy">New and Noteworthy</h2><p>This is a minor release of the NMS API which adds a few minor fixes for NMS Providers operating in MSDTC Transactions.</p><h2 id="Apache.NMSAPIv1.7.1-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMSAPIv1.7.1-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS-1.7.1-src.zip">Apache.NMS-1.7.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.1-src.zip.asc">Apache.NMS-1.7.1-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.1.3894</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS-1.7.1-bin.zip">Apache.NMS-1.7.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.1-bin.zip.asc">Apache.NMS-1.7.1-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.1.3894</p></td></tr></tbody></table></div><h2 id="Apache.NMSAPIv1.7.1-SVNTagCheckout">SVN Tag Checkout</h2><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.7.1/
-]]></script>
-</div></div><h2 id="Apache.NMSAPIv1.7.1-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12329541">release notes</a></p></div>
+<div class="wiki-content maincontent"><p> </p><h2>New and Noteworthy</h2><p>This is a minor release of the NMS API which adds a few minor fixes for NMS Providers operating in MSDTC Transactions.</p><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS-1.7.1-src.zip">Apache.NMS-1.7.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.1-src.zip.asc">Apache.NMS-1.7.1-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.1.3894</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS-1.7.1-bin.zip">Apache.NMS-1.7.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS-1.7.1-bin.zip.asc">Apache.NMS-1.7.1-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.1.3894</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="72fda2de-7cfb-4e9e-8d42-6ebf0acc3336" ac:name="code" ac:schema-version="1"><plain-text-body>svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS/tags/1.7.1/
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12329541">release notes</a></p></div>
diff --git a/nms/apachenms-ems-v110.xml b/nms/apachenms-ems-v110.xml
index a61478a..17d5ef7 100644
--- a/nms/apachenms-ems-v110.xml
+++ b/nms/apachenms-ems-v110.xml
@@ -1,7 +1,3 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSEMSv1.1.0-NewandNoteworthy">New and Noteworthy</h2><p>The 1.1.0 release is a major milestone for the Apache NMS EMS client. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release:</p><ul><li>Improved API Documentation.</li><li>Many bug fixes.</li></ul><p> </p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Support TIBCO EMS 4.1.0 and above.</p>
-</div></div><h2 id="Apache.NMSEMSv1.1.0-API">API</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMSEMSv1.1.0-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.EMS Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-src.zip">Apache.NMS.EMS-1.1.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-src.zip.asc">Apache.NMS.EMS-1.1.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.1.0.1642</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.EMS Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-bin.zip">Apache.NMS.EMS-1.1.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-bin.zip.asc">Apache.NMS.EMS-1.1.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.1.0.1642</p></td></tr></tbody></table></div><p><strong><em>NOTE:</em></strong> <em>In order to use the</em> <strong>Apache.NMS.EMS</strong> <em>project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application.</em></p><h2 id="Apache.NMSEMSv1.1.0-SVNTagCheckout">SVN Tag Checkout</h2><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co https://svn.apache.org/repos/asf/activemq/activemq-net/Apache.NMS.EMS/tags/1.1.0/
-]]></script>
-</div></div><h2 id="Apache.NMSEMSv1.1.0-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>The 1.1.0 release is a major milestone for the Apache NMS EMS client. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release:</p><ul><li>Improved API Documentation.</li><li>Many bug fixes.</li></ul><p> </p><structured-macro ac:macro-id="f83129f9-cc84-4ca0-9979-e412598d215e" ac:name="panel" ac:schema-version="1"><rich-text-body><p><strong>NOTE:</strong> Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro><h2>API</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><td colspan="1" rowspan="1"><p>Apache.NMS.EMS Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-src.zip">Apache.NMS.EMS-1.1.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-src.zip.asc">Apache.NMS.EMS-1.1.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.1.0.1642</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.EMS Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-bin.zip">Apache.NMS.EMS-1.1.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.EMS-1.1.0-bin.zip.asc">Apache.NMS.EMS-1.1.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.1.0.1642</p></td></tr></tbody></table><p><strong><em>NOTE:</em></strong> <em>In order to use the</em> <strong>Apache.NMS.EMS</strong> <em>project files, you will need to provide your own copy of the TIBCO.EMS.dll, as this is a licensed 3rd Party application.</em></p><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="ceb1874b-fac0-45fc-987f-27b1e4b72c88" ac:name="code" ac:schema-version="1"><plain-text-body>svn co https://svn.apache.org/repos/asf/activemq/activemq-net/Apache.NMS.EMS/tags/1.1.0/
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
diff --git a/nms/apachenms-msmq-v110.xml b/nms/apachenms-msmq-v110.xml
index 2a06683..177454a 100644
--- a/nms/apachenms-msmq-v110.xml
+++ b/nms/apachenms-msmq-v110.xml
@@ -1,28 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMSMSMQv1.1.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>The 1.1.0 release is a major milestone for the Apache NMS MSMQ client. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release:</p>
<ul><li>Improved API Documentation.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMSMSMQv1.1.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMSMSMQv1.1.0-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-src.zip">Apache.NMS.MSMQ-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-src.zip.asc">Apache.NMS.MSMQ-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-bin.zip">Apache.NMS.MSMQ-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-bin.zip.asc">Apache.NMS.MSMQ-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.1.0.1642 </p></td></tr></tbody></table></div>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-src.zip">Apache.NMS.MSMQ-1.1.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-src.zip.asc">Apache.NMS.MSMQ-1.1.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.MSMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-bin.zip">Apache.NMS.MSMQ-1.1.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.1.0/Apache.NMS.MSMQ-1.1.0-bin.zip.asc">Apache.NMS.MSMQ-1.1.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.1.0.1642 </p></td></tr></tbody></table>
-<h2 id="Apache.NMSMSMQv1.1.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e1471b74-3cde-4879-9a74-5b21acf45a7d" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-net/Apache.NMS.MSMQ/tags/1.1.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMSMSMQv1.1.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
diff --git a/nms/apachenms.xml b/nms/apachenms.xml
index b631d6c..f83d058 100644
--- a/nms/apachenms.xml
+++ b/nms/apachenms.xml
@@ -1,14 +1,14 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS-AnOverviewofNMS">An Overview of NMS</h2>
+<div class="wiki-content maincontent"><h2>An Overview of NMS</h2>
-<p>The <a shape="rect" href="nms-api.xml">NMS API</a> (<em>.Net Message Service API</em>) providers a standard .NET interface to Messaging Systems. There could be multiple implementations to different <a shape="rect" href="nms-providers.xml">providers</a> (including MSMQ). The NMS API This allows you to build .NET applications in C#, VB, or any other .NET language, using a single API to connect to multiple different providers using a JMS style API. </p>
+<p>The <link><page ri:content-title="NMS API"></page><link-body>NMS API</link-body></link> (<em>.Net Message Service API</em>) providers a standard .NET interface to Messaging Systems. There could be multiple implementations to different <link><page ri:content-title="NMS Providers"></page><link-body>providers</link-body></link> (including MSMQ). The NMS API This allows you to build .NET applications in C#, VB, or any other .NET language, using a single API to connect to multiple different providers using a JMS style API. </p>
<p>NMS API currently supports all of the features of JMS in a simple pure C# API and implementation apart from XA. Current features include</p>
<ul><li>creating & disposing of connections, sessions, producers, consumers</li><li>sending of messages to topics, queues with durable or non durable along with temporary destination support</li><li>synchronous consuming (blocking receive, receive with no wait or receive with a timeout)</li><li>asynchronous consuming (adding a MessageListener to be dispatched in the thread pool)</li><li>message header support along with custom properties</li><li>Text, Bytes, Stream and Map message support</li><li>support for transactions (sending and acknowledging multiple messages in an atomic transaction)</li><li>redelivery of messages in rollbacks up to some configured maximum redelivery count</li><li>Optional Queue browser interface for providers that can support it.</li><li>Optional .NET Distributed Transaction Support for providers that can support that.</li></ul>
-<p>A provider implementation based on a pure C# implementation of <a shape="rect" class="external-link" href="http://activemq.apache.org/openwire.html">OpenWire</a> is provided for working with the Apache ActiveMQ broker.  There are other <a shape="rect" href="nms-providers.xml">provider implementations</a> for working with Stomp, TIBCO, Microsoft Message Queue (MSMQ), and Windows Communication Foundation (WCF).</p>
+<p>A provider implementation based on a pure C# implementation of <a shape="rect" href="http://activemq.apache.org/openwire.html">OpenWire</a> is provided for working with the Apache ActiveMQ broker.  There are other <link><page ri:content-title="NMS Providers"></page><link-body>provider implementations</link-body></link> for working with Stomp, TIBCO, Microsoft Message Queue (MSMQ), and Windows Communication Foundation (WCF).</p>
-<p>If you are curious you can browse the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/">source code and tests</a> for the entire project or download an <a shape="rect" href="nms-providers.xml">NMS Provider</a>. </p>
+<p>If you are curious you can browse the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/">source code and tests</a> for the entire project or download an <link><page ri:content-title="NMS Providers"></page><link-body>NMS Provider</link-body></link>. </p>
-<ul class="childpages-macro"><li><a shape="rect" href="nms-api.xml">NMS API</a></li><li><a shape="rect" href="nms-api-downloads.xml">NMS API Downloads</a></li><li><a shape="rect" href="nms-examples.xml">NMS Examples</a></li><li><a shape="rect" href="nms-faq.xml">NMS FAQ</a></li><li><a shape="rect" href="nms-providers.xml">NMS Providers</a></li><li><a shape="rect" href="nms-uri-configuration.xml">NMS URI Configuration</a></li></ul></div>
+<structured-macro ac:macro-id="22dcc8c7-0ee3-4e3b-8723-ddc87e10b401" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/apachenmsactivemq-v120.xml b/nms/apachenmsactivemq-v120.xml
index df0b5d2..b3837cd 100644
--- a/nms/apachenmsactivemq-v120.xml
+++ b/nms/apachenmsactivemq-v120.xml
@@ -1,29 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.2.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS ActiveMQ library and fixes several bugs found in the 1.1.0 release.  Some highlights for this release.</p>
<ul><li>Addition of ConnectionMeteData to the Connection API.</li><li>Addition of QueueBrowser to the Session API.</li><li>Addition of an Individual Acknowledge Mode.</li><li>Improvements to the Failover Transport.</li><li>Improved API Documentation.</li><li>New IStreamMessage interface.</li><li>New IRedeliveryPolicy interface.</li><li>Expanded IByteMessage interface to read/write primitive types.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMS.ActiveMQv1.2.0-Apache.NMSActiveMQDownloads">Apache.NMS ActiveMQ Downloads</h2>
+<h2>Apache.NMS ActiveMQ Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-src.zip">Apache.NMS.ActiveMQ-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-src.zip.asc">Apache.NMS.ActiveMQ-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1864 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-bin.zip">Apache.NMS.ActiveMQ-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1864 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-src.zip">Apache.NMS.ActiveMQ-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-src.zip.asc">Apache.NMS.ActiveMQ-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1864 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-bin.zip">Apache.NMS.ActiveMQ-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.ActiveMQ-1.2.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1864 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p>
-</div></div>
+<structured-macro ac:macro-id="93b18be0-4102-4744-bbec-a6090d3a370b" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.2.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="68a04028-c5ca-453c-91e5-8bd4c0d0c009" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.2.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.2.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11815">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11815">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v130.xml b/nms/apachenmsactivemq-v130.xml
index 8baf42c..b94ad3f 100644
--- a/nms/apachenmsactivemq-v130.xml
+++ b/nms/apachenmsactivemq-v130.xml
@@ -1,29 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.3.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS ActiveMQ library and fixes several bugs found in the 1.2.0 release.  Some highlights for this release.</p>
<ul><li>Addition of QueueBrowser support</li><li>Addition of SSL Support</li><li>Improvements to the Failover Transport.</li><li>Improved API Documentation.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMS.ActiveMQv1.3.0-Apache.NMSClientDownloads">Apache.NMS Client Downloads</h2>
+<h2>Apache.NMS Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-src.zip">Apache.NMS.ActiveMQ-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-src.zip.asc">Apache.NMS.ActiveMQ-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1965 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-bin.zip">Apache.NMS.ActiveMQ-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1965 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-src.zip">Apache.NMS.ActiveMQ-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-src.zip.asc">Apache.NMS.ActiveMQ-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1965 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-bin.zip">Apache.NMS.ActiveMQ-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.ActiveMQ-1.3.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1965 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p>
-</div></div>
+<structured-macro ac:macro-id="88c87cc7-4218-4a08-aaf5-a14649681e00" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.3.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2db3a8f1-1cd7-4ef7-b7ab-7549c440a5f4" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.ActiveMQ/tags/1.3.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.3.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12150">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12150">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v140.xml b/nms/apachenmsactivemq-v140.xml
index cbb1053..af32969 100644
--- a/nms/apachenmsactivemq-v140.xml
+++ b/nms/apachenmsactivemq-v140.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.4.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS ActiveMQ library and fixes several bugs found in the 1.3.0 release.  Some highlights for this release.</p>
<ul><li>Improved URI handling in all NMS clients.</li><li>Improved handling of Request Timeout settings.</li><li>Added a new SetBytes method to IMapMessage.</li><li>Added a new MessageTransformer API.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMS.ActiveMQv1.4.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.4.0-Apache.NMSClientDownloads">Apache.NMS Client Downloads</h2>
+<h2>Apache.NMS Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.0-src.zip">Apache.NMS.ActiveMQ-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.0-src.zip.asc">Apache.NMS.ActiveMQ-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2098 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.0-bin.zip">Apache.NMS.ActiveMQ-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2098 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.0-src.zip">Apache.NMS.ActiveMQ-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.0-src.zip.asc">Apache.NMS.ActiveMQ-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2098 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.0-bin.zip">Apache.NMS.ActiveMQ-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2098 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p>
-</div></div>
+<structured-macro ac:macro-id="8810311f-fae4-4856-8da1-5364f5566c4d" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.4.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3458c3b3-053b-4a1d-9b8b-317955e11e53" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.4.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.4.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v141.xml b/nms/apachenmsactivemq-v141.xml
index 5da0bdf..1cefd84 100644
--- a/nms/apachenmsactivemq-v141.xml
+++ b/nms/apachenmsactivemq-v141.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.4.1-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS.ActiveMQ library and fixes several bugs found in the 1.3.0 release.  Some highlights for this release.</p>
<ul><li>Improved URI handling.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMS.ActiveMQv1.4.1-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.4.1-Apache.NMS.ActiveMQClientDownloads">Apache.NMS.ActiveMQ Client Downloads</h2>
+<h2>Apache.NMS.ActiveMQ Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-src.zip">Apache.NMS.ActiveMQ-1.4.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-src.zip.asc">Apache.NMS.ActiveMQ-1.4.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.1.2098 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-bin.zip">Apache.NMS.ActiveMQ-1.4.1-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.4.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.1.2098 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-src.zip">Apache.NMS.ActiveMQ-1.4.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-src.zip.asc">Apache.NMS.ActiveMQ-1.4.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.1.2098 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-bin.zip">Apache.NMS.ActiveMQ-1.4.1-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.ActiveMQ-1.4.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.4.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.1.2098 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p>
-</div></div>
+<structured-macro ac:macro-id="48054765-fbd5-40a8-b6fd-6be15425c087" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.4.1-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3fbd2081-bd0d-44ee-85ef-041f18beb4e4" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.4.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.4.1-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v150.xml b/nms/apachenmsactivemq-v150.xml
index a63ec5d..4d68ae2 100644
--- a/nms/apachenmsactivemq-v150.xml
+++ b/nms/apachenmsactivemq-v150.xml
@@ -1,35 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.5.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS ActiveMQ library and fixes several bugs found in the 1.4.0 release.</p>
-<h5 id="Apache.NMS.ActiveMQv1.5.0-Newinthisversion">New in this version</h5>
+<h5>New in this version</h5>
<ul><li>New startupMaxReconnectAttempts option in the failover transport.</li><li>Fixed a memory leak in the Inactivity Monitoring code.</li><li>Fixed a bug that could cause the Failover to not work.</li><li>Fixed a bug that caused SSL Certs to not be loaded in some cases.</li><li>Several other bugfixes for issues found since v1.4.0 was released.</li><li>Added support for participation in .NET Distributed Transactions (MSDTC).</li><li>Added .NET 4.0 build.</li><li>Many more fixes and internal improvements.</li></ul>
-<h2 id="Apache.NMS.ActiveMQv1.5.0-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.5.0-Apache.NMS.ActiveMQClientDownloads">Apache.NMS.ActiveMQ Client Downloads</h2>
+<h2>Apache.NMS.ActiveMQ Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-src.zip">Apache.NMS.ActiveMQ-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-src.zip.asc">Apache.NMS.ActiveMQ-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2235 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-bin.zip">Apache.NMS.ActiveMQ-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2235 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-src.zip">Apache.NMS.ActiveMQ-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-src.zip.asc">Apache.NMS.ActiveMQ-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2235 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-bin.zip">Apache.NMS.ActiveMQ-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2235 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p>
-</div></div>
+<structured-macro ac:macro-id="9d23db77-af1a-42d8-9db3-b4cb20578f80" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.5.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="fa3da16c-c64f-459e-a405-d8729fe2f28e" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.5.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.5.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v151.xml b/nms/apachenmsactivemq-v151.xml
index fbe215e..f44b754 100644
--- a/nms/apachenmsactivemq-v151.xml
+++ b/nms/apachenmsactivemq-v151.xml
@@ -1,30 +1,28 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.5.1-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS.ActiveMQ API.</p>
-<h5 id="Apache.NMS.ActiveMQv1.5.1-NMSAPIUpdates">NMS API Updates</h5>
+<h5>NMS API Updates</h5>
<ul><li>Many fixes for the MS Distributed Transaction support along with other minor bug fixes for issues found since the initial v1.5.0 release.</li></ul>
-<h2 id="Apache.NMS.ActiveMQv1.5.1-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.5.1-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.1-src.zip">Apache.NMS.ActiveMQ-1.5.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.1-src.zip.asc">Apache.NMS.ActiveMQ-1.5.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2341 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.1-bin.zip">Apache.NMS.ActiveMQ-1.5.1-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2341 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.1-src.zip">Apache.NMS.ActiveMQ-1.5.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.1-src.zip.asc">Apache.NMS.ActiveMQ-1.5.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2341 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.1-bin.zip">Apache.NMS.ActiveMQ-1.5.1-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2341 </p></td></tr></tbody></table>
-<h2 id="Apache.NMS.ActiveMQv1.5.1-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e49f390e-2d8f-4034-a4a6-1359b80f60f0" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.5.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.5.1-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315986">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315986">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v152.xml b/nms/apachenmsactivemq-v152.xml
index 8c05186..82c16d9 100644
--- a/nms/apachenmsactivemq-v152.xml
+++ b/nms/apachenmsactivemq-v152.xml
@@ -1,29 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.5.2-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new fixes to the NMS.ActiveMQ API.</p>
-<h5 id="Apache.NMS.ActiveMQv1.5.2-NMS.ActiveMQUpdates">NMS.ActiveMQ Updates</h5>
+<h5>NMS.ActiveMQ Updates</h5>
<p>This release focuses on performance and stability fixes to the ActiveMQ provider. No new features were added in this release. See the release notes below for a list of issues that were fixed in this release.</p>
-<h2 id="Apache.NMS.ActiveMQv1.5.2-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.5.2-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.2-src.zip">Apache.NMS.ActiveMQ-1.5.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.2-src.zip.asc">Apache.NMS.ActiveMQ-1.5.2-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.2.2508 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.2-bin.zip">Apache.NMS.ActiveMQ-1.5.2-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.2-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.2-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.2.2508 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.2-src.zip">Apache.NMS.ActiveMQ-1.5.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.2-src.zip.asc">Apache.NMS.ActiveMQ-1.5.2-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.2.2508 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.2-bin.zip">Apache.NMS.ActiveMQ-1.5.2-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.2-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.2-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.2.2508 </p></td></tr></tbody></table>
-<h2 id="Apache.NMS.ActiveMQv1.5.2-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="26359d2e-4e0f-4174-b53c-bc92ba8be547" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.5.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.5.2-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12316156">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12316156">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v153.xml b/nms/apachenmsactivemq-v153.xml
index 99e64e2..9754e4d 100644
--- a/nms/apachenmsactivemq-v153.xml
+++ b/nms/apachenmsactivemq-v153.xml
@@ -1,29 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.5.3-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new fixes to the NMS.ActiveMQ API.</p>
-<h5 id="Apache.NMS.ActiveMQv1.5.3-NMS.ActiveMQUpdates">NMS.ActiveMQ Updates</h5>
+<h5>NMS.ActiveMQ Updates</h5>
<p>This release focuses on stability fixes to the ActiveMQ provider. No new features were added in this release. See the release notes below for a list of issues that were fixed in this release.</p>
-<h2 id="Apache.NMS.ActiveMQv1.5.3-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.5.3-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.3-src.zip">Apache.NMS.ActiveMQ-1.5.3-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.3-src.zip.asc">Apache.NMS.ActiveMQ-1.5.3-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.3.2578 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.3-bin.zip">Apache.NMS.ActiveMQ-1.5.3-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.3-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.3-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.3.2578 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.3-src.zip">Apache.NMS.ActiveMQ-1.5.3-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.3-src.zip.asc">Apache.NMS.ActiveMQ-1.5.3-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.3.2578 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.3-bin.zip">Apache.NMS.ActiveMQ-1.5.3-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.3-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.3-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.3.2578 </p></td></tr></tbody></table>
-<h2 id="Apache.NMS.ActiveMQv1.5.3-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3125dc4a-99b7-47b4-bc22-aafa01a1d5d1" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.5.3/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.5.3-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12319084">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12319084">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v154.xml b/nms/apachenmsactivemq-v154.xml
index ea3edac..c660d32 100644
--- a/nms/apachenmsactivemq-v154.xml
+++ b/nms/apachenmsactivemq-v154.xml
@@ -1,29 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.5.4-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new fixes to the NMS.ActiveMQ API.</p>
-<h5 id="Apache.NMS.ActiveMQv1.5.4-NMS.ActiveMQUpdates">NMS.ActiveMQ Updates</h5>
+<h5>NMS.ActiveMQ Updates</h5>
<p>This release focuses on stability fixes to the ActiveMQ provider. No new features were added in this release. See the release notes below for a list of issues that were fixed in this release.</p>
-<h2 id="Apache.NMS.ActiveMQv1.5.4-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.5.4-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.4-src.zip">Apache.NMS.ActiveMQ-1.5.4-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.4-src.zip.asc">Apache.NMS.ActiveMQ-1.5.4-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.4.2655 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.4-bin.zip">Apache.NMS.ActiveMQ-1.5.4-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.4-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.4-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.4.2655 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.4-src.zip">Apache.NMS.ActiveMQ-1.5.4-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.4-src.zip.asc">Apache.NMS.ActiveMQ-1.5.4-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.4.2655 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.4-bin.zip">Apache.NMS.ActiveMQ-1.5.4-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.4-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.4-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.4.2655 </p></td></tr></tbody></table>
-<h2 id="Apache.NMS.ActiveMQv1.5.4-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5ec66a57-8dcf-4068-84df-354e64f0140c" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.5.4/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.5.4-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12319545">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12319545">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v155.xml b/nms/apachenmsactivemq-v155.xml
index cf54a95..5a2e2f2 100644
--- a/nms/apachenmsactivemq-v155.xml
+++ b/nms/apachenmsactivemq-v155.xml
@@ -1,32 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.5.5-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new fixes to the NMS.ActiveMQ API.</p>
<ul><li>Sending to non-existent temp queue causes consumer to shutdown</li><li>Consumers frequently fail to reconnect after broker outage/failover.</li><li>FailoverTransport doesn't trigger a reconnect on send of a Tracked Command.</li><li>ActiveMQ.NMS hangs sometimes due to concurrency problems while accessing static IDictionary</li><li>Apache.NMS.ActiveMQ discovery protocol throwing ArgumentOutOfRangeException</li></ul>
-<h5 id="Apache.NMS.ActiveMQv1.5.5-NMS.ActiveMQUpdates">NMS.ActiveMQ Updates</h5>
+<h5>NMS.ActiveMQ Updates</h5>
<p>This release focuses on stability fixes to the ActiveMQ provider. No new features were added in this release. See the release notes below for a list of issues that were fixed in this release.</p>
-<h2 id="Apache.NMS.ActiveMQv1.5.5-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.5.5-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.5-src.zip">Apache.NMS.ActiveMQ-1.5.5-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.5-src.zip.asc">Apache.NMS.ActiveMQ-1.5.5-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.5.2676 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.5-bin.zip">Apache.NMS.ActiveMQ-1.5.5-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.5-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.5-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.5.2676 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.5-src.zip">Apache.NMS.ActiveMQ-1.5.5-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.5-src.zip.asc">Apache.NMS.ActiveMQ-1.5.5-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.5.2676 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.5-bin.zip">Apache.NMS.ActiveMQ-1.5.5-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.5-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.5-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.5.2676 </p></td></tr></tbody></table>
-<h2 id="Apache.NMS.ActiveMQv1.5.5-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="16bc477c-5a09-432c-9801-0548a65371ee" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.5.5/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.5.5-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12320740">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12320740">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v156.xml b/nms/apachenmsactivemq-v156.xml
index 727a110..1a9916d 100644
--- a/nms/apachenmsactivemq-v156.xml
+++ b/nms/apachenmsactivemq-v156.xml
@@ -1,32 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.5.6-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new fixes to the NMS.ActiveMQ API.</p>
<ul><li>Adds compression support to the ObjectMessage payload</li><li>Fixes an issue in Message marshaling when tight-marshaling is enabled.</li></ul>
-<h5 id="Apache.NMS.ActiveMQv1.5.6-NMS.ActiveMQUpdates">NMS.ActiveMQ Updates</h5>
+<h5>NMS.ActiveMQ Updates</h5>
<p>This release focuses on stability fixes to the ActiveMQ provider. No new features were added in this release. See the release notes below for a list of issues that were fixed in this release.</p>
-<h2 id="Apache.NMS.ActiveMQv1.5.6-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.5.6-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.6-src.zip">Apache.NMS.ActiveMQ-1.5.6-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.6-src.zip.asc">Apache.NMS.ActiveMQ-1.5.6-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.6.2746 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.6-bin.zip">Apache.NMS.ActiveMQ-1.5.6-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.6-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.6-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.6.2746 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.6-src.zip">Apache.NMS.ActiveMQ-1.5.6-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.6-src.zip.asc">Apache.NMS.ActiveMQ-1.5.6-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.6.2746 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.6-bin.zip">Apache.NMS.ActiveMQ-1.5.6-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.ActiveMQ-1.5.6-bin.zip.asc">Apache.NMS.ActiveMQ-1.5.6-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.6.2746 </p></td></tr></tbody></table>
-<h2 id="Apache.NMS.ActiveMQv1.5.6-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="367b042d-e690-46c2-9051-fddfd6d9d880" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.5.6/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.5.6-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12321250">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12321250">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v160.xml b/nms/apachenmsactivemq-v160.xml
index 7767a40..fad2b67 100644
--- a/nms/apachenmsactivemq-v160.xml
+++ b/nms/apachenmsactivemq-v160.xml
@@ -1,32 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.6.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features and fixes to the NMS.ActiveMQ API.</p>
-<h5 id="Apache.NMS.ActiveMQv1.6.0-NMS.ActiveMQUpdates">NMS.ActiveMQ Updates</h5>
+<h5>NMS.ActiveMQ Updates</h5>
<p>This release adds several new features to the ActiveMQ client and fixes many bugs that have been reported since the last release.</p>
<ul><li>Adds support for non-blocking redelivery.</li><li>Supports priority backups for Failover transport.</li><li>Supports an Optimized Ack mode for MessageConsumers.</li><li>Adds Message Audits to prevent duplicate deliveries on Failover.</li><li>Implements the ISession Recover method.</li><li>Adds support for purging locally created temp destinations.</li><li>Properly handles cluster client re-balancing in Failover Transport.</li><li>Plus a lot more fixes and stability improvements.</li></ul>
-<h2 id="Apache.NMS.ActiveMQv1.6.0-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.ActiveMQv1.6.0-DownloadHere">Download Here</h2>
+<h2>Download Here</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.0-src.zip">Apache.NMS.ActiveMQ-1.6.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.0-src.zip.asc">Apache.NMS.ActiveMQ-1.6.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.6.0.3072 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.0-bin.zip">Apache.NMS.ActiveMQ-1.6.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.6.0.3072 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.0-src.zip">Apache.NMS.ActiveMQ-1.6.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.0-src.zip.asc">Apache.NMS.ActiveMQ-1.6.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.6.0.3072 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.ActiveMQ Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.0-bin.zip">Apache.NMS.ActiveMQ-1.6.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.6.0.3072 </p></td></tr></tbody></table>
-<h2 id="Apache.NMS.ActiveMQv1.6.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="ced857b2-8839-4aa8-b9f2-90fdbf1280ad" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.ActiveMQv1.6.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315987">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315987">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v161.xml b/nms/apachenmsactivemq-v161.xml
index 20fbee8..2eb1065 100644
--- a/nms/apachenmsactivemq-v161.xml
+++ b/nms/apachenmsactivemq-v161.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.6.1-NewandNoteworthy">New and Noteworthy</h2><p>This is a bugfix release for the NMS.ActiveMQ client library. Along with some bug fixes though we've also added support for better discovery transport agents and we now support HTTP discovery using the ActiveMQ broker's HTTP discovery registry.</p><h5 id="Apache.NMS.ActiveMQv1.6.1-NMS.ActiveMQUpdates">NMS.ActiveMQ Updates</h5><p>The change log for this release is below.</p><ul><li>Don't fire transport interrupted event when no resume is possible</li><li>dispatch paused, waiting for outstanding dispatch interruption processing to complete..</li><li>Better logging for XATransaction</li><li>Improve the discovery transport to be more robust and allow easier plugin of new agents.</li><li>Add an HTTP based discovery agent to the discovery transport feature.</li><li>Individual Acknowledgement seems not working in NMS</li></ul><h2 id="Apache.NMS.ActiveMQv1.6.1-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.ActiveMQv1.6.1-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.1-src.zip">Apache.NMS.ActiveMQ-1.6.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.1-src.zip.asc">Apache.NMS.ActiveMQ-1.6.1-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.0.3208</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.1-bin.zip">Apache.NMS.ActiveMQ-1.6.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.1-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.0.3208</p></td></tr></tbody></table></div><h2 id="Apache.NMS.ActiveMQv1.6.1-SVNTagCheckout">SVN Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.1/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.1/</a></p>
-</div></div><h2 id="Apache.NMS.ActiveMQv1.6.1-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12324792">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a bugfix release for the NMS.ActiveMQ client library. Along with some bug fixes though we've also added support for better discovery transport agents and we now support HTTP discovery using the ActiveMQ broker's HTTP discovery registry.</p><h5>NMS.ActiveMQ Updates</h5><p>The change log for this release is below.</p><ul><li>Don't fire transport interrupted event when no resume is possible</li><li>dispatch paused, waiting for outstanding dispatch interruption processing to complete..</li><li>Better logging for XATransaction</li><li>Improve the discovery transport to be more robust and allow easier plugin of new agents.</li><li>Add an HTTP based discovery agent to the discovery transport feature.</li><li>Individual Acknowledgement seems not working in NMS</li></ul><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.1-src.zip">Apache.NMS.ActiveMQ-1.6.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.1-src.zip.asc">Apache.NMS.ActiveMQ-1.6.1-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.0.3208</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.1-bin.zip">Apache.NMS.ActiveMQ-1.6.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.1-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.0.3208</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="8415d517-8d7b-4675-9ace-731a5469c5ef" ac:name="panel" ac:schema-version="1"><rich-text-body><p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.1/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.1/</a></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12324792">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v162.xml b/nms/apachenmsactivemq-v162.xml
index ccc4eac..6c5fd41 100644
--- a/nms/apachenmsactivemq-v162.xml
+++ b/nms/apachenmsactivemq-v162.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><p> </p><h2 id="Apache.NMS.ActiveMQv1.6.2-NewandNoteworthy">New and Noteworthy</h2><p>This is a bugfix release for the NMS.ActiveMQ client library. Along with some bug fixes though we've also added support for better discovery transport agents and we now support HTTP discovery using the ActiveMQ broker's HTTP discovery registry.</p><h5 id="Apache.NMS.ActiveMQv1.6.2-NMS.ActiveMQUpdates">NMS.ActiveMQ Updates</h5><p>This release addresses some issue in the DTC support and a fix for long delays while closing a Connection. </p><h2 id="Apache.NMS.ActiveMQv1.6.2-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.ActiveMQv1.6.2-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.2-src.zip">Apache.NMS.ActiveMQ-1.6.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.2-src.zip.asc">Apache.NMS.ActiveMQ-1.6.2-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.0.3271</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.2-bin.zip">Apache.NMS.ActiveMQ-1.6.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.2-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.2-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.0.3271</p></td></tr></tbody></table></div><h2 id="Apache.NMS.ActiveMQv1.6.2-SVNTagCheckout">SVN Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.2/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.2/</a></p>
-</div></div><h2 id="Apache.NMS.ActiveMQv1.6.2-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12325306">release notes</a></p></div>
+<div class="wiki-content maincontent"><p> </p><h2>New and Noteworthy</h2><p>This is a bugfix release for the NMS.ActiveMQ client library. Along with some bug fixes though we've also added support for better discovery transport agents and we now support HTTP discovery using the ActiveMQ broker's HTTP discovery registry.</p><h5>NMS.ActiveMQ Updates</h5><p>This release addresses some issue in the DTC support and a fix for long delays while closing a Connection. </p><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.2-src.zip">Apache.NMS.ActiveMQ-1.6.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.2-src.zip.asc">Apache.NMS.ActiveMQ-1.6.2-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.0.3271</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.2-bin.zip">Apache.NMS.ActiveMQ-1.6.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.2-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.2-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.0.3271</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="9a8d394c-5bda-45a3-9f35-f81ba65ee9b4" ac:name="panel" ac:schema-version="1"><rich-text-body><p>svn co <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.2/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.2/</a></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12325306">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v163.xml b/nms/apachenmsactivemq-v163.xml
index aee075b..1d032a3 100644
--- a/nms/apachenmsactivemq-v163.xml
+++ b/nms/apachenmsactivemq-v163.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.6.3-NewandNoteworthy">New and Noteworthy</h2><p>This is a bugfix release that addresses a few stability issues and improves the handling of Message Consumer instances that operate inside of Sessions in Transacted mode.</p><h2 id="Apache.NMS.ActiveMQv1.6.3-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.ActiveMQv1.6.3-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.3-src.zip">Apache.NMS.ActiveMQ-1.6.3-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.3-src.zip.asc">Apache.NMS.ActiveMQ-1.6.3-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.3.3483</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.3-bin.zip">Apache.NMS.ActiveMQ-1.6.3-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.3-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.3-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.3.3483</p></td></tr></tbody></table></div><h2 id="Apache.NMS.ActiveMQv1.6.3-SVNTagCheckout">SVN Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.3/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.3/</a></p>
-</div></div><h2 id="Apache.NMS.ActiveMQv1.6.3-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12325840">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a bugfix release that addresses a few stability issues and improves the handling of Message Consumer instances that operate inside of Sessions in Transacted mode.</p><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.3-src.zip">Apache.NMS.ActiveMQ-1.6.3-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.3-src.zip.asc">Apache.NMS.ActiveMQ-1.6.3-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.3.3483</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.3-bin.zip">Apache.NMS.ActiveMQ-1.6.3-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.3-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.3-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.3.3483</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="432ff941-955c-4dc4-9b6d-66176f9c7d5e" ac:name="panel" ac:schema-version="1"><rich-text-body><p>svn co <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.3/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.3/</a></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12325840">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v164.xml b/nms/apachenmsactivemq-v164.xml
index 30db783..01d9890 100644
--- a/nms/apachenmsactivemq-v164.xml
+++ b/nms/apachenmsactivemq-v164.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.6.4-NewandNoteworthy">New and Noteworthy</h2><p>This is a bugfix release that addresses a few stability issues and improves the handling of Message Consumer instances that operate inside of Sessions in Transacted mode as well as some fixes for potential deadlocks that could occur during failover connection recovery.</p><h2 id="Apache.NMS.ActiveMQv1.6.4-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.ActiveMQv1.6.4-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.4-src.zip">Apache.NMS.ActiveMQ-1.6.4-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.4-src.zip.asc">Apache.NMS.ActiveMQ-1.6.4-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.4.3531</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.4-bin.zip">Apache.NMS.ActiveMQ-1.6.4-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.4-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.4-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.4.3531</p></td></tr></tbody></table></div><h2 id="Apache.NMS.ActiveMQv1.6.4-SVNTagCheckout">SVN Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.4/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.4/</a></p>
-</div></div><h2 id="Apache.NMS.ActiveMQv1.6.4-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12327446">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a bugfix release that addresses a few stability issues and improves the handling of Message Consumer instances that operate inside of Sessions in Transacted mode as well as some fixes for potential deadlocks that could occur during failover connection recovery.</p><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.4-src.zip">Apache.NMS.ActiveMQ-1.6.4-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.4-src.zip.asc">Apache.NMS.ActiveMQ-1.6.4-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.4.3531</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.4-bin.zip">Apache.NMS.ActiveMQ-1.6.4-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.4-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.4-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.4.3531</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="5fd01f71-d571-4992-b9c0-63fea109a71f" ac:name="panel" ac:schema-version="1"><rich-text-body><p>svn co <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.4/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.4/</a></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12327446">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v165.xml b/nms/apachenmsactivemq-v165.xml
index e606081..d669545 100644
--- a/nms/apachenmsactivemq-v165.xml
+++ b/nms/apachenmsactivemq-v165.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.6.5-NewandNoteworthy">New and Noteworthy</h2><p>This is a small bugfix release that corrects an issue found in the OpenWire tight marshal code that can cause a connection to fail, also a fix for an incorrect redelivery count on some messages was applied.</p><h2 id="Apache.NMS.ActiveMQv1.6.5-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.ActiveMQv1.6.5-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.5-src.zip">Apache.NMS.ActiveMQ-1.6.5-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.5-src.zip.asc">Apache.NMS.ActiveMQ-1.6.5-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.5.3684</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.5-bin.zip">Apache.NMS.ActiveMQ-1.6.5-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.5-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.5-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.6.5.3684</p></td></tr></tbody></table></div><h2 id="Apache.NMS.ActiveMQv1.6.5-SVNTagCheckout">SVN Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.4/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.5/</a></p>
-</div></div><h2 id="Apache.NMS.ActiveMQv1.6.5-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12329150">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a small bugfix release that corrects an issue found in the OpenWire tight marshal code that can cause a connection to fail, also a fix for an incorrect redelivery count on some messages was applied.</p><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.5-src.zip">Apache.NMS.ActiveMQ-1.6.5-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.5-src.zip.asc">Apache.NMS.ActiveMQ-1.6.5-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.5.3684</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.5-bin.zip">Apache.NMS.ActiveMQ-1.6.5-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.6.0/Apache.NMS.ActiveMQ-1.6.5-bin.zip.asc">Apache.NMS.ActiveMQ-1.6.5-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.6.5.3684</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="f29accd1-b510-4a22-8a72-f3e7c680a15d" ac:name="panel" ac:schema-version="1"><rich-text-body><p>svn co <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.4/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.6.5/</a></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12329150">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v170.xml b/nms/apachenmsactivemq-v170.xml
index 9bf5561..90d9f6c 100644
--- a/nms/apachenmsactivemq-v170.xml
+++ b/nms/apachenmsactivemq-v170.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.7.0-NewandNoteworthy">New and Noteworthy</h2><p>This is the first release of the Apache.NMS.ActiveMQ 1.7.0 line.  This release is based on the Apache.NMS API v1.7.0 and includes several fixes and updates over the 1.6.x line.  The DotNetZlib dependency has been updated to the latest release and the Destination types now implement IDisposable for use in using blocks.  For full release details check out the release notes.</p><h2 id="Apache.NMS.ActiveMQv1.7.0-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.ActiveMQv1.7.0-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.0-src.zip">Apache.NMS.ActiveMQ-1.7.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.0-src.zip.asc">Apache.NMS.ActiveMQ-1.7.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.0.3660</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.0-bin.zip">Apache.NMS.ActiveMQ-1.7.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.7.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.0.3660</p></td></tr></tbody></table></div><h2 id="Apache.NMS.ActiveMQv1.7.0-SVNTagCheckout">SVN Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.0/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.0/</a></p>
-</div></div><h2 id="Apache.NMS.ActiveMQv1.7.0-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12325350">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is the first release of the Apache.NMS.ActiveMQ 1.7.0 line.  This release is based on the Apache.NMS API v1.7.0 and includes several fixes and updates over the 1.6.x line.  The DotNetZlib dependency has been updated to the latest release and the Destination types now implement IDisposable for use in using blocks.  For full release details check out the release notes.</p><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.0-src.zip">Apache.NMS.ActiveMQ-1.7.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.0-src.zip.asc">Apache.NMS.ActiveMQ-1.7.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.0.3660</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.0-bin.zip">Apache.NMS.ActiveMQ-1.7.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.0-bin.zip.asc">Apache.NMS.ActiveMQ-1.7.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.0.3660</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="be81e835-32bd-4370-aea9-1fb97d32eb56" ac:name="panel" ac:schema-version="1"><rich-text-body><p>svn co <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.0/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.0/</a></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12325350">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v171.xml b/nms/apachenmsactivemq-v171.xml
index 5b08ac3..73cad60 100644
--- a/nms/apachenmsactivemq-v171.xml
+++ b/nms/apachenmsactivemq-v171.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.7.1-NewandNoteworthy">New and Noteworthy</h2><p>This is a bugfix release of the Apache.NMS.ActiveMQ 1.7.x line.  This release is based on the Apache.NMS API v1.7.1 and includes several fixes and updates over the 1.7.0 release.  A fix for an issue where the client could falsely filtered a message as a duplicate included along with improvements to the QueueBrowser to prevent it filtering expired messages.  Several other issues were fixed and can be seen in the release notes.</p><h2 id="Apache.NMS.ActiveMQv1.7.1-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.ActiveMQv1.7.1-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.1-src.zip">Apache.NMS.ActiveMQ-1.7.1-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.1-src.zip.asc">Apache.NMS.ActiveMQ-1.7.1-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.1.3924</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.1-bin.zip">Apache.NMS.ActiveMQ-1.7.1-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.7.1-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.1.3924</p></td></tr></tbody></table></div><h2 id="Apache.NMS.ActiveMQv1.7.1-SVNTagCheckout">SVN Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.1/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.1/</a></p>
-</div></div><h2 id="Apache.NMS.ActiveMQv1.7.1-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12329541">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a bugfix release of the Apache.NMS.ActiveMQ 1.7.x line.  This release is based on the Apache.NMS API v1.7.1 and includes several fixes and updates over the 1.7.0 release.  A fix for an issue where the client could falsely filtered a message as a duplicate included along with improvements to the QueueBrowser to prevent it filtering expired messages.  Several other issues were fixed and can be seen in the release notes.</p><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.1-src.zip">Apache.NMS.ActiveMQ-1.7.1-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.1-src.zip.asc">Apache.NMS.ActiveMQ-1.7.1-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.1.3924</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.1-bin.zip">Apache.NMS.ActiveMQ-1.7.1-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="https://archive.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.1-bin.zip.asc">Apache.NMS.ActiveMQ-1.7.1-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.1.3924</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="be81e835-32bd-4370-aea9-1fb97d32eb56" ac:name="panel" ac:schema-version="1"><rich-text-body><p>svn co <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.1/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.1/</a></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12329541">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq-v172.xml b/nms/apachenmsactivemq-v172.xml
index 5a33cda..6f1f963 100644
--- a/nms/apachenmsactivemq-v172.xml
+++ b/nms/apachenmsactivemq-v172.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.ActiveMQv1.7.2-NewandNoteworthy">New and Noteworthy</h2><p>This is a bugfix release of the Apache.NMS.ActiveMQ 1.7.x line.  This release is based on the Apache.NMS API v1.7.1 and includes several fixes and updates over the 1.7.1 release. </p><h2 id="Apache.NMS.ActiveMQv1.7.2-APIDocumentation">API Documentation</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.ActiveMQv1.7.2-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.2-src.zip">Apache.NMS.ActiveMQ-1.7.2-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.2-src.zip.asc">Apache.NMS.ActiveMQ-1.7.2-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.2.4108</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.2-bin.zip">Apache.NMS.ActiveMQ-1.7.2-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.2-bin.zip.asc">Apache.NMS.ActiveMQ-1.7.2-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.7.2.4108</p></td></tr></tbody></table></div><h2 id="Apache.NMS.ActiveMQv1.7.2-SVNTagCheckout">SVN Tag Checkout</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.2/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.2/</a></p>
-</div></div><h2 id="Apache.NMS.ActiveMQv1.7.2-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12332993">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>This is a bugfix release of the Apache.NMS.ActiveMQ 1.7.x line.  This release is based on the Apache.NMS API v1.7.1 and includes several fixes and updates over the 1.7.1 release. </p><h2>API Documentation</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.2-src.zip">Apache.NMS.ActiveMQ-1.7.2-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.2-src.zip.asc">Apache.NMS.ActiveMQ-1.7.2-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.2.4108</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.ActiveMQ Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dyn/closer.lua/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.2-bin.zip">Apache.NMS.ActiveMQ-1.7.2-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.apache.org/dist/activemq/apache-nms/1.7.0/Apache.NMS.ActiveMQ-1.7.2-bin.zip.asc">Apache.NMS.ActiveMQ-1.7.2-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.7.2.4108</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="be81e835-32bd-4370-aea9-1fb97d32eb56" ac:name="panel" ac:schema-version="1"><rich-text-body><p>svn co <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.2/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.ActiveMQ/tags/1.7.2/</a></p></rich-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12332993">release notes</a></p></div>
diff --git a/nms/apachenmsactivemq.xml b/nms/apachenmsactivemq.xml
index 5a5745c..c09f367 100644
--- a/nms/apachenmsactivemq.xml
+++ b/nms/apachenmsactivemq.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ NMS client is a .NET client that communicates with the ActiveMQ broker using its native <a shape="rect" href="../openwire.xml">Openwire</a> protocol. This client supports <a shape="rect" href="activemq-advanced-features.xml">advanced features</a> such as Failover, Discovery, SSL, and Message Compression. This section of the NMS site provides documentation specific to the NMS.ActiveMQ client, for documentation on the other NMS clients refer to the Main <a shape="rect" href="index.xml">NMS page</a>.</p>
+<div class="wiki-content maincontent"><p>The ActiveMQ NMS client is a .NET client that communicates with the ActiveMQ broker using its native <link><page ri:content-title="OpenWire" ri:space-key="ACTIVEMQ"></page><link-body>Openwire</link-body></link> protocol. This client supports <link><page ri:content-title="ActiveMQ Advanced Features"></page><link-body>advanced features</link-body></link> such as Failover, Discovery, SSL, and Message Compression. This section of the NMS site provides documentation specific to the NMS.ActiveMQ client, for documentation on the other NMS clients refer to the Main <link><page ri:content-title="Index"></page><link-body>NMS page</link-body></link>.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="activemq-advanced-features.xml">ActiveMQ Advanced Features</a></li><li><a shape="rect" href="activemq-build-notes.xml">ActiveMQ Build Notes</a></li><li><a shape="rect" href="activemq-downloads.xml">ActiveMQ Downloads</a></li><li><a shape="rect" href="activemq-examples.xml">ActiveMQ Examples</a></li><li><a shape="rect" href="activemq-faq.xml">ActiveMQ FAQ</a></li><li><a shape="rect" href="activemq-uri-configuration.xml">ActiveMQ URI Configuration</a></li></ul></div>
+<structured-macro ac:macro-id="eac80b6d-fb19-4d4d-8beb-ac641295d459" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/apachenmsamqp.xml b/nms/apachenmsamqp.xml
index 7245bc4..af9b8df 100644
--- a/nms/apachenmsamqp.xml
+++ b/nms/apachenmsamqp.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The Apache NMS AMQP client provides an NMS layer on top of the Apache Qpid messaging client API. AMQP 1.0 support is provided by Apache Qpid Proton.</p><ul><li><a shape="rect" href="amqp-build-notes.xml">AMQP Build Notes</a></li><li><a shape="rect" href="amqp-downloads.xml">AMQP Downloads</a></li><li><a shape="rect" href="amqp-examples.xml">AMQP Examples</a></li><li><a shape="rect" href="amqp-faq.xml">AMQP FAQ</a></li></ul><p> </p><p> </p></div>
+<div class="wiki-content maincontent"><p>The Apache NMS AMQP client provides an NMS layer on top of the Apache Qpid messaging client API. AMQP 1.0 support is provided by Apache Qpid Proton.</p><ul><li><link><page ri:content-title="AMQP Build Notes"></page></link></li><li><link><page ri:content-title="AMQP Downloads"></page></link></li><li><link><page ri:content-title="AMQP Examples"></page></link></li><li><link><page ri:content-title="AMQP FAQ"></page></link></li></ul><p> </p><p> </p></div>
diff --git a/nms/apachenmsems.xml b/nms/apachenmsems.xml
index 9c94e79..e4f4d6e 100644
--- a/nms/apachenmsems.xml
+++ b/nms/apachenmsems.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>The Apache.NMS.EMS client provider for talking to TIBCO's EMS message broker. To use this, you will need to following TIBCO's licensing requirements to acquire the TIBCO client assembly DLL. NMS does not ship with the TIBCO client assembly.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="ems-build-notes.xml">EMS Build Notes</a></li><li><a shape="rect" href="ems-downloads.xml">EMS Downloads</a></li><li><a shape="rect" href="ems-examples.xml">EMS Examples</a></li><li><a shape="rect" href="ems-faq.xml">EMS FAQ</a></li></ul></div>
+<structured-macro ac:macro-id="5c40882b-6626-4591-986a-165a301c5b3d" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/apachenmsmqtt.xml b/nms/apachenmsmqtt.xml
index b38bac1..0b27ea9 100644
--- a/nms/apachenmsmqtt.xml
+++ b/nms/apachenmsmqtt.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The Apache.NMS.MQTT client provider for using the publish-subscribe pattern over a lightweight protocol on top of TCP/IP.</p><p></p></div>
+<div class="wiki-content maincontent"><p>The Apache.NMS.MQTT client provider for using the publish-subscribe pattern over a lightweight protocol on top of TCP/IP.</p><p><structured-macro ac:macro-id="5c40882b-6626-4591-986a-165a301c5b3d" ac:name="children" ac:schema-version="1"></structured-macro></p></div>
diff --git a/nms/apachenmsmsmq.xml b/nms/apachenmsmsmq.xml
index 6c30c94..c5c216c 100644
--- a/nms/apachenmsmsmq.xml
+++ b/nms/apachenmsmsmq.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>The Apache.NMS.MSMQ client provides an NMS layer on top of the MSMQ messaging API.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="msmq-build-notes.xml">MSMQ Build Notes</a></li><li><a shape="rect" href="msmq-downloads.xml">MSMQ Downloads</a></li><li><a shape="rect" href="msmq-examples.xml">MSMQ Examples</a></li><li><a shape="rect" href="msmq-faq.xml">MSMQ FAQ</a></li></ul></div>
+<structured-macro ac:macro-id="fdedc697-244d-4f1d-b064-9cbad06e05f9" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/apachenmsstomp-v120.xml b/nms/apachenmsstomp-v120.xml
index b956a89..81d73d5 100644
--- a/nms/apachenmsstomp-v120.xml
+++ b/nms/apachenmsstomp-v120.xml
@@ -1,30 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.Stompv1.2.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This is the first official release of the NMS Stomp client library. This library implements much of the NMS API although some features aren't possible due to limitations in the Stomp protocol.</p>
-<h2 id="Apache.NMS.Stompv1.2.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.Stompv1.2.0-Apache.NMS.StompDownloads">Apache.NMS.Stomp Downloads</h2>
+<h2>Apache.NMS.Stomp Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-src.zip">Apache.NMS.Stomp-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-src.zip.asc">Apache.NMS.Stomp-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1858 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-bin.zip">Apache.NMS.Stomp-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-bin.zip.asc">Apache.NMS.Stomp-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.2.0.1858 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-src.zip">Apache.NMS.Stomp-1.2.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-src.zip.asc">Apache.NMS.Stomp-1.2.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1858 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-bin.zip">Apache.NMS.Stomp-1.2.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.2.0/Apache.NMS.Stomp-1.2.0-bin.zip.asc">Apache.NMS.Stomp-1.2.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.2.0.1858 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p>
-</div></div>
+<structured-macro ac:macro-id="722b7e96-e6a6-4b64-a7d3-95da8f865900" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.2.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6313e913-5ca4-45b2-88d6-4e77c70bc1d3" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.2.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.2.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11815">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11815">release notes</a></p></div>
diff --git a/nms/apachenmsstomp-v130.xml b/nms/apachenmsstomp-v130.xml
index d8bbe63..ce82929 100644
--- a/nms/apachenmsstomp-v130.xml
+++ b/nms/apachenmsstomp-v130.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.Stompv1.3.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS Stomp library and fixes several bugs found in the 1.2.0 release.  Some highlights for this release.</p>
<ul><li>Addition of SSL Support</li><li>Improvements to the Failover Transport.</li><li>Improved API Documentation.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMS.Stompv1.3.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.Stompv1.3.0-Apache.NMS.StompDownloads">Apache.NMS.Stomp Downloads</h2>
+<h2>Apache.NMS.Stomp Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-src.zip">Apache.NMS.Stomp-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-src.zip.asc">Apache.NMS.Stomp-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1969 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-bin.zip">Apache.NMS.Stomp-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-bin.zip.asc">Apache.NMS.Stomp-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.3.0.1969 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-src.zip">Apache.NMS.Stomp-1.3.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-src.zip.asc">Apache.NMS.Stomp-1.3.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1969 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-bin.zip">Apache.NMS.Stomp-1.3.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.3.0/Apache.NMS.Stomp-1.3.0-bin.zip.asc">Apache.NMS.Stomp-1.3.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.3.0.1969 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p>
-</div></div>
+<structured-macro ac:macro-id="0b97a49a-8435-4f40-bdd4-685800e420a3" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.3.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d4aa9975-2578-45f8-b6ce-89fcb7984d0e" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.3.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.3.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12150">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12150">release notes</a></p></div>
diff --git a/nms/apachenmsstomp-v140.xml b/nms/apachenmsstomp-v140.xml
index 7b6f671..46d80a0 100644
--- a/nms/apachenmsstomp-v140.xml
+++ b/nms/apachenmsstomp-v140.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.Stompv1.4.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS Stomp library and fixes several bugs found in the 1.3.0 release.  Some highlights for this release.</p>
<ul><li>Improved URI handling in all NMS clients.</li><li>Improved handling of Request Timeout settings.</li><li>Added a new SetBytes method to IMapMessage.</li><li>Many new Unit Tests added to the Test Suite.</li><li>Many bug fixes.</li></ul>
-<h2 id="Apache.NMS.Stompv1.4.0-API">API</h2>
+<h2>API</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.Stompv1.4.0-Apache.NMS.StompDownloads">Apache.NMS.Stomp Downloads</h2>
+<h2>Apache.NMS.Stomp Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-src.zip">Apache.NMS.Stomp-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-src.zip.asc">Apache.NMS.Stomp-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2077 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-bin.zip">Apache.NMS.Stomp-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-bin.zip.asc">Apache.NMS.Stomp-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.4.0.2077 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-src.zip">Apache.NMS.Stomp-1.4.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-src.zip.asc">Apache.NMS.Stomp-1.4.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2077 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-bin.zip">Apache.NMS.Stomp-1.4.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.4.0/Apache.NMS.Stomp-1.4.0-bin.zip.asc">Apache.NMS.Stomp-1.4.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.4.0.2077 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p>
-</div></div>
+<structured-macro ac:macro-id="fa15fa42-ff9d-41a7-b2a1-581866e71b64" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.4.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d5915b65-5248-48cc-8800-6597f5726982" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.4.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.4.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=12188">release notes</a></p></div>
diff --git a/nms/apachenmsstomp-v150.xml b/nms/apachenmsstomp-v150.xml
index 08b6f1d..59f9ac1 100644
--- a/nms/apachenmsstomp-v150.xml
+++ b/nms/apachenmsstomp-v150.xml
@@ -1,33 +1,30 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.Stompv1.5.0-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS Stomp client library and fixes several bugs found in the 1.4.0 release.</p>
-<h6 id="Apache.NMS.Stompv1.5.0-Newinthisrelease:">New in this release:</h6>
+<h6>New in this release:</h6>
<ul><li>Support for the current changes in the Stomp 1.1 draft specification.</li><li>Improved Inactivity Monitoring with two way heartbeats when used with a Stomp v1.1 broker.</li><li>New startupMaxReconnectAttempts option in the failover transport.</li><li>Several other bugfixes for issues found since v1.4.0 was released.</li></ul>
-<h2 id="Apache.NMS.Stompv1.5.0-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.Stompv1.5.0-Apache.NMS.StompDownloads">Apache.NMS.Stomp Downloads</h2>
+<h2>Apache.NMS.Stomp Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.0-src.zip">Apache.NMS.Stomp-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.0-src.zip.asc">Apache.NMS.Stomp-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.0.2216 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip">Apache.NMS.Stomp-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.0-bin.zip.asc">Apache.NMS.Stomp-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2216 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.0-src.zip">Apache.NMS.Stomp-1.5.0-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.0-src.zip.asc">Apache.NMS.Stomp-1.5.0-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.0.2216 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip">Apache.NMS.Stomp-1.5.0-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.0-bin.zip.asc">Apache.NMS.Stomp-1.5.0-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2216 </p></td></tr></tbody></table>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p>
-</div></div>
+<structured-macro ac:macro-id="164e52c6-2765-40d2-94e3-1bcc9c58d65e" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.0-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="55c1a7db-629a-4051-bba2-f7233ec7e9fe" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.5.0/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.0-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
diff --git a/nms/apachenmsstomp-v151.xml b/nms/apachenmsstomp-v151.xml
index 74c62be..5f9cbe2 100644
--- a/nms/apachenmsstomp-v151.xml
+++ b/nms/apachenmsstomp-v151.xml
@@ -1,35 +1,32 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.Stompv1.5.1-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.4.0 release.  Some highlights for this release.</p>
-<h5 id="Apache.NMS.Stompv1.5.1-Newinthisrelease.">New in this release.</h5>
+<h5>New in this release.</h5>
<ul><li>Fixed a memory leak in the Inactivity Monitoring code.</li><li>Fixed a bug that could cause the Failover to not work.</li><li>Fixed a bug that caused SSL Certs to not be loaded in some cases.</li><li>Fixed a bug that was causing major performance issues for synchronous consumers.</li><li>Fixed issues found with the Stomp v1.1 support.</li></ul>
-<h2 id="Apache.NMS.Stompv1.5.1-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.Stompv1.5.1-Apache.NMS.StompClientDownloads">Apache.NMS.Stomp Client Downloads</h2>
+<h2>Apache.NMS.Stomp Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-src.zip">Apache.NMS.Stomp-1.5.1-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-src.zip.asc">Apache.NMS.Stomp-1.5.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2216 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip">Apache.NMS.Stomp-1.5.1-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip.asc">Apache.NMS.Stomp-1.5.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.1.2216 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-src.zip">Apache.NMS.Stomp-1.5.1-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-src.zip.asc">Apache.NMS.Stomp-1.5.1-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2216 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip">Apache.NMS.Stomp-1.5.1-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.1-bin.zip.asc">Apache.NMS.Stomp-1.5.1-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.1.2216 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p>
-</div></div>
+<structured-macro ac:macro-id="e1a3d617-029e-499e-aa4d-e8a7a748d411" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. Support TIBCO EMS 4.1.0 and above.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.1-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="edbb0ca8-b929-42c2-a99f-7c073569e352" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.5.1/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.1-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12315640">release notes</a></p></div>
diff --git a/nms/apachenmsstomp-v152.xml b/nms/apachenmsstomp-v152.xml
index d761dc2..731cd03 100644
--- a/nms/apachenmsstomp-v152.xml
+++ b/nms/apachenmsstomp-v152.xml
@@ -1,30 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.Stompv1.5.2-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>The release focuses on performance and stability fixes for issues found in the 1.5.1 release as well as addressing a compatibility issue found when connecting to Stomp v1.1 compliant brokers. </p>
-<h2 id="Apache.NMS.Stompv1.5.2-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.Stompv1.5.2-Apache.NMS.StompClientDownloads">Apache.NMS.Stomp Client Downloads</h2>
+<h2>Apache.NMS.Stomp Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.2-src.zip">Apache.NMS.Stomp-1.5.2-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.2-src.zip.asc">Apache.NMS.Stomp-1.5.2-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.2.2508 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.2-bin.zip">Apache.NMS.Stomp-1.5.2-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.2-bin.zip.asc">Apache.NMS.Stomp-1.5.2-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.2.2508 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.2-src.zip">Apache.NMS.Stomp-1.5.2-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.2-src.zip.asc">Apache.NMS.Stomp-1.5.2-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.2.2508 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.2-bin.zip">Apache.NMS.Stomp-1.5.2-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.2-bin.zip.asc">Apache.NMS.Stomp-1.5.2-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.2.2508 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. As well as with most Stomp v1.0 and v1.1 compliant messaging brokers.</p>
-</div></div>
+<structured-macro ac:macro-id="1076d4f8-9c47-4f66-acd1-70164cb29dfb" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. As well as with most Stomp v1.0 and v1.1 compliant messaging brokers.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.2-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6d9acfc9-2262-4382-9eab-0cb30b17ba58" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.5.2/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.2-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12316156">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12316156">release notes</a></p></div>
diff --git a/nms/apachenmsstomp-v153.xml b/nms/apachenmsstomp-v153.xml
index 1ef2b3d..07c9dc4 100644
--- a/nms/apachenmsstomp-v153.xml
+++ b/nms/apachenmsstomp-v153.xml
@@ -1,30 +1,27 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.Stompv1.5.3-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>The release focuses on performance and stability fixes for issues found in the 1.5.2 release as well as addressing a compatibility issue found when connecting to Stomp v1.1 compliant brokers. Additionally some improvements in fail-over handling and connection shut-down have been made. </p>
-<h2 id="Apache.NMS.Stompv1.5.3-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.Stompv1.5.3-Apache.NMS.StompClientDownloads">Apache.NMS.Stomp Client Downloads</h2>
+<h2>Apache.NMS.Stomp Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.3-src.zip">Apache.NMS.Stomp-1.5.3-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.3-src.zip.asc">Apache.NMS.Stomp-1.5.3-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.3.2795 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.3-bin.zip">Apache.NMS.Stomp-1.5.3-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.3-bin.zip.asc">Apache.NMS.Stomp-1.5.3-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.2.2795 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.3-src.zip">Apache.NMS.Stomp-1.5.3-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.3-src.zip.asc">Apache.NMS.Stomp-1.5.3-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.3.2795 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.3-bin.zip">Apache.NMS.Stomp-1.5.3-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.3-bin.zip.asc">Apache.NMS.Stomp-1.5.3-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.2.2795 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. As well as with most Stomp v1.0 and v1.1 compliant messaging brokers.</p>
-</div></div>
+<structured-macro ac:macro-id="5e592eb4-94a2-4647-83fc-7872efd8956b" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. As well as with most Stomp v1.0 and v1.1 compliant messaging brokers.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.3-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="62ee82d4-be40-4edc-8ae7-755efa52058f" ac:name="code" ac:schema-version="1"><plain-text-body>
svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.5.3/
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.3-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12319084">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&styleName=Html&version=12319084">release notes</a></p></div>
diff --git a/nms/apachenmsstomp-v154.xml b/nms/apachenmsstomp-v154.xml
index e8303e7..b4c69ab 100644
--- a/nms/apachenmsstomp-v154.xml
+++ b/nms/apachenmsstomp-v154.xml
@@ -1,28 +1,26 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.Stompv1.5.4-NewandNoteworthy">New and Noteworthy</h2>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2>
<p>The release includes a fix for exceptions that were being seen on Windows OS's configured with Non-US culture settings.</p>
-<h2 id="Apache.NMS.Stompv1.5.4-APIDocumentation">API Documentation</h2>
+<h2>API Documentation</h2>
-<p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p>
+<p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><link-body>here</link-body></link></p>
-<h2 id="Apache.NMS.Stompv1.5.4-Apache.NMS.StompClientDownloads">Apache.NMS.Stomp Client Downloads</h2>
+<h2>Apache.NMS.Stomp Client Downloads</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Download Link </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> PGP Signature File </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.4-src.zip">Apache.NMS.Stomp-1.5.4-src.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.4-src.zip.asc">Apache.NMS.Stomp-1.5.4-src.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.4.3215 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.4-bin.zip">Apache.NMS.Stomp-1.5.4-bin.zip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.4-bin.zip.asc">Apache.NMS.Stomp-1.5.4-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5.4.3215 </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Download Link </p></th><th colspan="1" rowspan="1"><p> PGP Signature File </p></th><th colspan="1" rowspan="1"><p> Version </p></th></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Source code </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.4-src.zip">Apache.NMS.Stomp-1.5.4-src.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.4-src.zip.asc">Apache.NMS.Stomp-1.5.4-src.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.4.3215 </p></td></tr><tr><td colspan="1" rowspan="1"><p> Apache.NMS.Stomp Binary Assemblies </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.4-bin.zip">Apache.NMS.Stomp-1.5.4-bin.zip</a> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.apache.org/dyn/closer.cgi/activemq/apache-nms/1.5.0/Apache.NMS.Stomp-1.5.4-bin.zip.asc">Apache.NMS.Stomp-1.5.4-bin.zip.asc</a> </p></td><td colspan="1" rowspan="1"><p> 1.5.4.3215 </p></td></tr></tbody></table>
<p><br clear="none" class="atl-forced-newline"></p>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. As well as with most Stomp v1.0 and v1.1 compliant messaging brokers.</p>
-</div></div>
+<structured-macro ac:macro-id="64c69a25-b1ca-441c-af47-df2abecab4f0" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p><strong>NOTE:</strong> Compatible with ActiveMQ Broker versions in the 4.X and 5.X family. As well as with most Stomp v1.0 and v1.1 compliant messaging brokers.</p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.4-SVNTagCheckout">SVN Tag Checkout</h2>
+<h2>SVN Tag Checkout</h2>
-<div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.5.4/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.5.4/</a></p>
-</div></div>
+<structured-macro ac:macro-id="06f5ea70-ac81-4fb2-90f2-16f233948a6a" ac:name="panel" ac:schema-version="1"><rich-text-body>
+<p>svn co <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.5.4/">https://svn.apache.org/repos/asf/activemq/activemq-dotnet/Apache.NMS.Stomp/tags/1.5.4/</a></p></rich-text-body></structured-macro>
-<h2 id="Apache.NMS.Stompv1.5.4-Changelog">Changelog</h2>
+<h2>Changelog</h2>
-<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12319545">release notes</a></p></div>
+<p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311201&version=12319545">release notes</a></p></div>
diff --git a/nms/apachenmsstomp.xml b/nms/apachenmsstomp.xml
index 3edb5f8..d1b18e7 100644
--- a/nms/apachenmsstomp.xml
+++ b/nms/apachenmsstomp.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>The NMS Stomp client is a small lightweight .NET client that can send and receive messages from any <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> based message broker. The NMS Stomp client currently supports the Stomp 1.0 protocol specification. </p>
+<div class="wiki-content maincontent"><p>The NMS Stomp client is a small lightweight .NET client that can send and receive messages from any <a shape="rect" href="http://stomp.codehaus.org/">Stomp</a> based message broker. The NMS Stomp client currently supports the Stomp 1.0 protocol specification. </p>
-<ul class="childpages-macro"><li><a shape="rect" href="stomp-advanced-features.xml">Stomp Advanced Features</a></li><li><a shape="rect" href="stomp-build-notes.xml">Stomp Build Notes</a></li><li><a shape="rect" href="stomp-downloads.xml">Stomp Downloads</a></li><li><a shape="rect" href="stomp-faq.xml">Stomp FAQ</a></li><li><a shape="rect" href="stomp-uri-configuration.xml">Stomp URI Configuration</a></li></ul></div>
+<structured-macro ac:macro-id="0877d63b-767f-4b92-b1b1-57522007a199" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/apachenmswcf-v110.xml b/nms/apachenmswcf-v110.xml
index 3239c75..13158d4 100644
--- a/nms/apachenmswcf-v110.xml
+++ b/nms/apachenmswcf-v110.xml
@@ -1,5 +1,3 @@
-<div class="wiki-content maincontent"><h2 id="Apache.NMS.WCFv1.1.0-NewandNoteworthy">New and Noteworthy</h2><p>The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS project, and all provider implementation projects.</p><h2 id="Apache.NMS.WCFv1.1.0-API">API</h2><p>Refer to the API for this release <a shape="rect" href="nms-api.xml">here</a></p><h2 id="Apache.NMS.WCFv1.1.0-DownloadHere">Download Here</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Download Link</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>PGP Signature File</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.WCF Source code</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-src.zip">Apache.NMS.WCF-1.1.0-src.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-src.zip.asc">Apache.NMS.WCF-1.1.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.1.0.1642</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache.NMS.WCF Binary Assemblies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-bin.zip">Apache.NMS.WCF-1.1.0-bin.zip</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-bin.zip.asc">Apache.NMS.WCF-1.1.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1.1.0.1642</p></td></tr></tbody></table></div><h2 id="Apache.NMS.WCFv1.1.0-SVNTagCheckout">SVN Tag Checkout</h2><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[svn co https://svn.apache.org/repos/asf/activemq/activemq-net/Apache.NMS.WCF/tags/1.1.0/
-]]></script>
-</div></div><h2 id="Apache.NMS.WCFv1.1.0-Changelog">Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
+<div class="wiki-content maincontent"><h2>New and Noteworthy</h2><p>The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS project, and all provider implementation projects.</p><h2>API</h2><p>Refer to the API for this release <link><page ri:content-title="NMS API"></page><plain-text-link-body>here</plain-text-link-body></link></p><h2>Download Here</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Download Link</p></th><th colspan="1" rowspan="1"><p>PGP Signature File</p></th><th colspan="1" rowspan="1"><p>Version</p></th></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.WCF Source code</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-src.zip">Apache.NMS.WCF-1.1.0-src.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-src.zip.asc">Apache.NMS.WCF-1.1.0-src.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.1.0.1642</p></td></tr><tr><td colspan="1" rowspan="1"><p>Apache.NMS.WCF Binary Assemblies</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-bin.zip">Apache.NMS.WCF-1.1.0-bin.zip</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://archive.apache.org/dist/activemq/apache-nms/1.1.0/Apache.NMS.WCF-1.1.0-bin.zip.asc">Apache.NMS.WCF-1.1.0-bin.zip.asc</a></p></td><td colspan="1" rowspan="1"><p>1.1.0.1642</p></td></tr></tbody></table><h2>SVN Tag Checkout</h2><structured-macro ac:macro-id="f028c0e7-3167-46f1-ba92-daf79741b48c" ac:name="code" ac:schema-version="1"><plain-text-body>svn co https://svn.apache.org/repos/asf/activemq/activemq-net/Apache.NMS.WCF/tags/1.1.0/
+</plain-text-body></structured-macro><h2>Changelog</h2><p>For a more detailed view of new features and bug fixes, see the <a shape="rect" href="https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=11010&styleName=Html&version=11814">release notes</a></p></div>
diff --git a/nms/apachenmswcf.xml b/nms/apachenmswcf.xml
index ca543cb..dd3b3b8 100644
--- a/nms/apachenmswcf.xml
+++ b/nms/apachenmswcf.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>NMS provider for use with the Windows Communication Framework (WCF).</p>
-<ul class="childpages-macro"><li><a shape="rect" href="wcf-downloads.xml">WCF Downloads</a></li><li><a shape="rect" href="wcf-examples.xml">WCF Examples</a></li></ul></div>
+<structured-macro ac:macro-id="af3b786b-dcdf-469f-b3a0-e48ba34824a0" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/apachenmsxms.xml b/nms/apachenmsxms.xml
index 28ae2a3..7d46d92 100644
--- a/nms/apachenmsxms.xml
+++ b/nms/apachenmsxms.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The Apache.NMS.XMS client provider for talking to IBM's WebSphere MQ Series message broker. To use this, you will need to following IBM's licensing requirements to acquire the MQSeries client assembly DLL. NMS does not ship with the MQSeries client assembly.</p><p></p></div>
+<div class="wiki-content maincontent"><p>The Apache.NMS.XMS client provider for talking to IBM's WebSphere MQ Series message broker. To use this, you will need to following IBM's licensing requirements to acquire the MQSeries client assembly DLL. NMS does not ship with the MQSeries client assembly.</p><p><structured-macro ac:macro-id="5c40882b-6626-4591-986a-165a301c5b3d" ac:name="children" ac:schema-version="1"></structured-macro></p></div>
diff --git a/nms/are-there-more-faq-entries.xml b/nms/are-there-more-faq-entries.xml
index c0751ef..23ef201 100644
--- a/nms/are-there-more-faq-entries.xml
+++ b/nms/are-there-more-faq-entries.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="AretheremoreFAQEntries-AretheremoreFAQEntries?">Are there more FAQ Entries?</h2>
+<div class="wiki-content maincontent"><h2>Are there more FAQ Entries?</h2>
-<p>Yes, see the <a shape="rect" class="external-link" href="http://activemq.apache.org/faq.html">ActiveMQ Main FAQ</a></p></div>
+<p>Yes, see the <a shape="rect" href="http://activemq.apache.org/faq.html">ActiveMQ Main FAQ</a></p></div>
diff --git a/nms/articles.xml b/nms/articles.xml
index fb4ce22..440d8fb 100644
--- a/nms/articles.xml
+++ b/nms/articles.xml
@@ -1,10 +1,11 @@
-<div class="wiki-content maincontent"><h2 id="Articles-ArticlesthatcovervariousNMSrelatedtopics.">Articles that cover various NMS related topics.</h2>
+<div class="wiki-content maincontent"><h2>Articles that cover various NMS related topics.</h2>
-<ul><li><a shape="rect" class="external-link" href="http://timbish.blogspot.com/2010/04/ussing-ssl-in-nmsactivemq.html" rel="nofollow">Using SSL with Apache.NMS.ActiveMQ</a></li><li><a shape="rect" class="external-link" href="http://remark.wordpress.com/articles/messaging-with-net-and-activemq/" rel="nofollow">Messaging with .NET and ActiveMQ</a></li><li><a shape="rect" class="external-link" href="http://remark.wordpress.com/articles/implementing-request-response-with-activemq-and-nms/" rel="nofollow">Implementing Request-Response with ActiveMQ and NMS</a></li><li><a shape="rect" class="external-link" href="http://remark.wordpress.com/articles/publish-subscribe-with-activemq-and-nms/" rel="nofollow">Publish-subscribe with ActiveMQ and NMS</a></li><li><a shape="rect" class="external-link" href="http://remark.wordpress.com/articles/transactional-message-processing-with-activemq-and-nms/" rel="nofollow">Transactional message processing with ActiveMQ and NMS</a></li></ul>
+<ul><li><a shape="rect" href="http://timbish.blogspot.com/2010/04/ussing-ssl-in-nmsactivemq.html">Using SSL with Apache.NMS.ActiveMQ</a></li><li><a shape="rect" href="http://remark.wordpress.com/articles/messaging-with-net-and-activemq/">Messaging with .NET and ActiveMQ</a></li><li><a shape="rect" href="http://remark.wordpress.com/articles/implementing-request-response-with-activemq-and-nms/">Implementing Request-Response with ActiveMQ and NMS</a></li><li><a shape="rect" href="http://remark.wordpress.com/articles/publish-subscribe-with-activemq-and-nms/">Publish-subscribe with ActiveMQ and NMS</a></li><li><a shape="rect" href="http://remark.wordpress.com/articles/transactional-message-processing-with-activemq-and-nms/">Transactional message processing with ActiveMQ and NMS</a></li></ul>
-<h2 id="Articles-OtherNMSrelatedcontent.">Other NMS related content.</h2>
+<h2>Other NMS related content.</h2>
-<p>While the NMS API is simple to use directly, you may want to take a look at <a shape="rect" class="external-link" href="http://springframework.net/" rel="nofollow">Spring.Net</a>,which offers various integration helper features similar to those in Spring for Java developers such as NmsTemplate and message listener containers etc.</p>
-<ul><li><a shape="rect" class="external-link" href="http://www.springframework.net/doc-latest/reference/html/messaging.html" rel="nofollow">Spring.Net Messaging Documentation</a></li><li><a shape="rect" class="external-link" href="http://www.springframework.net/doc-latest/reference/html/nms-quickstart.html" rel="nofollow">Spring.Net Messaging Examples</a></li></ul></div>
+<p>While the NMS API is simple to use directly, you may want to take a look at <a shape="rect" href="http://springframework.net/">Spring.Net</a>,which offers various integration helper features similar to those in Spring for Java developers such as NmsTemplate and message listener containers etc.</p>
+<ul><li><a shape="rect" href="http://www.springframework.net/doc-latest/reference/html/messaging.html">Spring.Net Messaging Documentation</a></li><li><a shape="rect" href="http://www.springframework.net/doc-latest/reference/html/nms-quickstart.html">Spring.Net Messaging Examples</a></li></ul>
+</div>
diff --git a/nms/banner.xml b/nms/banner.xml
index 572298d..860e1fd 100644
--- a/nms/banner.xml
+++ b/nms/banner.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><div id="asf_logo">
- <div id="activemq_logo">
- <a shape="rect" style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="">ActiveMQ</a>
- <a shape="rect" style="float:right; width:210px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:15px; margin-right:10px;" href="http://www.apache.org">ASF</a>
- </div>
-</div>
-</div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="2aca1a80-5394-4463-884c-a86206f71fdb" ac:name="html" ac:schema-version="1"><parameter ac:name="output">html</parameter><parameter ac:name="atlassian-macro-output-type">INLINE</parameter><parameter ac:name="noPanel">true</parameter><plain-text-body><div id="asf_logo">
+ <div id="activemq_logo">
+ <a style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="">ActiveMQ</a>
+ <a style="float:right; width:210px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:15px; margin-right:10px;" href="http://www.apache.org">ASF</a>
+ </div>
+</div>
+</plain-text-body></structured-macro></p></div>
diff --git a/nms/building.xml b/nms/building.xml
index 636f3b3..9a13ba9 100644
--- a/nms/building.xml
+++ b/nms/building.xml
@@ -1,19 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="Building-BuildingNMS">Building NMS</h2><p>Currently our main build tool for NMS is <a shape="rect" class="external-link" href="http://nant.sourceforge.net/" rel="nofollow">NAnt</a>.</p><div class="confluence-information-macro confluence-information-macro-tip"><p class="title">Setup For *NIX Users</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><ul><li>Install <a shape="rect" class="external-link" href="http://www.mono-project.com" rel="nofollow">Mono</a></li><li><p>On some operating systems (e.g. OS X), you may need to point the <strong>PKG_CONFIG_PATH</strong> environment variable at the mono packages</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
-</pre>
-</div></div></li><li>Depending on your installation of <a shape="rect" class="external-link" href="http://www.mono-project.com" rel="nofollow">Mono</a>, you may need additional steps to get NAnt going on OS X. The more recent versions of the Mono installer for OS X seem to set things up properly. However, if you are having problems running NAnt, try the following:<ul><li>download the binary of <a shape="rect" class="external-link" href="http://nant.sourceforge.net/" rel="nofollow">NAnt</a></li><li>create a script file called nant</li><li>chmod a+x nant</li><li><p>put the following into the script...</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>#!/bin/sh
+<div class="wiki-content maincontent"><h2>Building NMS</h2><p>Currently our main build tool for NMS is <a shape="rect" href="http://nant.sourceforge.net/">NAnt</a>.</p><structured-macro ac:macro-id="cd851e40-51da-4354-9757-59ae2cad278a" ac:name="tip" ac:schema-version="1"><parameter ac:name="title">Setup For *NIX Users</parameter><rich-text-body><ul><li>Install <a shape="rect" href="http://www.mono-project.com">Mono</a></li><li><p>On some operating systems (e.g. OS X), you may need to point the <strong>PKG_CONFIG_PATH</strong> environment variable at the mono packages</p><structured-macro ac:macro-id="e7bed819-de8c-437a-ab84-d93eec8d82f4" ac:name="noformat" ac:schema-version="1"><plain-text-body>export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
+</plain-text-body></structured-macro></li><li>Depending on your installation of <a shape="rect" href="http://www.mono-project.com">Mono</a>, you may need additional steps to get NAnt going on OS X. The more recent versions of the Mono installer for OS X seem to set things up properly. However, if you are having problems running NAnt, try the following:<ul><li>download the binary of <a shape="rect" href="http://nant.sourceforge.net/">NAnt</a></li><li>create a script file called nant</li><li>chmod a+x nant</li><li><p>put the following into the script...</p><structured-macro ac:macro-id="bbe1b5e9-c409-48e5-8ae5-7d72c9f9da78" ac:name="noformat" ac:schema-version="1"><plain-text-body>#!/bin/sh
exec /usr/bin/mono /path/to/nant/NAnt.exe "$@"
-</pre>
-</div></div></li></ul></li></ul><p>Thanks to the hints from <a shape="rect" class="external-link" href="http://cs-sdl.sourceforge.net/index.php/The_absolute_newbies_guide_to_SDL.NET" rel="nofollow">this page</a>.</p></div></div><h3 id="Building-BuildingNMSwithNant">Building NMS with Nant</h3><p>There are two steps to build the NMS project code, we'll look at each now.</p><h4 id="Building-SettingupyourNAntRepository.">Setting up your NAnt Repository.</h4><p>Before you can build the NMS API and the various provider libraries you need to initialize your local NAnt repository so that you have all the required dependencies available for the provider's NAnt build scripts to pull in during their builds. We maintain a tree in the NMS SVN repo with all the required dependencies which allow you to easily populate you NAnt repo. You can check out this tree by executing the following:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/vendor/
-</pre>
-</div></div><p>Now that you have the vendor tree checkout out you can install the various libaries into you NAnt repo by running each one's build script and with the 'install' target. You will need nant-0.91 or higher. The version 0.90 won't work. Let's take the NUnit testing framework libraries as an example, you install them like so:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>cd ./activemq-dotnet/vendor/NUnit/2.5.8
+</plain-text-body></structured-macro></li></ul></li></ul><p>Thanks to the hints from <a shape="rect" href="http://cs-sdl.sourceforge.net/index.php/The_absolute_newbies_guide_to_SDL.NET">this page</a>.</p></rich-text-body></structured-macro><h3>Building NMS with Nant</h3><p>There are two steps to build the NMS project code, we'll look at each now.</p><h4>Setting up your NAnt Repository.</h4><p>Before you can build the NMS API and the various provider libraries you need to initialize your local NAnt repository so that you have all the required dependencies available for the provider's NAnt build scripts to pull in during their builds. We maintain a tree in the NMS SVN repo with all the required dependencies which allow you to easily populate you NAnt repo. You can check out this tree by executing the following:</p><structured-macro ac:macro-id="86ea8e40-59d7-4664-a9da-10036af9af90" ac:name="noformat" ac:schema-version="1"><plain-text-body>svn co https://svn.apache.org/repos/asf/activemq/activemq-dotnet/vendor/
+</plain-text-body></structured-macro><p>Now that you have the vendor tree checkout out you can install the various libaries into you NAnt repo by running each one's build script and with the 'install' target. You will need nant-0.91 or higher. The version 0.90 won't work. Let's take the NUnit testing framework libraries as an example, you install them like so:</p><structured-macro ac:macro-id="2ef2e3db-85c4-401d-b73f-a40f820da55f" ac:name="noformat" ac:schema-version="1"><plain-text-body>cd ./activemq-dotnet/vendor/NUnit/2.5.8
nant install
-</pre>
-</div></div><p>Install each of the vendor libraries using the same process and then you are ready to build the NMS libraries.</p><h4 id="Building-BuildingtheNMSAPIandProviderlibraries.">Building the NMS API and Provider libraries.</h4><p>To build the code with Nant you will need to build the individual modules, starting with the main NMS module first. Following are the steps needed to build all of the modules, but depending on which provider you are using, you may only need to build the main Apache.NMS module and then your specific provider module. For example, if you are only working with ActiveMQ, then you would need to build the Apache.NMS module and the Apache.NMS.ActiveMQ provider module. Here are the steps to build all of the modules for the trunk version. Modify the paths to build a particular tag release (e.g., change the <strong>trunk</strong> folder to <strong>tags\1.0.0</strong>):</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>cd activemq-dotnetcd Apache.NMS\trunk
+</plain-text-body></structured-macro><p>Install each of the vendor libraries using the same process and then you are ready to build the NMS libraries.</p><h4>Building the NMS API and Provider libraries.</h4><p>To build the code with Nant you will need to build the individual modules, starting with the main NMS module first. Following are the steps needed to build all of the modules, but depending on which provider you are using, you may only need to build the main Apache.NMS module and then your specific provider module. For example, if you are only working with ActiveMQ, then you would need to build the Apache.NMS module and the Apache.NMS.ActiveMQ provider module. Here are the steps to build all of the modules for the trunk version. Modify the paths to build a particular tag release (e.g., change the <strong>trunk</strong> folder to <strong>tags\1.0.0</strong>):</p><structured-macro ac:macro-id="e10124cb-b80f-480b-b95a-1aa286c8a299" ac:name="noformat" ac:schema-version="1"><plain-text-body>cd activemq-dotnetcd Apache.NMS\trunk
nant
cd ..\..\Apache.NMS.ActiveMQ\trunk
@@ -38,9 +29,6 @@
nant
cd ..\..\Apache.NMS.ZMQ\trunk
-nant </pre>
-</div></div><p>This will build all of the providers. The only module that needs to be built first is the Apache.NMS module, as all of the other provider modules depend upon that module. <strong>IMPORTANT:</strong> In order to build the Apache.NMS.EMS module, you must have a licensed copy of the TIBCO.EMS.dll. This module is not available from The Apache Software Foundation.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Running the Unit Tests</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The unit tests depend on an ActiveMQ broker running on tcp://localhost:61616 so that the test cases can connect to ActiveMQ and send and receive messages etc. So if you have a distribution of ActiveMQ, <a shape="rect" class="external-link" href="http://activemq.apache.org/getting-started.html#GettingStarted-StartingActiveMQ">run the broker</a> first before testing Apache.NMS.ActiveMQ.</p></div></div><p>If you want to run a build with the unit tests (assuming you have a broker running) then type the following from the <strong>trunk</strong> folder of the provider module:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>nant test
-</pre>
-</div></div><p>Alternatively, you can use the NUnit graphical interface to load the appropriate module's nunit project file. Each project includes a file named Apache.NMS.<em>modulename</em>.Test.nunit, where <em>modulename</em> matches the provider module's name (e.g., ActiveMQ, AMQP, EMS, MQTT, MSMQ, Stomp, WCF, or ZMQ). This file can be loaded into the NUnit's graphical application to run all of the unit tests and see their output.</p><h2 id="Building-IDETips">IDE Tips</h2><p>If you are on windows then you probably want to use Visual Studio 2008; we highly recommend using <a shape="rect" class="external-link" href="http://www.jetbrains.com/resharper/" rel="nofollow">ReSharper</a> as well, - its a shame there is not a distro for OS X and Linux <img class="emoticon emoticon-sad" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/sad.png" data-emoticon-name="sad" alt="(sad)">.</p><h3 id="Building-UsingMonoDeveloptoeditC#">Using <a shape="rect" class="external-link" href="http://monodevelop.com/" rel="nofollow">MonoDevelop</a> to edit C#</h3><p>If you are on OS X or Linux (and even Windows nowdays) we recommend the use of <a shape="rect" class="external-link" href="http://monodevelop.com" rel="nofollow">MonoDevelop</a> for editing, refactoring and running the code. MonoDevelop can load the NMS Visual Studio Project files, and is integrated with the Mono debugger as well.</p><h3 id="Building-UsingEclipsetoeditC#">Using Eclipse to edit C#</h3><p>You can use Eclipse as your IDE to edit C# code.</p><p>If you want to use Eclipse there are the following two C# eclipse plugins we are aware of</p><ul><li><a shape="rect" class="external-link" href="http://emonic.sourceforge.net/" rel="nofollow">Emonic</a></li><li><a shape="rect" class="external-link" href="http://black-sun.sourceforge.net/" rel="nofollow">BlackSun</a></li><li><a shape="rect" class="external-link" href="http://www.improve-technologies.com/alpha/esharp/" rel="nofollow">Improve C#</a></li></ul><p>We tend to use BlackSun as it has auto-format and outline view support along with compiler warnings (though you might want to change the default font size).</p></div>
+nant </plain-text-body></structured-macro><p>This will build all of the providers. The only module that needs to be built first is the Apache.NMS module, as all of the other provider modules depend upon that module. <strong>IMPORTANT:</strong> In order to build the Apache.NMS.EMS module, you must have a licensed copy of the TIBCO.EMS.dll. This module is not available from The Apache Software Foundation.</p><structured-macro ac:macro-id="972b1522-2be5-411c-b495-de86a7ad85b5" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Running the Unit Tests</parameter><rich-text-body><p>The unit tests depend on an ActiveMQ broker running on tcp://localhost:61616 so that the test cases can connect to ActiveMQ and send and receive messages etc. So if you have a distribution of ActiveMQ, <a shape="rect" href="http://activemq.apache.org/getting-started.html#GettingStarted-StartingActiveMQ">run the broker</a> first before testing Apache.NMS.ActiveMQ.</p></rich-text-body></structured-macro><p>If you want to run a build with the unit tests (assuming you have a broker running) then type the following from the <strong>trunk</strong> folder of the provider module:</p><structured-macro ac:macro-id="553fdf82-7d60-41c8-9c58-213e096c32ba" ac:name="noformat" ac:schema-version="1"><plain-text-body>nant test
+</plain-text-body></structured-macro><p>Alternatively, you can use the NUnit graphical interface to load the appropriate module's nunit project file. Each project includes a file named Apache.NMS.<em>modulename</em>.Test.nunit, where <em>modulename</em> matches the provider module's name (e.g., ActiveMQ, AMQP, EMS, MQTT, MSMQ, Stomp, WCF, or ZMQ). This file can be loaded into the NUnit's graphical application to run all of the unit tests and see their output.</p><h2>IDE Tips</h2><p>If you are on windows then you probably want to use Visual Studio 2008; we highly recommend using <a shape="rect" href="http://www.jetbrains.com/resharper/">ReSharper</a> as well, - its a shame there is not a distro for OS X and Linux <emoticon ac:name="sad"></emoticon>.</p><h3>Using <a shape="rect" href="http://monodevelop.com/">MonoDevelop</a> to edit C#</h3><p>If you are on OS X or Linux (and even Windows nowdays) we recommend the use of <a shape="rect" href="http://monodevelop.com">MonoDevelop</a> for editing, refactoring and running the code. MonoDevelop can load the NMS Visual Studio Project files, and is integrated with the Mono debugger as well.</p><h3>Using Eclipse to edit C#</h3><p>You can use Eclipse as your IDE to edit C# code.</p><p>If you want to use Eclipse there are the following two C# eclipse plugins we are aware of</p><ul><li><a shape="rect" href="http://emonic.sourceforge.net/">Emonic</a></li><li><a shape="rect" href="http://black-sun.sourceforge.net/">BlackSun</a></li><li><a shape="rect" href="http://www.improve-technologies.com/alpha/esharp/">Improve C#</a></li></ul><p>We tend to use BlackSun as it has auto-format and outline view support along with compiler warnings (though you might want to change the default font size).</p></div>
diff --git a/nms/community.xml b/nms/community.xml
index 170071e..8cf6c99 100644
--- a/nms/community.xml
+++ b/nms/community.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="privacy-policy.xml">Privacy Policy</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="5f84320e-46e0-4177-b203-97d738b188cd" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/developers.xml b/nms/developers.xml
index 66c9060..ea8b9d3 100644
--- a/nms/developers.xml
+++ b/nms/developers.xml
@@ -1,3 +1,4 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="source.xml">Source</a></li></ul>
-<ul><li><a shape="rect" href="download.xml">Download</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="6ff6e627-87f7-43d8-be4b-b5486e1cc282" ac:name="children" ac:schema-version="1"></structured-macro>
+<ul><li><link><page ri:content-title="Download"></page><link-body>Download</link-body></link></li></ul>
+</div>
diff --git a/nms/download.xml b/nms/download.xml
index 81fa865..b6a9034 100644
--- a/nms/download.xml
+++ b/nms/download.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Download-Apache.NMSProjectDownloads">Apache.NMS Project Downloads</h2><p>Here you can Download the Apache.NMS API for .NET and the various Apache.NMS Provider Libraries such as Apache.NMS.ActiveMQ. Releases that are marked as <strong>in-progress</strong> won't be directly downloadable however there may be a SNAPSHOT build available, check the release page for more details on a specific release. </p><h3 id="Download-Apache.NMSAPIReleases"><a shape="rect" href="nms-api-downloads.xml">Apache.NMS API Releases</a></h3><p></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Release Date</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v171.xml">Apache.NMS API v1.7.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>09/04/2015</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v170.xml">Apache.NMS API v1.7.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/08/2015</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v160.xml">Apache.NMS API v1.6.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>05/24/2013</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v151.xml">Apache.NMS API v1.5.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/06/2012</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v150.xml">Apache.NMS API v1.5.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/10/2011</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v140.xml">Apache.NMS API v1.4.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>09/10/2010</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v130.xml">Apache.NMS API v1.3.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>05/14/2010</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v120.xml">Apache.NMS API v1.2.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/15/2010</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v110.xml">Apache.NMS API v1.1.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/12/2009</p></td></tr></tbody></table></div><h3 id="Download-Apache.NMS.ActiveMQReleases"><a shape="rect" href="activemq-downloads.xml">Apache.NMS.ActiveMQ Releases</a></h3><p></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Release Date</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>NMS API Rev</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v172.xml">Apache.NMS.ActiveMQ v1.7.2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>04/07/2016</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.7.1</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v171.xml">Apache.NMS.ActiveMQ v1.7.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10/05/2015</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.7.1</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v170.xml">Apache.NMS.ActiveMQ v1.7.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/16/2015</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.7.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v165.xml">Apache.NMS.ActiveMQ v1.6.5</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>02/05/2015</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v164.xml">Apache.NMS.ActiveMQ v1.6.4</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>09/14/2014</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v163.xml">Apache.NMS.ActiveMQ v1.6.3</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/21/2014</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v162.xml">Apache.NMS.ActiveMQ v1.6.2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>12/23/2013</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v161.xml">Apache.NMS.ActiveMQ v1.6.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10/19/2013</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v160.xml">Apache.NMS.ActiveMQ v1.6.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>06/06/2013</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.6.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v156.xml">Apache.NMS.ActiveMQ v1.5.6</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/12/2012</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.1</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v155.xml">Apache.NMS.ActiveMQ v1.5.5</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>05/03/2012</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v154.xml">Apache.NMS.ActiveMQ v1.5.4</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>04/13/2012</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v153.xml">Apache.NMS.ActiveMQ v1.5.3</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/27/2012</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v152.xml">Apache.NMS.ActiveMQ v1.5.2</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>11/18/2011</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v151.xml">Apache.NMS.ActiveMQ v1.5.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>06/04/2011</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v150.xml">Apache.NMS.ActiveMQ v1.5.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>02/17/2011</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.5.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v141.xml">Apache.NMS.ActiveMQ v1.4.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>10/04/2010</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.4.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v140.xml">Apache.NMS.ActiveMQ v1.4.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>09/17/2010</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.4.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v130.xml">Apache.NMS.ActiveMQ v1.3.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>05/21/2010</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.3.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenmsactivemq-v120.xml">Apache.NMS.ActiveMQ v1.2.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>02/12/2010</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.2.0</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-activemq-v110.xml">Apache.NMS ActiveMQ v1.1.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/12/2009</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>v1.1.0</p></td></tr></tbody></table></div><h3 id="Download-Apache.NMS.StompReleases"><a shape="rect" href="stomp-downloads.xml">Apache.NMS.Stomp Releases</a></h3><p></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Release Date </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v154.xml">Apache.NMS.Stomp v1.5.4</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 10/26/2013 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.1 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v153.xml">Apache.NMS.Stomp v1.5.3</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 08/30/2012 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.1 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v152.xml">Apache.NMS.Stomp v1.5.2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 11/19/2011 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v151.xml">Apache.NMS.Stomp v1.5.1</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 01/31/2011 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v150.xml">Apache.NMS.Stomp v1.5.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 01/14/2011 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v140.xml">Apache.NMS.Stomp v1.4.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 09/23/2010 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.4.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v130.xml">Apache.NMS.Stomp v1.3.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 05/27/2010 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.3.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v120.xml">Apache.NMS.Stomp v1.2.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 02/07/2010 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.2.0 </p></td></tr></tbody></table></div><h3 id="Download-Apache.NMS.MSMQReleases"><a shape="rect" href="msmq-downloads.xml">Apache.NMS.MSMQ Releases</a></h3><p></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Release Date </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenms-msmq-v110.xml">Apache.NMS MSMQ v1.1.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.1.0 </p></td></tr></tbody></table></div><h3 id="Download-Apache.NMS.EMSReleases"><a shape="rect" href="ems-downloads.xml">Apache.NMS.EMS Releases</a></h3><p></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Release Date </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenms-ems-v110.xml">Apache.NMS EMS v1.1.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.1.0 </p></td></tr></tbody></table></div><h3 id="Download-Apache.NMS.WCFReleases"><a shape="rect" href="wcf-downloads.xml">Apache.NMS.WCF Releases</a></h3><p></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Release Date </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmswcf-v110.xml">Apache.NMS.WCF v1.1.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.1.0 </p></td></tr></tbody></table></div><p> </p></div>
+<div class="wiki-content maincontent"><h2>Apache.NMS Project Downloads</h2><p>Here you can Download the Apache.NMS API for .NET and the various Apache.NMS Provider Libraries such as Apache.NMS.ActiveMQ. Releases that are marked as <strong>in-progress</strong> won't be directly downloadable however there may be a SNAPSHOT build available, check the release page for more details on a specific release. </p><h3><link><page ri:content-title="NMS API Downloads"></page><plain-text-link-body>Apache.NMS API Releases</plain-text-link-body></link></h3><p><structured-macro ac:macro-id="79cbe0cb-d173-4452-a630-866ad3454948" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="NMS API Downloads"></page></link></parameter></structured-macro></p><h3><link><page ri:content-title="ActiveMQ Downloads"></page><plain-text-link-body>Apache.NMS.ActiveMQ Releases</plain-text-link-body></link></h3><p><structured-macro ac:macro-id="d6a986b7-dc8d-47f5-af47-5ac5ef8299aa" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="ActiveMQ Downloads"></page></link></parameter></structured-macro></p><h3><link><page ri:content-title="Stomp Downloads"></page><plain-text-link-body>Apache.NMS.Stomp Releases</plain-text-link-body></link></h3><p><structured-macro ac:macro-id="85006c3b-4c81-4bff-b570-3231dea92b8e" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Stomp Downloads"></page></link></parameter></structured-macro></p><h3><link><page ri:content-title="MSMQ Downloads"></page><plain-text-link-body>Apache.NMS.MSMQ Releases</plain-text-link-body></link></h3><p><structured-macro ac:macro-id="c3158f84-277a-47bf-8179-c6d9ef7848bb" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="MSMQ Downloads"></page></link></parameter></structured-macro></p><h3><link><page ri:content-title="EMS Downloads"></page><plain-text-link-body>Apache.NMS.EMS Releases</plain-text-link-body></link></h3><p><structured-macro ac:macro-id="0be5d96e-02c9-45ca-8a0c-53a081e5d9dd" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="EMS Downloads"></page></link></parameter></structured-macro></p><h3><link><page ri:content-title="WCF Downloads"></page><plain-text-link-body>Apache.NMS.WCF Releases</plain-text-link-body></link></h3><p><structured-macro ac:macro-id="742c80db-eb7f-4e03-bd5c-125c253d2910" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="WCF Downloads"></page></link></parameter></structured-macro></p><p> </p></div>
diff --git a/nms/ems-downloads.xml b/nms/ems-downloads.xml
index 271598e..95e0a7b 100644
--- a/nms/ems-downloads.xml
+++ b/nms/ems-downloads.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Release Date </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenms-ems-v110.xml">Apache.NMS EMS v1.1.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.1.0 </p></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Release Date </p></th><th colspan="1" rowspan="1"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS EMS v1.1.0"></page></link> </p></td><td colspan="1" rowspan="1"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1"><p> v1.1.0 </p></td></tr></tbody></table>
+</div>
diff --git a/nms/ems-examples.xml b/nms/ems-examples.xml
index d62e311..19da9af 100644
--- a/nms/ems-examples.xml
+++ b/nms/ems-examples.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="fc540509-030d-47b5-b97d-8036a5e6ff87" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">3</parameter></structured-macro></div>
diff --git a/nms/examples.xml b/nms/examples.xml
index 788432d..6a12df2 100644
--- a/nms/examples.xml
+++ b/nms/examples.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="Examples-Examples">Examples</h2><p>The following example gives a brief demonstration for connecting, sending and receiving a message using NMS.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Sync NMS Example</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[using System;
+<div class="wiki-content maincontent"><h2>Examples</h2><p>The following example gives a brief demonstration for connecting, sending and receiving a message using NMS.</p><structured-macro ac:macro-id="efc4bb15-f991-4222-847d-28cd673c1f1f" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Sync NMS Example</parameter><plain-text-body>using System;
using Apache.NMS;
using Apache.NMS.Util;
@@ -15,9 +14,9 @@
// ems:tcp://tibcohost:7222
// msmq://localhost
- Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
+ Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
- Console.WriteLine("About to connect to " + connecturi);
+ Console.WriteLine("About to connect to " + connecturi);
// NOTE: ensure the nmsprovider-activemq.config file exists in the executable folder.
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
@@ -28,29 +27,29 @@
// Examples for getting a destination:
//
// Hard coded destinations:
- // IDestination destination = session.GetQueue("FOO.BAR");
+ // IDestination destination = session.GetQueue("FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = session.GetTopic("FOO.BAR");
+ // IDestination destination = session.GetTopic("FOO.BAR");
// Debug.Assert(destination is ITopic);
//
// Embedded destination type in the name:
- // IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = SessionUtil.GetDestination(session, "topic://FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "topic://FOO.BAR");
// Debug.Assert(destination is ITopic);
//
// Defaults to queue if type is not specified:
- // IDestination destination = SessionUtil.GetDestination(session, "FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "FOO.BAR");
// Debug.Assert(destination is IQueue);
//
// .NET 3.5 Supports Extension methods for a simplified syntax:
- // IDestination destination = session.GetDestination("queue://FOO.BAR");
+ // IDestination destination = session.GetDestination("queue://FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = session.GetDestination("topic://FOO.BAR");
+ // IDestination destination = session.GetDestination("topic://FOO.BAR");
// Debug.Assert(destination is ITopic);
- IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
- Console.WriteLine("Using destination: " + destination);
+ IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
+ Console.WriteLine("Using destination: " + destination);
// Create a consumer and producer
using(IMessageConsumer consumer = session.CreateConsumer(destination))
@@ -60,11 +59,11 @@
connection.Start();
producer.DeliveryMode = MsgDeliveryMode.Persistent;
- // Send a message
- ITextMessage request = session.CreateTextMessage("Hello World!");
- request.NMSCorrelationID = "abc";
- request.Properties["NMSXGroupID"] = "cheese";
- request.Properties["myHeader"] = "Cheddar";
+  // Send a message
+ ITextMessage request = session.CreateTextMessage("Hello World!");
+ request.NMSCorrelationID = "abc";
+ request.Properties["NMSXGroupID"] = "cheese";
+ request.Properties["myHeader"] = "Cheddar";
producer.Send(request);
@@ -72,21 +71,19 @@
ITextMessage message = consumer.Receive() as ITextMessage;
if(message == null)
{
- Console.WriteLine("No message received!");
+ Console.WriteLine("No message received!");
}
else
{
- Console.WriteLine("Received message with ID: " + message.NMSMessageId);
- Console.WriteLine("Received message with text: " + message.Text);
+ Console.WriteLine("Received message with ID: " + message.NMSMessageId);
+ Console.WriteLine("Received message with text: " + message.Text);
}
}
}
}
}
}
-]]></script>
-</div></div><h3 id="Examples-Asynchronousconsumption">Asynchronous consumption</h3><p>You have the choice of synchronously pulling messages via the Receive() methods as shown above, or you can use the asynchronous approach demonstrated in the following example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Async NMS Example</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[using System;
+</plain-text-body></structured-macro><h3>Asynchronous consumption</h3><p>You have the choice of synchronously pulling messages via the Receive() methods as shown above, or you can use the asynchronous approach demonstrated in the following example:</p><structured-macro ac:macro-id="3406da59-7c0a-498a-889f-d042d4dc6d65" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Async NMS Example</parameter><plain-text-body>using System;
using System.Threading;
using Apache.NMS;
using Apache.NMS.Util;
@@ -109,9 +106,9 @@
// ems:tcp://tibcohost:7222
// msmq://localhost
- Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
+ Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
- Console.WriteLine("About to connect to " + connecturi);
+ Console.WriteLine("About to connect to " + connecturi);
// NOTE: ensure the nmsprovider-activemq.config file exists in the executable folder.
@@ -123,30 +120,30 @@
// Examples for getting a destination:
//
// Hard coded destinations:
- // IDestination destination = session.GetQueue("FOO.BAR");
+ // IDestination destination = session.GetQueue("FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = session.GetTopic("FOO.BAR");
+ // IDestination destination = session.GetTopic("FOO.BAR");
// Debug.Assert(destination is ITopic);
//
// Embedded destination type in the name:
- // IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = SessionUtil.GetDestination(session, "topic://FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "topic://FOO.BAR");
// Debug.Assert(destination is ITopic);
//
// Defaults to queue if type is not specified:
- // IDestination destination = SessionUtil.GetDestination(session, "FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "FOO.BAR");
// Debug.Assert(destination is IQueue);
//
// .NET 3.5 Supports Extension methods for a simplified syntax:
- // IDestination destination = session.GetDestination("queue://FOO.BAR");
+ // IDestination destination = session.GetDestination("queue://FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = session.GetDestination("topic://FOO.BAR");
+ // IDestination destination = session.GetDestination("topic://FOO.BAR");
// Debug.Assert(destination is ITopic);
- IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
+ IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
- Console.WriteLine("Using destination: " + destination);
+ Console.WriteLine("Using destination: " + destination);
// Create a consumer and producer
using(IMessageConsumer consumer = session.CreateConsumer(destination))
@@ -159,10 +156,10 @@
consumer.Listener += new MessageListener(OnMessage);
// Send a message
- ITextMessage request = session.CreateTextMessage("Hello World!");
- request.NMSCorrelationID = "abc";
- request.Properties["NMSXGroupID"] = "cheese";
- request.Properties["myHeader"] = "Cheddar";
+ ITextMessage request = session.CreateTextMessage("Hello World!");
+ request.NMSCorrelationID = "abc";
+ request.Properties["NMSXGroupID"] = "cheese";
+ request.Properties["myHeader"] = "Cheddar";
producer.Send(request);
@@ -170,12 +167,12 @@
semaphore.WaitOne((int) receiveTimeout.TotalMilliseconds, true);
if(message == null)
{
- Console.WriteLine("No message received!");
+ Console.WriteLine("No message received!");
}
else
{
- Console.WriteLine("Received message with ID: " + message.NMSMessageId);
- Console.WriteLine("Received message with text: " + message.Text);
+ Console.WriteLine("Received message with ID: " + message.NMSMessageId);
+ Console.WriteLine("Received message with text: " + message.Text);
}
}
}
@@ -189,6 +186,5 @@
}
}
-]]></script>
-</div></div><p>The above uses a C# <strong>delegate</strong> so that the OnMessage() method will be called whenever a message arrives.</p><p>Note that the threading contract is similar to that of JMS - messages are dispatched for a single session's consumers in one thread at once. Consumers in different sessions can process messages concurrently, but consumers in the same session are guarenteed to be called by only one thread at a time (e.g., if you have 3 consumers on a session, then only one of the consumers will be called concurrently).</p></div>
+</plain-text-body></structured-macro><p>The above uses a C# <strong>delegate</strong> so that the OnMessage() method will be called whenever a message arrives.</p><p>Note that the threading contract is similar to that of JMS - messages are dispatched for a single session's consumers in one thread at once. Consumers in different sessions can process messages concurrently, but consumers in the same session are guarenteed to be called by only one thread at a time (e.g., if you have 3 consumers on a session, then only one of the consumers will be called concurrently).</p></div>
diff --git a/nms/faq.xml b/nms/faq.xml
index 149d612..f551315 100644
--- a/nms/faq.xml
+++ b/nms/faq.xml
@@ -1,20 +1,20 @@
-<div class="wiki-content maincontent"><h2 id="FAQ-GeneralQuestions">General Questions</h2>
+<div class="wiki-content maincontent"><h2>General Questions</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="are-there-more-faq-entries.xml">Are there more FAQ Entries</a></li><li><a shape="rect" href="should-i-pool-connections.xml">Should I pool connections</a></li><li><a shape="rect" href="what-is-nms.xml">What is NMS</a></li></ul>
+<structured-macro ac:macro-id="dc8c6620-2708-4b9d-82a6-41311ed7fe9c" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro>
-<h2 id="FAQ-UsingNMSFAQ">Using NMS FAQ</h2>
+<h2>Using NMS FAQ</h2>
+<structured-macro ac:macro-id="0badc8ca-d47a-4421-88b6-02223562fce8" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="NMS FAQ"></page></link></parameter></structured-macro>
+<h2>Using NMS.ActiveMQ FAQ</h2>
-<h2 id="FAQ-UsingNMS.ActiveMQFAQ">Using NMS.ActiveMQ FAQ</h2>
+<structured-macro ac:macro-id="895f0349-85ee-476d-8351-b5fe59041b8f" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="ActiveMQ FAQ"></page></link></parameter></structured-macro>
+<h2>Using NMS.Stomp FAQ</h2>
+<h2>Using NMS.MSMQ FAQ</h2>
-<h2 id="FAQ-UsingNMS.StompFAQ">Using NMS.Stomp FAQ</h2>
+<h2>Using NMS.EMS FAQ</h2>
-<h2 id="FAQ-UsingNMS.MSMQFAQ">Using NMS.MSMQ FAQ</h2>
-
-<h2 id="FAQ-UsingNMS.EMSFAQ">Using NMS.EMS FAQ</h2>
-
-<h2 id="FAQ-UsingNMS.WCFFAQ">Using NMS.WCF FAQ</h2></div>
+<h2>Using NMS.WCF FAQ</h2></div>
diff --git a/nms/index.xml b/nms/index.xml
index fdedd93..dfc9a4a 100644
--- a/nms/index.xml
+++ b/nms/index.xml
@@ -1,84 +1,2 @@
-<div class="wiki-content maincontent"><p>Welcome to the Apache NMS project, the <a shape="rect" href="nms-api.xml">.NET Messaging API</a>.</p><h3 id="Index-NMSAPIOverview">NMS API Overview</h3><p>The <a shape="rect" href="apachenms.xml">NMS API</a> This allows you to build .NET applications in C#, VB, or any other .NET language, using a single API to connect to multiple different providers using a JMS style API.</p><p></p><h3 id="Index-NMSProviders">NMS Providers</h3><p>An NMS Provider is a .NET Assembly that provides an implementation of the NMS API that provides connectivity with a particular Messaging Service or an implementation of a standard Messaging Protocol. Currently, the following providers are available:</p><ul><li><a shape="rect" href="apachenmsactivemq.xml"><strong>ActiveMQ</strong></a> client which communicates with ActiveMQ using its own native wire protocol and provides many <a shape="rect" href="activemq-advanced-features.xml">advanced features</a> beyond the standard NMS API.</li><li><a shape="rect" href="apachenmsstomp.xml"><strong>STOMP</strong></a> which connects to any <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect" class="external-link" href="http://stomp.codehaus.org/StompConnect" rel="nofollow">StompConnect</a>, NMS can be used to communicate with pretty much any existing MOM provider! (Or at least those that support JMS which most MOM providers do).</li><li><a shape="rect" href="apachenmsmsmq.xml"><strong>MSMQ</strong></a> is an implementation of NMS using Microsoft's MSMQ API.</li><li><a shape="rect" href="apachenmsems.xml"><strong>EMS</strong></a> provider for talking to TIBCO's EMS message broker.  To use this, you will need to following TIBCO's licensing requirements to acquire the TIBCO client assembly DLL.  NMS does not ship with the TIBCO client assembly.</li><li><a shape="rect" href="apachenmswcf.xml"><strong>WCF</strong></a> provides support of Windows Communications Framework.</li><li><a shape="rect" href="apachenmsamqp.xml"><strong>AMQP</strong></a> is an implementation of NMS using the <a shape="rect" class="external-link" href="https://qpid.apache.org/components/messaging-api/index.html">Apache Qpid Messaging API</a>. AMQP 1.0 protocol support is provided by <a shape="rect" class="external-link" href="https://qpid.apache.org/proton/index.html">Apache Qpid Proton</a>.</li><li><a shape="rect" href="apachenmsmqtt.xml"><strong>MQTT</strong></a> provider uses the publish-subscribe<span style="color: rgb(37,37,37);"> pattern that is a "light weight" messaging protocol for use on top of the </span><a shape="rect" class="external-link" href="https://en.wikipedia.org/wiki/TCP/IP" rel="nofollow" title="TCP/IP">TCP/IP protocol</a><span style="color: rgb(37,37,37);">. </span></li><li><span style="color: rgb(37,37,37);"><strong><a shape="rect" href="apachenmsxms.xml">XMS</a></strong> provider connects to the IBM WebSphere MQ Series broker.</span></li></ul><h3 id="Index-News">News</h3><p>
-
-
-
-</p><div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2016/04/07/apachenmsactivemq-v172-released.xml">Apache.NMS.ActiveMQ v1.7.2 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Apr 07, 2016</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><div class="wiki-content"><p>A new bug-fix version of the Apache.NMS.ActiveMQ library has been <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Downloads">released</a>.</p></div></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2015/10/05/apachenmsactivemq-v171-released.xml">Apache.NMS.ActiveMQ v1.7.1 Released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Oct 05, 2015</div>
-
- </div>
-
- <div class="wiki-content">
- <div class="wiki-content"><p>A new bug-fix version of the Apache.NMS.ActiveMQ library has been <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Downloads">released</a>.</p></div>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2015/04/28/apachenmsactivemq-v170-released.xml">Apache.NMS.ActiveMQ v1.7.0 released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Apr 28, 2015</div>
-
- </div>
-
- <div class="wiki-content">
- <p>A new major version of the Apache.NMS.ActiveMQ library has been <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Downloads">released</a>.</p>
- </div>
-
-
- </div>
-
-
-<div class="blog-post-listing">
- <div class="logo-heading-block">
- <span class="logoBlock">
- <a shape="rect" class="userLogoLink" href="https://cwiki.apache.org/confluence/display/~tabish121">
- <img class="userLogo logo" src="/images/confluence/icons/profilepics/default.png" alt="User icon: tabish121" title="tabish121">
- </a> </span>
- <span class="blogHeading">
- <a shape="rect" class="blogHeading" href="2015/04/28/apachenmsactivemq-v165-released.xml">Apache.NMS.ActiveMQ v1.6.5 released</a>
- </span><div class="page-metadata not-personal"> <a shape="rect" class="url fn confluence-userlink" href="https://cwiki.apache.org/confluence/display/~tabish121">Timothy Bish</a> posted on Apr 28, 2015</div>
-
- </div>
-
- <div class="wiki-content">
- <p>A new bug fix release of the Apache.NMS.ActiveMQ library has been <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Downloads">released</a>.</p>
- </div>
-
-
- </div>
- <h3 id="Index-WorkingwithNMS">Working with NMS</h3><p>To find out more about NMS, select from the following resources:</p><ul><li><a shape="rect" href="download.xml">Download NMS</a></li><li><a shape="rect" href="source.xml">Get the Source Code</a></li><li><a shape="rect" href="building.xml">How to build NMS</a></li><li><a shape="rect" href="nms.xml">Getting Started</a></li><li><a shape="rect" href="nms-api.xml">NMS API Documentation</a></li></ul></div>
+<div class="wiki-content maincontent"><p>Welcome to the Apache NMS project, the <link><page ri:content-title="NMS API"></page><plain-text-link-body>.NET Messaging API</plain-text-link-body></link>.</p><h3>NMS API Overview</h3><p>The <link><page ri:content-title="Apache.NMS"></page><plain-text-link-body>NMS API</plain-text-link-body></link> This allows you to build .NET applications in C#, VB, or any other .NET language, using a single API to connect to multiple different providers using a JMS style API.</p><p><structured-macro ac:macro-id="895ed7ef-b774-4c41-ba9d-e2b6439f581e" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="NMS Providers"></page></link></parameter></structured-macro></p><h3>News</h3><p><structured-macro ac:macro-id="590076f9-78cc-46a3-9689-9ebf753249dd" ac:name="blog-posts" ac:schema-version="1"><parameter ac:name="">4</parameter></structured-macro></p><h3>Working with NMS</h3><p>To find out more about NMS, select from the following resources:</p><ul><li><link><page ri:content-title="Download"></page><plain-text-link-body>Download NMS</plain-text-link-body></link></li><li><link><page ri:content-title="Source"></page><plain-text-link-body>Get the Source Code</plain-text-link-body></link></li><li><link><page ri:content-title="Building"></page><plain-text-link-body>How to build NMS</plain-text-link-body></link></li><li><link><page ri:content-title="NMS"></page><plain-text-link-body>Getting Started</plain-text-link-body></link></li><li><link><page ri:content-title="NMS API"></page><plain-text-link-body>NMS API Documentation</plain-text-link-body></link></li></ul></div>
diff --git a/nms/msmq-downloads.xml b/nms/msmq-downloads.xml
index 4cb1dc7..5350f55 100644
--- a/nms/msmq-downloads.xml
+++ b/nms/msmq-downloads.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Release Date </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenms-msmq-v110.xml">Apache.NMS MSMQ v1.1.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.1.0 </p></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Release Date </p></th><th colspan="1" rowspan="1"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS MSMQ v1.1.0"></page></link> </p></td><td colspan="1" rowspan="1"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1"><p> v1.1.0 </p></td></tr></tbody></table>
+</div>
diff --git a/nms/msmq-examples.xml b/nms/msmq-examples.xml
index d62e311..475517d 100644
--- a/nms/msmq-examples.xml
+++ b/nms/msmq-examples.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="d0c3e88c-212e-4754-a071-31e86e1146d7" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">3</parameter></structured-macro></div>
diff --git a/nms/navigation.xml b/nms/navigation.xml
index 7d93e5c..c494bee 100644
--- a/nms/navigation.xml
+++ b/nms/navigation.xml
@@ -1,32 +1,33 @@
-<div class="wiki-content maincontent"><h3 id="Navigation-Overview"><a shape="rect" href="overview.xml">Overview</a></h3>
+<div class="wiki-content maincontent"><h3><link><page ri:content-title="Overview"></page></link></h3>
-<ul class="alternate"><li><a shape="rect" href="index.xml">Home</a></li><li><a shape="rect" href="faq.xml">FAQ</a></li><li><a shape="rect" href="download.xml">Download</a></li></ul>
+<ul class="alternate"><li><link><page ri:content-title="Index"></page><link-body>Home</link-body></link></li><li><link><page ri:content-title="FAQ"></page></link></li><li><link><page ri:content-title="Download"></page></link></li></ul>
-<h3 id="Navigation-UsingNMS"><a shape="rect" href="using-nms.xml">Using NMS</a></h3>
+<h3><link><page ri:content-title="Using NMS"></page></link></h3>
-<ul class="alternate"><li><a shape="rect" href="apachenms.xml">NMS Overview</a></li><li><a shape="rect" href="nms.xml">Getting Started</a></li><li><a shape="rect" href="nms-api.xml">NMS API Reference</a></li><li><a shape="rect" href="apachenmsactivemq.xml">ActiveMQ</a></li><li><a shape="rect" href="apachenmsstomp.xml">Stomp</a></li><li><a shape="rect" href="apachenmsmsmq.xml">MSMQ</a></li><li><a shape="rect" href="apachenmsems.xml">Tibco EMS</a></li><li><a shape="rect" href="apachenmswcf.xml">WCF</a></li></ul>
+<ul class="alternate"><li><link><page ri:content-title="Apache.NMS"></page><link-body>NMS Overview</link-body></link></li><li><link><page ri:content-title="NMS"></page><link-body>Getting Started</link-body></link></li><li><link><page ri:content-title="NMS API"></page><link-body>NMS API Reference</link-body></link></li><li><link><page ri:content-title="Apache.NMS.ActiveMQ"></page><link-body>ActiveMQ</link-body></link></li><li><link><page ri:content-title="Apache.NMS.Stomp"></page><link-body>Stomp</link-body></link></li><li><link><page ri:content-title="Apache.NMS.MSMQ"></page><link-body>MSMQ</link-body></link></li><li><link><page ri:content-title="Apache.NMS.EMS"></page><link-body>Tibco EMS</link-body></link></li><li><link><page ri:content-title="Apache.NMS.WCF"></page><link-body>WCF</link-body></link></li></ul>
-<h3 id="Navigation-Search">Search</h3>
-<p></p><p>
-</p><form enctype="application/x-www-form-urlencoded" method="get" id="cse-search-box" action="http://www.google.com/cse">
- <div>
- <input type="hidden" name="cx" value="007878419884033443453:m5nhvy4hmyq">
- <input type="hidden" name="ie" value="UTF-8">
- <input type="text" name="q" size="21">
- <input type="submit" name="sa" value="Search">
- </div>
-</form>
-<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
-<p></p>
+<h3>Search</h3>
+<p></p><p><structured-macro ac:macro-id="4162f69a-6f79-4fb8-914d-d0ef4169ed10" ac:name="html" ac:schema-version="1"><plain-text-body>
+<form action="http://www.google.com/cse" id="cse-search-box">
+ <div>
+ <input type="hidden" name="cx" value="007878419884033443453:m5nhvy4hmyq" />
+ <input type="hidden" name="ie" value="UTF-8" />
+ <input type="text" name="q" size="21" />
+ <input type="submit" name="sa" value="Search" />
+ </div>
+</form>
+<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
+</plain-text-body></structured-macro></p><p></p>
-<h3 id="Navigation-Community"><a shape="rect" href="community.xml">Community</a></h3>
+<h3><link><page ri:content-title="Community"></page></link></h3>
-<ul class="alternate"><li><a shape="rect" href="support.xml">Support</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/contributing.html">Contributing</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a></li><li><a shape="rect" class="external-link" href="irc://irc.codehaus.org/activemq" rel="nofollow">IRC</a></li><li><a shape="rect" href="articles.xml">Articles</a></li><li><a shape="rect" href="site.xml">Site</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/team.html">Team</a></li></ul>
+<ul class="alternate"><li><link><page ri:content-title="Support"></page></link></li><li><a shape="rect" href="http://activemq.apache.org/contributing.html">Contributing</a></li><li><a shape="rect" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a></li><li><a shape="rect" href="irc://irc.codehaus.org/activemq">IRC</a></li><li><link><page ri:content-title="Articles"></page></link></li><li><link><page ri:content-title="Site"></page></link></li><li><a shape="rect" href="http://activemq.apache.org/team.html">Team</a></li></ul>
-<h3 id="Navigation-Developers"><a shape="rect" href="developers.xml">Developers</a></h3>
+<h3><link><page ri:content-title="Developers"></page></link></h3>
-<ul class="alternate"><li><a shape="rect" href="source.xml">Source</a></li><li><a shape="rect" href="building.xml">Building</a></li></ul></div>
+<ul class="alternate"><li><link><page ri:content-title="Source"></page></link></li><li><link><page ri:content-title="Building"></page></link></li></ul>
+</div>
diff --git a/nms/nms-api-downloads.xml b/nms/nms-api-downloads.xml
index 74ff0bd..1374d59 100644
--- a/nms/nms-api-downloads.xml
+++ b/nms/nms-api-downloads.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Release Date</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v171.xml">Apache.NMS API v1.7.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>09/04/2015</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v170.xml">Apache.NMS API v1.7.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/08/2015</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v160.xml">Apache.NMS API v1.6.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>05/24/2013</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v151.xml">Apache.NMS API v1.5.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/06/2012</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v150.xml">Apache.NMS API v1.5.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/10/2011</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v140.xml">Apache.NMS API v1.4.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>09/10/2010</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v130.xml">Apache.NMS API v1.3.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>05/14/2010</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v120.xml">Apache.NMS API v1.2.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>01/15/2010</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="apachenms-api-v110.xml">Apache.NMS API v1.1.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>07/12/2009</p></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><table><tbody><tr><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Release Date</p></th></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.7.1"></page></link></p></td><td colspan="1" rowspan="1"><p>09/04/2015</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.7.0"></page></link></p></td><td colspan="1" rowspan="1"><p>01/08/2015</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.6.0"></page></link></p></td><td colspan="1" rowspan="1"><p>05/24/2013</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.5.1"></page></link></p></td><td colspan="1" rowspan="1"><p>07/06/2012</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.5.0"></page></link></p></td><td colspan="1" rowspan="1"><p>01/10/2011</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.4.0"></page></link></p></td><td colspan="1" rowspan="1"><p>09/10/2010</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.3.0"></page></link></p></td><td colspan="1" rowspan="1"><p>05/14/2010</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.2.0"></page></link></p></td><td colspan="1" rowspan="1"><p>01/15/2010</p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="Apache.NMS API v1.1.0"></page></link></p></td><td colspan="1" rowspan="1"><p>07/12/2009</p></td></tr></tbody></table></div>
diff --git a/nms/nms-api.xml b/nms/nms-api.xml
index d8c05e5..983f997 100644
--- a/nms/nms-api.xml
+++ b/nms/nms-api.xml
@@ -1,8 +1,9 @@
-<div class="wiki-content maincontent"><p>The NMS documentation has been generated using <a shape="rect" class="external-link" href="http://sandcastle.codeplex.com/" rel="nofollow">Microsoft's Sandcastle</a> open source product. The <a shape="rect" class="external-link" href="http://sandcastlestyles.codeplex.com/" rel="nofollow">Sandcastle Styles</a> project was used to enhance the output generated from the current release of Sandcastle.</p>
+<div class="wiki-content maincontent"><p>The NMS documentation has been generated using <a shape="rect" href="http://sandcastle.codeplex.com/">Microsoft's Sandcastle</a> open source product. The <a shape="rect" href="http://sandcastlestyles.codeplex.com/">Sandcastle Styles</a> project was used to enhance the output generated from the current release of Sandcastle.</p>
-<h2 id="NMSAPI-NMSAPI1.6.0">NMS API 1.6.0</h2>
+<h2>NMS API 1.6.0</h2>
-<h3 id="NMSAPI-MSDNStyleFormatting">MSDN Style Formatting</h3>
+<h3>MSDN Style Formatting</h3>
-<ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/msdoc/1.6.0/vs2005/Output/html/N_Apache_NMS.htm">Apache.NMS Namespace</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/msdoc/1.6.0/vs2005/Output/html/N_Apache_NMS_Util.htm">Apache.NMS.Util Namespace</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/msdoc/1.6.0/vs2005/Output/html/N_Apache_NMS_Policies.htm">Apache.NMS.Policies Namespace</a></li></ul></div>
+<ul><li><a shape="rect" href="http://activemq.apache.org/nms/msdoc/1.6.0/vs2005/Output/html/N_Apache_NMS.htm">Apache.NMS Namespace</a></li><li><a shape="rect" href="http://activemq.apache.org/nms/msdoc/1.6.0/vs2005/Output/html/N_Apache_NMS_Util.htm">Apache.NMS.Util Namespace</a></li><li><a shape="rect" href="http://activemq.apache.org/nms/msdoc/1.6.0/vs2005/Output/html/N_Apache_NMS_Policies.htm">Apache.NMS.Policies Namespace</a></li></ul>
+</div>
diff --git a/nms/nms-examples.xml b/nms/nms-examples.xml
index ea83dca..e81b5b6 100644
--- a/nms/nms-examples.xml
+++ b/nms/nms-examples.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>This is where you will find examples of how to use the NMS API. These examples demonstrate using the NMS API generically and are limited to features exposed directly through the API model. For examples covering more advanced features of a specific NMS Provider, refer to the documentation for that NMS Provider.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="nms-simple-asynchronous-consumer-example.xml">NMS Simple Asynchronous Consumer Example</a></li><li><a shape="rect" href="nms-simple-synchornous-consumer-example.xml">NMS Simple Synchornous Consumer Example</a></li></ul></div>
+<structured-macro ac:macro-id="ad2ff0b3-960d-4232-960a-33036f4b83af" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">2</parameter></structured-macro></div>
diff --git a/nms/nms-providers.xml b/nms/nms-providers.xml
index a4d266a..e496ada 100644
--- a/nms/nms-providers.xml
+++ b/nms/nms-providers.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h3 id="NMSProviders-NMSProviders">NMS Providers</h3><p>An NMS Provider is a .NET Assembly that provides an implementation of the NMS API that provides connectivity with a particular Messaging Service or an implementation of a standard Messaging Protocol. Currently, the following providers are available:</p><ul><li><a shape="rect" href="apachenmsactivemq.xml"><strong>ActiveMQ</strong></a> client which communicates with ActiveMQ using its own native wire protocol and provides many <a shape="rect" href="activemq-advanced-features.xml">advanced features</a> beyond the standard NMS API.</li><li><a shape="rect" href="apachenmsstomp.xml"><strong>STOMP</strong></a> which connects to any <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect" class="external-link" href="http://stomp.codehaus.org/StompConnect" rel="nofollow">StompConnect</a>, NMS can be used to communicate with pretty much any existing MOM provider! (Or at least those that support JMS which most MOM providers do).</li><li><a shape="rect" href="apachenmsmsmq.xml"><strong>MSMQ</strong></a> is an implementation of NMS using Microsoft's MSMQ API.</li><li><a shape="rect" href="apachenmsems.xml"><strong>EMS</strong></a> provider for talking to TIBCO's EMS message broker.  To use this, you will need to following TIBCO's licensing requirements to acquire the TIBCO client assembly DLL.  NMS does not ship with the TIBCO client assembly.</li><li><a shape="rect" href="apachenmswcf.xml"><strong>WCF</strong></a> provides support of Windows Communications Framework.</li><li><a shape="rect" href="apachenmsamqp.xml"><strong>AMQP</strong></a> is an implementation of NMS using the <a shape="rect" class="external-link" href="https://qpid.apache.org/components/messaging-api/index.html">Apache Qpid Messaging API</a>. AMQP 1.0 protocol support is provided by <a shape="rect" class="external-link" href="https://qpid.apache.org/proton/index.html">Apache Qpid Proton</a>.</li><li><a shape="rect" href="apachenmsmqtt.xml"><strong>MQTT</strong></a> provider uses the publish-subscribe<span style="color: rgb(37,37,37);"> pattern that is a "light weight" messaging protocol for use on top of the </span><a shape="rect" class="external-link" href="https://en.wikipedia.org/wiki/TCP/IP" rel="nofollow" title="TCP/IP">TCP/IP protocol</a><span style="color: rgb(37,37,37);">. </span></li><li><span style="color: rgb(37,37,37);"><strong><a shape="rect" href="apachenmsxms.xml">XMS</a></strong> provider connects to the IBM WebSphere MQ Series broker.</span></li></ul></div>
+<div class="wiki-content maincontent"><h3>NMS Providers</h3><p>An NMS Provider is a .NET Assembly that provides an implementation of the NMS API that provides connectivity with a particular Messaging Service or an implementation of a standard Messaging Protocol. Currently, the following providers are available:</p><ul><li><link><page ri:content-title="Apache.NMS.ActiveMQ"></page><link-body><strong>ActiveMQ</strong></link-body></link> client which communicates with ActiveMQ using its own native wire protocol and provides many <link><page ri:content-title="ActiveMQ Advanced Features"></page><plain-text-link-body>advanced features</plain-text-link-body></link> beyond the standard NMS API.</li><li><link><page ri:content-title="Apache.NMS.Stomp"></page><link-body><strong>STOMP</strong></link-body></link> which connects to any <a shape="rect" href="http://stomp.codehaus.org/">STOMP Broker</a>.  Also, when coupled with <a shape="rect" href="http://stomp.codehaus.org/StompConnect">StompConnect</a>, NMS can be used to communicate with pretty much any existing MOM provider! (Or at least those that support JMS which most MOM providers do).</li><li><link><page ri:content-title="Apache.NMS.MSMQ"></page><link-body><strong>MSMQ</strong></link-body></link> is an implementation of NMS using Microsoft's MSMQ API.</li><li><link><page ri:content-title="Apache.NMS.EMS"></page><link-body><strong>EMS</strong></link-body></link> provider for talking to TIBCO's EMS message broker.  To use this, you will need to following TIBCO's licensing requirements to acquire the TIBCO client assembly DLL.  NMS does not ship with the TIBCO client assembly.</li><li><link><page ri:content-title="Apache.NMS.WCF"></page><link-body><strong>WCF</strong></link-body></link> provides support of Windows Communications Framework.</li><li><link><page ri:content-title="Apache.NMS.AMQP"></page><link-body><strong>AMQP</strong></link-body></link> is an implementation of NMS using the <a shape="rect" href="https://qpid.apache.org/components/messaging-api/index.html">Apache Qpid Messaging API</a>. AMQP 1.0 protocol support is provided by <a shape="rect" href="https://qpid.apache.org/proton/index.html">Apache Qpid Proton</a>.</li><li><link><page ri:content-title="Apache.NMS.MQTT"></page><link-body><strong>MQTT</strong></link-body></link> provider uses the publish-subscribe<span style="color: rgb(37,37,37);"> pattern that is a "light weight" messaging protocol for use on top of the </span><a shape="rect" class="mw-redirect" href="https://en.wikipedia.org/wiki/TCP/IP" title="TCP/IP">TCP/IP protocol</a><span style="color: rgb(37,37,37);">. </span></li><li><span style="color: rgb(37,37,37);"><strong><link><page ri:content-title="Apache.NMS.XMS"></page><plain-text-link-body>XMS</plain-text-link-body></link></strong> provider connects to the IBM WebSphere MQ Series broker.</span></li></ul></div>
diff --git a/nms/nms-simple-asynchronous-consumer-example.xml b/nms/nms-simple-asynchronous-consumer-example.xml
index d4a25bb..b9f8e9d 100644
--- a/nms/nms-simple-asynchronous-consumer-example.xml
+++ b/nms/nms-simple-asynchronous-consumer-example.xml
@@ -1,20 +1,19 @@
<div class="wiki-content maincontent"><p>The sample shows how to create an NMS Consumer to consume messages asynchronously. </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="13289401-17e4-4b16-9c8d-f86e8c335d45" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
+ * (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
+ * distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
@@ -41,9 +40,9 @@
// ems:tcp://tibcohost:7222
// msmq://localhost
- Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
+ Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
- Console.WriteLine("About to connect to " + connecturi);
+ Console.WriteLine("About to connect to " + connecturi);
// NOTE: ensure the nmsprovider-activemq.config file exists in the executable folder.
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
@@ -54,29 +53,29 @@
// Examples for getting a destination:
//
// Hard coded destinations:
- // IDestination destination = session.GetQueue("FOO.BAR");
+ // IDestination destination = session.GetQueue("FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = session.GetTopic("FOO.BAR");
+ // IDestination destination = session.GetTopic("FOO.BAR");
// Debug.Assert(destination is ITopic);
//
// Embedded destination type in the name:
- // IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = SessionUtil.GetDestination(session, "topic://FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "topic://FOO.BAR");
// Debug.Assert(destination is ITopic);
//
// Defaults to queue if type is not specified:
- // IDestination destination = SessionUtil.GetDestination(session, "FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "FOO.BAR");
// Debug.Assert(destination is IQueue);
//
// .NET 3.5 Supports Extension methods for a simplified syntax:
- // IDestination destination = session.GetDestination("queue://FOO.BAR");
+ // IDestination destination = session.GetDestination("queue://FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = session.GetDestination("topic://FOO.BAR");
+ // IDestination destination = session.GetDestination("topic://FOO.BAR");
// Debug.Assert(destination is ITopic);
- IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
+ IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
- Console.WriteLine("Using destination: " + destination);
+ Console.WriteLine("Using destination: " + destination);
// Create a consumer and producer
using(IMessageConsumer consumer = session.CreateConsumer(destination))
@@ -90,10 +89,10 @@
consumer.Listener += new MessageListener(OnMessage);
// Send a message
- ITextMessage request = session.CreateTextMessage("Hello World!");
- request.NMSCorrelationID = "abc";
- request.Properties["NMSXGroupID"] = "cheese";
- request.Properties["myHeader"] = "Cheddar";
+ ITextMessage request = session.CreateTextMessage("Hello World!");
+ request.NMSCorrelationID = "abc";
+ request.Properties["NMSXGroupID"] = "cheese";
+ request.Properties["myHeader"] = "Cheddar";
producer.Send(request);
@@ -102,12 +101,12 @@
if(message == null)
{
- Console.WriteLine("No message received!");
+ Console.WriteLine("No message received!");
}
else
{
- Console.WriteLine("Received message with ID: " + message.NMSMessageId);
- Console.WriteLine("Received message with text: " + message.Text);
+ Console.WriteLine("Received message with ID: " + message.NMSMessageId);
+ Console.WriteLine("Received message with text: " + message.Text);
}
}
}
@@ -121,6 +120,5 @@
}
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/nms/nms-simple-synchornous-consumer-example.xml b/nms/nms-simple-synchornous-consumer-example.xml
index 5b4ea9f..baeaa7f 100644
--- a/nms/nms-simple-synchornous-consumer-example.xml
+++ b/nms/nms-simple-synchornous-consumer-example.xml
@@ -1,19 +1,18 @@
<div class="wiki-content maincontent"><p>This example shows how to create and use an NMS Consumer to consume messages synchronously.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a85e28dd-6feb-4f0a-b75b-1e0aa658df6e" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
+ * (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
+ * distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
@@ -35,9 +34,9 @@
// ems:tcp://tibcohost:7222
// msmq://localhost
- Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
+ Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
- Console.WriteLine("About to connect to " + connecturi);
+ Console.WriteLine("About to connect to " + connecturi);
// NOTE: ensure the nmsprovider-activemq.config file exists in the executable folder.
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
@@ -48,29 +47,29 @@
// Examples for getting a destination:
//
// Hard coded destinations:
- // IDestination destination = session.GetQueue("FOO.BAR");
+ // IDestination destination = session.GetQueue("FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = session.GetTopic("FOO.BAR");
+ // IDestination destination = session.GetTopic("FOO.BAR");
// Debug.Assert(destination is ITopic);
//
// Embedded destination type in the name:
- // IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = SessionUtil.GetDestination(session, "topic://FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "topic://FOO.BAR");
// Debug.Assert(destination is ITopic);
//
// Defaults to queue if type is not specified:
- // IDestination destination = SessionUtil.GetDestination(session, "FOO.BAR");
+ // IDestination destination = SessionUtil.GetDestination(session, "FOO.BAR");
// Debug.Assert(destination is IQueue);
//
// .NET 3.5 Supports Extension methods for a simplified syntax:
- // IDestination destination = session.GetDestination("queue://FOO.BAR");
+ // IDestination destination = session.GetDestination("queue://FOO.BAR");
// Debug.Assert(destination is IQueue);
- // IDestination destination = session.GetDestination("topic://FOO.BAR");
+ // IDestination destination = session.GetDestination("topic://FOO.BAR");
// Debug.Assert(destination is ITopic);
- IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
- Console.WriteLine("Using destination: " + destination);
+ IDestination destination = SessionUtil.GetDestination(session, "queue://FOO.BAR");
+ Console.WriteLine("Using destination: " + destination);
// Create a consumer and producer
using(IMessageConsumer consumer = session.CreateConsumer(destination))
@@ -81,10 +80,10 @@
producer.DeliveryMode = MsgDeliveryMode.Persistent;
// Send a message
- ITextMessage request = session.CreateTextMessage("Hello World!");
- request.NMSCorrelationID = "abc";
- request.Properties["NMSXGroupID"] = "cheese";
- request.Properties["myHeader"] = "Cheddar";
+ ITextMessage request = session.CreateTextMessage("Hello World!");
+ request.NMSCorrelationID = "abc";
+ request.Properties["NMSXGroupID"] = "cheese";
+ request.Properties["myHeader"] = "Cheddar";
producer.Send(request);
@@ -92,12 +91,12 @@
ITextMessage message = consumer.Receive() as ITextMessage;
if(message == null)
{
- Console.WriteLine("No message received!");
+ Console.WriteLine("No message received!");
}
else
{
- Console.WriteLine("Received message with ID: " + message.NMSMessageId);
- Console.WriteLine("Received message with text: " + message.Text);
+ Console.WriteLine("Received message with ID: " + message.NMSMessageId);
+ Console.WriteLine("Received message with text: " + message.Text);
}
}
}
@@ -105,6 +104,5 @@
}
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/nms/nms-uri-configuration.xml b/nms/nms-uri-configuration.xml
index c692579..25af1a1 100644
--- a/nms/nms-uri-configuration.xml
+++ b/nms/nms-uri-configuration.xml
@@ -1,20 +1,20 @@
-<div class="wiki-content maincontent"><h2 id="NMSURIConfiguration-ConfiguringNMS">Configuring NMS</h2>
+<div class="wiki-content maincontent"><h2>Configuring NMS</h2>
<p>When working with the generic NMS API NMSConnectionFactory class you must choose via the URI which NMS provider you actually wish to use. This page documents the uri syntax and available options for the NMS providers.</p>
-<h3 id="NMSURIConfiguration-ConnectionURIParameters"><strong>Connection URI Parameters</strong></h3>
+<h3><strong>Connection URI Parameters</strong></h3>
-<h5 id="NMSURIConfiguration-ExampleConfiguration"> Example Configuration</h5>
+<h5> Example Configuration</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>cf = new NMSConnectionFactory("activemq:tcp://localhost:61616");
-</pre>
-</div></div>
+<structured-macro ac:macro-id="5c2de8cd-bb53-4569-9785-b14137b0aa5c" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+cf = new NMSConnectionFactory("activemq:tcp://localhost:61616");
+</plain-text-body></structured-macro>
-<h3 id="NMSURIConfiguration-NMSProviderOptions">NMS Provider Options</h3>
+<h3>NMS Provider Options</h3>
<p>Click on the provider name to visit the URI configuration documentation for your chosen NMS provider.</p>
-<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> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="activemq-uri-configuration.xml">activemq</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use the NMS.ActiveMQ Provider to talk to an ActiveMQ Broker. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="stomp-uri-configuration.xml">stomp</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use the NMS.Stomp Provider to talk to an Stomp Broker ActivemMQ Broker supports the Stomp protocol natively. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ems </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use the NMS.EMS Provider to talk to a TIBCO Broker. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> msmq </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use the NMS.MSMQ Provider to talk to a Microsoft Messaging (MSMQ) Broker. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wcf </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use the NMS.WCF Provider to support a Windows Communication Foundation (WCF) endpoint connection for connecting to a back-end broker. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> xms </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use the NMS.XMS Provider to talk to an IBM MQSerios Broker. This provider is currently not implemented. </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="ActiveMQ URI Configuration"></page><link-body>activemq</link-body></link> </p></td><td colspan="1" rowspan="1"><p> Use the NMS.ActiveMQ Provider to talk to an ActiveMQ Broker. </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Stomp URI Configuration"></page><link-body>stomp</link-body></link> </p></td><td colspan="1" rowspan="1"><p> Use the NMS.Stomp Provider to talk to an Stomp Broker ActivemMQ Broker supports the Stomp protocol natively. </p></td></tr><tr><td colspan="1" rowspan="1"><p> ems </p></td><td colspan="1" rowspan="1"><p> Use the NMS.EMS Provider to talk to a TIBCO Broker. </p></td></tr><tr><td colspan="1" rowspan="1"><p> msmq </p></td><td colspan="1" rowspan="1"><p> Use the NMS.MSMQ Provider to talk to a Microsoft Messaging (MSMQ) Broker. </p></td></tr><tr><td colspan="1" rowspan="1"><p> wcf </p></td><td colspan="1" rowspan="1"><p> Use the NMS.WCF Provider to support a Windows Communication Foundation (WCF) endpoint connection for connecting to a back-end broker. </p></td></tr><tr><td colspan="1" rowspan="1"><p> xms </p></td><td colspan="1" rowspan="1"><p> Use the NMS.XMS Provider to talk to an IBM MQSerios Broker. This provider is currently not implemented. </p></td></tr></tbody></table>
+
</div>
diff --git a/nms/nms.xml b/nms/nms.xml
index f7b0563..4313e5f 100644
--- a/nms/nms.xml
+++ b/nms/nms.xml
@@ -1,19 +1,20 @@
-<div class="wiki-content maincontent"><h2 id="NMS-GettingStartedwithNMS">Getting Started with NMS</h2>
+<div class="wiki-content maincontent"><h2>Getting Started with NMS</h2>
-<p>The NMS API provides your client with a common API model for working with Message Oriented Middleware, but to make use of the API you need to download one of the NMS Provider libraries. The NMS Providers libraries are what makes it possible for your code to connect to your Message Broker. Follow the links below to read more about the <a shape="rect" href="nms-providers.xml">NMS Provider</a> for your Message broker and <a shape="rect" href="download.xml">download</a> a release bundle.</p>
+<p>The NMS API provides your client with a common API model for working with Message Oriented Middleware, but to make use of the API you need to download one of the NMS Provider libraries. The NMS Providers libraries are what makes it possible for your code to connect to your Message Broker. Follow the links below to read more about the <link><page ri:content-title="NMS Providers"></page><link-body>NMS Provider</link-body></link> for your Message broker and <link><page ri:content-title="Download"></page><link-body>download</link-body></link> a release bundle.</p>
-<h3 id="NMS-NMSProviders">NMS Providers</h3><p>An NMS Provider is a .NET Assembly that provides an implementation of the NMS API that provides connectivity with a particular Messaging Service or an implementation of a standard Messaging Protocol. Currently, the following providers are available:</p><ul><li><a shape="rect" href="apachenmsactivemq.xml"><strong>ActiveMQ</strong></a> client which communicates with ActiveMQ using its own native wire protocol and provides many <a shape="rect" href="activemq-advanced-features.xml">advanced features</a> beyond the standard NMS API.</li><li><a shape="rect" href="apachenmsstomp.xml"><strong>STOMP</strong></a> which connects to any <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect" class="external-link" href="http://stomp.codehaus.org/StompConnect" rel="nofollow">StompConnect</a>, NMS can be used to communicate with pretty much any existing MOM provider! (Or at least those that support JMS which most MOM providers do).</li><li><a shape="rect" href="apachenmsmsmq.xml"><strong>MSMQ</strong></a> is an implementation of NMS using Microsoft's MSMQ API.</li><li><a shape="rect" href="apachenmsems.xml"><strong>EMS</strong></a> provider for talking to TIBCO's EMS message broker.  To use this, you will need to following TIBCO's licensing requirements to acquire the TIBCO client assembly DLL.  NMS does not ship with the TIBCO client assembly.</li><li><a shape="rect" href="apachenmswcf.xml"><strong>WCF</strong></a> provides support of Windows Communications Framework.</li><li><a shape="rect" href="apachenmsamqp.xml"><strong>AMQP</strong></a> is an implementation of NMS using the <a shape="rect" class="external-link" href="https://qpid.apache.org/components/messaging-api/index.html">Apache Qpid Messaging API</a>. AMQP 1.0 protocol support is provided by <a shape="rect" class="external-link" href="https://qpid.apache.org/proton/index.html">Apache Qpid Proton</a>.</li><li><a shape="rect" href="apachenmsmqtt.xml"><strong>MQTT</strong></a> provider uses the publish-subscribe<span style="color: rgb(37,37,37);"> pattern that is a "light weight" messaging protocol for use on top of the </span><a shape="rect" class="external-link" href="https://en.wikipedia.org/wiki/TCP/IP" rel="nofollow" title="TCP/IP">TCP/IP protocol</a><span style="color: rgb(37,37,37);">. </span></li><li><span style="color: rgb(37,37,37);"><strong><a shape="rect" href="apachenmsxms.xml">XMS</a></strong> provider connects to the IBM WebSphere MQ Series broker.</span></li></ul>
+<structured-macro ac:macro-id="956dc71e-79c5-40f3-84ea-b51e73ee1328" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="NMS Providers"></page></link></parameter></structured-macro>
-<h2 id="NMS-Buildingthecode">Building the code</h2>
+<h2>Building the code</h2>
-<p>While there are binary distributions available for all the <a shape="rect" href="nms-providers.xml">NMS Providers</a> you sometimes might want to build the code from trunk in order to test out the latest changes or fixes. On Windows you can use Visual Studio to build the code. On Linux or OS X you can use <a shape="rect" class="external-link" href="http://www.mono-project.com" rel="nofollow">Mono</a>.</p>
+<p>While there are binary distributions available for all the <link><page ri:content-title="NMS Providers"></page></link> you sometimes might want to build the code from trunk in order to test out the latest changes or fixes. On Windows you can use Visual Studio to build the code. On Linux or OS X you can use <a shape="rect" href="http://www.mono-project.com">Mono</a>.</p>
-<p>The build uses <a shape="rect" class="external-link" href="http://nant.sourceforge.net/" rel="nofollow">NAnt</a> which both work on .Net and Mono.  You will need to have NAnt 0.91-Alpha2 or later.</p>
+<p>The build uses <a shape="rect" href="http://nant.sourceforge.net/">NAnt</a> which both work on .Net and Mono.  You will need to have NAnt 0.91-Alpha2 or later.</p>
-<p>For more help see the <a shape="rect" class="external-link" href="http://activemq.apache.org/nms/building.html">Building NMS</a> guide.</p>
+<p>For more help see the <a shape="rect" href="http://activemq.apache.org/nms/building.html">Building NMS</a> guide.</p>
-<h2 id="NMS-AlternativestoNMS">Alternatives to NMS</h2>
+<h2>Alternatives to NMS</h2>
-<p>There are currently a few alternatives to using NMS and working with ActiveMQ in .NET applications however the <a shape="rect" href="apachenmsactivemq.xml">NMS ActiveMQ Provider</a> is very feature rich and we recommend it as your starting point for .NET ActiveMQ inter-op.</p>
-<ul><li>use the <a shape="rect" class="external-link" href="http://stomp.codehaus.org/DotNet" rel="nofollow">pure C# Stomp client</a> to access ActiveMQ from .Net using a lightweight client.</li><li>use the ActiveMQ Java client from C# and .Net using IKVM. <a shape="rect" class="external-link" href="http://dotnetjunkies.com/WebLog/csteen/archive/2004/08/20/22813.aspx" rel="nofollow">More information</a>.</li><li>use the <a shape="rect" class="external-link" href="http://activemq.apache.org/rest.html">ActiveMQ REST</a> API via HTTP</li><li>use the <a shape="rect" class="external-link" href="http://activemq.apache.org/c-integration.html">ActiveMQ C Integration</a> to reuse the C/C++ library.</li></ul></div>
+<p>There are currently a few alternatives to using NMS and working with ActiveMQ in .NET applications however the <link><page ri:content-title="Apache.NMS.ActiveMQ"></page><link-body>NMS ActiveMQ Provider</link-body></link> is very feature rich and we recommend it as your starting point for .NET ActiveMQ inter-op.</p>
+<ul><li>use the <a shape="rect" href="http://stomp.codehaus.org/DotNet">pure C# Stomp client</a> to access ActiveMQ from .Net using a lightweight client.</li><li>use the ActiveMQ Java client from C# and .Net using IKVM. <a shape="rect" href="http://dotnetjunkies.com/WebLog/csteen/archive/2004/08/20/22813.aspx">More information</a>.</li><li>use the <a shape="rect" href="http://activemq.apache.org/rest.html">ActiveMQ REST</a> API via HTTP</li><li>use the <a shape="rect" href="http://activemq.apache.org/c-integration.html">ActiveMQ C Integration</a> to reuse the C/C++ library.</li></ul>
+</div>
diff --git a/nms/overview.xml b/nms/overview.xml
index 3b873ee..9af7ca9 100644
--- a/nms/overview.xml
+++ b/nms/overview.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="download.xml">Download</a></li><li><a shape="rect" href="nms.xml">NMS</a></li><li><a shape="rect" href="using-nms.xml">Using NMS</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="99e93709-b5ee-4ac2-a9f5-c8417534e6e8" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/privacy-policy.xml b/nms/privacy-policy.xml
index b6db1d7..e37a397 100644
--- a/nms/privacy-policy.xml
+++ b/nms/privacy-policy.xml
@@ -3,7 +3,7 @@
<ol><li>The IP address from which you access the website;</li><li>The type of browser and operating system you use to access our site;</li><li>The date and time you access our site;</li><li>The pages you visit; and</li><li>The addresses of pages from where you followed a link to our site.</li></ol>
-<p>Part of this information is gathered using a tracking cookie set by the <a shape="rect" class="external-link" href="http://www.google.com/analytics/" rel="nofollow">Google Analytics</a> service and handled by Google as described in their <a shape="rect" class="external-link" href="http://www.google.com/privacy.html" rel="nofollow">privacy policy</a>. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.</p>
+<p>Part of this information is gathered using a tracking cookie set by the <a shape="rect" href="http://www.google.com/analytics/">Google Analytics</a> service and handled by Google as described in their <a shape="rect" href="http://www.google.com/privacy.html">privacy policy</a>. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.</p>
<p>We use the gathered information to help us make our site more useful to visitors and to better understand how and when our site is used. We do not track or collect personally identifiable information or associate gathered data with any personally identifying information from other sources.</p>
diff --git a/nms/quicklinks.xml b/nms/quicklinks.xml
index 98a4d78..0cd82a6 100644
--- a/nms/quicklinks.xml
+++ b/nms/quicklinks.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><a shape="rect" href="download.xml">Download</a> | <a shape="rect" href="nms-api.xml">API</a> | <a shape="rect" href="source.xml">Source</a> | <a shape="rect" class="external-link" href="http://activemq.apache.org/discussion-forums.html">Forums</a> | <a shape="rect" class="external-link" href="http://activemq.apache.org/support.html">Support</a></p></div>
+<div class="wiki-content maincontent"><p><link><page ri:content-title="Download"></page></link> | <link><page ri:content-title="NMS API"></page><link-body>API</link-body></link> | <link><page ri:content-title="Source"></page></link> | <a shape="rect" href="http://activemq.apache.org/discussion-forums.html">Forums</a> | <a shape="rect" href="http://activemq.apache.org/support.html">Support</a></p></div>
diff --git a/nms/should-i-pool-connections.xml b/nms/should-i-pool-connections.xml
index befc040..163dc93 100644
--- a/nms/should-i-pool-connections.xml
+++ b/nms/should-i-pool-connections.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="ShouldIpoolconnections-ShouldIpoolconnections?">Should I pool connections?</h2>
+<div class="wiki-content maincontent"><h2>Should I pool connections?</h2>
-<p>The Java documentation talks about <a shape="rect" class="external-link" href="http://activemq.apache.org/how-do-i-use-jms-efficiently.html">how to use JMS efficiently</a>. So when using .NET should you worry about pooling?</p>
+<p>The Java documentation talks about <a shape="rect" href="http://activemq.apache.org/how-do-i-use-jms-efficiently.html">how to use JMS efficiently</a>. So when using .NET should you worry about pooling?</p>
<p>Its worth thinking about - but it depends a little on your application. If its a client UI then just have a single connection and a few sessions and you'll be fine. </p>
diff --git a/nms/site.xml b/nms/site.xml
index 170b4d9..1fceffc 100644
--- a/nms/site.xml
+++ b/nms/site.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="banner.xml">Banner</a></li><li><a shape="rect" href="navigation.xml">Navigation</a><ul class="childpages-macro"><li><a shape="rect" href="support.xml">Support</a></li></ul></li><li><a shape="rect" href="quicklinks.xml">QuickLinks</a></li><li><a shape="rect" href="siteindex.xml">SiteIndex</a></li><li><a shape="rect" href="sitemap.xml">SiteMap</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="9c67c770-7259-4d74-80d0-adc8136932ab" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/nms/siteindex.xml b/nms/siteindex.xml
index f08b6dd..906aad1 100644
--- a/nms/siteindex.xml
+++ b/nms/siteindex.xml
@@ -1,427 +1,3 @@
<div class="wiki-content maincontent">
-<h2>Space Index</h2>
-
-<p>
-<table class="grid" width="99%" cellspacing="0"><tr><td colspan="2" rowspan="1">
- <table width="100%"><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-0-9">0-9</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-A">A</a> ... 84</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-B">B</a> ... 2</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-C">C</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-D">D</a> ... 2</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-E">E</a> ... 5</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-F">F</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-G">G</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-H">H</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-I">I</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-J">J</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-K">K</a> ... 0</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-L">L</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-M">M</a> ... 4</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-N">N</a> ... 10</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-O">O</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-P">P</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Q">Q</a> ... 1</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-R">R</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-S">S</a> ... 13</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-T">T</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-U">U</a> ... 1</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-V">V</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-W">W</a> ... 3</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-X">X</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Y">Y</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Z">Z</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-%21@%23%24">!@#$</a> ... 0</td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1"> </td></tr></table>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-0-9"></a>0-9</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-A"></a>A</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+.NET+1.1.0+Release">ActiveMQ .NET 1.1.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release: Support for Fai</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+.NET+1.2.0+Release">ActiveMQ .NET 1.2.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.1.0 release. Some highlights for this release. Addition of ConnectionMeteData to the Connection API. Addition of QueueBrowser t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+.NET+1.3.0+Release">ActiveMQ .NET 1.3.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.2.0 release. Some highlights for this release. Addition of QueueBrowser support to NMS.ActiveMQ Addition of SSL Support for NMS</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+.NET+1.4.0+Release">ActiveMQ .NET 1.4.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.3.0 release. Some highlights for this release. Improved URI handling in all NMS clients. Improved handling of Request Timeout s</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Advanced+Features">ActiveMQ Advanced Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The NMS.ActiveMQ client provides several features in addition to fully implementing the NMS API. The features are documented here.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Advisory+Message+Examples">ActiveMQ Advisory Message Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Async+Sends">ActiveMQ Async Sends</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background Apache.NMS.ActiveMQ supports sending messages to a broker in sync or async mode. The mode used has a huge impact in the latency of the send call. Since latency is typically a huge factor in the throughput that can achieved by producer, using as</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Build+Notes">ActiveMQ Build Notes</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Consumer+Dispatch+Async">ActiveMQ Consumer Dispatch Async</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview In AMQ4 onwards, the choice of a broker performing synchronous or asynchronous dispatch to a consumer has become more configurable. It is now configured as a default value on the connection URI, Connection and ConnectionFactory together with bein</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Consumer+Features">ActiveMQ Consumer Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Consumer+Priority">ActiveMQ Consumer Priority</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background As well as having a pluggable dispatch policy (e.g. round robin etc), we now support consumer priorities. This allows us to weight consumers to optimise network hops. For example, you typically want a broker to send messages to regular NMS cons</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Delay+and+Schedule+Message+Feature">ActiveMQ Delay and Schedule Message Feature</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ from version 5.4 has an optional persistent scheduler built into the ActiveMQ message broker. It is enabled by setting the broker schedulerSupport attribute to true in the xml configuration. An ActiveMQ client can take advantage of a delayed deli</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Destination+Features">ActiveMQ Destination Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Destination+Management">ActiveMQ Destination Management</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Apache.NMS.ActiveMQ client provides some additional features beyond the standard NMS API. One such feature is the ability to delete a given destination on the Broker. This can be useful during testing when you want to start the test with a destinati</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Destination+Options">ActiveMQ Destination Options</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background Destination Options are a way to provide extended configuration options to a NMS consumer without having to extend the NMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on. Consumer Opt</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Downloads">ActiveMQ Downloads</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Release Date NMS API Rev Apache.NMS.ActiveMQ v1.7.2 04/07/2016 v1.7.1 Apache.NMS.ActiveMQ v1.7.1 10/05/2015 v1.7.1 Apache.NMS.ActiveMQ v1.7.0 01/16/2015 v1.7.0 Apache.NMS.ActiveMQ v1.6.5 02/05/2015 v1.6.0 Apache.NMS.ActiveMQ v1.6.4 09/14/2014 </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Enumerate+Destination+using+Advisory+Messages">ActiveMQ Enumerate Destination using Advisory Messages</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Enumerating Available Destinations using Advisory Messages This example shows you how to consume Advisory Messages from the Broker to enumerate various destination types. /* * Licensed to the Apache Software Foundation (ASF) under one or more * contributo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Examples">ActiveMQ Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Exclusive+Consumers">ActiveMQ Exclusive Consumers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Exclusive Consumer We have a new feature in version 4.x and above called Exclusive Consumer or Exclusive Queues which avoids the end user having to pin anything. The broker will pick a single MessageConsumer to get all the messages for a queue to ensure o</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+FAQ">ActiveMQ FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Message+Dispatching+Features">ActiveMQ Message Dispatching Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Message+Features">ActiveMQ Message Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Mirrored+Queues">ActiveMQ Mirrored Queues</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Mirrored Queues</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Retroactive+Consumers">ActiveMQ Retroactive Consumers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background A retroactive consumer is just a regular NMS consumer who indicates that at the start of a subscription every attempt should be used to go back in time and send any old messages (or the last message sent on that topic) that the consumer may hav</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+URI+Configuration">ActiveMQ URI Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring NMS.ActiveMQ All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every facet of your NMS.ActiveMQ client. The tables below show the comprehensive set</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Virtual+Destinations">ActiveMQ Virtual Destinations</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Virtual Destinations</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/ActiveMQ+Wildcards">ActiveMQ Wildcards</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Wildcards</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/AMQP+Build+Notes">AMQP Build Notes</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Default build Executing nant in the project home directory will produce two builds: Debug/Release .NET 2.0 x86 in the \net-2.0 folder built with Visual Studio 2008 Debug/Release .NET 4.0 x86 in the \net-4.0 folder built with Visual Studio 2010 Your build </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/AMQP+Downloads">AMQP Downloads</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/AMQP+Examples">AMQP Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">HelloWorld.cs The source kit for the Apache.NMS.AMQP provider includes a HelloWorld project. HelloWorld requires an AMQP 1.0 broker (either ActiveMQ or Qpidd) to be running on localhost:5672. Of course you may specify a different URI to select any broker.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/AMQP+FAQ">AMQP FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS">Apache.NMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">An Overview of NMS The NMS API (.Net Message Service API) providers a standard .NET interface to Messaging Systems. There could be multiple implementations to different providers (including MSMQ). The NMS API This allows you to build .NET applications in </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+1.5.0+Release">Apache.NMS 1.5.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.4.0 release. Some highlights for this release. NMS API New Optional .NET Transaction Specific Connection classes that allow a c</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+ActiveMQ+v1.1.0">Apache.NMS ActiveMQ v1.1.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS.ActiveMQ project, and all provider implementation projects. Following are some highlights of this release: Suppor</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.1.0">Apache.NMS API v1.1.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release: Improved API Do</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.2.0">Apache.NMS API v1.2.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS API and fixes several bugs found in the 1.1.0 release. Some highlights for this release. Addition of IConnectionMeteData to the Connection API. Addition of IQueueBrowser to the Sessi</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.3.0">Apache.NMS API v1.3.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS API and fixes several bugs found in the 1.2.0 release. Some highlights for this release. Improved API Documentation. Many new Unit Tests added to the Test Suite. Many bug fixes. API </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.4.0">Apache.NMS API v1.4.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS API and fixes several bugs found in the 1.3.0 release. Some highlights for this release. Improved URI handling in all NMS clients. Added a new SetBytes method to IMapMessage. Added a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.5.0">Apache.NMS API v1.5.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS API. NMS API Updates New Optional .NET Transaction Specific Connection classes that allow a client to offer support for operations within MS .NET Distributed Transactions. API Documen</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.5.1">Apache.NMS API v1.5.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bugfix release of the NMS API there are no API changes in this release. NMS fixes Fixes a bug that can cause the Message properties object to marshal to a byte array that is much larger than needed which adds unwanted overhead</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.6.0">Apache.NMS API v1.6.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a major release of the NMS API which adds some new APIs and fixes some minor bugs in the NMS API libraries common code. Added Recover method to ISession. Added new events to ISession for Transaction begin, commit and rollback. A</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.7.0">Apache.NMS API v1.7.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a major release of the NMS API which adds some new APIs and fixes some minor bugs in the NMS API libraries common code. Added IDisposable as a base of IDestination. Added some improvements to the Unit tests framework. Added some</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+API+v1.7.1">Apache.NMS API v1.7.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"> New and Noteworthy This is a minor release of the NMS API which adds a few minor fixes for NMS Providers operating in MSDTC Transactions. API Documentation Refer to the API for this release here Download Here Description Download Link PGP Signature File</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+EMS+v1.1.0">Apache.NMS EMS v1.1.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The 1.1.0 release is a major milestone for the Apache NMS EMS client. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release: Improved API</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS+MSMQ+v1.1.0">Apache.NMS MSMQ v1.1.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The 1.1.0 release is a major milestone for the Apache NMS MSMQ client. It is the first official release of the main Apache.NMS project, and all provider implementation projects. Following are some highlights of this release: Improved AP</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ">Apache.NMS.ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The ActiveMQ NMS client is a .NET client that communicates with the ActiveMQ broker using its native Openwire protocol. This client supports advanced features such as Failover, Discovery, SSL, and Message Compression. This section of the NMS site provides</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.2.0">Apache.NMS.ActiveMQ v1.2.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS ActiveMQ library and fixes several bugs found in the 1.1.0 release. Some highlights for this release. Addition of ConnectionMeteData to the Connection API. Addition of QueueBrowser t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.3.0">Apache.NMS.ActiveMQ v1.3.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS ActiveMQ library and fixes several bugs found in the 1.2.0 release. Some highlights for this release. Addition of QueueBrowser support Addition of SSL Support Improvements to the Fai</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.4.0">Apache.NMS.ActiveMQ v1.4.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS ActiveMQ library and fixes several bugs found in the 1.3.0 release. Some highlights for this release. Improved URI handling in all NMS clients. Improved handling of Request Timeout s</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.4.1">Apache.NMS.ActiveMQ v1.4.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS.ActiveMQ library and fixes several bugs found in the 1.3.0 release. Some highlights for this release. Improved URI handling. Many bug fixes. API Refer to the API for this release her</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.5.0">Apache.NMS.ActiveMQ v1.5.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS ActiveMQ library and fixes several bugs found in the 1.4.0 release. New in this version New startupMaxReconnectAttempts option in the failover transport. Fixed a memory leak in the In</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.5.1">Apache.NMS.ActiveMQ v1.5.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS.ActiveMQ API. NMS API Updates Many fixes for the MS Distributed Transaction support along with other minor bug fixes for issues found since the initial v1.5.0 release. API Documentati</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.5.2">Apache.NMS.ActiveMQ v1.5.2</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new fixes to the NMS.ActiveMQ API. NMS.ActiveMQ Updates This release focuses on performance and stability fixes to the ActiveMQ provider. No new features were added in this release. See the release notes bel</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.5.3">Apache.NMS.ActiveMQ v1.5.3</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new fixes to the NMS.ActiveMQ API. NMS.ActiveMQ Updates This release focuses on stability fixes to the ActiveMQ provider. No new features were added in this release. See the release notes below for a list of</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.5.4">Apache.NMS.ActiveMQ v1.5.4</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new fixes to the NMS.ActiveMQ API. NMS.ActiveMQ Updates This release focuses on stability fixes to the ActiveMQ provider. No new features were added in this release. See the release notes below for a list of</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.5.5">Apache.NMS.ActiveMQ v1.5.5</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new fixes to the NMS.ActiveMQ API. Sending to non-existent temp queue causes consumer to shutdown Consumers frequently fail to reconnect after broker outage/failover. FailoverTransport doesn't trigger a reco</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.5.6">Apache.NMS.ActiveMQ v1.5.6</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new fixes to the NMS.ActiveMQ API. Adds compression support to the ObjectMessage payload Fixes an issue in Message marshaling when tight-marshaling is enabled. NMS.ActiveMQ Updates This release focuses on st</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.6.0">Apache.NMS.ActiveMQ v1.6.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features and fixes to the NMS.ActiveMQ API. NMS.ActiveMQ Updates This release adds several new features to the ActiveMQ client and fixes many bugs that have been reported since the last release. Adds sup</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.6.1">Apache.NMS.ActiveMQ v1.6.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bugfix release for the NMS.ActiveMQ client library. Along with some bug fixes though we've also added support for better discovery transport agents and we now support HTTP discovery using the ActiveMQ broker's HTTP discovery r</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.6.2">Apache.NMS.ActiveMQ v1.6.2</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"> New and Noteworthy This is a bugfix release for the NMS.ActiveMQ client library. Along with some bug fixes though we've also added support for better discovery transport agents and we now support HTTP discovery using the ActiveMQ broker's HTTP discovery</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.6.3">Apache.NMS.ActiveMQ v1.6.3</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bugfix release that addresses a few stability issues and improves the handling of Message Consumer instances that operate inside of Sessions in Transacted mode. API Documentation Refer to the API for this release here Download</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.6.4">Apache.NMS.ActiveMQ v1.6.4</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bugfix release that addresses a few stability issues and improves the handling of Message Consumer instances that operate inside of Sessions in Transacted mode as well as some fixes for potential deadlocks that could occur dur</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.6.5">Apache.NMS.ActiveMQ v1.6.5</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a small bugfix release that corrects an issue found in the OpenWire tight marshal code that can cause a connection to fail, also a fix for an incorrect redelivery count on some messages was applied. API Documentation Refer to th</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.7.0">Apache.NMS.ActiveMQ v1.7.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is the first release of the Apache.NMS.ActiveMQ 1.7.0 line. This release is based on the Apache.NMS API v1.7.0 and includes several fixes and updates over the 1.6.x line. The DotNetZlib dependency has been updated to the latest r</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.7.1">Apache.NMS.ActiveMQ v1.7.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bugfix release of the Apache.NMS.ActiveMQ 1.7.x line. This release is based on the Apache.NMS API v1.7.1 and includes several fixes and updates over the 1.7.0 release. A fix for an issue where the client could falsely filter</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.ActiveMQ+v1.7.2">Apache.NMS.ActiveMQ v1.7.2</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a bugfix release of the Apache.NMS.ActiveMQ 1.7.x line. This release is based on the Apache.NMS API v1.7.1 and includes several fixes and updates over the 1.7.1 release. API Documentation Refer to the API for this release here</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.AMQP">Apache.NMS.AMQP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Apache NMS AMQP client provides an NMS layer on top of the Apache Qpid messaging client API. AMQP 1.0 support is provided by Apache Qpid Proton. AMQP Build Notes AMQP Downloads AMQP Examples AMQP FAQ </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.EMS">Apache.NMS.EMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Apache.NMS.EMS client provider for talking to TIBCO's EMS message broker. To use this, you will need to following TIBCO's licensing requirements to acquire the TIBCO client assembly DLL. NMS does not ship with the TIBCO client assembly.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.MQTT">Apache.NMS.MQTT</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Apache.NMS.MQTT client provider for using the publish-subscribe pattern over a lightweight protocol on top of TCP/IP.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.MSMQ">Apache.NMS.MSMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Apache.NMS.MSMQ client provides an NMS layer on top of the MSMQ messaging API.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp">Apache.NMS.Stomp</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The NMS Stomp client is a small lightweight .NET client that can send and receive messages from any Stomp http://stomp.codehaus.org/ based message broker. The NMS Stomp client currently supports the Stomp 1.0 protocol specification.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp+v1.2.0">Apache.NMS.Stomp v1.2.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is the first official release of the NMS Stomp client library. This library implements much of the NMS API although some features aren't possible due to limitations in the Stomp protocol. API Refer to the API for this release here </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp+v1.3.0">Apache.NMS.Stomp v1.3.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS Stomp library and fixes several bugs found in the 1.2.0 release. Some highlights for this release. Addition of SSL Support Improvements to the Failover Transport. Improved API Docume</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp+v1.4.0">Apache.NMS.Stomp v1.4.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS Stomp library and fixes several bugs found in the 1.3.0 release. Some highlights for this release. Improved URI handling in all NMS clients. Improved handling of Request Timeout sett</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp+v1.5.0">Apache.NMS.Stomp v1.5.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS Stomp client library and fixes several bugs found in the 1.4.0 release. New in this release: Support for the current changes in the Stomp 1.1 draft specification. Improved Inactivity </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp+v1.5.1">Apache.NMS.Stomp v1.5.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release adds some great new features to the NMS client libraries and fixes several bugs found in the 1.4.0 release. Some highlights for this release. New in this release. Fixed a memory leak in the Inactivity Monitoring code. Fixe</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp+v1.5.2">Apache.NMS.Stomp v1.5.2</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The release focuses on performance and stability fixes for issues found in the 1.5.1 release as well as addressing a compatibility issue found when connecting to Stomp v1.1 compliant brokers. API Documentation Refer to the API for this </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp+v1.5.3">Apache.NMS.Stomp v1.5.3</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The release focuses on performance and stability fixes for issues found in the 1.5.2 release as well as addressing a compatibility issue found when connecting to Stomp v1.1 compliant brokers. Additionally some improvements in fail-over </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.Stomp+v1.5.4">Apache.NMS.Stomp v1.5.4</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The release includes a fix for exceptions that were being seen on Windows OS's configured with Non-US culture settings. API Documentation Refer to the API for this release here Apache.NMS.Stomp Client Downloads Description Download Link</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.WCF">Apache.NMS.WCF</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">NMS provider for use with the Windows Communication Framework (WCF).</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.WCF+v1.1.0">Apache.NMS.WCF v1.1.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy The 1.1.0 release is a major milestone for the Apache NMS project. It is the first official release of the main Apache.NMS project, and all provider implementation projects. API Refer to the API for this release here Download Here Descr</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Apache.NMS.XMS">Apache.NMS.XMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Apache.NMS.XMS client provider for talking to IBM's WebSphere MQ Series message broker. To use this, you will need to following IBM's licensing requirements to acquire the MQSeries client assembly DLL. NMS does not ship with the MQSeries client assemb</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Are+there+more+FAQ+Entries">Are there more FAQ Entries</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Are there more FAQ Entries? Yes, see the ActiveMQ Main FAQ http://activemq.apache.org/faq.html</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Articles">Articles</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Articles that cover various NMS related topics. Using SSL with Apache.NMS.ActiveMQ http://timbish.blogspot.com/2010/04/ussing-ssl-in-nmsactivemq.html Messaging with .NET and ActiveMQ http://remark.wordpress.com/articles/messaging-with-net-and-activemq/ Im</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-B"></a>B</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Banner">Banner</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"><div id="asf_logo"> <div id="activemq_logo"> <a style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="">ActiveMQ</a> <a style="float:right; width:210px;display:bl</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Building">Building</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Building NMS Currently our main build tool for NMS is NAnt http://nant.sourceforge.net/. Install Mono http://www.mono-project.com On some operating systems (e.g. OS X), you may need to point the PKG_CONFIG_PATH environment variable at the mono packages ex</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-C"></a>C</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Community">Community</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-D"></a>D</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Developers">Developers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Download</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Download">Download</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache.NMS Project Downloads Here you can Download the Apache.NMS API for .NET and the various Apache.NMS Provider Libraries such as Apache.NMS.ActiveMQ. Releases that are marked as in-progress won't be directly downloadable however there may be a SNAPSHO</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-E"></a>E</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/EMS+Build+Notes">EMS Build Notes</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/EMS+Downloads">EMS Downloads</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Release Date NMS API Rev Apache.NMS EMS v1.1.0 07/12/2009 v1.1.0</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/EMS+Examples">EMS Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/EMS+FAQ">EMS FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Examples">Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Examples The following example gives a brief demonstration for connecting, sending and receiving a message using NMS. using System; using Apache.NMS; using Apache.NMS.Util; namespace Apache.NMS.ActiveMQ.Test { public class TestMain { public static void Ma</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-F"></a>F</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/FAQ">FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">General Questions Using NMS FAQ NMS FAQ Using NMS.ActiveMQ FAQ ActiveMQ FAQ Using NMS.Stomp FAQ Using NMS.MSMQ FAQ Using NMS.EMS FAQ Using NMS.WCF FAQ</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-G"></a>G</h4>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-H"></a>H</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-I"></a>I</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-homepage" title="Home page">Home page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Index">Index</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Welcome to the Apache NMS project, the .NET Messaging API. NMS API Overview The NMS API This allows you to build .NET applications in C#, VB, or any other .NET language, using a single API to connect to multiple different providers using a JMS style API. </div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-J"></a>J</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-K"></a>K</h4>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-L"></a>L</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-M"></a>M</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/MSMQ+Build+Notes">MSMQ Build Notes</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/MSMQ+Downloads">MSMQ Downloads</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Release Date NMS API Rev Apache.NMS MSMQ v1.1.0 07/12/2009 v1.1.0</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/MSMQ+Examples">MSMQ Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/MSMQ+FAQ">MSMQ FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-N"></a>N</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Navigation">Navigation</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview Home FAQ Download Using NMS NMS Overview Getting Started NMS API Reference ActiveMQ Stomp MSMQ Tibco EMS WCF Search <form action="http://www.google.com/cse" id="cse-search-box"> <div> <input type="hidden" name="cx" value="007878419884033443453:m5</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS">NMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Getting Started with NMS The NMS API provides your client with a common API model for working with Message Oriented Middleware, but to make use of the API you need to download one of the NMS Provider libraries. The NMS Providers libraries are what makes i</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS+API">NMS API</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The NMS documentation has been generated using Microsoft's Sandcastle http://sandcastle.codeplex.com/ open source product. The Sandcastle Styles http://sandcastlestyles.codeplex.com/ project was used to enhance the output generated from the current releas</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS+API+Downloads">NMS API Downloads</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Release Date Apache.NMS API v1.7.1 09/04/2015 Apache.NMS API v1.7.0 01/08/2015 Apache.NMS API v1.6.0 05/24/2013 Apache.NMS API v1.5.1 07/06/2012 Apache.NMS API v1.5.0 01/10/2011 Apache.NMS API v1.4.0 09/10/2010 Apache.NMS API v1.3.0 05/14/2010</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS+Examples">NMS Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This is where you will find examples of how to use the NMS API. These examples demonstrate using the NMS API generically and are limited to features exposed directly through the API model. For examples covering more advanced features of a specific NMS Pro</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS+FAQ">NMS FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS+Providers">NMS Providers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">NMS Providers An NMS Provider is a .NET Assembly that provides an implementation of the NMS API that provides connectivity with a particular Messaging Service or an implementation of a standard Messaging Protocol. Currently, the following providers are av</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS+Simple+Asynchronous+Consumer+Example">NMS Simple Asynchronous Consumer Example</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The sample shows how to create an NMS Consumer to consume messages asynchronously. /* * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed with * this work for additional in</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS+Simple+Synchornous+Consumer+Example">NMS Simple Synchornous Consumer Example</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This example shows how to create and use an NMS Consumer to consume messages synchronously. /* * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed with * this work for addi</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/NMS+URI+Configuration">NMS URI Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring NMS When working with the generic NMS API NMSConnectionFactory class you must choose via the URI which NMS provider you actually wish to use. This page documents the uri syntax and available options for the NMS providers. Connection URI Parame</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-O"></a>O</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Overview">Overview</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-P"></a>P</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Privacy+Policy">Privacy Policy</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Information about your use of this website is collected using server access logs and a tracking cookie. The collected information consists of the following: The IP address from which you access the website; The type of browser and operating system you use</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Q"></a>Q</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/QuickLinks">QuickLinks</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Download | API | Source | Forums http://activemq.apache.org/discussion-forums.html | Support http://activemq.apache.org/support.html</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-R"></a>R</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-S"></a>S</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Should+I+pool+connections">Should I pool connections</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Should I pool connections? The Java documentation talks about how to use JMS efficiently http://activemq.apache.org/how-do-i-use-jms-efficiently.html. So when using .NET should you worry about pooling? Its worth thinking about - but it depends a little on</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Site">Site</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/SiteIndex">SiteIndex</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">{index}{index}</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/SiteMap">SiteMap</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Index</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Source">Source</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Web Browsing of Git repositories Browse the source tree of each of the NMS projects directly: https://git-wip-us.apache.org/repos/asf/activemq-nms-api.git https://git-wip-us.apache.org/repos/asf/activemq-nms-openwire.git https://git-wip-us.apache.org/repo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Stomp+Advanced+Features">Stomp Advanced Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Stomp+Build+Notes">Stomp Build Notes</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Stomp+Delayed+and+Scheduled+Message+Feature">Stomp Delayed and Scheduled Message Feature</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This documentation only applies when the Stomp client is connected to an ActiveMQ Broker v5.4 and above. ActiveMQ Delay and Schedule Message Feature</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Stomp+Downloads">Stomp Downloads</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Release Date NMS API Rev Apache.NMS.Stomp v1.5.4 10/26/2013 v1.5.1 Apache.NMS.Stomp v1.5.3 08/30/2012 v1.5.1 Apache.NMS.Stomp v1.5.2 11/19/2011 v1.5.0 Apache.NMS.Stomp v1.5.1 01/31/2011 v1.5.0 Apache.NMS.Stomp v1.5.0 01/14/2011 v1.5.0 Apache.N</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Stomp+FAQ">Stomp FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Stomp+Message+Features">Stomp Message Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Stomp+URI+Configuration">Stomp URI Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring NMS.Stomp All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every facet of your NMS.Stomp client. The tables below show the comprehensive set of pa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Support">Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Getting Help If you are experiencing problems using NMS then please first try the FAQ. If you cannot find your issue then report your problem to our Issue Tracker http://issues.apache.org/activemq/browse/AMQNET You may also find it useful to discuss your </div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-T"></a>T</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-U"></a>U</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/Using+NMS">Using NMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Using NMS Getting Started API Reference Examples ActiveMQ URI Configuration</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-V"></a>V</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-W"></a>W</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/WCF+Downloads">WCF Downloads</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Release Date NMS API Rev Apache.NMS.WCF v1.1.0 07/12/2009 v1.1.0</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/WCF+Examples">WCF Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/NMS/What+is+NMS">What is NMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What is NMS? NMS is the open source .Net Messaging API. This allows you to build .Net applications in C# or VB to a single API which can then be used to connect to multiple different Message Brokers.</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-X"></a>X</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Y"></a>Y</h4>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Z"></a>Z</h4>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-%21@%23%24"></a>!@#$</h4>
- </td></tr></table>
-</p></div>
+<structured-macro ac:macro-id="c63f538a-8989-4f35-804a-408dd41dbf4f" ac:name="unmigrated-inline-wiki-markup" ac:schema-version="1"><plain-text-body>{index}{index}</plain-text-body></structured-macro></div>
diff --git a/nms/sitemap.xml b/nms/sitemap.xml
index 7453512..a52f8aa 100644
--- a/nms/sitemap.xml
+++ b/nms/sitemap.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="apachenms.xml">Apache.NMS</a><ul class="childpages-macro"><li><a shape="rect" href="nms-api.xml">NMS API</a></li><li><a shape="rect" href="nms-api-downloads.xml">NMS API Downloads</a><ul class="childpages-macro"><li><a shape="rect" href="apachenms-api-v110.xml">Apache.NMS API v1.1.0</a></li><li><a shape="rect" href="apachenms-api-v120.xml">Apache.NMS API v1.2.0</a></li><li><a shape="rect" href="apachenms-api-v130.xml">Apache.NMS API v1.3.0</a></li><li><a shape="rect" href="apachenms-api-v140.xml">Apache.NMS API v1.4.0</a></li><li><a shape="rect" href="apachenms-api-v150.xml">Apache.NMS API v1.5.0</a></li><li><a shape="rect" href="apachenms-api-v151.xml">Apache.NMS API v1.5.1</a></li><li><a shape="rect" href="apachenms-api-v160.xml">Apache.NMS API v1.6.0</a></li><li><a shape="rect" href="apachenms-api-v170.xml">Apache.NMS API v1.7.0</a></li><li><a shape="rect" href="apachenms-api-v171.xml">Apache.NMS API v1.7.1</a></li></ul></li><li><a shape="rect" href="nms-examples.xml">NMS Examples</a><ul class="childpages-macro"><li><a shape="rect" href="nms-simple-asynchronous-consumer-example.xml">NMS Simple Asynchronous Consumer Example</a></li><li><a shape="rect" href="nms-simple-synchornous-consumer-example.xml">NMS Simple Synchornous Consumer Example</a></li></ul></li><li><a shape="rect" href="nms-faq.xml">NMS FAQ</a></li><li><a shape="rect" href="nms-providers.xml">NMS Providers</a><ul class="childpages-macro"><li><a shape="rect" href="apachenmsactivemq.xml">Apache.NMS.ActiveMQ</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-advanced-features.xml">ActiveMQ Advanced Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-consumer-features.xml">ActiveMQ Consumer Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-consumer-dispatch-async.xml">ActiveMQ Consumer Dispatch Async</a></li><li><a shape="rect" href="activemq-consumer-priority.xml">ActiveMQ Consumer Priority</a></li><li><a shape="rect" href="activemq-exclusive-consumers.xml">ActiveMQ Exclusive Consumers</a></li><li><a shape="rect" href="activemq-retroactive-consumers.xml">ActiveMQ Retroactive Consumers</a></li></ul></li><li><a shape="rect" href="activemq-destination-features.xml">ActiveMQ Destination Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-destination-management.xml">ActiveMQ Destination Management</a></li><li><a shape="rect" href="activemq-destination-options.xml">ActiveMQ Destination Options</a></li><li><a shape="rect" href="activemq-mirrored-queues.xml">ActiveMQ Mirrored Queues</a></li><li><a shape="rect" href="activemq-virtual-destinations.xml">ActiveMQ Virtual Destinations</a></li><li><a shape="rect" href="activemq-wildcards.xml">ActiveMQ Wildcards</a></li></ul></li><li><a shape="rect" href="activemq-message-dispatching-features.xml">ActiveMQ Message Dispatching Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-async-sends.xml">ActiveMQ Async Sends</a></li></ul></li><li><a shape="rect" href="activemq-message-features.xml">ActiveMQ Message Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-delay-and-schedule-message-feature.xml">ActiveMQ Delay and Schedule Message Feature</a></li></ul></li></ul></li><li><a shape="rect" href="activemq-build-notes.xml">ActiveMQ Build Notes</a></li><li><a shape="rect" href="activemq-downloads.xml">ActiveMQ Downloads</a><ul class="childpages-macro"><li><a shape="rect" href="apachenmsactivemq-v120.xml">Apache.NMS.ActiveMQ v1.2.0</a></li><li><a shape="rect" href="apachenmsactivemq-v130.xml">Apache.NMS.ActiveMQ v1.3.0</a></li><li><a shape="rect" href="apachenmsactivemq-v140.xml">Apache.NMS.ActiveMQ v1.4.0</a></li><li><a shape="rect" href="apachenmsactivemq-v141.xml">Apache.NMS.ActiveMQ v1.4.1</a></li><li><a shape="rect" href="apachenmsactivemq-v150.xml">Apache.NMS.ActiveMQ v1.5.0</a></li><li><a shape="rect" href="apachenmsactivemq-v151.xml">Apache.NMS.ActiveMQ v1.5.1</a></li><li><a shape="rect" href="apachenmsactivemq-v152.xml">Apache.NMS.ActiveMQ v1.5.2</a></li><li><a shape="rect" href="apachenmsactivemq-v153.xml">Apache.NMS.ActiveMQ v1.5.3</a></li><li><a shape="rect" href="apachenmsactivemq-v154.xml">Apache.NMS.ActiveMQ v1.5.4</a></li><li><a shape="rect" href="apachenmsactivemq-v155.xml">Apache.NMS.ActiveMQ v1.5.5</a></li><li><a shape="rect" href="apachenmsactivemq-v156.xml">Apache.NMS.ActiveMQ v1.5.6</a></li><li><a shape="rect" href="apachenmsactivemq-v160.xml">Apache.NMS.ActiveMQ v1.6.0</a></li><li><a shape="rect" href="apachenmsactivemq-v161.xml">Apache.NMS.ActiveMQ v1.6.1</a></li><li><a shape="rect" href="apachenmsactivemq-v162.xml">Apache.NMS.ActiveMQ v1.6.2</a></li><li><a shape="rect" href="apachenmsactivemq-v163.xml">Apache.NMS.ActiveMQ v1.6.3</a></li><li><a shape="rect" href="apachenmsactivemq-v164.xml">Apache.NMS.ActiveMQ v1.6.4</a></li><li><a shape="rect" href="apachenmsactivemq-v165.xml">Apache.NMS.ActiveMQ v1.6.5</a></li><li><a shape="rect" href="apachenmsactivemq-v170.xml">Apache.NMS.ActiveMQ v1.7.0</a></li><li><a shape="rect" href="apachenmsactivemq-v171.xml">Apache.NMS.ActiveMQ v1.7.1</a></li><li><a shape="rect" href="apachenmsactivemq-v172.xml">Apache.NMS.ActiveMQ v1.7.2</a></li><li><a shape="rect" href="apachenms-activemq-v110.xml">Apache.NMS ActiveMQ v1.1.0</a></li></ul></li><li><a shape="rect" href="activemq-examples.xml">ActiveMQ Examples</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-advisory-message-examples.xml">ActiveMQ Advisory Message Examples</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-enumerate-destination-using-advisory-messages.xml">ActiveMQ Enumerate Destination using Advisory Messages</a></li></ul></li></ul></li><li><a shape="rect" href="activemq-faq.xml">ActiveMQ FAQ</a></li><li><a shape="rect" href="activemq-uri-configuration.xml">ActiveMQ URI Configuration</a></li></ul></li><li><a shape="rect" href="apachenmsamqp.xml">Apache.NMS.AMQP</a><ul class="childpages-macro"><li><a shape="rect" href="amqp-build-notes.xml">AMQP Build Notes</a></li><li><a shape="rect" href="amqp-downloads.xml">AMQP Downloads</a></li><li><a shape="rect" href="amqp-examples.xml">AMQP Examples</a></li><li><a shape="rect" href="amqp-faq.xml">AMQP FAQ</a></li></ul></li><li><a shape="rect" href="apachenmsems.xml">Apache.NMS.EMS</a><ul class="childpages-macro"><li><a shape="rect" href="ems-build-notes.xml">EMS Build Notes</a></li><li><a shape="rect" href="ems-downloads.xml">EMS Downloads</a><ul class="childpages-macro"><li><a shape="rect" href="apachenms-ems-v110.xml">Apache.NMS EMS v1.1.0</a></li></ul></li><li><a shape="rect" href="ems-examples.xml">EMS Examples</a></li><li><a shape="rect" href="ems-faq.xml">EMS FAQ</a></li></ul></li><li><a shape="rect" href="apachenmsmqtt.xml">Apache.NMS.MQTT</a></li><li><a shape="rect" href="apachenmsmsmq.xml">Apache.NMS.MSMQ</a><ul class="childpages-macro"><li><a shape="rect" href="msmq-build-notes.xml">MSMQ Build Notes</a></li><li><a shape="rect" href="msmq-downloads.xml">MSMQ Downloads</a><ul class="childpages-macro"><li><a shape="rect" href="apachenms-msmq-v110.xml">Apache.NMS MSMQ v1.1.0</a></li></ul></li><li><a shape="rect" href="msmq-examples.xml">MSMQ Examples</a></li><li><a shape="rect" href="msmq-faq.xml">MSMQ FAQ</a></li></ul></li><li><a shape="rect" href="apachenmsstomp.xml">Apache.NMS.Stomp</a><ul class="childpages-macro"><li><a shape="rect" href="stomp-advanced-features.xml">Stomp Advanced Features</a><ul class="childpages-macro"><li><a shape="rect" href="stomp-message-features.xml">Stomp Message Features</a><ul class="childpages-macro"><li><a shape="rect" href="stomp-delayed-and-scheduled-message-feature.xml">Stomp Delayed and Scheduled Message Feature</a></li></ul></li></ul></li><li><a shape="rect" href="stomp-build-notes.xml">Stomp Build Notes</a></li><li><a shape="rect" href="stomp-downloads.xml">Stomp Downloads</a><ul class="childpages-macro"><li><a shape="rect" href="apachenmsstomp-v120.xml">Apache.NMS.Stomp v1.2.0</a></li><li><a shape="rect" href="apachenmsstomp-v130.xml">Apache.NMS.Stomp v1.3.0</a></li><li><a shape="rect" href="apachenmsstomp-v140.xml">Apache.NMS.Stomp v1.4.0</a></li><li><a shape="rect" href="apachenmsstomp-v150.xml">Apache.NMS.Stomp v1.5.0</a></li><li><a shape="rect" href="apachenmsstomp-v151.xml">Apache.NMS.Stomp v1.5.1</a></li><li><a shape="rect" href="apachenmsstomp-v152.xml">Apache.NMS.Stomp v1.5.2</a></li><li><a shape="rect" href="apachenmsstomp-v153.xml">Apache.NMS.Stomp v1.5.3</a></li><li><a shape="rect" href="apachenmsstomp-v154.xml">Apache.NMS.Stomp v1.5.4</a></li></ul></li><li><a shape="rect" href="stomp-faq.xml">Stomp FAQ</a></li><li><a shape="rect" href="stomp-uri-configuration.xml">Stomp URI Configuration</a></li></ul></li><li><a shape="rect" href="apachenmswcf.xml">Apache.NMS.WCF</a><ul class="childpages-macro"><li><a shape="rect" href="wcf-downloads.xml">WCF Downloads</a><ul class="childpages-macro"><li><a shape="rect" href="apachenmswcf-v110.xml">Apache.NMS.WCF v1.1.0</a></li></ul></li><li><a shape="rect" href="wcf-examples.xml">WCF Examples</a></li></ul></li><li><a shape="rect" href="apachenmsxms.xml">Apache.NMS.XMS</a></li></ul></li><li><a shape="rect" href="nms-uri-configuration.xml">NMS URI Configuration</a></li></ul></li><li><a shape="rect" href="articles.xml">Articles</a></li><li><a shape="rect" href="community.xml">Community</a><ul class="childpages-macro"><li><a shape="rect" href="privacy-policy.xml">Privacy Policy</a></li></ul></li><li><a shape="rect" href="developers.xml">Developers</a><ul class="childpages-macro"><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="source.xml">Source</a></li></ul></li><li><a shape="rect" href="faq.xml">FAQ</a><ul class="childpages-macro"><li><a shape="rect" href="are-there-more-faq-entries.xml">Are there more FAQ Entries</a></li><li><a shape="rect" href="should-i-pool-connections.xml">Should I pool connections</a></li><li><a shape="rect" href="what-is-nms.xml">What is NMS</a></li></ul></li><li><a shape="rect" href="overview.xml">Overview</a><ul class="childpages-macro"><li><a shape="rect" href="download.xml">Download</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-net-110-release.xml">ActiveMQ .NET 1.1.0 Release</a></li><li><a shape="rect" href="activemq-net-120-release.xml">ActiveMQ .NET 1.2.0 Release</a></li><li><a shape="rect" href="activemq-net-130-release.xml">ActiveMQ .NET 1.3.0 Release</a></li><li><a shape="rect" href="activemq-net-140-release.xml">ActiveMQ .NET 1.4.0 Release</a></li><li><a shape="rect" href="apachenms-150-release.xml">Apache.NMS 1.5.0 Release</a></li></ul></li><li><a shape="rect" href="nms.xml">NMS</a></li><li><a shape="rect" href="using-nms.xml">Using NMS</a><ul class="childpages-macro"><li><a shape="rect" href="examples.xml">Examples</a></li></ul></li></ul></li><li><a shape="rect" href="site.xml">Site</a><ul class="childpages-macro"><li><a shape="rect" href="banner.xml">Banner</a></li><li><a shape="rect" href="navigation.xml">Navigation</a><ul class="childpages-macro"><li><a shape="rect" href="support.xml">Support</a></li></ul></li><li><a shape="rect" href="quicklinks.xml">QuickLinks</a></li><li><a shape="rect" href="siteindex.xml">SiteIndex</a></li><li><a shape="rect" href="sitemap.xml">SiteMap</a></li></ul></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="267aaee9-545e-451c-8b6d-792546649fd5" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Index"></page></link></parameter></structured-macro></div>
diff --git a/nms/source.xml b/nms/source.xml
index 8b53ad5..7173129 100644
--- a/nms/source.xml
+++ b/nms/source.xml
@@ -1,14 +1,11 @@
-<div class="wiki-content maincontent"><h2 id="Source-WebBrowsingofGitrepositories">Web Browsing of Git repositories</h2><p>Browse the source tree of each of the NMS projects directly:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>https://git-wip-us.apache.org/repos/asf/activemq-nms-api.git
+<div class="wiki-content maincontent"><h2>Web Browsing of Git repositories</h2><p>Browse the source tree of each of the NMS projects directly:</p><structured-macro ac:macro-id="4e2d9207-a71b-4e95-be6d-9a9a9352b0aa" ac:name="noformat" ac:schema-version="1"><plain-text-body>https://git-wip-us.apache.org/repos/asf/activemq-nms-api.git
https://git-wip-us.apache.org/repos/asf/activemq-nms-openwire.git
https://git-wip-us.apache.org/repos/asf/activemq-nms-amqp.git
https://git-wip-us.apache.org/repos/asf/activemq-nms-ems.git
https://git-wip-us.apache.org/repos/asf/activemq-nms-msmq.git
https://git-wip-us.apache.org/repos/asf/activemq-nms-stomp.git
https://git-wip-us.apache.org/repos/asf/activemq-nms-zmq.git
-https://git-wip-us.apache.org/repos/asf/activemq-nms-xms.git</pre>
-</div></div><h2 id="Source-CheckingoutfromGit">Checking out from Git</h2><p>To download the individual projects, run the following command(s):</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>git clone https://git-wip-us.apache.org/repos/asf/activemq-nms-api.git
+https://git-wip-us.apache.org/repos/asf/activemq-nms-xms.git</plain-text-body></structured-macro><h2>Checking out from Git</h2><p>To download the individual projects, run the following command(s):</p><structured-macro ac:macro-id="3d25c442-0010-4b04-ac0c-c0dc9ca76929" ac:name="noformat" ac:schema-version="1"><plain-text-body>git clone https://git-wip-us.apache.org/repos/asf/activemq-nms-api.git
git clone https://git-wip-us.apache.org/repos/asf/activemq-nms-openwire.git
git clone https://git-wip-us.apache.org/repos/asf/activemq-nms-amqp.git
git clone https://git-wip-us.apache.org/repos/asf/activemq-nms-ems.git
@@ -16,6 +13,5 @@
git clone https://git-wip-us.apache.org/repos/asf/activemq-nms-stomp.git
git clone https://git-wip-us.apache.org/repos/asf/activemq-nms-zmq.git
git clone https://git-wip-us.apache.org/repos/asf/activemq-nms-xms.git
-</pre>
-</div></div><p>Only project developers can commit to the Git tree via this method.</p><h3 id="Source-Branches">Branches</h3><p>We use the master for the next main release; then we use a branch for any bug fixes on the previous major release.</p><h2 id="Source-Buildingthecode">Building the code</h2><p>To then build the code see <a shape="rect" href="building.xml">Building</a>.</p></div>
+</plain-text-body></structured-macro><p>Only project developers can commit to the Git tree via this method.</p><h3>Branches</h3><p>We use the master for the next main release; then we use a branch for any bug fixes on the previous major release.</p><h2>Building the code</h2><p>To then build the code see <link><page ri:content-title="Building"></page></link>.</p></div>
diff --git a/nms/stomp-advanced-features.xml b/nms/stomp-advanced-features.xml
index d08255f..9abdcc2 100644
--- a/nms/stomp-advanced-features.xml
+++ b/nms/stomp-advanced-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="stomp-message-features.xml">Stomp Message Features</a><ul class="childpages-macro"><li><a shape="rect" href="stomp-delayed-and-scheduled-message-feature.xml">Stomp Delayed and Scheduled Message Feature</a></li></ul></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="c83d2fb4-4282-40ec-90e1-ce44d57a2bda" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro></div>
diff --git a/nms/stomp-delayed-and-scheduled-message-feature.xml b/nms/stomp-delayed-and-scheduled-message-feature.xml
index 3a335cb..083ee90 100644
--- a/nms/stomp-delayed-and-scheduled-message-feature.xml
+++ b/nms/stomp-delayed-and-scheduled-message-feature.xml
@@ -1,62 +1,4 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This documentation only applies when the Stomp client is connected to an ActiveMQ Broker v5.4 and above.</p></div></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="7b8fafe0-a6fb-4c2c-877a-2dae473341e9" ac:name="info" ac:schema-version="1"><rich-text-body><p>This documentation only applies when the Stomp client is connected to an ActiveMQ Broker v5.4 and above.</p></rich-text-body></structured-macro>
-ActiveMQ from version <strong>5.4</strong> has an optional persistent scheduler built into the ActiveMQ message broker. It is enabled by setting the broker <strong>schedulerSupport</strong> attribute to true in the <a shape="rect" class="unresolved" href="#">xml configuration</a>. <br clear="none">
-An ActiveMQ client can take advantage of a delayed delivery by using the following message properties:
-
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_DELAY</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> long </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The time in milliseconds that a message will wait before being scheduled to be delivered by the broker</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_PERIOD </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>long </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The time in milliseconds to wait after the start time to wait before scheduling the message again</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_REPEAT </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>int </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The number of times to repeat scheduling a message for delivery</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>AMQ_SCHEDULED_CRON </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>String </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use a Cron entry to set the schedule</p></td></tr></tbody></table></div>
-
-
-<p>For example, to have a message scheduled for delivery in 60 seconds - you would need to set the <em>AMQ_SCHEDULED_DELAY</em> property:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- IMessageProducer producer = session.CreateProducer(destination);
- ITextMessage message = session.CreateTextMessage("test msg");
- long time = 60 * 1000;
- message.Properties["AMQ_SCHEDULED_DELAY"] = time;
- producer.Send(message);
-]]></script>
-</div></div>
-
-<p>You can set a message to wait with an initial delay, and the repeat delivery 10 times, waiting 10 seconds between each re-delivery:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- IMessageProducer producer = session.CreateProducer(destination);
- ITextMessage message = session.CreateTextMessage("test msg");
- long delay = 30 * 1000;
- long period = 10 * 1000;
- int repeat = 9;
- message.Properties["AMQ_SCHEDULED_DELAY"] = delay;
- message.Properties["AMQ_SCHEDULED_PERIOD"] = period;
- message.Properties["AMQ_SCHEDULED_REPEAT"] = repeat;
- producer.Send(message);
-]]></script>
-</div></div>
-
-
-<p>You can also use <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/Cron" rel="nofollow">CRON</a> to schedule a message, for example, if you want a message scheduled to be delivered every hour, you would need to set the CRON entry to be - <em>0 * * * *</em> - e.g.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- IMessageProducer producer = session.CreateProducer(destination);
- ITextMessage message = session.CreateTextMessage("test msg");
- message.Properties["AMQ_SCHEDULED_CRON"] = "0 * * * *";
- producer.Send(message);
-]]></script>
-</div></div>
-
-<p>CRON scheduling takes priority over using message delay - however, if a repeat and period is set with a CRON entry, the ActiveMQ scheduler will schedule delivery of the message for every time the CRON entry fires. Easier to explain with an example. Supposing that you want a message to be delivered 10 times, with a one second delay between each message - and you wanted this to happen every hour - you'd do this:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- IMessageProducer producer = session.CreateProducer(destination);
- ITextMessage message = session.CreateTextMessage("test msg");
- message.Properties["AMQ_SCHEDULED_CRON"] = "0 * * * *";
- message.Properties["AMQ_SCHEDULED_DELAY"] = 1000;
- message.Properties["AMQ_SCHEDULED_PERIOD"] = 1000;
- message.Properties["AMQ_SCHEDULED_REPEAT"] = 9;
- producer.Send(message);
-]]></script>
-</div></div></div>
+<structured-macro ac:macro-id="4a140266-43b2-437d-83d4-9faed9721212" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="ActiveMQ Delay and Schedule Message Feature"></page></link></parameter></structured-macro></div>
diff --git a/nms/stomp-downloads.xml b/nms/stomp-downloads.xml
index 0396c1e..838cdfb 100644
--- a/nms/stomp-downloads.xml
+++ b/nms/stomp-downloads.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Release Date </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v154.xml">Apache.NMS.Stomp v1.5.4</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 10/26/2013 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.1 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v153.xml">Apache.NMS.Stomp v1.5.3</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 08/30/2012 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.1 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v152.xml">Apache.NMS.Stomp v1.5.2</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 11/19/2011 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v151.xml">Apache.NMS.Stomp v1.5.1</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 01/31/2011 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v150.xml">Apache.NMS.Stomp v1.5.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 01/14/2011 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v140.xml">Apache.NMS.Stomp v1.4.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 09/23/2010 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.4.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v130.xml">Apache.NMS.Stomp v1.3.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 05/27/2010 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.3.0 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmsstomp-v120.xml">Apache.NMS.Stomp v1.2.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 02/07/2010 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.2.0 </p></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Release Date </p></th><th colspan="1" rowspan="1"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.Stomp v1.5.4"></page></link> </p></td><td colspan="1" rowspan="1"><p> 10/26/2013 </p></td><td colspan="1" rowspan="1"><p> v1.5.1 </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.Stomp v1.5.3"></page></link> </p></td><td colspan="1" rowspan="1"><p> 08/30/2012 </p></td><td colspan="1" rowspan="1"><p> v1.5.1 </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.Stomp v1.5.2"></page></link> </p></td><td colspan="1" rowspan="1"><p> 11/19/2011 </p></td><td colspan="1" rowspan="1"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.Stomp v1.5.1"></page></link> </p></td><td colspan="1" rowspan="1"><p> 01/31/2011 </p></td><td colspan="1" rowspan="1"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.Stomp v1.5.0"></page></link> </p></td><td colspan="1" rowspan="1"><p> 01/14/2011 </p></td><td colspan="1" rowspan="1"><p> v1.5.0 </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.Stomp v1.4.0"></page></link> </p></td><td colspan="1" rowspan="1"><p> 09/23/2010 </p></td><td colspan="1" rowspan="1"><p> v1.4.0 </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.Stomp v1.3.0"></page></link> </p></td><td colspan="1" rowspan="1"><p> 05/27/2010 </p></td><td colspan="1" rowspan="1"><p> v1.3.0 </p></td></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.Stomp v1.2.0"></page></link> </p></td><td colspan="1" rowspan="1"><p> 02/07/2010 </p></td><td colspan="1" rowspan="1"><p> v1.2.0 </p></td></tr></tbody></table>
+</div>
diff --git a/nms/stomp-message-features.xml b/nms/stomp-message-features.xml
index c58330d..ed8f293 100644
--- a/nms/stomp-message-features.xml
+++ b/nms/stomp-message-features.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="stomp-delayed-and-scheduled-message-feature.xml">Stomp Delayed and Scheduled Message Feature</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="a2317556-c09d-4881-8c14-46a5ab34cdc2" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/nms/stomp-uri-configuration.xml b/nms/stomp-uri-configuration.xml
index b27297c..9e7f945 100644
--- a/nms/stomp-uri-configuration.xml
+++ b/nms/stomp-uri-configuration.xml
@@ -1,87 +1,83 @@
-<div class="wiki-content maincontent"><h2 id="StompURIConfiguration-ConfiguringNMS.Stomp">Configuring NMS.Stomp</h2>
+<div class="wiki-content maincontent"><h2>Configuring NMS.Stomp</h2>
<p>All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every facet of your NMS.Stomp client. The tables below show the comprehensive set of parameters.</p>
-<h3 id="StompURIConfiguration-ConnectionURIParameters"><strong>Connection URI Parameters</strong></h3>
+<h3><strong>Connection URI Parameters</strong></h3>
-<h5 id="StompURIConfiguration-ExampleConfiguration"> Example Configuration</h5>
+<h5> Example Configuration</h5>
<p>Using the Generic NMSConnectionFactory class would look as follows:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>var cf = new NMSConnectionFactory(
+<structured-macro ac:macro-id="7e46419e-1c01-4a8a-bbe5-d30cb88303c8" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+var cf = new NMSConnectionFactory(
"stomp:tcp://localhost:61613");
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
<p>You can also use the Stomp ConecctionFactory implementation directory:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>var cf = new Apache.NMS.Stomp.ConnectionFactory(
+<structured-macro ac:macro-id="c3b5e7f5-7d2d-4617-bb72-0dfe2557f130" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+var cf = new Apache.NMS.Stomp.ConnectionFactory(
"tcp://localhost:61613");
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="StompURIConfiguration-ProtocolOptions">Protocol Options</h3>
+<h3>Protocol Options</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Option Name <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tcp </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses TCP/IP Sockets to connect to the Broker. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ssl </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses TCP/IP Sockets to connect to the Broker with an added SSL layer (Not available on .NETCF). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> failover </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses the Failover Transport to connect and reconnect to one or more Brokers </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name <br clear="none" class="atl-forced-newline"> </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> tcp </p></td><td colspan="1" rowspan="1"><p> Uses TCP/IP Sockets to connect to the Broker. </p></td></tr><tr><td colspan="1" rowspan="1"><p> ssl </p></td><td colspan="1" rowspan="1"><p> Uses TCP/IP Sockets to connect to the Broker with an added SSL layer (Not available on .NETCF). </p></td></tr><tr><td colspan="1" rowspan="1"><p> failover </p></td><td colspan="1" rowspan="1"><p> Uses the Failover Transport to connect and reconnect to one or more Brokers </p></td></tr></tbody></table>
<p>You can add the failover option using the Generic NMSConnectionFactory class like this:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>var cf = new NMSConnectionFactory(
+<structured-macro ac:macro-id="32e8292d-4333-4ec7-a147-52ab3460a9e6" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+var cf = new NMSConnectionFactory(
"stomp:failover:tcp://localhost:61613");
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
<p>You can also use the Stomp ConecctionFactory implementation directory:</p>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>var cf = new Apache.NMS.Stomp.ConnectionFactory(
+<structured-macro ac:macro-id="d2c17a8e-d03d-4b02-bbd3-850324c29e1d" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+var cf = new Apache.NMS.Stomp.ConnectionFactory(
"failover:tcp://localhost:61613");
-</pre>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="StompURIConfiguration-TransportOptions"><strong>Transport Options</strong></h4>
+<h4><strong>Transport Options</strong></h4>
-<h5 id="StompURIConfiguration-TCPTransportOptions"><strong>TCP Transport Options</strong></h5>
+<h5><strong>TCP Transport Options</strong></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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.useLogging </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Log data that is sent across the Transport. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.receiveBufferSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 8192 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Amount of Data to buffer from the Socket </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.sendBufferSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 8192 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Amount of Data to buffer before writing to the Socket </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.receiveTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Time to wait for more data, zero means wait infinitely </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.sendTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Timeout on sends, 0 means wait forever for completion </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.requestTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Time to wait before a Request Command is considered to have failed </p></td></tr><tr><td></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> transport.useLogging </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Log data that is sent across the Transport. </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.receiveBufferSize </p></td><td colspan="1" rowspan="1"><p> 8192 </p></td><td colspan="1" rowspan="1"><p> Amount of Data to buffer from the Socket </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.sendBufferSize </p></td><td colspan="1" rowspan="1"><p> 8192 </p></td><td colspan="1" rowspan="1"><p> Amount of Data to buffer before writing to the Socket </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.receiveTimeout </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Time to wait for more data, zero means wait infinitely </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.sendTimeout </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Timeout on sends, 0 means wait forever for completion </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.requestTimeout </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Time to wait before a Request Command is considered to have failed </p></td></tr><tr><td></td></tr></tbody></table>
-<h5 id="StompURIConfiguration-FailoverTransportOptions">Failover Transport Options</h5>
+<h5>Failover Transport Options</h5>
<p>Prior to NMS.Stomp v1.4.0 the failover transport options did not use the transport.* prefix.</p>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.timeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> -1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Time that a send operation blocks before failing. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.initialReconnectDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 10 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Time in Milliseconds that the transport waits before attempting to reconnect the first time. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.maxReconnectDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 30000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The max time in Milliseconds that the transport will wait before attempting to reconnect. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.backOffMultiplier </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 2 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The amount by which the reconnect delay will be multiplied by if useExponentialBackOff is enabled. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.useExponentialBackOff </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the delay between connection attempt grow on each try up to the max reconnect delay. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.randomize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the Uri to connect to be chosen at random from the list of available Uris. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.maxReconnectAttempts </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Maximum number of time the transport will attempt to reconnect before failing (0 means infinite retries) </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.startupMaxReconnectAttempts </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Maximum number of time the transport will attempt to reconnect before failing when there has never been a connection made. (0 means infinite retries) <strong>(included in NMS.Stomp v1.5.0+)</strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transport.reconnectDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 10 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The delay in milliseconds that the transport waits before attempting a reconnection. </p></td></tr><tr><td></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> transport.timeout </p></td><td colspan="1" rowspan="1"><p> -1 </p></td><td colspan="1" rowspan="1"><p> Time that a send operation blocks before failing. </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.initialReconnectDelay </p></td><td colspan="1" rowspan="1"><p> 10 </p></td><td colspan="1" rowspan="1"><p> Time in Milliseconds that the transport waits before attempting to reconnect the first time. </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.maxReconnectDelay </p></td><td colspan="1" rowspan="1"><p> 30000 </p></td><td colspan="1" rowspan="1"><p> The max time in Milliseconds that the transport will wait before attempting to reconnect. </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.backOffMultiplier </p></td><td colspan="1" rowspan="1"><p> 2 </p></td><td colspan="1" rowspan="1"><p> The amount by which the reconnect delay will be multiplied by if useExponentialBackOff is enabled. </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.useExponentialBackOff </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Should the delay between connection attempt grow on each try up to the max reconnect delay. </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.randomize </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Should the Uri to connect to be chosen at random from the list of available Uris. </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.maxReconnectAttempts </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Maximum number of time the transport will attempt to reconnect before failing (0 means infinite retries) </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.startupMaxReconnectAttempts </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> Maximum number of time the transport will attempt to reconnect before failing when there has never been a connection made. (0 means infinite retries) <strong>(included in NMS.Stomp v1.5.0+)</strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> transport.reconnectDelay </p></td><td colspan="1" rowspan="1"><p> 10 </p></td><td colspan="1" rowspan="1"><p> The delay in milliseconds that the transport waits before attempting a reconnection. </p></td></tr><tr><td></td></tr></tbody></table>
-<h4 id="StompURIConfiguration-ConnectionOptions"><strong>Connection Options</strong></h4>
+<h4><strong>Connection Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.AsyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Are message sent Asynchronously. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.AsyncClose </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the close command be sent Asynchronously </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.AlwaysSyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Causes all messages a Producer sends to be sent Asynchronously. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.CopyMessageOnSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Copies the Message objects a Producer sends so that the client can reuse Message objects without affecting an in-flight message. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.useCompression </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should message bodies be compressed before being sent. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.sendAcksAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should message acks be sent asynchronously </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.messagePrioritySupported </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should messages be delivered to the client based on the value of the Message Priority header. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection.dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the broker <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the connection's consumers. </p></td></tr><tr><td></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> connection.AsyncSend </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Are message sent Asynchronously. </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.AsyncClose </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Should the close command be sent Asynchronously </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.AlwaysSyncSend </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Causes all messages a Producer sends to be sent Asynchronously. </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.CopyMessageOnSend </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Copies the Message objects a Producer sends so that the client can reuse Message objects without affecting an in-flight message. </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.useCompression </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should message bodies be compressed before being sent. </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.sendAcksAsync </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should message acks be sent asynchronously </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.messagePrioritySupported </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Should messages be delivered to the client based on the value of the Message Priority header. </p></td></tr><tr><td colspan="1" rowspan="1"><p> connection.dispatchAsync </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should the broker <a shape="rect" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the connection's consumers. </p></td></tr><tr><td></td></tr></tbody></table>
-<h5 id="StompURIConfiguration-StompWireProtocolOptions"><strong>Stomp Wire Protocol Options</strong></h5>
+<h5><strong>Stomp Wire Protocol Options</strong></h5>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Be Careful</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>These values are currently not supported but are planned for a later release.</p></div></div>
+<structured-macro ac:macro-id="3c1a17fc-a887-4e54-9b9d-80ef1a9d74fe" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Be Careful</parameter><rich-text-body>
+<p>These values are currently not supported but are planned for a later release.</p></rich-text-body></structured-macro>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.maxInactivityDuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 30000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum inactivity duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to appear to die, so we allow the broker to kill connections if they are inactive for a period of time. Use by some transports to enable a keep alive heart beat feature. Set to a value <= 0 to disable inactivity monitoring. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.maxInactivityDurationInitialDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 10000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The initial delay in starting the maximum inactivity checks (and, yes, the word 'Initial' is supposed to be misspelled like that) </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.maxInactivityDuration </p></td><td colspan="1" rowspan="1"><p> 30000 </p></td><td colspan="1" rowspan="1"><p> The maximum inactivity duration (before which the socket is considered dead) in milliseconds. On some platforms it can take a long time for a socket to appear to die, so we allow the broker to kill connections if they are inactive for a period of time. Use by some transports to enable a keep alive heart beat feature. Set to a value <= 0 to disable inactivity monitoring. </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.maxInactivityDurationInitialDelay </p></td><td colspan="1" rowspan="1"><p> 10000 </p></td><td colspan="1" rowspan="1"><p> The initial delay in starting the maximum inactivity checks (and, yes, the word 'Initial' is supposed to be misspelled like that) </p></td></tr></tbody></table>
-<h3 id="StompURIConfiguration-DestinationURIParameters"><strong>Destination URI Parameters</strong></h3>
+<h3><strong>Destination URI Parameters</strong></h3>
-<h5 id="StompURIConfiguration-ExampleConfiguration.1">Example Configuration</h5>
+<h5>Example Configuration</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>d = session.CreateTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
-</pre>
-</div></div>
+<structured-macro ac:macro-id="d712c55b-ab45-4d96-929a-057c6d2f501d" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+d = session.CreateTopic("com.foo?consumer.prefetchSize=2000&consumer.noLocal=true");
+</plain-text-body></structured-macro>
-<h4 id="StompURIConfiguration-GeneralOptions"><strong>General Options</strong></h4>
+<h4><strong>General Options</strong></h4>
-<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 </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The number of message the consumer will <a shape="rect" class="external-link" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.noLocal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Should the broker <a shape="rect" class="external-link" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the consumer. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.retroactive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Is this a <a shape="rect" class="external-link" href="http://activemq.apache.org/retroactive-consumer.html">Retroactive Consumer</a>. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> JMS Selector used with the consumer. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer.exclusive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Is this an <a shape="rect" class="external-link" href="http://activemq.apache.org/exclusive-consumer.html">Exclusive Consumer</a>. </p></td></tr></tbody></table></div></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer.prefetchSize </p></td><td colspan="1" rowspan="1"><p> 1000 </p></td><td colspan="1" rowspan="1"><p> The number of message the consumer will <a shape="rect" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch</a>. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.noLocal </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Same as the noLocal flag on a Topic consumer. Exposed here so that it can be used with a queue. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.dispatchAsync </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Should the broker <a shape="rect" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatch messages asynchronously</a> to the consumer. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.retroactive </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Is this a <a shape="rect" href="http://activemq.apache.org/retroactive-consumer.html">Retroactive Consumer</a>. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.selector </p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> JMS Selector used with the consumer. </p></td></tr><tr><td colspan="1" rowspan="1"><p> consumer.exclusive </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Is this an <a shape="rect" href="http://activemq.apache.org/exclusive-consumer.html">Exclusive Consumer</a>. </p></td></tr></tbody></table>
+</div>
diff --git a/nms/support.xml b/nms/support.xml
index 755f5a2..51be745 100644
--- a/nms/support.xml
+++ b/nms/support.xml
@@ -1,15 +1,15 @@
-<div class="wiki-content maincontent"><h2 id="Support-GettingHelp">Getting Help</h2>
+<div class="wiki-content maincontent"><h2>Getting Help</h2>
-<p>If you are experiencing problems using NMS then please first try the <a shape="rect" href="faq.xml">FAQ</a>. If you cannot find your issue then report your problem to our <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQNET">Issue Tracker</a></p>
+<p>If you are experiencing problems using NMS then please first try the <link><page ri:content-title="FAQ"></page></link>. If you cannot find your issue then report your problem to our <a shape="rect" href="http://issues.apache.org/activemq/browse/AMQNET">Issue Tracker</a></p>
-<p>You may also find it useful to discuss your issues with the community on the <a shape="rect" class="external-link" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a> or join one of our <a shape="rect" class="external-link" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a>.</p>
+<p>You may also find it useful to discuss your issues with the community on the <a shape="rect" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a> or join one of our <a shape="rect" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a>.</p>
-<h3 id="Support-Links">Links</h3>
+<h3>Links</h3>
-<ul><li><a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQNET">Issue Tracker</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a></li><li><a shape="rect" href="faq.xml">FAQ</a></li></ul>
+<ul><li><a shape="rect" href="http://issues.apache.org/activemq/browse/AMQNET">Issue Tracker</a></li><li><a shape="rect" href="http://activemq.apache.org/discussion-forums.html">Discussion Forums</a></li><li><a shape="rect" href="http://activemq.apache.org/mailing-lists.html">Mailing Lists</a></li><li><link><page ri:content-title="FAQ"></page></link></li></ul>
-<h3 id="Support-Gettingmorehelp">Getting more help</h3>
+<h3>Getting more help</h3>
-<p>For more details on how to get more help see the <a shape="rect" class="external-link" href="http://activemq.apache.org/support.html">main ActiveMQ Support page</a></p></div>
+<p>For more details on how to get more help see the <a shape="rect" href="http://activemq.apache.org/support.html">main ActiveMQ Support page</a></p></div>
diff --git a/nms/using-nms.xml b/nms/using-nms.xml
index 5006d8f..c84d4e6 100644
--- a/nms/using-nms.xml
+++ b/nms/using-nms.xml
@@ -1,4 +1,5 @@
-<div class="wiki-content maincontent"><h3 id="UsingNMS-UsingNMS"><a shape="rect" href="using-nms.xml">Using NMS</a></h3>
+<div class="wiki-content maincontent"><h3><link></link></h3>
-<ul class="alternate"><li><a shape="rect" href="nms.xml">Getting Started</a></li><li><a shape="rect" href="nms-api.xml">API Reference</a></li><li><a shape="rect" href="examples.xml">Examples</a></li><li><a shape="rect" href="activemq-uri-configuration.xml">ActiveMQ URI Configuration</a></li></ul></div>
+<ul class="alternate"><li><link><page ri:content-title="NMS"></page><link-body>Getting Started</link-body></link></li><li><link><page ri:content-title="NMS API"></page><link-body>API Reference</link-body></link></li><li><link><page ri:content-title="Examples"></page></link></li><li><link><page ri:content-title="ActiveMQ URI Configuration"></page></link></li></ul>
+</div>
diff --git a/nms/wcf-downloads.xml b/nms/wcf-downloads.xml
index 910db09..4c6cd25 100644
--- a/nms/wcf-downloads.xml
+++ b/nms/wcf-downloads.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Release Date </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" href="apachenmswcf-v110.xml">Apache.NMS.WCF v1.1.0</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> v1.1.0 </p></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><table><tbody><tr><th colspan="1" rowspan="1"><p> Description </p></th><th colspan="1" rowspan="1"><p> Release Date </p></th><th colspan="1" rowspan="1"><p> NMS API Rev </p></th></tr><tr><td colspan="1" rowspan="1"><p> <link><page ri:content-title="Apache.NMS.WCF v1.1.0"></page></link> </p></td><td colspan="1" rowspan="1"><p> 07/12/2009 </p></td><td colspan="1" rowspan="1"><p> v1.1.0 </p></td></tr></tbody></table>
+</div>
diff --git a/nms/wcf-examples.xml b/nms/wcf-examples.xml
index d62e311..3f0f9c8 100644
--- a/nms/wcf-examples.xml
+++ b/nms/wcf-examples.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="e6f50ea6-790d-4301-9e62-06dc23b5caf6" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">3</parameter></structured-macro></div>
diff --git a/nms/what-is-nms.xml b/nms/what-is-nms.xml
index 1c2f9fa..ac4f1bb 100644
--- a/nms/what-is-nms.xml
+++ b/nms/what-is-nms.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="WhatisNMS-WhatisNMS?">What is NMS?</h2>
+<div class="wiki-content maincontent"><h2>What is NMS?</h2>
-<p><a shape="rect" href="nms.xml">NMS</a> is the open source .Net Messaging API. </p>
+<p><link><page ri:content-title="NMS"></page></link> is the open source .Net Messaging API. </p>
<p>This allows you to build .Net applications in C# or VB to a single API which can then be used to connect to multiple different Message Brokers.</p></div>
diff --git a/no-suitable-driver.xml b/no-suitable-driver.xml
index f383256..fc2731c 100644
--- a/no-suitable-driver.xml
+++ b/no-suitable-driver.xml
@@ -1,13 +1,14 @@
-<div class="wiki-content maincontent"><h3 id="Nosuitabledriver-Symptoms">Symptoms</h3>
+<div class="wiki-content maincontent"><h3>Symptoms</h3>
<p>I get an exception saying <strong>No suitable driver</strong> when initialising the JDBC driver.</p>
-<h3 id="Nosuitabledriver-Reason">Reason</h3>
+<h3>Reason</h3>
-<p>ActiveMQ tries to auto-detect the JDBC driver so that it can deduce the ultimate database's SQL dialect. Some JDBC drivers are not yet auto-recognised. Here's <a shape="rect" href="jdbc-support.xml">how to configure the language adapater class to use or to provide us with details of your driver so we can add support for it to ActiveMQ</a>.</p>
+<p>ActiveMQ tries to auto-detect the JDBC driver so that it can deduce the ultimate database's SQL dialect. Some JDBC drivers are not yet auto-recognised. Here's <link><page ri:content-title="JDBC Support"></page><link-body>how to configure the language adapater class to use or to provide us with details of your driver so we can add support for it to ActiveMQ</link-body></link>.</p>
-<h3 id="Nosuitabledriver-See">See</h3>
+<h3>See</h3>
-<ul><li><a shape="rect" href="jdbc-support.xml">JDBC Support</a></li><li><a shape="rect" href="persistence.xml">Persistence</a></li><li><a shape="rect" href="how-to-configure-a-new-database.xml">How to configure a new database</a></li></ul>
+<ul><li><link><page ri:content-title="JDBC Support"></page></link></li><li><link><page ri:content-title="Persistence"></page></link></li><li><link><page ri:content-title="How to configure a new database"></page></link></li></ul>
+
</div>
diff --git a/noclassdeffounderror-orgspringframeworkcoreioresource.xml b/noclassdeffounderror-orgspringframeworkcoreioresource.xml
index 9569069..d74e46d 100644
--- a/noclassdeffounderror-orgspringframeworkcoreioresource.xml
+++ b/noclassdeffounderror-orgspringframeworkcoreioresource.xml
@@ -2,17 +2,15 @@
<p>If you get an exception like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5ca8d7d4-3666-4e2d-ace3-fd67fd052ca4" ac:name="code" ac:schema-version="1"><plain-text-body>
java.lang.NoClassDefFoundError - org/springframework/core/io/Resource
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="NoClassDefFoundError-org.springframework.core.io.Resource-Cause">Cause</h3>
+<h3>Cause</h3>
-<p>You were probably trying to use the <a shape="rect" href="xml-configuration.xml">XML Configuration</a> mechanism, which uses Spring, but without having the Spring jar on your classpath.</p>
+<p>You were probably trying to use the <link><page ri:content-title="XML Configuration"></page></link> mechanism, which uses Spring, but without having the Spring jar on your classpath.</p>
-<h3 id="NoClassDefFoundError-org.springframework.core.io.Resource-Solution">Solution</h3>
+<h3>Solution</h3>
<p>Add the Spring jar to your classpath.</p></div>
diff --git a/objectmessage.xml b/objectmessage.xml
index 8b327ab..ab8b7f1 100644
--- a/objectmessage.xml
+++ b/objectmessage.xml
@@ -1,39 +1,27 @@
-<div class="wiki-content maincontent"><p>Although ObjectMessage usage is generally discouraged, as it introduces coupling of class paths between producers and consumers, ActiveMQ supports them as part of the JMS specification.</p><h2 id="ObjectMessage-Security">Security</h2><p>ObjectMessage objects depend on Java serialization of marshal/unmarshal object payload. This process is generally considered unsafe as malicious payload can exploit the host system. That's why starting with versions <strong>5.12.2</strong> and <strong>5.13.0</strong>, ActiveMQ enforces users to explicitly whitelist packages that can be exchanged using ObjectMessages.</p><p>If you need to exchange object messages, you need to add packages your applications are using. You can do that with by using <code>org.apache.activemq.SERIALIZABLE_PACKAGES</code> system property, interpreted by the broker and the activemq client library. You can add this system property to <code>ACTIVEMQ_OPTS</code> variable in <code>${ACTIVEMQ_HOME}/bin/env</code> script.</p><p>For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=java.lang,javax.security,java.util,org.apache.activemq,org.fusesource.hawtbuf,com.thoughtworks.xstream.mapper,com.mycompany.myapp]]></script>
-</div></div><p>will add <code>com.mycompany.myapp</code> package to the list of trusted packages. Note that other packages listed here are enabled by default as they are necessary for the regular broker work. In case you want to shortcut this mechanism, you can allow all packages to be trusted by using <code>*</code> wildcard, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=*]]></script>
-</div></div><h3 id="ObjectMessage-Clients">Clients</h3><p>On the client side, you need to have this same mechanism as malicious code can be deserialized on <code>ObjectMessage.getObject()</code> call, compromising your application's environment. You can use the same configuration mechanism on the broker and configure trusted classes using system properties. However, this is usually not convenient in the client applications, so in <strong>5.12.2</strong> and <strong>5.13.1</strong> we introduced additional configuration mechanism using <code>ActiveMQConnectionFactory</code>. There are two additional methods defined:</p><ul><li>The <code>setTrustedPackages()</code> method allows you to set the list of trusted packages you want to be to unserialize, like</li></ul><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory("tcp://localhost:61616");
-factory.setTrustedPackages(new ArrayList(Arrays.asList("org.apache.activemq.test,org.apache.camel.test".split(","))));]]></script>
-</div></div><ul><li>The <code>setTrustAllPackages()</code> allows you to turn off security check and trust all classes. It's useful for testing purposes.</li></ul><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory("tcp://localhost:61616");
-factory.setTrustAllPackages(true);]]></script>
-</div></div><p>You can set the same properties in Camel context like:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <bean id="connectionFactory" class="org.apache.activemq.spring.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61616"/>
- <property name="trustedPackages">
+<div class="wiki-content maincontent"><p>Although ObjectMessage usage is generally discouraged, as it introduces coupling of class paths between producers and consumers, ActiveMQ supports them as part of the JMS specification.</p><h2>Security</h2><p>ObjectMessage objects depend on Java serialization of marshal/unmarshal object payload. This process is generally considered unsafe as malicious payload can exploit the host system. That's why starting with versions <strong>5.12.2</strong> and <strong>5.13.0</strong>, ActiveMQ enforces users to explicitly whitelist packages that can be exchanged using ObjectMessages.</p><p>If you need to exchange object messages, you need to add packages your applications are using. You can do that with by using <code>org.apache.activemq.SERIALIZABLE_PACKAGES</code> system property, interpreted by the broker and the activemq client library. You can add this system property to <code>ACTIVEMQ_OPTS</code> variable in <code>${ACTIVEMQ_HOME}/bin/env</code> script.</p><p>For example:</p><structured-macro ac:macro-id="346591dd-1fb9-44e7-826f-7c8f0bae6ead" ac:name="code" ac:schema-version="1"><plain-text-body>-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=java.lang,javax.security,java.util,org.apache.activemq,org.fusesource.hawtbuf,com.thoughtworks.xstream.mapper,com.mycompany.myapp</plain-text-body></structured-macro><p>will add <code>com.mycompany.myapp</code> package to the list of trusted packages. Note that other packages listed here are enabled by default as they are necessary for the regular broker work. In case you want to shortcut this mechanism, you can allow all packages to be trusted by using <code>*</code> wildcard, like</p><structured-macro ac:macro-id="5d6cbfbc-f74d-407f-979a-f5a282b354f9" ac:name="code" ac:schema-version="1"><plain-text-body>-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=*</plain-text-body></structured-macro><h3>Clients</h3><p>On the client side, you need to have this same mechanism as malicious code can be deserialized on <code>ObjectMessage.getObject()</code> call, compromising your application's environment. You can use the same configuration mechanism on the broker and configure trusted classes using system properties. However, this is usually not convenient in the client applications, so in <strong>5.12.2</strong> and <strong>5.13.1</strong> we introduced additional configuration mechanism using <code>ActiveMQConnectionFactory</code>. There are two additional methods defined:</p><ul><li>The <code>setTrustedPackages()</code> method allows you to set the list of trusted packages you want to be to unserialize, like</li></ul><structured-macro ac:macro-id="6e2981f2-6a14-4f9c-9534-5cbb8a87cc90" ac:name="code" ac:schema-version="1"><plain-text-body>ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory("tcp://localhost:61616");
+factory.setTrustedPackages(new ArrayList(Arrays.asList("org.apache.activemq.test,org.apache.camel.test".split(","))));</plain-text-body></structured-macro><ul><li>The <code>setTrustAllPackages()</code> allows you to turn off security check and trust all classes. It's useful for testing purposes.</li></ul><structured-macro ac:macro-id="2890197f-3f12-4c14-8f97-1e13701ba67c" ac:name="code" ac:schema-version="1"><plain-text-body>ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory("tcp://localhost:61616");
+factory.setTrustAllPackages(true);</plain-text-body></structured-macro><p>You can set the same properties in Camel context like:</p><structured-macro ac:macro-id="106dc47e-d931-463a-a596-d077ad26676f" ac:name="code" ac:schema-version="1"><plain-text-body> <bean id="connectionFactory" class="org.apache.activemq.spring.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="tcp://localhost:61616"/>
+ <property name="trustedPackages">
<list>
<value>org.apache.activemq.test</value>
<value>org.apache.camel.test</value>
</list>
</property>
</bean>
- <bean id="jmsConfig" class="org.apache.camel.component.jms.JmsConfiguration">
- <property name="connectionFactory" ref="connectionFactory"/>
+ <bean id="jmsConfig" class="org.apache.camel.component.jms.JmsConfiguration">
+ <property name="connectionFactory" ref="connectionFactory"/>
</bean>
- <bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">
- <property name="configuration" ref="jmsConfig"/>
- </bean>]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <bean id="connectionFactory" class="org.apache.activemq.spring.ActiveMQConnectionFactory">
- <property name="brokerURL" value="tcp://localhost:61616"/>
- <property name="trustAllPackages" value="true"/>
+ <bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">
+ <property name="configuration" ref="jmsConfig"/>
+ </bean></plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="52c5267d-774d-417f-bf32-c66a3d1b7a6e" ac:name="code" ac:schema-version="1"><plain-text-body> <bean id="connectionFactory" class="org.apache.activemq.spring.ActiveMQConnectionFactory">
+ <property name="brokerURL" value="tcp://localhost:61616"/>
+ <property name="trustAllPackages" value="true"/>
</bean>
- <bean id="jmsConfig" class="org.apache.camel.component.jms.JmsConfiguration">
- <property name="connectionFactory" ref="connectionFactory"/>
+ <bean id="jmsConfig" class="org.apache.camel.component.jms.JmsConfiguration">
+ <property name="connectionFactory" ref="connectionFactory"/>
</bean>
- <bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">
- <property name="configuration" ref="jmsConfig"/>
- </bean>]]></script>
-</div></div><p>This configuration will override system properties if they are set.</p></div>
+ <bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">
+ <property name="configuration" ref="jmsConfig"/>
+ </bean></plain-text-body></structured-macro><p>This configuration will override system properties if they are set.</p></div>
diff --git a/old-osgi-integration.xml b/old-osgi-integration.xml
index 3a5c84f..060fe8c 100644
--- a/old-osgi-integration.xml
+++ b/old-osgi-integration.xml
@@ -1,39 +1,32 @@
-<div class="wiki-content maincontent"><p><strong>This article applies to versions of ActiveMQ prior to 5.4.0. If you use version 5.4.0 or newer proceed to the <a shape="rect" href="osgi-integration.xml">following article</a>.</strong></p>
+<div class="wiki-content maincontent"><p><strong>This article applies to versions of ActiveMQ prior to 5.4.0. If you use version 5.4.0 or newer proceed to the <link><page ri:content-title="OSGi Integration"></page><link-body>following article</link-body></link>.</strong></p>
-<h1 id="OldOSGiIntegration-Introduction">Introduction</h1>
+<h1>Introduction</h1>
-<p>All ActiveMQ modules are packaged as OSGi bundles and can be used in any OSGi container. This article will provide more details on how to use ActiveMQ in <a shape="rect" class="external-link" href="http://felix.apache.org/site/apache-felix-karaf.html">Apache Karaf</a>, small OSGi based runtime. Apache Karaf was previously know as <em>ServiceMix kernel</em>, so informations found here are applicable to <a shape="rect" class="external-link" href="http://servicemix.apache.org/home.html">Apache ServiceMix Enterprise Service Bus</a> as well.</p>
+<p>All ActiveMQ modules are packaged as OSGi bundles and can be used in any OSGi container. This article will provide more details on how to use ActiveMQ in <a shape="rect" href="http://felix.apache.org/site/apache-felix-karaf.html">Apache Karaf</a>, small OSGi based runtime. Apache Karaf was previously know as <em>ServiceMix kernel</em>, so informations found here are applicable to <a shape="rect" href="http://servicemix.apache.org/home.html">Apache ServiceMix Enterprise Service Bus</a> as well.</p>
-<h1 id="OldOSGiIntegration-ActiveMQ">ActiveMQ</h1>
+<h1>ActiveMQ</h1>
<p>ActiveMQ comes as a feature in ServiceMix (Karaf). So instead of installing all necessary bundles one by one, you can simply install it using a single command. But first of all, you need to setup ServiceMix features url.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6fdc52c5-1aa3-4658-bb8f-799b20301188" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> features/addUrl mvn:org.apache.servicemix/apache-servicemix/4.0.0/xml/features
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Now you can install ActiveMQ like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2092b3f0-16ae-4099-a6d3-7f6ca0fbfb68" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> features/install activemq
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This command will install all necessary ActiveMQ bundles and if you type</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="fe06efaf-d692-4f76-8368-7531b6330bc1" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/list
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>you should see something like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0a5b1a0b-1459-4a59-8967-ac1e77c37230" ac:name="code" ac:schema-version="1"><plain-text-body>
[ 50] [Active ] [ ] [ 60] geronimo-jta_1.1_spec (1.1.1)
[ 51] [Active ] [ ] [ 60] geronimo-j2ee-connector_1.5_spec (2.0.0)
[ 52] [Active ] [ ] [ 60] Apache ServiceMix Bundles: howl-1.0.1-1 (1.0.1.1_1)
@@ -51,16 +44,14 @@
[ 64] [Active ] [ ] [ 60] activemq-console (5.2.0)
[ 65] [Active ] [ ] [ 60] activemq-pool (5.2.0)
[ 66] [Active ] [Started] [ 60] Apache ServiceMix Features :: ActiveMQ Commands (4.0.0)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Once installed, this feature offers a special set of commands which enables you easily use the broker. </p>
-<div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>This feature comes pre-installed with the ServiceMix ESB so previous steps are not necessary.</p></div></div>
+<structured-macro ac:macro-id="86a43205-f95e-43fb-9388-c063abf85c23" ac:name="note" ac:schema-version="1"><rich-text-body>
+<p>This feature comes pre-installed with the ServiceMix ESB so previous steps are not necessary.</p></rich-text-body></structured-macro>
<p>The following example shows how to create and destroy the broker using the <code>create-broker</code> and <code>destroy-broker</code> commands.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9a0e1f89-7f5f-4c88-8479-94324142e989" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> activemq/create-broker
Creating file: /Users/dejanb/workspace/apache-servicemix-kernel-1.1.0/deploy/localhost-broker.xml
@@ -70,33 +61,27 @@
smx@root:/> activemq/destroy-broker
Default ActiveMQ Broker (localhost) configuration file created at: /Users/dejanb/workspace/apache-servicemix-kernel-1.1.0/deploy/localhost-broker.xml removed.
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>For more information on ActiveMQ feature take a look at the <a shape="rect" class="external-link" href="http://servicemix.apache.org/SMX4/activemq-integration.html">ServiceMix ActiveMQ integration guide </a></p>
+<p>For more information on ActiveMQ feature take a look at the <a shape="rect" href="http://servicemix.apache.org/SMX4/activemq-integration.html">ServiceMix ActiveMQ integration guide </a></p>
-<h1 id="OldOSGiIntegration-Webconsole">Web console</h1>
+<h1>Web console</h1>
-<p><a shape="rect" href="web-console.xml">Web console</a> is included in ActiveMQ distribution and you'll probably want to have it to monitor your broker. First of all you'll have to install the <code>web</code> feature, so that you have a web container ready to deploy our web application. To do that you should first add the ServiceMix features url, like we did above (if you didn't already). Now, you can just run</p>
+<p><link><page ri:content-title="Web console"></page></link> is included in ActiveMQ distribution and you'll probably want to have it to monitor your broker. First of all you'll have to install the <code>web</code> feature, so that you have a web container ready to deploy our web application. To do that you should first add the ServiceMix features url, like we did above (if you didn't already). Now, you can just run</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="bbbf47f0-359b-46d0-b5fc-987f90c0071d" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> features/install web
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>to grab all necessary bundles. If you type</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6b3333fb-c80d-47b7-a595-771c3082e7a2" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/list
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>you'll see all installed bundles (such as)</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="8e41e7b1-ae40-427b-9c67-8e0808120e6a" ac:name="code" ac:schema-version="1"><plain-text-body>
[ 43] [Active ] [ ] [ 60] Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.1)
[ 44] [Active ] [ ] [ 60] OPS4J Pax Web - Jsp Support (0.5.2)
[ 45] [Active ] [ ] [ 60] OPS4J Pax Web - Web Container (0.5.2)
@@ -104,11 +89,10 @@
[ 47] [Active ] [ ] [ 60] OPS4J Pax Web Extender - Whiteboard (0.5.0)
[ 48] [Active ] [ ] [ 60] OPS4J Pax Url - war:, war-i: (0.3.3)
[ 49] [Active ] [Started] [ 60] Apache ServiceMix WAR Deployer (4.0.0)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>This feature comes pre-installed with the ServiceMix ESB so previous steps are not necessary.</p></div></div>
+<structured-macro ac:macro-id="576d3e51-3af9-47f4-88f1-5a5f84f31e87" ac:name="note" ac:schema-version="1"><rich-text-body>
+<p>This feature comes pre-installed with the ServiceMix ESB so previous steps are not necessary.</p></rich-text-body></structured-macro>
<p>The important thing is that we need to use proper versions of Pax web bundles to make all this work, and those are:</p>
@@ -117,117 +101,95 @@
<p>So if you have older bundles, like it is the case in our example, you'll need to unistall them and install new ones. To uninstall old bundles, simply look at their id and execute</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a385ff2a-036e-46fe-8ba0-af93c2646e12" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/uninstall [id]
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>In this example it would be</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a26ee2fb-4e5e-4f19-958b-1c860835dd2f" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/uninstall 44
smx@root:/> osgi/uninstall 45
smx@root:/> osgi/uninstall 46
smx@root:/> osgi/uninstall 47
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Now install new ones</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="53adde10-a181-4b93-8ac2-f1e1aed51a9d" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/install mvn:org.ops4j.pax.web/pax-web-bundle/0.6.0
smx@root:/> osgi/install mvn:org.ops4j.pax.web/pax-web-jsp/0.6.0
smx@root:/> osgi/install mvn:org.ops4j.pax.web-extender/pax-web-ex-war/0.5.1
smx@root:/> osgi/install mvn:org.ops4j.pax.web-extender/pax-web-ex-whiteboard/0.5.1
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>After successful installation, you should start your newly added bundles. You can do that by executing </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2e36945f-3f28-40c0-8f02-434e1f6fb271" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/start [id]
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>It's best to restart your container at this point and afterwards we're finally ready to deploy our war. To do that we'll use the Pax Web War Extender. The following example will use the latest <code>5.3-SNAPSHOT</code> build and deploy it in the OSGi runtime</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="79aa08e5-1cf7-4687-bd4a-7beaa0ca2fc7" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/install war:mvn:org.apache.activemq/activemq-web-console/5.3-SNAPSHOT/war?Webapp-Context=activemqweb
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>You have to use the latest 5.3-SNAPSHOT web console, since this doesn't work right with previous versions.</p></div></div>
+<structured-macro ac:macro-id="fb6ee639-050c-4d91-bc59-bd20f9a77bc4" ac:name="note" ac:schema-version="1"><rich-text-body>
+<p>You have to use the latest 5.3-SNAPSHOT web console, since this doesn't work right with previous versions.</p></rich-text-body></structured-macro>
-<p>Also, if you have problems installing the war with the previous method, download it manually from <a shape="rect" class="external-link" href="https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-web-console/5.3-SNAPSHOT/">https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-web-console/5.3-SNAPSHOT/</a> and install using</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>Also, if you have problems installing the war with the previous method, download it manually from <a shape="rect" href="https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-web-console/5.3-SNAPSHOT/">https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-web-console/5.3-SNAPSHOT/</a> and install using</p>
+<structured-macro ac:macro-id="78e51787-f354-4e01-a1c0-ae02e83e31b1" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/install war:file:///path_to_the_war/activemq-web-console-5.3-SNAPSHOT.war?Webapp-Context=activemqweb
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Unfortunately the command</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="7bd31bb7-08a4-4eb5-8ae8-bc7c1eeb6ec0" ac:name="code" ac:schema-version="1"><plain-text-body>
osgi/install \
war:mvn:https://repository.apache.org/content/repositories/snapshots@snapshots!org.apache.activemq/activemq-web-console/5.3-SNAPSHOT/war?Webapp-Context=activemqweb
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>does not work with pax web war extender 0.5.1, but you try it if you're using the newer one.</p>
<p>If you execute</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2f39bbd9-fb88-48d5-921a-4497d9c1fe9f" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/list
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>you'll see the newly added bundle here.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="05683d0c-97d2-4db0-99b4-6a016f5cbaa4" ac:name="code" ac:schema-version="1"><plain-text-body>
[ 84] [Resolved ] [ ] [ 60] mvn_org.apache.activemq_activemq-web-console_5.3-SNAPSHOT_war (0)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>It's time t start it now</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4aa83bb4-dba0-47c2-a7a6-1a4dd98a80a9" ac:name="code" ac:schema-version="1"><plain-text-body>
smx@root:/> osgi/start 84
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p> Use the id of your bundle</p></div></div>
+<structured-macro ac:macro-id="2129747f-bc54-446f-bf13-3a7ecd75516e" ac:name="note" ac:schema-version="1"><rich-text-body><p> Use the id of your bundle</p></rich-text-body></structured-macro>
<p>The important thing to note here is that by default, web console will start an embedded broker and monitor it. So if you have a broker already running it will fail to start.</p>
-<p>Note that we have used <code>activemqweb</code> as a <code>WebApp-Context</code> while deploying the war, so the console will be available at <a shape="rect" class="external-link" href="http://localhost:8080/activemqweb" rel="nofollow">http://localhost:8080/activemqweb</a>. Visit this URL and administer your embedded broker.</p>
+<p>Note that we have used <code>activemqweb</code> as a <code>WebApp-Context</code> while deploying the war, so the console will be available at <a shape="rect" href="http://localhost:8080/activemqweb">http://localhost:8080/activemqweb</a>. Visit this URL and administer your embedded broker.</p>
<p>There a big chance that you don't want to monitor an embedded broker, but the broker you have started separately (in the OSGi runtime or elsewhere). To configure your web console to do that, you have to do the following. First, exit your OSGi runtime. Now you can edit the <code>etc/system.properties</code> file and add some configuration details. The following configuration snippet</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c2ee2fe2-7748-46ba-8ccb-34f1c15b600a" ac:name="code" ac:schema-version="1"><plain-text-body>
webconsole.type=properties
webconsole.jms.url=tcp://localhost:61616
webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root
webconsole.jmx.user=karaf
webconsole.jmx.password=karaf
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>should work fine with default broker started in the Karaf (ServiceMix). Adapt it to your specific needs.</p>
<p>Now if you run the runtime (and the console bundle), you'll notice that the console will not start the broker and will try to use one defined with the system properties.</p>
-<p>Visit <a shape="rect" class="external-link" href="http://localhost:8080/activemqweb" rel="nofollow">http://localhost:8080/activemqweb</a> and enjoy.</p></div>
+<p>Visit <a shape="rect" href="http://localhost:8080/activemqweb">http://localhost:8080/activemqweb</a> and enjoy.</p></div>
diff --git a/onmessage-method-of-messagelistener-is-never-called.xml b/onmessage-method-of-messagelistener-is-never-called.xml
index 473799a..a5ae562 100644
--- a/onmessage-method-of-messagelistener-is-never-called.xml
+++ b/onmessage-method-of-messagelistener-is-never-called.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>See <a shape="rect" href="i-am-not-receiving-any-messages-what-is-wrong.xml">I am not receiving any messages, what is wrong</a></p></div>
+<div class="wiki-content maincontent"><p>See <link><page ri:content-title="I am not receiving any messages, what is wrong"></page></link></p></div>
diff --git a/openwire-c-client.xml b/openwire-c-client.xml
index e6bd6fc..8c78b80 100644
--- a/openwire-c-client.xml
+++ b/openwire-c-client.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>This is the C library which is based on the <a shape="rect" href="openwire.xml">OpenWire</a> protocol.</p>
+<div class="wiki-content maincontent"><p>This is the C library which is based on the <link><page ri:content-title="OpenWire"></page></link> protocol.</p>
<p>You can browse the code here</p>
@@ -6,5 +6,6 @@
<p>e.g. here's an example of it in use...</p>
-<p><a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/src/examples/main.c">http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/src/examples/main.c</a></p></div>
+<p><a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/src/examples/main.c">http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/src/examples/main.c</a></p>
+</div>
diff --git a/openwire-cpp-client.xml b/openwire-cpp-client.xml
index f5e6829..c9fbf61 100644
--- a/openwire-cpp-client.xml
+++ b/openwire-cpp-client.xml
@@ -1,8 +1,8 @@
<div class="wiki-content maincontent">
-<h1 id="OpenWireCPPClient-OpenWireC++Client">OpenWire C++ Client</h1>
+<h1>OpenWire C++ Client</h1>
-<h2 id="OpenWireCPPClient-Goals">Goals</h2>
+<h2>Goals</h2>
<p> We want to be able to provide a C++ API to ActiveMQ that retains rough feature-parity with the Java API while at the same time allowing for more flexibility in application design by opening up lower levels of the event system. We have come up with an API / programming model that maximizes the ways in which the messaging library can adapt to the application using it, not the other way around. Specifically, our goals are:</p>
<ul><li>Make no assumption about the threading constraints of the containing application (specifically, allow asynchronous receives within a single-threaded application)</li><li>Make no assumption about the event loop characteristics of the containing application</li><li>Make no assumption about libraries needed – i.e. dont enforce use of a particular library or smart pointer implementation</li><li>Offer tradeoffs in flexibility versus application complexity</li><li>Provide distinctly C++-friendly APIs for asynchronous event notification</li><li>Provide pluggable data transports</li><li>Maximize portability</li></ul>
@@ -12,13 +12,13 @@
<p>When we use the term programming model, we are referring to the handling of the most complex part of asynchronous messaging APIs – message delivery to the application.</p>
-<h2 id="OpenWireCPPClient-JMS/Javaprogrammingmodel">JMS / Java programming model</h2>
+<h2>JMS / Java programming model</h2>
<p>JMS 1.1 provides two ways for an application to receive messages. One is by a blocking receive in the MsgConsumer class' receive() function. This will suspend the calling thread until a message is received. The other method is through callbacks in subclasses of MessageListener. The OnMessage function is called when a message is received on the topic or queue that the MessageListener was created for.</p>
<p>To sum up – The JMS model imposes a threading structure on the application developer. Either they must use multiple threads each doing synchronous receive() calls, or rely on a separate thread to deliver messages to them. A single-threaded model is impossible.</p>
-<h2 id="OpenWireCPPClient-WherewhatsbestforC++andJavaAPIsdiverge">Where whats best for C++ and Java APIs diverge</h2>
+<h2>Where whats best for C++ and Java APIs diverge</h2>
<p>The JMS API enforces a particular model of threading on an application. This is fine and well-accepted in the Java programming space, since Java is designed for it to be easiest to multiplex communications with threads. Threads are very easy and well-supported in Java.</p>
@@ -30,7 +30,7 @@
<p>We are proposing a three-tiered approach to provide the tradeoff between application simplicity and flexibility. The lowest level will do the least and allow the widest range of applications to use it, the next level will be much more functional, but with some design tradeoffs, and the highest we will leave up to enterprise-specific needs.</p>
-<h2 id="OpenWireCPPClient-ProposedC++APIDesign">Proposed C++ API Design</h2>
+<h2>Proposed C++ API Design</h2>
<p>The design that we are proposing consists of two layers. The core library owns no threads and acts simply as a filter – taking data from the broker in and dispatching messages if necessary. This core layer of the library is exposed to allow those C++ developers who do not want any threads other than their own managing events, and/or want to use non-TCP methods of communication with the broker. The socket to the ActiveMQ broker is to be exposed to the application by the transport layer, and data received on it is to be passed opaquely to the core library by the application. This allows for asynchronous messaging with a single-threaded program – a hard requirement for some developers.<br clear="none">
There are shortcomings to this approach. If the application blocks on some other activity and data from the broker is never processed, the TCP socket will back up and messages will build up on the broker side. Also, the single-threaded nature of the library means that the application must do all the I/O work itself, and implement a separate thread in order to make meaningful use of the blocking receive.</p>
@@ -41,15 +41,15 @@
<p>There is a third level – there is a need for higher-level, application framework libraries for messaging, that might take all control flow from the user and provide the simplest possible environment. The lower levels are designed to allow the most flexibility in the design and requirements of the third level, which is most often enterprise-specific and lies outside the scope of this document. An example of a library at this level would be one that provides a framework that makes it easy to write a completely callback-based application. Since this would require that an application be designed for it from the start, it is at this level that design decisions such as selecting a smart pointer implementation would be appropriate. It is likely that for a particular enterprise, most applications would use something like this, which would be implemented as a thin wrapper over the BrokerSession library.</p>
-<h2 id="OpenWireCPPClient-Transportlayerabstractionoverview">Transport layer abstraction overview</h2>
+<h2>Transport layer abstraction overview</h2>
<p> Similar to ActiveMQ itself, we provide a transport layer abstraction that manages connection and I/O on file descriptors. Initially only TCP socket support will be provided, but there is value in other implementations – in-process pipe, playing back from a file, UDP, etc. This layer provides logical connect, send, recv, and close operations. Transports are initialized with URIs in the same fashion that other ActiveMQ transports are.</p>
-<h2 id="OpenWireCPPClient-Corelibraryoverview">Core library overview</h2>
+<h2>Core library overview</h2>
<p>The core layer of the library provides a very simple interface – data in, messages out.</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="openwire-cpp-client.data/Core%20Library%20Usage.JPG" data-image-src="/confluence/download/attachments/35897/Core%20Library%20Usage.JPG?version=1&modificationDate=1138394355000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3261" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Core Library Usage.JPG" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="35897" data-linked-resource-container-version="8"></span></p>
+<p><image><attachment ri:filename="Core Library Usage.JPG"></attachment></image></p>
<p>When the returned file descriptor from the transport layer's connect() call reads active in the application's event loop, the application reads available data and passes that to the library. The library itself has an internal buffer that will deliver a message when one has been fully accumulated. The purpose of this disconnect is that the core library <strong>will not make any blocking I/O calls – or any system calls at all for that matter</strong>. This satisfies the portability goal, as well as ensuring that a single-threaded application can use this library without the potential for losing control of its thread.</p>
@@ -70,11 +70,11 @@
<p>The application is given two choices for message receipt. The library does this by means of one or more internal "message consumer" objects (similar to JMS MessageConsumer objects). There are two kinds – one for synchronous receives, and one for asynchronous. The synchronous consumer(BlockingMessageConsumer) offers a blocking receive that multiple threads can wait on for messages. The asynchronous message consumer uses an event-based interface, notifying the application that a message is ready via a byte written down a pipe. The NonBlockingMessageConsumer class can dispense its event file descriptor as well as received messages – the asynchronous receive() call is nonblocking and returns NULL if no message is ready.</p>
-<h2 id="OpenWireCPPClient-BrokerSessionlibraryoverview">BrokerSession library overview</h2>
+<h2>BrokerSession library overview</h2>
<p>The higher level library's interface offers a much simpler and more direct API to the developer than the first layer, as a result of having an internal thread to process data from the ActiveMQ broker.</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="openwire-cpp-client.data/BrokerSession%20Library%20Usage.JPG" data-image-src="/confluence/download/attachments/35897/BrokerSession%20Library%20Usage.JPG?version=1&modificationDate=1138394370000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3260" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="BrokerSession Library Usage.JPG" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="35897" data-linked-resource-container-version="8"></span></p>
+<p><image><attachment ri:filename="BrokerSession Library Usage.JPG"></attachment></image></p>
<p>Since the BrokerSession library contains a copy of the core library, ActiveMQ-specific code is kept encapsulated there. The code in the BrokerSession library does the legwork of managing the core library and broker communication for the application. The use of a background thread to do this and deliver incoming messages to the message consumers greatly simplifies application development.</p>
@@ -82,7 +82,7 @@
<p>This library allows both a JMS-like programming model of multiple threads waiting on message queues as well as an event-driven, select-loop model that is more common in C++ programs. This makes it adaptable to the varying requirements of new and existing C++ applications that have design constraints imposed by things other than the messaging library.</p>
-<h2 id="OpenWireCPPClient-Logginganderrorhandling">Logging and error handling</h2>
+<h2>Logging and error handling</h2>
<p>To fit with the goals of not enforcing particular dependencies and allowing easy enterprise integration, the libraries have a callback-based model for logging. The application registers a logger with the library to be called when log events occur - this logger has function callbacks for error logging, debug logging, etc. This allows the easiest integration with existing logging systems, as these callbacks can then call directly into the native logging environment (such as syslog) or log to a file, or anything else that is appropriate in the particular application.</p>
diff --git a/openwire-version-2-specification.xml b/openwire-version-2-specification.xml
index 91178cb..c86c26a 100644
--- a/openwire-version-2-specification.xml
+++ b/openwire-version-2-specification.xml
@@ -1,10 +1,7 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">OpenWire Version 2 is not the latest version.</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>This article references OpenWire V2 which is no longer the latest version. The formatting and encoding rules in this article are still valid for later OpenWire versions, but later versions define additional fields in the OpenWire commands. The default settings shown in this article may not reflect the current defaults, see <a shape="rect" href="configuring-wire-formats.xml">this page</a> for the latest default OpenWire settings.</p></div></div><h2 id="OpenWireVersion2Specification-Overview">Overview</h2><p>OpenWire is used to marshal objects to byte arrays and back. We will refer to the marshaled objects as commands.</p><p>A TCP network connection would see multiple commands back to back on the stream. Commands are not delimited in anyway and are variable sized.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[+---------+ +---------+ +---------+
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="e57eb113-a915-4ebf-8acb-20267863ecd8" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">OpenWire Version 2 is not the latest version.</parameter><rich-text-body><p>This article references OpenWire V2 which is no longer the latest version. The formatting and encoding rules in this article are still valid for later OpenWire versions, but later versions define additional fields in the OpenWire commands. The default settings shown in this article may not reflect the current defaults, see <link><page ri:content-title="Configuring Wire Formats"></page><plain-text-link-body>this page</plain-text-link-body></link> for the latest default OpenWire settings.</p></rich-text-body></structured-macro><h2>Overview</h2><p>OpenWire is used to marshal objects to byte arrays and back. We will refer to the marshaled objects as commands.</p><p>A TCP network connection would see multiple commands back to back on the stream. Commands are not delimited in anyway and are variable sized.</p><structured-macro ac:macro-id="dcbac81c-4b75-4411-b53d-36724c440353" ac:name="code" ac:schema-version="1"><plain-text-body>+---------+ +---------+ +---------+
| command | | command | .... | command |
+---------+ +---------+ +---------+
-]]></script>
-</div></div><p>All data primitive types used in the encoded commands are encoded in big-endian/network byte order.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[primitive types and encoding:
+</plain-text-body></structured-macro><p>All data primitive types used in the encoded commands are encoded in big-endian/network byte order.</p><structured-macro ac:macro-id="36d2f345-0a5b-40c9-8c00-ef7ba01c436e" ac:name="code" ac:schema-version="1"><plain-text-body>primitive types and encoding:
| | | | | |
+----------+ | +-----------+ | +-----------+ | +-----------+ | +-----------+ | +-----------+ | +-----------+
| byte | | | char | | | short | | | int | | | long | | | float | | | double |
@@ -12,14 +9,10 @@
| 1 octect | | | 2 octects | | | 2 octects | | | 4 octects | | | 8 octects | | | 4 octects | | | 8 octects |
+----------+ | +-----------+ | +-----------+ | +-----------+ | +-----------+ | +-----------+ | +-----------+
| | | | | |
-]]></script>
-</div></div><h2 id="OpenWireVersion2Specification-WireFormatNegotiation">Wire Format Negotiation</h2><p>OpenWire is an extensible in that it supports adding new encoding options while still being backward compatible with previous versions of the protocol. Every OpenWire protocol session initially starts with all encoding options turned off and at version 1 of command marshalers. An initial WIREFORMAT_INFO command is exchanged between the two nodes so that additional encoding features can be enabled. If both sides request an encoding feature to be enabled then it will be enabled. The command marshalers used will be the highest version that they both support.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[+-------------------------+ +---------+ +---------+ +---------+
+</plain-text-body></structured-macro><h2>Wire Format Negotiation</h2><p>OpenWire is an extensible in that it supports adding new encoding options while still being backward compatible with previous versions of the protocol. Every OpenWire protocol session initially starts with all encoding options turned off and at version 1 of command marshalers. An initial WIREFORMAT_INFO command is exchanged between the two nodes so that additional encoding features can be enabled. If both sides request an encoding feature to be enabled then it will be enabled. The command marshalers used will be the highest version that they both support.</p><structured-macro ac:macro-id="3d379f79-d70f-490d-a9f8-67ece215e6ea" ac:name="code" ac:schema-version="1"><plain-text-body>+-------------------------+ +---------+ +---------+ +---------+
| WIREFORMAT_INFO command | | command | | command | .... | command |
+-------------------------+ +---------+ +---------+ +---------+
-]]></script>
-</div></div><h2 id="OpenWireVersion2Specification-CommandEncoding">Command Encoding</h2><p>Every command is encoded as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[command encoding:
+</plain-text-body></structured-macro><h2>Command Encoding</h2><p>Every command is encoded as follows:</p><structured-macro ac:macro-id="60b03de1-6016-4994-bce7-63e7e51f772e" ac:name="code" ac:schema-version="1"><plain-text-body>command encoding:
[=If SizePrefixDisabled =]
[ option is not enabled. ]
[ +------+ ] +------+-------------------------+
@@ -28,9 +21,7 @@
[ | int | ] | byte | (size-1) octects |
[ +------+ ] +------+-------------------------+
[========================]
-]]></script>
-</div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Field</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>size</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Holds how many subsequent bytes are in the the command</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>type</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Command type identifier</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>command-specific-fields</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The data for the command. It is encoding depends on the type used</p></td></tr></tbody></table></div><p>If a command type does not have any command specific content, then size would be 1.</p><p>Prefixing the size on every command is done to aid in non-blocking IO processing so that receiver can easily determine when a whole command has been received and can be processed. But finding out the size of command takes additional buffering on the sender size and is not needed if the receiver is doing blocking IO. If the SizePrefixDisabled option is enabled after the exchange of WIREFORMAT_INFO packets, then every subsequent command will not have the size prefixed.</p><h2 id="OpenWireVersion2Specification-CommandTypes">Command Types</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Type Identifier</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Command</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>WIREFORMAT_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>BROKER_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>3</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CONNECTION_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>4</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>SESSION_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>5</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CONSUMER_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>6</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>PRODUCER_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>7</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>TRANSACTION_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>8</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>DESTINATION_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>9</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>REMOVE_SUBSCRIPTION_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>10</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>KEEP_ALIVE_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>11</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>SHUTDOWN_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>12</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>REMOVE_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>14</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CONTROL_COMMAND</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>15</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>FLUSH_COMMAND</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>16</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CONNECTION_ERROR</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>17</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CONSUMER_CONTROL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>18</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CONNECTION_CONTROL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>21</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>MESSAGE_DISPATCH</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>22</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>MESSAGE_ACK</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>23</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_MESSAGE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>24</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_BYTES_MESSAGE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>25</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_MAP_MESSAGE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>26</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_OBJECT_MESSAGE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>27</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_STREAM_MESSAGE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>28</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_TEXT_MESSAGE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>30</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>RESPONSE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>31</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>EXCEPTION_RESPONSE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>32</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>DATA_RESPONSE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>33</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>DATA_ARRAY_RESPONSE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>34</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>INTEGER_RESPONSE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>40</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>DISCOVERY_EVENT</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>50</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>JOURNAL_ACK</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>52</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>JOURNAL_REMOVE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>53</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>JOURNAL_TRACE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>54</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>JOURNAL_TRANSACTION</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>55</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>DURABLE_SUBSCRIPTION_INFO</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>60</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>PARTIAL_COMMAND</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>61</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>PARTIAL_LAST_COMMAND</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>65</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>REPLAY</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>70</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>BYTE_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>71</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CHAR_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>72</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>SHORT_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>73</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>INTEGER_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>74</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>LONG_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>75</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>DOUBLE_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>76</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>FLOAT_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>77</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>STRING_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>78</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>BOOLEAN_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>79</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>BYTE_ARRAY_TYPE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>90</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>MESSAGE_DISPATCH_NOTIFICATION</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>91</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>NETWORK_BRIDGE_FILTER</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>100</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_QUEUE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>101</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_TOPIC</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>102</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_TEMP_QUEUE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>103</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_TEMP_TOPIC</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>110</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>MESSAGE_ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>111</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_LOCAL_TRANSACTION_ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>112</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ACTIVEMQ_XA_TRANSACTION_ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>120</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CONNECTION_ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>121</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>SESSION_ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>122</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CONSUMER_ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>123</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>PRODUCER_ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>124</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>BROKER_ID</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr></tbody></table></div><h3 id="OpenWireVersion2Specification-CommandFieldEncoding">Command Field Encoding</h3><p>All OpenWire commands use the same algorithm when encoding their fields. The algorithm restricts commands to use fields that are of the following type:</p><ul><li>Java primitive types</li><li>String</li><li>Byte Arrays</li><li>N Sized Byte Arrays</li><li>Throwable</li><li>Nested OpenWire commands</li><li>Nested OpenWire command arrays</li><li>Cached Nested OpenWire commands</li></ul><p>Notice that OpenWire commands can nest other OpenWire commands in it's fields. Care must be taken that only acyclic graphs of commands are marshaled.</p><h4 id="OpenWireVersion2Specification-StringTypeEncoding">String Type Encoding</h4><p>Strings fields may be null. If it is null then it encodes to a single "0" byte.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[string encoding:
+</plain-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>size</p></td><td colspan="1" rowspan="1"><p>Holds how many subsequent bytes are in the the command</p></td></tr><tr><td colspan="1" rowspan="1"><p>type</p></td><td colspan="1" rowspan="1"><p>Command type identifier</p></td></tr><tr><td colspan="1" rowspan="1"><p>command-specific-fields</p></td><td colspan="1" rowspan="1"><p>The data for the command. It is encoding depends on the type used</p></td></tr></tbody></table><p>If a command type does not have any command specific content, then size would be 1.</p><p>Prefixing the size on every command is done to aid in non-blocking IO processing so that receiver can easily determine when a whole command has been received and can be processed. But finding out the size of command takes additional buffering on the sender size and is not needed if the receiver is doing blocking IO. If the SizePrefixDisabled option is enabled after the exchange of WIREFORMAT_INFO packets, then every subsequent command will not have the size prefixed.</p><h2>Command Types</h2><table><tbody><tr><th colspan="1" rowspan="1"><p>Type Identifier</p></th><th colspan="1" rowspan="1"><p>Command</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>WIREFORMAT_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>2</p></td><td colspan="1" rowspan="1"><p>BROKER_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>3</p></td><td colspan="1" rowspan="1"><p>CONNECTION_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>4</p></td><td colspan="1" rowspan="1"><p>SESSION_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>5</p></td><td colspan="1" rowspan="1"><p>CONSUMER_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>6</p></td><td colspan="1" rowspan="1"><p>PRODUCER_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>7</p></td><td colspan="1" rowspan="1"><p>TRANSACTION_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>8</p></td><td colspan="1" rowspan="1"><p>DESTINATION_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>9</p></td><td colspan="1" rowspan="1"><p>REMOVE_SUBSCRIPTION_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>10</p></td><td colspan="1" rowspan="1"><p>KEEP_ALIVE_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>11</p></td><td colspan="1" rowspan="1"><p>SHUTDOWN_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>12</p></td><td colspan="1" rowspan="1"><p>REMOVE_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>14</p></td><td colspan="1" rowspan="1"><p>CONTROL_COMMAND</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>15</p></td><td colspan="1" rowspan="1"><p>FLUSH_COMMAND</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>16</p></td><td colspan="1" rowspan="1"><p>CONNECTION_ERROR</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>17</p></td><td colspan="1" rowspan="1"><p>CONSUMER_CONTROL</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>18</p></td><td colspan="1" rowspan="1"><p>CONNECTION_CONTROL</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>21</p></td><td colspan="1" rowspan="1"><p>MESSAGE_DISPATCH</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>22</p></td><td colspan="1" rowspan="1"><p>MESSAGE_ACK</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>23</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_MESSAGE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>24</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_BYTES_MESSAGE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>25</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_MAP_MESSAGE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>26</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_OBJECT_MESSAGE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>27</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_STREAM_MESSAGE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>28</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_TEXT_MESSAGE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>30</p></td><td colspan="1" rowspan="1"><p>RESPONSE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>31</p></td><td colspan="1" rowspan="1"><p>EXCEPTION_RESPONSE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>32</p></td><td colspan="1" rowspan="1"><p>DATA_RESPONSE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>33</p></td><td colspan="1" rowspan="1"><p>DATA_ARRAY_RESPONSE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>34</p></td><td colspan="1" rowspan="1"><p>INTEGER_RESPONSE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>40</p></td><td colspan="1" rowspan="1"><p>DISCOVERY_EVENT</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>50</p></td><td colspan="1" rowspan="1"><p>JOURNAL_ACK</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>52</p></td><td colspan="1" rowspan="1"><p>JOURNAL_REMOVE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>53</p></td><td colspan="1" rowspan="1"><p>JOURNAL_TRACE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>54</p></td><td colspan="1" rowspan="1"><p>JOURNAL_TRANSACTION</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>55</p></td><td colspan="1" rowspan="1"><p>DURABLE_SUBSCRIPTION_INFO</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>60</p></td><td colspan="1" rowspan="1"><p>PARTIAL_COMMAND</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>61</p></td><td colspan="1" rowspan="1"><p>PARTIAL_LAST_COMMAND</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>65</p></td><td colspan="1" rowspan="1"><p>REPLAY</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>70</p></td><td colspan="1" rowspan="1"><p>BYTE_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>71</p></td><td colspan="1" rowspan="1"><p>CHAR_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>72</p></td><td colspan="1" rowspan="1"><p>SHORT_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>73</p></td><td colspan="1" rowspan="1"><p>INTEGER_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>74</p></td><td colspan="1" rowspan="1"><p>LONG_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>75</p></td><td colspan="1" rowspan="1"><p>DOUBLE_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>76</p></td><td colspan="1" rowspan="1"><p>FLOAT_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>77</p></td><td colspan="1" rowspan="1"><p>STRING_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>78</p></td><td colspan="1" rowspan="1"><p>BOOLEAN_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>79</p></td><td colspan="1" rowspan="1"><p>BYTE_ARRAY_TYPE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>90</p></td><td colspan="1" rowspan="1"><p>MESSAGE_DISPATCH_NOTIFICATION</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>91</p></td><td colspan="1" rowspan="1"><p>NETWORK_BRIDGE_FILTER</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>100</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_QUEUE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>101</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_TOPIC</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>102</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_TEMP_QUEUE</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>103</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_TEMP_TOPIC</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>110</p></td><td colspan="1" rowspan="1"><p>MESSAGE_ID</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>111</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_LOCAL_TRANSACTION_ID</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>112</p></td><td colspan="1" rowspan="1"><p>ACTIVEMQ_XA_TRANSACTION_ID</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>120</p></td><td colspan="1" rowspan="1"><p>CONNECTION_ID</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>121</p></td><td colspan="1" rowspan="1"><p>SESSION_ID</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>122</p></td><td colspan="1" rowspan="1"><p>CONSUMER_ID</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>123</p></td><td colspan="1" rowspan="1"><p>PRODUCER_ID</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>124</p></td><td colspan="1" rowspan="1"><p>BROKER_ID</p></td><td colspan="1" rowspan="1"><p> </p></td></tr></tbody></table><h3>Command Field Encoding</h3><p>All OpenWire commands use the same algorithm when encoding their fields. The algorithm restricts commands to use fields that are of the following type:</p><ul><li>Java primitive types</li><li>String</li><li>Byte Arrays</li><li>N Sized Byte Arrays</li><li>Throwable</li><li>Nested OpenWire commands</li><li>Nested OpenWire command arrays</li><li>Cached Nested OpenWire commands</li></ul><p>Notice that OpenWire commands can nest other OpenWire commands in it's fields. Care must be taken that only acyclic graphs of commands are marshaled.</p><h4>String Type Encoding</h4><p>Strings fields may be null. If it is null then it encodes to a single "0" byte.</p><structured-macro ac:macro-id="d6a2ba0b-657b-445d-9c5d-75ae56cb843b" ac:name="code" ac:schema-version="1"><plain-text-body>string encoding:
[=If not-null is 1===========]
+----------+ [ +-------+----------------+ ]
| not-null | [ | size | encoded-string | ]
@@ -38,9 +29,7 @@
| byte | [ | short | size octects | ]
+----------+ [ +-------+----------------+ ]
[============================]
-]]></script>
-</div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Field</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>not-null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1 if the string is not null, 0 if the string is null</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>size</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of bytes of the UTF-8 Encoded string</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>encoded-string</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The UTF-8 encoded form of the string</p></td></tr></tbody></table></div><h3 id="OpenWireVersion2Specification-ByteArrayTypeEncoding">Byte Array Type Encoding</h3><p>Byte array fields may be null. If it is null then it encodes to a single "0" byte.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[byte-array encoding:
+</plain-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>not-null</p></td><td colspan="1" rowspan="1"><p>1 if the string is not null, 0 if the string is null</p></td></tr><tr><td colspan="1" rowspan="1"><p>size</p></td><td colspan="1" rowspan="1"><p>The number of bytes of the UTF-8 Encoded string</p></td></tr><tr><td colspan="1" rowspan="1"><p>encoded-string</p></td><td colspan="1" rowspan="1"><p>The UTF-8 encoded form of the string</p></td></tr></tbody></table><h3>Byte Array Type Encoding</h3><p>Byte array fields may be null. If it is null then it encodes to a single "0" byte.</p><structured-macro ac:macro-id="944ceaf4-84b2-4dc5-b96e-f4c3a3af76cf" ac:name="code" ac:schema-version="1"><plain-text-body>byte-array encoding:
[=If not-null is 1========]
+----------+ [ +------+--------------+ ]
| not-null | [ | size | data | ]
@@ -48,17 +37,13 @@
| byte | [ | int | size octects | ]
+----------+ [ +------+--------------+ ]
[=========================]
-]]></script>
-</div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Field</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>not-null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1 if the byte array is not null, 0 if it is null</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>size</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of bytes in the byte array</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>data</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The data of the byte array</p></td></tr></tbody></table></div><h3 id="OpenWireVersion2Specification-NSizedByteArrayTypeEncoding">N Sized Byte Array Type Encoding</h3><p>Fixed Size Byte array fields may NOT be null and their length must be N length. Used for byte arrays that are always a fixed size.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[N-sized-byte-array encoding:
+</plain-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>not-null</p></td><td colspan="1" rowspan="1"><p>1 if the byte array is not null, 0 if it is null</p></td></tr><tr><td colspan="1" rowspan="1"><p>size</p></td><td colspan="1" rowspan="1"><p>The number of bytes in the byte array</p></td></tr><tr><td colspan="1" rowspan="1"><p>data</p></td><td colspan="1" rowspan="1"><p>The data of the byte array</p></td></tr></tbody></table><h3>N Sized Byte Array Type Encoding</h3><p>Fixed Size Byte array fields may NOT be null and their length must be N length. Used for byte arrays that are always a fixed size.</p><structured-macro ac:macro-id="dd7334a1-9fca-4ec6-aae8-69e9dd360d4d" ac:name="code" ac:schema-version="1"><plain-text-body>N-sized-byte-array encoding:
+-----------+
| data |
+-----------+
| N octects |
+-----------+
-]]></script>
-</div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Field</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>data</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The data of the byte array</p></td></tr></tbody></table></div><h3 id="OpenWireVersion2Specification-ThrowableTypeEncoding">Throwable Type Encoding</h3><p>Throwable fields may be null. If it is null then it encodes to a single "0" byte.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[throwable encoding:
+</plain-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>data</p></td><td colspan="1" rowspan="1"><p>The data of the byte array</p></td></tr></tbody></table><h3>Throwable Type Encoding</h3><p>Throwable fields may be null. If it is null then it encodes to a single "0" byte.</p><structured-macro ac:macro-id="217ef4df-fac6-467f-911c-09ae8f011345" ac:name="code" ac:schema-version="1"><plain-text-body>throwable encoding:
[=If not-null is 1===========================================================================]
[ [=If StackTraceEnabled option is enabled.==================] ]
[ [ [=Repeated size times======================] ] ]
@@ -70,9 +55,7 @@
[ [ [============================================] ] ]
[ [==========================================================] ]
[============================================================================================]
-]]></script>
-</div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Field</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>not-null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1 if the Throwable not null, 0 if the Throwable is null</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>exception-name</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The class name of the exception</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>message</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The exception message</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>size</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of stack frames in the stack trace</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>class</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the class in a stack frame</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>method</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the method in a stack frame</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>file</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the file in a stack frame</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>line-number</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The line number in a stack frame</p></td></tr></tbody></table></div><p>If the StackTraceEnabled encoding option is enabled after the exchange of WIREFORMAT_INFO packets, then every Throwable filed will have stack trace data appended to it.</p><h3 id="OpenWireVersion2Specification-NestedCommandTypeEncoding">Nested Command Type Encoding</h3><p>Nested command fields may be null. If it is null then it encodes to a single "0" byte.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[nested-object encoding:
+</plain-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>not-null</p></td><td colspan="1" rowspan="1"><p>1 if the Throwable not null, 0 if the Throwable is null</p></td></tr><tr><td colspan="1" rowspan="1"><p>exception-name</p></td><td colspan="1" rowspan="1"><p>The class name of the exception</p></td></tr><tr><td colspan="1" rowspan="1"><p>message</p></td><td colspan="1" rowspan="1"><p>The exception message</p></td></tr><tr><td colspan="1" rowspan="1"><p>size</p></td><td colspan="1" rowspan="1"><p>The number of stack frames in the stack trace</p></td></tr><tr><td colspan="1" rowspan="1"><p>class</p></td><td colspan="1" rowspan="1"><p>The name of the class in a stack frame</p></td></tr><tr><td colspan="1" rowspan="1"><p>method</p></td><td colspan="1" rowspan="1"><p>The name of the method in a stack frame</p></td></tr><tr><td colspan="1" rowspan="1"><p>file</p></td><td colspan="1" rowspan="1"><p>The name of the file in a stack frame</p></td></tr><tr><td colspan="1" rowspan="1"><p>line-number</p></td><td colspan="1" rowspan="1"><p>The line number in a stack frame</p></td></tr></tbody></table><p>If the StackTraceEnabled encoding option is enabled after the exchange of WIREFORMAT_INFO packets, then every Throwable filed will have stack trace data appended to it.</p><h3>Nested Command Type Encoding</h3><p>Nested command fields may be null. If it is null then it encodes to a single "0" byte.</p><structured-macro ac:macro-id="931597fa-9ac8-48c5-b243-5c3a3ff54511" ac:name="code" ac:schema-version="1"><plain-text-body>nested-object encoding:
[=If not-null is 1===================]
+----------+ [ +------+-------------------------+ ]
| not-null | [ | type | command-specific-fields | ]
@@ -80,9 +63,7 @@
| byte | [ | byte | variable sized | ]
+----------+ [ +------+-------------------------+ ]
[====================================]
-]]></script>
-</div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Field</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>not-null</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1 if the Throwable not null, 0 if the Throwable is null</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>type</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Command type identifier</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>command-specific-fields</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The data for the command. It is encoding depends on the type used</p></td></tr></tbody></table></div><h3 id="OpenWireVersion2Specification-CachedNestedCommandTypeEncoding">Cached Nested Command Type Encoding</h3><p>Nested Command types can be cached so that subsequent marshaling operations of the same object result in a smaller on the wire size. By default the CacheEnabled option is not enabled and therefore standard nested-object encoding is used.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cached-object-encoding:
+</plain-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>not-null</p></td><td colspan="1" rowspan="1"><p>1 if the Throwable not null, 0 if the Throwable is null</p></td></tr><tr><td colspan="1" rowspan="1"><p>type</p></td><td colspan="1" rowspan="1"><p>Command type identifier</p></td></tr><tr><td colspan="1" rowspan="1"><p>command-specific-fields</p></td><td colspan="1" rowspan="1"><p>The data for the command. It is encoding depends on the type used</p></td></tr></tbody></table><h3>Cached Nested Command Type Encoding</h3><p>Nested Command types can be cached so that subsequent marshaling operations of the same object result in a smaller on the wire size. By default the CacheEnabled option is not enabled and therefore standard nested-object encoding is used.</p><structured-macro ac:macro-id="bed186ab-21d4-4339-ae3c-b1d0e7d0ec19" ac:name="code" ac:schema-version="1"><plain-text-body>cached-object-encoding:
[=If CacheEnabled option is enabled=====================]
[ [=If new-value is 1===========] ]
[ +-----------+-------+ [ +-------------------------+ ] ]
@@ -100,6 +81,5 @@
[ | nested-object | ]
[ +-------------------------+ ]
[=====================================]
-]]></script>
-</div></div><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Field</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>new-value</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1 if the value is not in the cache, 0 if it already is in the cache</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>key</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Key used to identify the value in the cache</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>command-specific-fields</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The data for the command. It is encoding depends on the type used</p></td></tr></tbody></table></div><h2 id="OpenWireVersion2Specification-LooseEncoding">Loose Encoding</h2><p>The default encoding explained so far is called "loose encoding" and is the default encoding used when OpenWire if first initialized. Loose encoding is simple to implement does not add much CPU overhead to the marshaling/unmarshaling process. It is able to marshal an object graph in single pass of the object tree.</p><h2 id="OpenWireVersion2Specification-TightEncoding">Tight Encoding</h2><p>Another encoding option is supported by OpenWire which is called TightEncoding. When tight encoding is used, it uses bit streams to marshal all the boolean values that would have taken up a byte in loose encoding to a bit in the bit stream. To build the bit stream 2 passes through the object graph are taken so this is more CPU intensive marshaling process but it produces a smaller on the wire size.</p></div>
+</plain-text-body></structured-macro><table><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>new-value</p></td><td colspan="1" rowspan="1"><p>1 if the value is not in the cache, 0 if it already is in the cache</p></td></tr><tr><td colspan="1" rowspan="1"><p>key</p></td><td colspan="1" rowspan="1"><p>Key used to identify the value in the cache</p></td></tr><tr><td colspan="1" rowspan="1"><p>command-specific-fields</p></td><td colspan="1" rowspan="1"><p>The data for the command. It is encoding depends on the type used</p></td></tr></tbody></table><h2>Loose Encoding</h2><p>The default encoding explained so far is called "loose encoding" and is the default encoding used when OpenWire if first initialized. Loose encoding is simple to implement does not add much CPU overhead to the marshaling/unmarshaling process. It is able to marshal an object graph in single pass of the object tree.</p><h2>Tight Encoding</h2><p>Another encoding option is supported by OpenWire which is called TightEncoding. When tight encoding is used, it uses bit streams to marshal all the boolean values that would have taken up a byte in loose encoding to a bit in the bit stream. To build the bit stream 2 passes through the object graph are taken so this is more CPU intensive marshaling process but it produces a smaller on the wire size.</p></div>
diff --git a/openwire.xml b/openwire.xml
index 1a27fb8..3e0e30e 100644
--- a/openwire.xml
+++ b/openwire.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>OpenWire is our cross language <a shape="rect" href="wire-protocol.xml">Wire Protocol</a> to allow native access to ActiveMQ from a number of different languages and platforms. The Java OpenWire transport is the default transport in ActiveMQ 4.x or later. For other languages see the following...</p><ul><li class="confluence-link"><a shape="rect" class="external-link" href="http://activemq.apache.org/nms/">NMS</a> for the C# API to Messaging and the OpenWire implementation in C#</li><li class="confluence-link"><a shape="rect" href="cms/index.xml">CMS</a> for the C++ API to Messaging and the OpenWire implementation in C++</li></ul><p><strong>Note</strong> that you can also use <a shape="rect" href="stomp.xml">Stomp</a> to access ActiveMQ from many different languages as well as use <a shape="rect" href="how-do-i-access-activemq-from-c.xml">GCJ</a> or <a shape="rect" class="external-link" href="http://activemq.apache.org/nms/">IKVM</a> to access the Java code for ActiveMQ from C/C++ or .Net respectively without using OpenWire.</p><h3 id="OpenWire-Howitworks">How it works</h3><p>OpenWire works by code generating language specific commands and marshaling code which understands the core OpenWire protocol. Then we can write language specific extensions for the low level protocol to provide a nice and easy to use client API in different languages.</p><p>To give you an idea, <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-openwire-generator/src/main/java/org/apache/activemq/openwire/tool/">here</a> are the Java classes which code generate the C#, Java, C, and CPP client code.</p><p>Since OpenWire automates the creation of language specific <a shape="rect" href="wire-protocol.xml">Wire Protocol</a> implementations; then its a matter of wrapping the language specific TCP/IP socket code and wrapping the API in some easy to use functions/classes.</p><h3 id="OpenWire-Specification">Specification</h3><p>For a detailed specification of what you will see on the wire:</p><ul><li><a shape="rect" href="openwire-version-2-specification.xml">OpenWire Version 2 Specification</a></li></ul></div>
+<div class="wiki-content maincontent"><p>OpenWire is our cross language <link><page ri:content-title="Wire Protocol"></page></link> to allow native access to ActiveMQ from a number of different languages and platforms. The Java OpenWire transport is the default transport in ActiveMQ 4.x or later. For other languages see the following...</p><ul><li class="confluence-link"><a shape="rect" href="http://activemq.apache.org/nms/">NMS</a> for the C# API to Messaging and the OpenWire implementation in C#</li><li class="confluence-link"><link><page ri:content-title="Index" ri:space-key="AMQCPP"></page><plain-text-link-body>CMS</plain-text-link-body></link> for the C++ API to Messaging and the OpenWire implementation in C++</li></ul><p><strong>Note</strong> that you can also use <link><page ri:content-title="Stomp"></page></link> to access ActiveMQ from many different languages as well as use <link><page ri:content-title="How do I access ActiveMQ from C"></page><plain-text-link-body>GCJ</plain-text-link-body></link> or <a shape="rect" href="http://activemq.apache.org/nms/">IKVM</a> to access the Java code for ActiveMQ from C/C++ or .Net respectively without using OpenWire.</p><h3>How it works</h3><p>OpenWire works by code generating language specific commands and marshaling code which understands the core OpenWire protocol. Then we can write language specific extensions for the low level protocol to provide a nice and easy to use client API in different languages.</p><p>To give you an idea, <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-openwire-generator/src/main/java/org/apache/activemq/openwire/tool/">here</a> are the Java classes which code generate the C#, Java, C, and CPP client code.</p><p>Since OpenWire automates the creation of language specific <link><page ri:content-title="Wire Protocol"></page></link> implementations; then its a matter of wrapping the language specific TCP/IP socket code and wrapping the API in some easy to use functions/classes.</p><h3>Specification</h3><p>For a detailed specification of what you will see on the wire:</p><ul><li><link><page ri:content-title="OpenWire Version 2 Specification"></page></link></li></ul></div>
diff --git a/optimized-acknowledgement.xml b/optimized-acknowledgement.xml
index 0c5723d..f90b209 100644
--- a/optimized-acknowledgement.xml
+++ b/optimized-acknowledgement.xml
@@ -1,31 +1,25 @@
-<div class="wiki-content maincontent"><h2 id="OptimizedAcknowledgement-Overview">Overview</h2>
+<div class="wiki-content maincontent"><h2>Overview</h2>
<p>ActiveMQ supports acknowledging a range of messages in a single batch operations. This option is disabled by default but can be used to improve throughput in some circumstances as it decreases load on the broker. Consider enabling it for your performance test scenario to see if it is applicable.</p>
-<h3 id="OptimizedAcknowledgement-EnablingOptimizedAcknowledgementsusingaConnectionURI">Enabling Optimized Acknowledgements using a Connection URI</h3>
+<h3>Enabling Optimized Acknowledgements using a Connection URI</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-cf = new ActiveMQConnectionFactory("tcp://locahost:61616?jms.optimizeAcknowledge=true");
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="ff5918d5-cf60-480e-8c91-0143e11d8c87" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
+cf = new ActiveMQConnectionFactory("tcp://locahost:61616?jms.optimizeAcknowledge=true");
+</plain-text-body></structured-macro>
-<h3 id="OptimizedAcknowledgement-EnablingOptimizedAcknowledgementsattheConnectionFactoryLevel">Enabling Optimized Acknowledgements at the ConnectionFactory Level</h3>
+<h3>Enabling Optimized Acknowledgements at the ConnectionFactory Level</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="df0f6cc4-b780-4671-b0e8-3985ce49ee62" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
((ActiveMQConnectionFactory)connectionFactory).setOptimizeAcknowledge(true);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="OptimizedAcknowledgement-EnablingOptimizedAcknowledgementsattheConnectionLevel">Enabling Optimized Acknowledgements at the Connection Level</h3>
+<h3>Enabling Optimized Acknowledgements at the Connection Level</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="0bb6ad1b-7bed-4ddd-89ae-679dc2d902a3" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
((ActiveMQConnection)connection).setOptimizeAcknowledge(true);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="OptimizedAcknowledgement-setOptimizeAcknowledgeTimeOut(5.6)">setOptimizeAcknowledgeTimeOut (5.6)</h3>
+<h3>setOptimizeAcknowledgeTimeOut (5.6)</h3>
<p>Since 5.4.2 there is a default timeout on a batch optimized acknowledge which ensures that acks are timely even if consumers are slow. On slow networks, the timeout can expire before the batch limit is reached so the reduced bandwith utilisation is bypassed. In version 5.6, the timeout is configurable via the optimizeAcknowledgeTimeOut attribute. Set as above via the connectiion URI or at the factory and connection level. The default value is 300ms, a value of 0 disables.</p></div>
diff --git a/osgi-integration.xml b/osgi-integration.xml
index fd6025a..ea70c95 100644
--- a/osgi-integration.xml
+++ b/osgi-integration.xml
@@ -1,46 +1,26 @@
-<div class="wiki-content maincontent"><h1 id="OSGiIntegration-Introduction">Introduction</h1><p>This article will provide more details on how to use ActiveMQ in <a shape="rect" class="external-link" href="http://karaf.apache.org/">Apache Karaf</a>, small OSGi based runtime. Apache Karaf was previously know as <em>ServiceMix kernel</em>, so informations found here are applicable to <a shape="rect" class="external-link" href="http://servicemix.apache.org/home.html">Apache ServiceMix Enterprise Service Bus</a> as well.</p><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Procedures described in this article were tested using Apache karaf 2.3.0</p></div></div><h1 id="OSGiIntegration-Installation">Installation</h1><p>ActiveMQ provides Karaf features which will help you integrate and use the broker in OSGi environment. For starters you need to add the features URL to Karaf. For version 5.9.0 you can do it like this:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[karaf@root> features:chooseurl activemq 5.9.0
-]]></script>
-</div></div><p>After that you should see newly added features</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[karaf@root> features:list
+<div class="wiki-content maincontent"><h1>Introduction</h1><p>This article will provide more details on how to use ActiveMQ in <a shape="rect" href="http://karaf.apache.org/">Apache Karaf</a>, small OSGi based runtime. Apache Karaf was previously know as <em>ServiceMix kernel</em>, so informations found here are applicable to <a shape="rect" href="http://servicemix.apache.org/home.html">Apache ServiceMix Enterprise Service Bus</a> as well.</p><structured-macro ac:macro-id="2c896130-7d9d-44e3-90fe-6c0a154002c8" ac:name="note" ac:schema-version="1"><rich-text-body><p>Procedures described in this article were tested using Apache karaf 2.3.0</p></rich-text-body></structured-macro><h1>Installation</h1><p>ActiveMQ provides Karaf features which will help you integrate and use the broker in OSGi environment. For starters you need to add the features URL to Karaf. For version 5.9.0 you can do it like this:</p><structured-macro ac:macro-id="ce83faf0-9653-4d33-a754-abce466518f4" ac:name="code" ac:schema-version="1"><plain-text-body>karaf@root> features:chooseurl activemq 5.9.0
+</plain-text-body></structured-macro><p>After that you should see newly added features</p><structured-macro ac:macro-id="ecea4b99-311c-42a3-a2bb-38c7f41af388" ac:name="code" ac:schema-version="1"><plain-text-body>karaf@root> features:list
State Version Name Repository
[uninstalled] [5.9.0 ] activemq-broker activemq-5.9.0
[uninstalled] [5.9.0 ] activemq-http activemq-5.9.0
[uninstalled] [5.9.0 ] activemq-camel activemq-5.9.0
[uninstalled] [5.9.0 ] activemq-web-console activemq-5.9.0
-]]></script>
-</div></div><p>Installing and running the broker is as simple as installing <code>activemq-broker</code> feature, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[karaf@root> features:install activemq-broker
-]]></script>
-</div></div><p>This will install and start the full broker (including the web console), just as if you started the standalone distribution.</p><h1 id="OSGiIntegration-BrokerConfiguration">Broker Configuration</h1><p>Broker is configured using OSGi Config Admin mechanism and could be easily managed in <a shape="rect" class="external-link" href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/configuration.html">Karaf</a>. Configuration can be done by modifying <code>${KARAF_BASE}/etc/org.apache.activemq.server-default.cfg</code> file or respective config admin property. An example of the file looks like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[broker-name=amq-broker
+</plain-text-body></structured-macro><p>Installing and running the broker is as simple as installing <code>activemq-broker</code> feature, like</p><structured-macro ac:macro-id="826ce5f5-c195-4d48-929e-80b8562c7b6b" ac:name="code" ac:schema-version="1"><plain-text-body>karaf@root> features:install activemq-broker
+</plain-text-body></structured-macro><p>This will install and start the full broker (including the web console), just as if you started the standalone distribution.</p><h1>Broker Configuration</h1><p>Broker is configured using OSGi Config Admin mechanism and could be easily managed in <a shape="rect" href="http://karaf.apache.org/manual/latest-2.3.x/users-guide/configuration.html">Karaf</a>. Configuration can be done by modifying <code>${KARAF_BASE}/etc/org.apache.activemq.server-default.cfg</code> file or respective config admin property. An example of the file looks like</p><structured-macro ac:macro-id="e6d13142-ca34-4c78-b06d-64f022e58b88" ac:name="code" ac:schema-version="1"><plain-text-body>broker-name=amq-broker
data=${karaf.data}/${broker-name}
-config=${karaf.base}/etc/activemq.xml]]></script>
-</div></div><p>Mandatory properties are listed in the following table</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Property Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>broker-name</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Name of the broker</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>config</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Location of the XML configuration file</p></td></tr></tbody></table></div><p>You can also use this file to set other properties which will replace placeholders in XML configuration file, as the <code>${data</code>} property is used in this example.</p><p>Default XML configuration file is located in the <code>${KARAF_BASE}/etc/activemq.xml</code> by default.</p><h1 id="OSGiIntegration-WebConsole">Web Console</h1><p>Web Console is installed by default and can be reached at <a shape="rect" class="external-link" href="http://localhost:8181/activemqweb/" rel="nofollow">http://localhost:8181/activemqweb/</a></p><p>The configuration for the console is done in a similar fashion to the broker itself. Configuration is located in <code>${KARAF_BASE}/etc/org.apache.activemq.webconsole.cfg</code> and by default looks like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[webconsole.jms.url=tcp://localhost:61616
+config=${karaf.base}/etc/activemq.xml</plain-text-body></structured-macro><p>Mandatory properties are listed in the following table</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Property Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>broker-name</p></td><td colspan="1" rowspan="1"><p>Name of the broker</p></td></tr><tr><td colspan="1" rowspan="1"><p>config</p></td><td colspan="1" rowspan="1"><p>Location of the XML configuration file</p></td></tr></tbody></table><p>You can also use this file to set other properties which will replace placeholders in XML configuration file, as the <code>${data</code>} property is used in this example.</p><p>Default XML configuration file is located in the <code>${KARAF_BASE}/etc/activemq.xml</code> by default.</p><h1>Web Console</h1><p>Web Console is installed by default and can be reached at <a shape="rect" class="external-link" href="http://localhost:8181/activemqweb/" rel="nofollow">http://localhost:8181/activemqweb/</a></p><p>The configuration for the console is done in a similar fashion to the broker itself. Configuration is located in <code>${KARAF_BASE}/etc/org.apache.activemq.webconsole.cfg</code> and by default looks like</p><structured-macro ac:macro-id="c0edaec0-8367-4b38-a720-6e2fc51bddde" ac:name="code" ac:schema-version="1"><plain-text-body>webconsole.jms.url=tcp://localhost:61616
webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root
webconsole.jmx.user=karaf
-webconsole.jmx.password=karaf]]></script>
-</div></div><p><strong>Optional:</strong> In order to use the ActiveMQ console with a broker configured with authentication, it is necessary to configure the username/password for JMS connection as well.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[webconsole.jms.user=system
+webconsole.jmx.password=karaf</plain-text-body></structured-macro><p><strong>Optional:</strong> In order to use the ActiveMQ console with a broker configured with authentication, it is necessary to configure the username/password for JMS connection as well.</p><structured-macro ac:macro-id="8272db0f-f9c6-4843-91b8-7f405583b721" ac:name="code" ac:schema-version="1"><plain-text-body>webconsole.jms.user=system
webconsole.jms.password=manager
-]]></script>
-</div></div><h1 id="OSGiIntegration-Commands">Commands</h1><p>After these simple steps you have all necessary libraries installed in the container. Also, now you have specific commands on your disposal that you can use to manage your broker:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ browse Display selected messages in a specified destination
+</plain-text-body></structured-macro><h1>Commands</h1><p>After these simple steps you have all necessary libraries installed in the container. Also, now you have specific commands on your disposal that you can use to manage your broker:</p><structured-macro ac:macro-id="5992cc54-3198-43b8-b64e-9ebeb1899ee5" ac:name="code" ac:schema-version="1"><plain-text-body> browse Display selected messages in a specified destination
bstat Displays useful broker statistics
list Lists all available brokers in the specified JMX context
- purge Delete selected destination's messages that matches the message selector
- query Display selected broker component's attributes and statistics
- dstat Performs a predefined query that displays useful tabular statistics regarding the specified destination type ]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-tip"><p class="title">Help on commands</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>To obtain some detailed help on a given command, you can run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[activemq:[command] --help
-]]></script>
-</div></div></div></div><h2 id="OSGiIntegration-Brokerquerying">Broker querying</h2><p>Several commands are available to query the broker. To address local brokers, you need to use the <code>--jmxlocal</code> parameter.</p><p>The following command displays available brokers:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[karaf@root> activemq:list --jmxlocal
+ purge Delete selected destination's messages that matches the message selector
+ query Display selected broker component's attributes and statistics
+ dstat Performs a predefined query that displays useful tabular statistics regarding the specified destination type </plain-text-body></structured-macro><structured-macro ac:macro-id="83559582-5e8d-453f-bf74-c03380d4111c" ac:name="tip" ac:schema-version="1"><parameter ac:name="title">Help on commands</parameter><rich-text-body><p>To obtain some detailed help on a given command, you can run:</p><structured-macro ac:macro-id="806e7673-bc97-4c75-970b-aa7ee2d22dd3" ac:name="code" ac:schema-version="1"><plain-text-body>activemq:[command] --help
+</plain-text-body></structured-macro></rich-text-body></structured-macro><h2>Broker querying</h2><p>Several commands are available to query the broker. To address local brokers, you need to use the <code>--jmxlocal</code> parameter.</p><p>The following command displays available brokers:</p><structured-macro ac:macro-id="7c9b72b3-c17a-4cd4-8032-4bf278fbe3a0" ac:name="code" ac:schema-version="1"><plain-text-body>karaf@root> activemq:list --jmxlocal
BrokerName = mybroker
-]]></script>
-</div></div><p>To have more detailed informations, run:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[karaf@root> activemq:query --jmxlocal
-]]></script>
-</div></div><p>It will display informations about the connectors, list of queues, etc...</p><p>You can also browse or purge queues using the <code>activemq:browse</code> and <code>activemq:purge</code> commands.</p></div>
+</plain-text-body></structured-macro><p>To have more detailed informations, run:</p><structured-macro ac:macro-id="fb27593f-4cd4-4295-86c3-077b90f5bdd4" ac:name="code" ac:schema-version="1"><plain-text-body>karaf@root> activemq:query --jmxlocal
+</plain-text-body></structured-macro><p>It will display informations about the connectors, list of queues, etc...</p><p>You can also browse or purge queues using the <code>activemq:browse</code> and <code>activemq:purge</code> commands.</p></div>
diff --git a/osgi-support-in-development.xml b/osgi-support-in-development.xml
index a661cea..6dea185 100644
--- a/osgi-support-in-development.xml
+++ b/osgi-support-in-development.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="OSGisupport(indevelopment)-Splitpackages(2015-11-17)">Split packages (2015-11-17)</h2><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Package</th><th colspan="1" rowspan="1" class="confluenceTh">Modules</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/uri</td><td colspan="1" rowspan="1" class="confluenceTd"><p>artemis-core-client<br clear="none">artemis-jms-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/protocol/core/impl/wireformat</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client <br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/spi/core/protocol    </td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/protocol/core/impl</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>org/apache/activemq/artemis/core/transaction/impl</p></td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/security</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/protocol</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/buffers/impl</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-commons<br clear="none">artemis-core-client</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/server/management</td><td colspan="1" rowspan="1" class="confluenceTd"><p>artemis-core-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/api/core/management</td><td colspan="1" rowspan="1" class="confluenceTd"><p>artemis-core-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/server</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-commons (1 class)<br clear="none">artemis-core-client (1 class)<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>org/apache/activemq/artemis/spi/core/remoting</p></td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/protocol/core</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/utils</td><td colspan="1" rowspan="1" class="confluenceTd"><p>artemis-commons<br clear="none">artemis-core-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/api/core</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-commons<br clear="none">artemis-core-client</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/remoting/impl/netty</td><td colspan="1" rowspan="1" class="confluenceTd"><p>artemis-core-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/settings</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-core-client<br clear="none">artemis-server</td></tr></tbody></table></div><p> </p><p> </p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Package</th><th colspan="1" rowspan="1" class="confluenceTh">Modules</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/protocol/stomp</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-protocols/artemis-stomp-protocol<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">org/apache/activemq/artemis/core/protocol/hornetq</td><td colspan="1" rowspan="1" class="confluenceTd">artemis-protocols/artemis-hornetq-protocol<br clear="none">artemis-protocols/artemis-hqclient-protocol</td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><h2>Split packages (2015-11-17)</h2><table><tbody><tr><th colspan="1" rowspan="1">Package</th><th colspan="1" rowspan="1">Modules</th></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/uri</td><td colspan="1" rowspan="1"><p>artemis-core-client<br clear="none">artemis-jms-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/protocol/core/impl/wireformat</td><td colspan="1" rowspan="1">artemis-core-client <br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/spi/core/protocol    </td><td colspan="1" rowspan="1">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/protocol/core/impl</td><td colspan="1" rowspan="1">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1"><p>org/apache/activemq/artemis/core/transaction/impl</p></td><td colspan="1" rowspan="1">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/security</td><td colspan="1" rowspan="1">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/protocol</td><td colspan="1" rowspan="1">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/buffers/impl</td><td colspan="1" rowspan="1">artemis-commons<br clear="none">artemis-core-client</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/server/management</td><td colspan="1" rowspan="1"><p>artemis-core-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/api/core/management</td><td colspan="1" rowspan="1"><p>artemis-core-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/server</td><td colspan="1" rowspan="1">artemis-commons (1 class)<br clear="none">artemis-core-client (1 class)<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1"><p>org/apache/activemq/artemis/spi/core/remoting</p></td><td colspan="1" rowspan="1">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/protocol/core</td><td colspan="1" rowspan="1">artemis-core-client<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/utils</td><td colspan="1" rowspan="1"><p>artemis-commons<br clear="none">artemis-core-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/api/core</td><td colspan="1" rowspan="1">artemis-commons<br clear="none">artemis-core-client</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/remoting/impl/netty</td><td colspan="1" rowspan="1"><p>artemis-core-client<br clear="none">artemis-server</p></td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/settings</td><td colspan="1" rowspan="1">artemis-core-client<br clear="none">artemis-server</td></tr></tbody></table><p> </p><p> </p><table><tbody><tr><th colspan="1" rowspan="1">Package</th><th colspan="1" rowspan="1">Modules</th></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/protocol/stomp</td><td colspan="1" rowspan="1">artemis-protocols/artemis-stomp-protocol<br clear="none">artemis-server</td></tr><tr><td colspan="1" rowspan="1">org/apache/activemq/artemis/core/protocol/hornetq</td><td colspan="1" rowspan="1">artemis-protocols/artemis-hornetq-protocol<br clear="none">artemis-protocols/artemis-hqclient-protocol</td></tr></tbody></table></div>
diff --git a/outbound-communication.xml b/outbound-communication.xml
index 41e9179..6325adb 100644
--- a/outbound-communication.xml
+++ b/outbound-communication.xml
@@ -1,16 +1,15 @@
<div class="wiki-content maincontent">
-<h2 id="OutboundCommunication-INLINEConfiguringaSessionBeantosendmessagestoActiveMQ">Configuring a Session Bean to send messages to ActiveMQ</h2>
-<p>In the attached <a shape="rect" href="outbound-communication.data/activemq-jboss-test.zip?version=3&modificationDate=1117021355000&api=v2" data-linked-resource-id="3278" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="activemq-jboss-test.zip" data-nice-type="Zip Archive" data-linked-resource-content-type="application/zip" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">example application</a>, the three MDBs use the <code>SenderEJB</code> to send JMS messages to an ActiveMQ queue. In this example, I will be explaining how to:</p>
+<h2><structured-macro ac:macro-id="3a33b9bc-bf20-4880-8bf3-5bf1c2c71b46" ac:name="excerpt" ac:schema-version="1"><parameter ac:name="atlassian-macro-output-type">INLINE</parameter><rich-text-body><p>Configuring a Session Bean to send messages to ActiveMQ</p></rich-text-body></structured-macro></h2>
+<p>In the attached <link><attachment ri:filename="activemq-jboss-test.zip"><page ri:content-title="JBoss Integration"></page></attachment><link-body>example application</link-body></link>, the three MDBs use the <code>SenderEJB</code> to send JMS messages to an ActiveMQ queue. In this example, I will be explaining how to:</p>
<ol><li>Configure and deploy an ActiveMQ <code>Queue</code> to JBoss</li><li>Configure and deploy an ActiveMQ <code>QueueConnectionFactory</code> to JBoss</li><li>Configure an EJB, deployed to JBoss, to reference the above two.</li></ol>
-<h3 id="OutboundCommunication-TheBean">The Bean</h3>
-<p>In the <a shape="rect" href="outbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3249" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="ejb-jar.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">ejb-jar.xml</a> deployment descriptor, the <code>SenderEJB</code> is declared as follows:<br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-ejbSenderEJB"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ejb-jar.xml – session bean declaration</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h3>The Bean</h3>
+<p>In the <link><attachment ri:filename="ejb-jar.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>ejb-jar.xml</link-body></link> deployment descriptor, the <code>SenderEJB</code> is declared as follows:<br clear="none">
+<structured-macro ac:macro-id="6286c3f3-10c6-4372-adf8-e9ff10eb6708" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">ejbSenderEJB</parameter></structured-macro></p>
+<structured-macro ac:macro-id="8609e156-1e6f-45ea-a91a-f25204627979" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">ejb-jar.xml -- session bean declaration</parameter><plain-text-body>
<session>
...
<ejb-name>SenderEJB</ejb-name>
@@ -29,15 +28,13 @@
<message-destination-link>LoggingQueue</message-destination-link>
</message-destination-ref>
</session>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The <code>jms/MyQueueConnectionFactory</code> is the JNDI name the <code>SenderEJB</code> will use to lookup a <code>javax.jms.QueueConnectionFactory</code>. We will configure it to point to an ActiveMQ <code>QueueConnectionFactory</code>.</p>
-<p>The <code>jms/LogQueue</code> is the JNDI name the <code>SenderEJB</code> will use to lookup the <code>javax.jms.Queue</code> it will send messages to. We use the <code>message-destination-link</code> element to refer to the <code>LoggingQueue</code> which is declared in the <code>assembly-descriptor</code> section of the <a shape="rect" href="outbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3249" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="ejb-jar.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">ejb-jar.xml</a> deployment descriptor as: <br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-ejbLoggingQueue"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ejb-jar.xml – assembly descriptor section</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>The <code>jms/LogQueue</code> is the JNDI name the <code>SenderEJB</code> will use to lookup the <code>javax.jms.Queue</code> it will send messages to. We use the <code>message-destination-link</code> element to refer to the <code>LoggingQueue</code> which is declared in the <code>assembly-descriptor</code> section of the <link><attachment ri:filename="ejb-jar.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>ejb-jar.xml</link-body></link> deployment descriptor as: <br clear="none">
+<structured-macro ac:macro-id="efc34da6-ef9e-4ee3-9aa6-3cbd1be026ae" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">ejbLoggingQueue</parameter></structured-macro></p>
+<structured-macro ac:macro-id="46387c53-07d5-4288-bd88-fb68e51494b9" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">ejb-jar.xml -- assembly descriptor section</parameter><plain-text-body>
<assembly-descriptor>
...
<message-destination>
@@ -45,16 +42,14 @@
</message-destination>
...
</assembly-descriptor>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This is a standard EJB deployment descriptor, nothing special. </p>
-<h3 id="OutboundCommunication-TheConnector">The Connector</h3>
-<p>The <code>resource-ref</code> element <a shape="rect" href="#OutboundCommunication-ejbSenderEJB">shown above</a>, will be linked to the following element in the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml" rel="nofollow">ra.xml</a> file, which is contained within the <a shape="rect" href="jboss-integration.xml#JBossIntegration-rarfile">activemq-ra-1.2.rar</a> file:<br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-raQueueConnectionFactory"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ra.xml – The QueueConnectionFactory</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h3>The Connector</h3>
+<p>The <code>resource-ref</code> element <link ac:anchor="ejbSenderEJB" ac:tooltip="SenderEJB snippet from the ejb-jar.xml file"><link-body>shown above</link-body></link>, will be linked to the following element in the <a shape="rect" href="http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml">ra.xml</a> file, which is contained within the <link ac:anchor="rarfile" ac:tooltip="The ActiveMQ JCA"><page ri:content-title="JBoss Integration"></page><link-body>activemq-ra-1.2.rar</link-body></link> file:<br clear="none">
+<structured-macro ac:macro-id="5409f0be-9202-4bbf-baba-d9923ee9daa9" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">raQueueConnectionFactory</parameter></structured-macro></p>
+<structured-macro ac:macro-id="6c2e648d-24cd-4fa5-8e26-ec2eb2b65ca3" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">ra.xml -- The QueueConnectionFactory</parameter><plain-text-body>
<outbound-resourceadapter>
...
<connection-definition>
@@ -66,13 +61,11 @@
</connection-definition>
...
</outbound-resourceadapter>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>The <code>message-destination</code> element <a shape="rect" href="#OutboundCommunication-ejbLoggingQueue">shown above</a>, will be linked to the following element in the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml" rel="nofollow">ra.xml</a> file:<br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-raQueue"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ra.xml – The Queue</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>The <code>message-destination</code> element <link ac:anchor="ejbLoggingQueue" ac:tooltip="LoggingQueue snippet from the ejb-jar.xml file"><link-body>shown above</link-body></link>, will be linked to the following element in the <a shape="rect" href="http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml">ra.xml</a> file:<br clear="none">
+<structured-macro ac:macro-id="fc2f3d98-3563-4fbe-9f73-8bb775085f39" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">raQueue</parameter></structured-macro></p>
+<structured-macro ac:macro-id="bd6b04f5-9b2d-4a75-8129-9d85553185dc" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">ra.xml -- The Queue</parameter><plain-text-body>
<adminobject>
<adminobject-interface>javax.jms.Queue</adminobject-interface>
<adminobject-class>org.activemq.message.ActiveMQQueue</adminobject-class>
@@ -81,19 +74,17 @@
<config-property-type>java.lang.String</config-property-type>
</config-property>
</adminobject>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="OutboundCommunication-TheGlue">The Glue</h3>
-<p>In JBoss, connecting the resources needed by the <a shape="rect" href="outbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3249" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="ejb-jar.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">ejb-jar.xml</a> file to resources provided by the <a shape="rect" class="external-link" href="http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml" rel="nofollow">ra.xml</a> file involves two additional files:</p>
-<ol><li><strong><a shape="rect" href="outbound-communication.data/panacya-jms-ds.xml?version=5&modificationDate=1117021448000&api=v2" data-linked-resource-id="3271" data-linked-resource-version="5" data-linked-resource-type="attachment" data-linked-resource-default-alias="panacya-jms-ds.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">panacya-jms-ds.xml</a></strong> - This is a JBoss data source file. It specifies which connector objects JBoss should instantiate and where in JNDI JBoss should place those objects.</li><li><strong><a shape="rect" href="outbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3251" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="jboss.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">jboss.xml</a></strong> - This is a JBoss deployment descriptor which is contained within the <a shape="rect" href="jboss-integration.xml#JBossIntegration-ejbjarfile">panacya-mdb-test-1.0.jar</a> file. It links resources needed by the EJBs to the JNDI names of resources available in JBoss.</li></ol>
+<h3>The Glue</h3>
+<p>In JBoss, connecting the resources needed by the <link><attachment ri:filename="ejb-jar.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>ejb-jar.xml</link-body></link> file to resources provided by the <a shape="rect" href="http://activemq.codehaus.org/checkout/activemq/modules/ra/src/rar/META-INF/ra.xml">ra.xml</a> file involves two additional files:</p>
+<ol><li><strong><link><attachment ri:filename="panacya-jms-ds.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>panacya-jms-ds.xml</link-body></link></strong> - This is a JBoss data source file. It specifies which connector objects JBoss should instantiate and where in JNDI JBoss should place those objects.</li><li><strong><link><attachment ri:filename="jboss.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>jboss.xml</link-body></link></strong> - This is a JBoss deployment descriptor which is contained within the <link ac:anchor="ejbjarfile" ac:tooltip="The standalone ejb module"><page ri:content-title="JBoss Integration"></page><link-body>panacya-mdb-test-1.0.jar</link-body></link> file. It links resources needed by the EJBs to the JNDI names of resources available in JBoss.</li></ol>
-<h5 id="OutboundCommunication-panacya-jms-ds.xml–TheJBossDataSourceFile"><a shape="rect" href="outbound-communication.data/panacya-jms-ds.xml?version=5&modificationDate=1117021448000&api=v2" data-linked-resource-id="3271" data-linked-resource-version="5" data-linked-resource-type="attachment" data-linked-resource-default-alias="panacya-jms-ds.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">panacya-jms-ds.xml</a> – <em>The JBoss Data Source File</em></h5>
-<p>This first snippet configures the <code>QueueConnectionFactory</code>, <a shape="rect" href="#OutboundCommunication-raQueueConnectionFactory">declared above</a>, and places it in JNDI at <code>activemq/QueueConnectionFactory</code>:<br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-dsQueueConnectionFactory"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>panacya-jms-ds.xml – The QueueConnectionFactory</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h5><link><attachment ri:filename="panacya-jms-ds.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>panacya-jms-ds.xml</link-body></link> – <em>The JBoss Data Source File</em></h5>
+<p>This first snippet configures the <code>QueueConnectionFactory</code>, <link ac:anchor="raQueueConnectionFactory" ac:tooltip="QueueConnectionFactory snippet from the ra.xml file"><link-body>declared above</link-body></link>, and places it in JNDI at <code>activemq/QueueConnectionFactory</code>:<br clear="none">
+<structured-macro ac:macro-id="87a71a3f-a15e-41c0-b4a3-dd676a71cbab" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">dsQueueConnectionFactory</parameter></structured-macro></p>
+<structured-macro ac:macro-id="fdd69607-0a13-4e05-9c68-6e4d70d1c66c" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">panacya-jms-ds.xml -- The QueueConnectionFactory</parameter><plain-text-body>
<tx-connection-factory>
<jndi-name>activemq/QueueConnectionFactory</jndi-name>
<xa-transaction/>
@@ -101,31 +92,27 @@
<connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
<security-domain-and-application>JmsXARealm</security-domain-and-application>
</tx-connection-factory>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>This second snippet configures the <code>Queue</code>, <a shape="rect" href="#OutboundCommunication-raQueue">declared above</a>, and places it in JNDI at <code>activemq/queue/outbound</code>:<br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-dsQueue"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>panacya-jms-ds.xml – The Queue</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
- <attribute name="JNDIName">activemq/queue/outbound</attribute>
- <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra-1.2-SNAPSHOT.rar'</depends>
- <attribute name="Type">javax.jms.Queue</attribute>
- <attribute name="Properties">
+<p>This second snippet configures the <code>Queue</code>, <link ac:anchor="raQueue" ac:tooltip="Queue snippet from the ra.xml file"><link-body>declared above</link-body></link>, and places it in JNDI at <code>activemq/queue/outbound</code>:<br clear="none">
+<structured-macro ac:macro-id="cb602599-8c3b-4e04-bafa-a334d512979e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">dsQueue</parameter></structured-macro></p>
+<structured-macro ac:macro-id="6fa55612-7e41-4c0c-93b1-9ad345726635" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">panacya-jms-ds.xml -- The Queue</parameter><plain-text-body>
+<mbean code="org.jboss.resource.deployment.AdminObject" name="activemq.queue:name=outboundQueue">
+ <attribute name="JNDIName">activemq/queue/outbound</attribute>
+ <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='activemq-ra-1.2-SNAPSHOT.rar'</depends>
+ <attribute name="Type">javax.jms.Queue</attribute>
+ <attribute name="Properties">
PhysicalName=queue.outbound
</attribute>
</mbean>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>In the <a shape="rect" href="outbound-communication.data/panacya-jms-ds.xml?version=5&modificationDate=1117021448000&api=v2" data-linked-resource-id="3271" data-linked-resource-version="5" data-linked-resource-type="attachment" data-linked-resource-default-alias="panacya-jms-ds.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">panacya-jms-ds.xml</a> file section shown above, the value of the <code>Properties</code> element is set to <code>PhysicalName=queue.outbound</code>. This value is the physical name of the ActiveMQ destination the <code>SenderEJB</code> will be sending messages to and not a JNDI name. In other words, the value of the <code>PhysicalName</code> property has no meaning to JBoss. It is purely an ActiveMQ setting. </p>
+<p>In the <link><attachment ri:filename="panacya-jms-ds.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>panacya-jms-ds.xml</link-body></link> file section shown above, the value of the <code>Properties</code> element is set to <code>PhysicalName=queue.outbound</code>. This value is the physical name of the ActiveMQ destination the <code>SenderEJB</code> will be sending messages to and not a JNDI name. In other words, the value of the <code>PhysicalName</code> property has no meaning to JBoss. It is purely an ActiveMQ setting. </p>
-<h5 id="OutboundCommunication-jboss.xml–TheJBossDeploymentDescriptor"><a shape="rect" href="outbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3251" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="jboss.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">jboss.xml</a> – <em>The JBoss Deployment Descriptor</em></h5>
-<p>This first snippet links the <code><a shape="rect" href="#OutboundCommunication-ejbSenderEJB">jms/MyQueueConnectionFactory</a></code> JNDI name used by the <code>SenderEJB</code> to the resource name <code>queuefactoryref</code> which is local to the <a shape="rect" href="outbound-communication.data/jboss.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3251" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="jboss.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">jboss.xml</a> file: <br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-jbossQueuefactoryref"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>jboss.xml – The QueueConnectionFactory for the SenderEJB</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<h5><link><attachment ri:filename="jboss.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>jboss.xml</link-body></link> – <em>The JBoss Deployment Descriptor</em></h5>
+<p>This first snippet links the <code><link ac:anchor="ejbSenderEJB" ac:tooltip="SenderEJB snippet from the ejb-jar.xml file"><link-body>jms/MyQueueConnectionFactory</link-body></link></code> JNDI name used by the <code>SenderEJB</code> to the resource name <code>queuefactoryref</code> which is local to the <link><attachment ri:filename="jboss.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>jboss.xml</link-body></link> file: <br clear="none">
+<structured-macro ac:macro-id="c59f1670-7b5b-4d78-b7b8-b8a362108c0d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jbossQueuefactoryref</parameter></structured-macro></p>
+<structured-macro ac:macro-id="82a93989-89ad-4c6a-8345-50948b89d7b4" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">jboss.xml -- The QueueConnectionFactory for the SenderEJB</parameter><plain-text-body>
<enterprise-beans>
<session>
<ejb-name>SenderEJB</ejb-name>
@@ -136,13 +123,11 @@
</session>
...
</enterprise-beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>This second snippet links the local <code>queuefactoryref</code> name to the global JNDI name <code>java:/activemq/QueueConnectionFactory</code> which was <a shape="rect" href="#OutboundCommunication-dsQueueConnectionFactory">declared above</a>: <br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-jbossQueueConnectionFactory"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>jboss.xml – Linking queuefactoryref to the global JNDI namespace</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>This second snippet links the local <code>queuefactoryref</code> name to the global JNDI name <code>java:/activemq/QueueConnectionFactory</code> which was <link ac:anchor="dsQueueConnectionFactory" ac:tooltip="QueueConnectionFactory snippet from the panacya-jms-ds.xml file"><link-body>declared above</link-body></link>: <br clear="none">
+<structured-macro ac:macro-id="3c777a05-e82d-4669-8804-056b11f5ba25" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jbossQueueConnectionFactory</parameter></structured-macro></p>
+<structured-macro ac:macro-id="25909147-bec4-46d0-a03a-dda5f2ccb828" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">jboss.xml -- Linking queuefactoryref to the global JNDI namespace</parameter><plain-text-body>
<resource-managers>
<resource-manager>
<res-name>queuefactoryref</res-name>
@@ -150,23 +135,20 @@
</resource-manager>
...
</resource-managers>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>This third snippet links the <code>LoggingQueue</code>, which was <a shape="rect" href="#OutboundCommunication-ejbLoggingQueue">declared</a> in the <code>assembly-descriptor</code> section of the <a shape="rect" href="outbound-communication.data/ejb-jar.xml?version=3&modificationDate=1117021488000&api=v2" data-linked-resource-id="3249" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="ejb-jar.xml" data-nice-type="XML File" data-linked-resource-content-type="text/xml" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">ejb-jar.xml</a>, to the global JNDI name <code>activemq/queue/outbound</code> which was <a shape="rect" href="#OutboundCommunication-dsQueue">declared above</a>: <br clear="none">
-<span class="confluence-anchor-link" id="OutboundCommunication-jbossQueue"></span></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>jboss.xml – Linking LoggingQueue to the global JNDI namespace</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<p>This third snippet links the <code>LoggingQueue</code>, which was <link ac:anchor="ejbLoggingQueue" ac:tooltip="LoggingQueue snippet from the ejb-jar.xml file"><link-body>declared</link-body></link> in the <code>assembly-descriptor</code> section of the <link><attachment ri:filename="ejb-jar.xml"><page ri:content-title="JBoss Integration"></page></attachment><link-body>ejb-jar.xml</link-body></link>, to the global JNDI name <code>activemq/queue/outbound</code> which was <link ac:anchor="dsQueue" ac:tooltip="Queue snippet from the panacya-jms-ds.xml file"><link-body>declared above</link-body></link>: <br clear="none">
+<structured-macro ac:macro-id="2831eeb9-d124-4718-9caa-a1eb11f8a233" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jbossQueue</parameter></structured-macro></p>
+<structured-macro ac:macro-id="eab4bd66-e286-4a07-a4ac-79c62efdf353" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><parameter ac:name="title">jboss.xml -- Linking LoggingQueue to the global JNDI namespace</parameter><plain-text-body>
<assembly-descriptor>
<message-destination>
<message-destination-name>LoggingQueue</message-destination-name>
<jndi-name>activemq/queue/outbound</jndi-name>
</message-destination>
</assembly-descriptor>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The above example highlights the key configuration settings needed to enable EJBs deployed in JBoss to send JMS messages to an ActiveMQ destination. </p>
-<p>You can try the above example, plus a few more, by downloading the <a shape="rect" href="outbound-communication.data/activemq-jboss-test.zip?version=3&modificationDate=1117021355000&api=v2" data-linked-resource-id="3278" data-linked-resource-version="3" data-linked-resource-type="attachment" data-linked-resource-default-alias="activemq-jboss-test.zip" data-nice-type="Zip Archive" data-linked-resource-content-type="application/zip" data-linked-resource-container-id="35943" data-linked-resource-container-version="53">activemq-jboss-test.zip</a> file which contains the complete sample project.</p></div>
+<p>You can try the above example, plus a few more, by downloading the <link><attachment ri:filename="activemq-jboss-test.zip"><page ri:content-title="JBoss Integration"></page></attachment><link-body>activemq-jboss-test.zip</link-body></link> file which contains the complete sample project.</p></div>
diff --git a/overview.xml b/overview.xml
index b221e86..9f78483 100644
--- a/overview.xml
+++ b/overview.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="download.xml">Download</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-11-release.xml">ActiveMQ 1.1 Release</a></li><li><a shape="rect" href="activemq-12-release.xml">ActiveMQ 1.2 Release</a></li><li><a shape="rect" href="activemq-13-release.xml">ActiveMQ 1.3 Release</a></li><li><a shape="rect" href="activemq-14-release.xml">ActiveMQ 1.4 Release</a></li><li><a shape="rect" href="activemq-15-release.xml">ActiveMQ 1.5 Release</a></li><li><a shape="rect" href="activemq-20-release.xml">ActiveMQ 2.0 Release</a></li><li><a shape="rect" href="activemq-21-release.xml">ActiveMQ 2.1 Release</a></li><li><a shape="rect" href="activemq-30-release.xml">ActiveMQ 3.0 Release</a></li><li><a shape="rect" href="activemq-31-release.xml">ActiveMQ 3.1 Release</a></li><li><a shape="rect" href="activemq-321-release.xml">ActiveMQ 3.2.1 Release</a></li><li><a shape="rect" href="activemq-322-release.xml">ActiveMQ 3.2.2 Release</a></li><li><a shape="rect" href="activemq-32-release.xml">ActiveMQ 3.2 Release</a></li><li><a shape="rect" href="activemq-401-release.xml">ActiveMQ 4.0.1 Release</a></li><li><a shape="rect" href="activemq-402-release.xml">ActiveMQ 4.0.2 Release</a></li><li><a shape="rect" href="activemq-40-m4-release.xml">ActiveMQ 4.0 M4 Release</a></li><li><a shape="rect" href="activemq-40-rc2-release.xml">ActiveMQ 4.0 RC2 Release</a></li><li><a shape="rect" href="activemq-40-release.xml">ActiveMQ 4.0 Release</a></li><li><a shape="rect" href="activemq-410-release.xml">ActiveMQ 4.1.0 Release</a></li><li><a shape="rect" href="activemq-411-release.xml">ActiveMQ 4.1.1 Release</a></li><li><a shape="rect" href="activemq-412-release.xml">ActiveMQ 4.1.2 Release</a></li><li><a shape="rect" href="activemq-500-release.xml">ActiveMQ 5.0.0 Release</a></li><li><a shape="rect" href="activemq-510-release.xml">ActiveMQ 5.1.0 Release</a></li><li><a shape="rect" href="activemq-520-release.xml">ActiveMQ 5.2.0 Release</a></li><li><a shape="rect" href="activemq-530-release.xml">ActiveMQ 5.3.0 Release</a></li><li><a shape="rect" href="activemq-531-release.xml">ActiveMQ 5.3.1 Release</a></li><li><a shape="rect" href="activemq-532-release.xml">ActiveMQ 5.3.2 Release</a></li><li><a shape="rect" href="activemq-540-release.xml">ActiveMQ 5.4.0 Release</a></li><li><a shape="rect" href="activemq-541-release.xml">ActiveMQ 5.4.1 Release</a></li><li><a shape="rect" href="activemq-542-release.xml">ActiveMQ 5.4.2 Release</a></li><li><a shape="rect" href="activemq-543-release.xml">ActiveMQ 5.4.3 Release</a></li><li><a shape="rect" href="activemq-550-release.xml">ActiveMQ 5.5.0 Release</a></li><li><a shape="rect" href="activemq-551-release.xml">ActiveMQ 5.5.1 Release</a></li><li><a shape="rect" href="activemq-560-release.xml">ActiveMQ 5.6.0 Release</a></li><li><a shape="rect" href="activemq-570-release.xml">ActiveMQ 5.7.0 Release</a></li><li><a shape="rect" href="activemq-580-release.xml">ActiveMQ 5.8.0 Release</a><ul class="childpages-macro"><li><a shape="rect" href="58-migration-guide.xml">5.8 Migration Guide</a></li></ul></li><li><a shape="rect" href="activemq-590-release.xml">ActiveMQ 5.9.0 Release</a><ul class="childpages-macro"><li><a shape="rect" href="59-migration-guide.xml">5.9 Migration Guide</a></li></ul></li><li><a shape="rect" href="activemq-591-release.xml">ActiveMQ 5.9.1 Release</a></li><li><a shape="rect" href="activemq-5100-release.xml">ActiveMQ 5.10.0 Release</a></li><li><a shape="rect" href="activemq-5101-release.xml">ActiveMQ 5.10.1 Release</a></li><li><a shape="rect" href="activemq-5102-release.xml">ActiveMQ 5.10.2 Release</a></li><li><a shape="rect" href="activemq-5110-release.xml">ActiveMQ 5.11.0 Release</a></li><li><a shape="rect" href="activemq-5111-release.xml">ActiveMQ 5.11.1 Release</a></li><li><a shape="rect" href="activemq-5112-release.xml">ActiveMQ 5.11.2 Release</a></li><li><a shape="rect" href="activemq-5113-release.xml">ActiveMQ 5.11.3 Release</a></li><li><a shape="rect" href="activemq-5120-release.xml">ActiveMQ 5.12.0 Release</a></li><li><a shape="rect" href="activemq-5121-release.xml">ActiveMQ 5.12.1 Release</a></li><li><a shape="rect" href="activemq-5122-release.xml">ActiveMQ 5.12.2 Release</a></li><li><a shape="rect" href="activemq-5130-release.xml">ActiveMQ 5.13.0 Release</a></li><li><a shape="rect" href="activemq-5131-release.xml">ActiveMQ 5.13.1 Release</a></li><li><a shape="rect" href="activemq-5132-release.xml">ActiveMQ 5.13.2 Release</a></li><li><a shape="rect" href="activemq-5133-release.xml">ActiveMQ 5.13.3 Release</a></li><li><a shape="rect" href="activemq-5134-release.xml">ActiveMQ 5.13.4 Release</a></li><li><a shape="rect" href="activemq-5140-release.xml">ActiveMQ 5.14.0 Release</a></li><li><a shape="rect" href="activemq-5141-release.xml">ActiveMQ 5.14.1 Release</a></li><li><a shape="rect" href="activemq-5142-release.xml">ActiveMQ 5.14.2 Release</a></li><li><a shape="rect" href="activemq-5143-release.xml">ActiveMQ 5.14.3 Release</a></li><li><a shape="rect" href="activemq-5144-release.xml">ActiveMQ 5.14.4 Release</a></li><li><a shape="rect" href="activemq-5145-release.xml">ActiveMQ 5.14.5 Release</a></li><li><a shape="rect" href="activemq-5150-release.xml">ActiveMQ 5.15.0 Release</a></li><li><a shape="rect" href="activemq-5151-release.xml">ActiveMQ 5.15.1 Release</a></li><li><a shape="rect" href="activemq-5152-release.xml">ActiveMQ 5.15.2 Release</a></li><li><a shape="rect" href="in-progress.xml">In Progress</a></li></ul></li><li><a shape="rect" href="download-archives.xml">Download Archives</a></li><li><a shape="rect" href="javadocs.xml">JavaDocs</a></li><li><a shape="rect" href="news.xml">News</a></li></ul> </div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="29f43a49-84d0-4dd5-b108-5c922aba7f34" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro> </div>
diff --git a/peer-transport-reference.xml b/peer-transport-reference.xml
index f9cc1ba..0abfc1b 100644
--- a/peer-transport-reference.xml
+++ b/peer-transport-reference.xml
@@ -1,17 +1,16 @@
-<div class="wiki-content maincontent"><h3 id="PeerTransportReference-ThePeerTransport">The Peer Transport</h3>
+<div class="wiki-content maincontent"><h3>The Peer Transport</h3>
<p>The Peer transport provides a peer-to-peer network with ActiveMQ. What actually happens is the peer transport uses the VM transport to create and connect to a local embedded broker but which configures the embedded broker to establish network connections to other peer embedded brokers.</p>
-<h4 id="PeerTransportReference-ConfigurationSyntax">Configuration Syntax</h4>
+<h4>Configuration Syntax</h4>
<p><strong>peer://peer-group/brokerName?brokerOptions</strong></p>
-<h5 id="PeerTransportReference-ExampleURI">Example URI</h5>
+<h5>Example URI</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>peer://groupa/broker1?persistent=false
-</pre>
-</div></div>
+<structured-macro ac:macro-id="d4973bd1-7ca2-4098-b501-53fca5f603df" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+peer://groupa/broker1?persistent=false
+</plain-text-body></structured-macro>
<p> </p>
<p> </p></div>
diff --git a/per-destination-policies.xml b/per-destination-policies.xml
index f974c25..5559405 100644
--- a/per-destination-policies.xml
+++ b/per-destination-policies.xml
@@ -1,20 +1,19 @@
-<div class="wiki-content maincontent"><p>Multiple different policies can be applied per destination (queue or topic), or using wildcard notation to apply to a hierarchy of queues or topics, making it possible, therefore, to configure how different regions of the JMS destination space are handled.</p><p>The following properties can be applied to either topics and/or queues:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Common Property</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForConsumed</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Send an advisory message when a message is consumed by a client.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForDelivery</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Send an advisory message when a message is sent to a client.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForFastProducers</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Send an advisory message if a producer is deemed fast.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForSlowConsumers</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Send an advisory message if a consumer is deemed slow.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryWhenFull</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Send an advisory message when a limit (memory, store, temp disk) is full.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>enableAudit</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong> the broker will track duplicate messages. Duplicates can happen for non-persistent messages during failover.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>gcInactiveDestinations</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Garbage collect inactive destinations.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>inactiveTimoutBeforeGC</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The timeout (in ms) after which a destination is considered inactive.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>includeBodyForAdvisory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Includes the body of the original message that triggered the advisory as part of the <strong><code>dataStructure</code></strong> field in the advisory message (where applicable). Normally the message body is cleared.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxBrowsePageSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>400</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of messages to page in from the store at one time for a browser.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxDestinations</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(v5.12) If <strong><code>>= 0</code></strong>, sets the maximum number of destinations that can be created. This parameter is intended to limit the number of hierarchical destinations that can be created under a wildcard destination.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxPageSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>200</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of messages to page in from the store at one time. Increase this value to improve performance for queue destination's that contain grouped messages that are consumed by multiple concurrent consumers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>memoryLimit</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>n/a</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The memory limit (in bytes) of the destination's cursor.</p><p>This memory limit is subordinate to the system level memory limit, as specified by the <a shape="rect" href="producer-flow-control.xml#ProducerFlowControl-Systemusage"><code><systemUsage>/<memoryUsage></code></a> <span class="confluence-link">attribute</span>. There is no default for this value; it simply acts as a child to the overall broker memory until the broker memory is exhausted.</p><p><strong>Note</strong>: when this limit is specified the destination's <strong><code>cursorMemoryHighWaterMark</code></strong> will be applied against it and not the <strong><code><systemUsage>/><memoryUsage></code></strong> memory limit.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>minimumMessageSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1024</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For non-serialized messages (embedded broker) - the assumed size of the message used for memory usage calculation. Serialized messages use the serialized size as the basis for the memory calculation.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>prioritizedMessages</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Persist message priority information.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>producerFlowControl</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> the broker will throttle (flow-control) the producer. Throttling is achieved either by withholding the producer's ACK or by raising a <strong><code>javax.jms.ResourceAllocationException</code></strong> (that's propagated back to the client) when local resources, e.g., memory and/or storage, have been exhausted.</p><p>If <strong><code>false</code></strong> excess messages will be written to the message store to prevent memory exhaustion. However, when the message store reaches capacity the producer will be throttled until resources are freed.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>slowConsumerStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>null</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the strategy for handling slow consumers. See <a shape="rect" class="external-link" href="https://github.com/apache/activemq/blob/master/activemq-broker/src/main/java/org/apache/activemq/broker/region/policy/AbortSlowConsumerStrategy.java" rel="nofollow">AbortSlowConsumerStrategy.</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>storeUsageHighWaterMark</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>100</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The percentage (%) threshold of the <strong><code><systemUsage>/<storeUsage></code></strong> store limit which when exceeded causes a producer send to block.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useCache</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> persistent messages are cached for fast retrieval from store.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span><code>usePrefetchExtension</code><br clear="none"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The prefetch extension is used when a message is delivered but not ACK'ed, such that the broker can dispatch another message, e.g., <strong><code>prefetch == 0</code></strong>, the idea being that there will always be prefetch number of messages pending. It also allows a transaction batch to exceed the prefetch value.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code><span style="color: rgb(0,0,0);">sendFailIfNoSpace </span></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code><span style="color: rgb(0,0,0);">false</span></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);">(v5.16.0) If <strong><code>true</code></strong>, will cause a send to fail with a <strong><code>javax.jms.ResourceAllocationException</code></strong> when the destination has reached is resource limits (memory or storage)</span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code><span style="color: rgb(0,0,0);">sendFailIfNoSpaceAfterTimeout</span></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);">(v5.16.0) If <strong><code>> 0</code></strong>, will cause a send to fail with a <span style="color: rgb(0,0,0);"><strong><code>javax.jms.ResourceAllocationException</code></strong></span> when the destination resource limits (memory or storage) remain exhausted for the configured duration in milliseconds</span></p></td></tr></tbody></table></div><p>The following properties can be applied <em>only</em> to a queue:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Queue Only Property</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>allConsumersExclusiveByDefault</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong> all consumers will be exclusive. See <a shape="rect" href="nms/activemq-exclusive-consumers.xml">ActiveMQ Exclusive Consumers</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cursorMemoryHighWaterMark</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>70</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The percentage (%) threshold applied either to the <strong><code><systemUsage>/<memoryUsage></code></strong> or the destination's <strong><code>memoryLimit</code></strong> (when defined) which when exceeded will cause the destination's cursor to either block or write to disk.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>consumersBeforeDispatchStarts</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When the first consumer connects, wait for specified number of consumers before message dispatching starts.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>expireMessagesPeriod</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The period (in ms) of checks for message expiry on queued messages.</p><p>A value of <strong><code>0</code></strong> will disable expiration checking.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>lazyDispatch</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Only page in from store the number of messages that can be dispatched at time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxExpirePageSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>400</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of messages to page in when periodically expiring messages.</p><p>Messages are paged in according to this setting if the number of messages in memory pending dispatch is less than this value, and there are messages in the store to page in. Messages are expired during this paging step as they are brought into memory from the store.</p><p>Once the paging process is completed, messages are expired from the list of those that are in memory and pending dispatch, then from the list of those that are in memory but not yet targeted at a subscription.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>optimizedDispatch</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Don't use a separate thread for dispatching from a Queue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>persistJMSRedelivered</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(v 5.10) If true, before a persistent message is dispatched by the broker for the first time, the message is rewritten to reflect the possible delivery.</p><p>This ensures the message <strong><code>JMSRedelivered</code></strong> header is a reliable indication of possible duplicate delivery.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>queuePrefetch</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>n/a</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the prefetch for consumers that are using the default value.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>strictOrderDispatch</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> queue will not round robin consumers, but it'll use a single one until its prefetch buffer is full.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>timeBeforeDispatchStarts</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When the first consumer connects, wait for specified time (in ms) before message dispatching starts.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useConsumerPriority</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Use the priority of a consumer when dispatching messages from a Queue.</p></td></tr></tbody></table></div><p>The following properties can be applied <em>only</em> to a topic:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Topic Only Property</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>advisoryForDiscardingMessages</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Send an advisory when a message is discarded from a non durable subscription.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>cursorMemoryHighWaterMark</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>70</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The percentage (%) threshold applied to the <strong><code><systemUsage>/<memoryUsage></code></strong> which when exceeded will cause the destination's cursor to either block or write to disk.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);"><code>alwaysRetroactive</code><br clear="none"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Makes all subscribers retroactive negating the need to modify the clients to enable this feature.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>durableTopicPrefetch</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>n/a</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the prefetch for durable topic consumers that are using the default value.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span style="color: rgb(0,0,0);"><code>expireMessagesPeriod</code><br clear="none"></span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The interval (in ms) between message expiration checks on inactive durable subscribers.</p><p><strong>Note</strong>: set to <strong><code>0</code></strong> to disable message expiration checking.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>topicPrefetch</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>n/a</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the prefetch for topic consumers that are using the default value.</p></td></tr></tbody></table></div><p><span style="line-height: 1.4285715;">The following are examples of different policies that can be customized on a per destination basis:</span></p><ul><li><a shape="rect" href="dispatch-policies.xml">Dispatch Policies</a></li></ul><p>An example from the demos <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=assembly/src/release/examples/conf/activemq-demo.xml;hb=HEAD">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=assembly/src/release/examples/conf/activemq-demo.xml;hb=HEAD</a>: </p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
+<div class="wiki-content maincontent"><p>Multiple different policies can be applied per destination (queue or topic), or using wildcard notation to apply to a hierarchy of queues or topics, making it possible, therefore, to configure how different regions of the JMS destination space are handled.</p><p>The following properties can be applied to either topics and/or queues:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Common Property</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>advisoryForConsumed</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Send an advisory message when a message is consumed by a client.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>advisoryForDelivery</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Send an advisory message when a message is sent to a client.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>advisoryForFastProducers</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Send an advisory message if a producer is deemed fast.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>advisoryForSlowConsumers</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Send an advisory message if a consumer is deemed slow.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>advisoryWhenFull</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Send an advisory message when a limit (memory, store, temp disk) is full.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>enableAudit</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code></strong> the broker will track duplicate messages. Duplicates can happen for non-persistent messages during failover.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>gcInactiveDestinations</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Garbage collect inactive destinations.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>inactiveTimoutBeforeGC</code></p></td><td colspan="1" rowspan="1"><p><code>5000</code></p></td><td colspan="1" rowspan="1"><p>The timeout (in ms) after which a destination is considered inactive.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>includeBodyForAdvisory</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Includes the body of the original message that triggered the advisory as part of the <strong><code>dataStructure</code></strong> field in the advisory message (where applicable). Normally the message body is cleared.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxBrowsePageSize</code></p></td><td colspan="1" rowspan="1"><p><code>400</code></p></td><td colspan="1" rowspan="1"><p>The maximum number of messages to page in from the store at one time for a browser.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxDestinations</code></p></td><td colspan="1" rowspan="1"><p><code>-1</code></p></td><td colspan="1" rowspan="1"><p>(v5.12) If <strong><code>>= 0</code></strong>, sets the maximum number of destinations that can be created. This parameter is intended to limit the number of hierarchical destinations that can be created under a wildcard destination.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxPageSize</code></p></td><td colspan="1" rowspan="1"><p><code>200</code></p></td><td colspan="1" rowspan="1"><p>The maximum number of messages to page in from the store at one time. Increase this value to improve performance for queue destination's that contain grouped messages that are consumed by multiple concurrent consumers.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>memoryLimit</code></p></td><td colspan="1" rowspan="1"><p><code>n/a</code></p></td><td colspan="1" rowspan="1"><p>The memory limit (in bytes) of the destination's cursor.</p><p>This memory limit is subordinate to the system level memory limit, as specified by the <link ac:anchor="System usage"><page ri:content-title="Producer Flow Control"></page><link-body><code><systemUsage>/<memoryUsage></code></link-body></link> <span class="confluence-link">attribute</span>. There is no default for this value; it simply acts as a child to the overall broker memory until the broker memory is exhausted.</p><p><strong>Note</strong>: when this limit is specified the destination's <strong><code>cursorMemoryHighWaterMark</code></strong> will be applied against it and not the <strong><code><systemUsage>/><memoryUsage></code></strong> memory limit.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>minimumMessageSize</code></p></td><td colspan="1" rowspan="1"><p><code>1024</code></p></td><td colspan="1" rowspan="1"><p>For non-serialized messages (embedded broker) - the assumed size of the message used for memory usage calculation. Serialized messages use the serialized size as the basis for the memory calculation.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>prioritizedMessages</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Persist message priority information.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>producerFlowControl</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> the broker will throttle (flow-control) the producer. Throttling is achieved either by withholding the producer's ACK or by raising a <strong><code>javax.jms.ResourceAllocationException</code></strong> (that's propagated back to the client) when local resources, e.g., memory and/or storage, have been exhausted.</p><p>If <strong><code>false</code></strong> excess messages will be written to the message store to prevent memory exhaustion. However, when the message store reaches capacity the producer will be throttled until resources are freed.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>slowConsumerStrategy</code></p></td><td colspan="1" rowspan="1"><p><code>null</code></p></td><td colspan="1" rowspan="1"><p>Sets the strategy for handling slow consumers. See <a shape="rect" href="https://github.com/apache/activemq/blob/master/activemq-broker/src/main/java/org/apache/activemq/broker/region/policy/AbortSlowConsumerStrategy.java">AbortSlowConsumerStrategy.</a></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>storeUsageHighWaterMark</code></p></td><td colspan="1" rowspan="1"><p><code>100</code></p></td><td colspan="1" rowspan="1"><p>The percentage (%) threshold of the <strong><code><systemUsage>/<storeUsage></code></strong> store limit which when exceeded causes a producer send to block.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useCache</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> persistent messages are cached for fast retrieval from store.</p></td></tr><tr><td colspan="1" rowspan="1"><p><span><code>usePrefetchExtension</code><br clear="none"></span></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>The prefetch extension is used when a message is delivered but not ACK'ed, such that the broker can dispatch another message, e.g., <strong><code>prefetch == 0</code></strong>, the idea being that there will always be prefetch number of messages pending. It also allows a transaction batch to exceed the prefetch value.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code><span style="color: rgb(0,0,0);">sendFailIfNoSpace </span></code></p></td><td colspan="1" rowspan="1"><p><code><span style="color: rgb(0,0,0);">false</span></code></p></td><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);">(v5.16.0) If <strong><code>true</code></strong>, will cause a send to fail with a <strong><code>javax.jms.ResourceAllocationException</code></strong> when the destination has reached is resource limits (memory or storage)</span></p></td></tr><tr><td colspan="1" rowspan="1"><p><code><span style="color: rgb(0,0,0);">sendFailIfNoSpaceAfterTimeout</span></code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);">(v5.16.0) If <strong><code>> 0</code></strong>, will cause a send to fail with a <span style="color: rgb(0,0,0);"><strong><code>javax.jms.ResourceAllocationException</code></strong></span> when the destination resource limits (memory or storage) remain exhausted for the configured duration in milliseconds</span></p></td></tr></tbody></table><p>The following properties can be applied <em>only</em> to a queue:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Queue Only Property</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>allConsumersExclusiveByDefault</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code></strong> all consumers will be exclusive. See <link><page ri:content-title="ActiveMQ Exclusive Consumers" ri:space-key="NMS"></page></link></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>cursorMemoryHighWaterMark</code></p></td><td colspan="1" rowspan="1"><p><code>70</code></p></td><td colspan="1" rowspan="1"><p>The percentage (%) threshold applied either to the <strong><code><systemUsage>/<memoryUsage></code></strong> or the destination's <strong><code>memoryLimit</code></strong> (when defined) which when exceeded will cause the destination's cursor to either block or write to disk.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>consumersBeforeDispatchStarts</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>When the first consumer connects, wait for specified number of consumers before message dispatching starts.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>expireMessagesPeriod</code></p></td><td colspan="1" rowspan="1"><p><code>30000</code></p></td><td colspan="1" rowspan="1"><p>The period (in ms) of checks for message expiry on queued messages.</p><p>A value of <strong><code>0</code></strong> will disable expiration checking.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>lazyDispatch</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Only page in from store the number of messages that can be dispatched at time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxExpirePageSize</code></p></td><td colspan="1" rowspan="1"><p><code>400</code></p></td><td colspan="1" rowspan="1"><p>The maximum number of messages to page in when periodically expiring messages.</p><p>Messages are paged in according to this setting if the number of messages in memory pending dispatch is less than this value, and there are messages in the store to page in. Messages are expired during this paging step as they are brought into memory from the store.</p><p>Once the paging process is completed, messages are expired from the list of those that are in memory and pending dispatch, then from the list of those that are in memory but not yet targeted at a subscription.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>optimizedDispatch</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Don't use a separate thread for dispatching from a Queue.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>persistJMSRedelivered</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>(v 5.10) If true, before a persistent message is dispatched by the broker for the first time, the message is rewritten to reflect the possible delivery.</p><p>This ensures the message <strong><code>JMSRedelivered</code></strong> header is a reliable indication of possible duplicate delivery.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>queuePrefetch</code></p></td><td colspan="1" rowspan="1"><p><code>n/a</code></p></td><td colspan="1" rowspan="1"><p>Sets the prefetch for consumers that are using the default value.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>strictOrderDispatch</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> queue will not round robin consumers, but it'll use a single one until its prefetch buffer is full.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>timeBeforeDispatchStarts</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>When the first consumer connects, wait for specified time (in ms) before message dispatching starts.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useConsumerPriority</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Use the priority of a consumer when dispatching messages from a Queue.</p></td></tr></tbody></table><p>The following properties can be applied <em>only</em> to a topic:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Topic Only Property</p></th><th colspan="1" rowspan="1"><p>Default</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>advisoryForDiscardingMessages</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Send an advisory when a message is discarded from a non durable subscription.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>cursorMemoryHighWaterMark</code></p></td><td colspan="1" rowspan="1"><p><code>70</code></p></td><td colspan="1" rowspan="1"><p>The percentage (%) threshold applied to the <strong><code><systemUsage>/<memoryUsage></code></strong> which when exceeded will cause the destination's cursor to either block or write to disk.</p></td></tr><tr><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);"><code>alwaysRetroactive</code><br clear="none"></span></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Makes all subscribers retroactive negating the need to modify the clients to enable this feature.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>durableTopicPrefetch</code></p></td><td colspan="1" rowspan="1"><p><code>n/a</code></p></td><td colspan="1" rowspan="1"><p>Sets the prefetch for durable topic consumers that are using the default value.</p></td></tr><tr><td colspan="1" rowspan="1"><p><span style="color: rgb(0,0,0);"><code>expireMessagesPeriod</code><br clear="none"></span></p></td><td colspan="1" rowspan="1"><p><code>30000</code></p></td><td colspan="1" rowspan="1"><p>The interval (in ms) between message expiration checks on inactive durable subscribers.</p><p><strong>Note</strong>: set to <strong><code>0</code></strong> to disable message expiration checking.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>topicPrefetch</code></p></td><td colspan="1" rowspan="1"><p><code>n/a</code></p></td><td colspan="1" rowspan="1"><p>Sets the prefetch for topic consumers that are using the default value.</p></td></tr></tbody></table><p><span style="line-height: 1.4285715;">The following are examples of different policies that can be customized on a per destination basis:</span></p><ul><li><link><page ri:content-title="Dispatch Policies"></page></link></li></ul><p>An example from the demos <a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=assembly/src/release/examples/conf/activemq-demo.xml;hb=HEAD">https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=assembly/src/release/examples/conf/activemq-demo.xml;hb=HEAD</a>: </p><structured-macro ac:macro-id="396a8d80-d5ba-44b5-9136-6cfe07ef8322" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:amq="http://activemq.apache.org/schema/core"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+ http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker persistent="false"
- brokerName="${brokername}"
- xmlns="http://activemq.apache.org/schema/core">
+ <broker persistent="false"
+ brokerName="${brokername}"
+ xmlns="http://activemq.apache.org/schema/core">
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry topic="FOO.>">
+ <policyEntry topic="FOO.>">
<dispatchPolicy>
<roundRobinDispatchPolicy/>
</dispatchPolicy>
@@ -23,35 +22,34 @@
</subscriptionRecoveryPolicy>
</policyEntry>
- <policyEntry topic="ORDERS.>">
+ <policyEntry topic="ORDERS.>">
<dispatchPolicy>
<strictOrderDispatchPolicy/>
</dispatchPolicy>
- <!-- Recover 1 minute's worth -->
+ <!-- Recover 1 minute's worth -->
<subscriptionRecoveryPolicy>
- <timedSubscriptionRecoveryPolicy recoverDuration="60000"/>
+ <timedSubscriptionRecoveryPolicy recoverDuration="60000"/>
</subscriptionRecoveryPolicy>
</policyEntry>
- <policyEntry topic="PRICES.>">
+ <policyEntry topic="PRICES.>">
<!-- Force pending messages to be discarded for slow consumers -->
<pendingMessageLimitStrategy>
- <constantPendingMessageLimitStrategy limit="10"/>
+ <constantPendingMessageLimitStrategy limit="10"/>
</pendingMessageLimitStrategy>
<!-- 10 seconds worth -->
<subscriptionRecoveryPolicy>
- <timedSubscriptionRecoveryPolicy recoverDuration="10000"/>
+ <timedSubscriptionRecoveryPolicy recoverDuration="10000"/>
</subscriptionRecoveryPolicy>
</policyEntry>
- <policyEntry tempTopic="true" advisoryForConsumed="true"/>
- <policyEntry tempQueue="true" advisoryForConsumed="true"/>
+ <policyEntry tempTopic="true" advisoryForConsumed="true"/>
+ <policyEntry tempQueue="true" advisoryForConsumed="true"/>
</policyEntries>
</policyMap>
</destinationPolicy>
</broker>
-</beans>]]></script>
-</div></div><p> </p><p> </p></div>
+</beans></plain-text-body></structured-macro><p> </p><p> </p></div>
diff --git a/performance-report.xml b/performance-report.xml
index f58b949..2b51c08 100644
--- a/performance-report.xml
+++ b/performance-report.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h2 id="Performancereport-Performanceguides">Performance guides</h2>
+<div class="wiki-content maincontent"><h2>Performance guides</h2>
-<p>If you're not convinced by performance reports then please do try running performance tests yourself. You might wanna check out our overview of <a shape="rect" href="performance.xml">Performance</a> or try using out the <a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a></p>
+<p>If you're not convinced by performance reports then please do try running performance tests yourself. You might wanna check out our overview of <link><page ri:content-title="Performance"></page></link> or try using out the <link><page ri:content-title="ActiveMQ Performance Module Users Manual"></page></link></p>
-<p>The Commercial Providers on the <a shape="rect" href="support.xml">Support</a> page may also be able to help diagnose performance issues, suggest changes, etc...</p></div>
+<p>The Commercial Providers on the <link><page ri:content-title="Support"></page></link> page may also be able to help diagnose performance issues, suggest changes, etc...</p></div>
diff --git a/performance-tuning.xml b/performance-tuning.xml
index 536417c..20fda8e 100644
--- a/performance-tuning.xml
+++ b/performance-tuning.xml
@@ -1,6 +1,2 @@
-<div class="wiki-content maincontent"><p>For a more complete overview see <a shape="rect" href="performance.xml">Performance</a>.</p><p>There are trade-offs between performance and reliability. By default, ActiveMQ strikes a balance between the two, so there are some things you can change to increase throughput.</p><h2 id="PerformanceTuning-AsyncPublishing">Async Publishing</h2><p>First some background:</p><p>When an ActiveMQ message producer sends a non-persistent message, its dispatched asynchronously (fire and forget) - but for persistent messages, the publisher will block until it gets a notification that the message has been processed (saved to the store - queued to be dispatched to any active consumers etc) by the broker. messages are dispatched with delivery mode set to be persistent by default (which is required by the JMS spec). So if you are sending messages on a Topic, the publisher will block by default (even if there are no durable subscribers on the topic) until the broker has returned a notification.</p><p>So if you looking for good performance with topic messages, either set the delivery mode on the publisher to be non-persistent, or set the <strong><code>useAsyncSend</code></strong> property on the ActiveMQ ConnectionFactory to be <strong>true</strong>.</p><h2 id="PerformanceTuning-Pre-fetchSizesforConsumers">Pre-fetch Sizes for Consumers</h2><p>ActiveMQ will push as many messages to the consumer as fast as possible, where they will be queued for processing by an ActiveMQ Session. The maximum number of messages that ActiveMQ will push to a Consumer without the Consumer processing a message is set by the pre-fetch size. You can improve throughput by running ActiveMQ with larger pre-fetch sizes. Pre-fetch sizes are determined by the <strong><code>ActiveMQPrefetchPolicy</code></strong> bean, which is set on the ActiveMQ <strong><code>ConnectionFactory</code></strong>.</p><p>Default values:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Consumer Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>queue</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>queue browser</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>topic</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>32767</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>durable topic</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td></tr></tbody></table></div><h2 id="PerformanceTuning-OptimizedAcknowledge">Optimized Acknowledge</h2><p>When consuming messages in auto acknowledge mode (set when creating the consumers' session), ActiveMQ can acknowledge receipt of messages back to the broker in batches (to improve performance). The batch size is 65% of the prefetch limit for the Consumer. Also if message consumption is slow the batch will be sent every 300ms. You switch batch acknowledgment on by setting <strong><code>optimizeAcknowledge=true</code></strong> on the ActiveMQ <strong><code>ConnectionFactory</code></strong>.</p><h2 id="PerformanceTuning-StraightthroughSessionConsumption">Straight through Session Consumption</h2><p>By default, a Consumer's session will dispatch messages to the consumer in a separate thread. If you are using Consumers with auto acknowledge, you can increase throughput by passing messages straight through the Session to the Consumer by setting <strong><code>alwaysSessionAsync=false</code></strong> on the ActiveMQ <strong><code>ConnectionFactory</code></strong>.</p><h2 id="PerformanceTuning-FilebasedPersistence">File based Persistence</h2><p>We have a <a shape="rect" href="kaha-persistence.xml">file based persistence store</a> that can be used to increase throughput for the persistent messages</p><p></p><h2 id="PerformanceTuning-Performanceguides">Performance guides</h2>
-
-<p>If you're not convinced by performance reports then please do try running performance tests yourself. You might wanna check out our overview of <a shape="rect" href="performance.xml">Performance</a> or try using out the <a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a></p>
-
-<p>The Commercial Providers on the <a shape="rect" href="support.xml">Support</a> page may also be able to help diagnose performance issues, suggest changes, etc...</p></div>
+<div class="wiki-content maincontent"><p>For a more complete overview see <link><page ri:content-title="Performance"></page></link>.</p><p>There are trade-offs between performance and reliability. By default, ActiveMQ strikes a balance between the two, so there are some things you can change to increase throughput.</p><h2>Async Publishing</h2><p>First some background:</p><p>When an ActiveMQ message producer sends a non-persistent message, its dispatched asynchronously (fire and forget) - but for persistent messages, the publisher will block until it gets a notification that the message has been processed (saved to the store - queued to be dispatched to any active consumers etc) by the broker. messages are dispatched with delivery mode set to be persistent by default (which is required by the JMS spec). So if you are sending messages on a Topic, the publisher will block by default (even if there are no durable subscribers on the topic) until the broker has returned a notification.</p><p>So if you looking for good performance with topic messages, either set the delivery mode on the publisher to be non-persistent, or set the <strong><code>useAsyncSend</code></strong> property on the ActiveMQ ConnectionFactory to be <strong>true</strong>.</p><h2>Pre-fetch Sizes for Consumers</h2><p>ActiveMQ will push as many messages to the consumer as fast as possible, where they will be queued for processing by an ActiveMQ Session. The maximum number of messages that ActiveMQ will push to a Consumer without the Consumer processing a message is set by the pre-fetch size. You can improve throughput by running ActiveMQ with larger pre-fetch sizes. Pre-fetch sizes are determined by the <strong><code>ActiveMQPrefetchPolicy</code></strong> bean, which is set on the ActiveMQ <strong><code>ConnectionFactory</code></strong>.</p><p>Default values:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Consumer Type</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>queue</p></td><td colspan="1" rowspan="1"><p><code>1000</code></p></td></tr><tr><td colspan="1" rowspan="1"><p>queue browser</p></td><td colspan="1" rowspan="1"><p><code>500</code></p></td></tr><tr><td colspan="1" rowspan="1"><p>topic</p></td><td colspan="1" rowspan="1"><p><code>32767</code></p></td></tr><tr><td colspan="1" rowspan="1"><p>durable topic</p></td><td colspan="1" rowspan="1"><p><code>1000</code></p></td></tr></tbody></table><h2>Optimized Acknowledge</h2><p>When consuming messages in auto acknowledge mode (set when creating the consumers' session), ActiveMQ can acknowledge receipt of messages back to the broker in batches (to improve performance). The batch size is 65% of the prefetch limit for the Consumer. Also if message consumption is slow the batch will be sent every 300ms. You switch batch acknowledgment on by setting <strong><code>optimizeAcknowledge=true</code></strong> on the ActiveMQ <strong><code>ConnectionFactory</code></strong>.</p><h2>Straight through Session Consumption</h2><p>By default, a Consumer's session will dispatch messages to the consumer in a separate thread. If you are using Consumers with auto acknowledge, you can increase throughput by passing messages straight through the Session to the Consumer by setting <strong><code>alwaysSessionAsync=false</code></strong> on the ActiveMQ <strong><code>ConnectionFactory</code></strong>.</p><h2>File based Persistence</h2><p>We have a <link><page ri:content-title="Kaha Persistence"></page><plain-text-link-body>file based persistence store</plain-text-link-body></link> that can be used to increase throughput for the persistent messages</p><p><structured-macro ac:macro-id="9cd31d2e-5170-4031-a064-9326143a54d6" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Performance report"></page></link></parameter></structured-macro></p></div>
diff --git a/performance.xml b/performance.xml
index 6772fca..cf37e27 100644
--- a/performance.xml
+++ b/performance.xml
@@ -1,26 +1,22 @@
-<div class="wiki-content maincontent"><h2 id="Performance-Performance">Performance</h2>
+<div class="wiki-content maincontent"><h2>Performance</h2>
<p>Performance differs greatly depending on many different factors</p>
-<ul><li>the network <a shape="rect" href="topologies.xml">topology</a></li><li>transport <a shape="rect" href="uri-protocols.xml">protocols</a> used</li><li><a shape="rect" href="qos.xml">quality of service</a></li><li>hardware, network, JVM and operating system</li><li>number of producers, number of consumers</li><li>distribution of messages across destinations along with message size</li></ul>
+<ul><li>the network <link><page ri:content-title="Topologies"></page><link-body>topology</link-body></link></li><li>transport <link><page ri:content-title="URI Protocols"></page><link-body>protocols</link-body></link> used</li><li><link><page ri:content-title="QoS"></page><link-body>quality of service</link-body></link></li><li>hardware, network, JVM and operating system</li><li>number of producers, number of consumers</li><li>distribution of messages across destinations along with message size</li></ul>
-<p>To give you an idea of the kinds of performance you can expect from ActiveMQ we have a bunch of <a shape="rect" href="jmeter-performance-tests.xml">JMeter Performance Tests</a> that you can run on your hardware with the protocols of your choice.</p>
+<p>To give you an idea of the kinds of performance you can expect from ActiveMQ we have a bunch of <link><page ri:content-title="JMeter Performance Tests"></page></link> that you can run on your hardware with the protocols of your choice.</p>
<p>The last test run we ran was on a small network of 2 dual CPU opteron linux boxes (64 bit) running SuSe and with Java 5 from Sun.</p>
<p>When running the server on one box and a single producer and consumer thread in separate VMs on the other box, using a single topic we got around 21-22,000 messages/second using 1-2K messages. Another test running the broker on a Intel Celeron CPU 2.40GHz we got 2000 messages/second on a durable queue with 1 producer and 1 consumer thread on another box. So your milleage may vary greatly on your environment.</p>
-<h3 id="Performance-PerformanceTesting">Performance Testing</h3>
+<h3>Performance Testing</h3>
<p>We have a few tools to help you evaluate performance.</p>
-<ul><li><a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a></li><li><a shape="rect" href="load-testing-with-camel.xml">Load Testing with Camel</a></li><li><a shape="rect" href="jmeter-performance-tests.xml">JMeter Performance Tests</a></li></ul>
+<ul><li><link><page ri:content-title="ActiveMQ Performance Module Users Manual"></page></link></li><li><link><page ri:content-title="Load Testing with Camel"></page></link></li><li><link><page ri:content-title="JMeter Performance Tests"></page></link></li></ul>
-<h2 id="Performance-Performanceguides">Performance guides</h2>
-
-<p>If you're not convinced by performance reports then please do try running performance tests yourself. You might wanna check out our overview of <a shape="rect" href="performance.xml">Performance</a> or try using out the <a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a></p>
-
-<p>The Commercial Providers on the <a shape="rect" href="support.xml">Support</a> page may also be able to help diagnose performance issues, suggest changes, etc...</p></div>
+<structured-macro ac:macro-id="8c845d04-94d0-453d-9a26-58ad707c2ed5" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Performance report"></page></link></parameter></structured-macro></div>
diff --git a/periodically-checking-disk-limits.xml b/periodically-checking-disk-limits.xml
index ec0389a..b16fcdb 100644
--- a/periodically-checking-disk-limits.xml
+++ b/periodically-checking-disk-limits.xml
@@ -1,7 +1,5 @@
-<div class="wiki-content maincontent"><p>Store and temporary disk limits are set for the Broker on startup based on configuration and available space. Sometimes other processes (such as logs) can grow and reduce the available disk space enough that the limits detected at start up no longer have any effect. Since ActiveMQ version <strong style="line-height: 1.4285715;">5.12.0</strong>, it's possible to configure the Broker to periodically check disk space and reconfigure the limits accordingly using the broker attribute schedulePeriodForDiskUsageCheck > 0.</p><p>For example a configuration like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <broker xmlns="http://activemq.apache.org/schema/core" schedulePeriodForDiskUsageCheck="60000">
+<div class="wiki-content maincontent"><p>Store and temporary disk limits are set for the Broker on startup based on configuration and available space. Sometimes other processes (such as logs) can grow and reduce the available disk space enough that the limits detected at start up no longer have any effect. Since ActiveMQ version <strong style="line-height: 1.4285715;">5.12.0</strong>, it's possible to configure the Broker to periodically check disk space and reconfigure the limits accordingly using the broker attribute schedulePeriodForDiskUsageCheck > 0.</p><p>For example a configuration like</p><structured-macro ac:macro-id="65894a73-9f06-406a-a6d6-83772abe71e8" ac:name="code" ac:schema-version="1"><plain-text-body> <broker xmlns="http://activemq.apache.org/schema/core" schedulePeriodForDiskUsageCheck="60000">
...
</broker>
-]]></script>
-</div></div><p>will check the store and temporary disk limits every 60 seconds (<code>schedulePeriodForDiskUsageCheck</code> option, default value is 0 which disables this check).</p><p> </p></div>
+</plain-text-body></structured-macro><p>will check the store and temporary disk limits every 60 seconds (<code>schedulePeriodForDiskUsageCheck</code> option, default value is 0 which disables this check).</p><p> </p></div>
diff --git a/persistence-questions.xml b/persistence-questions.xml
index 55f2929..e88e5e7 100644
--- a/persistence-questions.xml
+++ b/persistence-questions.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>Questions relating to long term persistence of messages.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="are-messages-read-directly-from-the-journal.xml">Are messages read directly from the journal</a></li><li><a shape="rect" href="does-activemq-support-my-sql-database.xml">Does ActiveMQ support my SQL database</a></li><li><a shape="rect" href="how-does-journaling-work-with-multiple-brokers.xml">How does journaling work with multiple brokers</a></li><li><a shape="rect" href="how-does-the-journal-work.xml">How does the journal work</a></li><li><a shape="rect" href="how-do-i-back-up-kahadb.xml">How do I back-up KahaDB</a></li><li><a shape="rect" href="how-do-i-change-the-message-store-directory-for-an-embedded-broker.xml">How do I change the message store directory for an embedded broker</a></li><li><a shape="rect" href="is-there-a-specified-size-of-the-journal.xml">Is there a specified size of the journal</a></li><li><a shape="rect" href="what-happens-when-the-journal-size-is-exceeded.xml">What happens when the journal size is exceeded</a></li><li><a shape="rect" href="what-is-the-difference-between-persistent-and-non-persistent-delivery.xml">What is the difference between persistent and non-persistent delivery</a></li></ul></div>
+<structured-macro ac:macro-id="a68a4179-efd8-4461-8b91-c4eb78c1c715" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/persistence.xml b/persistence.xml
index ded01e6..618faba 100644
--- a/persistence.xml
+++ b/persistence.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="Persistence-ActiveMQV5.9">ActiveMQ V5.9</h2><p>In ActiveMQ 5.9, the <a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a> is introduced. It handles using <a shape="rect" class="external-link" href="http://zookeeper.apache.org/">Apache ZooKeeper</a> to pick a master from a set of broker nodes configured to replicate single LevelDB Store. Then synchronizes all slave LevelDB Stores with the master keeps them up to date by replicating all updates to the master. This might become the preferred <a shape="rect" href="masterslave.xml">Master Slave</a> configuration going forward.</p><h2 id="Persistence-ActiveMQV5.8">ActiveMQ V5.8</h2><p>In ActiveMQ 5.8, the <a shape="rect" href="leveldb-store.xml">LevelDB Store</a> was introduced. The LevelDB Store is a file based persistence database. It has been optimized to provide even faster persistence than KahaDB. Although not yet the default message store, we expect this store implementation become the default in future releases.</p><h2 id="Persistence-ActiveMQV5.3">ActiveMQ V5.3</h2><p>From 5.3 onwards - we recommend you use <a shape="rect" href="kahadb.xml">KahaDB</a> - which offers improved scalability and recoverability over the <a shape="rect" href="amq-message-store.xml">AMQ Message Store</a>.<br clear="none"> The <a shape="rect" href="amq-message-store.xml">AMQ Message Store</a> which although faster than <a shape="rect" href="kahadb.xml">KahaDB</a> - does not scales as well as <a shape="rect" href="kahadb.xml">KahaDB</a> and recovery times take longer.</p><h2 id="Persistence-ActiveMQV4">ActiveMQ V4</h2><p>For long term persistence we recommend using JDBC coupled with our high performance journal. You can use just JDBC if you wish but its quite slow.</p><p>Our out of the box default configuration uses <a shape="rect" class="external-link" href="http://incubator.apache.org/derby/">Apache Derby</a> as the default database, which is easy to embed - but we support all the <a shape="rect" href="jdbc-support.xml">major SQL databases</a> - just reconfigure your JDBC configuration in the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>.</p><h2 id="Persistence-Highperformancejournal-ActiveMQ4.x">High performance journal - ActiveMQ 4.x</h2><p>To achieve high performance of durable messaging in ACtiveMQ V4.x we strongly recommend you use our high performance journal - which is enabled by default. This works rather like a database; messages (and transcation commits/rollbacks and message acknowledgements) are written to the journal as fast as is humanly possible - then at intervals we checkpoint the journal to the long term persistence storage (in this case JDBC).</p><p>Its common when using queues for example that messages are consumed fairly shortly after being published; so you could publish 10,000 messages and only have a few messages outstanding - so when we checkpoint to the JDBC database, we often have only a small amount of messages to actually write to JDBC. Even if we have to write all the messages to the JDBC, we still get performance gains with the journal, since we can use a large transaction batch to insert the messages into the JDBC database to boost performance on the JDBC side.</p><p>Our journal is based on lots of the great work in the <a shape="rect" class="external-link" href="http://howl.objectweb.org/" rel="nofollow">Howl</a> project; we keep close ties to the Howl community. However since ActiveMQ has to handle arbitarily large message sizes, we've had to make our journal handle any size of message and so we don't use the fixed size record model that Howl uses.</p><h2 id="Persistence-Configuringpersistence">Configuring persistence</h2><p>For full explict control over configuration check out the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. However a quick way to set which persistence adapter to use is to set the following system property to be the class name of the PersistenceAdapter implementation.</p><plain-text-body>activemq.persistenceAdapter
+<div class="wiki-content maincontent"><h2>ActiveMQ V5.9</h2><p>In ActiveMQ 5.9, the <link><page ri:content-title="Replicated LevelDB Store"></page></link> is introduced. It handles using <a shape="rect" href="http://zookeeper.apache.org/">Apache ZooKeeper</a> to pick a master from a set of broker nodes configured to replicate single LevelDB Store. Then synchronizes all slave LevelDB Stores with the master keeps them up to date by replicating all updates to the master. This might become the preferred <link><page ri:content-title="MasterSlave"></page><plain-text-link-body>Master Slave</plain-text-link-body></link> configuration going forward.</p><h2>ActiveMQ V5.8</h2><p>In ActiveMQ 5.8, the <link><page ri:content-title="LevelDB Store"></page></link> was introduced. The LevelDB Store is a file based persistence database. It has been optimized to provide even faster persistence than KahaDB. Although not yet the default message store, we expect this store implementation become the default in future releases.</p><h2>ActiveMQ V5.3</h2><p>From 5.3 onwards - we recommend you use <link><page ri:content-title="KahaDB"></page></link> - which offers improved scalability and recoverability over the <link><page ri:content-title="AMQ Message Store"></page></link>.<br clear="none"> The <link><page ri:content-title="AMQ Message Store"></page></link> which although faster than <link><page ri:content-title="KahaDB"></page></link> - does not scales as well as <link><page ri:content-title="KahaDB"></page></link> and recovery times take longer.</p><h2>ActiveMQ V4</h2><p>For long term persistence we recommend using JDBC coupled with our high performance journal. You can use just JDBC if you wish but its quite slow.</p><p>Our out of the box default configuration uses <a shape="rect" href="http://incubator.apache.org/derby/">Apache Derby</a> as the default database, which is easy to embed - but we support all the <link><page ri:content-title="JDBC Support"></page><plain-text-link-body>major SQL databases</plain-text-link-body></link> - just reconfigure your JDBC configuration in the <link><page ri:content-title="Xml Configuration"></page></link>.</p><h2>High performance journal - ActiveMQ 4.x</h2><p>To achieve high performance of durable messaging in ACtiveMQ V4.x we strongly recommend you use our high performance journal - which is enabled by default. This works rather like a database; messages (and transcation commits/rollbacks and message acknowledgements) are written to the journal as fast as is humanly possible - then at intervals we checkpoint the journal to the long term persistence storage (in this case JDBC).</p><p>Its common when using queues for example that messages are consumed fairly shortly after being published; so you could publish 10,000 messages and only have a few messages outstanding - so when we checkpoint to the JDBC database, we often have only a small amount of messages to actually write to JDBC. Even if we have to write all the messages to the JDBC, we still get performance gains with the journal, since we can use a large transaction batch to insert the messages into the JDBC database to boost performance on the JDBC side.</p><p>Our journal is based on lots of the great work in the <a shape="rect" href="http://howl.objectweb.org/">Howl</a> project; we keep close ties to the Howl community. However since ActiveMQ has to handle arbitarily large message sizes, we've had to make our journal handle any size of message and so we don't use the fixed size record model that Howl uses.</p><h2>Configuring persistence</h2><p>For full explict control over configuration check out the <link><page ri:content-title="Xml Configuration"></page></link>. However a quick way to set which persistence adapter to use is to set the following system property to be the class name of the PersistenceAdapter implementation.</p><plain-text-body>activemq.persistenceAdapter
</plain-text-body><p>When running the broker from the command line, we look for the activemq.xml on the classpath unless you specify one to use. e.g.<br clear="none"> <strong>AMQ 4.x</strong></p><plain-text-body>activemq xbean:file:myconfig.xml
</plain-text-body><p><strong>AMQ 3.x</strong></p><plain-text-body>activemq myconfig.xml
</plain-text-body><p>or just<br clear="none"> <strong>AMQ3.x/AMQ4.x</strong></p><plain-text-body>activemq
@@ -38,7 +38,7 @@
<property name="poolPreparedStatements" value="true"/>
</bean>
-->
-</beans></plain-text-body><p>For more details see the <a shape="rect" href="initial-configuration.xml">Initial Configuration</a> guide.</p><h2 id="Persistence-JDBCPersistencewithoutJournaling">JDBC Persistence without Journaling</h2><p>To enable JDBC persistence of JMS messages without journaling, we need to change the message broker's default persistence configuration from<br clear="none"> <strong>AMQ 4.x</strong></p><plain-text-body><persistenceAdapter>
+</beans></plain-text-body><p>For more details see the <link><page ri:content-title="Initial Configuration"></page></link> guide.</p><h2>JDBC Persistence without Journaling</h2><p>To enable JDBC persistence of JMS messages without journaling, we need to change the message broker's default persistence configuration from<br clear="none"> <strong>AMQ 4.x</strong></p><plain-text-body><persistenceAdapter>
<journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data"/>
</persistenceAdapter>
</plain-text-body><p>to</p><plain-text-body><persistenceAdapter>
@@ -52,7 +52,7 @@
</plain-text-body><p>to</p><plain-text-body><persistence>
<jdbcPersistence dataSourceRef="derby-ds"/>
</persistence>
-</plain-text-body><p>Make sure to send durable messages so that it will be persisted in the database server while waiting to be consumed by clients. More information on configuration JDBC persistence at <a shape="rect" href="jdbc-support.xml">JDBC Support</a></p><p><parameter ac:name=""><a shape="rect" href="kaha-persistence.xml">Kaha Persistence</a></parameter></p><h2 id="Persistence-DisasterRecoveryoptions">Disaster Recovery options</h2><p>For people with high <a shape="rect" href="dr.xml">DR</a> requirements we have various options for providing a <a shape="rect" href="replicated-message-store.xml">Replicated Message Store</a> to allow full failover in times of major data centre failure.</p><h2 id="Persistence-DisablingPersistence">Disabling Persistence</h2><p>If you don't want persistence at all you can disable it easily via the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. e.g.</p><plain-text-body><broker persistent="false">
+</plain-text-body><p>Make sure to send durable messages so that it will be persisted in the database server while waiting to be consumed by clients. More information on configuration JDBC persistence at <link><page ri:content-title="JDBC Support"></page></link></p><p><parameter ac:name=""><link><page ri:content-title="Kaha Persistence"></page></link></parameter></p><h2>Disaster Recovery options</h2><p>For people with high <link><page ri:content-title="DR"></page></link> requirements we have various options for providing a <link><page ri:content-title="Replicated Message Store"></page></link> to allow full failover in times of major data centre failure.</p><h2>Disabling Persistence</h2><p>If you don't want persistence at all you can disable it easily via the <link><page ri:content-title="Xml Configuration"></page></link>. e.g.</p><plain-text-body><broker persistent="false">
</broker>
-</plain-text-body><p>This will make the broker use the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/store/memory/MemoryPersistenceAdapter.html"><memoryPersistenceAdapter></a><br clear="none"> For an example of using a configuration URI see <a shape="rect" href="how-to-unit-test-jms-code.xml">How To Unit Test JMS Code</a></p></div>
+</plain-text-body><p>This will make the broker use the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/store/memory/MemoryPersistenceAdapter.html"><memoryPersistenceAdapter></a><br clear="none"> For an example of using a configuration URI see <link><page ri:content-title="How To Unit Test JMS Code"></page></link></p></div>
diff --git a/pluggable-storage-lockers.xml b/pluggable-storage-lockers.xml
index 49cd07f..8f0c635 100644
--- a/pluggable-storage-lockers.xml
+++ b/pluggable-storage-lockers.xml
@@ -1,41 +1,33 @@
-<div class="wiki-content maincontent"><p>As of the 5.7.0 release of ActiveMQ the choice of storage locking mechanism, as used by a persistence adapter, has been made pluggable. This feature is only meaningful to brokers configured in a shared storage master/slave topology. Prior to release 5.7.0 the storage locking mechanism (and thus master election) was dictated by the choice of persistence adapter. With the KahaDB persistence adapter, for example, the storage locking mechanism was based on a shared file lock. Similarly, the JDBC persistence adapter used a database backed storage lock.</p><p>Now that the choice of storage locker is divorced from that of the persistence adapter one can mix and match combinations of the two. Storage locker pluggability is made possible by the <a shape="rect" class="external-link" href="https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/broker/Locker.java?hb=true" rel="nofollow">Locker</a> interface that all pluggable lockers must implement. This interface makes it easy to implement a custom storage locker that meets local requirements.</p><p>Every persistence adapter, however, has its own default locker which works as before.</p><h2 id="Pluggablestoragelockers-Lockers">Lockers</h2><p>Every locker must implement the <a shape="rect" class="external-link" href="https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/broker/Locker.java?hb=true" rel="nofollow">Locker</a> interface. The locker interface has the following properties:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property 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><strong><code>lockAcquireSleepInterval</code></strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The polling interval (in milliseconds) between lock acquire attempts.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>failIfLocked</code></strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker start fail if the lock is not immediately available. When <strong><code>true</code></strong> slave brokers will not start.</p></td></tr></tbody></table></div><h2 id="Pluggablestoragelockers-PersistenceAdapters">Persistence Adapters</h2><p>Every persistence adapter (or any other broker service that wishes to use locks) must implement the <a shape="rect" class="external-link" href="https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/broker/Lockable.java?r=1383400" rel="nofollow">Lockable</a> interface. This interface has the following properties:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property 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><strong><code>useLock</code></strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the persistence adapter use the configured locker. Intended primarily for use during development to temporarily disable the use of the locker without having to remove its configuration.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>lockKeepAlivePeriod</code></strong></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The duration (in milliseconds) to keep the lock alive, when greater than <code>0</code>.</p></td></tr></tbody></table></div><h2 id="Pluggablestoragelockers-ExistingLockers">Existing Lockers</h2><h3 id="Pluggablestoragelockers-SharedFileLocker">Shared File Locker</h3><p>The Shared File Locker is the default locker for the KahaDB persistence adapter. It locks a file to ensure that only the broker holding the lock (the master) is granted access to the message store.</p><h4 id="Pluggablestoragelockers-Example:">Example:</h4><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<persistenceAdapter>
- <kahaDB directory="target/activemq-data" lockKeepAlivePeriod="10000">
+<div class="wiki-content maincontent"><p>As of the 5.7.0 release of ActiveMQ the choice of storage locking mechanism, as used by a persistence adapter, has been made pluggable. This feature is only meaningful to brokers configured in a shared storage master/slave topology. Prior to release 5.7.0 the storage locking mechanism (and thus master election) was dictated by the choice of persistence adapter. With the KahaDB persistence adapter, for example, the storage locking mechanism was based on a shared file lock. Similarly, the JDBC persistence adapter used a database backed storage lock.</p><p>Now that the choice of storage locker is divorced from that of the persistence adapter one can mix and match combinations of the two. Storage locker pluggability is made possible by the <a shape="rect" href="https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/broker/Locker.java?hb=true">Locker</a> interface that all pluggable lockers must implement. This interface makes it easy to implement a custom storage locker that meets local requirements.</p><p>Every persistence adapter, however, has its own default locker which works as before.</p><h2>Lockers</h2><p>Every locker must implement the <a shape="rect" href="https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/broker/Locker.java?hb=true">Locker</a> interface. The locker interface has the following properties:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong><code>lockAcquireSleepInterval</code></strong></p></td><td colspan="1" rowspan="1"><p><code>10000</code></p></td><td colspan="1" rowspan="1"><p>The polling interval (in milliseconds) between lock acquire attempts.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong><code>failIfLocked</code></strong></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Should the broker start fail if the lock is not immediately available. When <strong><code>true</code></strong> slave brokers will not start.</p></td></tr></tbody></table><h2>Persistence Adapters</h2><p>Every persistence adapter (or any other broker service that wishes to use locks) must implement the <a shape="rect" href="https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-broker/src/main/java/org/apache/activemq/broker/Lockable.java?r=1383400">Lockable</a> interface. This interface has the following properties:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Property Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong><code>useLock</code></strong></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>Should the persistence adapter use the configured locker. Intended primarily for use during development to temporarily disable the use of the locker without having to remove its configuration.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong><code>lockKeepAlivePeriod</code></strong></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>The duration (in milliseconds) to keep the lock alive, when greater than <code>0</code>.</p></td></tr></tbody></table><h2>Existing Lockers</h2><h3>Shared File Locker</h3><p>The Shared File Locker is the default locker for the KahaDB persistence adapter. It locks a file to ensure that only the broker holding the lock (the master) is granted access to the message store.</p><h4>Example:</h4><structured-macro ac:macro-id="a992c3be-c681-47aa-80c4-c8b67fc9485b" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><persistenceAdapter>
+ <kahaDB directory="target/activemq-data" lockKeepAlivePeriod="10000">
<locker>
- <shared-file-locker lockAcquireSleepInterval="5000"/>
+ <shared-file-locker lockAcquireSleepInterval="5000"/>
</locker>
</kahaDB>
-</persistenceAdapter>]]></script>
-</div></div><p>The <strong><code>lockKeepAlivePeriod</code></strong> attribute is not applicable to versions of ActiveMQ older than 5.9.0.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Consequences of lockKeepAlivePeriod = 0</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>For this locker <strong><code>lockKeepAlivePeriod</code></strong> should be greater than <strong><code>0</code></strong>.This period is the frequency with which the master broker makes lock keep alive calls.</p><p>When <strong><code>lockKeepAlivePeriod = 0</code></strong> slave brokers are still unable to obtain the file lock. However, if some third party modifies the lock file (either modification or deletion) the master broker will not detect the change. Therefore a slave broker's next attempt (per its configured <strong><code>lockAcquireSleepInterval</code></strong>) to obtain the file lock will succeed. When this happens there will be two master brokers in the cluster. <em><u>This situation will result in message store corruption</u></em>!</p><p>When <strong><code>lockKeepAlivePeriod</code></strong> is greater than <strong><code>0</code></strong>, the master broker will make a lock keep alive call every <strong><code>lockKeepAlivePeriod</code></strong> milliseconds. Therefore the master broker will detect any lock file changes when it makes its next keep alive call. Upon detecting said change the master broker will demote itself to a slave broker.</p></div></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Note that as of ActiveMQ 5.9.0 the KahaDB persistence adapter can also use the Lease Database Locker (see below).</p></div></div><h3 id="Pluggablestoragelockers-DatabaseLocker">Database Locker</h3><p>The Database Locker is the default locker for the JDBC persistence adapter. It locks a database table in a transaction to ensure that only single resource is used.</p><h4 id="Pluggablestoragelockers-Example:.1">Example:</h4><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<persistenceAdapter>
- <jdbcPersistenceAdapter dataDirectory="${activemq.data}" dataSource="#mysql-ds" lockKeepAlivePeriod="10000">
+</persistenceAdapter></plain-text-body></structured-macro><p>The <strong><code>lockKeepAlivePeriod</code></strong> attribute is not applicable to versions of ActiveMQ older than 5.9.0.</p><structured-macro ac:macro-id="ba619597-e25a-4d23-a904-9b9a1301dbad" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Consequences of lockKeepAlivePeriod = 0</parameter><rich-text-body><p>For this locker <strong><code>lockKeepAlivePeriod</code></strong> should be greater than <strong><code>0</code></strong>.This period is the frequency with which the master broker makes lock keep alive calls.</p><p>When <strong><code>lockKeepAlivePeriod = 0</code></strong> slave brokers are still unable to obtain the file lock. However, if some third party modifies the lock file (either modification or deletion) the master broker will not detect the change. Therefore a slave broker's next attempt (per its configured <strong><code>lockAcquireSleepInterval</code></strong>) to obtain the file lock will succeed. When this happens there will be two master brokers in the cluster. <em><u>This situation will result in message store corruption</u></em>!</p><p>When <strong><code>lockKeepAlivePeriod</code></strong> is greater than <strong><code>0</code></strong>, the master broker will make a lock keep alive call every <strong><code>lockKeepAlivePeriod</code></strong> milliseconds. Therefore the master broker will detect any lock file changes when it makes its next keep alive call. Upon detecting said change the master broker will demote itself to a slave broker.</p></rich-text-body></structured-macro><structured-macro ac:macro-id="29199f5d-3193-4a1c-8580-f74d360b1bfe" ac:name="info" ac:schema-version="1"><rich-text-body><p>Note that as of ActiveMQ 5.9.0 the KahaDB persistence adapter can also use the Lease Database Locker (see below).</p></rich-text-body></structured-macro><h3>Database Locker</h3><p>The Database Locker is the default locker for the JDBC persistence adapter. It locks a database table in a transaction to ensure that only single resource is used.</p><h4>Example:</h4><structured-macro ac:macro-id="7ac0fbce-b922-43b4-bd9f-5422e6862bd4" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><persistenceAdapter>
+ <jdbcPersistenceAdapter dataDirectory="${activemq.data}" dataSource="#mysql-ds" lockKeepAlivePeriod="10000">
<locker>
- <database-locker lockAcquireSleepInterval="5000"/>
+ <database-locker lockAcquireSleepInterval="5000"/>
</locker>
</jdbcPersistenceAdapter>
-</persistenceAdapter>]]></script>
-</div></div><p>The Database Locker uses its <strong><code>keepAlive</code></strong> method to ensure the broker still holds the lock. You can set the keep alive period using the <strong><code>lockKeepAlivePeriod</code></strong> property. The default period is 30000 ms. If a broker fails to acquire the lock on the database, it will retry every <strong><code>lockAcquireSleepInterval</code></strong> milliseconds.</p><p>This locker opens a JDBC transaction against a database table (<strong><code>activemq_lock</code></strong>) that lasts as long as the broker remains alive. This locks the entire table and prevents another broker from accessing the store. In most cases this will be a fairly long running JDBC transaction which occupies resources on the database over time.</p><p>A problem with this locker can arise when the master broker crashes or loses its connection to the database causing the lock to remain in the database until the database responds to the half closed socket connection via a TCP timeout. The database lock expiry requirement can prevent the slave from starting some time. In addition, if the database supports failover, and the connection is dropped in the event of a replica failover, that JDBC transaction will be rolled back. The broker sees this as a failure. Both master and slave brokes will again compete for a lock.</p><h3 id="Pluggablestoragelockers-LeaseDatabaseLocker">Lease Database Locker</h3><p>The Lease Database Locker was created to solve the shortcomings of the Database Locker. The Lease Database Locker does not open a long running JDBC transaction. Instead it lets the master broker acquire a lock that's valid for a fixed (usually short) duration after which it expires. To retain the lock the master broker must periodically extend the lock's lease before it expires. Simultaneously the slave broker checks periodically to see if the lease has expired. If, for whatever reason, the master broker fails to update its lease on the lock the slave will take ownership of the lock becoming the new master in the process. The leased lock can survive a DB replica failover.</p><h4 id="Pluggablestoragelockers-Example:.2">Example:</h4><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<persistenceAdapter>
- <jdbcPersistenceAdapter dataDirectory="${activemq.data}" dataSource="#mysql-ds" lockKeepAlivePeriod="5000">
+</persistenceAdapter></plain-text-body></structured-macro><p>The Database Locker uses its <strong><code>keepAlive</code></strong> method to ensure the broker still holds the lock. You can set the keep alive period using the <strong><code>lockKeepAlivePeriod</code></strong> property. The default period is 30000 ms. If a broker fails to acquire the lock on the database, it will retry every <strong><code>lockAcquireSleepInterval</code></strong> milliseconds.</p><p>This locker opens a JDBC transaction against a database table (<strong><code>activemq_lock</code></strong>) that lasts as long as the broker remains alive. This locks the entire table and prevents another broker from accessing the store. In most cases this will be a fairly long running JDBC transaction which occupies resources on the database over time.</p><p>A problem with this locker can arise when the master broker crashes or loses its connection to the database causing the lock to remain in the database until the database responds to the half closed socket connection via a TCP timeout. The database lock expiry requirement can prevent the slave from starting some time. In addition, if the database supports failover, and the connection is dropped in the event of a replica failover, that JDBC transaction will be rolled back. The broker sees this as a failure. Both master and slave brokes will again compete for a lock.</p><h3>Lease Database Locker</h3><p>The Lease Database Locker was created to solve the shortcomings of the Database Locker. The Lease Database Locker does not open a long running JDBC transaction. Instead it lets the master broker acquire a lock that's valid for a fixed (usually short) duration after which it expires. To retain the lock the master broker must periodically extend the lock's lease before it expires. Simultaneously the slave broker checks periodically to see if the lease has expired. If, for whatever reason, the master broker fails to update its lease on the lock the slave will take ownership of the lock becoming the new master in the process. The leased lock can survive a DB replica failover.</p><h4>Example:</h4><structured-macro ac:macro-id="4b46ab4c-27c9-4687-94ef-b3f06d3f0798" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><persistenceAdapter>
+ <jdbcPersistenceAdapter dataDirectory="${activemq.data}" dataSource="#mysql-ds" lockKeepAlivePeriod="5000">
<locker>
- <lease-database-locker lockAcquireSleepInterval="10000"/>
+ <lease-database-locker lockAcquireSleepInterval="10000"/>
</locker>
</jdbcPersistenceAdapter>
-</persistenceAdapter>]]></script>
-</div></div><p>In order for this mechanism to work correctly, each broker in a master/slave(s) cluster must have a unique value for the <strong><code>brokerName</code></strong> attribute as defined on the <strong><code><broker/></code></strong> tag. Alternatively, use unique values for the <span><strong><code>leaseHolderId</code></strong> attribute</span> on the <strong><code><span style="line-height: 1.42857;"><lease-database-locker/></span></code></strong><span> tag as this value is used to create a lease lock definition.</span></p><p>The lease based lock is acquired by blocking at startup. It is then retained for a period whose duration (in ms) is given by the <strong><code>lockKeepAlivePeriod</code></strong> attribute. To retain the lock the master broker periodically extends its lease by <strong><code>lockAcquireSleepInterval</code></strong> milliseconds each time. In theory, therefore, the master broker is always (<strong><code>lockAcquireSleepInterval - lockKeepAlivePeriod</code></strong>) ahead of the slave broker with regard to the lease. It is imperative that <strong><code>lockAcquireSleepInterval > lockKeepAlivePeriod</code></strong>, to ensure the lease is always current. As of ActiveMQ 5.9.0 a warning message is logged if this condition is not met.</p><p>In the simplest case, the clocks between master and slave must be in sync for this solution to work properly. If the clocks cannot be in sync, the locker can use the system time from the database CURRENT TIME and adjust the timeouts in accordance with their local variance from the DB system time. If <strong><code>maxAllowableDiffFromDBTime</code></strong> is greater than zero the local periods will be adjusted by any delta that exceeds <strong><code>maxAllowableDiffFromDBTime</code></strong>.</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>It is important to know if the default rules your JDBC driver uses for converting <code>TIME</code> values are JDBC compliant. If you're using MySQL, for example, the driver's JDBC URL should contain <strong><code>useJDBCCompliantTimezoneShift=true</code></strong> to ensure that <code>TIME</code> value conversion is JDBC compliant. If not the locker could report a large time difference when it compares the retrieved lease expiration time against the current system time. Consult your JDBC driver's documentation for more details.</p></div></div><p>As of ActiveMQ 5.9.0 the lease database locker can be used in conjunction with the KahaDB persistence adapter. However, this particular combination requires that the lease database locker element contains a <strong><code><statements/></code></strong> child element. In the example below the <strong><code>lockTableName</code></strong> is also configured, although doing so is not mandatory.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <persistenceAdapter>
- <kahaDB directory="target/activemq-data" lockKeepAlivePeriod="5000">
+</persistenceAdapter></plain-text-body></structured-macro><p>In order for this mechanism to work correctly, each broker in a master/slave(s) cluster must have a unique value for the <strong><code>brokerName</code></strong> attribute as defined on the <strong><code><broker/></code></strong> tag. Alternatively, use unique values for the <span><strong><code>leaseHolderId</code></strong> attribute</span> on the <strong><code><span style="line-height: 1.42857;"><lease-database-locker/></span></code></strong><span> tag as this value is used to create a lease lock definition.</span></p><p>The lease based lock is acquired by blocking at startup. It is then retained for a period whose duration (in ms) is given by the <strong><code>lockKeepAlivePeriod</code></strong> attribute. To retain the lock the master broker periodically extends its lease by <strong><code>lockAcquireSleepInterval</code></strong> milliseconds each time. In theory, therefore, the master broker is always (<strong><code>lockAcquireSleepInterval - lockKeepAlivePeriod</code></strong>) ahead of the slave broker with regard to the lease. It is imperative that <strong><code>lockAcquireSleepInterval > lockKeepAlivePeriod</code></strong>, to ensure the lease is always current. As of ActiveMQ 5.9.0 a warning message is logged if this condition is not met.</p><p>In the simplest case, the clocks between master and slave must be in sync for this solution to work properly. If the clocks cannot be in sync, the locker can use the system time from the database CURRENT TIME and adjust the timeouts in accordance with their local variance from the DB system time. If <strong><code>maxAllowableDiffFromDBTime</code></strong> is greater than zero the local periods will be adjusted by any delta that exceeds <strong><code>maxAllowableDiffFromDBTime</code></strong>.</p><structured-macro ac:macro-id="e068e3fd-f2fc-4391-8b4c-6338e9dbde1f" ac:name="info" ac:schema-version="1"><rich-text-body><p>It is important to know if the default rules your JDBC driver uses for converting <code>TIME</code> values are JDBC compliant. If you're using MySQL, for example, the driver's JDBC URL should contain <strong><code>useJDBCCompliantTimezoneShift=true</code></strong> to ensure that <code>TIME</code> value conversion is JDBC compliant. If not the locker could report a large time difference when it compares the retrieved lease expiration time against the current system time. Consult your JDBC driver's documentation for more details.</p></rich-text-body></structured-macro><p>As of ActiveMQ 5.9.0 the lease database locker can be used in conjunction with the KahaDB persistence adapter. However, this particular combination requires that the lease database locker element contains a <strong><code><statements/></code></strong> child element. In the example below the <strong><code>lockTableName</code></strong> is also configured, although doing so is not mandatory.</p><structured-macro ac:macro-id="f3c6bc58-79eb-41f3-874d-944410aa835d" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body> <persistenceAdapter>
+ <kahaDB directory="target/activemq-data" lockKeepAlivePeriod="5000">
<locker>
- <!-- When used with the KahaDB persistence adapter the 'dataSource' attribute must be defined on the locker itself: -->
- <lease-database-locker lockAcquireSleepInterval="10000" dataSource="#mysql-ds">
+ <!-- When used with the KahaDB persistence adapter the 'dataSource' attribute must be defined on the locker itself: -->
+ <lease-database-locker lockAcquireSleepInterval="10000" dataSource="#mysql-ds">
<statements>
<!-- Default locker attributes and SQL statements may be overridden here
- using one or more <statements attribute_or_statement="value"/> entries: -->
- <statements lockTableName="activemq_lock"/>
+ using one or more <statements attribute_or_statement="value"/> entries: -->
+ <statements lockTableName="activemq_lock"/>
</statements>
</lease-database-locker>
</locker>
</kahaDB>
-</persistenceAdapter>]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>To see the complete list of attributes and SQL statements that can be overridden see the <a shape="rect" class="external-link" href="https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-jdbc-store/src/main/java/org/apache/activemq/store/jdbc/Statements.java?hb=true" rel="nofollow">Statements</a> class.</p></div></div><p>When the KahaDB persistence adapter is configured to use the <strong><code>lease-database-locker</code></strong> you must configure the broker to use your own IO exception handler as neither the <strong><code>DefaultIOExceptionHandler</code></strong> nor the <strong><code>JDBCIOExceptionHandler</code></strong> will work correctly with this combination. See <a shape="rect" href="configurable-ioexception-handling.xml">Configurable IOException Handlers</a> for details on how to write a handler.</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>As of ActiveMQ 5.11, however, the <strong><code>JDBCIOExceptionHandler</code></strong> has been deprecated. It has been replaced by the <strong><code>org.apache.activemq.util.LeaseLockerIOExceptionHandler</code></strong> that will work with any persistence adapter that supports pluggable storage lockers, regardless if one is configured.</p></div></div><p> </p><p> </p><p> </p><p> </p><p> </p></div>
+</persistenceAdapter></plain-text-body></structured-macro><structured-macro ac:macro-id="fa277709-df06-464d-be9b-6543bb5b45c4" ac:name="info" ac:schema-version="1"><rich-text-body><p>To see the complete list of attributes and SQL statements that can be overridden see the <a shape="rect" href="https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-jdbc-store/src/main/java/org/apache/activemq/store/jdbc/Statements.java?hb=true">Statements</a> class.</p></rich-text-body></structured-macro><p>When the KahaDB persistence adapter is configured to use the <strong><code>lease-database-locker</code></strong> you must configure the broker to use your own IO exception handler as neither the <strong><code>DefaultIOExceptionHandler</code></strong> nor the <strong><code>JDBCIOExceptionHandler</code></strong> will work correctly with this combination. See <link><page ri:content-title="Configurable IOException Handling"></page><plain-text-link-body>Configurable IOException Handlers</plain-text-link-body></link> for details on how to write a handler.</p><structured-macro ac:macro-id="8fef4ccb-7429-438c-9940-91a5320234e6" ac:name="info" ac:schema-version="1"><rich-text-body><p>As of ActiveMQ 5.11, however, the <strong><code>JDBCIOExceptionHandler</code></strong> has been deprecated. It has been replaced by the <strong><code>org.apache.activemq.util.LeaseLockerIOExceptionHandler</code></strong> that will work with any persistence adapter that supports pluggable storage lockers, regardless if one is configured.</p></rich-text-body></structured-macro><p> </p><p> </p><p> </p><p> </p><p> </p></div>
diff --git a/pmc-templates.xml b/pmc-templates.xml
index ff047f2..e6bf0a8 100644
--- a/pmc-templates.xml
+++ b/pmc-templates.xml
@@ -1,29 +1,2 @@
-<div class="wiki-content maincontent"><p>The following email templates are for use by the ActiveMQ PMC: </p><p></p><div class="toc-macro client-side-toc-macro" data-headerelements="H1,H2,H3,H4,H5,H6,H7"></div><h1 id="PMCTemplates-CommitterDiscussion">Committer Discussion</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org<br clear="none"></a>Subject: [DISCUSS] Invite <CANDIDATE> to become an ActiveMQ committer</p><p>Considering <CANDIDATE>’s contributions to the ActiveMQ project...</p><p><INSERT EVIDENCE HERE></p><p>Based on this person's contributions above, I think we should invite <CANDIDATE> to become a committer.</p><p>Please remember that this is not a vote for this person to become a committer, at this point it is only a discussion.</p>
-</div></div><p> </p><h1 id="PMCTemplates-CommitterVote">Committer Vote</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org<br clear="none"></a>Subject: [VOTE] Invite <CANDIDATE> to become an ActiveMQ committer</p><p>After positive discussion about <CANDIDATE>’s contributions to the project, I would like to initiate a formal vote.</p><p>Considering <INSERT EVIDENCE HERE> as raised in the discussion thread...</p><p>This vote will follow the ASF process for committer votes and consensus approval (at least three binding +1 votes and no vetoes)The vote will be open for 72 hours.</p><p>[ ] +1 Accept <CANDIDATE> as a committer of Apache ActiveMQ<br clear="none">[ ] +0<br clear="none">[ ] -1 Do not accept at this time because...</p>
-</div></div><p> </p><h1 id="PMCTemplates-CommitterVoteResult">Committer Vote Result</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org<br clear="none"></a>Subject: [RESULT][VOTE] Invite <CANDIDATE> to become an ActiveMQ committer.</p><p>This vote has been open for <X> days and is now closed with the following results:</p><p>* Number of +1s<br clear="none">* Number of 0s<br clear="none">* Number of -1s</p><p>The vote <passes|does not pass>.</p>
-</div></div><p> </p><h1 id="PMCTemplates-CommitterInvitation">Committer Invitation</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <INVITEE EMAIL><br clear="none">Cc: <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org<br clear="none"></a>Subject: Invitation to become Apache Active committer</p><p>Hello <INVITEE>,</p><p>The Apache ActiveMQ Project Management Committee (PMC) hereby invites you to become committer on the project. These privileges are offered on the understanding that you'll use them reasonably and with common sense. We like to work on trust rather than unnecessary constraints.</p><p>Being a committer enables you to more easily make changes without needing to go through the patch submission process. Although you will be granted commit access to project repositories, you will be expected to adhere to project best practices when committing. The following URL some good resources regarding expectations and processes:</p><p><a shape="rect" class="external-link" href="http://www.apache.org/dev/new-committers-guide.html">http://www.apache.org/dev/new-committers-guide.html</a></p><p>This is a personal invitation for you to accept or decline in private. Please reply to the <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org</a> address only.</p><p>If you accept the invitation, the next step is to register an Individual Contributor License Agreement (ICLA) with the Apache Software Foundation if you have not already. Details of the ICLA and the forma can be found at the following URL:</p><p><a shape="rect" class="external-link" href="http://www.apache.org/licenses/#clas">http://www.apache.org/licenses/#clas</a></p><p>The form provides instructions for its completion and submittal to the Secretary of the ASF.</p><p>When you submit the completed ICLA, please request to notify the Apache ActiveMQ project upon official receipt.Once your ICLA has been acknowledged by the Secretary, you will need to choose a unique ASF ID. You can check to see if your preferred id is already taken by browsing the following list of ASF committers:</p><p><a shape="rect" class="external-link" href="http://people.apache.org/committer-index.html">http://people.apache.org/committer-index.html</a></p><p>When your ICLA is recognized by the Secretary, you will receive a follow-up message with the next steps for establishing you as a committer.</p><p>We look forward to your response!</p>
-</div></div>
-<div class="aui-message contentf-msgbox shadowed aui-message-hint">
- <p class="title">
-
- <span class="aui-icon icon-hint"></span>
- <strong>IMPORTANT</strong>
- </p>
- <p></p><p>Once the prospective committer has accepted the invitation and the ICLA has been acknowledged (check the following URL to be sure it has been submitted: <a shape="rect" class="external-link" href="https://people.apache.org/unlistedclas.html">https://people.apache.org/unlistedclas.html</a>), locate the vote result thread permalink from the private@activemq list can be found using: <a shape="rect" class="external-link" href="https://mail-search.apache.org/">https://mail-search.apache.org/</a> or <a shape="rect" class="external-link" href="https://lists.apache.org/">https://lists.apache.org/</a> (authentication required).</p><p>Upon locating the permalink, use the account request form to request the new ASF user id: <a shape="rect" class="external-link" href="https://id.apache.org/acreq/pmc-chairs">https://id.apache.org/acreq/pmc-chairs</a>  If the name isn't in the list be sure to click the link on the bottom right.</p>
-</div>
-<h1 id="PMCTemplates-CommitterAnnouncement">Committer Announcement</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <a shape="rect" class="external-link" href="mailto:dev@activemq.apache.org" rel="nofollow">dev@activemq.apache.org</a><br clear="none">Subject: [ANNOUNCE] New Apache ActiveMQ Committer <INVITEE></p><p>On behalf of the Apache ActiveMQ PMC, I am very pleased to announce that <INVITEE> has accepted an invitation to become a committer. We greatly appreciate all of <INVITEE>'s hard work and generous contributions to the project. We look forward to <her/his> continued involvement in the project.</p><p>Welcome <INVITEE> and congratulations!</p>
-</div></div><p> </p><h1 id="PMCTemplates-CommiterOnboarding">Commiter Onboarding</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <a shape="rect" class="external-link" href="mailto:private@acctivemq.apache.org" rel="nofollow">private@acctivemq.apache.org</a>, <NEW COMMITTER><br clear="none">Subject: [committer]: What to do now that you're a committer?</p><p><COMMITTER>, the ASF Infrastructure has set up your user account as the '<ASF USER ID>'.</p><p>To learn more about how the ASF works, please visit the following URL and read the items in the 'Committers and Contributors' section:</p><p><a shape="rect" class="external-link" href="https://www.apache.org/dev/#committers">https://www.apache.org/dev/#committers</a></p><p>It is especially important to read through the New Committers Guide at the following URL:</p><p><a shape="rect" class="external-link" href="https://www.apache.org/dev/new-committers-guide.html">https://www.apache.org/dev/new-committers-guide.html</a></p><p>Please ensure that you subscribed to the Apache ActiveMQ Developers mailing list <a shape="rect" class="external-link" href="mailto:dev@activemq.apache.org" rel="nofollow">dev@activemq.apache.org</a>. We also recommend subscribing to the users@ and commits@ mailing lists at <a shape="rect" class="external-link" href="mailto:users@activemq.apache.org" rel="nofollow">users@activemq.apache.org</a> and <a shape="rect" class="external-link" href="mailto:commits@activemq.apache.org" rel="nofollow">commits@activemq.apache.org</a>. Please see the following page for more info about the mailing lists:</p><p><a shape="rect" class="external-link" href="http://activemq.apache.org/mailing-lists.html">http://activemq.apache.org/mailing-lists.html</a><br clear="none"> <br clear="none">To push commits, ensure that you use HTTPS or SSH in your git remotes, or if you've been pulling from a mirror like Github, you'll need to add a remote such as:</p><p><br clear="none"> $ git remote add apache <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq.git">https://git-wip-us.apache.org/repos/asf/activemq.git</a></p><p><br clear="none">If you have any questions please ask on the dev@activemq list.</p>
-</div></div><p> </p><h1 id="PMCTemplates-PMCDiscussion">PMC Discussion</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org<br clear="none"></a>Subject: [DISCUSS] Invite <CANDIDATE> to join ActiveMQ PMC</p><p>Considering <CANDIDATE>’s contributions to the ActiveMQ project as a committer...</p><p><INSERT EVIDENCE HERE></p><p>Based on this person's contributions above, I think we should invite <CANDIDATE> to become a committer.</p><p>Please remember that this is not a vote for this person to become a committer, at this point it is only a discussion.</p>
-</div></div><h1 id="PMCTemplates-PMCVote">PMC Vote</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org</a><br clear="none">Subject: [VOTE] Invite <span><CANDIDATE> </span>to join Apache ActiveMQ PMC</p><p>After positive discussion considering <CANDIDATE>’s contributions as a committer, I would like to initiate a formal vote.</p><p><INSERT EVIDENCE HERE></p><p>This vote will follow the ASF process for committer votes and consensus approval (at least three binding +1 votes and no vetoes)</p><p>The vote will be open for 72 hours.</p><p>[ ] +1 Accept <CANDIDATE> as a PMC member of Apache ActiveMQ<br clear="none">[ ] +0<br clear="none">[ ] -1 Do not accept at this time because...</p>
-</div></div><p> </p><h1 id="PMCTemplates-PMCInvite">PMC Invite</h1><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>To: <INVITEE EMAIL><br clear="none">Cc: <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org</a><br clear="none">Subject: Invitation to join the Apache ActiveMQ PMC</p><p><INVITEE>,<br clear="none">In recognition of your continued contributions to the project, the Apache ActiveMQ PMC has voted to invite you to join the PMC. I am writing on behalf of the PMC to give you the opportunity to either accept or reject this invitation by replying to <a shape="rect" class="external-link" href="mailto:private@activemq.apache.org" rel="nofollow">private@activemq.apache.org</a>.</p><p>In making your decision, please see the following URL for more information on PMCs:</p><p><a shape="rect" class="external-link" href="https://www.apache.org/dev/pmc.html">https://www.apache.org/dev/pmc.html</a></p><p>If you have questions before making a decision, please let us know.</p>
-</div></div></div>
+<div class="wiki-content maincontent"><p>The following email templates are for use by the ActiveMQ PMC: </p><p><structured-macro ac:macro-id="5d00b44d-7927-4c01-8842-8a373f77d24b" ac:name="toc" ac:schema-version="1"></structured-macro></p><h1>Committer Discussion</h1><structured-macro ac:macro-id="d147b9c1-9d75-4d4f-b760-9945c192bed8" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org<br clear="none"></a>Subject: [DISCUSS] Invite <CANDIDATE> to become an ActiveMQ committer</p><p>Considering <CANDIDATE>’s contributions to the ActiveMQ project...</p><p><INSERT EVIDENCE HERE></p><p>Based on this person's contributions above, I think we should invite <CANDIDATE> to become a committer.</p><p>Please remember that this is not a vote for this person to become a committer, at this point it is only a discussion.</p></rich-text-body></structured-macro><p> </p><h1>Committer Vote</h1><structured-macro ac:macro-id="ed4aaec6-1858-4603-b6b8-3cb0c1acea5d" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org<br clear="none"></a>Subject: [VOTE] Invite <CANDIDATE> to become an ActiveMQ committer</p><p>After positive discussion about <CANDIDATE>’s contributions to the project, I would like to initiate a formal vote.</p><p>Considering <INSERT EVIDENCE HERE> as raised in the discussion thread...</p><p>This vote will follow the ASF process for committer votes and consensus approval (at least three binding +1 votes and no vetoes)The vote will be open for 72 hours.</p><p>[ ] +1 Accept <CANDIDATE> as a committer of Apache ActiveMQ<br clear="none">[ ] +0<br clear="none">[ ] -1 Do not accept at this time because...</p></rich-text-body></structured-macro><p> </p><h1>Committer Vote Result</h1><structured-macro ac:macro-id="c1d32f39-ad5d-40ca-9fa5-ea1d71f1e657" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org<br clear="none"></a>Subject: [RESULT][VOTE] Invite <CANDIDATE> to become an ActiveMQ committer.</p><p>This vote has been open for <X> days and is now closed with the following results:</p><p>* Number of +1s<br clear="none">* Number of 0s<br clear="none">* Number of -1s</p><p>The vote <passes|does not pass>.</p></rich-text-body></structured-macro><p> </p><h1>Committer Invitation</h1><structured-macro ac:macro-id="8cc1f42d-1f40-47aa-b8bf-ef40e00aae70" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <INVITEE EMAIL><br clear="none">Cc: <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org<br clear="none"></a>Subject: Invitation to become Apache Active committer</p><p>Hello <INVITEE>,</p><p>The Apache ActiveMQ Project Management Committee (PMC) hereby invites you to become committer on the project. These privileges are offered on the understanding that you'll use them reasonably and with common sense. We like to work on trust rather than unnecessary constraints.</p><p>Being a committer enables you to more easily make changes without needing to go through the patch submission process. Although you will be granted commit access to project repositories, you will be expected to adhere to project best practices when committing. The following URL some good resources regarding expectations and processes:</p><p><a shape="rect" href="http://www.apache.org/dev/new-committers-guide.html">http://www.apache.org/dev/new-committers-guide.html</a></p><p>This is a personal invitation for you to accept or decline in private. Please reply to the <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org</a> address only.</p><p>If you accept the invitation, the next step is to register an Individual Contributor License Agreement (ICLA) with the Apache Software Foundation if you have not already. Details of the ICLA and the forma can be found at the following URL:</p><p><a shape="rect" href="http://www.apache.org/licenses/#clas">http://www.apache.org/licenses/#clas</a></p><p>The form provides instructions for its completion and submittal to the Secretary of the ASF.</p><p>When you submit the completed ICLA, please request to notify the Apache ActiveMQ project upon official receipt.Once your ICLA has been acknowledged by the Secretary, you will need to choose a unique ASF ID. You can check to see if your preferred id is already taken by browsing the following list of ASF committers:</p><p><a shape="rect" href="http://people.apache.org/committer-index.html">http://people.apache.org/committer-index.html</a></p><p>When your ICLA is recognized by the Secretary, you will receive a follow-up message with the next steps for establishing you as a committer.</p><p>We look forward to your response!</p></rich-text-body></structured-macro><structured-macro ac:macro-id="608ed2a9-144d-4f3c-8fa6-475c454ca983" ac:name="auimessage" ac:schema-version="1"><parameter ac:name="title">IMPORTANT</parameter><parameter ac:name="type">hint</parameter><rich-text-body><p>Once the prospective committer has accepted the invitation and the ICLA has been acknowledged (check the following URL to be sure it has been submitted: <a shape="rect" href="https://people.apache.org/unlistedclas.html">https://people.apache.org/unlistedclas.html</a>), locate the vote result thread permalink from the private@activemq list can be found using: <a shape="rect" class="external-link" href="https://mail-search.apache.org/">https://mail-search.apache.org/</a> or <a shape="rect" href="https://lists.apache.org/">https://lists.apache.org/</a> (authentication required).</p><p>Upon locating the permalink, use the account request form to request the new ASF user id: <a shape="rect" class="external-link" href="https://id.apache.org/acreq/pmc-chairs">https://id.apache.org/acreq/pmc-chairs</a>  If the name isn't in the list be sure to click the link on the bottom right.</p></rich-text-body></structured-macro><h1>Committer Announcement</h1><structured-macro ac:macro-id="d5df4d47-f505-4d53-9535-1b4195f3da97" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <a shape="rect" href="mailto:dev@activemq.apache.org">dev@activemq.apache.org</a><br clear="none">Subject: [ANNOUNCE] New Apache ActiveMQ Committer <INVITEE></p><p>On behalf of the Apache ActiveMQ PMC, I am very pleased to announce that <INVITEE> has accepted an invitation to become a committer. We greatly appreciate all of <INVITEE>'s hard work and generous contributions to the project. We look forward to <her/his> continued involvement in the project.</p><p>Welcome <INVITEE> and congratulations!</p></rich-text-body></structured-macro><p> </p><h1>Commiter Onboarding</h1><structured-macro ac:macro-id="61bf0c7d-b9c9-4cff-8802-768617ae58f8" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <a shape="rect" href="mailto:private@acctivemq.apache.org">private@acctivemq.apache.org</a>, <NEW COMMITTER><br clear="none">Subject: [committer]: What to do now that you're a committer?</p><p><COMMITTER>, the ASF Infrastructure has set up your user account as the '<ASF USER ID>'.</p><p>To learn more about how the ASF works, please visit the following URL and read the items in the 'Committers and Contributors' section:</p><p><a shape="rect" href="https://www.apache.org/dev/#committers">https://www.apache.org/dev/#committers</a></p><p>It is especially important to read through the New Committers Guide at the following URL:</p><p><a shape="rect" href="https://www.apache.org/dev/new-committers-guide.html">https://www.apache.org/dev/new-committers-guide.html</a></p><p>Please ensure that you subscribed to the Apache ActiveMQ Developers mailing list <a shape="rect" href="mailto:dev@activemq.apache.org">dev@activemq.apache.org</a>. We also recommend subscribing to the users@ and commits@ mailing lists at <a shape="rect" href="mailto:users@activemq.apache.org">users@activemq.apache.org</a> and <a shape="rect" href="mailto:commits@activemq.apache.org">commits@activemq.apache.org</a>. Please see the following page for more info about the mailing lists:</p><p><a shape="rect" href="http://activemq.apache.org/mailing-lists.html">http://activemq.apache.org/mailing-lists.html</a><br clear="none"> <br clear="none">To push commits, ensure that you use HTTPS or SSH in your git remotes, or if you've been pulling from a mirror like Github, you'll need to add a remote such as:</p><p><br clear="none"> $ git remote add apache <a shape="rect" href="https://git-wip-us.apache.org/repos/asf/activemq.git">https://git-wip-us.apache.org/repos/asf/activemq.git</a></p><p><br clear="none">If you have any questions please ask on the dev@activemq list.</p></rich-text-body></structured-macro><p> </p><h1>PMC Discussion</h1><structured-macro ac:macro-id="87b2b57b-6652-42e6-9b83-18f6dbaece4a" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org<br clear="none"></a>Subject: [DISCUSS] Invite <CANDIDATE> to join ActiveMQ PMC</p><p>Considering <CANDIDATE>’s contributions to the ActiveMQ project as a committer...</p><p><INSERT EVIDENCE HERE></p><p>Based on this person's contributions above, I think we should invite <CANDIDATE> to become a committer.</p><p>Please remember that this is not a vote for this person to become a committer, at this point it is only a discussion.</p></rich-text-body></structured-macro><h1>PMC Vote</h1><structured-macro ac:macro-id="a221036b-3cf8-43c3-92ab-70329f703618" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org</a><br clear="none">Subject: [VOTE] Invite <span><CANDIDATE> </span>to join Apache ActiveMQ PMC</p><p>After positive discussion considering <CANDIDATE>’s contributions as a committer, I would like to initiate a formal vote.</p><p><INSERT EVIDENCE HERE></p><p>This vote will follow the ASF process for committer votes and consensus approval (at least three binding +1 votes and no vetoes)</p><p>The vote will be open for 72 hours.</p><p>[ ] +1 Accept <CANDIDATE> as a PMC member of Apache ActiveMQ<br clear="none">[ ] +0<br clear="none">[ ] -1 Do not accept at this time because...</p></rich-text-body></structured-macro><p> </p><h1>PMC Invite</h1><structured-macro ac:macro-id="0695afda-45b3-4f04-a588-97d64e1026ef" ac:name="panel" ac:schema-version="1"><rich-text-body><p>To: <INVITEE EMAIL><br clear="none">Cc: <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org</a><br clear="none">Subject: Invitation to join the Apache ActiveMQ PMC</p><p><INVITEE>,<br clear="none">In recognition of your continued contributions to the project, the Apache ActiveMQ PMC has voted to invite you to join the PMC. I am writing on behalf of the PMC to give you the opportunity to either accept or reject this invitation by replying to <a shape="rect" href="mailto:private@activemq.apache.org">private@activemq.apache.org</a>.</p><p>In making your decision, please see the following URL for more information on PMCs:</p><p><a shape="rect" href="https://www.apache.org/dev/pmc.html">https://www.apache.org/dev/pmc.html</a></p><p>If you have questions before making a decision, please let us know.</p></rich-text-body></structured-macro></div>
diff --git a/privacy-policy.xml b/privacy-policy.xml
index b6db1d7..e37a397 100644
--- a/privacy-policy.xml
+++ b/privacy-policy.xml
@@ -3,7 +3,7 @@
<ol><li>The IP address from which you access the website;</li><li>The type of browser and operating system you use to access our site;</li><li>The date and time you access our site;</li><li>The pages you visit; and</li><li>The addresses of pages from where you followed a link to our site.</li></ol>
-<p>Part of this information is gathered using a tracking cookie set by the <a shape="rect" class="external-link" href="http://www.google.com/analytics/" rel="nofollow">Google Analytics</a> service and handled by Google as described in their <a shape="rect" class="external-link" href="http://www.google.com/privacy.html" rel="nofollow">privacy policy</a>. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.</p>
+<p>Part of this information is gathered using a tracking cookie set by the <a shape="rect" href="http://www.google.com/analytics/">Google Analytics</a> service and handled by Google as described in their <a shape="rect" href="http://www.google.com/privacy.html">privacy policy</a>. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.</p>
<p>We use the gathered information to help us make our site more useful to visitors and to better understand how and when our site is used. We do not track or collect personally identifiable information or associate gathered data with any personally identifying information from other sources.</p>
diff --git a/producer-flow-control.xml b/producer-flow-control.xml
index aec841d..95aed8a 100644
--- a/producer-flow-control.xml
+++ b/producer-flow-control.xml
@@ -1,52 +1,40 @@
-<div class="wiki-content maincontent"><h2 id="ProducerFlowControl-ProducerFlowControl">Producer Flow Control</h2><p>In ActiveMQ 4.x flow control was implemented using TCP flow control. The underlying network connection of throttled consumers was suspended to enforce flow control limits. This strategy is very efficient but can lead to deadlocks if there are multiple producers and consumers sharing the same connection.</p><p>As of ActiveMQ 5.0, we can now individually flow control each producer on a shared connection without having to suspend the entire connection. By 'flow control' we mean that if the broker detects that the memory limit for the destination, or the temp- or file-store limits for the broker, have been exceeded, then the flow of messages can be slowed down. The producer will be either blocked until resources are available <em>or</em> will receive a JMSException: this behaviour is configurable and described in the section below on <code><systemUsage></code>.</p><p>It's worth noting that the default <code><systemUsage></code> settings will cause the producer to <em>block</em> when the <code>memoryLimit</code> or <code><systemUsage></code> limits are reached: this blocking behaviour is sometimes misinterpreted as a 'hung producer', when in fact the producer is simply diligently waiting until space is available.</p><ul><li>Messages that are sent synchronously will automatically use per producer flow control; this applies generally to persistent messages which are sent synchronously <em>unless</em> you enable the <code>useAsyncSend</code> flag.</li></ul><ul><li>Producers that use <a shape="rect" href="async-sends.xml">Async Sends</a> - generally speaking, producers of non-persistent messages - don't bother waiting for any acknowledgement from the broker; so, if a memory limit has been exceeded, you will <em>not</em> get notfied. If you do want to be aware of broker limits being exceeded, you will need to configure the ProducerWindowSize connection option so that even async messages are flow controlled per producer.</li></ul><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ActiveMQConnectionFactory connctionFactory = ...
+<div class="wiki-content maincontent"><h2>Producer Flow Control</h2><p>In ActiveMQ 4.x flow control was implemented using TCP flow control. The underlying network connection of throttled consumers was suspended to enforce flow control limits. This strategy is very efficient but can lead to deadlocks if there are multiple producers and consumers sharing the same connection.</p><p>As of ActiveMQ 5.0, we can now individually flow control each producer on a shared connection without having to suspend the entire connection. By 'flow control' we mean that if the broker detects that the memory limit for the destination, or the temp- or file-store limits for the broker, have been exceeded, then the flow of messages can be slowed down. The producer will be either blocked until resources are available <em>or</em> will receive a JMSException: this behaviour is configurable and described in the section below on <code><systemUsage></code>.</p><p>It's worth noting that the default <code><systemUsage></code> settings will cause the producer to <em>block</em> when the <code>memoryLimit</code> or <code><systemUsage></code> limits are reached: this blocking behaviour is sometimes misinterpreted as a 'hung producer', when in fact the producer is simply diligently waiting until space is available.</p><ul><li>Messages that are sent synchronously will automatically use per producer flow control; this applies generally to persistent messages which are sent synchronously <em>unless</em> you enable the <code>useAsyncSend</code> flag.</li></ul><ul><li>Producers that use <link><page ri:content-title="Async Sends"></page></link> - generally speaking, producers of non-persistent messages - don't bother waiting for any acknowledgement from the broker; so, if a memory limit has been exceeded, you will <em>not</em> get notfied. If you do want to be aware of broker limits being exceeded, you will need to configure the ProducerWindowSize connection option so that even async messages are flow controlled per producer.</li></ul><structured-macro ac:macro-id="81758a12-e709-4add-8394-366b2ed46dae" ac:name="code" ac:schema-version="1"><plain-text-body>ActiveMQConnectionFactory connctionFactory = ...
connctionFactory.setProducerWindowSize(1024000);
-]]></script>
-</div></div><p>The ProducerWindowSize is the maximum number of bytes of data that a producer will transmit to a broker before waiting for acknowledgment messages from the broker that it has accepted the previously sent messages.</p><p>Alternatively, if you're sending non-persisted messages (which are by default sent async), and want to be informed if the queue or topic's memory limit has been breached, then you can simply configure the connection factory to 'alwaysSyncSend'. While this is going to be slower, it will ensure that your message producer is informed immediately of memory issues.</p><p>If you like, you can disable flow control for specific JMS queues and topics on the broker by setting the <code>producerFlowControl</code> flag to false on the appropriate destination policy in the Broker configuration - e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<destinationPolicy>
+</plain-text-body></structured-macro><p>The ProducerWindowSize is the maximum number of bytes of data that a producer will transmit to a broker before waiting for acknowledgment messages from the broker that it has accepted the previously sent messages.</p><p>Alternatively, if you're sending non-persisted messages (which are by default sent async), and want to be informed if the queue or topic's memory limit has been breached, then you can simply configure the connection factory to 'alwaysSyncSend'. While this is going to be slower, it will ensure that your message producer is informed immediately of memory issues.</p><p>If you like, you can disable flow control for specific JMS queues and topics on the broker by setting the <code>producerFlowControl</code> flag to false on the appropriate destination policy in the Broker configuration - e.g.</p><structured-macro ac:macro-id="25a71a92-ce5b-48c5-b53f-b867a8efc000" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry topic="FOO.>" producerFlowControl="false"/>
+ <policyEntry topic="FOO.>" producerFlowControl="false"/>
</policyEntries>
</policyMap>
</destinationPolicy>
-]]></script>
-</div></div><p>see <a shape="rect" href="xml-configuration.xml">Broker Configuration</a>.</p><p>Note that, since the introduction of the new file cursor in ActiveMQ 5.x, non-persisted messages are shunted into the temporary file store to reduce the amount of memory used for non-persistent messaging. As a result, you may find that a queue's memoryLimit is never reached, as the cursor doesn't use very much memory. If you really do want to keep all your non-persistent messages in memory, and stop producers when the limit is reached, you should configure the <code><vmQueueCursor></code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
+</plain-text-body></structured-macro><p>see <link><page ri:content-title="Xml Configuration"></page><plain-text-link-body>Broker Configuration</plain-text-link-body></link>.</p><p>Note that, since the introduction of the new file cursor in ActiveMQ 5.x, non-persisted messages are shunted into the temporary file store to reduce the amount of memory used for non-persistent messaging. As a result, you may find that a queue's memoryLimit is never reached, as the cursor doesn't use very much memory. If you really do want to keep all your non-persistent messages in memory, and stop producers when the limit is reached, you should configure the <code><vmQueueCursor></code>.</p><structured-macro ac:macro-id="e0611bd3-5d45-4ea5-a794-2e753cc20011" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><policyEntry queue=">" producerFlowControl="true" memoryLimit="1mb">
<pendingQueuePolicy>
<vmQueueCursor/>
</pendingQueuePolicy>
</policyEntry>
-]]></script>
-</div></div><p>The fragment above will ensure that all non-persistent queue messages are kept in memory, with each queue having a limit of 1Mb.</p><h3 id="ProducerFlowControl-HowProducerFlowControlworks">How Producer Flow Control works</h3><p>If you are sending a persistent message (so that a response of the <a shape="rect" href="openwire.xml">OpenWire</a> Message is expected then the broker will send the producer a <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.9.0/apidocs/index.html">ProducerAck</a> message. This informs the producer that the previous sending window has been processed, so that it can now send another window. Its kinda like consumer acks but in reverse.</p><h4 id="ProducerFlowControl-Advantage">Advantage</h4><p>So a nice producer might wait for a producer ack before sending more data, to avoid flooding the broker (and forcing the broker to block the entire connection if a slow consumer occurs). To see how this works in source code, check out the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.9.0/apidocs/index.html">ActiveMQMessageProducer</a> code.</p><p>Though a client can ignore the producer ACKs altogether and the broker should just stall the transport if it has to for slow consumer handling; though this does mean it'll stall the entire connection.</p><h3 id="ProducerFlowControl-ConfigureClient-SideExceptions">Configure Client-Side Exceptions</h3><p>An alternative to the indefinite blocking of the <code>send()</code> operation when no space is free on the broker is to instead configure that an exception to be thrown on the client-side. By configuring the <code>sendFailIfNoSpace</code> property to <code>true</code>, the broker will cause the <code>send()</code> operation to fail with a <code>javax.jms.ResourceAllocationException</code>, which will propagate to the client. Below is an example of this configuration:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<systemUsage>
- <systemUsage sendFailIfNoSpace="true">
+</plain-text-body></structured-macro><p>The fragment above will ensure that all non-persistent queue messages are kept in memory, with each queue having a limit of 1Mb.</p><h3>How Producer Flow Control works</h3><p>If you are sending a persistent message (so that a response of the <link><page ri:content-title="OpenWire"></page></link> Message is expected then the broker will send the producer a <a shape="rect" href="http://activemq.apache.org/maven/5.9.0/apidocs/index.html">ProducerAck</a> message. This informs the producer that the previous sending window has been processed, so that it can now send another window. Its kinda like consumer acks but in reverse.</p><h4>Advantage</h4><p>So a nice producer might wait for a producer ack before sending more data, to avoid flooding the broker (and forcing the broker to block the entire connection if a slow consumer occurs). To see how this works in source code, check out the <a shape="rect" href="http://activemq.apache.org/maven/5.9.0/apidocs/index.html">ActiveMQMessageProducer</a> code.</p><p>Though a client can ignore the producer ACKs altogether and the broker should just stall the transport if it has to for slow consumer handling; though this does mean it'll stall the entire connection.</p><h3>Configure Client-Side Exceptions</h3><p>An alternative to the indefinite blocking of the <code>send()</code> operation when no space is free on the broker is to instead configure that an exception to be thrown on the client-side. By configuring the <code>sendFailIfNoSpace</code> property to <code>true</code>, the broker will cause the <code>send()</code> operation to fail with a <code>javax.jms.ResourceAllocationException</code>, which will propagate to the client. Below is an example of this configuration:</p><structured-macro ac:macro-id="b109dd0a-ab99-4851-9352-a12dc64d7ef7" ac:name="code" ac:schema-version="1"><plain-text-body><systemUsage>
+ <systemUsage sendFailIfNoSpace="true">
<memoryUsage>
- <memoryUsage limit="20 mb"/>
+ <memoryUsage limit="20 mb"/>
</memoryUsage>
</systemUsage>
-</systemUsage>]]></script>
-</div></div><p>The advantage of this property is that the client can catch the <code>javax.jms.ResourceAllocationException</code>, wait a bit and retry the <code>send()</code> operation instead of just hanging indefinitely.</p><p>Starting in version 5.3.1 the <code>sendFailIfNoSpaceAfterTimeout</code> property has been added. This property causes the <code>send()</code> operation to fail with an exception on the client-side, but only after waiting the given amount of time. If space on the broker is still not freed after the configured amount of time, only then does the <code>send()</code> operation fail with an exception to the client-side. Below is an example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<systemUsage>
- <systemUsage sendFailIfNoSpaceAfterTimeout="3000">
+</systemUsage></plain-text-body></structured-macro><p>The advantage of this property is that the client can catch the <code>javax.jms.ResourceAllocationException</code>, wait a bit and retry the <code>send()</code> operation instead of just hanging indefinitely.</p><p>Starting in version 5.3.1 the <code>sendFailIfNoSpaceAfterTimeout</code> property has been added. This property causes the <code>send()</code> operation to fail with an exception on the client-side, but only after waiting the given amount of time. If space on the broker is still not freed after the configured amount of time, only then does the <code>send()</code> operation fail with an exception to the client-side. Below is an example:</p><structured-macro ac:macro-id="3633fe45-9e7f-445f-bc4d-0b644c1563d1" ac:name="code" ac:schema-version="1"><plain-text-body><systemUsage>
+ <systemUsage sendFailIfNoSpaceAfterTimeout="3000">
<memoryUsage>
- <memoryUsage limit="20 mb"/>
+ <memoryUsage limit="20 mb"/>
</memoryUsage>
</systemUsage>
-</systemUsage>]]></script>
-</div></div><p>The timeout is defined in milliseconds so the example above waits for three seconds before failing the <code>send()</code> operation with an exception to the client-side. The advantage of this property is that it will block for the configured amount of time instead of failing immediately or blocking indefinitely. This property offers not only an improvement on the broker-side, but also an improvement for the client so it can catch the exception, wait a bit and retry the <code>send()</code> operation.</p><p>Starting in version 5.16.0 the <code>sendFailIfNoSpace</code> and <span><code>sendFailIfNoSpaceAfterTimeout</code> can be configured on a per destination basis via <a shape="rect" href="per-destination-policies.xml">destination policies</a>.</span></p><h2 id="ProducerFlowControl-DisablingFlowControl">Disabling Flow Control</h2><p>A common requirement is to disable flow control so that message dispatching continues until all available disk is used up by pending messages (whether persistent or non persistent messaging is configured). To do this enable <a shape="rect" href="message-cursors.xml">Message Cursors</a>.</p><h2 id="ProducerFlowControl-Systemusage">System usage</h2><p>You can also slow down producers via some attributes on the <code><systemUsage></code> element. Take a look at the following example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<systemUsage>
+</systemUsage></plain-text-body></structured-macro><p>The timeout is defined in milliseconds so the example above waits for three seconds before failing the <code>send()</code> operation with an exception to the client-side. The advantage of this property is that it will block for the configured amount of time instead of failing immediately or blocking indefinitely. This property offers not only an improvement on the broker-side, but also an improvement for the client so it can catch the exception, wait a bit and retry the <code>send()</code> operation.</p><p>Starting in version 5.16.0 the <code>sendFailIfNoSpace</code> and <span><code>sendFailIfNoSpaceAfterTimeout</code> can be configured on a per destination basis via <link><page ri:content-title="Per Destination Policies"></page><plain-text-link-body>destination policies</plain-text-link-body></link>.</span></p><h2>Disabling Flow Control</h2><p>A common requirement is to disable flow control so that message dispatching continues until all available disk is used up by pending messages (whether persistent or non persistent messaging is configured). To do this enable <link><page ri:content-title="Message Cursors"></page></link>.</p><h2>System usage</h2><p>You can also slow down producers via some attributes on the <code><systemUsage></code> element. Take a look at the following example:</p><structured-macro ac:macro-id="69f65235-7613-462c-81a2-7b9cb20474c0" ac:name="code" ac:schema-version="1"><plain-text-body><systemUsage>
<systemUsage>
<memoryUsage>
- <memoryUsage limit="64 mb" />
+ <memoryUsage limit="64 mb" />
</memoryUsage>
<storeUsage>
- <storeUsage limit="100 gb" />
+ <storeUsage limit="100 gb" />
</storeUsage>
<tempUsage>
- <tempUsage limit="10 gb" />
+ <tempUsage limit="10 gb" />
</tempUsage>
</systemUsage>
-</systemUsage>]]></script>
-</div></div><p>You can set limits of memory for <code>NON_PERSISTENT</code> messages, disk storage for <code>PERSITENT</code> messages and total usage for temporary messages, the broker will use before it slowdown producers. <em>Using the default settings shown above, the broker will block the <code>send()</code> call until some messages are consumed and space becomes available on the broker.</em> The default values are shown above, you will probably need to increase these values for your environment.</p><p><span style="color: rgb(102,0,51);">PercentUsage</span></p><p> Both StoreUsage and TempUsage support a percentLimit attribute where the limit is determined as a percentage of the total available. From version 5.15.x there is an additional related total attribute that can be used to explicitly set the total available such that the file system is not queried. This is useful in the case that only part of a disk partition is available to the broker or where the underlying file store reports > Long.MAX_VALUE available capacity (e.g: EFS) which will overflow the long return value of <a shape="rect" class="external-link" href="http://java.io" rel="nofollow">java.io</a>.File#getTotalSpace. Note that when a total is specified, that actual data available will not be validated agains the file system, just the store usage relative to that absolute total.</p></div>
+</systemUsage></plain-text-body></structured-macro><p>You can set limits of memory for <code>NON_PERSISTENT</code> messages, disk storage for <code>PERSITENT</code> messages and total usage for temporary messages, the broker will use before it slowdown producers. <em>Using the default settings shown above, the broker will block the <code>send()</code> call until some messages are consumed and space becomes available on the broker.</em> The default values are shown above, you will probably need to increase these values for your environment.</p><p><span style="color: rgb(102,0,51);">PercentUsage</span></p><p> Both StoreUsage and TempUsage support a percentLimit attribute where the limit is determined as a percentage of the total available. From version 5.15.x there is an additional related total attribute that can be used to explicitly set the total available such that the file system is not queried. This is useful in the case that only part of a disk partition is available to the broker or where the underlying file store reports > Long.MAX_VALUE available capacity (e.g: EFS) which will overflow the long return value of <a shape="rect" href="http://java.io">java.io</a>.File#getTotalSpace. Note that when a total is specified, that actual data available will not be validated agains the file system, just the store usage relative to that absolute total.</p></div>
diff --git a/projects-using-activemq.xml b/projects-using-activemq.xml
index 983238c..0040a46 100644
--- a/projects-using-activemq.xml
+++ b/projects-using-activemq.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Apache Camel</a> is a POJO based routing and mediation framework</li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/cxf/">Apache CXF</a> is a JAX-WS client and web services framework</li><li><a shape="rect" class="external-link" href="http://geronimo.apache.org/">Apache Geronimo</a> is the J2EE server project of the Apache Software Foundation.</li><li><a shape="rect" class="external-link" href="http://incubator.apache.org/servicemix/">Apache ServiceMix</a> an open source Enterprise Service Bus (ESB) based around the Java Business Integration specification (JSR 208). ServiceMix consists of a JBI container and component suite, massive <a shape="rect" class="external-link" href="http://incubator.apache.org/servicemix/Components">connectivity</a> with complete integration with Spring and Geronimo as well as supporting straight through, SEDA and clustered message flows, smart routing and transformations and orchestration via BPEL.</li><li><a shape="rect" class="external-link" href="http://portals.apache.org/jetspeed-2/">Apache Jetspeed</a> is the Apache enterprise portal.</li><li><a shape="rect" class="external-link" href="http://directory.apache.org/">Apache Directory</a> is the Apache LDAP and Directory services project.</li><li><a shape="rect" class="external-link" href="http://openejb.apache.org">Apache TomEE</a> ActiveMQ is the default JMS provider.</li><li><a shape="rect" class="external-link" href="http://lingo.codehaus.org/" rel="nofollow">Lingo</a> a remoting framework for <a shape="rect" class="external-link" href="http://www.springframework.org/" rel="nofollow">Spring</a> which use JMS and ActiveMQ by default.</li><li><a shape="rect" class="external-link" href="http://www.eclipse.org/" rel="nofollow">Eclipse</a> is integrating ActiveMQ into the real time editing features for team development</li><li><a shape="rect" class="external-link" href="http://activecluster.codehaus.org/" rel="nofollow">ActiveCluster</a> is a clustering API with an implementation which uses JMS and ActiveMQ by default.</li><li><a shape="rect" class="external-link" href="http://activesoap.codehaus.org/" rel="nofollow">ActiveSOAP</a> is a lightweight and fast SOAP stack with pluggable transports</li><li><a shape="rect" class="external-link" href="http://www.open-im.net/en/" rel="nofollow">OpenIM Java Jabber ® Server</a> is an open-source Java implementation (BSD License) of Jabber Instant Messager</li><li><a shape="rect" class="external-link" href="http://mule.codehaus.org/" rel="nofollow">Mule</a> is an Enterprise Service Bus (ESB) messaging framework. It is a scalable, highly distributable object broker that can seamlessly handle interactions with services and applications using disparate transport and messaging technologies.</li><li><a shape="rect" class="external-link" href="http://planb.cloudnine.net.nz/" rel="nofollow">plan/b</a> a distributed backup system</li><li><a shape="rect" class="external-link" href="http://www.hermesjms.com/" rel="nofollow">Hermes</a> is a Swing application that allows you to interact with JMS providers. Hermes will work with any JMS enabled transport making it easy to browse or seach queues and topics, copy (via drag and drop) messages and delete them.</li><li><a shape="rect" class="external-link" href="http://sourceforge.net/projects/springside/" rel="nofollow">SpringSide</a> Pragmatic Enterprise Application KickStart and Common Library Stack. Use Spring Framework as core,provided a enterprise application develop platform and demo the best practice in enterprise application.</li></ul></div>
+<div class="wiki-content maincontent"><ul><li><a shape="rect" href="http://activemq.apache.org/camel/">Apache Camel</a> is a POJO based routing and mediation framework</li><li><a shape="rect" href="http://incubator.apache.org/cxf/">Apache CXF</a> is a JAX-WS client and web services framework</li><li><a shape="rect" href="http://geronimo.apache.org/">Apache Geronimo</a> is the J2EE server project of the Apache Software Foundation.</li><li><a shape="rect" href="http://incubator.apache.org/servicemix/">Apache ServiceMix</a> an open source Enterprise Service Bus (ESB) based around the Java Business Integration specification (JSR 208). ServiceMix consists of a JBI container and component suite, massive <a shape="rect" href="http://incubator.apache.org/servicemix/Components">connectivity</a> with complete integration with Spring and Geronimo as well as supporting straight through, SEDA and clustered message flows, smart routing and transformations and orchestration via BPEL.</li><li><a shape="rect" href="http://portals.apache.org/jetspeed-2/">Apache Jetspeed</a> is the Apache enterprise portal.</li><li><a shape="rect" href="http://directory.apache.org/">Apache Directory</a> is the Apache LDAP and Directory services project.</li><li><a shape="rect" href="http://openejb.apache.org">Apache TomEE</a> ActiveMQ is the default JMS provider.</li><li><a shape="rect" href="http://lingo.codehaus.org/">Lingo</a> a remoting framework for <a shape="rect" href="http://www.springframework.org/">Spring</a> which use JMS and ActiveMQ by default.</li><li><a shape="rect" href="http://www.eclipse.org/">Eclipse</a> is integrating ActiveMQ into the real time editing features for team development</li><li><a shape="rect" href="http://activecluster.codehaus.org/">ActiveCluster</a> is a clustering API with an implementation which uses JMS and ActiveMQ by default.</li><li><a shape="rect" href="http://activesoap.codehaus.org/">ActiveSOAP</a> is a lightweight and fast SOAP stack with pluggable transports</li><li><a shape="rect" href="http://www.open-im.net/en/">OpenIM Java Jabber ® Server</a> is an open-source Java implementation (BSD License) of Jabber Instant Messager</li><li><a shape="rect" href="http://mule.codehaus.org/">Mule</a> is an Enterprise Service Bus (ESB) messaging framework. It is a scalable, highly distributable object broker that can seamlessly handle interactions with services and applications using disparate transport and messaging technologies.</li><li><a shape="rect" href="http://planb.cloudnine.net.nz/">plan/b</a> a distributed backup system</li><li><a shape="rect" href="http://www.hermesjms.com/">Hermes</a> is a Swing application that allows you to interact with JMS providers. Hermes will work with any JMS enabled transport making it easy to browse or seach queues and topics, copy (via drag and drop) messages and delete them.</li><li><a shape="rect" href="http://sourceforge.net/projects/springside/">SpringSide</a> Pragmatic Enterprise Application KickStart and Common Library Stack. Use Spring Framework as core,provided a enterprise application develop platform and demo the best practice in enterprise application.</li></ul>
+</div>
diff --git a/proposed-c-client-architecture.xml b/proposed-c-client-architecture.xml
index a05fa0d..7f55f1e 100644
--- a/proposed-c-client-architecture.xml
+++ b/proposed-c-client-architecture.xml
@@ -3,7 +3,7 @@
<p>/////////////////////////////////////////////// </p>
-<p>Given that there are several separate efforts going on now toward the common goal of creating an ActiveMQ c++ client, I've put together a <a shape="rect" class="external-link" href="http://docs.codehaus.org/download/attachments/48149/ActiveMQClientArchitecture.pdf" rel="nofollow">doc</a>that attempts to merge our complete set of goals and propose an architecture (in rough form) that meets those goals.  I've stored the document here because it was too large for the distribution list.</p>
+<p>Given that there are several separate efforts going on now toward the common goal of creating an ActiveMQ c++ client, I've put together a <a shape="rect" href="http://docs.codehaus.org/download/attachments/48149/ActiveMQClientArchitecture.pdf">doc</a>that attempts to merge our complete set of goals and propose an architecture (in rough form) that meets those goals.  I've stored the document here because it was too large for the distribution list.</p>
<p> Please review and provide feedback at your earliest convenience.</p>
diff --git a/protocols.xml b/protocols.xml
index 053e6bc..a113392 100644
--- a/protocols.xml
+++ b/protocols.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>Apache ActiveMQ is a message broker which supports multiple wire level protocols for maximum interoperability.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="amqp.xml">AMQP</a></li><li><a shape="rect" href="auto.xml">AUTO</a></li><li><a shape="rect" href="mqtt.xml">MQTT</a></li><li><a shape="rect" href="openwire.xml">OpenWire</a></li><li><a shape="rect" href="rest.xml">REST</a></li><li><a shape="rect" href="rss-and-atom.xml">RSS and Atom</a></li><li><a shape="rect" href="stomp.xml">Stomp</a></li><li><a shape="rect" href="wsif.xml">WSIF</a></li><li><a shape="rect" href="ws-notification.xml">WS Notification</a></li><li><a shape="rect" href="xmpp.xml">XMPP</a></li></ul></div>
+<structured-macro ac:macro-id="e08eb648-e2c7-4225-bfa7-fd7fb21abc44" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/pure-master-slave.xml b/pure-master-slave.xml
index 319c437..2cb160d 100644
--- a/pure-master-slave.xml
+++ b/pure-master-slave.xml
@@ -1,13 +1,13 @@
-<div class="wiki-content maincontent"><h3 id="PureMasterSlave-PureMasterSlave">Pure Master Slave</h3>
+<div class="wiki-content maincontent"><h3>Pure Master Slave</h3>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">This feature has been deprecated and will be removed in version 5.8</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<structured-macro ac:macro-id="0544b78d-ffad-4680-9079-1628602e06d0" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">This feature has been deprecated and will be removed in version 5.8</parameter><rich-text-body>
<p>This feature will be removed in 5.8 as it has not evolved to be production ready. <br clear="none">
-You are advised to use <a shape="rect" href="masterslave.xml">shared storage master/slave</a> or the <a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a>.<br clear="none">
-See <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4165">AMQ-4165</a></p></div></div>
+You are advised to use <link><page ri:content-title="MasterSlave"></page><link-body>shared storage master/slave</link-body></link> or the <link><page ri:content-title="Replicated LevelDB Store"></page></link>.<br clear="none">
+See <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-4165">AMQ-4165</a></p></rich-text-body></structured-macro>
<p>A Pure Master Slave configuration provides a basic shared nothing, fully replicated topology which does not depend on a shared file system or shared database. </p>
-<h3 id="PureMasterSlave-HowPureMasterSlaveworks">How Pure Master Slave works</h3>
+<h3>How Pure Master Slave works</h3>
<ul><li>A slave of a master broker consumes all message states from the master - messages, acknowledgments and transactional states.<br clear="none">
Whilst a Slave is actively connected to the Master - it does not allow or start any network or transport connectors, it's sole purpose is to duplicate the state of the master.</li></ul>
@@ -25,64 +25,58 @@
<ul><li>clients should use a failover transport for connecting to the master broker first and then the slave. e.g. using a URL such as</li></ul>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5658a66f-188d-45ed-bdbd-570413b97b5a" ac:name="code" ac:schema-version="1"><plain-text-body>
failover://(tcp://masterhost:61616,tcp://slavehost:61616)?randomize=false
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The <strong>randomize</strong> property just disables randomness so that the transport will always try the master first, then the slave if it can't connect to that. Note that the slave does not accept connections until it becomes the master</p>
-<h3 id="PureMasterSlave-LimitationsofPureMasterSlave">Limitations of Pure Master Slave</h3>
+<h3>Limitations of Pure Master Slave</h3>
<ul><li>Only one slave can be connected to the Master</li><li>A failed master cannot be re-introduced without shutting down the the slave broker (no automatic failback)</li><li>There is no automatic synchronization between brokers. This is a manual process.</li></ul>
-<h3 id="PureMasterSlave-RecoveringaPureMasterSlavetopology">Recovering a Pure Master Slave topology</h3>
+<h3>Recovering a Pure Master Slave topology</h3>
<p>This is a manual process - once a master has failed, the only sure way to ensure that the toplogy is synchronized again is manually:</p>
<ul><li>shutdown the slave broker (The clients do not need to be shutdown - they will wait until the topology is re-established if they are failover clients</li><li>copy the data directory from the slave over the data directory of the master broker</li><li>re-start the master and the slave</li></ul>
-<h3 id="PureMasterSlave-ConfiguringPureMasterSlave">Configuring Pure Master Slave</h3>
+<h3>Configuring Pure Master Slave</h3>
-<div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>You should not configure a connection between the master and a slave. The connection is automatically established with the slave's configuration. If you explicitly configure a network connection, you may encounter race conditions when the master broker is under heavy load.</p></div></div>
+<structured-macro ac:macro-id="05b329fe-8c42-457b-9bd0-892806596141" ac:name="note" ac:schema-version="1"><rich-text-body>
+<p>You should not configure a connection between the master and a slave. The connection is automatically established with the slave's configuration. If you explicitly configure a network connection, you may encounter race conditions when the master broker is under heavy load.</p></rich-text-body></structured-macro>
<p>A master broker doesn't need any special configuration - it's a normal broker until a slave broker attaches itself.<br clear="none">
-To identify a broker as a slave - there is just one property to set (see below) as this <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/broker/ft/slave2.xml">example shows</a> - so configuration is nice and easy:</p>
+To identify a broker as a slave - there is just one property to set (see below) as this <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/broker/ft/slave2.xml">example shows</a> - so configuration is nice and easy:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker masterConnectorURI="tcp://masterhost:62001" shutdownOnMasterFailure="false">
+<structured-macro ac:macro-id="1ecdcc54-02a6-4304-9dde-a99ea9f9f912" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<broker masterConnectorURI="tcp://masterhost:62001" shutdownOnMasterFailure="false">
<persistenceAdapter>
- <journaledJDBC journalLogFiles="5" dataDirectory="${activemq.base}/data/broker2" />
+ <journaledJDBC journalLogFiles="5" dataDirectory="${activemq.base}/data/broker2" />
</persistenceAdapter>
<transportConnectors>
- <transportConnector uri="tcp://slavehost:61616"/>
+ <transportConnector uri="tcp://slavehost:61616"/>
</transportConnectors>
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Broker Property </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> default </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> masterConnectorURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> URI to the master broker e.g. <strong><em>tcp://masterhost:62001</em></strong> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> shutdownOnMasterFailure </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> if true, the slave will shut down if the master fails otherwise the slave will take over as being the new master. The slave ensures that there is a separate copy of each message and acknowledgement on another machine which can protect against catastrophic hardware failure. If the master fails you might want the slave to shut down as well as you may always want to duplicate messages to 2 physical locations to prevent message loss on catastrophic data centre or hardware failure. If you would rather the system keep on running after a master failure then leave this flag as false. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>waitForSlave</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> version 5.2+, if true, a master will wait till a slave has attached before completing its startup sequence</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>shutdownOnSlaveFailure</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> version 5.2+, if true, a master will shutdown if the slave connection is lost, ensuring that the master will not become out of sync with the slave.</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Broker Property </p></th><th colspan="1" rowspan="1"><p> default </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> masterConnectorURI </p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> URI to the master broker e.g. <strong><em>tcp://masterhost:62001</em></strong> </p></td></tr><tr><td colspan="1" rowspan="1"><p> shutdownOnMasterFailure </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> if true, the slave will shut down if the master fails otherwise the slave will take over as being the new master. The slave ensures that there is a separate copy of each message and acknowledgement on another machine which can protect against catastrophic hardware failure. If the master fails you might want the slave to shut down as well as you may always want to duplicate messages to 2 physical locations to prevent message loss on catastrophic data centre or hardware failure. If you would rather the system keep on running after a master failure then leave this flag as false. </p></td></tr><tr><td colspan="1" rowspan="1"><p>waitForSlave</p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> version 5.2+, if true, a master will wait till a slave has attached before completing its startup sequence</p></td></tr><tr><td colspan="1" rowspan="1"><p>shutdownOnSlaveFailure</p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> version 5.2+, if true, a master will shutdown if the slave connection is lost, ensuring that the master will not become out of sync with the slave.</p></td></tr></tbody></table>
-<h3 id="PureMasterSlave-ConfiguringtheauthenticationoftheSlave">Configuring the authentication of the Slave</h3>
+<h3>Configuring the authentication of the Slave</h3>
-<p>In ActiveMQ 4.1 or later you can use a <strong><masterConnector/></strong> element as an alternative XML configuration mechanism as shown in the following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/broker/ft/slave2.xml">example</a> to configure the user and password that the slave will use to connect to the master</p>
+<p>In ActiveMQ 4.1 or later you can use a <strong><masterConnector/></strong> element as an alternative XML configuration mechanism as shown in the following <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/resources/org/apache/activemq/broker/ft/slave2.xml">example</a> to configure the user and password that the slave will use to connect to the master</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker brokerName="slave" useJmx="false" deleteAllMessagesOnStartup="true" xmlns="http://activemq.apache.org/schema/core">
+<structured-macro ac:macro-id="a13054a4-7af8-43ff-8a58-8b9c4611b433" ac:name="code" ac:schema-version="1"><plain-text-body>
+<broker brokerName="slave" useJmx="false" deleteAllMessagesOnStartup="true" xmlns="http://activemq.apache.org/schema/core">
<services>
- <masterConnector remoteURI= "tcp://localhost:62001" userName="James" password="Cheese"/>
+ <masterConnector remoteURI= "tcp://localhost:62001" userName="James" password="Cheese"/>
</services>
<transportConnectors>
- <transportConnector uri="tcp://localhost:62002"/>
+ <transportConnector uri="tcp://localhost:62002"/>
</transportConnectors>
</broker>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/quicklinks.xml b/quicklinks.xml
index 7dbf8d5..f91a01d 100644
--- a/quicklinks.xml
+++ b/quicklinks.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><a shape="rect" href="download.xml">Download</a> | <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/index.html">JavaDocs</a> <a shape="rect" href="javadocs.xml">More...</a> | <a shape="rect" href="source.xml">Source</a> | <a shape="rect" href="discussion-forums.xml">Forums</a> | <a shape="rect" href="support.xml">Support</a></p></div>
+<div class="wiki-content maincontent"><p><link><page ri:content-title="Download"></page></link> | <a shape="rect" href="http://activemq.apache.org/maven/apidocs/index.html">JavaDocs</a> <link><page ri:content-title="JavaDocs"></page><plain-text-link-body>More...</plain-text-link-body></link> | <link><page ri:content-title="Source"></page></link> | <link><page ri:content-title="Discussion Forums"></page><plain-text-link-body>Forums</plain-text-link-body></link> | <link><page ri:content-title="Support"></page></link></p></div>
diff --git a/redelivery-policy.xml b/redelivery-policy.xml
index 7d23601..26d774f 100644
--- a/redelivery-policy.xml
+++ b/redelivery-policy.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="RedeliveryPolicy-RedeliveryPolicy">Redelivery Policy</h2><p>Detail on when messages are redelivered to a client can be found in the <a shape="rect" href="message-redelivery-and-dlq-handling.xml">Message Redelivery and DLQ Handling</a> section. You can configure the <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup">RedeliveryPolicy</a> on your <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQConnectionFactory.java?view=markup">ActiveMQConnectionFactory</a> or <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQConnection.java?view=markup">ActiveMQConnection</a> to customize exactly how you want the redelivery to work.</p><p>You can use Java code, Spring or the <a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a> to customize this.</p><h3 id="RedeliveryPolicy-AvailableProperties">Available Properties</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Property</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><code>backOffMultiplier</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The back-off multiplier.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>collisionAvoidanceFactor</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0.15</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The percentage of range of collision avoidance if enabled.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>initialRedeliveryDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000L</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The initial redelivery delay in milliseconds.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maximumRedeliveries</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>6</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the maximum number of times a message will be redelivered before it is considered a <strong>poisoned pill</strong> and returned to the broker so it can go to a Dead Letter Queue.</p><p>Set to <strong><code>-1</code></strong> for unlimited redeliveries.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maximumRedeliveryDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>-1</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the maximum delivery delay that will be applied if the <strong><code>useExponentialBackOff</code></strong> option is set. (use value <strong><code>-1</code></strong> to define that no maximum be applied) (<span style="color: red;">v5.5</span>).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>redeliveryDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000L</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The delivery delay if <strong><code>initialRedeliveryDelay=0</code></strong> (<span style="color: red;">v5.4</span>).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useCollisionAvoidance</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should the redelivery policy use collision avoidance.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useExponentialBackOff</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should exponential back-off be used, i.e., to exponentially increase the timeout.</p></td></tr></tbody></table></div><h2 id="RedeliveryPolicy-RedeliveryPolicyperDestination">RedeliveryPolicy per Destination</h2><p>As of ActiveMQ v5.7.0 you can now configure a <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup">RedeliveryPolicy</a> on a per-destination bases. The <strong><code>ActiveMQConnection</code></strong> factory class now exposes a <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/broker/region/policy/RedeliveryPolicyMap.java?view=markup">RedeliveryPolicyMap</a> property that allows to assign a RedeliveryPolicy using named destinations or using destination wildcards. The code snipped below shows how to configure a different <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup">RedeliveryPolicy</a> for Topics and Queues.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ ActiveMQConnection connection ... // Create a connection
+<div class="wiki-content maincontent"><h2>Redelivery Policy</h2><p>Detail on when messages are redelivered to a client can be found in the <link><page ri:content-title="Message Redelivery and DLQ Handling"></page></link> section. You can configure the <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup">RedeliveryPolicy</a> on your <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQConnectionFactory.java?view=markup">ActiveMQConnectionFactory</a> or <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/ActiveMQConnection.java?view=markup">ActiveMQConnection</a> to customize exactly how you want the redelivery to work.</p><p>You can use Java code, Spring or the <link><page ri:content-title="Connection Configuration URI"></page></link> to customize this.</p><h3>Available Properties</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Property</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>backOffMultiplier</code></p></td><td colspan="1" rowspan="1"><p><code>5</code></p></td><td colspan="1" rowspan="1"><p>The back-off multiplier.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>collisionAvoidanceFactor</code></p></td><td colspan="1" rowspan="1"><p><code>0.15</code></p></td><td colspan="1" rowspan="1"><p>The percentage of range of collision avoidance if enabled.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>initialRedeliveryDelay</code></p></td><td colspan="1" rowspan="1"><p><code>1000L</code></p></td><td colspan="1" rowspan="1"><p>The initial redelivery delay in milliseconds.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maximumRedeliveries</code></p></td><td colspan="1" rowspan="1"><p><code>6</code></p></td><td colspan="1" rowspan="1"><p>Sets the maximum number of times a message will be redelivered before it is considered a <strong>poisoned pill</strong> and returned to the broker so it can go to a Dead Letter Queue.</p><p>Set to <strong><code>-1</code></strong> for unlimited redeliveries.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maximumRedeliveryDelay</code></p></td><td colspan="1" rowspan="1"><p><code>-1</code></p></td><td colspan="1" rowspan="1"><p>Sets the maximum delivery delay that will be applied if the <strong><code>useExponentialBackOff</code></strong> option is set. (use value <strong><code>-1</code></strong> to define that no maximum be applied) (<span style="color: red;">v5.5</span>).</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>redeliveryDelay</code></p></td><td colspan="1" rowspan="1"><p><code>1000L</code></p></td><td colspan="1" rowspan="1"><p>The delivery delay if <strong><code>initialRedeliveryDelay=0</code></strong> (<span style="color: red;">v5.4</span>).</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useCollisionAvoidance</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Should the redelivery policy use collision avoidance.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useExponentialBackOff</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Should exponential back-off be used, i.e., to exponentially increase the timeout.</p></td></tr></tbody></table><h2>RedeliveryPolicy per Destination</h2><p>As of ActiveMQ v5.7.0 you can now configure a <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup">RedeliveryPolicy</a> on a per-destination bases. The <strong><code>ActiveMQConnection</code></strong> factory class now exposes a <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/broker/region/policy/RedeliveryPolicyMap.java?view=markup">RedeliveryPolicyMap</a> property that allows to assign a RedeliveryPolicy using named destinations or using destination wildcards. The code snipped below shows how to configure a different <a shape="rect" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup">RedeliveryPolicy</a> for Topics and Queues.</p><structured-macro ac:macro-id="7d31d1f3-c21c-4223-9684-c746160b6941" ac:name="code" ac:schema-version="1"><plain-text-body> ActiveMQConnection connection ... // Create a connection
RedeliveryPolicy queuePolicy = new RedeliveryPolicy();
queuePolicy.setInitialRedeliveryDelay(0);
@@ -15,9 +14,8 @@
// Receive a message with the JMS API
RedeliveryPolicyMap map = connection.getRedeliveryPolicyMap();
- map.put(new ActiveMQTopic(">"), topicPolicy);
- map.put(new ActiveMQQueue(">"), queuePolicy);
+ map.put(new ActiveMQTopic(">"), topicPolicy);
+ map.put(new ActiveMQQueue(">"), queuePolicy);
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/release-guide.xml b/release-guide.xml
index 4e839f4..3850ba3 100644
--- a/release-guide.xml
+++ b/release-guide.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><p>How to create and announce an ActiveMQ release. This release is based on <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">General guide for releasing Maven-based project at Apache </a>, so be sure to check it out before continuing and meet all prerequisites.</p><h2 id="ReleaseGuide-Maven2Setup">Maven 2 Setup</h2><p>Before you deploy anything to the maven repository using Maven 2, you should configure your ~/.m2/settings.xml file<br clear="none"> so that the file permissions of the deployed artifacts are group writeable. If you do not do this, other developers will not able to overwrite your SNAPSHOT releases with newer versions.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<settings>
+<div class="wiki-content maincontent"><p>How to create and announce an ActiveMQ release. This release is based on <a shape="rect" href="http://maven.apache.org/developers/release/apache-release.html">General guide for releasing Maven-based project at Apache </a>, so be sure to check it out before continuing and meet all prerequisites.</p><h2>Maven 2 Setup</h2><p>Before you deploy anything to the maven repository using Maven 2, you should configure your ~/.m2/settings.xml file<br clear="none"> so that the file permissions of the deployed artifacts are group writeable. If you do not do this, other developers will not able to overwrite your SNAPSHOT releases with newer versions.</p><structured-macro ac:macro-id="75ba3cea-b7a5-49f8-bea6-cef8c4e09a40" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><settings>
...
<servers>
@@ -30,12 +29,8 @@
</servers>
...
</settings>
-]]></script>
-</div></div><p>It is also essential that you configure your umask to 2 on people.apache.org for non-interactive login. If your shell is tcsh you can edit .cshrc to include</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[umask 2
-]]></script>
-</div></div><p>Other shell initialization files may interfere with this setting but if this is the only umask setting it appears to work. Instructions for other shells would be welcome.</p><h3 id="ReleaseGuide-Additionallocalconfigurationforusingreleaseandstagingplugins.">Additional local configuration for using release and staging plugins.</h3><p>To effectively use the release and staging plugins you need some information about where the staging will happen and signing information for gpg. Your ~/.m2/settings.xml should contain a profile like this:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<settings>
+</plain-text-body></structured-macro><p>It is also essential that you configure your umask to 2 on people.apache.org for non-interactive login. If your shell is tcsh you can edit .cshrc to include</p><structured-macro ac:macro-id="991c1010-e00b-4ee9-9a7d-f7a1b2a797ea" ac:name="code" ac:schema-version="1"><plain-text-body>umask 2
+</plain-text-body></structured-macro><p>Other shell initialization files may interfere with this setting but if this is the only umask setting it appears to work. Instructions for other shells would be welcome.</p><h3>Additional local configuration for using release and staging plugins.</h3><p>To effectively use the release and staging plugins you need some information about where the staging will happen and signing information for gpg. Your ~/.m2/settings.xml should contain a profile like this:</p><structured-macro ac:macro-id="e4d0820a-d791-42cc-8d68-74e6521b5133" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><settings>
<profiles>
<profile>
<id>apache-release</id>
@@ -46,35 +41,17 @@
</profiles>
...
</settings>
-]]></script>
-</div></div><h2 id="ReleaseGuide-CreatingtheActiveMQRelease">Creating the ActiveMQ Release</h2><p>The release plugin will prompt for a release version, tag and next release version. Use a three digit release version of the form: 5.x.x and for the tag use a string of the form: activemq-5.x.x. The next version string should use the two digit from: 5.x-SNAPSHOT as this can be consistent for future SNAPSHOT releases.</p><ol><li><p>Verify the to-be-released version identifier exists in the <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-spring/src/main/resources/META-INF/spring.schemas;hb=HEAD">META-INF/spring.schemas</a> mappings file AND <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-osgi/src/main/resources/META-INF/spring.schemas;hb=HEAD">activemq-osgi/src/main/resources/META-INF/spring.schemas</a> file, if not add it and commit. It should contain:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd]]></script>
-</div></div></li><li><p>Verify headers with <a shape="rect" class="external-link" href="http://incubator.apache.org/rat/apache-rat-plugin/usage.html">rat</a></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn -e apache-rat:check
-grep -e ' !?????' target/rat.txt -- will show any files without licenses
-]]></script>
-</div></div></li><li><p>Do a release dry run to check for problems</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn release:prepare -DdryRun=true
-]]></script>
-</div></div><p>Check that you are happy with the results. The poms for the proposed tags will be in pom.xml.tag. When you like the results, clean up:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn release:clean
-]]></script>
-</div></div></li><li><p>Prepare the release</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn release:prepare
-]]></script>
-</div></div><p>This will create the tag in git and leave various stuff around locally to direct the perform phase.</p></li><li><p>Make a local copy of the release configuration in case something goes wrong</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd ..
+</plain-text-body></structured-macro><h2>Creating the ActiveMQ Release</h2><p>The release plugin will prompt for a release version, tag and next release version. Use a three digit release version of the form: 5.x.x and for the tag use a string of the form: activemq-5.x.x. The next version string should use the two digit from: 5.x-SNAPSHOT as this can be consistent for future SNAPSHOT releases.</p><ol><li><p>Verify the to-be-released version identifier exists in the <a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-spring/src/main/resources/META-INF/spring.schemas;hb=HEAD">META-INF/spring.schemas</a> mappings file AND <a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-osgi/src/main/resources/META-INF/spring.schemas;hb=HEAD">activemq-osgi/src/main/resources/META-INF/spring.schemas</a> file, if not add it and commit. It should contain:</p><structured-macro ac:macro-id="be57ba07-af94-4309-9fc3-17bb1b703d8f" ac:name="code" ac:schema-version="1"><plain-text-body>http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd</plain-text-body></structured-macro></li><li><p>Verify headers with <a shape="rect" href="http://incubator.apache.org/rat/apache-rat-plugin/usage.html">rat</a></p><structured-macro ac:macro-id="728bb745-de7e-4f0d-a9eb-d032af3bc637" ac:name="code" ac:schema-version="1"><plain-text-body>mvn -e apache-rat:check
+grep -e ' !?????' target/rat.txt -- will show any files without licenses
+</plain-text-body></structured-macro></li><li><p>Do a release dry run to check for problems</p><structured-macro ac:macro-id="6072536c-6c96-4842-8e2e-a98143781f0a" ac:name="code" ac:schema-version="1"><plain-text-body>mvn release:prepare -DdryRun=true
+</plain-text-body></structured-macro><p>Check that you are happy with the results. The poms for the proposed tags will be in pom.xml.tag. When you like the results, clean up:</p><structured-macro ac:macro-id="7ef5650e-abc3-4cdb-854d-12b89cb3dc62" ac:name="code" ac:schema-version="1"><plain-text-body>mvn release:clean
+</plain-text-body></structured-macro></li><li><p>Prepare the release</p><structured-macro ac:macro-id="191d99fb-01a4-4e3b-b11a-fc5ab026076b" ac:name="code" ac:schema-version="1"><plain-text-body>mvn release:prepare
+</plain-text-body></structured-macro><p>This will create the tag in git and leave various stuff around locally to direct the perform phase.</p></li><li><p>Make a local copy of the release configuration in case something goes wrong</p><structured-macro ac:macro-id="2f26725a-56e0-46d6-9005-e83477b647f1" ac:name="code" ac:schema-version="1"><plain-text-body>cd ..
cp -r activemq-release activemq-release-prepared
cd activemq-release
-]]></script>
-</div></div></li><li><p>Perform the release to the staging repo</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn release:perform
-]]></script>
-</div></div><p>This uses both the activemq release profile which directs building source jars, javadoc jars, and signing everything, and also the settings release profile that says where to<br clear="none"> put stuff and how to sign it.</p></li><li>Close the staging repository<br clear="none"> Quote from the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">Maven release guide for Apache projects</a><blockquote><p>Login to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a> using your Apache LDAP credentials. Click on "Staging". Then click on "maven" in the list of repositories. In the panel below you should see an open repository that is linked to your username and ip. Right click on this repository and select "Close". This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything. Enter the name and version of the artifact being released in the "Description" field and then click "Close". This will make it easier to identify it later.</p></blockquote>See the image in the original guide for more info.</li><li>Verify staged artifacts<br clear="none"> Quote from the <a shape="rect" class="external-link" href="http://maven.apache.org/developers/release/apache-release.html">original guide</a><blockquote><p>If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of *.asc (signature) files. If the you don't like the content of the repository, right click your repository and choose "Drop". You can then rollback your release and repeat the process.<br clear="none"> Note the repository URL, you will need this in your vote email.</p></blockquote></li><li><p>Build the site from the tag that release:perform checked out into target/checkout in the previous step.<br clear="none"> Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd target/checkout
-mvn site -Prelease]]></script>
-</div></div></li><li><p>Populate the Javadocs site in svn</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
+</plain-text-body></structured-macro></li><li><p>Perform the release to the staging repo</p><structured-macro ac:macro-id="b9c25523-2ece-4d52-9777-b1f0c9d73a47" ac:name="code" ac:schema-version="1"><plain-text-body>mvn release:perform
+</plain-text-body></structured-macro><p>This uses both the activemq release profile which directs building source jars, javadoc jars, and signing everything, and also the settings release profile that says where to<br clear="none"> put stuff and how to sign it.</p></li><li>Close the staging repository<br clear="none"> Quote from the <a shape="rect" href="http://maven.apache.org/developers/release/apache-release.html">Maven release guide for Apache projects</a><blockquote><p>Login to <a shape="rect" class="external-link" href="https://repository.apache.org">https://repository.apache.org</a> using your Apache LDAP credentials. Click on "Staging". Then click on "maven" in the list of repositories. In the panel below you should see an open repository that is linked to your username and ip. Right click on this repository and select "Close". This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything. Enter the name and version of the artifact being released in the "Description" field and then click "Close". This will make it easier to identify it later.</p></blockquote>See the image in the original guide for more info.</li><li>Verify staged artifacts<br clear="none"> Quote from the <a shape="rect" href="http://maven.apache.org/developers/release/apache-release.html">original guide</a><blockquote><p>If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of *.asc (signature) files. If the you don't like the content of the repository, right click your repository and choose "Drop". You can then rollback your release and repeat the process.<br clear="none"> Note the repository URL, you will need this in your vote email.</p></blockquote></li><li><p>Build the site from the tag that release:perform checked out into target/checkout in the previous step.<br clear="none"> Note that the -Prelease profile is needed to specify the profile in settings.xml that configures the staging location.</p><structured-macro ac:macro-id="53884a8b-109c-48fb-8e96-2af9ba34b936" ac:name="code" ac:schema-version="1"><plain-text-body>cd target/checkout
+mvn site -Prelease</plain-text-body></structured-macro></li><li><p>Populate the Javadocs site in svn</p><structured-macro ac:macro-id="13bdb923-a453-4573-9ec3-e286b237df6c" ac:name="noformat" ac:schema-version="1"><plain-text-body>svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/maven
mkdir <version>
#copy over apidocs folder that was created by the site plugin to <version>/apidocs
@@ -82,19 +59,13 @@
svn rm apidocs
ln -s <version>/apidocs apidocs
svn add apidocs
-# and commit once it looks good.</pre>
-</div></div></li><li><p>Stage the official release artifacts in the SVN dist dev area for folks to test and vote on, using the helper script already in the repo:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>svn co https://dist.apache.org/repos/dist/dev/activemq/activemq/
+# and commit once it looks good.</plain-text-body></structured-macro></li><li><p>Stage the official release artifacts in the SVN dist dev area for folks to test and vote on, using the helper script already in the repo:</p><structured-macro ac:macro-id="e82dca02-badd-4c46-842c-881423fdf5f6" ac:name="noformat" ac:schema-version="1"><plain-text-body>svn co https://dist.apache.org/repos/dist/dev/activemq/activemq/
cd activemq
./prepare-release.sh <nexus-staging-repo-url> <version>
# Example: ./prepare-release.sh https://repository.apache.org/content/repositories/orgapacheactivemq-1149 5.15.1
svn add <version>
-and commit once it looks good.</pre>
-</div></div></li><li>Call a vote on the dev list, listing the great new features of the release.</li></ol><h2 id="ReleaseGuide-Afterthevotepasses">After the vote passes</h2><ol><li>Promote the release (i.e. release the staging repository): login to<span style="color: rgb(112,112,112);"> </span><a shape="rect" class="external-link" href="https://repository.apache.org/">https://repository.apache.org</a>, navigate to the staging repository and click the "release" button. </li><li><p>Copy the staged release files from the SVN dist dev folder to the SVN dist release folder: <a shape="rect" class="external-link" href="https://dist.apache.org/repos/dist/release/activemq/">https://dist.apache.org/repos/dist/release/activemq/</a></p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>svn cp -m "add files for activemq-<version>" https://dist.apache.org/repos/dist/dev/activemq/activemq/<version> https://dist.apache.org/repos/dist/release/activemq/<version>
-# Example: svn cp -m "add files for activemq-5.15.1" https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.1 https://dist.apache.org/repos/dist/release/activemq/5.15.1</pre>
-</div></div></li><li><p>Populate the schema site in svn</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
+and commit once it looks good.</plain-text-body></structured-macro></li><li>Call a vote on the dev list, listing the great new features of the release.</li></ol><h2>After the vote passes</h2><ol><li>Promote the release (i.e. release the staging repository): login to<span style="color: rgb(112,112,112);"> </span><a shape="rect" class="external-link" href="https://repository.apache.org/">https://repository.apache.org</a>, navigate to the staging repository and click the "release" button. </li><li><p>Copy the staged release files from the SVN dist dev folder to the SVN dist release folder: <a shape="rect" href="https://dist.apache.org/repos/dist/release/activemq/">https://dist.apache.org/repos/dist/release/activemq/</a></p><structured-macro ac:macro-id="584ae20f-3171-4882-86e9-6cfd55889764" ac:name="noformat" ac:schema-version="1"><plain-text-body>svn cp -m "add files for activemq-<version>" https://dist.apache.org/repos/dist/dev/activemq/activemq/<version> https://dist.apache.org/repos/dist/release/activemq/<version>
+# Example: svn cp -m "add files for activemq-5.15.1" https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.1 https://dist.apache.org/repos/dist/release/activemq/5.15.1</plain-text-body></structured-macro></li><li><p>Populate the schema site in svn</p><structured-macro ac:macro-id="2747fd28-e8ca-4029-9e68-e27f4826c66a" ac:name="noformat" ac:schema-version="1"><plain-text-body>svn co https://svn.apache.org/repos/infra/websites/production/activemq/content
cd content/schema/core
curl --remote-name-all https://repository.apache.org/content/repositories/releases/org/apache/activemq/activemq-spring/<version>/activemq-spring-<version>{-schema.html,.xsd}{.asc,.asc.md5,.asc.sha1,.sha1,.md5,}
for i in activemq-spring-5.9.0*; do mv -- "$i" "${i//spring/core}"; done;
@@ -103,6 +74,5 @@
ln -s activemq-core-5.9.0.xsd activemq-core.xsd
svn add activemq-core.xsd
# and commit once it looks good.
-</pre>
-</div></div></li><li>Continue with the Announcing section below</li><li>Created a in progress wiki page for the next release</li><li>Remove any releases from the dist site that are no longer supported and update the wiki page for that release to point to the archives for downloads.</li></ol><h2 id="ReleaseGuide-AnnouncingtheActiveMQRelease">Announcing the ActiveMQ Release</h2><ol><li>Perform a release in JIRA and create a new release version in JIRA.<ol><li>Move unresolved issues to the next release first, in a bulk (do not send email) update</li><li>You might also want to search for resolved/closed issues with no fix version just in case</li></ol></li><li>Create a download page for the release in the WIKI similar like the <a shape="rect" href="activemq-530-release.xml">ActiveMQ 5.3.0 Release</a>; also update the main <a shape="rect" href="download.xml">Download</a> page as appropriate</li><li>Update the <a shape="rect" href="xml-reference.xml">Xml Reference</a> page with a link to the HTML and XSD</li><li>Update latest release link on home page</li><li>Change the links for the prior release to reference the archive (at <a shape="rect" class="external-link" href="http://archive.apache.org/dist/activemq/">http://archive.apache.org/dist/activemq/</a>); otherwise, users will not be able to locate the older release for download</li><li>Update <a shape="rect" href="quicklinks.xml">QuickLinks</a> and <a shape="rect" href="javadocs.xml">JavaDocs</a> pages</li><li>Mail the <a shape="rect" class="external-link" href="mailto:dev@activemq.codehaus.org" rel="nofollow">dev</a> & <a shape="rect" class="external-link" href="mailto:user@activemq.codehaus.org" rel="nofollow">user</a> lists</li><li><a shape="rect" class="external-link" href="http://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=ACTIVEMQ">Post</a> a news entry on the WIKI</li><li>tweet</li><li>Have a beer! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></li></ol></div>
+</plain-text-body></structured-macro></li><li>Continue with the Announcing section below</li><li>Created a in progress wiki page for the next release</li><li>Remove any releases from the dist site that are no longer supported and update the wiki page for that release to point to the archives for downloads.</li></ol><h2>Announcing the ActiveMQ Release</h2><ol><li>Perform a release in JIRA and create a new release version in JIRA.<ol><li>Move unresolved issues to the next release first, in a bulk (do not send email) update</li><li>You might also want to search for resolved/closed issues with no fix version just in case</li></ol></li><li>Create a download page for the release in the WIKI similar like the <link><page ri:content-title="ActiveMQ 5.3.0 Release"></page></link>; also update the main <link><page ri:content-title="Download"></page></link> page as appropriate</li><li>Update the <link><page ri:content-title="Xml Reference"></page></link> page with a link to the HTML and XSD</li><li>Update latest release link on home page</li><li>Change the links for the prior release to reference the archive (at <a shape="rect" href="http://archive.apache.org/dist/activemq/">http://archive.apache.org/dist/activemq/</a>); otherwise, users will not be able to locate the older release for download</li><li>Update <link><page ri:content-title="QuickLinks"></page></link> and <link><page ri:content-title="JavaDocs"></page></link> pages</li><li>Mail the <a shape="rect" href="mailto:dev@activemq.codehaus.org">dev</a> & <a shape="rect" href="mailto:user@activemq.codehaus.org">user</a> lists</li><li><a shape="rect" href="http://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=ACTIVEMQ">Post</a> a news entry on the WIKI</li><li>tweet</li><li>Have a beer! <emoticon ac:name="smile"></emoticon></li></ol></div>
diff --git a/release-info.xml b/release-info.xml
index 7a22bce..3b4535c 100644
--- a/release-info.xml
+++ b/release-info.xml
@@ -1,5 +1,6 @@
<div class="wiki-content maincontent">
-<h2 id="ReleaseInfo-GeneralReleaseInformation">General Release Information</h2>
+<h2>General Release Information</h2>
-<ul><li><a shape="rect" class="external-link" href="http://jira.activemq.org/jira/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel" rel="nofollow">Current RoadMap</a></li><li><a shape="rect" href="release-guide.xml">Release Guide</a></li><li><a shape="rect" class="external-link" href="http://wiki.apache.org/incubator/SigningReleases">Signing Releases</a></li><li><a shape="rect" class="external-link" href="http://apache.org/dev/mirrors.html">Apache Mirror Guidelines</a></li></ul></div>
+<ul><li><a shape="rect" href="http://jira.activemq.org/jira/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel">Current RoadMap</a></li><li><link><page ri:content-title="Release Guide"></page></link></li><li><a shape="rect" href="http://wiki.apache.org/incubator/SigningReleases">Signing Releases</a></li><li><a shape="rect" href="http://apache.org/dev/mirrors.html">Apache Mirror Guidelines</a></li></ul>
+</div>
diff --git a/release-plans.xml b/release-plans.xml
index 42e95ca..b6555e1 100644
--- a/release-plans.xml
+++ b/release-plans.xml
@@ -1,10 +1,11 @@
<div class="wiki-content maincontent">
-<h3 id="ReleasePlans-Information">Information</h3>
+<h3>Information</h3>
-<ul><li><a shape="rect" href="release-info.xml">Release Info</a></li><li><a shape="rect" href="how-you-can-help-release.xml">How you can help release</a></li></ul>
+<ul><li><link><page ri:content-title="Release Info"></page></link></li><li><link><page ri:content-title="How you can help release"></page></link></li></ul>
-<h3 id="ReleasePlans-ReleasePlans">Release Plans</h3>
+<h3>Release Plans</h3>
-<ul><li><a shape="rect" href="40-rc-1-guide.xml">4.0 RC 1 Guide</a></li></ul></div>
+<ul><li><link><page ri:content-title="4.0 RC 1 Guide"></page></link></li></ul>
+</div>
diff --git a/replicated-leveldb-store.xml b/replicated-leveldb-store.xml
index efc5c11..3cff206 100644
--- a/replicated-leveldb-store.xml
+++ b/replicated-leveldb-store.xml
@@ -1,22 +1,18 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The LevelDB store has been deprecated and is no longer supported or recommended for use. The recommended store is <a shape="rect" href="kahadb.xml">KahaDB</a></p></div></div><h2 id="ReplicatedLevelDBStore-Synopsis">Synopsis</h2><p>The Replicated LevelDB Store uses Apache ZooKeeper to pick a master from a set of broker nodes configured to replicate a LevelDB Store. Then synchronizes all slave LevelDB Stores with the master keeps them up to date by replicating all updates from the master.</p><p>The Replicated LevelDB Store uses the same data files as a LevelDB Store, so you can switch a broker configuration between replicated and non replicated whenever you want.</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Version Compatibility</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Available as of ActiveMQ 5.9.0.</p></div></div><h2 id="ReplicatedLevelDBStore-Howitworks.">How it works.</h2><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="replicated-leveldb-store.data/replicated-leveldb-store.png" data-image-src="/confluence/download/attachments/31820167/replicated-leveldb-store.png?version=1&modificationDate=1367958504000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="31949055" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="replicated-leveldb-store.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="31820167" data-linked-resource-container-version="31"></span></p><p>It uses <a shape="rect" class="external-link" href="http://zookeeper.apache.org/">Apache ZooKeeper</a> to coordinate which node in the cluster becomes the master. The elected master broker node starts and accepts client connections. The other nodes go into slave mode and connect the the master and synchronize their persistent state /w it. The slave nodes do not accept client connections. All persistent operations are replicated to the connected slaves. If the master dies, the slaves with the latest update gets promoted to become the master. The failed node can then be brought back online and it will go into slave mode.</p><p>All messaging operations which require a sync to disk will wait for the update to be replicated to a quorum of the nodes before completing. So if you configure the store with <code>replicas="3"</code> then the quorum size is <code>(3/2+1)=2</code>. The master will store the update locally and wait for 1 other slave to store the update before reporting success. Another way to think about it is that store will do synchronous replication to a quorum of the replication nodes and asynchronous replication replication to any additional nodes.</p><p>When a new master is elected, you also need at least a quorum of nodes online to be able to find a node with the lastest updates. The node with the lastest updates will become the new master. Therefore, it's recommend that you run with at least 3 replica nodes so that you can take one down without suffering a service outage.</p><h3 id="ReplicatedLevelDBStore-DeploymentTips">Deployment Tips</h3><p>Clients should be using the <a shape="rect" href="failover-transport-reference.xml">Failover Transport</a> to connect to the broker nodes in the replication cluster. e.g. using a URL something like the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[failover:(tcp://broker1:61616,tcp://broker2:61616,tcp://broker3:61616)
-]]></script>
-</div></div><p>You should run at least 3 ZooKeeper server nodes so that the ZooKeeper service is highly available. Don't overcommit your ZooKeeper servers. An overworked ZooKeeper might start thinking live replication nodes have gone offline due to delays in processing their 'keep-alive' messages.</p><p>For best results, make sure you explicitly configure the hostname attribute with a hostname or ip address for the node that other cluster members to access the machine with. The automatically determined hostname is not always accessible by the other cluster members and results in slaves not being able to establish a replication session with the master.</p><h2 id="ReplicatedLevelDBStore-Configuration">Configuration</h2><p>You can configure ActiveMQ to use LevelDB for its persistence adapter - like below :</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <broker brokerName="broker" ... >
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="9bd9729a-2a60-451b-8c3b-fcf0ab16dfcb" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>The LevelDB store has been deprecated and is no longer supported or recommended for use. The recommended store is <link><page ri:content-title="KahaDB"></page></link></p></rich-text-body></structured-macro><h2>Synopsis</h2><p>The Replicated LevelDB Store uses Apache ZooKeeper to pick a master from a set of broker nodes configured to replicate a LevelDB Store. Then synchronizes all slave LevelDB Stores with the master keeps them up to date by replicating all updates from the master.</p><p>The Replicated LevelDB Store uses the same data files as a LevelDB Store, so you can switch a broker configuration between replicated and non replicated whenever you want.</p><structured-macro ac:macro-id="2430bb56-885a-4fe1-a01a-dad92e2e86c4" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Version Compatibility</parameter><rich-text-body><p>Available as of ActiveMQ 5.9.0.</p></rich-text-body></structured-macro><h2>How it works.</h2><p><image><attachment ri:filename="replicated-leveldb-store.png"></attachment></image></p><p>It uses <a shape="rect" href="http://zookeeper.apache.org/">Apache ZooKeeper</a> to coordinate which node in the cluster becomes the master. The elected master broker node starts and accepts client connections. The other nodes go into slave mode and connect the the master and synchronize their persistent state /w it. The slave nodes do not accept client connections. All persistent operations are replicated to the connected slaves. If the master dies, the slaves with the latest update gets promoted to become the master. The failed node can then be brought back online and it will go into slave mode.</p><p>All messaging operations which require a sync to disk will wait for the update to be replicated to a quorum of the nodes before completing. So if you configure the store with <code>replicas="3"</code> then the quorum size is <code>(3/2+1)=2</code>. The master will store the update locally and wait for 1 other slave to store the update before reporting success. Another way to think about it is that store will do synchronous replication to a quorum of the replication nodes and asynchronous replication replication to any additional nodes.</p><p>When a new master is elected, you also need at least a quorum of nodes online to be able to find a node with the lastest updates. The node with the lastest updates will become the new master. Therefore, it's recommend that you run with at least 3 replica nodes so that you can take one down without suffering a service outage.</p><h3>Deployment Tips</h3><p>Clients should be using the <link><page ri:content-title="Failover Transport Reference"></page><plain-text-link-body>Failover Transport</plain-text-link-body></link> to connect to the broker nodes in the replication cluster. e.g. using a URL something like the following:</p><structured-macro ac:macro-id="6f40f660-59d9-47bd-9621-f557dcb71e22" ac:name="code" ac:schema-version="1"><plain-text-body>failover:(tcp://broker1:61616,tcp://broker2:61616,tcp://broker3:61616)
+</plain-text-body></structured-macro><p>You should run at least 3 ZooKeeper server nodes so that the ZooKeeper service is highly available. Don't overcommit your ZooKeeper servers. An overworked ZooKeeper might start thinking live replication nodes have gone offline due to delays in processing their 'keep-alive' messages.</p><p>For best results, make sure you explicitly configure the hostname attribute with a hostname or ip address for the node that other cluster members to access the machine with. The automatically determined hostname is not always accessible by the other cluster members and results in slaves not being able to establish a replication session with the master.</p><h2>Configuration</h2><p>You can configure ActiveMQ to use LevelDB for its persistence adapter - like below :</p><structured-macro ac:macro-id="28174a1b-24fc-496a-8a73-c48b7004b0a6" ac:name="code" ac:schema-version="1"><plain-text-body> <broker brokerName="broker" ... >
...
<persistenceAdapter>
<replicatedLevelDB
- directory="activemq-data"
- replicas="3"
- bind="tcp://0.0.0.0:0"
- zkAddress="zoo1.example.org:2181,zoo2.example.org:2181,zoo3.example.org:2181"
- zkPassword="password"
- zkPath="/activemq/leveldb-stores"
- hostname="broker1.example.org"
+ directory="activemq-data"
+ replicas="3"
+ bind="tcp://0.0.0.0:0"
+ zkAddress="zoo1.example.org:2181,zoo2.example.org:2181,zoo3.example.org:2181"
+ zkPassword="password"
+ zkPath="/activemq/leveldb-stores"
+ hostname="broker1.example.org"
/>
</persistenceAdapter>
...
</broker>
-]]></script>
-</div></div><h3 id="ReplicatedLevelDBStore-ReplicatedLevelDBStoreProperties">Replicated LevelDB Store Properties</h3><p>All the broker nodes that are part of the same replication set should have matching <code>brokerName</code> XML attributes. The following configuration properties should be the same on all the broker nodes that are part of the same replication set:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>replicas</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>3</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of nodes that will exist in the cluster. At least (replicas/2)+1 nodes must be online to avoid service outage.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>securityToken</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A security token which must match on all replication nodes for them to accept each others replication requests.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>zkAddress</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>127.0.0.1:2181</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A comma separated list of ZooKeeper servers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>zkPassword</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The password to use when connecting to the ZooKeeper server.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>zkPath</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>/default</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The path to the ZooKeeper directory where Master/Slave election information will be exchanged.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>zkSessionTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>2s</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>How quickly a node failure will be detected by ZooKeeper. (prior to 5.11 - this had a typo <span>zkSessionTmeout)</span></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>sync</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>quorum_mem</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Controls where updates are reside before being considered complete. This setting is a comma separated list of the following options: <code>local_mem</code>, <code>local_disk</code>, <code>remote_mem</code>, <code>remote_disk</code>, <code>quorum_mem</code>, <code>quorum_disk</code>. If you combine two settings for a target, the stronger guarantee is used. For example, configuring <code>local_mem, local_disk</code> is the same as just using <code>local_disk</code>. quorum_mem is the same as <code>local_mem, remote_mem</code> and <code>quorum_disk</code> is the same as <code>local_disk, remote_disk</code></p></td></tr></tbody></table></div><p>Different replication sets can share the same <code>zkPath</code> as long they have different <code>brokerName</code>.</p><p>The following configuration properties can be unique per node:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>bind</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>tcp://0.0.0.0:61619</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When this node becomes a master, it will bind the configured address and port to service the replication protocol. Using dynamic ports is also supported. Just configure with <code>tcp://0.0.0.0:0</code></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>hostname</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The host name used to advertise the replication service when this node becomes the master. If not set it will be automatically determined.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>weight</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The replication node that has the latest update with the highest weight will become the master. Used to give preference to some nodes towards becoming master.</p></td></tr></tbody></table></div><p>The store also supports the same configuration properties of a standard <a shape="rect" href="leveldb-store.xml">LevelDB Store</a> but it does not support the pluggable storage lockers :</p><h3 id="ReplicatedLevelDBStore-StandardLevelDBStoreProperties">Standard LevelDB Store Properties</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>property name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>directory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>LevelDB</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The directory which the store will use to hold it's data files. The store will create the directory if it does not already exist.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>readThreads</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>10</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The number of concurrent IO read threads to allowed.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>logSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>104857600</code> (100 MB)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The max size (in bytes) of each data log file before log file rotation occurs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>verifyChecksums</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Set to true to force checksum verification of all data that is read from the file system.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>paranoidChecks</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Make the store error out as soon as possible if it detects internal corruption.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>org.fusesource.leveldbjni.JniDBFactory, org.iq80.leveldb.impl.Iq80DBFactory</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The factory classes to use when creating the LevelDB indexes</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexMaxOpenFiles</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number of open files that can be used by the index.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexBlockRestartInterval</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>16</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Number keys between restart points for delta encoding of keys.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexWriteBufferSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>6291456</code> (6 MB)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Amount of index data to build up in memory before converting to a sorted on-disk file.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexBlockSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>4096</code> (4 K)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The size of index data packed per block.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexCacheSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>268435456</code> (256 MB)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum amount of off-heap memory to use to cache index blocks.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>indexCompression</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>snappy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The type of compression to apply to the index blocks. Can be snappy or none.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>logCompression</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>none</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The type of compression to apply to the log records. Can be snappy or none.</p></td></tr></tbody></table></div><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Caveats</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The LevelDB store does not yet support storing data associated with <a shape="rect" href="delay-and-schedule-message-delivery.xml">Delay and Schedule Message Delivery</a>. Those are are stored in a separate non-replicated KahaDB data files. Unexpected results will occur if you use <a shape="rect" href="delay-and-schedule-message-delivery.xml">Delay and Schedule Message Delivery</a> with the replicated leveldb store since that data will be not be there when the master fails over to a slave.</p></div></div></div>
+</plain-text-body></structured-macro><h3>Replicated LevelDB Store Properties</h3><p>All the broker nodes that are part of the same replication set should have matching <code>brokerName</code> XML attributes. The following configuration properties should be the same on all the broker nodes that are part of the same replication set:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>replicas</code></p></td><td colspan="1" rowspan="1"><p><code>3</code></p></td><td colspan="1" rowspan="1"><p>The number of nodes that will exist in the cluster. At least (replicas/2)+1 nodes must be online to avoid service outage.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>securityToken</code></p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p>A security token which must match on all replication nodes for them to accept each others replication requests.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>zkAddress</code></p></td><td colspan="1" rowspan="1"><p><code>127.0.0.1:2181</code></p></td><td colspan="1" rowspan="1"><p>A comma separated list of ZooKeeper servers.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>zkPassword</code></p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p>The password to use when connecting to the ZooKeeper server.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>zkPath</code></p></td><td colspan="1" rowspan="1"><p><code>/default</code></p></td><td colspan="1" rowspan="1"><p>The path to the ZooKeeper directory where Master/Slave election information will be exchanged.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>zkSessionTimeout</code></p></td><td colspan="1" rowspan="1"><p><code>2s</code></p></td><td colspan="1" rowspan="1"><p>How quickly a node failure will be detected by ZooKeeper. (prior to 5.11 - this had a typo <span>zkSessionTmeout)</span></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>sync</code></p></td><td colspan="1" rowspan="1"><p><code>quorum_mem</code></p></td><td colspan="1" rowspan="1"><p>Controls where updates are reside before being considered complete. This setting is a comma separated list of the following options: <code>local_mem</code>, <code>local_disk</code>, <code>remote_mem</code>, <code>remote_disk</code>, <code>quorum_mem</code>, <code>quorum_disk</code>. If you combine two settings for a target, the stronger guarantee is used. For example, configuring <code>local_mem, local_disk</code> is the same as just using <code>local_disk</code>. quorum_mem is the same as <code>local_mem, remote_mem</code> and <code>quorum_disk</code> is the same as <code>local_disk, remote_disk</code></p></td></tr></tbody></table><p>Different replication sets can share the same <code>zkPath</code> as long they have different <code>brokerName</code>.</p><p>The following configuration properties can be unique per node:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>bind</code></p></td><td colspan="1" rowspan="1"><p><code>tcp://0.0.0.0:61619</code></p></td><td colspan="1" rowspan="1"><p>When this node becomes a master, it will bind the configured address and port to service the replication protocol. Using dynamic ports is also supported. Just configure with <code>tcp://0.0.0.0:0</code></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>hostname</code></p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p>The host name used to advertise the replication service when this node becomes the master. If not set it will be automatically determined.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>weight</code></p></td><td colspan="1" rowspan="1"><p>1</p></td><td colspan="1" rowspan="1"><p>The replication node that has the latest update with the highest weight will become the master. Used to give preference to some nodes towards becoming master.</p></td></tr></tbody></table><p>The store also supports the same configuration properties of a standard <link><page ri:content-title="LevelDB Store"></page></link> but it does not support the pluggable storage lockers :</p><h3>Standard LevelDB Store Properties</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>property name</p></th><th colspan="1" rowspan="1"><p>default value</p></th><th colspan="1" rowspan="1"><p>Comments</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>directory</code></p></td><td colspan="1" rowspan="1"><p><code>LevelDB</code></p></td><td colspan="1" rowspan="1"><p>The directory which the store will use to hold it's data files. The store will create the directory if it does not already exist.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>readThreads</code></p></td><td colspan="1" rowspan="1"><p><code>10</code></p></td><td colspan="1" rowspan="1"><p>The number of concurrent IO read threads to allowed.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>logSize</code></p></td><td colspan="1" rowspan="1"><p><code>104857600</code> (100 MB)</p></td><td colspan="1" rowspan="1"><p>The max size (in bytes) of each data log file before log file rotation occurs.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>verifyChecksums</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Set to true to force checksum verification of all data that is read from the file system.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>paranoidChecks</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Make the store error out as soon as possible if it detects internal corruption.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexFactory</code></p></td><td colspan="1" rowspan="1"><p><code>org.fusesource.leveldbjni.JniDBFactory, org.iq80.leveldb.impl.Iq80DBFactory</code></p></td><td colspan="1" rowspan="1"><p>The factory classes to use when creating the LevelDB indexes</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexMaxOpenFiles</code></p></td><td colspan="1" rowspan="1"><p><code>1000</code></p></td><td colspan="1" rowspan="1"><p>Number of open files that can be used by the index.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexBlockRestartInterval</code></p></td><td colspan="1" rowspan="1"><p><code>16</code></p></td><td colspan="1" rowspan="1"><p>Number keys between restart points for delta encoding of keys.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexWriteBufferSize</code></p></td><td colspan="1" rowspan="1"><p><code>6291456</code> (6 MB)</p></td><td colspan="1" rowspan="1"><p>Amount of index data to build up in memory before converting to a sorted on-disk file.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexBlockSize</code></p></td><td colspan="1" rowspan="1"><p><code>4096</code> (4 K)</p></td><td colspan="1" rowspan="1"><p>The size of index data packed per block.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexCacheSize</code></p></td><td colspan="1" rowspan="1"><p><code>268435456</code> (256 MB)</p></td><td colspan="1" rowspan="1"><p>The maximum amount of off-heap memory to use to cache index blocks.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>indexCompression</code></p></td><td colspan="1" rowspan="1"><p><code>snappy</code></p></td><td colspan="1" rowspan="1"><p>The type of compression to apply to the index blocks. Can be snappy or none.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>logCompression</code></p></td><td colspan="1" rowspan="1"><p><code>none</code></p></td><td colspan="1" rowspan="1"><p>The type of compression to apply to the log records. Can be snappy or none.</p></td></tr></tbody></table><structured-macro ac:macro-id="64752425-9c11-44f7-9161-355edf9feb3b" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Caveats</parameter><rich-text-body><p>The LevelDB store does not yet support storing data associated with <link><page ri:content-title="Delay and Schedule Message Delivery"></page></link>. Those are are stored in a separate non-replicated KahaDB data files. Unexpected results will occur if you use <link><page ri:content-title="Delay and Schedule Message Delivery"></page></link> with the replicated leveldb store since that data will be not be there when the master fails over to a slave.</p></rich-text-body></structured-macro></div>
diff --git a/replicated-message-store.xml b/replicated-message-store.xml
index e9f41ee..44c9499 100644
--- a/replicated-message-store.xml
+++ b/replicated-message-store.xml
@@ -1,28 +1,29 @@
<div class="wiki-content maincontent"><p>If messages are stored on the hard drive of a broker or inside a single database; then you have a single point of failure with respect to the message persistence. If you lose the entire machine, disk or database, you have lost messages.</p>
-<p>For some high end users, messages should never be lost as they could have a large impact on the business. These kinds of users often require some kind of <a shape="rect" href="dr.xml">DR</a> stategy to support message replication so that they can loose an entire data centre and still not loose a message.</p>
+<p>For some high end users, messages should never be lost as they could have a large impact on the business. These kinds of users often require some kind of <link><page ri:content-title="DR"></page></link> stategy to support message replication so that they can loose an entire data centre and still not loose a message.</p>
<p>There are various solutions to the problem of reducing chance of message loss.</p>
-<h3 id="ReplicatedMessageStore-UseRAIDdisks">Use RAID disks</h3>
+<h3>Use RAID disks</h3>
-<p>If you're using RAID disks striped sufficiently, you could just restart the machine - or move the disk to a new machine and restart the broker. This could be sufficient if you're a small business but if you've stringent <a shape="rect" href="dr.xml">DR</a> requirements then if you loose a datacentre the RAID option is not a solution.</p>
+<p>If you're using RAID disks striped sufficiently, you could just restart the machine - or move the disk to a new machine and restart the broker. This could be sufficient if you're a small business but if you've stringent <link><page ri:content-title="DR"></page></link> requirements then if you loose a datacentre the RAID option is not a solution.</p>
-<h3 id="ReplicatedMessageStore-SANorsharednetworkdrive">SAN or shared network drive</h3>
+<h3>SAN or shared network drive</h3>
<p>If you use one of the file based persistence mechanisms such as the default high performance journal and Apache Derby, you could write to a SAN or shared network drive and in times of failure, start up a new broker using the files from the failed broker.</p>
-<p>Also 4.1 allows you to start many brokers reading from the same shared file system to support high availability via the <a shape="rect" href="shared-file-system-master-slave.xml">Shared File System Master Slave</a> feature.</p>
+<p>Also 4.1 allows you to start many brokers reading from the same shared file system to support high availability via the <link><page ri:content-title="Shared File System Master Slave"></page></link> feature.</p>
-<h3 id="ReplicatedMessageStore-Master/Slave">Master/Slave</h3>
+<h3>Master/Slave</h3>
-<p>An alternative is to use the <a shape="rect" href="masterslave.xml">MasterSlave</a> feature to pair brokers together so that all messages are replicated to both brokers, the master and slave to ensure that there are two physical copies of the message so that catastrophic hardware failures (such as loss of an entire data centre) can be handled.</p>
+<p>An alternative is to use the <link><page ri:content-title="MasterSlave"></page></link> feature to pair brokers together so that all messages are replicated to both brokers, the master and slave to ensure that there are two physical copies of the message so that catastrophic hardware failures (such as loss of an entire data centre) can be handled.</p>
-<h3 id="ReplicatedMessageStore-ClusteredJDBCdatabases">Clustered JDBC databases</h3>
+<h3>Clustered JDBC databases</h3>
<p>Various databases like Oracle and MySQL support clustered databases; so we can use these databases with the JDBC MessageStore to get a clustered message store. Note if this option is used then the high performance journal must be disabled (which severely affects performance)</p>
-<h4 id="ReplicatedMessageStore-UseC-JDBC">Use C-JDBC</h4>
+<h4>Use C-JDBC</h4>
-<p>If you don't have or can't afford a clustered database then you could use <a shape="rect" class="external-link" href="http://c-jdbc.objectweb.org/" rel="nofollow">C-JDBC</a> to replicate state across a number of physical datbases to avoid single point of failure and provide a <a shape="rect" href="dr.xml">DR</a> solution. As noted above using a replicated JDBC approach is very slow as it requires us to disable the high performance journal.</p></div>
+<p>If you don't have or can't afford a clustered database then you could use <a shape="rect" href="http://c-jdbc.objectweb.org/">C-JDBC</a> to replicate state across a number of physical datbases to avoid single point of failure and provide a <link><page ri:content-title="DR"></page></link> solution. As noted above using a replicated JDBC approach is very slow as it requires us to disable the high performance journal.</p>
+</div>
diff --git a/resource-adapter-does-not-seem-to-pool-connections.xml b/resource-adapter-does-not-seem-to-pool-connections.xml
index 8ffbf89..7ef1ebf 100644
--- a/resource-adapter-does-not-seem-to-pool-connections.xml
+++ b/resource-adapter-does-not-seem-to-pool-connections.xml
@@ -1,11 +1,9 @@
<div class="wiki-content maincontent"><p>It may seem like the resource adapter when used in an app server like geronimo or jboss is not pooling connections. Looking the the ActiveMQ broker logs, it will show multiple message for each use of a pooled conntion simlilar to:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="21ffa5c6-27c5-468d-9fcd-be9f6e053026" ac:name="code" ac:schema-version="1"><plain-text-body>
16:43:07 INFO Adding new client: ID:localhost-58375-1120682586690-1:0 on transport: TcpTransportChannel: Socket[addr=/127.0.0.1,port=58376,localport=61616]
16:43:08 INFO Removing client: ID:localhost-58375-1120682586690-1:0 on transport: TcpTransportChannel: Socket[addr=/127.0.0.1,port=58376,localport=61616]
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>At first glance it may seem like a new connection is being established.. but if you look at the logs is more detail, you will noticed that the client connection id's are being reused since the connections are being pooled. This behavior is a side-effect of the connection being reset to a 'cleaned up' state. It allows the next client to use the connection as if it has just been created.</p>
diff --git a/resource-adapter-properties.xml b/resource-adapter-properties.xml
index 42fb4c5..5749034 100644
--- a/resource-adapter-properties.xml
+++ b/resource-adapter-properties.xml
@@ -3,42 +3,42 @@
<p>The properties that can be configured are:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Required </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> ServerUrl </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> tcp://localhost:61616 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The URI to connect to the broker on </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> UserName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> defaultUser </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> User name </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> defaultPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Password </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Clientid </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> null </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The JMS client ID to use </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> UseInboundSession </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> BrokerXmlConfig </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The ActiveMQ XML config file to use to deploy an embedded broker. E.g. to configure via an XML configuration file then use <strong>xbean:activemq.xml</strong> or to configure via a <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a> (to avoid using Spring, XBean and XML) then use <strong>broker:(tcp://localhost:61616)</strong> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Required </p></th><th colspan="1" rowspan="1"><p> Default Value </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> ServerUrl </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> tcp://localhost:61616 </p></td><td colspan="1" rowspan="1"><p> The URI to connect to the broker on </p></td></tr><tr><td colspan="1" rowspan="1"><p> UserName </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> defaultUser </p></td><td colspan="1" rowspan="1"><p> User name </p></td></tr><tr><td colspan="1" rowspan="1"><p> Password </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> defaultPassword </p></td><td colspan="1" rowspan="1"><p> Password </p></td></tr><tr><td colspan="1" rowspan="1"><p> Clientid </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> null </p></td><td colspan="1" rowspan="1"><p> The JMS client ID to use </p></td></tr><tr><td colspan="1" rowspan="1"><p> UseInboundSession </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p> BrokerXmlConfig </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p> The ActiveMQ XML config file to use to deploy an embedded broker. E.g. to configure via an XML configuration file then use <strong>xbean:activemq.xml</strong> or to configure via a <link><page ri:content-title="Broker Configuration URI"></page></link> (to avoid using Spring, XBean and XML) then use <strong>broker:(tcp://localhost:61616)</strong> </p></td></tr></tbody></table>
-<h4 id="ResourceAdapterProperties-Performancerelatedsettings">Performance related settings</h4>
+<h4>Performance related settings</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Required </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> AllPrefetchValues </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Sets all the prefetch values in one setting </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> DurableTopicPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 100 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of messages sent to a consumer on a durable topic until acknowledgements are received </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> QueuePrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of messages sent to a consumer on a queue until acknowledgements are received </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> InputStreamPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 100 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of messages sent to a consumer on a JMS stream until acknowledgements are received </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> TopicPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Short.MAX_VALUE - 1 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of messages sent to a consumer on a non-durable topic until acknowledgements are received </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Required </p></th><th colspan="1" rowspan="1"><p> Default Value </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> AllPrefetchValues </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p> Sets all the prefetch values in one setting </p></td></tr><tr><td colspan="1" rowspan="1"><p> DurableTopicPrefetch </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> 100 </p></td><td colspan="1" rowspan="1"><p> The maximum number of messages sent to a consumer on a durable topic until acknowledgements are received </p></td></tr><tr><td colspan="1" rowspan="1"><p> QueuePrefetch </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> 1000 </p></td><td colspan="1" rowspan="1"><p> The maximum number of messages sent to a consumer on a queue until acknowledgements are received </p></td></tr><tr><td colspan="1" rowspan="1"><p> InputStreamPrefetch </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> 100 </p></td><td colspan="1" rowspan="1"><p> The maximum number of messages sent to a consumer on a JMS stream until acknowledgements are received </p></td></tr><tr><td colspan="1" rowspan="1"><p> TopicPrefetch </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> Short.MAX_VALUE - 1 </p></td><td colspan="1" rowspan="1"><p> The maximum number of messages sent to a consumer on a non-durable topic until acknowledgements are received </p></td></tr></tbody></table>
-<h4 id="ResourceAdapterProperties-Redeliveryproperties">Redelivery properties</h4>
+<h4>Redelivery properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Required </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> InitialRedeliveryDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The delay before redeliveries start. Also configurable on the ActivationSpec. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> MaximumRedeliveries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 5 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The maximum number of redeliveries or -1 for no maximum. Also configurable on the ActivationSpec. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> RedeliveryBackOffMultiplier </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 5 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The multiplier to use if exponential back off is enabled. Also configurable on the ActivationSpec. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> RedeliveryUseExponentialBackOff </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> no </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> To enable exponential backoff. Also configurable on the ActivationSpec. </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Required </p></th><th colspan="1" rowspan="1"><p> Default Value </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> InitialRedeliveryDelay </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> 1000 </p></td><td colspan="1" rowspan="1"><p> The delay before redeliveries start. Also configurable on the ActivationSpec. </p></td></tr><tr><td colspan="1" rowspan="1"><p> MaximumRedeliveries </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> 5 </p></td><td colspan="1" rowspan="1"><p> The maximum number of redeliveries or -1 for no maximum. Also configurable on the ActivationSpec. </p></td></tr><tr><td colspan="1" rowspan="1"><p> RedeliveryBackOffMultiplier </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> 5 </p></td><td colspan="1" rowspan="1"><p> The multiplier to use if exponential back off is enabled. Also configurable on the ActivationSpec. </p></td></tr><tr><td colspan="1" rowspan="1"><p> RedeliveryUseExponentialBackOff </p></td><td colspan="1" rowspan="1"><p> no </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> To enable exponential backoff. Also configurable on the ActivationSpec. </p></td></tr></tbody></table>
-<h4 id="ResourceAdapterProperties-ServerUrl">ServerUrl</h4>
+<h4>ServerUrl</h4>
-<p>The URL to the ActiveMQ server that you want this connection to connect to. If using an embedded broker, this value should be 'vm://localhost' if using the auto-created embedded broker, otherwise if you explicitly create a broker (e.g. using one of the <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">embedded broker</a> techniques), then this value should be 'vm://brokerName', where brokerName is replaced by the broker's name.</p>
+<p>The URL to the ActiveMQ server that you want this connection to connect to. If using an embedded broker, this value should be 'vm://localhost' if using the auto-created embedded broker, otherwise if you explicitly create a broker (e.g. using one of the <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><link-body>embedded broker</link-body></link> techniques), then this value should be 'vm://brokerName', where brokerName is replaced by the broker's name.</p>
-<h4 id="ResourceAdapterProperties-UserName">UserName</h4>
+<h4>UserName</h4>
<p>The default user name that will be used to establish connections to the ActiveMQ server.</p>
-<h4 id="ResourceAdapterProperties-Password">Password</h4>
+<h4>Password</h4>
<p>The default password that will be used to log the default user into the ActiveMQ server.</p>
-<h4 id="ResourceAdapterProperties-Clientid">Clientid</h4>
+<h4>Clientid</h4>
<p>The client id that will be set on the connection that is established to the ActiveMQ server.</p>
-<h4 id="ResourceAdapterProperties-UseInboundSession">UseInboundSession</h4>
+<h4>UseInboundSession</h4>
<p>Boolean to configure if outbound connections should reuse the inbound connection's session for sending messages.</p>
-<h4 id="ResourceAdapterProperties-BrokerXmlConfig">BrokerXmlConfig</h4>
+<h4>BrokerXmlConfig</h4>
-<p>Sets the XML configuration file used to configure the embedded ActiveMQ broker via Spring if using embedded mode. If this property is omitted then no embedded broker is used and you must <a shape="rect" href="run-broker.xml">run the broker</a> in a separate process or deployment unit.</p>
+<p>Sets the XML configuration file used to configure the embedded ActiveMQ broker via Spring if using embedded mode. If this property is omitted then no embedded broker is used and you must <link><page ri:content-title="Run Broker"></page><link-body>run the broker</link-body></link> in a separate process or deployment unit.</p>
<p>BrokerXmlConfig is the filename which is assumed to be on the classpath unless a URL is specified. So a value of foo/bar.xml would be assumed to be on the classpath whereas file:dir/file.xml would use the file system. Any valid URL string is supported. </p></div>
diff --git a/resource-adapter.xml b/resource-adapter.xml
index 59355b7..085bd39 100644
--- a/resource-adapter.xml
+++ b/resource-adapter.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="ResourceAdapter-Introduction">Introduction</h2><p>ActiveMQ includes a Java Connector Architecture (JCA) 1.5 Resource Adapter. JCA 1.5 defines the contract between an J2EE application server and external resources such as databases and messaging middleware. It allows the application server to efficiently pool connections, control transactions and manage security. The Resource Adapter allows ActiveMQ to be used from any J2EE 1.4 application server. We have tested that the Resource Adapter works in the following J2EE 1.4 containers</p><ul><li><a shape="rect" class="external-link" href="http://tomee.apache.org/tomcat-jms.html">TomEE</a> 1</li><li>Geronimo 1</li><li>GlassFish</li><li>JBoss 4</li><li>WebLogic 9</li><li>WebSphere 6</li></ul><h2 id="ResourceAdapter-Features">Features</h2><ul><li>Inbound connection delivers messages to MDBs via XA or local transactions.</li><li>Outbound connections support standard container pooling or can reuse the inbound connection/session to avoid XA.</li><li>JTA support: Can be enlisted in XA and local transactions.</li><li>XA transaction recovery via XAResource.recover() supported.</li><li>When used outside a JTA transaction, session transaction settings retain normal JMS semantics so that it be used by your web-app tier.</li><li>Can configure and start up embedded broker.</li><li>Can connect to external ActiveMQ broker or embedded broker.</li><li>Inbound message delivery supports fine grain control of concurrency and prefetching.</li><li>Batching so that multiple messages can be delivered within the same transaction for optimal performances.</li></ul><h2 id="ResourceAdapter-DownloadingtheRAR">Downloading the RAR</h2><p>The RAR is available via <a shape="rect" class="external-link" href="http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22activemq-rar%22" rel="nofollow">maven central</a></p><p><span style="color: rgb(102,0,51);font-size: 20.0px;line-height: 1.5;">Deployment Guides</span></p><ul><li><a shape="rect" href="tomee.xml">TomEE</a></li><li><a shape="rect" href="geronimo.xml">Geronimo</a></li><li><a shape="rect" href="integrating-apache-activemq-with-glassfish.xml">Integrating Apache ActiveMQ with Glassfish</a></li><li><a shape="rect" href="jboss-integration.xml">JBoss Integration</a></li></ul><h2 id="ResourceAdapter-TheuseofanEmbeddedBroker">The use of an Embedded Broker</h2><p>The ActiveMQ Resource Adapter can connect to a remote broker using any of the available transports, or it can start up an embedded broker. As described in the <a shape="rect" href="resource-adapter-properties.xml">Resource Adapter Properties</a>, you can enable an embedded broker using the <strong>BrokerXmlConfig</strong> property.</p><h2 id="ResourceAdapter-ConfigurationReference">Configuration Reference</h2><ul><li><a shape="rect" href="resource-adapter-properties.xml">Resource Adapter Properties</a></li><li><a shape="rect" href="connection-factory-properties.xml">Connection Factory Properties</a></li><li><a shape="rect" href="activation-spec-properties.xml">Activation Spec Properties</a></li></ul></div>
+<div class="wiki-content maincontent"><h2>Introduction</h2><p>ActiveMQ includes a Java Connector Architecture (JCA) 1.5 Resource Adapter. JCA 1.5 defines the contract between an J2EE application server and external resources such as databases and messaging middleware. It allows the application server to efficiently pool connections, control transactions and manage security. The Resource Adapter allows ActiveMQ to be used from any J2EE 1.4 application server. We have tested that the Resource Adapter works in the following J2EE 1.4 containers</p><ul><li><a shape="rect" href="http://tomee.apache.org/tomcat-jms.html">TomEE</a> 1</li><li>Geronimo 1</li><li>GlassFish</li><li>JBoss 4</li><li>WebLogic 9</li><li>WebSphere 6</li></ul><h2>Features</h2><ul><li>Inbound connection delivers messages to MDBs via XA or local transactions.</li><li>Outbound connections support standard container pooling or can reuse the inbound connection/session to avoid XA.</li><li>JTA support: Can be enlisted in XA and local transactions.</li><li>XA transaction recovery via XAResource.recover() supported.</li><li>When used outside a JTA transaction, session transaction settings retain normal JMS semantics so that it be used by your web-app tier.</li><li>Can configure and start up embedded broker.</li><li>Can connect to external ActiveMQ broker or embedded broker.</li><li>Inbound message delivery supports fine grain control of concurrency and prefetching.</li><li>Batching so that multiple messages can be delivered within the same transaction for optimal performances.</li></ul><h2>Downloading the RAR</h2><p>The RAR is available via <a shape="rect" href="http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22activemq-rar%22">maven central</a></p><p><span style="color: rgb(102,0,51);font-size: 20.0px;line-height: 1.5;">Deployment Guides</span></p><ul><li><link><page ri:content-title="TomEE"></page></link></li><li><link><page ri:content-title="Geronimo"></page></link></li><li><link><page ri:content-title="Integrating Apache ActiveMQ with Glassfish"></page></link></li><li><link><page ri:content-title="JBoss Integration"></page></link></li></ul><h2>The use of an Embedded Broker</h2><p>The ActiveMQ Resource Adapter can connect to a remote broker using any of the available transports, or it can start up an embedded broker. As described in the <link><page ri:content-title="Resource Adapter Properties"></page></link>, you can enable an embedded broker using the <strong>BrokerXmlConfig</strong> property.</p><h2>Configuration Reference</h2><ul><li><link><page ri:content-title="Resource Adapter Properties"></page></link></li><li><link><page ri:content-title="Connection Factory Properties"></page></link></li><li><link><page ri:content-title="Activation Spec Properties"></page></link></li></ul></div>
diff --git a/rest-protocols.xml b/rest-protocols.xml
index a856e42..f3703ef 100644
--- a/rest-protocols.xml
+++ b/rest-protocols.xml
@@ -1,34 +1,28 @@
<div class="wiki-content maincontent"><p>There are many ways to map JMS to REST...</p>
-<h2 id="RESTprotocols-Crappynon-REST">Crappy non-REST</h2>
+<h2>Crappy non-REST</h2>
<p>Send via </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d7b1badc-1a83-45f4-aa96-bccc7d98258c" ac:name="code" ac:schema-version="1"><plain-text-body>
POST /queue/Destination
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Consume</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a4aabcb2-1c9b-4fd2-8749-7afdc2abee82" ac:name="code" ac:schema-version="1"><plain-text-body>
GET /queue/Destination
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This is bad as the GET is not idempotent. We can add a user ID or use a cookie</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c5a27fcb-bed0-4dc0-bfae-b2da55d827c2" ac:name="code" ac:schema-version="1"><plain-text-body>
GET /queue/Destination?jsessionId=....
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>though a caching proxy may keep returning the same message</p>
-<h2 id="RESTprotocols-SimpleRESTusing1atatimedelivery">Simple REST using 1 at a time delivery</h2>
+<h2>Simple REST using 1 at a time delivery</h2>
<p>Subscribe via</p>
@@ -43,13 +37,11 @@
<p>POST /ack/consumerId/messageId</p>
-<h2 id="RESTprotocols-BatchmessageREST">Batch message REST</h2>
+<h2>Batch message REST</h2>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="7d52776b-30cf-4924-a0b6-9962cc902061" ac:name="code" ac:schema-version="1"><plain-text-body>
POST lockNextMessage/consumerId?max=10
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>-> give back up to 10 message URLs</p>
@@ -59,11 +51,12 @@
<p>DELETE /consumerId/messages/messageId</p>
-<h3 id="RESTprotocols-Furtheroptions...">Further options...</h3>
+<h3>Further options...</h3>
<p>You can include ACK messages inside the POST; so the 2nd POST could include the ACKs - also you could return the batch of messages as well.</p>
+
</div>
diff --git a/rest.xml b/rest.xml
index 01c0cd7..0f6aef9 100644
--- a/rest.xml
+++ b/rest.xml
@@ -1,13 +1,6 @@
-<div class="wiki-content maincontent"><p>ActiveMQ implements a RESTful API to messaging which allows any web capable device to publish or consume messages using a regular HTTP POST or GET.</p><p>If you are interested in messaging directly from web browsers you might wanna check out our <a shape="rect" href="ajax.xml">Ajax</a> or <a shape="rect" href="websockets.xml">WebSockets</a> support or try <a shape="rect" href="web-samples.xml">running the REST examples</a></p><h2 id="REST-MappingofRESTtoJMS">Mapping of REST to JMS</h2><p>To publish a message use a HTTP POST. To consume a message use HTTP DELETE or GET.</p><p>ActiveMQ has a Servlet that takes care of the integration between HTTP and the ActiveMQ dispatcher.</p><p><span style="color: rgb(255,153,0);">NOTE: The example below requires servlet mapping on the URL. For posting without the servlet mapping, see examples further down.</span></p><p>You can map a URI to the servlet and then use the relative part of the URI as the topic or queue name. e.g. you could HTTP POST to</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[http://www.acme.com/orders/input
-]]></script>
-</div></div><p>which would publish the contents of the HTTP POST to the orders.input queue on JMS. </p><p>Similarly you could perform a HTTP DELETE GET on the above URL to read from the same queue. In this case we will map the MessageServlet from ActiveMQ to the URI</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[http://www.acme.com/queue
-]]></script>
-</div></div><p>and configure it to accept the URI as a queue destination. We can do similar things to support topic destinations too.</p><p>We can use the HTTP session to denote a unique publisher or consumer.</p><p>Note that strict REST requires that GET be a read only operation; so strictly speaking we should not use GET to allow folks to consume messages. Though we allow this as it simplifies HTTP/DHTML/Ajax integration somewhat.</p><p>For a more cleaner mapping of a simple transfer protocol to different languages, you might wish to take a look at <a shape="rect" href="stomp.xml">Stomp</a>.</p><h2 id="REST-Defaultconfiguration">Default configuration</h2><p>Until version 5.8, REST API was part of the <a shape="rect" href="web-samples.xml">Web Samples</a> and was mapped to <a shape="rect" class="external-link" href="http://localhost:8161/demo/message" rel="nofollow">http://localhost:8161/demo/message</a> url. From 5.8 onwards, the API is available by default at <a shape="rect" class="external-link" href="http://localhost:8161/api/message" rel="nofollow">http://localhost:8161/api/message</a> url. Also, starting with 5.8, web server is secured by default (see <a shape="rect" href="web-console.xml">Web Console</a> for more information), so have that in mind when trying to use it. Examples below will assume new api location and secured web server.</p><h3 id="REST-Producing">Producing</h3><p>You can produce by sending a POST request to the server, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[curl -u admin:admin -d "body=message" http://localhost:8161/api/message/TEST?type=queue]]></script>
-</div></div><p> </p><p><span style="color: rgb(255,153,0);">NOTE: If no type parameter is specified, the default is to create a  topic. To change the default to queue, initialize  the servlet  with an init param in the <code>webapps/demo/WEB-INF/web.xml</code></span></p><p><span style="color: rgb(255,153,0);">As shown below:</span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<servlet>
+<div class="wiki-content maincontent"><p>ActiveMQ implements a RESTful API to messaging which allows any web capable device to publish or consume messages using a regular HTTP POST or GET.</p><p>If you are interested in messaging directly from web browsers you might wanna check out our <link><page ri:content-title="Ajax"></page></link> or <link><page ri:content-title="WebSockets"></page></link> support or try <link><page ri:content-title="Web Samples"></page><plain-text-link-body>running the REST examples</plain-text-link-body></link></p><h2>Mapping of REST to JMS</h2><p>To publish a message use a HTTP POST. To consume a message use HTTP DELETE or GET.</p><p>ActiveMQ has a Servlet that takes care of the integration between HTTP and the ActiveMQ dispatcher.</p><p><span style="color: rgb(255,153,0);">NOTE: The example below requires servlet mapping on the URL. For posting without the servlet mapping, see examples further down.</span></p><p>You can map a URI to the servlet and then use the relative part of the URI as the topic or queue name. e.g. you could HTTP POST to</p><structured-macro ac:macro-id="c3e31109-4566-4337-a87f-0d4e80212900" ac:name="code" ac:schema-version="1"><plain-text-body>http://www.acme.com/orders/input
+</plain-text-body></structured-macro><p>which would publish the contents of the HTTP POST to the orders.input queue on JMS. </p><p>Similarly you could perform a HTTP DELETE GET on the above URL to read from the same queue. In this case we will map the MessageServlet from ActiveMQ to the URI</p><structured-macro ac:macro-id="ce9bcef9-c5d4-4aba-b407-70cc33320dcf" ac:name="code" ac:schema-version="1"><plain-text-body>http://www.acme.com/queue
+</plain-text-body></structured-macro><p>and configure it to accept the URI as a queue destination. We can do similar things to support topic destinations too.</p><p>We can use the HTTP session to denote a unique publisher or consumer.</p><p>Note that strict REST requires that GET be a read only operation; so strictly speaking we should not use GET to allow folks to consume messages. Though we allow this as it simplifies HTTP/DHTML/Ajax integration somewhat.</p><p>For a more cleaner mapping of a simple transfer protocol to different languages, you might wish to take a look at <link><page ri:content-title="Stomp"></page></link>.</p><h2>Default configuration</h2><p>Until version 5.8, REST API was part of the <link><page ri:content-title="Web Samples"></page></link> and was mapped to <a shape="rect" class="external-link" href="http://localhost:8161/demo/message" rel="nofollow">http://localhost:8161/demo/message</a> url. From 5.8 onwards, the API is available by default at <a shape="rect" class="external-link" href="http://localhost:8161/api/message" rel="nofollow">http://localhost:8161/api/message</a> url. Also, starting with 5.8, web server is secured by default (see <link><page ri:content-title="Web Console"></page></link> for more information), so have that in mind when trying to use it. Examples below will assume new api location and secured web server.</p><h3>Producing</h3><p>You can produce by sending a POST request to the server, like</p><structured-macro ac:macro-id="15cc401b-06c0-41d8-9570-0e1ebb7c8104" ac:name="code" ac:schema-version="1"><plain-text-body>curl -u admin:admin -d "body=message" http://localhost:8161/api/message/TEST?type=queue</plain-text-body></structured-macro><p> </p><p><span style="color: rgb(255,153,0);">NOTE: If no type parameter is specified, the default is to create a  topic. To change the default to queue, initialize  the servlet  with an init param in the <code>webapps/demo/WEB-INF/web.xml</code></span></p><p><span style="color: rgb(255,153,0);">As shown below:</span></p><structured-macro ac:macro-id="755e25dd-23f3-47cf-911a-e9ac921d3479" ac:name="code" ac:schema-version="1"><plain-text-body><servlet>
<servlet-name>MessageServlet</servlet-name>
<servlet-class>org.apache.activemq.web.MessageServlet</servlet-class>
<load-on-startup>1</load-on-startup>
@@ -15,18 +8,12 @@
<param-name>topic</param-name>
<param-value>false</param-value>
</init-param>
-</servlet>]]></script>
-</div></div><h4 class="p1" id="REST-AlternateProducingSyntax"><span class="s1">Alternate Producing Syntax</span></h4><p class="p1"><span class="s1">An alternative syntax for posting is supported, using the destination URL-encoded parameter; here are some examples:</span> </p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[# Send to queue orders.input:
-curl -XPOST -d "body=message" http://admin:admin@localhost:8161/api/message?destination=queue://orders.input
+</servlet></plain-text-body></structured-macro><h4 class="p1"><span class="s1">Alternate Producing Syntax</span></h4><p class="p1"><span class="s1">An alternative syntax for posting is supported, using the destination URL-encoded parameter; here are some examples:</span> </p><structured-macro ac:macro-id="9dcfc8f1-019b-4f13-8277-ae4e80d218c3" ac:name="code" ac:schema-version="1"><plain-text-body># Send to queue orders.input:
+curl -XPOST -d "body=message" http://admin:admin@localhost:8161/api/message?destination=queue://orders.input
# Send to topic orders.input:
-curl -XPOST -d "body=message" http://admin:admin@localhost:8161/api/message?destination=topic://orders.input]]></script>
-</div></div><h3 id="REST-Timeouts">Timeouts</h3><p>When reading from a queue we might not have any messages. We can use a timeout query parameter to indicate how long we are prepared to wait for a message to arrive. This allows us to poll or block until a message arrives.</p><p>Couple this with HTTP 1.1 keep-alive sockets and pipeline processing we can have efficient access to JMS over HTTP.</p><p>Obviously if your client is Java then using ActiveMQ's JMS API is the fastest and most efficient way to work with the message broker; however, if you are not using Java or prefer the simplicity of HTTP then it should be fairly efficient, especially if your HTTP client supports keep-alive sockets and pipeline processing.</p><h4 class="p1" id="REST-Consuming"><span style="font-size: 16.0px;line-height: 1.5625;">Consuming</span></h4><p>When consuming messages using the REST API, you have to keep session alive between GET requests, or you'll create a separate consumer for every request and due to prefetch limit your succeeding call will hang.</p><p>For example, you can use <code>wget</code> to consume messages, like this:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[wget --user admin --password admin --save-cookies cookies.txt --load-cookies cookies.txt --keep-session-cookies http://localhost:8161/api/message/TEST1?type=queue
-]]></script>
-</div></div><p>Also, if you plan to have multiple consumer using REST, it's advisable to set prefetch size to 1 so all consumers have an equal chance of getting the message. You can do that by passing a special parameter to the <code>MessageServlet</code></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <servlet>
+curl -XPOST -d "body=message" http://admin:admin@localhost:8161/api/message?destination=topic://orders.input</plain-text-body></structured-macro><h3>Timeouts</h3><p>When reading from a queue we might not have any messages. We can use a timeout query parameter to indicate how long we are prepared to wait for a message to arrive. This allows us to poll or block until a message arrives.</p><p>Couple this with HTTP 1.1 keep-alive sockets and pipeline processing we can have efficient access to JMS over HTTP.</p><p>Obviously if your client is Java then using ActiveMQ's JMS API is the fastest and most efficient way to work with the message broker; however, if you are not using Java or prefer the simplicity of HTTP then it should be fairly efficient, especially if your HTTP client supports keep-alive sockets and pipeline processing.</p><h4 class="p1"><span style="font-size: 16.0px;line-height: 1.5625;">Consuming</span></h4><p>When consuming messages using the REST API, you have to keep session alive between GET requests, or you'll create a separate consumer for every request and due to prefetch limit your succeeding call will hang.</p><p>For example, you can use <code>wget</code> to consume messages, like this:</p><structured-macro ac:macro-id="5baaa5cf-de9f-40c9-b2dc-b381c3a1fd90" ac:name="code" ac:schema-version="1"><plain-text-body>wget --user admin --password admin --save-cookies cookies.txt --load-cookies cookies.txt --keep-session-cookies http://localhost:8161/api/message/TEST1?type=queue
+</plain-text-body></structured-macro><p>Also, if you plan to have multiple consumer using REST, it's advisable to set prefetch size to 1 so all consumers have an equal chance of getting the message. You can do that by passing a special parameter to the <code>MessageServlet</code></p><structured-macro ac:macro-id="1f82d93b-8c78-407e-889b-9511337343db" ac:name="code" ac:schema-version="1"><plain-text-body> <servlet>
<servlet-name>MessageServlet</servlet-name>
<servlet-class>org.apache.activemq.web.MessageServlet</servlet-class>
<load-on-startup>1</load-on-startup>
@@ -35,31 +22,17 @@
<param-value>consumer.prefetchSize=1</param-value>
</init-param>
</servlet>
-]]></script>
-</div></div><p>in the <code>webapps/demo/WEB-INF/web.xml</code></p><h4 class="p1" id="REST-AlternateConsumingSyntax"><span class="s1">Alternate Consuming Syntax</span></h4><p class="p1"><span class="s1">As with producing, an alternative syntax for consuming messages is also supported, using the destination URL-encoded parameter; here are some examples:</span> </p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[# Send to queue orders.input:
+</plain-text-body></structured-macro><p>in the <code>webapps/demo/WEB-INF/web.xml</code></p><h4 class="p1"><span class="s1">Alternate Consuming Syntax</span></h4><p class="p1"><span class="s1">As with producing, an alternative syntax for consuming messages is also supported, using the destination URL-encoded parameter; here are some examples:</span> </p><structured-macro ac:macro-id="6d9e1eb2-9250-41e2-a32d-2aff6a409823" ac:name="code" ac:schema-version="1"><plain-text-body># Send to queue orders.input:
curl -XGET http://admin:admin@localhost:8161/api/message?destination=queue://orders.input
# Send to topic orders.input:
-curl -XGET http://admin:admin@localhost:8161/api/message?destination=topic://orders.input]]></script>
-</div></div><h4 class="p1" id="REST-Consumingwithoutsessions"><span style="font-size: 16.0px;line-height: 1.5625;">Consuming without sessions</span></h4><p>Since 5.2.0 you can use <code>clientId</code> parameter to avoid storing actual JMS consumer in the request session. When using this approach, you don't need to keep sessions alive between requests, you just need to use the same <code>clientId</code> every time.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[wget --user admin --password admin http://localhost:8161/api/message/test?type=queue&clientId=consumerA
-]]></script>
-</div></div><p>Every such call will use the same JMS consumer and deliver messages send to it by the broker.</p><p>In 5.4.1 it's also possible to unsubscribe the client. It's done by sending a POST call with <code>clientId</code> and <code>action=unsubscribe</code> parameters to the server, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[http://localhost:8161/demo/message/test?clientId=consumerA&action=unsubscribe]]></script>
-</div></div><h3 id="REST-Consumingwithselectors">Consuming with selectors</h3><p>As of ActiveMQ 5.4.0, you can use selectors when consuming using REST protocol. To do that, just specify the appropriate header with selector. To define a selector for the consumer, you have to provide it in an appropriate HTTP header. By default selector header name is <code>selector</code>, so the following example</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[wget --user admin --password admin --save-cookies cookies.txt --load-cookies cookies.txt --keep-session-cookies --header="selector: test=2" http://localhost:8161/api/message/test?type=queue
-]]></script>
-</div></div><p>should consume only messages that have <code>test</code> property set to <code>2</code>.</p><p>You can change the name of the selector header using the <code>org.apache.activemq.selectorName</code> Servlet context property in <code>WEB-INF/web.xml</code>, such as</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <context-param>
+curl -XGET http://admin:admin@localhost:8161/api/message?destination=topic://orders.input</plain-text-body></structured-macro><h4 class="p1"><span style="font-size: 16.0px;line-height: 1.5625;">Consuming without sessions</span></h4><p>Since 5.2.0 you can use <code>clientId</code> parameter to avoid storing actual JMS consumer in the request session. When using this approach, you don't need to keep sessions alive between requests, you just need to use the same <code>clientId</code> every time.</p><structured-macro ac:macro-id="fb0668ba-f67a-4c35-a437-fe63da5cd862" ac:name="code" ac:schema-version="1"><plain-text-body>wget --user admin --password admin http://localhost:8161/api/message/test?type=queue&clientId=consumerA
+</plain-text-body></structured-macro><p>Every such call will use the same JMS consumer and deliver messages send to it by the broker.</p><p>In 5.4.1 it's also possible to unsubscribe the client. It's done by sending a POST call with <code>clientId</code> and <code>action=unsubscribe</code> parameters to the server, like</p><structured-macro ac:macro-id="84b289a3-86fe-4d90-b463-47b67945f6ae" ac:name="code" ac:schema-version="1"><plain-text-body>http://localhost:8161/demo/message/test?clientId=consumerA&action=unsubscribe</plain-text-body></structured-macro><h3>Consuming with selectors</h3><p>As of ActiveMQ 5.4.0, you can use selectors when consuming using REST protocol. To do that, just specify the appropriate header with selector. To define a selector for the consumer, you have to provide it in an appropriate HTTP header. By default selector header name is <code>selector</code>, so the following example</p><structured-macro ac:macro-id="b9c43ba1-754c-4e76-a8fd-c3723e33f690" ac:name="code" ac:schema-version="1"><plain-text-body>wget --user admin --password admin --save-cookies cookies.txt --load-cookies cookies.txt --keep-session-cookies --header="selector: test=2" http://localhost:8161/api/message/test?type=queue
+</plain-text-body></structured-macro><p>should consume only messages that have <code>test</code> property set to <code>2</code>.</p><p>You can change the name of the selector header using the <code>org.apache.activemq.selectorName</code> Servlet context property in <code>WEB-INF/web.xml</code>, such as</p><structured-macro ac:macro-id="9e372605-8936-4880-8a8b-437846b22d91" ac:name="code" ac:schema-version="1"><plain-text-body> <context-param>
<param-name>org.apache.activemq.selectorName</param-name>
<param-value>activemq-selector</param-value>
</context-param>
-]]></script>
-</div></div><p>For more info, take a look at <a shape="rect" class="external-link" href="http://fisheye6.atlassian.com/browse/activemq/trunk/activemq-web-demo/src/test/java/org/apache/activemq/web/RestTest.java?r=HEAD" rel="nofollow">RestTest</a></p><h3 id="REST-ConsumingwithOneShotConsumers">Consuming with One Shot Consumers</h3><p>One shot consumption allows a REST call to receive a single message and then immediately close the associated consumer.</p><p>All of the examples so far lead to the servlet creating and holding on to consumers of the destination across multiple HTTP requests. Without care, these consumers could easily lead to confusion as messages are dispatched to them but then sit unused because the consuming HTTP session, or clientId, fails to connect to continue requesting the messages. One way around that problem is the use of one-shot consumers.  Simple add the <code>?oneShot=true</code> option and the consumer is removed once the consumption completes; as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[curl -XGET http://admin:admin@localhost:8161/api/message?destination=queue://orders.input&oneShot=true]]></script>
-</div></div><p>Note that interrupting the call while the consumer is waiting for a message, the consumer may remain until the server times out the HTTP request, or until a message finally arrives.</p><h3 id="REST-ContentTypes">Content Types</h3><p>By default messages are sent to the consumers with <code>text/xml</code> content type. Your REST-based application may expect JSON response instead of XML one. In that case, you can configure the servlet to send responses back by adding something like this</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <servlet>
+</plain-text-body></structured-macro><p>For more info, take a look at <a shape="rect" href="http://fisheye6.atlassian.com/browse/activemq/trunk/activemq-web-demo/src/test/java/org/apache/activemq/web/RestTest.java?r=HEAD">RestTest</a></p><h3>Consuming with One Shot Consumers</h3><p>One shot consumption allows a REST call to receive a single message and then immediately close the associated consumer.</p><p>All of the examples so far lead to the servlet creating and holding on to consumers of the destination across multiple HTTP requests. Without care, these consumers could easily lead to confusion as messages are dispatched to them but then sit unused because the consuming HTTP session, or clientId, fails to connect to continue requesting the messages. One way around that problem is the use of one-shot consumers.  Simple add the <code>?oneShot=true</code> option and the consumer is removed once the consumption completes; as follows:</p><structured-macro ac:macro-id="92667124-da38-4faa-b3c5-7f664ca05963" ac:name="code" ac:schema-version="1"><plain-text-body>curl -XGET http://admin:admin@localhost:8161/api/message?destination=queue://orders.input&oneShot=true</plain-text-body></structured-macro><p>Note that interrupting the call while the consumer is waiting for a message, the consumer may remain until the server times out the HTTP request, or until a message finally arrives.</p><h3>Content Types</h3><p>By default messages are sent to the consumers with <code>text/xml</code> content type. Your REST-based application may expect JSON response instead of XML one. In that case, you can configure the servlet to send responses back by adding something like this</p><structured-macro ac:macro-id="27c27645-a0fb-4875-a67a-cf5866fee82b" ac:name="code" ac:schema-version="1"><plain-text-body> <servlet>
<servlet-name>MessageServlet</servlet-name>
<servlet-class>org.apache.activemq.web.MessageServlet</servlet-class>
<load-on-startup>1</load-on-startup>
@@ -68,28 +41,13 @@
<param-value>application/json</param-value>
</init-param>
</servlet>
-]]></script>
-</div></div><p>to your <code>WEB-INF/web.xml</code>.</p><p>A default content type can also be overridden using request headers. Specifying <code>xml=true</code> or <code>json=true</code> URL parameter you'll get a response with the desired content type.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[wget --user admin --password admin http://localhost:8161/api/message/TEST?type=queue\&clientId=A\&json=true]]></script>
-</div></div><h3 id="REST-Security">Security</h3><p>Since 5.7.0 release REST API can connect to the secured brokers. The API uses basic authentication header format to get username and password information.</p><p>For example, with curl you can do something like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[curl -u system:manager -d "body=message" http://localhost:8161/demo/message/TEST?type=queue]]></script>
-</div></div><p>Also, you might want to enable <code>ssl</code> for your connections. To do that, just uncomment SecureConnector in <code>conf/jetty.xml</code></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <bean id="SecureConnector" class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
- <property name="port" value="8162" />
- <property name="keystore" value="file:${activemq.conf}/broker.ks" />
- <property name="password" value="password" />
- </bean>]]></script>
-</div></div><h2 id="REST-RestManagement">Rest Management</h2><p>Starting with version 5.8 we provide a REST management API for the broker. Using <a shape="rect" class="external-link" href="http://www.jolokia.org/" rel="nofollow">Jolokia</a> JMX-HTTP bridge it's possible to access all broker metrics (like memory usage) and execute management operations (like purging queues) using REST API. By default the management API is exposed at <a shape="rect" class="external-link" href="http://localhost:8161/api/jolokia/" rel="nofollow">http://localhost:8161/api/jolokia/</a> URL. So you can for example get basic broker data with</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[wget --user admin --password admin --auth-no-challenge http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost]]></script>
-</div></div><p>or to be more specific, total consumer count with</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[wget --user admin --password admin --auth-no-challenge http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost/TotalConsumerCount]]></script>
-</div></div><p>For more information on Jolokia protocol, see its reference manual. An API like this makes it easy to script monitoring and management operations against the broker, see also <a shape="rect" href="how-can-i-monitor-activemq.xml">How can I monitor ActiveMQ</a>?</p><h2 id="REST-Gotcha'sandothertrivia">Gotcha's and other trivia</h2><ol><li>Missing "body" parameter</li></ol><p style="margin-left: 90.0px;">In the curl POST examples above, the use of "body=..." is critical. If this is not specified in front of the message body contents, the web servlet will attempt to read the body from the request (rather than from the -d parameter), and this will result in the following exception:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[java.lang.IllegalStateException: STREAMED
+</plain-text-body></structured-macro><p>to your <code>WEB-INF/web.xml</code>.</p><p>A default content type can also be overridden using request headers. Specifying <code>xml=true</code> or <code>json=true</code> URL parameter you'll get a response with the desired content type.</p><structured-macro ac:macro-id="c2b26994-ed0e-4a69-8d75-d1ac50b78dad" ac:name="code" ac:schema-version="1"><plain-text-body>wget --user admin --password admin http://localhost:8161/api/message/TEST?type=queue\&clientId=A\&json=true</plain-text-body></structured-macro><h3>Security</h3><p>Since 5.7.0 release REST API can connect to the secured brokers. The API uses basic authentication header format to get username and password information.</p><p>For example, with curl you can do something like</p><structured-macro ac:macro-id="e1169b07-d531-4ff6-99be-f93af72839a9" ac:name="code" ac:schema-version="1"><plain-text-body>curl -u system:manager -d "body=message" http://localhost:8161/demo/message/TEST?type=queue</plain-text-body></structured-macro><p>Also, you might want to enable <code>ssl</code> for your connections. To do that, just uncomment SecureConnector in <code>conf/jetty.xml</code></p><structured-macro ac:macro-id="d77b0a9d-152d-468f-8269-75ce924d08c4" ac:name="code" ac:schema-version="1"><plain-text-body> <bean id="SecureConnector" class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
+ <property name="port" value="8162" />
+ <property name="keystore" value="file:${activemq.conf}/broker.ks" />
+ <property name="password" value="password" />
+ </bean></plain-text-body></structured-macro><h2>Rest Management</h2><p>Starting with version 5.8 we provide a REST management API for the broker. Using <a shape="rect" href="http://www.jolokia.org/">Jolokia</a> JMX-HTTP bridge it's possible to access all broker metrics (like memory usage) and execute management operations (like purging queues) using REST API. By default the management API is exposed at <a shape="rect" class="external-link" href="http://localhost:8161/api/jolokia/" rel="nofollow">http://localhost:8161/api/jolokia/</a> URL. So you can for example get basic broker data with</p><structured-macro ac:macro-id="756c35b2-1331-4db0-9362-374edd630e41" ac:name="code" ac:schema-version="1"><plain-text-body>wget --user admin --password admin --auth-no-challenge http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost</plain-text-body></structured-macro><p>or to be more specific, total consumer count with</p><structured-macro ac:macro-id="a67c2a02-e85f-4542-a10f-920558715997" ac:name="code" ac:schema-version="1"><plain-text-body>wget --user admin --password admin --auth-no-challenge http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost/TotalConsumerCount</plain-text-body></structured-macro><p>For more information on Jolokia protocol, see its reference manual. An API like this makes it easy to script monitoring and management operations against the broker, see also <link><page ri:content-title="How can I monitor ActiveMQ"></page></link>?</p><h2>Gotcha's and other trivia</h2><ol><li>Missing "body" parameter</li></ol><p style="margin-left: 90.0px;">In the curl POST examples above, the use of "body=..." is critical. If this is not specified in front of the message body contents, the web servlet will attempt to read the body from the request (rather than from the -d parameter), and this will result in the following exception:</p><structured-macro ac:macro-id="4d227c07-3d94-4e1d-b1d2-ccffa88b5fc8" ac:name="code" ac:schema-version="1"><plain-text-body>java.lang.IllegalStateException: STREAMED
at org.eclipse.jetty.server.Request.getReader(Request.java:898)
at org.apache.activemq.web.MessageServletSupport.getPostedMessageBody(MessageServletSupport.java:347)
at org.apache.activemq.web.MessageServlet.doPost(MessageServlet.java:126)
-...]]></script>
-</div></div><p style="margin-left: 90.0px;">However, one option in this case would be to specify the content type explicitly:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[curl -u admin:admin -d "hello world $(date)" -H "Content-Type: text/plain" -XPOST http://localhost:8161/api/message?destination=queue://abc.def]]></script>
-</div></div></div>
+...</plain-text-body></structured-macro><p style="margin-left: 90.0px;">However, one option in this case would be to specify the content type explicitly:</p><structured-macro ac:macro-id="75b549c1-79fa-4b39-bd8e-855732a103b3" ac:name="code" ac:schema-version="1"><plain-text-body>curl -u admin:admin -d "hello world $(date)" -H "Content-Type: text/plain" -XPOST http://localhost:8161/api/message?destination=queue://abc.def</plain-text-body></structured-macro></div>
diff --git a/restful-queue.xml b/restful-queue.xml
index a8c7027..72b20a1 100644
--- a/restful-queue.xml
+++ b/restful-queue.xml
@@ -1,196 +1,175 @@
-<div class="wiki-content maincontent"><h2 id="RESTfulQueue-RESTfulQueue">RESTful Queue</h2>
+<div class="wiki-content maincontent"><h2>RESTful Queue</h2>
<p>This document is intended to document the ideal RESTful interface to message queues in light of</p>
-<ul><li><a shape="rect" class="external-link" href="http://tech.groups.yahoo.com/group/rest-discuss/message/8955" rel="nofollow">the discussion on rest-discuss</a></li><li><a shape="rect" class="external-link" href="http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-17.html" rel="nofollow">Atom Publishing Protocol</a> (APP)</li><li><a shape="rect" class="external-link" href="http://www.dehora.net/doc/httplr/draft-httplr-01.html" rel="nofollow">httplr</a></li></ul>
+<ul><li><a shape="rect" href="http://tech.groups.yahoo.com/group/rest-discuss/message/8955">the discussion on rest-discuss</a></li><li><a shape="rect" href="http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-17.html">Atom Publishing Protocol</a> (APP)</li><li><a shape="rect" href="http://www.dehora.net/doc/httplr/draft-httplr-01.html">httplr</a></li></ul>
-<h3 id="RESTfulQueue-IssueswithQueuesandREST">Issues with Queues and REST</h3>
+<h3>Issues with Queues and REST</h3>
<p>One of the main issues with making a truly RESTful API to a message queue is that a message queue is essentially a load balancer, so each consumer of a queue sees essentially a different queue; as only one consumer gets a copy of each message.</p>
<p>Also if a consumer goes away, the messages that were associated with that consumer need to be re-assigned to another consumer. So the main tricky part really is the operation for a consumer to find out what messages it may consume.</p>
-<h3 id="RESTfulQueue-Queueadministration">Queue administration</h3>
+<h3>Queue administration</h3>
<p>This section deals with the general browsing and creation/deletion of queues.</p>
-<h4 id="RESTfulQueue-Browseavailablequeues">Browse available queues</h4>
+<h4>Browse available queues</h4>
<p>To browse the queues, they are a hierarchial structure usually, so lets browse them like any APP collection</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3fa761d7-8cd8-4f8c-83b8-a2b1668580a4" ac:name="code" ac:schema-version="1"><plain-text-body>
GET /queues
-------------------->
200 OK
Atom Feed with one entry per directory/category/queue
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="RESTfulQueue-Browseaqueue'smessages">Browse a queue's messages</h4>
+<h4>Browse a queue's messages</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="1bf2b8f7-f81e-4248-8e19-1e9fd926097a" ac:name="code" ac:schema-version="1"><plain-text-body>
GET /queues/uk/products/books/computers
-------------------->
200 OK
Atom Feed with one entry per pending message
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Note that we could expose the queues as a tree, for example</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9e54d0a4-4970-4724-a2f9-a6f0d29def2d" ac:name="code" ac:schema-version="1"><plain-text-body>
GET /queues/uk/products
-------------------->
200 OK
Atom Feed with one entry per queue in uk.products.* together with any child catgory/directory
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="RESTfulQueue-Creatingaqueue">Creating a queue</h4>
+<h4>Creating a queue</h4>
<p>Creating a queue is typically idempotent; since really you are just creating a name that folks can post to.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="75a802e6-2ef3-4091-81ed-000610653001" ac:name="code" ac:schema-version="1"><plain-text-body>
POST /queues
-------------------->
201 OK
Location: someUniqueUrlForTheNewQueueToBePostedTo
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="RESTfulQueue-Deletingaqueue">Deleting a queue</h4>
+<h4>Deleting a queue</h4>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="346b40b2-c328-4458-b4ea-26a176422a1a" ac:name="code" ac:schema-version="1"><plain-text-body>
DELETE /queues/foo.bar
-------------------->
200 OK
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="RESTfulQueue-Sendtoqueue">Send to queue</h3>
+<h3>Send to queue</h3>
<p>Sending to queue is the usual APP-style double request; one to get the unique URI to post to and secondly to do the actual post...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6f2ef332-dfeb-4e45-9d03-c204a1a7bd72" ac:name="code" ac:schema-version="1"><plain-text-body>
POST /queues/foo.bar
-------------------->
201 OK
Location: someUniqueUrlForTheNewMessageToBePostedTo
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The client can then repeatedly POST the mesage to someUniqueUrlForTheNewMessageToBePostedTo until it gets a 200 OK which avoids duplicates.</p>
-<h4 id="RESTfulQueue-Optionalalternativeforsinglerequest">Optional alternative for single request</h4>
+<h4>Optional alternative for single request</h4>
<p>If a smart client is capable of generating a system wide unique GUID (id) for the message, the server side could ignore duplicates. So posting to queue could be done without the double-request approach above</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="dc797621-e532-4c96-a49e-2a20bcb948af" ac:name="code" ac:schema-version="1"><plain-text-body>
POST /queues/foo.bar?guid=clientGeneratedUniqueId
-------------------->
200 OK
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="RESTfulQueue-Consumingfromaqueue">Consuming from a queue</h3>
+<h3>Consuming from a queue</h3>
<p>As described above, this is the tricky part of mapping message queues to REST. </p>
<p>So we introduce a resource for a <em>subscription</em> to a queue. The subscription remains active until some timeout value - so a subscription is a sort of lease.</p>
<p>When a subscription is created it can be given a variety of different pieces of data such as </p>
-<ul><li>the <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch buffer</a></li><li>what destinations it applies to (for example we could use wildcards)</li><li>whether a selector/filter is applied</li></ul>
+<ul><li>the <link><page ri:content-title="What is the Prefetch Limit For?"></page><link-body>prefetch buffer</link-body></link></li><li>what destinations it applies to (for example we could use wildcards)</li><li>whether a selector/filter is applied</li></ul>
-<h4 id="RESTfulQueue-Createasubscription">Create a subscription</h4>
+<h4>Create a subscription</h4>
- <div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+ <structured-macro ac:macro-id="d49de1c7-6395-4df3-8699-dab96e796744" ac:name="code" ac:schema-version="1"><plain-text-body>
POST /subscriptions
-------------------->
201 OK
Location: subscriptionUri
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The actual subscription data could be form encoded key/value pairs.</p>
-<h4 id="RESTfulQueue-Deletingasubscription">Deleting a subscription</h4>
+<h4>Deleting a subscription</h4>
<p>Good clients will delete subscriptions when they are no longer required; though they do timeout eventually.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6badd40e-e6f3-4b2c-af45-6ee2c6a8db8d" ac:name="code" ac:schema-version="1"><plain-text-body>
DELETE subscriptionUri
-------------------->
200 OK
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="RESTfulQueue-Consumingmessages">Consuming messages</h4>
+<h4>Consuming messages</h4>
<p>You consume messages by browsing the subscription (like any APP resource) then DELETEing the message when you have finished processing it.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="bfb180ae-ec58-4f0d-a60f-0467b961cf5f" ac:name="code" ac:schema-version="1"><plain-text-body>
GET subscriptionUri
-------------------->
200 OK
Atom Feed with one entry per message associated to this subscription
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Then to acknowledge a particular message has been processed</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2b9a473f-a596-45c3-9d91-d25aca26d9c2" ac:name="code" ac:schema-version="1"><plain-text-body>
DELETE messageUri
-------------------->
200 OK
<--------------------
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="RESTfulQueue-DeltaswithAPP">Deltas with APP</h2>
+<h2>Deltas with APP</h2>
<p>Almost all of the above could be just pure APP really. The only real difference is that each consumer has its own feed of messages which are to be consumed. </p>
-<p>In ActiveMQ's case, we use a <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch value per consumer</a> to define how many messages each consumer gets in its buffer, before messages must be acknowledged to get more messages.</p>
+<p>In ActiveMQ's case, we use a <link><page ri:content-title="What is the Prefetch Limit For?"></page><link-body>prefetch value per consumer</link-body></link> to define how many messages each consumer gets in its buffer, before messages must be acknowledged to get more messages.</p>
<p>So the idea is that we have a per-consumer feed which is created; it can then be browsed (by anyone with sufficient karma).</p>
+
</div>
diff --git a/retroactive-consumer.xml b/retroactive-consumer.xml
index e6bc50a..9c29383 100644
--- a/retroactive-consumer.xml
+++ b/retroactive-consumer.xml
@@ -1,21 +1,19 @@
-<div class="wiki-content maincontent"><h2 id="RetroactiveConsumer-Background">Background</h2>
+<div class="wiki-content maincontent"><h2>Background</h2>
<p>A retroactive consumer is just a regular JMS <strong>Topic</strong> consumer who indicates that at the start of a subscription every attempt should be used to go back in time and send any old messages (or the last message sent on that topic) that the consumer may have missed.</p>
-<p>See the <a shape="rect" href="subscription-recovery-policy.xml">Subscription Recovery Policy</a> for more detail.</p>
+<p>See the <link><page ri:content-title="Subscription Recovery Policy"></page></link> for more detail.</p>
-<h3 id="RetroactiveConsumer-Example">Example</h3>
+<h3>Example</h3>
<p>You mark a Consumer as being retroactive as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-topic = new ActiveMQTopic("TEST.Topic?consumer.retroactive=true");
+<structured-macro ac:macro-id="462c0993-e6fb-4e86-84d7-558eaea7c411" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
+topic = new ActiveMQTopic("TEST.Topic?consumer.retroactive=true");
consumer = session.createConsumer(topic);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="RetroactiveConsumer-Limitations">Limitations</h2>
+<h2>Limitations</h2>
<p>Retroactive consumer will not consistently work when used across a network of brokers.</p>
diff --git a/rss-and-atom.xml b/rss-and-atom.xml
index 949c8f0..6fd633e 100644
--- a/rss-and-atom.xml
+++ b/rss-and-atom.xml
@@ -1,17 +1,18 @@
<div class="wiki-content maincontent">
-<p>We have added support for the <a shape="rect" href="rest.xml">REST</a>ful browsing of message queues in the <strong>activemq-web</strong> module. To try out this feature try the <a shape="rect" href="web-samples.xml">Web Samples</a>.</p>
+<p>We have added support for the <link><page ri:content-title="REST"></page></link>ful browsing of message queues in the <strong>activemq-web</strong> module. To try out this feature try the <link><page ri:content-title="Web Samples"></page></link>.</p>
<p>Browsing of queues is implemented by a servlet, <strong>QueueBrowseServlet</strong> which allows queues to be browsed using pluggable views. The current views supported are</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>View name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>simple</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Renders a list of <message> elements with an id attribute</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>xml</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses XStream to render the entire messages as XML</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>rss</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses <a shape="rect" class="external-link" href="https://rome.dev.java.net/" rel="nofollow">Rome</a> to render the messages as an RSS 0.9*, 1.0, 2.0 or Atom 0.3 feed. You can configure the type of feed using the <strong>feedType</strong></p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>View name</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>simple</p></td><td colspan="1" rowspan="1"><p>Renders a list of <message> elements with an id attribute</p></td></tr><tr><td colspan="1" rowspan="1"><p>xml</p></td><td colspan="1" rowspan="1"><p>Uses XStream to render the entire messages as XML</p></td></tr><tr><td colspan="1" rowspan="1"><p>rss</p></td><td colspan="1" rowspan="1"><p>Uses <a shape="rect" href="https://rome.dev.java.net/">Rome</a> to render the messages as an RSS 0.9*, 1.0, 2.0 or Atom 0.3 feed. You can configure the type of feed using the <strong>feedType</strong></p></td></tr></tbody></table>
<p>Any properties on the view objects can be configured via reflection using query parameters. e.g. you can specify these common properties</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>contentType</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Override the MIME content type of the view</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maxMessages</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of messages to render</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Parameter</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>contentType</p></td><td colspan="1" rowspan="1"><p>Override the MIME content type of the view</p></td></tr><tr><td colspan="1" rowspan="1"><p>maxMessages</p></td><td colspan="1" rowspan="1"><p>The maximum number of messages to render</p></td></tr></tbody></table>
-<h3 id="RSSandAtom-Examples">Examples</h3>
+<h3>Examples</h3>
-<ul><li><a shape="rect" class="external-link" href="http://localhost:8080/queueBrowse/FOO/BAR?view=xml" rel="nofollow">http://localhost:8080/queueBrowse/FOO/BAR?view=xml</a> will browse the queue as XML</li><li><a shape="rect" class="external-link" href="http://localhost:8080/queueBrowse/FOO/BAR?view=rss&feedType=rss_2.0" rel="nofollow">http://localhost:8080/queueBrowse/FOO/BAR?view=rss&feedType=rss_2.0</a> will browse the FOO.BAR queue using RSS 2.0</li><li><a shape="rect" class="external-link" href="http://localhost:8080/queueBrowse/FOO/BAR?view=rss&feedType=atom_0.3" rel="nofollow">http://localhost:8080/queueBrowse/FOO/BAR?view=rss&feedType=atom_0.3</a> will browse the FOO.BAR queue using Atom</li></ul></div>
+<ul><li><a shape="rect" class="external-link" href="http://localhost:8080/queueBrowse/FOO/BAR?view=xml" rel="nofollow">http://localhost:8080/queueBrowse/FOO/BAR?view=xml</a> will browse the queue as XML</li><li><a shape="rect" class="external-link" href="http://localhost:8080/queueBrowse/FOO/BAR?view=rss&feedType=rss_2.0" rel="nofollow">http://localhost:8080/queueBrowse/FOO/BAR?view=rss&feedType=rss_2.0</a> will browse the FOO.BAR queue using RSS 2.0</li><li><a shape="rect" class="external-link" href="http://localhost:8080/queueBrowse/FOO/BAR?view=rss&feedType=atom_0.3" rel="nofollow">http://localhost:8080/queueBrowse/FOO/BAR?view=rss&feedType=atom_0.3</a> will browse the FOO.BAR queue using Atom</li></ul>
+</div>
diff --git a/run-broker.xml b/run-broker.xml
index 0c3967c..684636c 100644
--- a/run-broker.xml
+++ b/run-broker.xml
@@ -1,11 +1,5 @@
-<div class="wiki-content maincontent"><h1 id="RunBroker-RunninganActiveMQBroker">Running an ActiveMQ Broker</h1><p>Note if you want to use an <strong>embedded broker</strong> then see <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></p><p>This page describes how to run a broker using 4.x or later of ActiveMQ.</p><h3 id="RunBroker-RunningthebrokerasaUnixService">Running the broker as a Unix Service</h3><p class="confluence-link">See the  <a shape="rect" href="unix-shell-script.xml">Unix Shell Script</a> for details.</p><h3 id="RunBroker-RunningthebrokerusingtheJavaServiceWrapperImplementation">Running the broker using the Java Service Wrapper Implementation</h3><p>See the <a shape="rect" href="java-service-wrapper.xml">Java Service Wrapper Page</a> for details.</p><h3 id="RunBroker-Monitoringthebroker">Monitoring the broker</h3><p>You can monitor ActiveMQ using the <a shape="rect" href="web-console.xml">Web Console</a> by pointing your browser at</p><p><a shape="rect" class="external-link" href="http://localhost:8161/admin" rel="nofollow">http://localhost:8161/admin</a></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>From ActiveMQ 5.8 onwards the web apps is secured out of the box.<br clear="none"> The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.</p></div></div><p>Or you can use the <a shape="rect" href="jmx.xml">JMX</a> support to view the running state of ActiveMQ.</p><p>For more information see the file <code>docs/WebConsole-README.txt</code> in the distribution.</p><h3 id="RunBroker-RunningthebrokerinsideaServletEngine">Running the broker inside a Servlet Engine</h3><p>See the source code (or WAR) of the <a shape="rect" href="web-console.xml">Web Console</a> for an example of how to run the broker inside a web application using Spring.</p><h3 id="RunBroker-RunningthebrokerinsideyourJ2EE1.4ApplicationServer">Running the broker inside your J2EE 1.4 Application Server</h3><p>Whether its Apache Geronmio, JBoss 4, WebLogic 9 or some other J2EE 1.4 container you should be able to just reconfigure and then deploy the activemq-*.rar which is included in the binary distribution as a deployment unit in your app server. By default the rar is not configured to start an embedded broker. But by setting the brokerXmlConfig on the resource adapter configuration, the resource adapter will start an embedded broker.</p><p>For more details see <a shape="rect" href="j2ee.xml">J2EE</a></p><h3 id="RunBroker-Runningthebrokerfromthesourcecode">Running the broker from the source code</h3><p>From the latest <a shape="rect" href="source.xml">checkout</a> of the code you can run a broker using the <a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Plugin</a></p><h3 id="RunBroker-Runningthebrokerfrommaven">Running the broker from maven</h3><p>You can download and install the ActiveMQ Startup Maven Plugin via the following command if you are in a directory with a pom.xml. More detailed usage <a shape="rect" href="maven2-activemq-broker-plugin.xml">here</a></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn org.apache.activemq.tooling:maven-activemq-plugin:5.0-SNAPSHOT:run
-]]></script>
-</div></div><p>You can also include it the pom and run it using:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn activemq:run
-]]></script>
-</div></div><h2 id="RunBroker-HandlingJMSbrokersgoingdown">Handling JMS brokers going down</h2><p>A common requirement is that if the JMS broker goes down you want to automatically detect the failure and try to reconnect under the covers so that your application does not have to worry about reconnection.</p><p>There is detailed documentation on this in <a shape="rect" href="configuring-transports.xml">Configuring Transports</a>; briefly...</p><p>Just change your connection URI in 4.x to</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[failover:tcp://host:port
-]]></script>
-</div></div><p>And the JMS client will auto-reconnect to the broker if it is shutdown and restarted later on.</p></div>
+<div class="wiki-content maincontent"><h1>Running an ActiveMQ Broker</h1><p>Note if you want to use an <strong>embedded broker</strong> then see <link><page ri:content-title="How do I embed a Broker inside a Connection"></page></link></p><p>This page describes how to run a broker using 4.x or later of ActiveMQ.</p><h3>Running the broker as a Unix Service</h3><p class="confluence-link">See the  <link><page ri:content-title="Unix Shell Script"></page></link> for details.</p><h3>Running the broker using the Java Service Wrapper Implementation</h3><p>See the <link><page ri:content-title="Java Service Wrapper"></page><plain-text-link-body>Java Service Wrapper Page</plain-text-link-body></link> for details.</p><h3>Monitoring the broker</h3><p><structured-macro ac:macro-id="f323e9fa-3807-41d2-8105-cef766188784" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Monitoring ActiveMQ"></page></link></parameter></structured-macro></p><h3>Running the broker inside a Servlet Engine</h3><p>See the source code (or WAR) of the <link><page ri:content-title="Web Console"></page></link> for an example of how to run the broker inside a web application using Spring.</p><h3>Running the broker inside your J2EE 1.4 Application Server</h3><p>Whether its Apache Geronmio, JBoss 4, WebLogic 9 or some other J2EE 1.4 container you should be able to just reconfigure and then deploy the activemq-*.rar which is included in the binary distribution as a deployment unit in your app server. By default the rar is not configured to start an embedded broker. But by setting the brokerXmlConfig on the resource adapter configuration, the resource adapter will start an embedded broker.</p><p>For more details see <link><page ri:content-title="J2EE"></page></link></p><h3>Running the broker from the source code</h3><p>From the latest <link><page ri:content-title="Source"></page><plain-text-link-body>checkout</plain-text-link-body></link> of the code you can run a broker using the <link><page ri:content-title="ActiveMQ Performance Module Users Manual"></page><plain-text-link-body>ActiveMQ Performance Plugin</plain-text-link-body></link></p><h3>Running the broker from maven</h3><p>You can download and install the ActiveMQ Startup Maven Plugin via the following command if you are in a directory with a pom.xml. More detailed usage <link><page ri:content-title="Maven2 ActiveMQ Broker Plugin"></page><plain-text-link-body>here</plain-text-link-body></link></p><structured-macro ac:macro-id="216ea735-8cdd-4322-ac8b-ad8829396ff8" ac:name="code" ac:schema-version="1"><plain-text-body>mvn org.apache.activemq.tooling:maven-activemq-plugin:5.0-SNAPSHOT:run
+</plain-text-body></structured-macro><p>You can also include it the pom and run it using:</p><structured-macro ac:macro-id="3d8a1a6a-2884-4381-9b31-256988a19897" ac:name="code" ac:schema-version="1"><plain-text-body>mvn activemq:run
+</plain-text-body></structured-macro><h2>Handling JMS brokers going down</h2><p>A common requirement is that if the JMS broker goes down you want to automatically detect the failure and try to reconnect under the covers so that your application does not have to worry about reconnection.</p><p>There is detailed documentation on this in <link><page ri:content-title="Configuring Transports"></page></link>; briefly...</p><p>Just change your connection URI in 4.x to</p><structured-macro ac:macro-id="aaf9c28a-8b93-4338-87fb-7326c5c154b9" ac:name="code" ac:schema-version="1"><plain-text-body>failover:tcp://host:port
+</plain-text-body></structured-macro><p>And the JMS client will auto-reconnect to the broker if it is shutdown and restarted later on.</p></div>
diff --git a/runtime-configuration.xml b/runtime-configuration.xml
index 9e652a9..beeb1d3 100644
--- a/runtime-configuration.xml
+++ b/runtime-configuration.xml
@@ -4,15 +4,13 @@
The addition of a new store could entail a new network connector and some new authorization policies, both of which can now be modified on the fly.</p>
<p>The plugin is configured via the broker xml configuration as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker xmlns="http://activemq.apache.org/schema/core" start="false" ... >
+<structured-macro ac:macro-id="2e5295a6-1d1e-45bc-9bdf-81324f278474" ac:name="code" ac:schema-version="1"><plain-text-body><broker xmlns="http://activemq.apache.org/schema/core" start="false" ... >
<plugins>
- <runtimeConfigurationPlugin checkPeriod="1000" />
+ <runtimeConfigurationPlugin checkPeriod="1000" />
</plugins>
...
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Note: the start="false" attribute. It ensures that xbean-spring does not auto start the broker when the application context is loading. <br clear="none">
This ensures that the plugins reference to the broker is fully initialized before it is used and the xml configuration location can be successfully resolved.</p>
@@ -24,5 +22,5 @@
-<p>Some more implementation detail and links to the tests can be found in <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4682">AMQ-4682</a></p></div>
+<p>Some more implementation detail and links to the tests can be found in <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-4682">AMQ-4682</a></p></div>
diff --git a/sample-camel-routes.xml b/sample-camel-routes.xml
index ddc41a4..25aa11f 100644
--- a/sample-camel-routes.xml
+++ b/sample-camel-routes.xml
@@ -1,40 +1,39 @@
-<div class="wiki-content maincontent"><h3 id="SampleCamelRoutes-ExampleofaconfigurationthatshowhowtouseCamelrouteswithJuelandXpath.">Example of a configuration that show how to use Camel routes with Juel and Xpath.</h3>
+<div class="wiki-content maincontent"><h3>Example of a configuration that show how to use Camel routes with Juel and Xpath.</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="41ae1a77-7a67-4919-a2be-1f5d0e54506c" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<beans>
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
- brokerName="localhost" dataDirectory="${activemq.base}/data">
+ <broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0"
+ brokerName="localhost" dataDirectory="${activemq.base}/data">
</broker>
- <camelContext id="camel" xmlns="http://activemq.apache.org/camel/schema/spring">
+ <camelContext id="camel" xmlns="http://activemq.apache.org/camel/schema/spring">
<!-- simple bridge from a topic to queue -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming">
- <to uri="activemq:queue:queue.HelloWorld">
+ <from uri="activemq:topic:topic.HelloWorld.incoming">
+ <to uri="activemq:queue:queue.HelloWorld">
</route>
<!-- Dependencies: camel-juel-[camel-n].jar, juel-[juel-n]-impl.jar, juel-[juel-n].jar must be in the activemq lib directory -->
<!-- 2 separate JUEL based filters -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming.camel1">
+ <from uri="activemq:topic:topic.HelloWorld.incoming.camel1">
<filter>
- <el>${in.headers.JMSType.equals('foo')}</el>
+ <el>${in.headers.JMSType.equals('foo')}</el>
<filter>
- <el>${in.headers.myHeaderField.equals('takeMe')}</el>
- <to uri="activemq:queue:queue.HelloWorld.camel1.fooMsgs">
+ <el>${in.headers.myHeaderField.equals('takeMe')}</el>
+ <to uri="activemq:queue:queue.HelloWorld.camel1.fooMsgs">
</filter>
</filter>
<filter>
- <el>${in.headers.JMSType.equals('bar')}</el>
+ <el>${in.headers.JMSType.equals('bar')}</el>
<filter>
- <el>${in.headers.myHeaderField.equals('takeMe')}</el>
+ <el>${in.headers.myHeaderField.equals('takeMe')}</el>
<filter>
- <el>${in.headers.myOtherHeaderField.equals('3')}</el>
- <to uri="activemq:queue:queue.HelloWorld.camel1.fooMsgs.special">
+ <el>${in.headers.myOtherHeaderField.equals('3')}</el>
+ <to uri="activemq:queue:queue.HelloWorld.camel1.fooMsgs.special">
</filter>
</filter>
</filter>
@@ -43,28 +42,28 @@
<!-- route using 2 separate xpath based filters, assuming the message has an XML body -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming.camel2">
+ <from uri="activemq:topic:topic.HelloWorld.incoming.camel2">
<filter>
- <xpath>$JMSType = 'foo' and $myCustomHeader='takeMe'</xpath>
- <to uri="activemq:queue:queue.HelloWorld.camel2.fooMsgs">
+ <xpath>$JMSType = 'foo' and $myCustomHeader='takeMe'</xpath>
+ <to uri="activemq:queue:queue.HelloWorld.camel2.fooMsgs">
</filter>
<filter>
- <xpath>$JMSType = 'bar' and $myCustomHeader='takeMe'</xpath>
- <to uri="activemq:queue:queue.HelloWorld.camel2.barMsgs">
+ <xpath>$JMSType = 'bar' and $myCustomHeader='takeMe'</xpath>
+ <to uri="activemq:queue:queue.HelloWorld.camel2.barMsgs">
</filter>
</route>
<!-- route using choice route based on xpath -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming.camel3">
+ <from uri="activemq:topic:topic.HelloWorld.incoming.camel3">
<choice>
<when>
- <xpath>$JMSType = 'foo'</xpath>
- <to uri="activemq:queue:queue.HelloWorld.camel3.fooMsgs">
+ <xpath>$JMSType = 'foo'</xpath>
+ <to uri="activemq:queue:queue.HelloWorld.camel3.fooMsgs">
</when>
<otherwise>
- <to uri="activemq:queue:queue.HelloWorld.camel3.nonFooMsgs">
+ <to uri="activemq:queue:queue.HelloWorld.camel3.nonFooMsgs">
</otherwise>
</choice>
</route>
@@ -72,11 +71,11 @@
<!-- route using choice route based on JUEL -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming.camel4">
+ <from uri="activemq:topic:topic.HelloWorld.incoming.camel4">
<choice>
<when>
- <el>${in.headers.JMSType.equals('foo')}</el>
- <to uri="activemq:queue:queue.HelloWorld.camel4.fooMsgs">
+ <el>${in.headers.JMSType.equals('foo')}</el>
+ <to uri="activemq:queue:queue.HelloWorld.camel4.fooMsgs">
</when>
</choice>
</route>
@@ -84,16 +83,16 @@
<!-- route using nested JUEL based filters -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming.camel5">
+ <from uri="activemq:topic:topic.HelloWorld.incoming.camel5">
<filter>
- <el>${in.headers.JMSType.equals('foo')}</el>
+ <el>${in.headers.JMSType.equals('foo')}</el>
<filter>
- <el>${in.headers.OperationRequest.equals('foo1')}</el>
- <to uri="activemq:queue:queue.HelloWorld.camel5.foo1Msgs">
+ <el>${in.headers.OperationRequest.equals('foo1')}</el>
+ <to uri="activemq:queue:queue.HelloWorld.camel5.foo1Msgs">
</filter>
<filter>
- <el>${in.headers.OperationRequest.equals('foo2')}</el>
- <to uri="activemq:queue:queue.HelloWorld.camel5.foo2Msgs">
+ <el>${in.headers.OperationRequest.equals('foo2')}</el>
+ <to uri="activemq:queue:queue.HelloWorld.camel5.foo2Msgs">
</filter>
</filter>
</route>
@@ -101,12 +100,12 @@
<!-- route using nested JUEL and xpath filters, including a filter which examines the message content for an xml attribute -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming.camel6">
+ <from uri="activemq:topic:topic.HelloWorld.incoming.camel6">
<filter>
- <el>${in.headers.JMSType.equals('foo')}</el>
+ <el>${in.headers.JMSType.equals('foo')}</el>
<filter>
- <xpath>/rootXMLBodyNode/childXMLBodyNode[@myAttributeKey='myAttributeValue']</xpath>
- <to uri="activemq:queue:queue.HelloWorld.camel6.fooMsgs">
+ <xpath>/rootXMLBodyNode/childXMLBodyNode[@myAttributeKey='myAttributeValue']</xpath>
+ <to uri="activemq:queue:queue.HelloWorld.camel6.fooMsgs">
</filter>
</filter>
</route>
@@ -114,12 +113,12 @@
<!-- route using nested JUEL and xpath filters, including a filter which examines the message content for an xml value -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming.camel7">
+ <from uri="activemq:topic:topic.HelloWorld.incoming.camel7">
<filter>
- <el>${in.headers.JMSType.equals('Tideworks.GateVision.XmlCmd')}</el>
+ <el>${in.headers.JMSType.equals('Tideworks.GateVision.XmlCmd')}</el>
<filter>
- <xpath>/rootXMLBodyNode/childXMLBodyNode/elementKey = 'elementValue'</xpath>
- <to uri="activemq:queue:queue.HelloWorld.camel7.fooMsgs">
+ <xpath>/rootXMLBodyNode/childXMLBodyNode/elementKey = 'elementValue'</xpath>
+ <to uri="activemq:queue:queue.HelloWorld.camel7.fooMsgs">
</filter>
</filter>
</route>
@@ -127,17 +126,16 @@
<!-- route using nested JUEL and xpath filters, including a filter which examines the message content for an xml attribute -->
<route>
- <from uri="activemq:topic:topic.HelloWorld.incoming.camel8">
+ <from uri="activemq:topic:topic.HelloWorld.incoming.camel8">
<filter>
- <el>${in.headers.JMSType.equals('foo')}</el>
+ <el>${in.headers.JMSType.equals('foo')}</el>
<filter>
- <xpath>/rootXMLBodyNode/childXMLBodyNode[@myAttributeKey='myAttributeValue']/grandchildXMLBodyNode[@myAttributeKey='myAttributeValue']</xpath>
- <to uri="activemq:queue:queue.HelloWorld.camel8.fooMsgs">
+ <xpath>/rootXMLBodyNode/childXMLBodyNode[@myAttributeKey='myAttributeValue']/grandchildXMLBodyNode[@myAttributeKey='myAttributeValue']</xpath>
+ <to uri="activemq:queue:queue.HelloWorld.camel8.fooMsgs">
</filter>
</filter>
</route>
</camelContext>
</beans>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/sample-report.xml b/sample-report.xml
index 180371f..9475d26 100644
--- a/sample-report.xml
+++ b/sample-report.xml
@@ -1,7 +1,7 @@
-<div class="wiki-content maincontent"><h2 id="samplereport-PerformanceTestReportTemplate">Performance Test Report Template</h2>
+<div class="wiki-content maincontent"><h2>Performance Test Report Template</h2>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre><testResult>
+<structured-macro ac:macro-id="00b92e64-60d1-468f-8ffa-af56e342b2fd" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+<testResult>
<property name='systemSettings'>
<props>
<prop key='java.runtime.name'>Java(TM) 2 Runtime Environment, Standard Edition</prop>
@@ -68,6 +68,5 @@
</props>
</property>
</testResult>
-</pre>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/sandbox.xml b/sandbox.xml
index d62e311..3f2fb55 100644
--- a/sandbox.xml
+++ b/sandbox.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="b545d023-2618-4e8c-8e07-60dc93882c84" ac:name="children" ac:schema-version="1"></structured-macro></div>
diff --git a/scaling-queues.xml b/scaling-queues.xml
index f265861..c4b4022 100644
--- a/scaling-queues.xml
+++ b/scaling-queues.xml
@@ -1,11 +1,3 @@
-<div class="wiki-content maincontent"><p>Scaling to tens of thousands of Queues in a single broker is relatively straightforward - but requires some configuration changes from the default.</p><h2 id="ScalingQueues-ReducingThreads">Reducing Threads</h2><p>With the default configuration, ActiveMQ is configured to use a dispatch thread per Queue - you can use set the optimizedDispatch property on the destination policy entry - see <a shape="rect" href="per-destination-policies.xml">configuring Queues</a>.</p><p>ActiveMQ can optionally use internally a thread pool to control dispatching of messages - but as a lot of deployment operating systems are good at handling a large number of threads, this is off by default. To enable this option, either set the ACTIVEMQ_OPTS to disable dedicated task runners in the start up script, INSTALL_DIR/bin/activemq -e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ACTIVEMQ_OPTS="-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=false"
-]]></script>
-</div></div><p>or you can set ACTIVEMQ_OPTS in /etc/activemq.conf.</p><p><strong>Note:</strong> From ActiveMQ 5.6 onwards the dedicated task runner is disabled by default (see
- <span class="jira-issue resolved">
- <a shape="rect" class="jira-issue-key" href="https://issues.apache.org/jira/browse/AMQ-3667?src=confmacro"><img class="icon" src="https://issues.apache.org/jira/images/icons/issuetypes/improvement.png">AMQ-3667</a>
-
- <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Resolved</span>
- </span>
-).</p><p>To reduce the number of threads used for the transport - take a look at using the NIO transport - see <a shape="rect" href="configuring-transports.xml">Configuring Transports</a></p><p>Here is an <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/sample-conf/activemq-scalability.xml">example</a> of this in use in one of the provided sample broker configuration files.</p><h2 id="ScalingQueues-ReducingMemoryConsumption">Reducing Memory Consumption</h2><p>Reduce the memory used per thread - see <a shape="rect" href="javalangoutofmemory.xml">reducing memory consumption</a></p><h2 id="ScalingQueues-Reducenumberoffiledescriptors">Reduce number of file descriptors</h2><p>ActiveMQ uses the amqPersistenceAdapter by default for persistent messages. Unfortunately, this persistence adapter (as well as the kahaPersistenceAdapter) opens a file descriptor for each queue. When creating large numbers of queues, you'll quickly run into the limit for your OS.</p><p>You can either choose another <a shape="rect" href="persistence.xml">persistence option</a></p><p>or - try out the new <a shape="rect" href="kahadb.xml">KahaDB</a> in version 5.3 and higher</p><h2 id="ScalingQueues-Increasethelimitonfiledescriptorsperprocess">Increase the limit on file descriptors per process</h2><p>Try <a shape="rect" class="external-link" href="http://tinyurl.com/o9qs2f" rel="nofollow">googling for the OS you are using</a></p></div>
+<div class="wiki-content maincontent"><p>Scaling to tens of thousands of Queues in a single broker is relatively straightforward - but requires some configuration changes from the default.</p><h2>Reducing Threads</h2><p>With the default configuration, ActiveMQ is configured to use a dispatch thread per Queue - you can use set the optimizedDispatch property on the destination policy entry - see <link><page ri:content-title="Per Destination Policies"></page><plain-text-link-body>configuring Queues</plain-text-link-body></link>.</p><p>ActiveMQ can optionally use internally a thread pool to control dispatching of messages - but as a lot of deployment operating systems are good at handling a large number of threads, this is off by default. To enable this option, either set the ACTIVEMQ_OPTS to disable dedicated task runners in the start up script, INSTALL_DIR/bin/activemq -e.g.</p><structured-macro ac:macro-id="c277ee98-10b9-4eea-802b-5b68565257c8" ac:name="code" ac:schema-version="1"><plain-text-body>ACTIVEMQ_OPTS="-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=false"
+</plain-text-body></structured-macro><p>or you can set ACTIVEMQ_OPTS in /etc/activemq.conf.</p><p><strong>Note:</strong> From ActiveMQ 5.6 onwards the dedicated task runner is disabled by default (see <structured-macro ac:macro-id="1d4abf51-199a-4b44-89ec-b024075836b8" ac:name="jira" ac:schema-version="1"><parameter ac:name="showSummary">false</parameter><parameter ac:name="server">ASF JIRA</parameter><parameter ac:name="serverId">5aa69414-a9e9-3523-82ec-879b028fb15b</parameter><parameter ac:name="key">AMQ-3667</parameter></structured-macro>).</p><p>To reduce the number of threads used for the transport - take a look at using the NIO transport - see <link><page ri:content-title="Configuring Transports"></page></link></p><p>Here is an <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/sample-conf/activemq-scalability.xml">example</a> of this in use in one of the provided sample broker configuration files.</p><h2>Reducing Memory Consumption</h2><p>Reduce the memory used per thread - see <link><page ri:content-title="java.lang.OutOfMemory"></page><plain-text-link-body>reducing memory consumption</plain-text-link-body></link></p><h2>Reduce number of file descriptors</h2><p>ActiveMQ uses the amqPersistenceAdapter by default for persistent messages. Unfortunately, this persistence adapter (as well as the kahaPersistenceAdapter) opens a file descriptor for each queue. When creating large numbers of queues, you'll quickly run into the limit for your OS.</p><p>You can either choose another <link><page ri:content-title="Persistence"></page><plain-text-link-body>persistence option</plain-text-link-body></link></p><p>or - try out the new <link><page ri:content-title="KahaDB"></page></link> in version 5.3 and higher</p><h2>Increase the limit on file descriptors per process</h2><p>Try <a shape="rect" href="http://tinyurl.com/o9qs2f">googling for the OS you are using</a></p></div>
diff --git a/scaling-the-depth-of-a-queue.xml b/scaling-the-depth-of-a-queue.xml
index f5933e7..1c1d1cb 100644
--- a/scaling-the-depth-of-a-queue.xml
+++ b/scaling-the-depth-of-a-queue.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>Nearly all messaging systems (certainly open source ones) hold either a copy of a persistent message or a reference to a persisted message in memory. This is primarily to try and improve performance, but it also can significantly decrease the complexity of implementation. In fact ActiveMQ version 4 and below worked this - way - by holding references to persisted messages in memory.</p><p>However there is a limitation to this approach, no matter how much memory you have at your disposal, you will hit a limit to the number persistent messages a broker can handle at any particular time.</p><p>To get around this limitation, ActiveMQ introduced a paging cache - for all message stores (except the memory store) to get the best of both worlds - great performance and the ability to hold 100s of millions of messages in persistent store. ActiveMQ is <strong>not</strong> limited by memory availability, but by the size of the disk available to hold the persistent messages.</p><p>For more information see: <a shape="rect" href="message-cursors.xml">Message Cursors</a></p></div>
+<div class="wiki-content maincontent"><p>Nearly all messaging systems (certainly open source ones) hold either a copy of a persistent message or a reference to a persisted message in memory. This is primarily to try and improve performance, but it also can significantly decrease the complexity of implementation. In fact ActiveMQ version 4 and below worked this - way - by holding references to persisted messages in memory.</p><p>However there is a limitation to this approach, no matter how much memory you have at your disposal, you will hit a limit to the number persistent messages a broker can handle at any particular time.</p><p>To get around this limitation, ActiveMQ introduced a paging cache - for all message stores (except the memory store) to get the best of both worlds - great performance and the ability to hold 100s of millions of messages in persistent store. ActiveMQ is <strong>not</strong> limited by memory availability, but by the size of the disk available to hold the persistent messages.</p><p>For more information see: <link><page ri:content-title="Message Cursors"></page></link></p></div>
diff --git a/security-advisories.xml b/security-advisories.xml
index 59ca1b7..b8c6358 100644
--- a/security-advisories.xml
+++ b/security-advisories.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="SecurityAdvisories-ApacheActiveMQ">Apache ActiveMQ</h2><h3 id="SecurityAdvisories-2017">2017</h3><ul><li><p class="p1"><span class="s1"><a shape="rect" href="security-advisories.data/CVE-2015-7559-announcement.txt?version=1&modificationDate=1493024710000&api=v2" data-linked-resource-id="69407411" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2015-7559-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2015-7559</a> - DoS in client via shutdown command</span></p></li></ul><h3 id="SecurityAdvisories-2016">2016</h3><ul><li><a shape="rect" href="security-advisories.data/CVE-2016-6810-announcement.txt?version=2&modificationDate=1481290006000&api=v2" data-linked-resource-id="67634297" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2016-6810-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2016-6810</a> - ActiveMQ Web Console - Cross-Site Scripting</li><li><a shape="rect" href="security-advisories.data/CVE-2016-0734-announcement.txt?version=1&modificationDate=1457613666000&api=v2" data-linked-resource-id="62687061" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2016-0734-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2016-0734</a> - ActiveMQ Web Console - Clickjacking</li><li><a shape="rect" href="security-advisories.data/CVE-2016-0782-announcement.txt?version=2&modificationDate=1458229308000&api=v2" data-linked-resource-id="62687062" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2016-0782-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2016-0782</a> - ActiveMQ Web Console - Cross-Site Scripting</li><li><a shape="rect" href="security-advisories.data/CVE-2016-3088-announcement.txt?version=5&modificationDate=1464092715000&api=v2" data-linked-resource-id="63406525" data-linked-resource-version="5" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2016-3088-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2016-3088</a> - ActiveMQ Fileserver web application vulnerabilities</li></ul><h3 id="SecurityAdvisories-2015">2015</h3><ul><li><a shape="rect" href="security-advisories.data/CVE-2015-5254-announcement.txt?version=1&modificationDate=1449589734000&api=v2" data-linked-resource-id="61331741" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2015-5254-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2015-5254</a> - Unsafe deserialization in ActiveMQ</li><li><a shape="rect" href="security-advisories.data/CVE-2015-1830-announcement.txt?version=2&modificationDate=1440426986000&api=v2" data-linked-resource-id="61313840" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2015-1830-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2015-1830</a> - Path traversal leading to unauthenticated RCE in ActiveMQ </li></ul><h3 id="SecurityAdvisories-2014">2014</h3><ul><li><a shape="rect" href="security-advisories.data/CVE-2014-3576-announcement.txt?version=1&modificationDate=1446901063000&api=v2" data-linked-resource-id="61327457" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2014-3576-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2014-3576</a> - Remote Unauthenticated Shutdown of Broker (DoS)</li><li><a shape="rect" href="security-advisories.data/CVE-2014-3600-announcement.txt?version=2&modificationDate=1423051306000&api=v2" data-linked-resource-id="52035730" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2014-3600-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2014-3600</a> - Apache ActiveMQ XXE with XPath selectors</li><li><a shape="rect" href="security-advisories.data/CVE-2014-3612-announcement.txt?version=2&modificationDate=1423051365000&api=v2" data-linked-resource-id="52035731" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2014-3612-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2014-3612</a> - ActiveMQ JAAS: LDAPLoginModule allows empty password authentication and Wildcard Interpretation</li><li><a shape="rect" href="security-advisories.data/CVE-2014-8110-announcement.txt?version=2&modificationDate=1423051381000&api=v2" data-linked-resource-id="52035732" data-linked-resource-version="2" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2014-8110-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2014-8110</a> - <span style="line-height: 1.4285715;">ActiveMQ Web Console - Cross-Site Scripting</span><span style="line-height: 1.4285715;"><br clear="none"></span></li></ul><h2 id="SecurityAdvisories-ActiveMQApollo"><span style="line-height: 1.4285715;">ActiveMQ Apollo</span></h2><h3 id="SecurityAdvisories-2014.1"><span style="line-height: 1.4285715;">2014</span></h3><ul><li><span style="line-height: 1.4285715;"><span style="line-height: 1.4285715;"> </span></span><a shape="rect" href="security-advisories.data/CVE-2014-3579-announcement.txt?version=1&modificationDate=1423054118000&api=v2" data-linked-resource-id="52035737" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="CVE-2014-3579-announcement.txt" data-nice-type="Text File" data-linked-resource-content-type="text/plain" data-linked-resource-container-id="51808957" data-linked-resource-container-version="13">CVE-2014-3579</a><span style="line-height: 1.4285715;"> - ActiveMQ Apollo XXE with XPath selectors</span></li></ul><p><span style="line-height: 1.4285715;"> </span></p></div>
+<div class="wiki-content maincontent"><h2>Apache ActiveMQ</h2><h3>2017</h3><ul><li><p class="p1"><span class="s1"><link><attachment ri:filename="CVE-2015-7559-announcement.txt"></attachment><plain-text-link-body>CVE-2015-7559</plain-text-link-body></link> - DoS in client via shutdown command</span></p></li></ul><h3>2016</h3><ul><li><link><attachment ri:filename="CVE-2016-6810-announcement.txt"></attachment><plain-text-link-body>CVE-2016-6810</plain-text-link-body></link> - ActiveMQ Web Console - Cross-Site Scripting</li><li><link><attachment ri:filename="CVE-2016-0734-announcement.txt"></attachment><plain-text-link-body>CVE-2016-0734</plain-text-link-body></link> - ActiveMQ Web Console - Clickjacking</li><li><link><attachment ri:filename="CVE-2016-0782-announcement.txt"></attachment><plain-text-link-body>CVE-2016-0782</plain-text-link-body></link> - ActiveMQ Web Console - Cross-Site Scripting</li><li><link><attachment ri:filename="CVE-2016-3088-announcement.txt"></attachment><plain-text-link-body>CVE-2016-3088</plain-text-link-body></link> - ActiveMQ Fileserver web application vulnerabilities</li></ul><h3>2015</h3><ul><li><link><attachment ri:filename="CVE-2015-5254-announcement.txt"></attachment><plain-text-link-body>CVE-2015-5254</plain-text-link-body></link> - Unsafe deserialization in ActiveMQ</li><li><link><attachment ri:filename="CVE-2015-1830-announcement.txt"></attachment><plain-text-link-body>CVE-2015-1830</plain-text-link-body></link> - Path traversal leading to unauthenticated RCE in ActiveMQ </li></ul><h3>2014</h3><ul><li><link><attachment ri:filename="CVE-2014-3576-announcement.txt"></attachment><plain-text-link-body>CVE-2014-3576</plain-text-link-body></link> - Remote Unauthenticated Shutdown of Broker (DoS)</li><li><link><attachment ri:filename="CVE-2014-3600-announcement.txt"></attachment><plain-text-link-body>CVE-2014-3600</plain-text-link-body></link> - Apache ActiveMQ XXE with XPath selectors</li><li><link><attachment ri:filename="CVE-2014-3612-announcement.txt"></attachment><plain-text-link-body>CVE-2014-3612</plain-text-link-body></link> - ActiveMQ JAAS: LDAPLoginModule allows empty password authentication and Wildcard Interpretation</li><li><link><attachment ri:filename="CVE-2014-8110-announcement.txt"></attachment><plain-text-link-body>CVE-2014-8110</plain-text-link-body></link> - <span style="line-height: 1.4285715;">ActiveMQ Web Console - Cross-Site Scripting</span><span style="line-height: 1.4285715;"><br clear="none"></span></li></ul><h2><span style="line-height: 1.4285715;">ActiveMQ Apollo</span></h2><h3><span style="line-height: 1.4285715;">2014</span></h3><ul><li><span style="line-height: 1.4285715;"><span style="line-height: 1.4285715;"> </span></span><link><attachment ri:filename="CVE-2014-3579-announcement.txt"></attachment><plain-text-link-body>CVE-2014-3579</plain-text-link-body></link><span style="line-height: 1.4285715;"> - ActiveMQ Apollo XXE with XPath selectors</span></li></ul><p><span style="line-height: 1.4285715;"> </span></p></div>
diff --git a/security.xml b/security.xml
index 06e3d8e..8d1365f 100644
--- a/security.xml
+++ b/security.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><p>ActiveMQ 4.x and greater provides pluggable security through various different providers.</p><p>The most common providers are</p><ul><li><a shape="rect" class="external-link" href="http://java.sun.com/products/jaas/" rel="nofollow">JAAS</a> for authentication</li><li>a default authorization mechanism using a simple XML configuration file.</li></ul><h3 id="Security-Authentication">Authentication</h3><p>The default <a shape="rect" class="external-link" href="http://java.sun.com/products/jaas/" rel="nofollow">JAAS</a> plugin relies on the standard JAAS mechanism for authentication. Refer to the <a shape="rect" class="external-link" href="http://java.sun.com/products/jaas/reference/docs/index.html" rel="nofollow">documentation</a> for more detail.</p><p>Typically you configure JAAS using a config file like <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/login.config">this one</a> and set the <strong>java.security.auth.login.config</strong> system property to point to it. If no system property is specified then by default the ActiveMQ JAAS plugin will look for <strong>login.config</strong> on the classpath and use that.</p><h4 id="Security-AuthenticationExample">Authentication Example</h4><p>Here is an example <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/login.config">login.config</a> which then points to these files</p><ul><li><a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/users.properties">users.properties</a></li><li><a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/groups.properties">groups.properties</a></li></ul><p><strong>Note:</strong> Until version 5.11.1, these property files got reloaded on every authentication request by default. So updates to users, password and groups were loaded immediately. From 5.12 onward they only get reloaded if reload=true is set in your LoginModule configuration, e.g.</p><plain-text-body>activemq {
+<div class="wiki-content maincontent"><p>ActiveMQ 4.x and greater provides pluggable security through various different providers.</p><p>The most common providers are</p><ul><li><a shape="rect" href="http://java.sun.com/products/jaas/">JAAS</a> for authentication</li><li>a default authorization mechanism using a simple XML configuration file.</li></ul><h3>Authentication</h3><p>The default <a shape="rect" href="http://java.sun.com/products/jaas/">JAAS</a> plugin relies on the standard JAAS mechanism for authentication. Refer to the <a shape="rect" href="http://java.sun.com/products/jaas/reference/docs/index.html">documentation</a> for more detail.</p><p>Typically you configure JAAS using a config file like <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/login.config">this one</a> and set the <strong>java.security.auth.login.config</strong> system property to point to it. If no system property is specified then by default the ActiveMQ JAAS plugin will look for <strong>login.config</strong> on the classpath and use that.</p><h4>Authentication Example</h4><p>Here is an example <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/login.config">login.config</a> which then points to these files</p><ul><li><a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/users.properties">users.properties</a></li><li><a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/groups.properties">groups.properties</a></li></ul><p><strong>Note:</strong> Until version 5.11.1, these property files got reloaded on every authentication request by default. So updates to users, password and groups were loaded immediately. From 5.12 onward they only get reloaded if reload=true is set in your LoginModule configuration, e.g.</p><plain-text-body>activemq {
org.apache.activemq.jaas.PropertiesLoginModule required
org.apache.activemq.jaas.properties.user="users.properties"
org.apache.activemq.jaas.properties.group="groups.properties"
reload=true;
};
-</plain-text-body><p>If reload=true is not set, these property files get loaded on broker startup only!! See AMQ-5876 for details.</p><h4 id="Security-SimpleAuthenticationPlugin">Simple Authentication Plugin</h4><p>If you have modest authentication requirements (or just want to quickly set up your testing environment) you can use SimpleAuthenticationPlugin. With this plugin you can define users and groups directly in the broker's XML configuration. Take a look at the following snippet for example:</p><parameter ac:name="">xml</parameter><plain-text-body><simpleAuthenticationPlugin>
+</plain-text-body><p>If reload=true is not set, these property files get loaded on broker startup only!! See AMQ-5876 for details.</p><h4>Simple Authentication Plugin</h4><p>If you have modest authentication requirements (or just want to quickly set up your testing environment) you can use SimpleAuthenticationPlugin. With this plugin you can define users and groups directly in the broker's XML configuration. Take a look at the following snippet for example:</p><parameter ac:name="">xml</parameter><plain-text-body><simpleAuthenticationPlugin>
<users>
<authenticationUser username="system" password="manager"
groups="users,admins"/>
@@ -13,7 +13,7 @@
<authenticationUser username="guest" password="password" groups="guests"/>
</users>
</simpleAuthenticationPlugin>
-</plain-text-body><p>Users and groups defined in this way can be later used with the appropriate authorization plugin.</p><h5 id="Security-Anonymousaccess">Anonymous access</h5><p>From version 5.4.0 onwards, you can configure simple authentication plugin to allow anonymous access to the broker.</p><parameter ac:name="">xml</parameter><plain-text-body><simpleAuthenticationPlugin anonymousAccessAllowed="true">
+</plain-text-body><p>Users and groups defined in this way can be later used with the appropriate authorization plugin.</p><h5>Anonymous access</h5><p>From version 5.4.0 onwards, you can configure simple authentication plugin to allow anonymous access to the broker.</p><parameter ac:name="">xml</parameter><plain-text-body><simpleAuthenticationPlugin anonymousAccessAllowed="true">
<users>
<authenticationUser username="system" password="manager"
groups="users,admins"/>
@@ -22,13 +22,13 @@
<authenticationUser username="guest" password="password" groups="guests"/>
</users>
</simpleAuthenticationPlugin>
-</plain-text-body><p>To allow anonymous access to the broker, use <code>anonymousAccessAllowed</code> attribute and set it to <code>true</code> as shown above. Now, when the client connects without username and password provided, a default username (<code>anonymous</code>) and group (<code>anonymous</code>) will be assigned to its security context. You can use this username and password to authorize client's access to appropriate broker resources (see the next section). You can also change username and group that will be assigned to <em>anonymous</em> users by using <code>anonymousUser</code> and <code>anonymousGroup</code> attributes.</p><h3 id="Security-Authorization">Authorization</h3><p>In ActiveMQ we use a number of operations which you can associate with user roles and either individual queues or topics or you can use wildcards to attach to hierarchies of topics and queues.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Operation</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>read</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can browse and consume from the destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>write</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can send messages to the destination</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>admin</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>You can lazily create the destination if it does not yet exist. This allows you fine grained control over which new destinations can be dynamically created in what part of the queue/topic hierarchy</p></td></tr></tbody></table></div><p>Queues/Topics can specified using the ActiveMQ <a shape="rect" href="wildcards.xml">Wildcards</a> syntax.</p><h4 id="Security-AuthorizationExample">Authorization Example</h4><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/jaas-broker.xml">example</a> shows these 2 plugins in operation. Though note its very easy to write your own plugin.<plain-text-body>{snippet:id=example|lang=xml|url=activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/jaas-broker.xml}</plain-text-body><strong>Note</strong> that full access rights should generally be given to the ActiveMQ.Advisory destinations because by default an ActiveMQConnection uses destination advisories to get early knowledge of temp destination creation and deletion. In addition, dynamic network connectors use advisories to determine consumer demand.<br clear="none"> If necessary, the use of advisories in this manner can be disabled via the <em>watchTopicAdvisories</em> boolean attribute of ActiveMQConnectionFactory and for a networkConnector, via the network connector <em>staticBridge</em>(5.6) boolean attribute.</p><h3 id="Security-Broker-to-BrokerAuthenticationandAuthorization">Broker-to-Broker Authentication and Authorization</h3><p>If you have enabled authentication for a particular message broker, then other brokers that wish to connect to that broker must provide the proper authentication credentials via their <networkConnector> element. For example, suppose that we have a network of brokers with the following configuration:</p><ul class="alternate"><li>The network of brokers comprises two brokers (BrokerA and BrokerB)</li><li>Authentication for BrokerA has been enabled via the example <simpleAuthenticationPlugin> element.</li><li>Authentication for BrokerB has not been enabled.</li><li>BrokerA only listens for connections. In other words, BrokerA has a <transportConnector> element, but no <networkConnector> elements.</li></ul><p>In order for BrokerB to connect to BrokerA, the corresponding <networkConnector> element in BrokerB's XML configuration file must be set up as follows.</p><parameter ac:name="">xml</parameter><plain-text-body><networkConnectors>
+</plain-text-body><p>To allow anonymous access to the broker, use <code>anonymousAccessAllowed</code> attribute and set it to <code>true</code> as shown above. Now, when the client connects without username and password provided, a default username (<code>anonymous</code>) and group (<code>anonymous</code>) will be assigned to its security context. You can use this username and password to authorize client's access to appropriate broker resources (see the next section). You can also change username and group that will be assigned to <em>anonymous</em> users by using <code>anonymousUser</code> and <code>anonymousGroup</code> attributes.</p><h3>Authorization</h3><p>In ActiveMQ we use a number of operations which you can associate with user roles and either individual queues or topics or you can use wildcards to attach to hierarchies of topics and queues.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Operation</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>read</p></td><td colspan="1" rowspan="1"><p>You can browse and consume from the destination</p></td></tr><tr><td colspan="1" rowspan="1"><p>write</p></td><td colspan="1" rowspan="1"><p>You can send messages to the destination</p></td></tr><tr><td colspan="1" rowspan="1"><p>admin</p></td><td colspan="1" rowspan="1"><p>You can lazily create the destination if it does not yet exist. This allows you fine grained control over which new destinations can be dynamically created in what part of the queue/topic hierarchy</p></td></tr></tbody></table><p>Queues/Topics can specified using the ActiveMQ <link><page ri:content-title="Wildcards"></page></link> syntax.</p><h4>Authorization Example</h4><p>The following <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/jaas-broker.xml">example</a> shows these 2 plugins in operation. Though note its very easy to write your own plugin.<plain-text-body>{snippet:id=example|lang=xml|url=activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/security/jaas-broker.xml}</plain-text-body><strong>Note</strong> that full access rights should generally be given to the ActiveMQ.Advisory destinations because by default an ActiveMQConnection uses destination advisories to get early knowledge of temp destination creation and deletion. In addition, dynamic network connectors use advisories to determine consumer demand.<br clear="none"> If necessary, the use of advisories in this manner can be disabled via the <em>watchTopicAdvisories</em> boolean attribute of ActiveMQConnectionFactory and for a networkConnector, via the network connector <em>staticBridge</em>(5.6) boolean attribute.</p><h3>Broker-to-Broker Authentication and Authorization</h3><p>If you have enabled authentication for a particular message broker, then other brokers that wish to connect to that broker must provide the proper authentication credentials via their <networkConnector> element. For example, suppose that we have a network of brokers with the following configuration:</p><ul class="alternate"><li>The network of brokers comprises two brokers (BrokerA and BrokerB)</li><li>Authentication for BrokerA has been enabled via the example <simpleAuthenticationPlugin> element.</li><li>Authentication for BrokerB has not been enabled.</li><li>BrokerA only listens for connections. In other words, BrokerA has a <transportConnector> element, but no <networkConnector> elements.</li></ul><p>In order for BrokerB to connect to BrokerA, the corresponding <networkConnector> element in BrokerB's XML configuration file must be set up as follows.</p><parameter ac:name="">xml</parameter><plain-text-body><networkConnectors>
<networkConnector name="brokerAbridge"
userName="user"
password="password"
uri="static://(tcp://brokerA:61616)"/>
</networkConnectors>
-</plain-text-body><p>Note how BrokerB's <networkConnector> element must provide the proper credentials in order to connect to BrokerA. If authorization has been enabled on BrokerA, then the userName assigned to the <networkConnector> element must also have the proper authorization credentials. Messages cannot be forwarded from BrokerB to BrokerA if BrokerA has authorization enabled and BrokerB's corresponding <networkConnector> element's userName has not been given the proper authorization credentials.</p><p>Also, if BrokerA is given a <networkConnector> element so that it can initiate a connection to BrokerB, then that <networkConnector> must be given a userName/password combination that is defined in the <simpleAuthenticationPlugin> element; this is required even though BrokerB does not have authentication services enabled.</p><h3 id="Security-ControllingAccessToTemporaryDestinations">Controlling Access To Temporary Destinations</h3><p>To control access to temporary destinations, you will need to add a <tempDestinationAuthorizationEntry> element to the authorizationMap. Through this element, you control access to all temporary destinations. If this element is not present, read, write, and admin privileges for temporary destinations will be granted to all. In the example below, read, write, and admin privileges for temporary destinations are only granted to those clients that have been assigned to the 'admin' group.</p><parameter ac:name="">xml</parameter><plain-text-body><broker>
+</plain-text-body><p>Note how BrokerB's <networkConnector> element must provide the proper credentials in order to connect to BrokerA. If authorization has been enabled on BrokerA, then the userName assigned to the <networkConnector> element must also have the proper authorization credentials. Messages cannot be forwarded from BrokerB to BrokerA if BrokerA has authorization enabled and BrokerB's corresponding <networkConnector> element's userName has not been given the proper authorization credentials.</p><p>Also, if BrokerA is given a <networkConnector> element so that it can initiate a connection to BrokerB, then that <networkConnector> must be given a userName/password combination that is defined in the <simpleAuthenticationPlugin> element; this is required even though BrokerB does not have authentication services enabled.</p><h3>Controlling Access To Temporary Destinations</h3><p>To control access to temporary destinations, you will need to add a <tempDestinationAuthorizationEntry> element to the authorizationMap. Through this element, you control access to all temporary destinations. If this element is not present, read, write, and admin privileges for temporary destinations will be granted to all. In the example below, read, write, and admin privileges for temporary destinations are only granted to those clients that have been assigned to the 'admin' group.</p><parameter ac:name="">xml</parameter><plain-text-body><broker>
..
<plugins>
..
@@ -49,7 +49,7 @@
</plugins>
..
</broker>
-</plain-text-body><h3 id="Security-LDAPAuthenticationUsingtheJAASPlugin">LDAP Authentication Using the JAAS Plugin</h3><parameter ac:name="">New module</parameter><rich-text-body><p>A new/better ldap authorization module is available since 5.6. See <a shape="rect" href="cached-ldap-authorization-module.xml">Cached LDAP Authorization Module</a> for more info.</p></rich-text-body><p>1. Configure the JAAS LDAPLoginModule and the LDAPAuthorizationMap in activemq.xml:</p><parameter ac:name="">xml</parameter><plain-text-body> <plugins>
+</plain-text-body><h3>LDAP Authentication Using the JAAS Plugin</h3><parameter ac:name="">New module</parameter><rich-text-body><p>A new/better ldap authorization module is available since 5.6. See <link><page ri:content-title="Cached LDAP Authorization Module"></page></link> for more info.</p></rich-text-body><p>1. Configure the JAAS LDAPLoginModule and the LDAPAuthorizationMap in activemq.xml:</p><parameter ac:name="">xml</parameter><plain-text-body> <plugins>
<!-- use JAAS to authenticate using the login.config file on the classpath to configure JAAS -->
<jaasAuthenticationPlugin configuration="LdapConfiguration" />
<!-- lets configure a destination based role/group authorization mechanism -->
@@ -269,7 +269,7 @@
objectClass: account
objectClass: simpleSecurityObject
objectClass: top
-</plain-text-body><p>4. Start up ActiveMQ</p><p>5. Test it out</p><h3 id="Security-SecurityandActiveMQComponents">Security and ActiveMQ Components</h3><p>Along with the message broker, you can optionally execute several additional "components", such as Camel and/or the Web console. These components establish connections with the broker; therefore, if you have secured your broker (i.e., enabled authentication), you will have to configure these components in order to have them provide the required security credentials (username, password) when they connect to the broker.</p><h4 id="Security-Camel">Camel</h4><p>You may have the following Camel context defined in your broker's XML configuration file.</p><parameter ac:name="">xml</parameter><plain-text-body><!--
+</plain-text-body><p>4. Start up ActiveMQ</p><p>5. Test it out</p><h3>Security and ActiveMQ Components</h3><p>Along with the message broker, you can optionally execute several additional "components", such as Camel and/or the Web console. These components establish connections with the broker; therefore, if you have secured your broker (i.e., enabled authentication), you will have to configure these components in order to have them provide the required security credentials (username, password) when they connect to the broker.</p><h4>Camel</h4><p>You may have the following Camel context defined in your broker's XML configuration file.</p><parameter ac:name="">xml</parameter><plain-text-body><!--
** Lets deploy some Enterprise Integration Patterns inside the ActiveMQ Message Broker
** For more details see
**
@@ -294,19 +294,19 @@
</property>
</bean>
</plain-text-body><p>With the above bean definition, Camel will pass the specified security credentials when it connects to the broker.</p><p>If the broker is running in an OSGi container, add the following line after the ActiveMQComponent bean definition:</p><parameter ac:name="">xml</parameter><plain-text-body><service ref="activemq" interface="org.apache.camel.Component"/>
-</plain-text-body><h4 id="Security-WebConsole">Web Console</h4><p>If you want to use the Web Console with a secured broker, you have to change <code>connectionFactory</code> bean in your <code>webapps/admin/WEB-INF/webconsole-embeded.xml</code> to something like this:</p><parameter ac:name="">xml</parameter><plain-text-body><bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
+</plain-text-body><h4>Web Console</h4><p>If you want to use the Web Console with a secured broker, you have to change <code>connectionFactory</code> bean in your <code>webapps/admin/WEB-INF/webconsole-embeded.xml</code> to something like this:</p><parameter ac:name="">xml</parameter><plain-text-body><bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="vm://localhost"/>
<property name="userName" value="system"/>
<property name="password" value="manager"/>
</bean>
-</plain-text-body><h4 id="Security-DefaultCredentials">Default Credentials</h4><p>Starting with version 5.3, all of the above configuration details are included in the default ActiveMQ configuration. Also, there is a central place where you can set credentials that these components will use to connect to the broker. Just set your desired username and password in the <code>conf/credentials.properties</code> file, which by default looks like this:</p><plain-text-body>activemq.username=system
+</plain-text-body><h4>Default Credentials</h4><p>Starting with version 5.3, all of the above configuration details are included in the default ActiveMQ configuration. Also, there is a central place where you can set credentials that these components will use to connect to the broker. Just set your desired username and password in the <code>conf/credentials.properties</code> file, which by default looks like this:</p><plain-text-body>activemq.username=system
activemq.password=manager
-</plain-text-body><h4 id="Security-EncryptedPasswords">Encrypted Passwords</h4><p>As of version 5.4.1 you can also use <a shape="rect" href="encrypted-passwords.xml">Encrypted passwords</a> with your broker</p><h3 id="Security-MessagelevelAuthorization">Message level Authorization</h3><p>It's also possible to authorize each single message using some content based authorization policy of your choosing. In comparison to the other security options described before, Message level Authorization requires a bit more than just some configuration. You have to start with creating a new maven project and add the <a shape="rect" class="external-link" href="https://mvnrepository.com/artifact/org.apache.activemq/activemq-all" rel="nofollow">activemq-all</a> maven dependency (in the same version as your activemq installation) to the pom.xml of your new project.<br clear="none">In the next step you have to create a new Java class and let it implement the org.apache.activemq.security.MessageAuthorizationPolicy interface. After that, simply add a method with signature:</p><p>public boolean isAllowedToConsume(ConnectionContext context, Message message){...}</p><p>to the new Java class. For usage of your own Message level Authorization policy, the Java class has to be packaged as jar and added to the /lib folder of ActiveMQ to make it available for ActiveMQ. In the last step, it has to be configured on the broker directly by using the * messageAuthorizationPolicy* property or add it to the XML as follows</p><parameter ac:name="">xml</parameter><plain-text-body><broker>
+</plain-text-body><h4>Encrypted Passwords</h4><p>As of version 5.4.1 you can also use <link><page ri:content-title="Encrypted passwords"></page></link> with your broker</p><h3>Message level Authorization</h3><p>It's also possible to authorize each single message using some content based authorization policy of your choosing. In comparison to the other security options described before, Message level Authorization requires a bit more than just some configuration. You have to start with creating a new maven project and add the <a shape="rect" href="https://mvnrepository.com/artifact/org.apache.activemq/activemq-all">activemq-all</a> maven dependency (in the same version as your activemq installation) to the pom.xml of your new project.<br clear="none">In the next step you have to create a new Java class and let it implement the org.apache.activemq.security.MessageAuthorizationPolicy interface. After that, simply add a method with signature:</p><p>public boolean isAllowedToConsume(ConnectionContext context, Message message){...}</p><p>to the new Java class. For usage of your own Message level Authorization policy, the Java class has to be packaged as jar and added to the /lib folder of ActiveMQ to make it available for ActiveMQ. In the last step, it has to be configured on the broker directly by using the * messageAuthorizationPolicy* property or add it to the XML as follows</p><parameter ac:name="">xml</parameter><plain-text-body><broker>
..
<messageAuthorizationPolicy>
<bean class="com.acme.MyMessageAuthorizationPolicy" xmlns=""/>
</messageAuthorizationPolicy>
..
</broker>
-</plain-text-body><h2 id="Security-ImplementingyourowncustomSecurityPlugin">Implementing your own custom Security Plugin</h2><p>All of the various security implementations are implemented as <a shape="rect" href="interceptors.xml">Interceptors</a> so its very easy to add your own custom implementation. Its probably easier to start with one of the <a shape="rect" class="external-link" 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 shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/jaas/package-summary.html">JAAS implementation</a>.</p><h3 id="Security-ThirdPartyTools">Third Party Tools</h3><ul><li><a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_LDAP_JDBC_Security_Plugins.php" rel="nofollow">ActiveMQ LDAP and JDBC Security Plugins from TTM Solutions</a></li></ul></div>
+</plain-text-body><h2>Implementing your own custom Security Plugin</h2><p>All of the various security implementations are implemented as <link><page ri:content-title="Interceptors"></page></link> so its very easy to add your own custom implementation. Its probably easier to start with one of the <a shape="rect" 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 shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/jaas/package-summary.html">JAAS implementation</a>.</p><h3>Third Party Tools</h3><ul><li><a shape="rect" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_LDAP_JDBC_Security_Plugins.php">ActiveMQ LDAP and JDBC Security Plugins from TTM Solutions</a></li></ul></div>
diff --git a/seda.xml b/seda.xml
index a4a9583..3117fd8 100644
--- a/seda.xml
+++ b/seda.xml
@@ -1,5 +1,5 @@
<div class="wiki-content maincontent">
-<p>Staged Event Driven Architecture which is a design pattern for building high performance and scalable distributed systems. See <a shape="rect" class="external-link" href="http://www.eecs.harvard.edu/~mdw/proj/seda/" rel="nofollow">this paper</a> for more details.</p></div>
+<p>Staged Event Driven Architecture which is a design pattern for building high performance and scalable distributed systems. See <a shape="rect" href="http://www.eecs.harvard.edu/~mdw/proj/seda/">this paper</a> for more details.</p></div>
diff --git a/selectors.xml b/selectors.xml
index 6b5dbc4..4cf870d 100644
--- a/selectors.xml
+++ b/selectors.xml
@@ -1,39 +1,34 @@
-<div class="wiki-content maincontent"><h2 id="Selectors-JMSSelectors">JMS Selectors</h2>
+<div class="wiki-content maincontent"><h2>JMS Selectors</h2>
<p>Selectors are a way of attaching a filter to a subscription to perform content based routing. Selectors are defined using SQL 92 syntax and typically apply to message headers; whether the standard properties available on a JMS message or custom headers you can add via the JMS code.</p>
<p>Here is an example</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-JMSType = 'car' AND color = 'blue' AND weight > 2500
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="f3768a53-c6dc-48df-b415-351bc7ffc0ba" ac:name="code" ac:schema-version="1"><plain-text-body>
+JMSType = 'car' AND color = 'blue' AND weight > 2500
+</plain-text-body></structured-macro>
-<p>For more documentation on the detail of selectors see the reference on <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html" rel="nofollow">javax.jmx.Message</a>. <br clear="none">
-ActiveMQ supports some JMS defined properties, as well as some ActiveMQ ones - see <a shape="rect" href="activemq-message-properties.xml">message properies </a> - that the selector can use.</p>
+<p>For more documentation on the detail of selectors see the reference on <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html">javax.jmx.Message</a>. <br clear="none">
+ActiveMQ supports some JMS defined properties, as well as some ActiveMQ ones - see <link><page ri:content-title="ActiveMQ Message Properties"></page><link-body>message properies </link-body></link> - that the selector can use.</p>
-<h3 id="Selectors-UsingXPathtofiltermessages">Using XPath to filter messages</h3>
+<h3>Using XPath to filter messages</h3>
<p>Apache ActiveMQ also supports XPath based selectors when working with messages containing XML bodies. To use an XPath selector use the following syntax</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-XPATH '//title[@lang=''eng'']'
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="518e2e91-77e2-4043-8eb8-a0cb12d232f8" ac:name="code" ac:schema-version="1"><plain-text-body>
+XPATH '//title[@lang=''eng'']'
+</plain-text-body></structured-macro>
-<div class="confluence-information-macro confluence-information-macro-tip"><p class="title">Xalan dependency</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>XPath support requires <a shape="rect" class="external-link" href="http://xalan.apache.org/index.html">Xalan</a> which is not part of the distribution. The Xalan jars needs to be manually added to lib directory or pulled into your app via maven </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<dependency>
+<structured-macro ac:macro-id="a2264760-f437-4e30-aef0-a443c1339472" ac:name="tip" ac:schema-version="1"><parameter ac:name="title">Xalan dependency</parameter><rich-text-body>
+<p>XPath support requires <a shape="rect" href="http://xalan.apache.org/index.html">Xalan</a> which is not part of the distribution. The Xalan jars needs to be manually added to lib directory or pulled into your app via maven </p>
+<structured-macro ac:macro-id="50c8144b-97b0-4de2-866f-df74715a9173" ac:name="code" ac:schema-version="1"><plain-text-body><dependency>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.6.0</version>
-</dependency>]]></script>
-</div></div></div></div>
+</dependency></plain-text-body></structured-macro></rich-text-body></structured-macro>
-<h3 id="Selectors-StringPropertyConversions/SelectingAgainstSTOMPmessages">String Property Conversions / Selecting Against STOMP messages</h3>
+<h3>String Property Conversions / Selecting Against STOMP messages</h3>
-<p>The JMS spec states that a String property should not get converted to a numeric when used in a selector. So for example, if a message has the 'age' property set to String '21' then the following selector should not match it: 'age > 18'. Since ActiveMQ support STOMP client which can only send messages with string properties, that restriction is a bit limiting. If you want your JMS selectors to auto-convert String properties the the appropriate number type, just prefix the the selector with 'convert_string_expressions:'. If you changed selector in the previous example to be 'convert_string_expressions:age > 18', then it would match the message.</p></div>
+<p>The JMS spec states that a String property should not get converted to a numeric when used in a selector. So for example, if a message has the 'age' property set to String '21' then the following selector should not match it: 'age > 18'. Since ActiveMQ support STOMP client which can only send messages with string properties, that restriction is a bit limiting. If you want your JMS selectors to auto-convert String properties the the appropriate number type, just prefix the the selector with 'convert_string_expressions:'. If you changed selector in the previous example to be 'convert_string_expressions:age > 18', then it would match the message.</p>
+</div>
diff --git a/setting-up-activemq-with-tomcat-559.xml b/setting-up-activemq-with-tomcat-559.xml
index 3f45749..d55147e 100644
--- a/setting-up-activemq-with-tomcat-559.xml
+++ b/setting-up-activemq-with-tomcat-559.xml
@@ -1,51 +1,47 @@
<div class="wiki-content maincontent"><p>Create the file <webapp-root>/META-INF/context.xml. Here is an example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<Context antiJARLocking="true">
+<structured-macro ac:macro-id="7dd5eabb-c111-44ea-8f88-6ef5041b9159" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<Context antiJARLocking="true">
<Resource
- name="jms/ConnectionFactory"
- auth="Container"
- type="org.apache.activemq.ActiveMQConnectionFactory"
- description="JMS Connection Factory"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory"
- brokerURL="tcp://localhost:61616"
- brokerName="LocalActiveMQBroker"
- useEmbeddedBroker="false"/>
+ name="jms/ConnectionFactory"
+ auth="Container"
+ type="org.apache.activemq.ActiveMQConnectionFactory"
+ description="JMS Connection Factory"
+ factory="org.apache.activemq.jndi.JNDIReferenceFactory"
+ brokerURL="tcp://localhost:61616"
+ brokerName="LocalActiveMQBroker"
+ useEmbeddedBroker="false"/>
- <Resource name="jms/topic/MyTopic"
- auth="Container"
- type="org.apache.activemq.command.ActiveMQTopic"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory"
- physicalName="MY.TEST.FOO"/>
- <Resource name="jms/queue/MyQueue"
- auth="Container"
- type="org.apache.activemq.command.ActiveMQQueue"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory"
- physicalName="MY.TEST.FOO.QUEUE"/>
+ <Resource name="jms/topic/MyTopic"
+ auth="Container"
+ type="org.apache.activemq.command.ActiveMQTopic"
+ factory="org.apache.activemq.jndi.JNDIReferenceFactory"
+ physicalName="MY.TEST.FOO"/>
+ <Resource name="jms/queue/MyQueue"
+ auth="Container"
+ type="org.apache.activemq.command.ActiveMQQueue"
+ factory="org.apache.activemq.jndi.JNDIReferenceFactory"
+ physicalName="MY.TEST.FOO.QUEUE"/>
</Context>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This will setup the JNDI for the ConectionFactory and Topic to work within Tomcat.</p>
<p>Here is some example code that will publish a test message to the MY.TEST.FOO Topic:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b64cbd8a-16e8-45e4-ab6b-2dacc0a5b5c2" ac:name="code" ac:schema-version="1"><plain-text-body>
try {
InitialContext initCtx = new InitialContext();
- Context envContext = (Context) initCtx.lookup("java:comp/env");
- ConnectionFactory connectionFactory = (ConnectionFactory) envContext.lookup("jms/ConnectionFactory");
+ Context envContext = (Context) initCtx.lookup("java:comp/env");
+ ConnectionFactory connectionFactory = (ConnectionFactory) envContext.lookup("jms/ConnectionFactory");
Connection connection = connectionFactory.createConnection();
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
- MessageProducer producer = session.createProducer((Destination) envContext.lookup("jms/topic/MyTopic"));
+ MessageProducer producer = session.createProducer((Destination) envContext.lookup("jms/topic/MyTopic"));
Message testMessage = session.createMessage();
- testMessage.setStringProperty("testKey", "testValue");
+ testMessage.setStringProperty("testKey", "testValue");
producer.send(testMessage);
} catch (NamingException e) {
// TODO handle exception
} catch (JMSException e) {
// TODO handle exception
}
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/shared-file-system-master-slave.xml b/shared-file-system-master-slave.xml
index f599014..828d5bc 100644
--- a/shared-file-system-master-slave.xml
+++ b/shared-file-system-master-slave.xml
@@ -1,26 +1,16 @@
-<div class="wiki-content maincontent"><h2 id="SharedFileSystemMasterSlave-SharedFileSystemMasterSlave">Shared File System Master Slave</h2><p>If you have a SAN or shared file system it can be used to provide <em>high availability</em> such that if a broker is killed, another broker can take over immediately.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Ensure your shared file locks work</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Note that the requirements of this failover system are a distributed file system like a SAN for which exclusive file locks work reliably. If you do not have such a thing available then consider using <a shape="rect" href="masterslave.xml">MasterSlave</a> instead which implements something similar but working on commodity hardware using local file systems which ActiveMQ does the replication.</p><div class="confluence-information-macro confluence-information-macro-note"><p class="title">OCFS2 Warning</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Was testing using OCFS2 and both brokers thought they had the master lock - this is because "OCFS2 only supports locking with 'fcntl' and not 'lockf and flock', therefore mutex file locking from Java isn't supported."</p><p>From <a shape="rect" class="external-link" href="http://sources.redhat.com/cluster/faq.html#gfs_vs_ocfs2" rel="nofollow">http://sources.redhat.com/cluster/faq.html#gfs_vs_ocfs2</a> :<br clear="none"> OCFS2: No cluster-aware flock or POSIX locks<br clear="none"> GFS: fully supports Cluster-wide flocks and POSIX locks and is supported.<br clear="none"> See this JIRA for more discussion: <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4378">https://issues.apache.org/jira/browse/AMQ-4378</a></p></div></div><div class="confluence-information-macro confluence-information-macro-note"><p class="title">NFSv3 Warning</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>In the event of an abnormal NFSv3 client termination (i.e., the ActiveMQ master broker), the NFSv3 server will not timeout the lock that is held by that client. This effectively renders the ActiveMQ data directory inaccessible because the ActiveMQ slave broker can't acquire the lock and therefore cannot start up. The only solution to this predicament with NFSv3 is to reboot all ActiveMQ instances to reset everything.</p><p>Use of NFSv4 is another solution because its design includes timeouts for locks. When using NFSv4 and the client holding the lock experiences an abnormal termination, by design, the lock is released after 30 seconds, allowing another client to grab the lock. For more information about this, see <a shape="rect" class="external-link" href="http://blogs.netapp.com/eislers_nfs_blog/2008/07/part-i-since-nf.html" rel="nofollow">this blog entry</a>.</p></div></div></div></div><p>Basically you can run as many brokers as you wish from the same shared file system directory. The first broker to grab the exclusive lock on the file is the master broker. If that broker dies and releases the lock then another broker takes over. The slave brokers sit in a loop trying to grab the lock from the master broker.</p><p>The following example shows how to configure a broker for Shared File System Master Slave where <strong>/sharedFileSystem</strong> is some directory on a shared file system. It is just a case of configuring a file based store to use a shared directory.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <persistenceAdapter>
- <kahaDB directory="/sharedFileSystem/sharedBrokerData"/>
+<div class="wiki-content maincontent"><h2>Shared File System Master Slave</h2><p>If you have a SAN or shared file system it can be used to provide <em>high availability</em> such that if a broker is killed, another broker can take over immediately.</p><structured-macro ac:macro-id="85475cc1-b94a-45ca-901e-7c43a6763787" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Ensure your shared file locks work</parameter><rich-text-body><p>Note that the requirements of this failover system are a distributed file system like a SAN for which exclusive file locks work reliably. If you do not have such a thing available then consider using <link><page ri:content-title="MasterSlave"></page></link> instead which implements something similar but working on commodity hardware using local file systems which ActiveMQ does the replication.</p><structured-macro ac:macro-id="ac672a77-53f7-40b0-8cf1-4074d0cbf732" ac:name="note" ac:schema-version="1"><parameter ac:name="title">OCFS2 Warning</parameter><rich-text-body><p>Was testing using OCFS2 and both brokers thought they had the master lock - this is because "OCFS2 only supports locking with 'fcntl' and not 'lockf and flock', therefore mutex file locking from Java isn't supported."</p><p>From <a shape="rect" class="external-link" href="http://sources.redhat.com/cluster/faq.html#gfs_vs_ocfs2" rel="nofollow">http://sources.redhat.com/cluster/faq.html#gfs_vs_ocfs2</a> :<br clear="none"> OCFS2: No cluster-aware flock or POSIX locks<br clear="none"> GFS: fully supports Cluster-wide flocks and POSIX locks and is supported.<br clear="none"> See this JIRA for more discussion: <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4378">https://issues.apache.org/jira/browse/AMQ-4378</a></p></rich-text-body></structured-macro><structured-macro ac:macro-id="26037037-9d93-4407-807d-d8bb080027b9" ac:name="note" ac:schema-version="1"><parameter ac:name="title">NFSv3 Warning</parameter><rich-text-body><p>In the event of an abnormal NFSv3 client termination (i.e., the ActiveMQ master broker), the NFSv3 server will not timeout the lock that is held by that client. This effectively renders the ActiveMQ data directory inaccessible because the ActiveMQ slave broker can't acquire the lock and therefore cannot start up. The only solution to this predicament with NFSv3 is to reboot all ActiveMQ instances to reset everything.</p><p>Use of NFSv4 is another solution because its design includes timeouts for locks. When using NFSv4 and the client holding the lock experiences an abnormal termination, by design, the lock is released after 30 seconds, allowing another client to grab the lock. For more information about this, see <a shape="rect" href="http://blogs.netapp.com/eislers_nfs_blog/2008/07/part-i-since-nf.html">this blog entry</a>.</p></rich-text-body></structured-macro></rich-text-body></structured-macro><p>Basically you can run as many brokers as you wish from the same shared file system directory. The first broker to grab the exclusive lock on the file is the master broker. If that broker dies and releases the lock then another broker takes over. The slave brokers sit in a loop trying to grab the lock from the master broker.</p><p>The following example shows how to configure a broker for Shared File System Master Slave where <strong>/sharedFileSystem</strong> is some directory on a shared file system. It is just a case of configuring a file based store to use a shared directory.</p><structured-macro ac:macro-id="a9501ea9-3a9e-4a57-af82-e214b13403ef" ac:name="code" ac:schema-version="1"><plain-text-body> <persistenceAdapter>
+ <kahaDB directory="/sharedFileSystem/sharedBrokerData"/>
</persistenceAdapter>
-]]></script>
-</div></div><p>or:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <persistenceAdapter>
- <levelDB directory="/sharedFileSystem/sharedBrokerData"/>
+</plain-text-body></structured-macro><p>or:</p><structured-macro ac:macro-id="4ebd665a-ddb9-482b-824e-b47910adf715" ac:name="code" ac:schema-version="1"><plain-text-body> <persistenceAdapter>
+ <levelDB directory="/sharedFileSystem/sharedBrokerData"/>
</persistenceAdapter>
-]]></script>
-</div></div><p>or:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <persistenceAdapter>
- <amqPersistenceAdapter directory="/sharedFileSystem/sharedBrokerData"/>
+</plain-text-body></structured-macro><p>or:</p><structured-macro ac:macro-id="a610da29-a160-4831-902b-96258209f92a" ac:name="code" ac:schema-version="1"><plain-text-body> <persistenceAdapter>
+ <amqPersistenceAdapter directory="/sharedFileSystem/sharedBrokerData"/>
</persistenceAdapter>
-]]></script>
-</div></div><h3 id="SharedFileSystemMasterSlave-Startup">Startup</h3><p>On startup one master grabs an exclusive lock on the broker file directory - all other brokers are slaves and pause waiting for the exclusive lock.</p><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="shared-file-system-master-slave.data/Startup.png" data-image-src="/confluence/download/attachments/35958/Startup.png?version=1&modificationDate=1153806958000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3240" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Startup.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35958" data-linked-resource-container-version="22"></span></p><p>Clients should be using the <a shape="rect" href="failover-transport-reference.xml">Failover Transport</a> to connect to the available brokers. e.g. using a URL something like the following</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[failover:(tcp://broker1:61616,tcp://broker2:61616,tcp://broker3:61616)
-]]></script>
-</div></div><p>Only the master broker starts up its transport connectors and so the clients can only connect to the master.</p><h3 id="SharedFileSystemMasterSlave-Masterfailure">Master failure</h3><p>If the master looses the exclusive lock then it immediately shuts down. If a master shuts down or fails, one of the other slaves will grab the lock and so the topology switches to the following diagram</p><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="shared-file-system-master-slave.data/MasterFailed.png" data-image-src="/confluence/download/attachments/35958/MasterFailed.png?version=1&modificationDate=1153806959000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3255" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="MasterFailed.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35958" data-linked-resource-container-version="22"></span></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>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><h3 id="SharedFileSystemMasterSlave-Masterrestart">Master restart</h3><p>At any time you can restart other brokers which join the cluster and start as slaves waiting to become a master if the master is shutdown or a failure occurs. So the following topology is created after a restart of an old master...</p><p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="shared-file-system-master-slave.data/MasterRestarted.png" data-image-src="/confluence/download/attachments/35958/MasterRestarted.png?version=1&modificationDate=1153806958000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3247" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="MasterRestarted.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35958" data-linked-resource-container-version="22"></span></p><h3 id="SharedFileSystemMasterSlave-SchedulerSupport">Scheduler Support</h3><p>ActiveMQ maintains information about schedules independent to the settings in the persistence adapter. With a shared file-system it is therefore important to tell ActiveMQ expressly where to store scheduler information. To do this, set the <code>dataDirectory</code> attribute on the <code>broker</code>, for example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker xmlns="http://activemq.apache.org/schema/core"
-dataDirectory="/some/location"
-brokerName="mmuserb2" useJmx="true" advisorySupport="false"
-persistent="true" deleteAllMessagesOnStartup="false"
-useShutdownHook="false" schedulerSupport="true">]]></script>
-</div></div></div>
+</plain-text-body></structured-macro><h3>Startup</h3><p>On startup one master grabs an exclusive lock on the broker file directory - all other brokers are slaves and pause waiting for the exclusive lock.</p><p><image><attachment ri:filename="Startup.png"></attachment></image></p><p>Clients should be using the <link><page ri:content-title="Failover Transport Reference"></page><plain-text-link-body>Failover Transport</plain-text-link-body></link> to connect to the available brokers. e.g. using a URL something like the following</p><structured-macro ac:macro-id="3c51402a-0246-453c-9e5a-38fab6f25e75" ac:name="code" ac:schema-version="1"><plain-text-body>failover:(tcp://broker1:61616,tcp://broker2:61616,tcp://broker3:61616)
+</plain-text-body></structured-macro><p>Only the master broker starts up its transport connectors and so the clients can only connect to the master.</p><h3>Master failure</h3><p>If the master looses the exclusive lock then it immediately shuts down. If a master shuts down or fails, one of the other slaves will grab the lock and so the topology switches to the following diagram</p><p><image><attachment ri:filename="MasterFailed.png"></attachment></image></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>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><h3>Master restart</h3><p>At any time you can restart other brokers which join the cluster and start as slaves waiting to become a master if the master is shutdown or a failure occurs. So the following topology is created after a restart of an old master...</p><p><image><attachment ri:filename="MasterRestarted.png"></attachment></image></p><h3>Scheduler Support</h3><p>ActiveMQ maintains information about schedules independent to the settings in the persistence adapter. With a shared file-system it is therefore important to tell ActiveMQ expressly where to store scheduler information. To do this, set the <code>dataDirectory</code> attribute on the <code>broker</code>, for example:</p><structured-macro ac:macro-id="4f436336-254b-4003-8118-ee80b6f4c689" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><broker xmlns="http://activemq.apache.org/schema/core"
+dataDirectory="/some/location"
+brokerName="mmuserb2" useJmx="true" advisorySupport="false"
+persistent="true" deleteAllMessagesOnStartup="false"
+useShutdownHook="false" schedulerSupport="true"></plain-text-body></structured-macro></div>
diff --git a/shiro.xml b/shiro.xml
index 8b583f4..535ba65 100644
--- a/shiro.xml
+++ b/shiro.xml
@@ -1,15 +1,14 @@
-<div class="wiki-content maincontent"><p> </p><p>ActiveMQ 5.10 and later provides a fully customizable security experience using <a shape="rect" class="external-link" href="http://shiro.apache.org">Apache Shiro</a>.</p><p>The ActiveMQ Shiro plugin can secure the ActiveMQ broker, from authenticating transport connections to authorizing behavior with topics and queues and everything in between.</p><h2 id="Shiro-Quickstart">Quickstart</h2><p>The fastest/simplest way to enable the ShiroPlugin is to define it as a Spring bean in the <code>broker</code> <code>plugins</code> section and embed <a shape="rect" class="external-link" href="http://shiro.apache.org/configuration.html">Shiro ini configuration</a>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="
+<div class="wiki-content maincontent"><p> </p><p>ActiveMQ 5.10 and later provides a fully customizable security experience using <a shape="rect" href="http://shiro.apache.org">Apache Shiro</a>.</p><p>The ActiveMQ Shiro plugin can secure the ActiveMQ broker, from authenticating transport connections to authorizing behavior with topics and queues and everything in between.</p><h2>Quickstart</h2><p>The fastest/simplest way to enable the ShiroPlugin is to define it as a Spring bean in the <code>broker</code> <code>plugins</code> section and embed <a shape="rect" href="http://shiro.apache.org/configuration.html">Shiro ini configuration</a>:</p><structured-macro ac:macro-id="410790d6-bf71-4674-b71c-71a81928bdd4" ac:name="code" ac:schema-version="1"><plain-text-body><beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:amq="http://activemq.apache.org/schema/core"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
+ http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
- <broker xmlns="http://activemq.apache.org/schema/core" ... other attributes here ...>
+ <broker xmlns="http://activemq.apache.org/schema/core" ... other attributes here ...>
<plugins>
- <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
- <property name="iniConfig"><value>
+ <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <property name="iniConfig"><value>
[main]
# Shiro object graph configuration here if desired/necessary
@@ -25,7 +24,7 @@
#
# Roles and permissions assigned to roles are defined in the [roles] section
# below. By transitive association, any user assigned a role is granted the
- # role's permissions.
+ # role's permissions.
# ActiveMQ System User
# needed for in-VM/local connections when authentication is enabled:
@@ -42,7 +41,7 @@
#
# roleName = wildcardPermission1, wildcardPermission2, ..., wildcardPermissionN
#
- # The 'system' role is assigned all permissions (*). Be careful when assigning
+ # The 'system' role is assigned all permissions (*). Be careful when assigning
# this to actual users other than then system user:
system = *
@@ -52,7 +51,7 @@
#
# http://activemq.apache.org/security.html
#
- # So we create an 'advisory' role here with a wildcard/catch-all permissions
+ # So we create an 'advisory' role here with a wildcard/catch-all permissions
# for all advisory topics. To make your life easy, ensure you assign this to
# any/all users in the [users] section above, e.g.
#
@@ -65,11 +64,9 @@
</plugins>
</broker>
</beans>
-]]></script>
-</div></div><p>This config assumes you have a simple/small set of static users that access your ActiveMQ broker. We'll cover enabling more advanced user repositories later.</p><h4 id="Shiro-EncryptedPasswords">Encrypted Passwords</h4><p>The above example uses plaintext passwords, which is simple to set up and easy to use for testing, but not really secure. Most production deployments will likely want to use encrypted passwords. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+</plain-text-body></structured-macro><p>This config assumes you have a simple/small set of static users that access your ActiveMQ broker. We'll cover enabling more advanced user repositories later.</p><h4>Encrypted Passwords</h4><p>The above example uses plaintext passwords, which is simple to set up and easy to use for testing, but not really secure. Most production deployments will likely want to use encrypted passwords. For example:</p><structured-macro ac:macro-id="80a54d4f-b985-456b-9d96-b85f8974b9c8" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
<!-- enabled by default. To disable, uncomment:
- <property name="iniConfig"><value>
+ <property name="iniConfig"><value>
[main]
# Shiro object graph configuration here
@@ -85,44 +82,32 @@
advisory = topic:ActiveMQ.Advisory*
</value></property>
</bean>
-]]></script>
-</div></div><p>As you can see, two things are different than the simpler/default configuration:</p><ol><li>The <code>[main]</code> section configured a <code>PasswordMatcher</code> on the implicit <code>iniRealm</code>. This indicates that all <code>.ini</code>-configured users are expected to have proper hashed/secure passwords.</li><li>The <code>[users]</code> lines now have hash values in the <code>password</code> location instead of plaintext values.</li></ol><p>To get the hashed password text values, you will want to <a shape="rect" class="external-link" href="http://search.maven.org/remotecontent?filepath=org/apache/shiro/tools/shiro-tools-hasher/1.2.2/shiro-tools-hasher-1.2.2-cli.jar" rel="nofollow">Download Shiro's Command Line Hasher</a> from Maven Central. Once downloaded, you can use it to create secure password hashes that you can safely copy-and-paste in to the <code>[users]</code> section:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ java -jar shiro-tools-hasher-X.X.X-cli.jar -p
-]]></script>
-</div></div><p>It will then ask you to enter the password and then confirm it:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Password to hash:
+</plain-text-body></structured-macro><p>As you can see, two things are different than the simpler/default configuration:</p><ol><li>The <code>[main]</code> section configured a <code>PasswordMatcher</code> on the implicit <code>iniRealm</code>. This indicates that all <code>.ini</code>-configured users are expected to have proper hashed/secure passwords.</li><li>The <code>[users]</code> lines now have hash values in the <code>password</code> location instead of plaintext values.</li></ol><p>To get the hashed password text values, you will want to <a shape="rect" href="http://search.maven.org/remotecontent?filepath=org/apache/shiro/tools/shiro-tools-hasher/1.2.2/shiro-tools-hasher-1.2.2-cli.jar">Download Shiro's Command Line Hasher</a> from Maven Central. Once downloaded, you can use it to create secure password hashes that you can safely copy-and-paste in to the <code>[users]</code> section:</p><structured-macro ac:macro-id="790da932-f14a-46eb-84b5-f30042a6811a" ac:name="code" ac:schema-version="1"><plain-text-body>$ java -jar shiro-tools-hasher-X.X.X-cli.jar -p
+</plain-text-body></structured-macro><p>It will then ask you to enter the password and then confirm it:</p><structured-macro ac:macro-id="44da639a-a80b-458a-99ab-36a36213d8b2" ac:name="code" ac:schema-version="1"><plain-text-body>Password to hash:
Password to hash (confirm):
-]]></script>
-</div></div><p>When this command executes, it will print out the securely-salted-iterated-and-hashed password. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$shiro1$SHA-256$500000$eWpVX2tGX7WCP2J+jMCNqw==$it/NRclMOHrfOvhAEFZ0mxIZRdbcfqIBdwdwdDXW2dM=
-]]></script>
-</div></div><p>Take this value and place it as the password in the user definition line (followed by any desired roles, such as the <code>advisory</code> role). For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[[users]
+</plain-text-body></structured-macro><p>When this command executes, it will print out the securely-salted-iterated-and-hashed password. For example:</p><structured-macro ac:macro-id="c4c99adb-f812-4f21-a972-d924e3c67740" ac:name="code" ac:schema-version="1"><plain-text-body>$shiro1$SHA-256$500000$eWpVX2tGX7WCP2J+jMCNqw==$it/NRclMOHrfOvhAEFZ0mxIZRdbcfqIBdwdwdDXW2dM=
+</plain-text-body></structured-macro><p>Take this value and place it as the password in the user definition line (followed by any desired roles, such as the <code>advisory</code> role). For example:</p><structured-macro ac:macro-id="60b1b0b1-204f-40ef-a55e-2b5a5ad6b3b1" ac:name="code" ac:schema-version="1"><plain-text-body>[users]
scott = $shiro1$SHA-256$500000$eWpVX2tGX7WCP2J+jMCNqw==$it/NRclMOHrfOvhAEFZ0mxIZRdbcfqIBdwdwdDXW2dM=, advisory
system = $shiro1$SHA-256$500000$eUyGwMGr9GYzB/gg/MoNgw==$WGc0yWFWv8+hLqjzVLgW7Hat2FQTywDXBl5izpqaLSY=, system
-]]></script>
-</div></div><h2 id="Shiro-Configuration">Configuration</h2><p>The ActiveMQ Shiro plugin can be configured in a number of ways. For example, with Java:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[BrokerService brokerService = new BrokerService();
+</plain-text-body></structured-macro><h2>Configuration</h2><p>The ActiveMQ Shiro plugin can be configured in a number of ways. For example, with Java:</p><structured-macro ac:macro-id="dd6c68e7-e08e-40a3-b8b0-853344a52c3f" ac:name="code" ac:schema-version="1"><plain-text-body>BrokerService brokerService = new BrokerService();
ShiroPlugin shiroPlugin = new ShiroPlugin();
//configure shiroPlugin via getters/setters here
broker.setPlugins(new BrokerPlugin[]{shiroPlugin});
//continue configuring the brokerService as necessary ...
-]]></script>
-</div></div><p>Or, if using traditional ActiveMQ xml, as a Spring bean in the <code>broker</code> <code>plugins</code> section. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="
+</plain-text-body></structured-macro><p>Or, if using traditional ActiveMQ xml, as a Spring bean in the <code>broker</code> <code>plugins</code> section. For example:</p><structured-macro ac:macro-id="8f5044da-28d5-4ab3-960f-7bcc8afcb793" ac:name="code" ac:schema-version="1"><plain-text-body><beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:amq="http://activemq.apache.org/schema/core"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
+ http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
- <broker xmlns="http://activemq.apache.org/schema/core" ... other attributes here ...>
+ <broker xmlns="http://activemq.apache.org/schema/core" ... other attributes here ...>
<plugins>
- <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
<!-- Config properties via getters/setters as necessary: -->
</bean>
@@ -130,96 +115,84 @@
</broker>
</beans>
-]]></script>
-</div></div><p>The remaining configuration examples on this page will be shown as bean XML, but know that the same configuration can be done in Java as standard JavaBeans-compatible getter and setter methods.</p><h3 id="Shiro-Enabling/Disabling">Enabling/Disabling</h3><p>You can enable or disable the ShiroPlugin entirely without having to remove it from your configuration. This is convenient when testing, or when you want to enable or disable it based on a configuration parameter at startup.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+</plain-text-body></structured-macro><p>The remaining configuration examples on this page will be shown as bean XML, but know that the same configuration can be done in Java as standard JavaBeans-compatible getter and setter methods.</p><h3>Enabling/Disabling</h3><p>You can enable or disable the ShiroPlugin entirely without having to remove it from your configuration. This is convenient when testing, or when you want to enable or disable it based on a configuration parameter at startup.</p><structured-macro ac:macro-id="30beb787-00a0-43a7-b9c7-d248f43355e7" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
<!-- enabled by default. To disable, uncomment:
- <property name="enabled" value="false"/> -->
+ <property name="enabled" value="false"/> -->
</bean>
-]]></script>
-</div></div><p>A nice technique is to use Spring's <a shape="rect" class="external-link" href="http://static.springsource.org/spring/docs/3.2.x/javadoc-api/org/springframework/context/support/PropertySourcesPlaceholderConfigurer.html" rel="nofollow">PropertySourcesPlaceholderConfigurer</a> and placeholder tokens (set <code>shiro.enabled = true</code> in one of your placeholder property files):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans ...>
+</plain-text-body></structured-macro><p>A nice technique is to use Spring's <a shape="rect" href="http://static.springsource.org/spring/docs/3.2.x/javadoc-api/org/springframework/context/support/PropertySourcesPlaceholderConfigurer.html">PropertySourcesPlaceholderConfigurer</a> and placeholder tokens (set <code>shiro.enabled = true</code> in one of your placeholder property files):</p><structured-macro ac:macro-id="8a00e352-47a8-4d57-a718-9c828da661f4" ac:name="code" ac:schema-version="1"><plain-text-body><beans ...>
- <bean class="org.springframework.context.support.PropertySourcesPlaceholderConfigurer">
+ <bean class="org.springframework.context.support.PropertySourcesPlaceholderConfigurer">
...
</bean>
<broker ...>
<plugins ...>
- <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
- <property name="enabled" value="${shiro.enabled}"/>
+ <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <property name="enabled" value="${shiro.enabled}"/>
</bean>
</plugins>
</broker>
</beans>
-]]></script>
-</div></div><p>This allows you to enable or disable the Shiro plugin by simply setting a property in a <code>.properties</code> file without having to change your XML config.</p><h3 id="Shiro-ShiroEnvironment">Shiro Environment</h3><p>The <code>shiroPlugin</code> requires a Shiro <a shape="rect" class="external-link" href="http://shiro.apache.org/static/current/apidocs/org/apache/shiro/env/Environment.html">Environment</a> to function. You must either configure the plugin with:</p><ul><li>an <code>Environment</code> instance (or a Shiro <code>SecurityManager</code> instance) that you instantiate and configure elsewhere - e.g. in Java code or elsewhere in the Spring XML config, or</li><li>specify some Shiro <a shape="rect" class="external-link" href="http://shiro.apache.org/configuration.html">.ini configuration</a>, either as a direct String, an <a shape="rect" class="external-link" href="http://shiro.apache.org/static/current/apidocs/org/apache/shiro/config/Ini.html">Ini</a> instance, or a <a shape="rect" class="external-link" href="http://shiro.apache.org/static/current/apidocs/org/apache/shiro/io/ResourceUtils.html#getInputStreamForPath(java.lang.String)">resource path</a> where your <code>shiro.ini</code> file is located. The plugin will load the ini config and create an <code>Environment</code> automatically.</li></ul><h4 id="Shiro-CustomEnvironment">Custom Environment</h4><p>A Shiro <code>Environment</code> object contains everything that Shiro needs to operate, and this encapsulates the Shiro <code>SecurityManager</code> as well. If you want to construct and configure an Environment instance yourself:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans ...>
+</plain-text-body></structured-macro><p>This allows you to enable or disable the Shiro plugin by simply setting a property in a <code>.properties</code> file without having to change your XML config.</p><h3>Shiro Environment</h3><p>The <code>shiroPlugin</code> requires a Shiro <a shape="rect" href="http://shiro.apache.org/static/current/apidocs/org/apache/shiro/env/Environment.html">Environment</a> to function. You must either configure the plugin with:</p><ul><li>an <code>Environment</code> instance (or a Shiro <code>SecurityManager</code> instance) that you instantiate and configure elsewhere - e.g. in Java code or elsewhere in the Spring XML config, or</li><li>specify some Shiro <a shape="rect" href="http://shiro.apache.org/configuration.html">.ini configuration</a>, either as a direct String, an <a shape="rect" href="http://shiro.apache.org/static/current/apidocs/org/apache/shiro/config/Ini.html">Ini</a> instance, or a <a shape="rect" href="http://shiro.apache.org/static/current/apidocs/org/apache/shiro/io/ResourceUtils.html#getInputStreamForPath(java.lang.String)">resource path</a> where your <code>shiro.ini</code> file is located. The plugin will load the ini config and create an <code>Environment</code> automatically.</li></ul><h4>Custom Environment</h4><p>A Shiro <code>Environment</code> object contains everything that Shiro needs to operate, and this encapsulates the Shiro <code>SecurityManager</code> as well. If you want to construct and configure an Environment instance yourself:</p><structured-macro ac:macro-id="b10b03b1-a900-471b-a1f2-92eb4b74eccb" ac:name="code" ac:schema-version="1"><plain-text-body><beans ...>
<broker ...>
<plugins>
- <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
- <property name="environment" ref="shiroEnvironment"/>
+ <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <property name="environment" ref="shiroEnvironment"/>
</bean>
</plugins>
</broker>
- <bean id="shiroEnvironment" class="..">
+ <bean id="shiroEnvironment" class="..">
... config here ...
</bean>
- <bean class="org.apache.shiro.spring.LifecycleBeanPostProcessor"/>
+ <bean class="org.apache.shiro.spring.LifecycleBeanPostProcessor"/>
</beans>
-]]></script>
-</div></div><h4 id="Shiro-CustomSecurityManager">Custom SecurityManager</h4><p>Instead of configuring an <code>Environment</code> instance, you can construct a <code>SecurityManager</code> instead:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans ...>
+</plain-text-body></structured-macro><h4>Custom SecurityManager</h4><p>Instead of configuring an <code>Environment</code> instance, you can construct a <code>SecurityManager</code> instead:</p><structured-macro ac:macro-id="e2b2eab0-f4cf-4f84-a1cb-e91d57883d88" ac:name="code" ac:schema-version="1"><plain-text-body><beans ...>
<broker ...>
<plugins>
- <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
- <property name="securityManager" ref="shiroSecurityManager"/>
+ <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <property name="securityManager" ref="shiroSecurityManager"/>
</bean>
</plugins>
</broker>
- <bean id="shiroSecurityManager" class="org.apache.shiro.mgt.DefaultSecurityManager">
- <property name="realms">
+ <bean id="shiroSecurityManager" class="org.apache.shiro.mgt.DefaultSecurityManager">
+ <property name="realms">
<list>
- <bean id="myRealm" class="...">
+ <bean id="myRealm" class="...">
...
</bean>
... maybe more Realm beans ...
</list>
</property>
</bean>
- <bean class="org.apache.shiro.spring.LifecycleBeanPostProcessor"/>
+ <bean class="org.apache.shiro.spring.LifecycleBeanPostProcessor"/>
</beans>
-]]></script>
-</div></div><p>If specifying a <code>SecurityManager</code> instead of the <code>Environment</code> property, an <code>Environment</code> will be created automatically that wraps the configured <code>SecurityManager</code>.</p><h4 id="Shiro-shiro.iniFile">shiro.ini File</h4><p>If you don't want to construct a <code>SecurityManager</code> or <code>Environment</code> in code or xml, you can easily specify a <a shape="rect" class="external-link" href="http://shiro.apache.org/configuration.html">shiro.ini</a> file instead and an Environment/SecurityManager will automatically be created based on that:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans ...>
+</plain-text-body></structured-macro><p>If specifying a <code>SecurityManager</code> instead of the <code>Environment</code> property, an <code>Environment</code> will be created automatically that wraps the configured <code>SecurityManager</code>.</p><h4>shiro.ini File</h4><p>If you don't want to construct a <code>SecurityManager</code> or <code>Environment</code> in code or xml, you can easily specify a <a shape="rect" href="http://shiro.apache.org/configuration.html">shiro.ini</a> file instead and an Environment/SecurityManager will automatically be created based on that:</p><structured-macro ac:macro-id="8342078e-7dd0-42f5-ab58-e00e225b4023" ac:name="code" ac:schema-version="1"><plain-text-body><beans ...>
<broker ...>
<plugins>
- <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
- <property name="iniResourcePath" value="classpath:myshiro.ini"/>
+ <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <property name="iniResourcePath" value="classpath:myshiro.ini"/>
</bean>
</plugins>
</broker>
</beans>
-]]></script>
-</div></div><p>This allows you to keep your Shiro config separate from your ActiveMQ broker configuration if you prefer.</p><h4 id="Shiro-shiro.iniEmbedded">shiro.ini Embedded</h4><p>If you want to use ini configuration and you would prefer to have all configuration in one place, you can embed the ini config instead:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans ...>
+</plain-text-body></structured-macro><p>This allows you to keep your Shiro config separate from your ActiveMQ broker configuration if you prefer.</p><h4>shiro.ini Embedded</h4><p>If you want to use ini configuration and you would prefer to have all configuration in one place, you can embed the ini config instead:</p><structured-macro ac:macro-id="7c1da3f0-e830-4697-9133-19700c4141ec" ac:name="code" ac:schema-version="1"><plain-text-body><beans ...>
<broker ...>
<plugins ...>
- <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
- <property name="iniConfig">
+ <bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <property name="iniConfig">
<value>
[main]
@@ -238,20 +211,15 @@
</plugins>
</broker>
</beans>
-]]></script>
-</div></div><h2 id="Shiro-Design">Design</h2><p>The Shiro plugin is a <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerPlugin.html">BrokerPlugin</a> that inserts 3 <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html">BrokerFilter</a>s in the broker filter chain: the <code>SubjectFilter</code>, the <code>AuthenticationFilter</code> and the <code>AuthorizationFilter</code></p><p><strong>SubjectFilter</strong></p><p>The <code>SubjectFilter</code> exists before all other Shiro-related broker filters in the broker filter chain. It constructs a Shiro <a shape="rect" class="external-link" href="http://shiro.apache.org/subject.html">Subject</a> instance reflecting the broker client and ensures the <code>Subject</code> instance is available for all downstream broker filters that may need to use the <code>Subject</code> to perform security operations.</p><p><strong>AuthenticationFilter</strong></p><p>The <code>AuthenticationFilter</code> exists immediately after the <code>SubjectFilter</code> in the broker filter chain. It ensures that the broker client <code>Subject</code> is authenticated if necessary before allowing the chain to continue. If authentication is required and the <code>Subject</code> is not authenticated, the broker filter chain will not be executed, ensuring only verified identities may perform further behavior.</p><p><strong>AuthorizationFilter</strong></p><p>The <code>AuthorizationFilter</code> exists immediately after the <code>AuthenticationFilter</code> in the broker filter chain. It ensures that the <code>Subject</code> associated with the filter chain is authorized (permitted) to perform the action being attempted before allowing the action to execute.</p><p>For example, it would ensure that the <code>Subject</code> is allowed to send a message to a particular topic before allowing the send operation to execute. If authorization is enabled and the <code>Subject</code> is not authorized to perform the desired action, the broker filter chain will not be executed.</p><h2 id="Shiro-SubjectFilter">SubjectFilter</h2><p>The ShiroPlugin installs and executes the <code>SubjectFilter</code> before all other Shiro-related broker filters in the broker filter chain. The <code>SubjectFilter</code> constructs a Shiro <a shape="rect" class="external-link" href="http://shiro.apache.org/subject.html">Subject</a> instance reflecting the broker client and ensures the <code>Subject</code> instance is available for all downstream broker filters that may need to use the <code>Subject</code> to perform security operations.</p><p>The <code>SubjectFilter</code> is mostly a 'behind the scenes' component of the SubjectFilter, but it does offer some customization for advanced use cases:</p><ul><li>the ability to customize exactly how broker clients' <code>Subject</code> instances are created via a <code>ConnectionSubjectFactory</code> and</li><li>the ability to customize how the ActiveMQ ConnectionContext's <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/security/SecurityContext.html">SecurityContext</a> is constructed.</li></ul><p>Unless you're deeply familiar with ActiveMQ's security model, you can safely skip to <strong>Authentication</strong> below.</p><h3 id="Shiro-ConnectionSubjectFactory">ConnectionSubjectFactory</h3><p>A <code>ConnectionSubjectFactory</code> creates a <code>Subject</code> instance that represents the broker client's identity. The <code>SubjectFilter</code>'s default instance is a <code>DefaultConnectionSubjectFactory</code></p><p>Most <code>ConnectionSubjectFactory</code> implementations will simply use Shiro's <code>Subject.Builder</code> to create an anonymous Subject instance and let the downstream <code>AuthenticationFilter</code> authenticate the Subject based on any credentials associated with the connection. After authentication, the Subject will have an identity, and this is the expected flow for most connection clients.</p><p>However, if there is some other data associated with the connection that can be inspected to create a Subject instance beyond what the <code>DefaultConnectionSubjectFactory</code>, you can implement the <code>ConnectionSubjectFactory</code> interface and plug it in to the <code>SubjectFilter</code>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
- <property name="subjectFilter.connectionSubjectFactory">
- <bean class="com.my.ConnectionSubjectFactory" .../>
+</plain-text-body></structured-macro><h2>Design</h2><p>The Shiro plugin is a <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerPlugin.html">BrokerPlugin</a> that inserts 3 <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/BrokerFilter.html">BrokerFilter</a>s in the broker filter chain: the <code>SubjectFilter</code>, the <code>AuthenticationFilter</code> and the <code>AuthorizationFilter</code></p><p><strong>SubjectFilter</strong></p><p>The <code>SubjectFilter</code> exists before all other Shiro-related broker filters in the broker filter chain. It constructs a Shiro <a shape="rect" href="http://shiro.apache.org/subject.html">Subject</a> instance reflecting the broker client and ensures the <code>Subject</code> instance is available for all downstream broker filters that may need to use the <code>Subject</code> to perform security operations.</p><p><strong>AuthenticationFilter</strong></p><p>The <code>AuthenticationFilter</code> exists immediately after the <code>SubjectFilter</code> in the broker filter chain. It ensures that the broker client <code>Subject</code> is authenticated if necessary before allowing the chain to continue. If authentication is required and the <code>Subject</code> is not authenticated, the broker filter chain will not be executed, ensuring only verified identities may perform further behavior.</p><p><strong>AuthorizationFilter</strong></p><p>The <code>AuthorizationFilter</code> exists immediately after the <code>AuthenticationFilter</code> in the broker filter chain. It ensures that the <code>Subject</code> associated with the filter chain is authorized (permitted) to perform the action being attempted before allowing the action to execute.</p><p>For example, it would ensure that the <code>Subject</code> is allowed to send a message to a particular topic before allowing the send operation to execute. If authorization is enabled and the <code>Subject</code> is not authorized to perform the desired action, the broker filter chain will not be executed.</p><h2>SubjectFilter</h2><p>The ShiroPlugin installs and executes the <code>SubjectFilter</code> before all other Shiro-related broker filters in the broker filter chain. The <code>SubjectFilter</code> constructs a Shiro <a shape="rect" href="http://shiro.apache.org/subject.html">Subject</a> instance reflecting the broker client and ensures the <code>Subject</code> instance is available for all downstream broker filters that may need to use the <code>Subject</code> to perform security operations.</p><p>The <code>SubjectFilter</code> is mostly a 'behind the scenes' component of the SubjectFilter, but it does offer some customization for advanced use cases:</p><ul><li>the ability to customize exactly how broker clients' <code>Subject</code> instances are created via a <code>ConnectionSubjectFactory</code> and</li><li>the ability to customize how the ActiveMQ ConnectionContext's <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/security/SecurityContext.html">SecurityContext</a> is constructed.</li></ul><p>Unless you're deeply familiar with ActiveMQ's security model, you can safely skip to <strong>Authentication</strong> below.</p><h3>ConnectionSubjectFactory</h3><p>A <code>ConnectionSubjectFactory</code> creates a <code>Subject</code> instance that represents the broker client's identity. The <code>SubjectFilter</code>'s default instance is a <code>DefaultConnectionSubjectFactory</code></p><p>Most <code>ConnectionSubjectFactory</code> implementations will simply use Shiro's <code>Subject.Builder</code> to create an anonymous Subject instance and let the downstream <code>AuthenticationFilter</code> authenticate the Subject based on any credentials associated with the connection. After authentication, the Subject will have an identity, and this is the expected flow for most connection clients.</p><p>However, if there is some other data associated with the connection that can be inspected to create a Subject instance beyond what the <code>DefaultConnectionSubjectFactory</code>, you can implement the <code>ConnectionSubjectFactory</code> interface and plug it in to the <code>SubjectFilter</code>:</p><structured-macro ac:macro-id="24a32c24-9100-4131-a2cf-3ca2f1df9224" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <property name="subjectFilter.connectionSubjectFactory">
+ <bean class="com.my.ConnectionSubjectFactory" .../>
</property>
</bean>
-]]></script>
-</div></div><h3 id="Shiro-SecurityContextFactory">SecurityContextFactory</h3><p>The ActiveMQ <code>ConnectionContext</code> associated with broker client connections utilizes a <code>SecurityContext</code> object. When the <code>SubjectFilter</code> executes, it needs to create a Shiro-specific <code>SecurityContext</code> and associate it with the <code>ConnectionContext</code> so the Subject may be accessed downstream for all subsequent security operations.</p><p>The <code>SubjectFilter</code> delegates <code>SecurityContext</code> creation to a <code>SecurityContextFactory</code> instance. The <code>DefaultSecurityContextFactory</code> implementation returns <code>SubjectSecurityContext</code> instances based on the connection's associated <code>Subject</code>. It should be an extremely rare thing to change, but if you must configure a custom <code>SecurityContextFactory</code>, you can do as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
- <property name="subjectFilter.securityContextFactory">
- <bean class="com.my.SecurityContextFactory" .../>
+</plain-text-body></structured-macro><h3>SecurityContextFactory</h3><p>The ActiveMQ <code>ConnectionContext</code> associated with broker client connections utilizes a <code>SecurityContext</code> object. When the <code>SubjectFilter</code> executes, it needs to create a Shiro-specific <code>SecurityContext</code> and associate it with the <code>ConnectionContext</code> so the Subject may be accessed downstream for all subsequent security operations.</p><p>The <code>SubjectFilter</code> delegates <code>SecurityContext</code> creation to a <code>SecurityContextFactory</code> instance. The <code>DefaultSecurityContextFactory</code> implementation returns <code>SubjectSecurityContext</code> instances based on the connection's associated <code>Subject</code>. It should be an extremely rare thing to change, but if you must configure a custom <code>SecurityContextFactory</code>, you can do as follows:</p><structured-macro ac:macro-id="4d0d08f3-a136-4932-882e-aabd81e6d568" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="shiroPlugin" class="org.apache.activemq.shiro.ShiroPlugin" xmlns="http://www.springframework.org/schema/beans">
+ <property name="subjectFilter.securityContextFactory">
+ <bean class="com.my.SecurityContextFactory" .../>
</property>
</bean>
-]]></script>
-</div></div><p>Note however that much of the plugin's functionality and downstream filters expect created <code>SecurityContext</code> instances to be <code>SubjectSecurityContext</code> instances.</p><h2 id="Shiro-Authentication">Authentication</h2><p>The ShiroPlugin installs the <code>AuthenticationFilter</code> immediately after the <code>SubjectFilter</code> in the broker filter chain. The <code>AuthenticationFilter</code> ensures that the broker client <code>Subject</code> is authenticated if necessary before allowing the chain to continue. If authentication is required and the <code>Subject</code> is not authenticated, the broker filter chain will not be executed, ensuring only verified identities may perform further behavior.</p><p>WORK IN PROGRESS - STILL AUTHORING</p></div>
+</plain-text-body></structured-macro><p>Note however that much of the plugin's functionality and downstream filters expect created <code>SecurityContext</code> instances to be <code>SubjectSecurityContext</code> instances.</p><h2>Authentication</h2><p>The ShiroPlugin installs the <code>AuthenticationFilter</code> immediately after the <code>SubjectFilter</code> in the broker filter chain. The <code>AuthenticationFilter</code> ensures that the broker client <code>Subject</code> is authenticated if necessary before allowing the chain to continue. If authentication is required and the <code>Subject</code> is not authenticated, the broker filter chain will not be executed, ensuring only verified identities may perform further behavior.</p><p>WORK IN PROGRESS - STILL AUTHORING</p></div>
diff --git a/should-i-deploy-enterprise-integration-patterns-in-the-broker-or-another-application.xml b/should-i-deploy-enterprise-integration-patterns-in-the-broker-or-another-application.xml
index 486ef57..2663376 100644
--- a/should-i-deploy-enterprise-integration-patterns-in-the-broker-or-another-application.xml
+++ b/should-i-deploy-enterprise-integration-patterns-in-the-broker-or-another-application.xml
@@ -1,20 +1,21 @@
-<div class="wiki-content maincontent"><h2 id="ShouldIdeployEnterpriseIntegrationPatternsinthebrokeroranotherapplication-ShouldIdeployEnterpriseIntegrationPatternsinthebrokeroranotherapplication">Should I deploy Enterprise Integration Patterns in the broker or another application</h2>
+<div class="wiki-content maincontent"><h2>Should I deploy Enterprise Integration Patterns in the broker or another application</h2>
-<p>Whether you deploy the <a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> inside the ActiveMQ Broker or in a separate application depends on your requirements. </p>
+<p>Whether you deploy the <link><page ri:content-title="Enterprise Integration Patterns"></page></link> inside the ActiveMQ Broker or in a separate application depends on your requirements. </p>
-<h3 id="ShouldIdeployEnterpriseIntegrationPatternsinthebrokeroranotherapplication-AdvantagesofdeployingEIPinsidethebroker">Advantages of deploying EIP inside the broker</h3>
+<h3>Advantages of deploying EIP inside the broker</h3>
-<ul><li>Its a single JVM so less moving parts and you're less likely to forget to deploy something</li><li>if you are doing things like polling resources such as files, databases and bridging them to queues or topics then its usually more efficient to host in the broker; as there's less contention and there's no network communication between the EIP rules and the message broker as its all in the same JVM (so you can use the <a shape="rect" href="vm-transport-reference.xml">VM Transport</a> to avoid network overhead.</li></ul>
+<ul><li>Its a single JVM so less moving parts and you're less likely to forget to deploy something</li><li>if you are doing things like polling resources such as files, databases and bridging them to queues or topics then its usually more efficient to host in the broker; as there's less contention and there's no network communication between the EIP rules and the message broker as its all in the same JVM (so you can use the <link><page ri:content-title="VM Transport Reference"></page><link-body>VM Transport</link-body></link> to avoid network overhead.</li></ul>
-<h3 id="ShouldIdeployEnterpriseIntegrationPatternsinthebrokeroranotherapplication-AdvantagesofdeployingEIPinsideaseparateapplication">Advantages of deploying EIP inside a separate application</h3>
+<h3>Advantages of deploying EIP inside a separate application</h3>
-<ul><li>its easier to deploy loads of JVMs containing the EIP routing rules to get better load balancing</li><li>you can easily change your routing rules then stop/restart applications without having to restart your broker. Having said that since ActiveMQ supports <a shape="rect" href="how-can-i-support-auto-reconnection.xml">auto reconnection</a> its not such a big deal to bounce the Broker now and again to refresh routing rules. Note that at some point <a shape="rect" class="external-link" href="https://issues.apache.org/activemq/browse/CAMEL-234">Camel will support auto-reload of routing rules on the fly without having to stop and reload the JVM</a> so one day this won't be such a big benefit.</li></ul>
+<ul><li>its easier to deploy loads of JVMs containing the EIP routing rules to get better load balancing</li><li>you can easily change your routing rules then stop/restart applications without having to restart your broker. Having said that since ActiveMQ supports <link><page ri:content-title="How can I support auto reconnection"></page><link-body>auto reconnection</link-body></link> its not such a big deal to bounce the Broker now and again to refresh routing rules. Note that at some point <a shape="rect" href="https://issues.apache.org/activemq/browse/CAMEL-234">Camel will support auto-reload of routing rules on the fly without having to stop and reload the JVM</a> so one day this won't be such a big benefit.</li></ul>
-<h3 id="ShouldIdeployEnterpriseIntegrationPatternsinthebrokeroranotherapplication-SeeAlso">See Also</h3>
+<h3>See Also</h3>
-<ul><li><a shape="rect" href="should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml">Should I deploy the broker inside my JVM or AppServer</a></li></ul>
+<ul><li><link><page ri:content-title="Should I deploy the broker inside my JVM or AppServer"></page></link></li></ul>
+
</div>
diff --git a/should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml b/should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml
index 487fb64..afb48ba 100644
--- a/should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml
+++ b/should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml
@@ -1,21 +1,22 @@
<div class="wiki-content maincontent"><p>You can deploy the ActiveMQ Broker inside your JVM or Application Server. Whether you do or not has pros and cons depending on how many JVMs you have and what your backup & recovery policy is.</p>
-<h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-Advantagesofembeddingthebroker">Advantages of embedding the broker</h3>
+<h3>Advantages of embedding the broker</h3>
<ul><li>embedding a broker means you can use the VM transport which avoids the use of sockets and serialization. Instead ActiveMQ can pass around messages by value.
- <ul><li>the slight exception to this is ObjectMessage; the JMS specification says you must serialize the body of the ObjectMessage whenever you send it. However you can <a shape="rect" href="how-should-i-use-the-vm-transport.xml">disable this feature</a> if you want really high performance when using VM transport</li></ul>
+ <ul><li>the slight exception to this is ObjectMessage; the JMS specification says you must serialize the body of the ObjectMessage whenever you send it. However you can <link><page ri:content-title="How should I use the VM transport"></page><link-body>disable this feature</link-body></link> if you want really high performance when using VM transport</li></ul>
</li><li>its only 1 single deployment unit/JVM rather than 2 coupled processes.</li></ul>
-<h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-Disadvantagesofembeddingthebroker">Disadvantages of embedding the broker</h3>
+<h3>Disadvantages of embedding the broker</h3>
<p>If you have lots of JVMs (say 100s of them) and have very stringent requirements; you don't ever want to loose a message and so you want to backup and manage the persistent ActiveMQ database (and/or files) very carefully.</p>
<p>Having an embdded broker inside each JVM could result in large number of sets of files to manage. So it may be simpler to separate the two out, so that your 100s of JVMs talk to a relatively small cluster of brokers (say 2-10 of them) so that you can avoid worrying about persistent state in each JVM and just focus on backing up and managing the files/databases used by the brokers.</p>
-<p>Also its typically easier to run and manage ActiveMQ brokers when they are separate; you can have some ClassLoader issues when trying to embed ActiveMQ inside an application server. e.g. you can sometimes get <a shape="rect" href="javalangnosuchmethoderror.xml">ClassPath Errors </a></p>
+<p>Also its typically easier to run and manage ActiveMQ brokers when they are separate; you can have some ClassLoader issues when trying to embed ActiveMQ inside an application server. e.g. you can sometimes get <link><page ri:content-title="java.lang.NoSuchMethodError"></page><link-body>ClassPath Errors </link-body></link></p>
-<h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-See">See</h3>
+<h3>See</h3>
-<ul><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li><li><a shape="rect" href="run-broker.xml">Run Broker</a></li></ul></div>
+<ul><li><link><page ri:content-title="How do I embed a Broker inside a Connection"></page></link></li><li><link><page ri:content-title="Run Broker"></page></link></li></ul>
+</div>
diff --git a/should-i-run-activemq-on-windows-in-a-directory-with-spaces.xml b/should-i-run-activemq-on-windows-in-a-directory-with-spaces.xml
index 70131f8..cb7ad45 100644
--- a/should-i-run-activemq-on-windows-in-a-directory-with-spaces.xml
+++ b/should-i-run-activemq-on-windows-in-a-directory-with-spaces.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="ShouldIrunActiveMQonWindowsinadirectorywithspaces-ShouldIrunActiveMQonWindowsinadirectorywithspaces">Should I run ActiveMQ on Windows in a directory with spaces</h2>
+<div class="wiki-content maincontent"><h2>Should I run ActiveMQ on Windows in a directory with spaces</h2>
<p>No.</p>
diff --git a/should-i-use-transactions.xml b/should-i-use-transactions.xml
index 70e689d..868ce58 100644
--- a/should-i-use-transactions.xml
+++ b/should-i-use-transactions.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>There are four main approaches as to a client can consume messages. They are:</p><ol><li>Auto-acknowledgement</li><li>Explicit acknowledgement via <strong><code>Message.acknowledge()</code></strong></li><li>JMS Transactions</li><li>XA</li></ol><p>For a discussion on XA see: <a shape="rect" href="should-i-use-xa.xml">Should I use XA</a></p><p>The main difference between 1 & 2 and 3 & 4 is the latter allow messages to be rolled back and redelivered if an error occurs whilst processing. There is no JMS 'unacknowledge'. So for this reason JMS transactions should be preferred to message acknowledgements in most use cases.</p><p>It's a common misconception that transactions are inherently slow. In reality there's little difference in performance, from the broker's perspective, between the use of a JMS transaction and invoking <strong><code>Message.acknowledge()</code></strong>. However, a performance penalty is incurred when the delivery mode is set to  persistent. This causes the broker to block until the commit is synchronized to disk. This is similar to how <strong><code>Message.acknowledge()</code></strong> blocks when using a non-transactional JMS session.</p><div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">Transaction support is also available for non-persistent delivery mode.</div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Batched Transactions Are The Fastest Way To Process Messages!</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">It's worth noting that the fastest way to consume persistent messages is to use a JMS transaction combined with message batching, e.g., have the commit boundary encompass multiple messages, not just one. This applies to both producers and consumers and to clients that are both.</div></div><p>When using transactions a batch of 1000 messages, say, can be sent in a single atomic step. The message transmission is asynchronous and therefore very fast. The producer need only perform one commit every batch in order to minimize the latency that would otherwise be incurred with disk syncing.</p></div>
+<div class="wiki-content maincontent"><p>There are four main approaches as to a client can consume messages. They are:</p><ol><li>Auto-acknowledgement</li><li>Explicit acknowledgement via <strong><code>Message.acknowledge()</code></strong></li><li>JMS Transactions</li><li>XA</li></ol><p>For a discussion on XA see: <link><page ri:content-title="Should I use XA"></page></link></p><p>The main difference between 1 & 2 and 3 & 4 is the latter allow messages to be rolled back and redelivered if an error occurs whilst processing. There is no JMS 'unacknowledge'. So for this reason JMS transactions should be preferred to message acknowledgements in most use cases.</p><p>It's a common misconception that transactions are inherently slow. In reality there's little difference in performance, from the broker's perspective, between the use of a JMS transaction and invoking <strong><code>Message.acknowledge()</code></strong>. However, a performance penalty is incurred when the delivery mode is set to  persistent. This causes the broker to block until the commit is synchronized to disk. This is similar to how <strong><code>Message.acknowledge()</code></strong> blocks when using a non-transactional JMS session.</p><structured-macro ac:macro-id="99e15250-081e-40c1-8520-add30849917e" ac:name="note" ac:schema-version="1"><rich-text-body>Transaction support is also available for non-persistent delivery mode.</rich-text-body></structured-macro><structured-macro ac:macro-id="ac5e07ae-6a38-465c-bf38-5641bb66d218" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Batched Transactions Are The Fastest Way To Process Messages!</parameter><rich-text-body>It's worth noting that the fastest way to consume persistent messages is to use a JMS transaction combined with message batching, e.g., have the commit boundary encompass multiple messages, not just one. This applies to both producers and consumers and to clients that are both.</rich-text-body></structured-macro><p>When using transactions a batch of 1000 messages, say, can be sent in a single atomic step. The message transmission is asynchronous and therefore very fast. The producer need only perform one commit every batch in order to minimize the latency that would otherwise be incurred with disk syncing.</p></div>
diff --git a/should-i-use-xa.xml b/should-i-use-xa.xml
index d87c24e..8bc45d2 100644
--- a/should-i-use-xa.xml
+++ b/should-i-use-xa.xml
@@ -1,23 +1,22 @@
-<div class="wiki-content maincontent"><h2 id="ShouldIuseXA-ShouldIuseXAtransactions(twophasecommit?)">Should I use XA transactions (two phase commit?)</h2>
+<div class="wiki-content maincontent"><h2>Should I use XA transactions (two phase commit?)</h2>
<p>A common use of JMS is to consume messages from a queue or topic, process them using a database or EJB, then acknowledge / commit the message.</p>
<p>If you are using more than one resource; e.g. reading a JMS message and writing to a database, you really should use XA - its purpose is to provide atomic transactions for multiple transactional resources. For example there is a small window from when you complete updating the database and your changes are committed up to the point at which you commit/acknowledge the message; if there is a network/hardware/process failure inside that window, the message will be redelivered and you may end up processing duplicates.</p>
-<p>The problem with XA is it can be a bit slow; as the XA protocol requires multiple syncs to disk to ensure it can always recover properly under every possible failure scenario. This adds significant cost (in terms of latency, performance, resources and complexity). Also quite a few EJB servers and databases don't actually properly support XA! <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>The problem with XA is it can be a bit slow; as the XA protocol requires multiple syncs to disk to ensure it can always recover properly under every possible failure scenario. This adds significant cost (in terms of latency, performance, resources and complexity). Also quite a few EJB servers and databases don't actually properly support XA! <emoticon ac:name="smile"></emoticon></p>
-<div class="confluence-information-macro confluence-information-macro-information"><p class="title">Be Careful</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>ActiveMQ does not currently support XA Transaction suspend / resume semantics. </p></div></div>
+<structured-macro ac:macro-id="ade54758-a256-48e9-a6f9-f66fa2e33e56" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Be Careful</parameter><rich-text-body>
+<p>ActiveMQ does not currently support XA Transaction suspend / resume semantics. </p></rich-text-body></structured-macro>
-<h3 id="ShouldIuseXA-AnalternativetoXA">An alternative to XA</h3>
+<h3>An alternative to XA</h3>
<p>So a good optimisation is to use regular JMS transactions - with no XA - and just perform some duplicate message detection in your code to check you have not already processed the message. </p>
-<p>For example you can use an <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/idempotent-consumer.html">Idempotent Consumer</a> from the <a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a> to solve this scenario.</p>
+<p>For example you can use an <a shape="rect" href="http://activemq.apache.org/camel/idempotent-consumer.html">Idempotent Consumer</a> from the <link><page ri:content-title="Enterprise Integration Patterns"></page></link> to solve this scenario.</p>
<p>Or in pseudocode you could use something like the following...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="6da27eb1-3c43-4c9f-9947-2e2289b73375" ac:name="code" ac:schema-version="1"><plain-text-body>
onMessage
try {
if I have not processed this message successfully before {
@@ -29,17 +28,16 @@
catch (Exception e) {
jms.rollback()
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This leads to <strong>much</strong> better performance since you are not performing many slow syncs to disk (per transaction!) for the XA protocol. The only downside with this approach is it means you have to use some application specific logic to detect if you've processed the message before or not. However its quite common that you'll have some way of detecting this. e.g. if the message contains a purchase order and version; have you stored that purchase order and version in the database yet?</p>
<p>So provided the message has some kind of ID and version, you can often detect duplicates yourself and so not require to pay the performance cost of XA</p>
-<p>It may also be worth reading <a shape="rect" href="should-i-use-transactions.xml">Should I use transactions</a>.</p>
+<p>It may also be worth reading <link><page ri:content-title="Should I use transactions"></page></link>.</p>
-<h3 id="ShouldIuseXA-Furtheroptimisation">Further optimisation</h3>
+<h3>Further optimisation</h3>
<p>Performing duplicate detection can add a performance overhead. e.g. doing a database query to see if you've processed the purchase order before etc. Most of the time things will work; its only in rare circumstances (ilke if a server crashes mid-way processing some messages) that messages get redelivered.</p>
-<p>So you can use the <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html#getJMSRedelivered()" rel="nofollow">Message.getJMSRedelivered()</a> method to detect if a message has been redelivered and only if its been redelivered then perform the duplicate detection check.</p></div>
+<p>So you can use the <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html#getJMSRedelivered()">Message.getJMSRedelivered()</a> method to detect if a message has been redelivered and only if its been redelivered then perform the duplicate detection check.</p></div>
diff --git a/site.xml b/site.xml
index 1441e9b..a0f4585 100644
--- a/site.xml
+++ b/site.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="banner.xml">Banner</a></li><li><a shape="rect" href="navigation.xml">Navigation</a></li><li><a shape="rect" href="quicklinks.xml">QuickLinks</a></li><li><a shape="rect" href="siteindex.xml">SiteIndex</a></li><li><a shape="rect" href="sitemap.xml">SiteMap</a></li></ul></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="77df46ae-dff4-4d4e-b437-cf9292d94677" ac:name="children" ac:schema-version="1"><parameter ac:name="">all</parameter></structured-macro></div>
diff --git a/siteindex.xml b/siteindex.xml
index a0a16a1..8d7b40c 100644
--- a/siteindex.xml
+++ b/siteindex.xml
@@ -1,1840 +1,3 @@
<div class="wiki-content maincontent">
-<h2>Space Index</h2>
-
-<p>
-<table class="grid" width="99%" cellspacing="0"><tr><td colspan="2" rowspan="1">
- <table width="100%"><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-0-9">0-9</a> ... 4</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-A">A</a> ... 130</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-B">B</a> ... 15</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-C">C</a> ... 39</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-D">D</a> ... 23</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-E">E</a> ... 7</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-F">F</a> ... 5</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-G">G</a> ... 4</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-H">H</a> ... 102</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-I">I</a> ... 19</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-J">J</a> ... 32</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-K">K</a> ... 4</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-L">L</a> ... 8</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-M">M</a> ... 21</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-N">N</a> ... 21</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-O">O</a> ... 12</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-P">P</a> ... 16</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Q">Q</a> ... 2</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-R">R</a> ... 16</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-S">S</a> ... 40</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-T">T</a> ... 18</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-U">U</a> ... 13</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-V">V</a> ... 16</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-W">W</a> ... 26</td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="#index-X">X</a> ... 5</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Y">Y</a> ... 0</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-Z">Z</a> ... 3</td><td colspan="1" rowspan="1"><a shape="rect" href="#index-%21@%23%24">!@#$</a> ... 0</td><td colspan="1" rowspan="1"> </td><td colspan="1" rowspan="1"> </td></tr></table>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-0-9"></a>0-9</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/2007+April">2007 April</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">April 2007 Report ActiveMQ 4.1.1 Released voted in a new committer, John Heitmann the developer and user lists continue to be very active</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/4.0+RC+1+Guide">4.0 RC 1 Guide</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ 4.0-RC-1 Release Guide Release Info Release Manager Hiram Chirino Special issues We are still in the Incubator so need to ensure that all the proper disclaimers are in place and that the artifacts are all properly named incubator-activemq. Open I</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/5.8+Migration+Guide">5.8 Migration Guide</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are some changes in 5.8 that may require some code change New modules may effect your maven pom dependencies activemq-core has been replaced with activemq-client and activemq-broker. The various message stores have their own activemq-xx-store module</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/5.9+Migration+Guide">5.9 Migration Guide</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are some changes in 5.9 that may require user intervention Schema change to JDBC Persistence Adapter. XID column type change. If you use XA transactions you need to ensure there are no XA transactions pending completion before you upgrade. Some mode</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-A"></a>A</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Activation+Spec+Properties">Activation Spec Properties</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">An Activation Spec is used to configure the message delivery to an MDB. The ejb-jar.xml deployment descriptor needs to include a <activation-config> element inside the <message-driven> element like: <activation-config> <activation-config-property> <activa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Active+Groups">Active Groups</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Active Groups is a dynamic collaboration framework so simplify message passing and shared state between members of the group. It is available in ActiveMQ 6.0 Active Groups includes the following: Dynamic membership information broadcast messaging point-to</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+1.1+Release">ActiveMQ 1.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release represents a major increase in functionality; the new features in this release are:- distributed queues and topics and clusters of message brokers auto-reconnection of clients across a cluster of brokers support for high pe</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+1.2+Release">ActiveMQ 1.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release represents a major increase in functionality; the new features in this release are:- heaps of bug fixes and new test cases Download Here Download Description activemq-release-1.2.zip http://dist.codehaus.org/activemq/distri</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+1.3+Release">ActiveMQ 1.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release represents a major increase in functionality; the new features in this release are:- heaps of bug fixes and new test cases Download Here Download Description activemq-release-1.3.zip http://dist.codehaus.org/activemq/distri</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+1.4+Release">ActiveMQ 1.4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release represents a major increase in functionality; the new features in this release are:- heaps of bug fixes and new test cases Download Here Download Description activemq-release-1.4.zip http://dist.codehaus.org/activemq/distri</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+1.5+Release">ActiveMQ 1.5 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release is mostly a bug fix release:- A few bug fixes for J2EE compliance Download Here Download Description activemq-release-1.5.zip http://dist.codehaus.org/activemq/distributions/activemq-release-1.5.zip Binary Distribution in z</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+2.0+Release">ActiveMQ 2.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a major release including lots of new functionality and performance improvements: This release includes advisory messages so you can listen to the state of the message fabric optimised wire format for higher throughput improved </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+2.1+Release">ActiveMQ 2.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release includes full support for the high performance journal. Our default persistence mechanism is now the journal for short term persistence and then JDBC (via Apache Derby by default) for long term storage. The journal is regul</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+3.0+Release">ActiveMQ 3.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This new release includes the following a new 'discovery' transport protocol for a pure client-only peer network - a self discovering cluster which automatically finds the brokers available on the network (as opposed to the 'peer' proto</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+3.1+Release">ActiveMQ 3.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This new release includes the following New Stomp http://stomp.codehaus.org/ support to make it easy to create cross language clients such as for Ruby or Perl etc. (Python, C and .Net coming soon) XPath based selectors and demand based </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+3.2+Release">ActiveMQ 3.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This new release includes the following Improved Stomp http://stomp.codehaus.org/ 1.0 support to make it easy to create cross language clients such as for C, C#, Python, Ruby, Perl and Pike. Ajax support now uses OpenRico as the default</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+3.2.1+Release">ActiveMQ 3.2.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release is a bug fix release and users of previous versions of 3.2 are encouraged to upgrade to this version. Download Here Download Description activemq-3.2.1.zip http://dist.codehaus.org/activemq/distributions/activemq-3.2.1.zip </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+3.2.2+Release">ActiveMQ 3.2.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This release is a bug fix release and users of previous versions of 3.2 are encouraged to upgrade to this version. Download Here Download Description activemq-3.2.2.zip http://dist.codehaus.org/activemq/distributions/activemq-3.2.2.zip </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+4.0+M4+Release">ActiveMQ 4.0 M4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is the first milestone release of 4.x since the move to Apache so the package names have changed from org.activemq to org.apache.activemq. For a full list see the Changes in 4.0. This release of ActiveMQ includes a large number of </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+4.0+RC2+Release">ActiveMQ 4.0 RC2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is the second release candiate release of 4.0. This release of ActiveMQ includes a large number of new features such as MasterSlave and Message Groups together with numerous bug fixes. Warnings When upgrading from a previous releas</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+4.0+Release">ActiveMQ 4.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is the 4.0 release of Apache ActiveMQ. This release of Apache ActiveMQ includes a large number of new features such as MasterSlave and Message Groups together with numerous bug fixes. Warnings When upgrading from a previous release</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+4.0.1+Release">ActiveMQ 4.0.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"><!-- {warning:title=The Release is still in progress} You are previewing the release page for unreleased version of ActiveMQ. The download links on the page below will not work until it is offically released. Until the release is approved you could try th</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+4.0.2+Release">ActiveMQ 4.0.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New and Noteworthy This is a minor bug fix release. All previous installations of Apache ActiveMQ 4.0.1 are recommended to upgrade to this release. Download Here Description Download Link PGP Signature file of download Binary for Windows incubator-activem</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+4.1.0+Release">ActiveMQ 4.1.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png New and Noteworthy This is release contains several major enhancements such as: Virtual Destinations JDBC based Master/Slave locking XMPP/Jabber Support - ActiveMQ can no</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+4.1.1+Release">ActiveMQ 4.1.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png New and Noteworthy Contains slew of bug fixes that are tracked in the change log. Getting the Binary Distributions Description Download Link PGP Signature file of downloa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+4.1.2+Release">ActiveMQ 4.1.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-410-release.data/activemq-4.1-box-reflection.png New and Noteworthy Contains slew of bug fixes that are tracked in the change log. Getting the Binary Distributions Description Download Link PGP Signature file of downloa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.0.0+Release">ActiveMQ 5.0.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">activemq-5.x-box-reflection.png New Features in 5.0 Getting the Binary Distributions Description Download Link PGP Signature file of download Windows Distribution apache-activemq-5.0.0.zip http://archive.apache.org/dist/activemq/apache-activemq/5.0.0/apac</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.1.0+Release">ActiveMQ 5.1.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png New Features in 5.1 Getting the Binary Distributions Description Download Link PGP Signature file of download Windows Distribution apache-activemq-5.1.0-bin.zip http://ar</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.10.0+Release">ActiveMQ 5.10.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.10.0 Release Apache ActiveMQ 5.10.0 resolves more than 234 issues https://issues.apache.org/jira/browse/AMQ-5061?jql=project%20%3D%20AMQ%20AND%20fixVersion%2</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.10.1+Release">ActiveMQ 5.10.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.10.1 Release Apache ActiveMQ 5.10.1 resolves 33 issues https://issues.apache.org/jira/browse/AMQ-5514?jql=fixVersion%20%3D%205.10.1%20AND%20project%20%3D%20A</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.10.2+Release">ActiveMQ 5.10.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.10.2 Release Apache ActiveMQ 5.10.2 resolves 2 issues https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.2, both </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.11.0+Release">ActiveMQ 5.11.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ 5.11.0 Release Apache ActiveMQ 5.11.0 resolves more than 130 issues https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%205.11.0%20AND%20project%20%3D%20AMQ, mostly bug fixes and improvements. It is build with and requires jdk 1.7 New Fea</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.11.1+Release">ActiveMQ 5.11.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.11.1 Release Apache ActiveMQ 5.11.1 resolves 6 issues https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.11.1, mostl</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.11.2+Release">ActiveMQ 5.11.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.11.2 Release Apache ActiveMQ 5.11.2 resolves several issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329669, mostl</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.11.3+Release">ActiveMQ 5.11.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.11.3 Release Apache ActiveMQ 5.11.3 resolves several issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329669, mostl</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.12.0+Release">ActiveMQ 5.12.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.12.0 Release Apache ActiveMQ 5.12.0 resolves several issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12329258, and p</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.12.1+Release">ActiveMQ 5.12.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.12.1 Release Apache ActiveMQ 5.12.1 includes several improvements and resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123112</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.12.2+Release">ActiveMQ 5.12.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.12.2 Release Apache ActiveMQ 5.12.2 includes several improvements and resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123112</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.13.0+Release">ActiveMQ 5.13.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.13.0 Release Apache ActiveMQ 5.13.0 includes several resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123298</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.13.1+Release">ActiveMQ 5.13.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.13.1 Release Apache ActiveMQ 5.13.1 includes over 40 resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123342</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.13.2+Release">ActiveMQ 5.13.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.13.2 Release Apache ActiveMQ 5.13.2 includes over 15 resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123347</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.13.3+Release">ActiveMQ 5.13.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.13.3 Release Apache ActiveMQ 5.13.3 includes over 25 resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123350</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.13.4+Release">ActiveMQ 5.13.4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.13.4 Release Apache ActiveMQ 5.13.4 includes 30 resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12335661&projectId=12311210 an</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.14.0+Release">ActiveMQ 5.14.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.14.0 Release Apache ActiveMQ 5.14.0 includes many resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12334188,</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.14.1+Release">ActiveMQ 5.14.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.14.1 Release Apache ActiveMQ 5.14.1 includes many resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338124 </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.14.2+Release">ActiveMQ 5.14.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.14.2 Release Apache ActiveMQ 5.14.2 includes many resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12338329 </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.14.3+Release">ActiveMQ 5.14.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.14.3 Release Apache ActiveMQ 5.14.3 includes several resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123388</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.14.4+Release">ActiveMQ 5.14.4 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.14.4 Release Apache ActiveMQ 5.14.4 includes several resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123389</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.14.5+Release">ActiveMQ 5.14.5 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.14.5 Release Apache ActiveMQ 5.14.5 includes several resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123389</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.15.0+Release">ActiveMQ 5.15.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.15.0 Release Apache ActiveMQ 5.15.0 includes several resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123380</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.15.1+Release">ActiveMQ 5.15.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.15.1 Release Apache ActiveMQ 5.15.1 includes several resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123410</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.15.2+Release">ActiveMQ 5.15.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png ActiveMQ 5.15.2 Release Apache ActiveMQ 5.15.2 includes several resolved issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=123416</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.2.0+Release">ActiveMQ 5.2.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png New Features in 5.2 Getting the Binary Distributions Description Download Link PGP Signature file of download Windows Distribution apache-activemq-5.2.0-bin.zip http://ar</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.3.0+Release">ActiveMQ 5.3.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png New Features in 5.3 Getting the Binary Distributions Description Download Link PGP Signature file of download Windows Distribution apache-activemq-5.3.0-bin.zip http://ar</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.3.1+Release">ActiveMQ 5.3.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.3 is primarily a maintenance release which resolves https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.3.2+Release">ActiveMQ 5.3.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.3.2 is primarily a maintenance release which resolves https://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&&pid=10520&fixfor=12310&s</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.4.0+Release">ActiveMQ 5.4.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png This release has been retracted due to bug AMQ-3491 https://issues.apache.org/jira/browse/AMQ-3491. It is no longer downloadable from ASF servers. Please use the ActiveMQ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.4.1+Release">ActiveMQ 5.4.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png This release has been retracted due to bug AMQ-3491 https://issues.apache.org/jira/browse/AMQ-3491. It is no longer downloadable from ASF servers. Please use the ActiveMQ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.4.2+Release">ActiveMQ 5.4.2 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png This release has been retracted due to bug AMQ-3491 https://issues.apache.org/jira/browse/AMQ-3491. It is no longer downloadable from ASF servers. Please use the ActiveMQ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.4.3+Release">ActiveMQ 5.4.3 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.4.3 is a maintenance release which resolves AMQ-3491 https://issues.apache.org/jira/browse/AMQ-3491, a critical bug which caused the 5.4.0, 5.4.1, and 5</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.5.0+Release">ActiveMQ 5.5.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png This release has been retracted due to bug AMQ-3491 https://issues.apache.org/jira/browse/AMQ-3491. It is no longer downloadable from ASF servers. Please use the ActiveMQ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.5.1+Release">ActiveMQ 5.5.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.5.1 is a maintenance release which resolves AMQ-3491 https://issues.apache.org/jira/browse/AMQ-3491, a critical bug which caused the 5.5.0 release to be</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.6.0+Release">ActiveMQ 5.6.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.6.0 is primarily a maintenance release which resolves over 435 issues https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=proj</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.7.0+Release">ActiveMQ 5.7.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.7.0 is primarily a maintenance release which resolves nearly 200 issues https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.8.0+Release">ActiveMQ 5.8.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.8.0 resolves 160 issues https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.8.0%22+AND</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.9.0+Release">ActiveMQ 5.9.0 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.9.0 resolves more than 200 issues https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+5.9.1+Release">ActiveMQ 5.9.1 Release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">http://activemq.apache.org/activemq-500-release.data/activemq-5.x-box-reflection.png Apache ActiveMQ 5.9.1 resolves more than 120 issues https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+AMQ+AND+fixVersion+%3D+%225.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+Artemis+Roadmap">ActiveMQ Artemis Roadmap</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The goal of this page is to identify the outstanding issues that must be addressed by Artemis in order to achieve some level of feature parity with ActiveMQ 5.x. The overall objective for working toward feature parity between ActiveMQ 5.x and Artemis is f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+C+++Development">ActiveMQ C Development</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ CPP Development Page This page documents current and planned development of ActiveMQ CPP. The table below lists development tasks and their current status Development Activeity Status Openwire Support in-progress Openwire Support This task adds</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="activemq-c-clients.xml">ActiveMQ C++ Clients</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ C++ Integration CMS http://activemq.apache.org/cms/ is an easy-to-use JMS 1.1-like API. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+Command+Line+Tools+Reference">ActiveMQ Command Line Tools Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Command Line Tools The current script contains the entire functionality to manage activemq. ActiveMQ Command Line Tools Reference - runs an activemq broker (see Unix Shell Script) In versions prior 5.4.1 some management functionalities beyond controlling </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+Connection+URIs">ActiveMQ Connection URIs</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring Transports</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+InactivityMonitor">ActiveMQ InactivityMonitor</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ InactivityMonitor The ActiveMQ InactivityMonitor is an active thread that checks the connection is still active and if it suspects the connection is not functioning correctly, it closes the connection. Connections are monitored by: Ensuring data </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+Message+Properties">ActiveMQ Message Properties</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ Messages support the following default message properties: Message Attributes Accessed as Properties: Property Name Type Default Value Description JMSDestination javax.jms.Destination Set by the producer Destination used by the producer. JMSReply</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+Performance+Module+Users+Manual">ActiveMQ Performance Module Users Manual</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Running Maven 2 Performance Test This Maven 2 http://maven.apache.org plugin allows you to run performance tests easily using the Maven command line or run tests automatically in Continuum http://maven.apache.org/continuum/ Prerequisites Starting with Act</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ActiveMQ+Real+Time">ActiveMQ Real Time</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ Real Time is a sub-project of the popular Apache ActiveMQ messaging system but is designed specifically to meet the needs for low latency high throughput collaborative real-time applications. It is designed to be used by multiple languages on mul</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Advisory+Message">Advisory Message</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ supports advisory messages which allows you to watch the system using regular JMS messages. Currently we have advisory messages that support: consumers, producers and connections starting and stopping temporary destinations being created and dest</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Ajax">Ajax</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Introduction ActiveMQ supports Ajax http://en.wikipedia.org/wiki/Ajax_%28programming%29 which is an Asychronous Javascript And Xml mechanism for real time web applications. This means you can create highly real time web applications taking full advantage </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/All+Forums">All Forums</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"><a id="nabblelink" href="http://www.nabble.com/ActiveMQ-f2354.html">ActiveMQ</a> <script src="http://www.nabble.com/embed/f2354"></script></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQ+Message+Store">AMQ Message Store</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Basics This is the default storage for AcitveMQ 5 and above. The AMQ Message Store is an embeddable transactional message storage solution that is extremely fast and reliable. message commands are written to a transactional journal - which consists of</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/AMQP">AMQP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ supports the AMQP 1.0 https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp protocol which is an OASIS standard. Available from ActiveMQ version 5.8 onward. Enabling the ActiveMQ Broker for AMQP To enable AMQP protocol support on the b</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200708-august.xml">Apache ActiveMQ Board Report - 2007.08 (August)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project July board report was missed in part due to a change in PMC chair. Community: * The developer and user communities remain very active. * New committer added: Albert Strasheim Development: The CMS API has been </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200710-october.xml">Apache ActiveMQ Board Report - 2007.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project Community: * The developer and user communities remain very active. * The Camel project, NMS project, and recent release candidate for ActiveMQ 5.0 have generated much mailing list activity. * A code grant has</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200801-january.xml">Apache ActiveMQ Board Report - 2008.01 (January)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project Community: * Nicky Sandhu and Hadrian Zbarcea were voted in and accepted becoming ActiveMQ committers * A code grant was accepted for an NMS implementation that access Tibco EMS. * The development and user lis</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200807-july.xml">Apache ActiveMQ Board Report - 2008.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project Community: * The ActiveMQ project has had another very busy quarter. Seven new contributors were voted in and accepted becoming ActiveMQ committers: * Gary Tully * Gert Vanthienen * Dejan Bosanac * Claus Ibsen</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200810-october.xml">Apache ActiveMQ Board Report - 2008.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project Community: * The ActiveMQ project has had another very busy quarter. Jonathan Anstey was voted in as an ActiveMQ committer. * The development and user lists continue to stay vibrant. Development: * Lots of dev</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200901-january.xml">Apache ActiveMQ Board Report - 2009.01 (January)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project Community: * The ActiveMQ project has had another very busy quarter. William Tam has been added as an ActiveMQ committer. * The development and user lists continue to stay vibrant. * The Camel sub project has </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200904-april.xml">Apache ActiveMQ Board Report - 2009.04 (April)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project Community: * The ActiveMQ project has had another very busy but quiet quarter. * The development and user lists continue to stay vibrant. * The Camel sub project has completed moving to a TLP. Development: * A</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200907-july.xml">Apache ActiveMQ Board Report - 2009.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: * The ActiveMQ project has had another very busy but quiet quarter. * The development and user lists continue to stay vibrant. * New PMC members: Dejan Bosanac * New Committers: Colin MacNaughton, Bruce Snyder Development: * The first release o</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-200910-october.xml">Apache ActiveMQ Board Report - 2009.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: * The ActiveMQ project has had another very busy but quiet quarter. * The development and user lists continue to stay vibrant. Development: * It was a busy an fruitful quarter which produced several new releases. Releases: * Apache.NMS 1.1.0 * </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201001-january.xml">Apache ActiveMQ Board Report - 2010.01 (January)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: * The ActiveMQ project has had another very busy but quiet quarter. * The development and user lists continue to stay vibrant. * Tim Bish has joined the ActiveMQ PMC Development: * The Apache.NMS.Stomp project has begun development of its first</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201005-may.xml">Apache ActiveMQ Board Report - 2010.05 (May)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project Apologies for missing the April board report deadline. Community: * The ActiveMQ project has had another very busy but quiet quarter. * The development and user lists continue to stay vibrant. Development: * W</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201007-july.xml">Apache ActiveMQ Board Report - 2010.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: The development and user lists continue to stay active and vibrant. No new committers or PMC members added Development: Working towards an ActiveMQ 5.4 release. Prototype broker core for ActiveMQ 6.x is showing promise Releases: ActiveMQ-CPP 3.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201010-october.xml">Apache ActiveMQ Board Report - 2010.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: The development and user lists continue to stay active and vibrant. No new committers or PMC members added Development: Development has started on the next ActiveMQ 5.5 release. Prototype broker core slated for ActiveMQ 6.x is still under devel</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201101-january.xml">Apache ActiveMQ Board Report - 2011.01 (January)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: The development and user lists continue to stay active. No new committers or PMC members added. Development: Development has started on the next ActiveMQ 5.5 release. Prototype broker core slated for ActiveMQ 6.x is still under development. Apa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201104-april.xml">Apache ActiveMQ Board Report - 2011.04 (April)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: The development and user lists continue to stay active. Alex Dean (alexd) added as a committer to the project Development: Development has started on the next ActiveMQ 5.6 release. Development continues on the ActiveMQ Apollo 1.0 release. Devel</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201107-july.xml">Apache ActiveMQ Board Report - 2011.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: The development and user lists continue to stay active. No new committers or PMC members added. Development: Development has started on the next ActiveMQ 5.6 release. Apollo 1.0 is approaching completion. Several betas have been released and it</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201110-october.xml">Apache ActiveMQ Board Report - 2011.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Community: The development and user lists continue to stay active. No new committers or PMC members added. Development: A LGPL licensed artifact was discovered to be in a Apache Camel dependency which was included in the ActiveMQ 5.4.0, 5.4.1, 5.4.2 and 5</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201201-january.xml">Apache ActiveMQ Board Report - 2012.01 (January)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201204-april.xml">Apache ActiveMQ Board Report - 2012.04 (April)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201207-july.xml">Apache ActiveMQ Board Report - 2012.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201210-october.xml">Apache ActiveMQ Board Report - 2012.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201301-january.xml">Apache ActiveMQ Board Report - 2013.01 (January)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201304-april.xml">Apache ActiveMQ Board Report - 2013.04 (April)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201307-july.xml">Apache ActiveMQ Board Report - 2013.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201310-october.xml">Apache ActiveMQ Board Report - 2013.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201401-january.xml">Apache ActiveMQ Board Report - 2014.01 (January)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201404-april.xml">Apache ActiveMQ Board Report - 2014.04 (April)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201407-july.xml">Apache ActiveMQ Board Report - 2014.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201410-october.xml">Apache ActiveMQ Board Report - 2014.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201502-february.xml">Apache ActiveMQ Board Report - 2015.02 (February)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201504-april.xml">Apache ActiveMQ Board Report - 2015.04 (April)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201506-june.xml">Apache ActiveMQ Board Report - 2015.06 (June)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The May ASF board meeting already took place this week, so we will need to publish this report in time for next month's meeting. TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports ma</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201507-july.xml">Apache ActiveMQ Board Report - 2015.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201508-august.xml">Apache ActiveMQ Board Report - 2015.08 (August)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201510-october.xml">Apache ActiveMQ Board Report - 2015.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TLP Description: Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201602-february.xml">Apache ActiveMQ Board Report - 2016.02 (February)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201604-april.xml">Apache ActiveMQ Board Report - 2016.04 (April)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201605-may.xml">Apache ActiveMQ Board Report - 2016.05 (May)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully supporting J</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201607-july.xml">Apache ActiveMQ Board Report - 2016.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Apache ActiveMQ is a popular and powerful open source messaging server. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features while fully </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201610-october.xml">Apache ActiveMQ Board Report - 2016.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features w</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201701-january.xml">Apache ActiveMQ Board Report - 2017.01 (January)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features w</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201704-april.xml">Apache ActiveMQ Board Report - 2017.04 (April)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features w</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201707-july.xml">Apache ActiveMQ Board Report - 2017.07 (July)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features w</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="apache-activemq-board-report-201710-october.xml">Apache ActiveMQ Board Report - 2017.10 (October)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Description Apache ActiveMQ is a popular and powerful open source message-oriented middleware. Apache ActiveMQ is fast, supports many cross language clients and protocols, comes with easy to use enterprise integration patterns and many advanced features w</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Apache+ActiveMQ+Board+Report+-+April+2008">Apache ActiveMQ Board Report - April 2008</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Status report for the Apache ActiveMQ Project Community: The ActiveMQ community continues to stay vibrant with a very healthy amount of email traffic flowing through it's email lists. It has also added several new committers to it's ranks. New Committers:</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Apache+ActiveMQ+Board+Reports">Apache ActiveMQ Board Reports</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The current ActiveMQ reporting schedule is: January, April, July, October</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Are+destinations+case+sensitive">Are destinations case sensitive</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There seems to be no consensus on whether JMS providers should use case insensitive destination names. Since most names in Java & J2EE are case sensitive (class names, JNDi names, file names (on many unix operating systems), URIs and URLs - we've followed</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Are+messages+read+directly+from+the+journal">Are messages read directly from the journal</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Kind of. A message can be loaded directly from the journal if it was swapped out of memory. The journal cannot be used, however, to recover a durable subscription as it does not keep an ordered index of messages per durable sub. So when a durable sub is a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Articles">Articles</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page captures resources and articles outside the ActiveMQ project which may assist your development. Please add any new resources that you come across by clicking the edit link at the bottom of the page. If you do this, please make sure to attach a d</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Async+Sends">Async Sends</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background ActiveMQ supports sending messages to a broker in sync or async mode. The mode used has a huge impact in the latency of the send call. Since latency is typically a huge factor in the throughput that can achieved by producer, using async sends c</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Audit+Logging">Audit Logging</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For many secured environments there's a requirement to log every user management action. For that ActiveMQ implements audit logging, which means that every management action made through JMX or Web Console management interface will be logged and available</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/AUTO">AUTO</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Starting with version 5.13.0, ActiveMQ supports wire format protocol detection. OpenWire, STOMP, AMQP, and MQTT can be automatically detected. This allows one transport to be shared for all 4 types of clients. Enabling AUTO over TCP To configure Active</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Axis+and+CXF+Support">Axis and CXF Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ supports both Apache Axis http://ws.apache.org/axis/ and Apache CXF http://incubator.apache.org/cxf out of the box. Support for Axis is deprecated, and will be removed from ActiveMQ 5.8 onwards. Just add the required jars to your classpath and yo</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-B"></a>B</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Banner">Banner</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"><div id="asf_logo"> <div id="activemq_logo"> <a style="float:left; width:280px;display:block;text-indent:-5000px;text-decoration:none;line-height:60px; margin-top:10px; margin-left:100px;" href="http://activemq.apache.org" title="The most popular and powe</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Becoming+a+committer">Becoming a committer</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page details how to become a committer. How to become a committer First of all you need to get involved and Contribute via the mail list, forums, edit the documention, work on the issue tracker and submit patches. Once you're contributing and your wo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Benchmark+Tests">Benchmark Tests</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ Maven Performance test plugin. Starting with ActiveMQ 5.5 and above the plugin can be obtained from maven or if you download the src from SVN you can build it yourself. To run the following Maven goals make sure you are inside a Maven2 project di</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/BlazeDS">BlazeDS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">BlazeDS You may also want to check out the Simplified BlazeDS and JMS article http://mmartinsoftware.blogspot.com/2008/05/simplified-blazeds-and-jms.html by Michael Martin http://mmartinsoftware.blogspot.com/. Using the dynamicQueues feature of the JNDI S</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Blob+Messages">Blob Messages</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Blob Messages A common requirement these days is to send around massive files for processing by consumers. Folks want to take advantage of the message broker's features such as reliable, transactional load balancing of queues with smart routing but still </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Board+Reports">Board Reports</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Board Reports The following are the Apache Software Foundation Board Reports.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Books">Books</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Books This page lists the known books about Apache ActiveMQ. If you happen to know a book which is not listed then please contact us, for example using the Mailing Lists. ActiveMQ in Action http://bit.ly/2je6cQ Instant Apache ActiveMQ Messaging Applicatio</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Broadcasting">Broadcasting</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveBlaze provides infrastructure for fast, reliable peer to peer messaging to meet the demands of high performance and collaborative applications. Using the basic building block of a Channel, there exists a functional hierarchy used for different probl</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Broker+Camel+Component">Broker Camel Component</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Broker Camel Component Available as of ActiveMQ 5.9 Embedding Apache Camel inside the ActiveMQ broker provides great flexibility for extending the message broker with the integration power of Camel. Apache Camel routes also benefit in that you can avoid t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Broker+Configuration+URI">Broker Configuration URI</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview An ActiveMQ broker can be extensivly configured using a single configuration URI. The following URI schemes are supported Scheme Link Description xbean: Broker XBean URI Configures the broker using an Xml Configuration from an XML file which is o</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Broker+Properties+URI">Broker Properties URI</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Broker Properties URI From version 4.2 of ActiveMQ onwards the Broker Properties URI allows you to run a configured broker by referencing a properties file which could be on the classpath, a local file or a remote URL. Syntax properties:name Where name is</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Broker+URI">Broker URI</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Broker URI The Broker URI allows you to run a configured broker using a single URI for all the configuration. Syntax The URI is assumed to be a composite uri with multiple uris that are used to bind the connectors of the broker. broker:(transportURI,netwo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Broker+XBean+URI">Broker XBean URI</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Broker XBean URI The Broker XBean URI allows you to run a configured broker by referencing an Xml Configuration on the classpath. The URI points to an XML document which can be parsed via XBean or Spring. This URI is typically on the classpath; though in </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Building">Building</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Building ActiveMQ from Source ActiveMQ uses Maven http://maven.apache.org/ as its build and management tool. If you don't fancy using Maven you can use your IDE directly or Download a distribution or JAR. Prequisites Required: Download and install Maven h</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Building+ActiveMQ+CPP">Building ActiveMQ CPP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Dependencies libuuid The build requires the libuuid library that is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net/ http://e2fsprogs.sourceforge.net/ which is not always installed by default. cppunit The package conta</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-C"></a>C</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/C+Integration">C Integration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">It is very common for an organisation to have lots of legacy C code which needs integration into the message bus. The current available solutions are CMS is an easy-to-use JMS 1.1-like API for C++. Our implementation of CMS is called ActiveMQ-CPP, the arc</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/C+integration+scenarios">C integration scenarios</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">One way and RPC with C services Its common for the C services to be the back end services. The 2 common use cases are we send a message one-way to a C service we send a message to a C-service and wait for the result, then reply back to the originator the </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Cached+LDAP+Authorization+Module">Cached LDAP Authorization Module</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Available since 5.6 Cached LDAP authorization module is an implementation of an default authorization module that initializes and updates data from LDAP. It supports all standard features like defining wildcard policy entries and entry for temporary desti</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Can+I+get+commercial+support">Can I get commercial support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Can I get commercial support? Absolutely, see our Support page for more details</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Can+I+modify+messages+on+a+queue">Can I modify messages on a queue</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Can I modify messages on a queue? The short answer is no. In JMS messages are immutable once they have been sent. If you find you need to modify messages its recommended that you create a consumer with some selector which matches the messages you wish to </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Can+I+send+and+receive+messages+concurrently+on+one+JMS+Connection">Can I send and receive messages concurrently on one JMS Connection</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Absolutely! Strictly speaking each producer being used concurrently should be using a separate session (though in ActiveMQ it'll probably work fine if you just use one session for all publishers). For concurrent consumption create a session per consumer -</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Can+I+send+really+large+files+over+ActiveMQ">Can I send really large files over ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Can I send really large files over ActiveMQ The answer is yes. If you are using ActiveMQ 4.2 or later we highly recommend you use Blob Messages which implements an out of band transport of the messages; it allows the files to be hosted on external http/ft</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Can+I+use+ActiveMQ+5.x+or+later+on+Java+1.4">Can I use ActiveMQ 5.x or later on Java 1.4</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Can I use ActiveMQ 5.0 or later on Java 1.4? Apache ActiveMQ 5.x or later is developed to run on Java 5 or later to take advantage of the new language features together with the major fact that on Java 5 the new concurrency code is faster & less buggy and</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Can+two+brokers+share+the+same+database">Can two brokers share the same database</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Can two brokers share the same database The short answer is no; 2 brokers cannot operate on the same sets of database tables concurrently. ActiveMQ is designed for high performance so we want to minimise the amount of pessimistic locking; each broker is d</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Can+you+browse+a+topic">Can you browse a topic</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You can browse queues, can you browse a topic? No. But then consuming messages on a topic does not affect any other consumers, so you don't need to 'browse' per se, just subscribe. i.e. browsing is necessary on queues as you wanna see what messages there </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/certificate_unknown">certificate_unknown</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you get an error something like this... javax.jms.JMSException: start failed: Received fatal alert: certificate_unknown at org.activemq.transport.tcp.TcpTransportChannel.start(TcpTransportChannel.java:200) at org.activemq.broker.impl.BrokerConnectorImp</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Changes+in+4.0">Changes in 4.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in 4.0 MasterSlave provides support for continuous availability and fault tolerance of brokers to be able to handle catastrophic hardware failure and not loose a message (or get duplicates). A new Exclusive Consumer feature allows you to pin </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Class+Diagrams+for+activemq-4.0-M4+source+code">Class Diagrams for activemq-4.0-M4 source code</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Class Diagrams for activemq-4.0-M4 source code. These diagrams cover the bulk of the source code and are in EMF format. http://docs.codehaus.org/download/attachments/50288/Class+Diagrams+activemq-4.0-M4.zip http://docs.codehaus.org/download/attachments/5</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Clustering">Clustering</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Clustering is a large topic and often means different things to different people. We'll try to list the various aspects of clustering and how they relate to ActiveMQ Queue consumer clusters ActiveMQ supports reliable high performance load balancing of mes</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Code+Overview">Code Overview</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Architecture The following section walks through the main parts of Apache ActiveMQ and links to the code to help you understand the layout http://activemq.apache.org/images/BrokerDiagram.png JMS Client The org.apache.activemq http://incubator.apache.org/a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Command+Agent">Command Agent</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">https://issues.apache.org/jira/browse/AMQ-4406 https://issues.apache.org/jira/browse/AMQ-4406 Command Agent From 4.2 onwards Apache ActiveMQ allows you to communicate with a broker Command Agent to be able to perform administration queries and commands. T</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Community">Community</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"> </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Compile+ActiveMQ+with+GCJ">Compile ActiveMQ with GCJ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You can use GCJ http://gcc.gnu.org/java/ to build ActiveMQ as a shared library you can reuse from C++. Native compile ActiveMQ HOWTO Abstract This document describes how to native compile ActiveMQ for use in a C++ environment. The version of ActiveMQ used</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="complex-single-broker-configuration-stomp-only.xml">Complex Single Broker Configuration (STOMP only)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Example of an ActiveMQ configuration with predefined queues, simple destination security (could easily update it to JAAS), complex Web Console security with Jetty JAAS, and JMX security too. While this is a fairly detailed configuration, it locks down eve</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Composite+Destinations">Composite Destinations</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">As of version 1.1, ActiveMQ supports a technology we call composite destinations. This allows a single virtual JMS Destination to be used to represent a collection of JMS Destinations. For example you can use composite destinations to send a message to 12</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configurable+IOException+Handling">Configurable IOException Handling</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Starting with 5.3.1, ActiveMQ provides configurable IOException handling for its file-based message stores. From version 5.5 the handler is also invoked when the JDBC persistence adapter gets a failure on getConnection(). Default IOException handler Activ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configuration">Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Questions on configuring ActiveMQ's JMS client or the Message Broker</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configure+Startup+Destinations">Configure Startup Destinations</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Typically in Apache ActiveMQ we create destinations on demand as clients start to use them. However sometimes users want to be able to configure which destinations are available on startup explicitly in the Xml Configuration. Note this feature is availabl</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configure+version+5+Brokers">Configure version 5 Brokers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview There is an updates XML syntax for configuring message brokers - see here http://activemq.apache.org/schema/core/activemq-core-5.0-SNAPSHOT.xsd So we decided that using XML would make this configuration much easier. we use XBean http://xbean.org/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configuring+ActiveMQ+CPP">Configuring ActiveMQ CPP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The configuration of ActiveMQ is so slick, we decided to take a similar approach with ActiveMQ-CPP. All configuration is achieved via URI-encoded parameters, either on the connection or destinations. Through the URIs, you can configure virtually every fac</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configuring+Brokers">Configuring Brokers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview In ActiveMQ 4, we are using a new xml format to configure the broker. Syntax The following xsd describes the syntax of the broker configuration file. activemq-4.0.xsd And here is the reference documentation for that xsd file. activemq-4.0.xsd.htm</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configuring+Transports">Configuring Transports</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Transport configuration options One of the first kinds of URI you are likely to use is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are the first transports you'll use. All of the following URI configurations are b</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configuring+Version+5+Transports">Configuring Version 5 Transports</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring Transports</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Configuring+Wire+Formats">Configuring Wire Formats</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The OpenWire Wire Format OpenWire is the default wire format used by ActiveMQ. It provides a highly efficient binary format for high speed messaging. OpenWire options can be configured on a JMS client's connection URI or on a broker's transport bind URI</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Connection+Configuration+URI">Connection Configuration URI</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Connection Configuration URI An Apache ActiveMQ connection can be configured by explicitly setting properties on the ActiveMQConnection http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.html or ActiveMQConnectionFactory http:</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Connection+Factory+Properties">Connection Factory Properties</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The 'outbound' Connection Factory objects used to send messages by default use the connection configuration properties of the Resource Adapter deployment, but those properties can be overridden per connection factory. The Connection Factory properties tha</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Connectivity">Connectivity</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ is designed to support a large number if Cross Language Clients, speak a wide range of Protocols and be usable in a wide variety of Containers in addition to being usable in a stand alone Java SE platform.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Consumer+Dispatch+Async">Consumer Dispatch Async</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview From ActiveMQ v4: the choice of a broker performing synchronous or asynchronous dispatch to a consumer has become more configurable. It is now configured as a default value on the connection URI, Connection and ConnectionFactory as well as with b</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Consumer+Features">Consumer Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Consumer+Priority">Consumer Priority</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background As well as having a pluggable dispatch policy e.g. round robin, ActiveMQ also supports consumer priorities. This allows us to weight consumers to optimize network hops. For example, you typically want a broker to send messages to regular JMS co</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Containers">Containers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page lists the various containers that Apache ActiveMQ works inside</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Contributing">Contributing</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are many ways you can help make ActiveMQ a better piece of software - please dive in and help! Try surf the documentation - if somethings confusing or not clear, let us know. Download the code & try it out and see what you think. Browse the source c</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Could+not+find+PacketReader+for+packet+type+-+UNKNOWN+PACKET+TYPE">Could not find PacketReader for packet type - UNKNOWN PACKET TYPE</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Error Could not find PacketReader for packet type: UNKNOWN PACKET TYPE: -102 Reason You are probably using different versions of ActiveMQ jars on the client and the broker. Try using the same jars on each node and the problem should go away. Once 4.0 is G</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Cross+Language+Clients">Cross Language Clients</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ is a message broker written in Java with JMS, REST and WebSocket interfaces, however it supports protocols like AMQP, MQTT, OpenWire and STOMP that can be used by applications in different languages. Libraries .NET http://activemq.apache.o</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-D"></a>D</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Delay+and+Schedule+Message+Delivery">Delay and Schedule Message Delivery</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ from version 5.4 has an optional persistent scheduler built into the ActiveMQ message broker. It is enabled by setting the broker schedulerSupport attribute to true in the Xml Configuration. An ActiveMQ client can take advantage of a delayed deli</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Delete+Inactive+Destinations">Delete Inactive Destinations</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">An 'inactive' destination is one that has had no messages pending and no consumers connected for some configured period of time.By default the broker does not check for inactive destinations. This as governed by the default values for the following option</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Delphi+and+FreePascal">Delphi and FreePascal</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Delphi and FreePascal Client Habari ActiveMQ Client is a library for Delphi(tm) and Free Pascal. With Habari, applications can connect to Apache ActiveMQ servers, subscribe to queues and topics, send and receive messages and objects, and work with transac</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Design+Documents">Design Documents</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Slow Consumers Durable Queue Memory Management Supporting IO Streams Message Redelivery and DLQ Handling Multicast Transport Proposed C Client Architecture REST protocols</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Destination+Features">Destination Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Destination+Options">Destination Options</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background Destination Options are a way to provide extended configuration options to a JMS consumer without having to extend the JMS API. The options are encoded using URL query syntax in the destination name that the consumer is created on. Consumer Opt</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Destinations+Plugin">Destinations Plugin</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">In some environments clients can't create destinations and only administrators are allowed to do that using management consoles or APIs. This plugin allows users to export destinations created during the runtime of the broker and replicate that state on a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Developer+Forum">Developer Forum</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"><a id="nabblelink" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html">ActiveMQ - Dev</a> <script src="http://activemq.2283324.n4.nabble.com/embed/f2368404"></script></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Developer+Guide">Developer Guide</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The following documents might be interesting Building Release Plans Release Guide Design Documents Changes in 4.0 Apache ActiveMQ Board Reports Maven SNAPSHOT Repository in your POM Code walkthrough Code Overview Wire Protocol Developing Plugins</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Developers">Developers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Developing+ActiveMQ">Developing ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Questions for developers wishing to extend or enhance Apache ActiveMQ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Developing+Plugins">Developing Plugins</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ is based on the model of POJOs and Dependency Injection. If you are developing Interceptors or additional components or plugins for ActiveMQ then the first thing you should do is develop the code as if you are writing any other Spring comp</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Discovery">Discovery</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Discovery Agents ActiveMQ uses an abstraction called a Discovery Agent http://actievmq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/transport/discovery/DiscoveryAgent.html to detect remote services such as remote brokers. We can use discover</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Discovery+Transport+Reference">Discovery Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Discovery Transport The Discovery transport works just like the Failover transport, except that it uses a discovery agent to locate the list of uri to connect to. The Discovery transport is also used by the Fanout transport for discovering brokers to </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Discussion+Forums">Discussion Forums</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Before posting you might want to read the Tips for getting help. Many users prefer to use online forums rather than joining a mail list which can lead to lots more email traffic so we use the online forums at Nabble forums http://activemq.2283324.n4.nabbl</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Dispatch+Policies">Dispatch Policies</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Dispatch Policies Dispatch policies for queues Plug-able dispatch policies only apply to topics. For Queues, dispatch is more static, you can choose round robin (the default) or strict order. Before discussing dispatch policies its worth first understandi</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Does+ActiveMQ+support+clustering">Does ActiveMQ support clustering</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Yes, though there are various kinds of clustering. See this page on details</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Does+ActiveMQ+support+my+SQL+database">Does ActiveMQ support my SQL database</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Quite possibly . See the JDBC Support page for details of how to configure for your database or how to let us know of a database which does not work. Also see Persistence</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Download">Download</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Latest Releases The latest stable release is the ActiveMQ 5.15.2 Release Getting past releases See the Download Archives for all time releases. In Progress Maven Repositories All ActiveMQ releases are available from the Maven central repository https://</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Download+Archives">Download Archives</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Download archives You can use the Apache Archives to download all the ActiveMQ releases. http://archive.apache.org/dist/activemq/ http://archive.apache.org/dist/activemq/ - ActiveMQ releases http://archive.apache.org/dist/activemq/apache-activemq/ http://</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Downloading+ActiveMQ+CPP">Downloading ActiveMQ CPP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ CPP distributions are source-only. To get the source bundle for a particular release, go here. Follow the instructions here only if you want the bleeding edge from trunk. Web Browsing of SVN To browse via the web use the ViewVC interface: http://</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/DR">DR</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Disaster Recovery. Typically this means having multiple data centres configured such that if there is a major catastrophy and an entire data centre is lost, messages are replicated to another location so the systems can continue running.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Durable+Queue+Memory+Management">Durable Queue Memory Management</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The current 3.x code can have issues with massive queues with un-acknowledged messages; its complex due to consumption from multiple points in the queue, consumers coming & going, selectors matching only certain points in the queue etc. This page outlines</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-E"></a>E</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Encrypted+passwords">Encrypted passwords</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">As of ActiveMQ 5.4.1 you can encrypt your passwords and safely store them in configuration files. To encrypt the password, you can use the newly added encrypt command like: $ bin/activemq encrypt --password activemq --input mypassword ... Encrypted text: </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Enterprise+Integration+Patterns">Enterprise Integration Patterns</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Enterprise Integration Patterns Version 5.0 onwards of Apache ActiveMQ comes complete with full support for the Enterprise Integration Patterns http://www.enterpriseintegrationpatterns.com/toc.html (from the excellent book by Gregor Hohpe http://www.amazo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Errors">Errors</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Questions on specific kinds of errors. If you have seen a specific exception then check the Exceptions</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Example+Testing+Scenario">Example Testing Scenario</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ Performance Module Users Manual Example Testing Scenario This page gives a simple example of the kinds of thing we wanna do. Assuming that all the test code is within a single Maven POM for now (e.g. activemq-integration-test version 4.0) which w</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Examples">Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Version 5 Examples</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Exceptions">Exceptions</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Questions Java Exceptions (when you get a nasty stack trace while working with ActiveMQ)</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Exclusive+Consumer">Exclusive Consumer</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background We maintain the order of messages in queues and dispatch them to consumers in order. However if you have multiple JMS Sessions and MessageConsumer instances consuming from the same queue (whether in the same JVM or not), you will loose the guar</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-F"></a>F</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Failover+Transport+Reference">Failover Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Failover Transport The Failover transport layers reconnect logic on top of any of the other transports. The configuration syntax allows you to specify any number of composite URIs. The Failover transport randomly chooses one of the composite URIs and </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Fanout+Transport+Reference">Fanout Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Fanout Transport The Fanout transport layers reconnect and replication logic on top of any of the other transports. It utilizes the Discovery transport to discover brokers and replicates commands to those brokers. Configuration Syntax fanout:(discover</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/FAQ">FAQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">FAQ Here are a list of commonly asked questions and answers. If you have any questions which are not on this list, please talk to us on the forums. We welcome contributions and this entire website is a wiki that you can edit so please join in and help us </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Features">Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ Features Apache ActiveMQ is packed with features; to get an idea you might want to look at the Features Overview otherwise here is the list of all of the main features...</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Features+Overview">Features Overview</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Supports a variety of Cross Language Clients and Protocols from Java, C, C++, C#, Ruby, Perl, Python, PHP OpenWire for high performance clients in Java, C, C++, C# Stomp support so that clients can be written easily in C, Ruby, Perl, Python, PHP, ActionSc</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-G"></a>G</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/General">General</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">General questions about ActiveMQ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Geronimo">Geronimo</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ is the default JMS provider in Apache Geronimo http://geronimo.apache.org. ActiveMQ can be used both as JMS Client and a JMS Broker. This short article explains how to use it on a standalone client to access the topics/queues setup on a remote Ge</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Getting+Started">Getting Started</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Introduction This document describes how to install and configure ActiveMQ 4.x/5.x for both Unix and Windows' platforms. Document Organization The Getting Started Guide for ActiveMQ 4.x document contains the following sections: Pre-Installation Requiremen</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Group+Membership">Group Membership</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveBlaze supports group membership using a GroupChannel - which can be created from a GroupChannelFactory. You have to explicitly say which group you want to join/leave - and you can join multiple groups. Each GroupChannel has both a globally unique id</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-H"></a>H</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/HA">HA</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">High Availability. This typically refers to having a number of available instances of a service (such as a Message Broker) such that if the instance you're connected to fails, you can failover quickly to another instance providing high availabliity and re</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Hello+World">Hello World</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The following is a very simple JMS application with multiple, concurrent, consumers and producers. See the Initial Configuration guide for details on how to setup your classpath correctly. Things you might do after running this example: Setup a broker ins</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Hermes+Jms">Hermes Jms</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You can use ActiveMQ with Hermes JMS http://hermesjms.sourceforge.net/ which is a graphical user interface for working with JMS queues. Please refer to the Hermes JMS http://hermesjms.sourceforge.net/ site for detailed instructions on using this software.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Hermes+Screenshot">Hermes Screenshot</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The following is an example of running HermesJms with ActiveMQ on OS X http://activemq.codehaus.org/hermes.png</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Horizontal+Scaling">Horizontal Scaling</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+add+a+new+type+of+transport">How can I add a new type of transport</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ is specifically designed to allow custom transports to be plugged in. You can programatically create TransportConnector instances and add them to the BrokerService in Java code using the BrokerService.addConnector() method http://activemq.codehau</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+avoid+serialization+of+Objects+in+ObjectMessage">How can I avoid serialization of Objects in ObjectMessage</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Use the VM transport and see details on how to disable serialization to pass by value</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+contribute">How can I contribute</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How can I contribute to Apache ActiveMQ? Contributing</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+enable+detailed+logging">How can I enable detailed logging</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How can I enable detailed logging We use slf4j which allows the underlying logging implementation to be statically bound at startup. By default we ship with log4j but feel free to make your own choice. If you've got log4j.jar on your classpath you can use</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+get+a+list+of+the+topics+and+queues+in+a+broker">How can I get a list of the topics and queues in a broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How can I get a list of the topics and queues in a broker? As of 5.1.0 you can use the new DestinationSource http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/DestinationSource.html on an ActiveMQConnection to access the </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+get+help">How can I get help</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Support</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+get+the+source+code+from+subversion">How can I get the source code from subversion</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Source</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+make+ActiveMQ+faster">How can I make ActiveMQ faster</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">See the Performance page for information about the performance of ActiveMQ and it's tuning parameters.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+monitor+ActiveMQ">How can I monitor ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How can I monitor ActiveMQ Starting with ActiveMQ 5.8.0 Jolokia http://www.jolokia.org/ is bundled which provides a RESTful interface to ActiveMQ's JMX capabilities. An open source third party tool that connects via Jolokia is hawt.io http://hawt.io/, an </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+monitor+the+connection+with+the+broker">How can I monitor the connection with the broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How can I monitor the connection with the broker You can monitor the status of the connection with the broker via the addTransportListener() method on the ActiveMQConnection http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.h</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+see+what+destinations+are+used">How can I see what destinations are used</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The easiest way is to use JMX by pointing your JMX console or JConsole at the broker JVM. You can also get all of the active destinations from the broker using Java code via getDestinations() http://activemq.apache.org/maven/5.8.0/apidocs/org/apache/activ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+support+auto+reconnection">How can I support auto reconnection</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How can I support auto reconnection? Networks are unreliable and sockets do get dropped from time to time (it could be a network glitch, dodgy router, firewall, or someone could even just restart a broker). You often want a JMS client to automatically han</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+support+priority+queues">How can I support priority queues</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How can I support priority queues? Use Message Priority A common requirement is to support priority consumption; so high priority messages are consumed before low priority. In version 5.4 priority queues are supported. Both the message cursors and the mes</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+can+I+use+different+network+protocols">How can I use different network protocols</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For easy configuration, ActiveMQ supports a configurable URL to denote the connection mechanism to other clients. There is an example of how to do this along with a description of the available protocols in the Protocols overview</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+distributed+queues+work">How do distributed queues work</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are various Topologies that you can employ with ActiveMQ, where clients are connected to message brokers in various ways like peer based client server hub and spoke Each client communicates with a broker using some kind of client library and network</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+durable+queues+and+topics+work">How do durable queues and topics work</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Durable queues keep messages around persistently for any suitable consumer to consume them. Durable queues do not need to concern themselves with which consumer is going to consume the messages at some point in the future. There is just one copy of a mess</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+access+ActiveMQ+from+C">How do I access ActiveMQ from C</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">See the C Integration page for the available options.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+access+ActiveMQ+from+CSharp+or+dotNet">How do I access ActiveMQ from CSharp or dotNet</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">dot Net</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+access+ActiveMQ+from+Ruby%2C+Perl%2C+Python%2C+PHP">How do I access ActiveMQ from Ruby, Perl, Python, PHP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Use Stomp http://stomp.codehaus.org/ which is a simple to implement client protocol for working with ActiveMQ and other messaging systems.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+add+my+own+plugins">How do I add my own plugins</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">See Developing Plugins for how to add your own functionality into Apache ActiveMQ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+avoid+Maven+downloading+latest+jars">How do I avoid Maven downloading latest jars</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You can use the -o switch (for offline mode) to avoid maven auto-downloading new snapshot jars (e.g. the Geronimo jars at the time of writing). maven -o or to run a server go to the \assembly module and run maven -o server</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+back-up+KahaDB">How do I back-up KahaDB</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">In creating a backup, there may be an issue with the lock file, or with an inuse journal file. The lock file is not important but you would want the latest journal files. Freeze the filesystem containing the database to ensure that you get a consistent sn</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+bridge+different+JMS+providers">How do I bridge different JMS providers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">To bridge from ActiveMQ to another JMS provider use the JMS bridge. To bridge to another kind of transport completely, use Camel http://camel.apache.org or ServiceMix http://servicemix.apache.org</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+build+but+disable+the+unit+tests">How do I build but disable the unit tests</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I build but disable the unit tests The test cases in ActiveMQ can take a very long time to run! To disable this you can try the following mvn install -Dmaven.test.skip=true</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+change+dispatch+policy">How do I change dispatch policy</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This is much simpler and more powerful in ActiveMQ 4.0 - you can configure different Dispatch Policies directly. For now in ActiveMQ 3.x we have a PrefetchPolicy configuration. This allows a certain number of messages to be dispatched to a consumer before</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+change+the+logging">How do I change the logging</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I change the logging We use slf4j to log information in the broker client and the broker itself so you can fully configure which logging levels are used and whether to log to files or the console etc. For more information see the log4j manual. http</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+change+the+message+store+directory+for+an+embedded+broker">How do I change the message store directory for an embedded broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Embedded brokers create an ActiveMQ directory under the current working directory to store it's persistent message data. To change the location of the directory used by the message store, set the activemq.store.dir system property to the directory you wan</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+compile+from+the+source">How do I compile from the source</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I compile from the source code? See the Building page</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+configure+10s+of+1000s+of+Queues+in+a+single+broker">How do I configure 10s of 1000s of Queues in a single broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Scaling Queues</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+configure+ActiveMQ+to+hold+100s+of+millions+of+Queue+Messages">How do I configure ActiveMQ to hold 100s of millions of Queue Messages</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Scaling the Depth of a Queue</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+configure+ActiveMQ+to+use+AIO+server+transport">How do I configure ActiveMQ to use AIO server transport</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For Windows XP: 1. Download AIO (Asynchronous IO for Java) from IBM (http://www.alphaworks.ibm.com/tech/aio4j http://www.alphaworks.ibm.com/tech/aio4j). 2. Unzip the downloaded file and copy the following files: ibmaio.dll ibmaio-1.0.jar 3. Place ibmaio.d</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+configure+automatic+reconnection">How do I configure automatic reconnection</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If a JMS broker goes down, ActiveMQ can automatically reconnect to an available JMS broker using the failover: protocol. Not only does this automatically reconnect, it will also resume any temporary destinations, sessions, producers and most importantly c</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+configure+distributed+queues+or+topics">How do I configure distributed queues or topics</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I configure distributed queues or topics You don't need to explicitly configure distributed queues or topics as any queue or topic is automatically distributed across other brokers when the brokers are configured in either a store and forward netwo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+configure+the+queues+I+want">How do I configure the queues I want</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I create new destinations With ActiveMQ there is no real resaon to explicitly setup/configure the queues you are gonna need. If you try to publish or subscribe from any queue or topic it will be silently created on the fly. Sometimes people put des</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+connect+to+one+of+a+number+of+message+brokers">How do I connect to one of a number of message brokers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You can specify a list of URLs to connect to (for example if you have message brokers running on a number of machines). To specify a list of URLs, use a comma separated list of URLs with a prefix of list:. e.g. list:tcp://localhost:61699,tcp://localhost:6</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+consume+a+specific+message">How do I consume a specific message</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you want to consume messages in a different order, or consume specific messages at the head, middle or tail of the queue, you can browse the messages using the QueueBrowser to find the JMSMessageID's of the messages you want to consume create a new con</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+create+new+destinations">How do I create new destinations</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">In ActiveMQ you do not have to create destinations up front before you can use them. The ActiveMQ broker auto-creates the physical resources associated with a destination on demand (i.e. when messages are sent to a new destination on a broker). This means</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+debug+ActiveMQ+from+my+IDE">How do I debug ActiveMQ from my IDE</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">One option is to run your broker in the same JVM as your application; see How To Unit Test JMS Code. Or you can try uncommenting ACTIVEMQ_DEBUG_OPTS in your activemq start script (bin/activemq or bin\activemq.bat) and start remote debugging in your IDE. F</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+define+a+local+address+and+local+port+for+TCP+or+SSL">How do I define a local address and local port for TCP or SSL</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">TCP based transport protocols (including SSL) allow you to define the local address and local port for Socket to use when it's created. This can be useful for clients that reside on multi-homed machines or for clients operating in a DMZ, where only pre-de</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+delete+a+destination">How do I delete a destination</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I delete a destination via Java code or JMX you can grab the BrokerViewMBean http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/BrokerViewMBean.html and call one of the following methods removeQueue(String) http:/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+disable+logging">How do I disable logging</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I disable logging? See How do I change the logging</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+disable+persistence">How do I disable persistence</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are three main ways to disable persistence, such as for unit testing JMS code Set the NON_PERSISTENT message delivery flag on your MessageProducer Set the persistent=false flag in the <broker/> element of the Xml Configuration or on the property Bro</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+edit+the+website">How do I edit the website</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The website is all contained on a Wiki so that anyone can contribute How to edit You can also click the edit button when viewing the website which is located on the bottom of each page. We have been attacked by spammers so we are running a spam-avoiding s</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+embed+a+Broker+inside+a+Connection">How do I embed a Broker inside a Connection</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">In many messaging topologies there are JMS Brokers (server side) and a JMS client side. Often it makes sense to deploy a broker within your JVM. This allows you to optimise away a network hop; making the networking of JMS as efficient as pure RMI, but wit</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+enable+asynchronous+sending">How do I enable asynchronous sending</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The default setting for ActiveMQ is that all persistent messages outside of a transaction are sent to a broker are synchronous. This means that the send method is blocked until the message is received by the broker, its then written to disk - then a respo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+enable+debug+logging">How do I enable debug logging</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I enable debug logging? For background see How do I change the logging. You can enable debug logging in ActiveMQ by adding the following line to the conf/log4j.properties file log4j.logger.org.apache.activemq=DEBUG</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+find+the+Size+of+a+Queue">How do I find the Size of a Queue</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I check on the size of the queue? I know it's not JMS standard, but most JMS implementations have a way to do this. You can view the queue depth using the MBeans in ActiveMQ 5.x. Use any JMX management console to see the statistics. See How can I m</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+get+started+with+JMS">How do I get started with JMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I get started with JMS Your best way to get started understanding the JMS API is Sun's JMS tutorial http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JMS.html#wp84181. Alternatively you could stick to writing business level POJOs and hide the middlewa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+make+messages+durable">How do I make messages durable</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Durability of messages is defined by the MessagerProducer http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html. You can explicitly configure the durability via the setDeliveryMode() method http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Me</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+preserve+order+of+messages">How do I preserve order of messages</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ will preserve the order of messages sent by a single producer to all consumers on a topic. If there is a single consumer on a queue then the order of messages sent by a single producer will be preserved as well. If you have multiple consumers on </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+purge+a+queue">How do I purge a queue</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">A frequent requirement is to purge a queue (i.e. delete all the messages on it). Solution You can use the Web Console to view queues, add/remove queues, purge queues or delete/forward individual messages. Another option is to use JMX to browse the queues </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+restart+embedded+broker">How do I restart embedded broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Pure restart of the embedded broker is not advisable, since it's state could be corrupted. Therefore, you're advised to instantiate the broker again before restarting it. BrokerService service = BrokerFactory.createBroker("xbean:activemq.xml"); service.st</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+restrict+connections+from+creating+new+queues+or+topics">How do I restrict connections from creating new queues or topics</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I restrict connections from creating new queues or topics? As is described in How do I create new destinations there is no need to create all the destinations up front, you can let the broker create them on the fly. However if you don't want this b</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+run+a+broker">How do I run a broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For ActiveMQ 3.x/4.x Please see the running a broker page</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+run+ActiveMQ+under+the+Kaffe+JVM">How do I run ActiveMQ under the Kaffe JVM</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ will run under Kaffe with a few adjustments to the default configuration. We have found the Kaffe does not properly implement: File based NIO Multicast Sockets JMX connector JNDI handling Therefore, the default ActiveMQ configuration must be adju</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+send+messages+to+different+Destinations+from+a+single+MessageProducer">How do I send messages to different Destinations from a single MessageProducer</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I send messages to different Destinations from a single MessageProducer? Create the MessageProducer using a null destination; then specify the destination each time you send... MessageProducer producer = session.createProducer(null); ... producer.s</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+set+the+message+expiration">How do I set the message expiration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JMSExpiration on a message is set by the MessageProducer in JMS - either via producer.setTimeToLive() http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#setTimeToLive(long) producer.send(Destination, Message, int, int, long) http://java.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+turn+off+creating+an+embedded+ActiveMQ+broker+when+using+the+VM+transport">How do I turn off creating an embedded ActiveMQ broker when using the VM transport</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You can turn off auto creation by setting the create property on the VM Transport to false: ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory("vm://localhost?create=false");</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+unack+the+message+with+Stomp">How do I unack the message with Stomp</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There is no explicit "unack" command in Stomp. Once the client receives the message it cannot be marked as "unconsumed" and sent to another subscriber (or redelivered to the same subscriber again). It's up to your application (or Stomp client) to handle f</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+use+ActiveMQ+using+in+JVM+messaging">How do I use ActiveMQ using in JVM messaging</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For ActiveMQ 3.x/4.x To use pure in-memory messaging you just need to set the broker URL to be vm://localhost Actually you can use any text after vm:// so that you can segment multiple logical JMS brokers within the same JVM and classloader, using the n</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+use+durable+subscribers+in+a+network+of+brokers">How do I use durable subscribers in a network of brokers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Durable subscribers behave a little differently across a cluster of ActiveMQ brokers. The two main issues surround messages getting stuck on other brokers in the network after a durable subscriber has disconnected and reconnected to a different broker in </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+use+Ivy+with+ActiveMQ">How do I use Ivy with ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"><ivyconf> <!--loads properties file as ivy variables, 0..n--> <properties file="${ivy.conf.dir}/ivyconf-file.properties" /> <!--configures ivy with some defaults, 0..1--> <conf defaultResolver="localChain" checkUpToDate="false" /> <!--typedef:defines new </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+use+JMS+efficiently">How do I use JMS efficiently</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How do I use JMS efficiently? JMS is designed for high performance. In particular its design is such that you are meant to create a number of objects up front on the startup of your application and then resuse them throughout your application. e.g. its a </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+use+log4j+JMS+appender+with+ActiveMQ">How do I use log4j JMS appender with ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Log4j JMS appender http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/net/JMSAppender.html can be used to send your log messages to JMS broker. To use ActiveMQ as a destination of your messages, you need to configure JMS appender properly. The c</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+I+use+SSL">How do I use SSL</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Setting up the Key and Trust Stores Also see Tomcat's SSL instructions http://jakarta.apache.org/tomcat/tomcat-5.5-doc/ssl-howto.html for more info. The following was provided by Colin Kilburn. Thanks Colin! ActiveMQ includes key and trust stores that ref</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+Message+Groups+compare+to+Selectors">How do Message Groups compare to Selectors</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Selectors are just filters. Message Groups are a way of grouping messages together to the same consumer to partition your application or insure ordering is maintained. Now you could implement message groups by hand, by having each consumer use its own sel</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+do+multiple+transports+work">How do multiple transports work</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For ActiveMQ 3.x/4.x The transport a client uses to connect to the broker is just the transport your client uses. So messages the broker sends to your client will be sent over that transport. However the broker can support many transports. So client A cou</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+Do+Transactions+Work">How Do Transactions Work</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are two levels of transaction support in ActiveMQ: JMS Transactions - the commit()/rollback() methods on a Session (which is like doing commit()/rollback() on a JDBC connection) XA Transactions - where the XASession http://activemq.apache.org/maven/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+a+Queue+compare+to+a+Topic">How does a Queue compare to a Topic</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Topics In JMS a Topic implements publish and subscribe semantics. When you publish a message it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message. Only subscribers who had an active subscriptio</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+ActiveMQ+compare+to+AMQP">How does ActiveMQ compare to AMQP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">AMQP stands for the Advanced Message Queue Protocol and is a specification for how messaging clients and brokers can interoperate. AMQP is a specification of a wire-level protocol for client to message broker communication. It is not a messaging system li</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+ActiveMQ+compare+to+Artemis">How does ActiveMQ compare to Artemis</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Artemis https://activemq.apache.org/artemis/ is the codename used for the HornetQ code that was donated to the Apache Foundation. It is possible that Artemis will eventually become the successor to ActiveMQ 5.x (and that it might eventually be branded as </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+ActiveMQ+compare+to+Fuse+Message+Broker">How does ActiveMQ compare to Fuse Message Broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Fuse Message Broker http://fusesource.com/products/enterprise-activemq/ is a certified distribution of Apache ActiveMQ provided by FuseSource. FuseSource http://fusesource.com does all of its development and bug fixes as part of the Apache ActiveMQ commun</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+ActiveMQ+compare+to+JBossMQ">How does ActiveMQ compare to JBossMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are some similarities between the two; they both support JMS 1.1 and run inside JBoss 4.x. However ActiveMQ does offer some specific differences and advantages (at least from our perspective) ActiveMQ works great in any JVM not just inside the JBoss</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+ActiveMQ+compare+to+Mantaray">How does ActiveMQ compare to Mantaray</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We are obviously biased, and will tell you "just use ActiveMQ!" But Mantaray is an OK JMS provider. The interesting thing about MantaRay is it can support a peer-based network, just as ActiveMQ does with its peer transport. We benchmark against Mantaray a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+ActiveMQ+compare+to+Mule">How does ActiveMQ compare to Mule</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ is a messaging provider, with extensive capabilities for message brokering. Mule is described as an ESB, in that it defines and executes the brokering of message exchanges among integrated software components. Architecture Mule provides an</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+ActiveMQ+compare+to+Spread+Toolkit">How does ActiveMQ compare to Spread Toolkit</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Spread Toolkit is a C++ library for messaging and only has partial support for JMS http://www.spread.org/JMS4Spread/docs/. It doesn't support durable messaging, transactions, XA or full JMS 1.1. It is also dependent on a native code Spread daemon running </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+ConnectionFactory+relate+to+the+Broker">How does ConnectionFactory relate to the Broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How does ConnectionFactory relate to the Broker? The ConnectionFactory is a JMS specification client side interface for creating connections to a JMS broker. The Broker is a service on the network or embedded in the same JVM which provides the message pro</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+JMS+compare+with+email">How does JMS compare with email</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Certainly they both do similar things. The main difference between them is their history and design criteria. JMS has a bunch of different qualities of service (durable v non-durable, queue v topic) designed for very high performance messaging with low la</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+journaling+work+with+multiple+brokers">How does journaling work with multiple brokers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Brokers cannot share a journal. Each must be configured with it's own journal.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+OpenWire+compare+to+Stomp">How does OpenWire compare to Stomp</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">OpenWire is the native protocol that Apache ActiveMQ uses. It is designed for performance and size on the wire - sacrificing some ease of implementation with higher performance and reduced network bandwidth as a priority. OpenWire was first released in Ap</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+the+journal+work">How does the journal work</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">See the description here</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+the+website+work">How does the website work</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This website is actually rendered from the Wiki contents that you can edit. When viewing a page on the static HTML website you can click on the edit link (bottom of the page) and you can edit the page. Other useful Site links are Site Note that it takes a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+does+XBean+compare+to+Spring+2">How does XBean compare to Spring 2</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Spring 2.0 has introduced the ability to handle custom XML languages inside the spring.xml. This is something we developed XBean http://geronimo.apache.org/xbean/ for way back in the Spring 1.x days. The Spring hook requires component developers to write </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+fast+is+ActiveMQ">How fast is ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How fast is ActiveMQ? It all depends on the configuration, the operating system, hardware, JVM, JVM configuration and what you're doing. For more details see Performance Performance report</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+lightweight+is+sending+a+message">How lightweight is sending a message</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For ActiveMQ 3.x/4.x It depends If you are in a JMS transaction, are using non-durable messaging then its fairly lightweight and fast - typically just blocking until the message has got onto the socket buffer. Though if you are using durable messaging and</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+should+I+implement+request+response+with+JMS">How should I implement request response with JMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How should I implement request response with JMS? The simplest solution is to use Camel as a Spring Remoting provider http://activemq.apache.org/camel/spring-remoting.html which allows you to hide all the JMS API from your business logic and letting Camel</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+should+I+package+applications+using+Camel+and+ActiveMQ">How should I package applications using Camel and ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How should I package applications using Camel and ActiveMQ So you may wish to use Camel's Enterprise Integration Patterns inside the ActiveMQ Broker. In which case the stand alone broker is already packaged to work with Camel out of the box; just add your</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+should+I+use+the+VM+transport">How should I use the VM transport</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For ActiveMQ 3.x/4.x Using the VM transport to connect to an in-JVM broker is the fastest and most efficient transport you can use. This is because by default there is no serialization to a socket or operating system socket resources used up; its purely a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+Become+a+Committer+on+the+ActiveMQ+Project">How to Become a Committer on the ActiveMQ Project</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How to Become a Committer on the ActiveMQ Project This page is under active development so the ideas here are very fluid right now. As outlined on How It Works document http://www.apache.org/foundation/how-it-works.html and the ASF roles https://www.apach</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+configure+a+new+database">How to configure a new database</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ explicity supports Derby, Axion, HSQL, Oracle, and SQLServer. Below are the steps on how to configure a new database. 1. Modify activemq.xml found in the directory "activemq_home/conf" by editing or adding a JDBC DataSource Configuration. e.g. <b</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+deal+with+large+number+of+threads+in+clients">How to deal with large number of threads in clients</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you study thread allocation in ActiveMQ clients, you'll notice that by default there is one thread allocated by every session. This basically means that session will use its ThreadPoolExecutor http://docs.oracle.com/javase/6/docs/api/java/util/concurre</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+deploy+activemq-ra-version.rar+to+weblogic">How to deploy activemq-ra-version.rar to weblogic</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This is a guide on how to deploy ActiveMQ's resouce adapter to weblogic 9.1. Create a new domain in weblogic using the configuration wizard (Start menu BEA Products -> Tools -> configuration Wizard ). Add the jar dependencies (these are the jars inside th</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+disable+auto+destination+creation">How to disable auto destination creation</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">see How do I restrict connections from creating new queues or topics</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+disable+multicast+discovery">How to disable multicast discovery</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">By default, the ActiveMQ xml configuration includes the multicast discovery mechanism. The tcp transport connector advertises its self using multicast and a multicast network connector is configured to listen to the same address. In this way, all brokers </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+To+Unit+Test+JMS+Code">How To Unit Test JMS Code</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">When unit testing code with JMS you'll typically want to avoid the overhead of running separate proceses; plus you'll want to increase startup time as fast as possible as you tend to run unit tests often and want immediate feedback. Also persistence can o</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+you+can+help+release">How you can help release</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How to Help Everyone in the ActiveMQ community can help with releases; users, developers, commmiters are all encouraged to test out a release and post any comments to the activemq-dev@ mailing list or create a JIRA https://issues.apache.org/activemq/brows</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/HTTP+and+HTTPs+Transports+Reference">HTTP and HTTPs Transports Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">HTTP and HTTPS Transports The HTTP and HTTPS transports are used to tunnel over HTTP or HTTPS using XML payloads. This allows the ActiveMQ client and broker to tunnel over HTTP avoiding any firewall issues. If the client is not JMS you might want to look </div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-I"></a>I</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/I+am+having+problems+with+the+Spring+JmsTemplate">I am having problems with the Spring JmsTemplate</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">I am having problems with the Spring JmsTemplate For more detail see the JmsTemplate Gotchas page along with the Spring Support</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/I+am+not+receiving+any+messages%2C+what+is+wrong">I am not receiving any messages, what is wrong</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">I am not receiving any messages - what is wrong? A very common gotcha when working with JMS is forgetting to start the JMS connection, creating a consumer and not having it receive any messages. I myself have tripped up over this one many many times! Make</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/I+cannot+connect+to+ActiveMQ+from+JConsole">I cannot connect to ActiveMQ from JConsole</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Make sure that the machine you are talking to has a valid java.rmi.server.hostname-property value e.g. on unix (OS X, Linux, Solaris) export ACTIVEMQ_OPTS=$ACTIVEMQ_OPTS -Djava.rmi.server.hostname=<hostname> activemq or on Windows SET ACTIVEMQ_OPTS=%ACTIV</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/I+do+not+receive+messages+in+my+second+consumer">I do not receive messages in my second consumer</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Scenario You send 100 messages to a queue. Start consumer A, it receives the message You start another consumer B, it doesn't receive any messages. You kill A. Consumer B receives messages now, why? Answer This is to do with prefetch buffers. ActiveMQ wil</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/I+get+errors+building+the+code+whats+wrong">I get errors building the code whats wrong</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We currently use a multi-project maven build system, which can be a little fragile. If you are ever having problems building we suggest you try the following in the root activemq directory mvn clean rm -rf ~/.m2/repository mvn You may also want to disable</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/I+see+NC_+client-ids%2C+what+does+that+mean">I see NC_ client-ids, what does that mean</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Durable subscription ClientIds and SubscriptionNames using the NC prefix are the result of durable subscriptions in a Networks of Brokers. When a durable subscription is being forwarded by a network connector (or demand forwarding bridge), the network dur</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Ideas">Ideas</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page hosts various ideas and thoughts...</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/In+Progress">In Progress</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Releases In Progress The following releases are currently in progress</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Inbound+Communication">Inbound Communication</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring an MDB to receive messages from ActiveMQ There are three MDBs declared in the ejb-jar.xml deployment descriptor. For this example, I will be explaining how to configure the TopicDurableMDB to be invoked by JBoss when a message is received on a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-homepage" title="Home page">Home page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Index">Index</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Download ActiveMQ 5.15.2 Today! Apache ActiveMQ http://activemq.apache.org/ ™ is the most popular and powerful open source messaging and Integration Patterns server. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with e</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Initial+Configuration">Initial Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Initial Configuration Document Organization #Required JARs #Optional JARS #Persistence Support #Next steps #Additional Resources #Related Reading #Specifications #Related open source projects Firstly you need to add the jars to your classpath. Required JA</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Installation">Installation</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Download a binary distribution of ActiveMQ and unpack it into some directory. To run an ActiveMQ broker, type the following commands from the directory in which you have just unpacked the ActiveMQ distribution. cd bin activemq The ActiveMQ broker should n</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Integrating+Apache+ActiveMQ+with+Glassfish">Integrating Apache ActiveMQ with Glassfish</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">General See this article for a description of how to connect Glassfish 3 to an ActiveMQ 5 broker, and consume messages using a Message Driven Bean: http://geertschuring.wordpress.com/2012/04/20/how-to-connect-glassfish-3-to-activemq-5/ http://geertschurin</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Integrating+Apache+ActiveMQ+with+JBoss">Integrating Apache ActiveMQ with JBoss</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">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, messa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Integration+Tests">Integration Tests</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Integration Tests validate that ActiveMQ Resource Adapter operate correctly when deployed with a J2EE application running in an Application Server such as Apache Geronimo. Getting Ready The instructions on this page reference a few directories that yo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Interceptors">Interceptors</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ has a sophisticated interceptor stack so that you can attach whatever functionality you require into the broker in an easy way without complicating all of the other broker code. This has really helped us keep the code clean and modular while offe</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/IOException+-+could+not+find+class+for+resource">IOException - could not find class for resource</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you get an exception looking like this Reason: java.io.exception : could not find class for resource: META-INF/services/org/apache/activemq/transport/tcp Cause You are probably using the ActiveMQ source code without using the resources Quick fix Try </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/IRC">IRC</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Committers and contributors can often be found hanging out in IRC. Below is the information about the channel that we use: Server: irc.freenode.net Channel: #apache-activemq There are many IRC clients https://en.wikipedia.org/wiki/Comparison_of_Internet_</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Is+there+a+specified+size+of+the+journal">Is there a specified size of the journal</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There is a "preferred" size for each log file of the journal. By default there are 2 20 meg log files.</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-J"></a>J</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/J2EE">J2EE</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">In J2EE 1.4 or later the standard way to integrate with a JMS provider is via JCA 1.5 and a Resource Adapter. Resource Adapter</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Java+Service+Wrapper">Java Service Wrapper</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page provides some useful information on running the ActiveMQ broker as a windows-NT service or a daemon thread in Linux or Unix systems. The ActiveMQ distribution uses an older and free community release of the service wrapper library. This wrapper </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/java.io.InterruptedIOException">java.io.InterruptedIOException</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"> The activemq client will throw an java.io http://java.io.InterruptedIOException if the calling thread has been interrupted while the transport (ResponseCorrelator) is waiting for a response. Thread interruption while waiting for a response is treated a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/java.io.IOException+Failed+to+create+database+%27derbydb%27%2C+see+the+next+exception+for+details">java.io.IOException Failed to create database 'derbydb', see the next exception for details</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you get an error like this Jun 19, 2006 10:35:27 PM org.apache.activemq.broker.BrokerService getBroker INFO: ActiveMQ 4.0 JMS Message Broker (localhost) is starting Jun 19, 2006 10:35:27 PM org.apache.activemq.broker.BrokerService getBroker INFO: For h</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/java.lang.NoSuchMethodError">java.lang.NoSuchMethodError</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you get an error like java.lang.NoSuchMethodError: javax.jms.Session.createConsumer(Ljavax/jms/Destination;)Ljavax/jms/MessageConsumer; or java.lang.AbstractMethodError: javax.jms.ConnectionFactory.createConnection()Ljavax/jms/Connection; Fix You proba</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/java.lang.NoSuchMethodException+org.activemq.ra.ActiveMQResourceAdapter.setUseEmbeddedBroker">java.lang.NoSuchMethodException org.activemq.ra.ActiveMQResourceAdapter.setUseEmbeddedBroker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you get an error like this 2005-08-14 17:18:45,618 ERROR [org.jboss.resource.deployment.RARDeployment] Starting failed jboss.jca:service=RARDeployment,name='activemq-ra-3.0.rar' org.jboss.deployment.DeploymentException: Error for resource adapter class</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/java.lang.OutOfMemory">java.lang.OutOfMemory</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Ok, this is manageable. It is possible to configure just about all of the memory utilisation of ActiveMQ. The first thing to determine is what part of the system is running out of memory. Is it the JVM, the broker, the consumers or the producers? This ent</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JavaDocs">JavaDocs</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JavaDocs for Apache ActiveMQ Versioned JavaDocs for Apache ActiveMQ could be found at http://activemq.apache.org/maven/ http://activemq.apache.org/maven/x.y.z/apidocs/index.html kind of url, where x.y.z is broker version you're looking for. For example ht</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml">javax.jms.JMSException - Wire format negociation timeout - peer did not send his wire format.</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you get exception like this: javax.jms.JMSException: Wire format negociation timeout: peer did not send his wire format. at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:58) at org.apache.activemq.ActiveMQConnection.syncS</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI () needs 2.1 API.</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">When using JDK 6 (up to JDK 6 Update 3) to run ActiveMQ you can run into this exception. There are two solutions to this: Upgrade to JDK to 1.6.0_04 or above, which includes JAXB 2.1 Copy JAXB 2.1 to <JAVA_HOME>/lib/endorsed to override the API jars that </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JAXB+2.0+API+is+being+loaded+from+the+bootstrap+classloader%2C+but+this+RI+%28xxx%29+needs+2.1+API">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (xxx) needs 2.1 API</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">When using JDK 6 (up to JDK 6 Update 3) to run ActiveMQ you can run into this exception. There are two solutions to this: Upgrade to JDK to 1.6.0_04 or above, which includes JAXB 2.1 Copy JAXB 2.1 to <JAVA_HOME>/lib/endorsed to override the API jars that </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JBoss+Integration">JBoss Integration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Integrating Apache ActiveMQ with JBoss</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JCA+Container">JCA Container</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We will continune to support the ActiveMQ JCA Container up until ActiveMQ 3.1. After that point we will be moving to Jencks http://jencks.codehaus.org/ which is a migration of the ActiveMQ codebase together with code Geronimo http://geronimo.apache.org an</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JDBC+Master+Slave">JDBC Master Slave</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JDBC Master Slave First supported in ActiveMQ version 4.1 If you are using pure JDBC and not using the high performance journal then you are generally relying on your database as your single point of failure and persistence engine. If you do not have real</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JDBC+Support">JDBC Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We support a range of SQL databases for message persistence such as Apache Derby Axion DB2 HSQL Informix MaxDB MySQL Oracle Postgresql SQLServer Sybase as well as a number of generic JDBC providers. Auto-discovery of your JDBC provider We try to auto-dete</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMeter+Performance+Tests">JMeter Performance Tests</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JMeter performance test You can use JMeter to test the performance of your ActiveMQ Server. Please refer to the JMeter site http://jakarta.apache.org/jmeter/ for detailed instructions on using this software. Downloading the JMeter Performance Test Binary </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMeter+System+Tests">JMeter System Tests</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JMeter System Tests You can use JMeter to test your ActiveMQ Server. Please refer to the JMeter site for detailed instructions on using this software. The Test would check for duplicate messages and the order of messages received. Building a Test Plan For</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMS">JMS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Questions on using the JMS API and MOM in general</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMS+and+JDBC+operations+in+one+transaction">JMS and JDBC operations in one transaction</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JMS and JDBC operations in one transaction with Spring/Jencks/ActiveMQ Spring beans: <beans> <!-- ActiveMQ Broker --> <bean id="broker" class="org.apache.activemq.broker.BrokerService" init-method="start" destroy-method="stop"> <property name="persistent"</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMS+Bridge+With+Local+Broker">JMS Bridge With Local Broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Example of a configuration that shows how to use a BridgeConnector to make a connection to the local ActiveMQ broker. <beans> <!-- Allows us to use system properties as variables in this configuration file --> <bean class="org.springframework.beans.factor</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMS+Bridge+With+Oracle+AQ">JMS Bridge With Oracle AQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Example of a configuration that shows how to connect to Oracle AQ queues and topics. <beans> <!-- Allows us to use system properties as variables in this configuration file --> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfi</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMS+Bridge+With+Remote+Broker">JMS Bridge With Remote Broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Example of a configuration that shows how to use a BridgeConnector to make a connection to a remote ActiveMQ broker. <beans> <!-- Allows us to use system properties as variables in this configuration file --> <bean class="org.springframework.beans.factory</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMS+Bridge+With+Remote+TIBCO+Broker">JMS Bridge With Remote TIBCO Broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Example of a configuration that shows how to use a BridgeConnector to make a connection to a remote TIBCO EMS broker. <beans> <!-- Allows us to use system properties as variables in this configuration file --> <bean class="org.springframework.beans.factor</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMS+Streams">JMS Streams</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">deprecated This feature is deprecated, and end users is encouraged to not use it. This feature will be removed in a later ActiveMQ release. Sometimes you need to send truly massive files (many Gb) around the network in a reliable manner. The JMS API expec</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMS+to+JMS+Bridge">JMS to JMS Bridge</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Introduction Note that we recommend you look at using Apache Camel http://camel.apache.org/ for bridging ActiveMQ to or from any message broker (or indeed any other technology, protocol or middleware http://camel.apache.org/components.html) as its much ea</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JmsTemplate+Gotchas">JmsTemplate Gotchas</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The thing to remember is JmsTemplate is designed for use in EJBs using the EJB containers JMS pooling abstraction. So every method will typically create a connection, session, producer or consumer, do something, then close them all down again. The idea be</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMSXUserID">JMSXUserID</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JMSXUserID support It is sometimes useful to know the authenticated username of the sender of a message. This is not added by default but you can enable it by setting the populateJMSXUserID property on the broker via Java code BrokerService broker = new B</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMX">JMX</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JMX Apache ActiveMQ has extensive support for JMX to allow you to monitor and control the behavior of the broker via the JMX MBeans http://activemq.apache.org/maven/apidocs/org/apache/activemq/broker/jmx/package-summary.html. Using JMX to monitor Apache A</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JMX+Support">JMX Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page describes the JMX management requirements. Required MBeans Broker MBeans We need MBeans for the core Broker types in the activemq.broker package to allow folks to see a broker's configuration, its connectors, currently connected clients & discon</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JNDI+Support">JNDI Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ will work with any JNDI provider capable of storing Java objects. However it is common to require a JNDI initial context to be able to run many JMS example programs, like Sun's JMS tutorial. http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Journal+is+already+opened+by+this+application">Journal is already opened by this application</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Error You get something like this java.io.IOException: Journal is already opened by this application. at org.apache.activeio.journal.active.ControlFile.lock(ControlFile.java:71) at org.apache.activeio.journal.active.LogFileManager.initialize(LogFileManage</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/JUnit+Reports">JUnit Reports</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The latest test reports are visible via the Hudson ActiveMQ continuous integration builds https://hudson.apache.org/hudson/job/ActiveMQ/</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-K"></a>K</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Kaha+Persistence">Kaha Persistence</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Kaha Persistence Kaha Peristence is a storage solution written especially for message persistence and is part of the ActiveMQ project. It's tuned to provide optimal performance for typical message usage patterns, which involves writing/reading and discard</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/KahaDB">KahaDB</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">KahaDB is a file based persistence database that is local to the message broker that is using it. It has been optimized for fast persistence. It is the the default storage mechanism since ActiveMQ 5.4. KahaDB uses less file descriptors and provides faster</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="kahadb-replication-experimental.xml">KahaDB Replication (Experimental)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This is under review - and not currently supported. Overview The new KahaDB store supports a very fast and flexible replication system. It features: Journal level replication (The translates into lower overhead to the master to replicate records). Support</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Known+Bad+OS+and+JVM+Combinations">Known Bad OS and JVM Combinations</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Operating System Java Virtual Machine Problem description Red Hat Linux Advanced Server release 2.1AS (Pensacola) kernel 2.4.9-e.62smp j2sdk1.4.0_01 Broker could not start up due to error with journal</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-L"></a>L</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Latency">Latency</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Latency We typically use this term when talking about the elapsed time it takes to process a single message. When using Request-Response message topologies its often means the round trip time for a message to flow to a service and for the reply to be reci</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/LDAP+Broker+Discovery+Mechanism">LDAP Broker Discovery Mechanism</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring network topologies can be quite tedious when the number of brokers in the system is large. To help ease the configuration overhead for these types of situations, a broker can be configured to look up its broker connections using a LDAP v3 dire</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/LevelDB+Store">LevelDB Store</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The LevelDB store has been deprecated and is no longer supported or recommended for use. The recommended store is KahaDB Available in ActiveMQ 5.8.0 and newer The LevelDB Store is a file based persistence database that is local to the message broker that </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Life+Cycle">Life Cycle</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Life cycle of Channels Blaze Channels are in one of five states: Constructed - the Channel isn't initialized or has been shutDown initialized - you can explicitly initialize a Channel by invoking its init() method. At this point its Configuration is set B</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Load+Testing+with+Camel">Load Testing with Camel</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Load Testing with Camel It is preferable at the time of writing to check out the source of ActiveMQ and Camel and perform local builds first. Then run a broker either via the bin/activemq script or you could be untar/unzip the assembly/target/apache-activ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/log4j-WARN+No+appenders+could+be+found+for+logger">log4j-WARN No appenders could be found for logger</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Error log4j:WARN No appenders could be found for logger (org.activemq.transport.tcp.TcpTransportChannel). log4j:WARN Please initialize the log4j system properly. Solution You have not initialised log4j properly. Try reading the online log4j manual http://</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Logging+a+warning+if+you+forget+to+start+a+Connection">Logging a warning if you forget to start a Connection</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Logging a warning if you forget to start a Connection A very common gotcha when working with JMS is forgetting to start the JMS connection, creating a consumer and not having it receive any messages. I myself have tripped up over this one many many times!</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Logging+Interceptor">Logging Interceptor</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Logging Interceptor The Logging Interceptor is a pretty trivial Interceptor which just logs to Jakarta Commons Logging http://jakarta.apache.org/commons/logging/ or log4j http://logging.apache.org/log4j/docs/ as messages are sent or acknowledged on a brok</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-M"></a>M</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Mailing+Lists">Mailing Lists</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The following mailing lists are available. Before posting you might want to read the Tips for getting help. Apache Mailing Lists List Name Subscribe Unsubscribe Archive Nabble (Online Forums) MarkMail (searchable via UI) ActiveMQ User List Subscribe mailt</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Manage+Durable+Subscribers">Manage Durable Subscribers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Durable topic subscribers that are offline for a long period of time are usually not desired in the system. The reason for that is that broker needs to keep all the messages sent to those topics for the said subscribers. And this message piling can over t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/MasterSlave">MasterSlave</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Introduction to Master / Slave The following are the different kinds of Master/Slave configurations available: Master Slave Type Requirements Pros Cons Shared File System Master Slave A shared file system such as a SAN Run as many slaves as required. Auto</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Maven+SNAPSHOT+Repository+in+your+POM">Maven SNAPSHOT Repository in your POM</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ In your pom.xml file you can add the Maven 2 snapshot repository if you want to try out the SNAPSHOT versions: <repository> <id>apache.snapshots</id> <name>Apache Development Snapshot Repository</name> <url>https://repository.apache.org/content/r</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Maven2+ActiveMQ+Broker+Plugin">Maven2 ActiveMQ Broker Plugin</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ provides a Maven2 plugin to easily startup a JMS broker. It is useful to quickly boot up a message broker in your Maven2 project for debugging or for doing integration tests. How to Use The maven plugins in ActiveMQ have been renamed in version </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/MDC+Logging">MDC Logging</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ uses slf4j http://www.slf4j.org/ as its logging framework. This allows ActiveMQ to support MDC logging http://www.slf4j.org/api/org/slf4j/MDC.html. For more information about about MDC logging see the logback manual http://logback.qos.ch/manual/m</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Message+Cursors">Message Cursors</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Message Cursors A common problem in previous versions of ActiveMQ was running out of RAM buffer when using non-persistent messaging. Beginning with ActiveMQ 5.0.0, there is a new memory model that allows messages to be paged in from storage when space is </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Message+Dispatching+Features">Message Dispatching Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Message+Features">Message Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Message+Groups">Message Groups</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Message Groups Message Groups are an enhancement to the Exclusive Consumer feature. They provide: Guaranteed ordering of the processing of related messages across a single queue. Load balancing of the processing of messages across multiple consumers. High</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Message+Redelivery+and+DLQ+Handling">Message Redelivery and DLQ Handling</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview Messages are redelivered to a client when any of the following occurs: A transacted session is used and rollback() is called. A transacted session is closed before commit() is called. A session is using CLIENT_ACKNOWLEDGE and Session.recover() is</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Message+Transformation">Message Transformation</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Message Transformation It is sometimes useful to transform a message inside the JMS provider. For example you may have an application that has been live for some time that uses ObjectMessage messages, but that you wish to convert to use XML payloads (to p</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Mirrored+Queues">Mirrored Queues</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Mirrored Queues Queues provide an excellent reliable and high performance load balancing mechanism. Each message placed on a queue can only be successfully processed by a single consumer. This is a good thing! . However sometimes you want to monitor what </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/MOM">MOM</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Message Orientated Middleware. The art of building distributed systems using mostly asynchronous message passing with loosely coupled services consuming and emitting messages. So this includes JMS providers and message brokers. Typically MOMs can handle a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Monitoring+ActiveMQ">Monitoring ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You can monitor ActiveMQ using the Web Console by pointing your browser at http://localhost:8161/admin http://localhost:8161/admin From ActiveMQ 5.8 onwards the web apps is secured out of the box. The default username and password is admin/admin. You can </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/MQTT">MQTT</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ supports the MQTT http://mqtt.org/ protocol and will automatically map between JMS/NMS and MQTT clients. MQTT is a machine-to-machine (M2M) publish/subscribe messaging transport. Please see the MQTT site http://mqtt.org/ for more details Enabling</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Multicast+-+Watch+out+for+IPV6+vs+IPV4+support+on+your+operating+system+or+distribution+or+network">Multicast - Watch out for IPV6 vs IPV4 support on your operating system or distribution or network</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You may wonder why you are not receiving any message at all during multicast, maybe you have just tried everything, and even on some other OS or distributions and JDK and realize that it works in some place and not on other... you may have tried a small C</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Multicast+Transport">Multicast Transport</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We could support a reliable multicast protocol and use that to distribute messages across. This page braindumps how that could fit in with ActiveMQ 4.x's architecture. each VM would have its own embedded broker; JMS connections would talk VM protocol to t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Multicast+Transport+Reference">Multicast Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Multicast Transport The Multicast transport allows clients to connect to a remote ActiveMQ broker using multicast Note that by default Multicast is not reliable; datagrams can be lost so you should add a reliability layer to ensure the JMS contract ca</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Multiple+consumers+on+a+queue">Multiple consumers on a queue</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you want to consume concurrently from a queue, then you must use a different session for each consumer. This is because you must have a session per thread. The JMS contract is that only 1 session is used by one thread at once - which if you're using co</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/My+producer+blocks">My producer blocks</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What can I do if my producer blocks sending a message? This relates to Producer Flow Control. Active 4.x In ActiveMQ 4.x, all in transit messages are held in memory. If you have a slow consumer, to avoid exausting the JVM memory and getting an out of memo</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-N"></a>N</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Navigation">Navigation</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview Index News New Features Getting Started FAQ Articles Books Download License http://www.apache.org/licenses/ Search <DIV> <FORM action="http://www.google.com/search" method="get" style="font-size: 10px;"> <INPUT name="ie" type="hidden" value="UTF-</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Networks+of+Brokers">Networks of Brokers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">To provide massive scalability of a large messaging fabric you typically want to allow many brokers to be connected together into a network so that you can have as many clients as you wish all logically connected together - and running as many message bro</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features">New Features</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features This page documents the various new features we add in each major release New Features in 6.0 New Features in 5.13 New Features in 5.11 New Features in 5.6 New Features in 5.5 New Features in 5.4 New Features in 5.2 New Features in 5.1 New Fe</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+4.1">New Features in 4.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in Apache ActiveMQ 4.1 Shared File System Master Slave JDBC Master Slave Virtual Destinations Configure Startup Destinations Structured Message Properties and MapMessages</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.0">New Features in 5.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in 5.0 In the 5.0 release of Apache ActiveMQ there are the following new features: AMQ Message Store (Faster Persistence!) Message Cursors (To handle very large number of stored messages) Blob Messages Command Agent Enterprise Integration Pat</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.1">New Features in 5.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in 5.1 In the 5.1.x release of Apache ActiveMQ there are the following new features: You can use the new DestinationSource http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/advisory/DestinationSource.html on an Active</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.11">New Features in 5.11</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in 5.11.0 Destination import/export for lock down mode AMQ-5218 https://issues.apache.org/jira/browse/AMQ-5218 Dynamic camel root loading AMQ-5351 https://issues.apache.org/jira/browse/AMQ-5351 MQTT - QOS2 mapped to virtual topics AMQ-5290 ht</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.13">New Features in 5.13</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in 5.13.0 New transport protocol, AUTO AMQ-5889 https://issues.apache.org/jira/browse/AMQ-5889 Dynamic network support for virtual consumers, Networks of Brokers AMQ-6027 https://issues.apache.org/jira/browse/AMQ-6027 Pending message size met</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.2">New Features in 5.2</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ 5.2 is primarily a maintenance release which resolves https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=11841 . New Features in 5.2 The new features and enhancements in this release include: </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.3">New Features in 5.3</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ 5.3 is primarily a maintenance release which resolves https://issues.apache.org/activemq/secure/ReleaseNote.jspa?version=11914&styleName=Html&projectId=10520 334 issues. New Features in 5.3 The new features and enhancements in this release</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.4">New Features in 5.4</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in 5.4.1 Encrypted passwords Added selector support in Ajax New Features in 5.4 Delay and Schedule Message Delivery Message Priority WebSockets Better OSGi support Broker side options for updating failover clients automatically of new brokers</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.5">New Features in 5.5</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in 5.5.0 Dependency on Java 1.6 (java 1.5 is no longer supported) MDC logging (SLF4J http://slf4j.org/) Upgrade to camel 2.7.0 DLQ processing per durable subscription New network connector MBeans IOExceptionHandler http://activemq.apache.org/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.6">New Features in 5.6</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">New Features in 5.6.0 LevelDB Store MQTT transport New LDAP security module Stomp 1.1 support stomp+nio+ssl transport Multi KahaDB persistence Priority Failover URIs Automatic client rebalance in broker cluster</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.7">New Features in 5.7</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Java 7 support (compiled with jdk6 and validated with jdk7) Secure WebSockets (wss) transport http://activemq.apache.org/websockets.html#WebSockets-SecureWebSockets Broker Based Redelivery http://activemq.apache.org/message-redelivery-and-dlq-handling.htm</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.8">New Features in 5.8</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">AMQP new feature modules and activemq-client module allowing smaller foorprint management via REST with jolokia http://www.jolokia.org/ jmx to http bridge Includes Apache Camel 2.10.3 http://camel.apache.org/camel-2103-release.html Java 7 support (compile</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+5.9">New Features in 5.9</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Replicated LevelDB Store for shared nothing Master/Slave. Runtime Configuration Generic JMS XA connection pool in activemq-jms-pool module (has no ActiveMQ dependency) MQTT over WebSockets support broker Apache Camel component Broker auto-restart upon los</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/New+Features+in+6.0">New Features in 6.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">At one point, if you were interested in Version 6, you could take a look at Apollo subproject http://activemq.apache.org/apollo/ as it was expected to be the core of the 6.0 broker. However, as of July 2015, Apollo is being unofficially declared dead. T</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/News">News</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/NIO+Transport+Reference">NIO Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">NIO Transport is very similar to the regular TCP transport. The difference is that it is implemented using NIO API which can help with performance and scalability. NIO is a server side transport option only. Trying to use it on the client side will instan</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/No+suitable+driver">No suitable driver</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Symptoms I get an exception saying No suitable driver when initialising the JDBC driver. Reason ActiveMQ tries to auto-detect the JDBC driver so that it can deduce the ultimate database's SQL dialect. Some JDBC drivers are not yet auto-recognised. Here's </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/NoClassDefFoundError+-+org.springframework.core.io.Resource">NoClassDefFoundError - org.springframework.core.io.Resource</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If you get an exception like this java.lang.NoClassDefFoundError - org/springframework/core/io/Resource Cause You were probably trying to use the XML Configuration mechanism, which uses Spring, but without having the Spring jar on your classpath. Solution</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-O"></a>O</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ObjectMessage">ObjectMessage</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Although ObjectMessage usage is generally discouraged, as it introduces coupling of class paths between producers and consumers, ActiveMQ supports them as part of the JMS specification. Security ObjectMessage objects depend on Java serialization of marsha</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Old+OSGi+Integration">Old OSGi Integration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This article applies to versions of ActiveMQ prior to 5.4.0. If you use version 5.4.0 or newer proceed to the following article. Introduction All ActiveMQ modules are packaged as OSGi bundles and can be used in any OSGi container. This article will provid</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/onMessage+method+of+MessageListener+is+never+called">onMessage method of MessageListener is never called</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">See I am not receiving any messages, what is wrong</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/OpenWire">OpenWire</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">OpenWire is our cross language Wire Protocol to allow native access to ActiveMQ from a number of different languages and platforms. The Java OpenWire transport is the default transport in ActiveMQ 4.x or later. For other languages see the following... NMS</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/OpenWire+C+Client">OpenWire C Client</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This is the C library which is based on the OpenWire protocol. You can browse the code here http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/ http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/ e.g. here's an example of it in use... ht</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/OpenWire+CPP+Client">OpenWire CPP Client</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">OpenWire C++ Client Goals We want to be able to provide a C++ API to ActiveMQ that retains rough feature-parity with the Java API while at the same time allowing for more flexibility in application design by opening up lower levels of the event system. We</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/OpenWire+Version+2+Specification">OpenWire Version 2 Specification</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This article references OpenWire V2 which is no longer the latest version. The formatting and encoding rules in this article are still valid for later OpenWire versions, but later versions define additional fields in the OpenWire commands. The default set</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Optimized+Acknowledgement">Optimized Acknowledgement</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Overview ActiveMQ supports acknowledging a range of messages in a single batch operations. This option is disabled by default but can be used to improve throughput in some circumstances as it decreases load on the broker. Consider enabling it for your per</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/OSGi+Integration">OSGi Integration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Introduction This article will provide more details on how to use ActiveMQ in Apache Karaf http://karaf.apache.org/, small OSGi based runtime. Apache Karaf was previously know as ServiceMix kernel, so informations found here are applicable to Apache Servi</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="osgi-support-in-development.xml">OSGi support (in development)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Split packages (2015-11-17) Package Modules org/apache/activemq/artemis/uri artemis-core-client artemis-jms-client artemis-server org/apache/activemq/artemis/core/protocol/core/impl/wireformat artemis-core-client artemis-server org/apache/activemq/artemis</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Outbound+Communication">Outbound Communication</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuring a Session Bean to send messages to ActiveMQ In the attached example application, the three MDBs use the SenderEJB to send JMS messages to an ActiveMQ queue. In this example, I will be explaining how to: Configure and deploy an ActiveMQ Queue t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Overview">Overview</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-P"></a>P</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Peer+Transport+Reference">Peer Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Peer Transport The Peer transport provides a peer-to-peer network with ActiveMQ. What actually happens is the peer transport uses the VM transport to create and connect to a local embedded broker but which configures the embedded broker to establish n</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Per+Destination+Policies">Per Destination Policies</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Multiple different policies can be applied per destination (queue or topic), or using wildcard notation to apply to a hierarchy of queues or topics, making it possible, therefore, to configure how different regions of the JMS destination space are handled</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Performance">Performance</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Performance Performance differs greatly depending on many different factors the network topology transport protocols used quality of service hardware, network, JVM and operating system number of producers, number of consumers distribution of messages acro</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Performance+report">Performance report</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Performance guides If you're not convinced by performance reports then please do try running performance tests yourself. You might wanna check out our overview of Performance or try using out the ActiveMQ Performance Module Users Manual The Commercial Pro</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Performance+Tuning">Performance Tuning</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For a more complete overview see Performance. There are trade-offs between performance and reliability. By default, ActiveMQ strikes a balance between the two, so there are some things you can change to increase throughput. Async Publishing First some bac</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Periodically+checking+disk+limits">Periodically checking disk limits</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Store and temporary disk limits are set for the Broker on startup based on configuration and available space. Sometimes other processes (such as logs) can grow and reduce the available disk space enough that the limits detected at start up no longer have </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Persistence">Persistence</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ V5.9 In ActiveMQ 5.9, the Replicated LevelDB Store is introduced. It handles using Apache ZooKeeper http://zookeeper.apache.org/ to pick a master from a set of broker nodes configured to replicate single LevelDB Store. Then synchronizes all slave</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Persistence+Questions">Persistence Questions</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Questions relating to long term persistence of messages.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Pluggable+storage+lockers">Pluggable storage lockers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">As of the 5.7.0 release of ActiveMQ the choice of storage locking mechanism, as used by a persistence adapter, has been made pluggable. This feature is only meaningful to brokers configured in a shared storage master/slave topology. Prior to release 5.7.0</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/PMC+Templates">PMC Templates</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The following email templates are for use by the ActiveMQ PMC: Committer Discussion To: private@activemq.apache.org mailto:private@activemq.apache.orgSubject: [DISCUSS] Invite <CANDIDATE> to become an ActiveMQ committer Considering <CANDIDATE>’s contribu</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Privacy+Policy">Privacy Policy</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Information about your use of this website is collected using server access logs and a tracking cookie. The collected information consists of the following: The IP address from which you access the website; The type of browser and operating system you use</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Producer+Flow+Control">Producer Flow Control</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Producer Flow Control In ActiveMQ 4.x flow control was implemented using TCP flow control. The underlying network connection of throttled consumers was suspended to enforce flow control limits. This strategy is very efficient but can lead to deadlocks if </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Projects+Using+ActiveMQ">Projects Using ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache Camel http://activemq.apache.org/camel/ is a POJO based routing and mediation framework Apache CXF http://incubator.apache.org/cxf/ is a JAX-WS client and web services framework Apache Geronimo http://geronimo.apache.org/ is the J2EE server project</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Proposed+C+Client+Architecture">Proposed C Client Architecture</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">4/16/06 - Attaching wire_formats.pdf - a first cut at defining all of the commands for both openwire an stomp. Working toward an architecture that will support both. /////////////////////////////////////////////// Given that there are several separate </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Protocols">Protocols</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ is a message broker which supports multiple wire level protocols for maximum interoperability.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Pure+Master+Slave">Pure Master Slave</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Pure Master Slave This feature will be removed in 5.8 as it has not evolved to be production ready. You are advised to use shared storage master/slave or the Replicated LevelDB Store. See AMQ-4165 https://issues.apache.org/jira/browse/AMQ-4165 A Pure Mast</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Q"></a>Q</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/QoS">QoS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">QoS is a MOM abbreviation of the term Quality of Service. There are many different kinds of messaging with different qualities of service such as topics versus queues durable messaging versus reliable (some buffering takes place but if a consumer is down </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/QuickLinks">QuickLinks</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Download | JavaDocs http://activemq.apache.org/maven/apidocs/index.html More... | Source | Forums | Support</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-R"></a>R</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Redelivery+Policy">Redelivery Policy</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Redelivery Policy Detail on when messages are redelivered to a client can be found in the Message Redelivery and DLQ Handling section. You can configure the RedeliveryPolicy http://svn.apache.org/viewvc/activemq/trunk/activemq-client/src/main/java/org/apa</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Release+Guide">Release Guide</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How to create and announce an ActiveMQ release. This release is based on General guide for releasing Maven-based project at Apache http://maven.apache.org/developers/release/apache-release.html, so be sure to check it out before continuing and meet all pr</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Release+Info">Release Info</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">General Release Information Current RoadMap http://jira.activemq.org/jira/browse/AMQ?report=com.atlassian.jira.plugin.system.project:roadmap-panel Release Guide Signing Releases http://wiki.apache.org/incubator/SigningReleases Apache Mirror Guidelines htt</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Release+Plans">Release Plans</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Information Release Info How you can help release Release Plans 4.0 RC 1 Guide</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Replicated+LevelDB+Store">Replicated LevelDB Store</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The LevelDB store has been deprecated and is no longer supported or recommended for use. The recommended store is KahaDB Synopsis The Replicated LevelDB Store uses Apache ZooKeeper to pick a master from a set of broker nodes configured to replicate a Leve</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Replicated+Message+Store">Replicated Message Store</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If messages are stored on the hard drive of a broker or inside a single database; then you have a single point of failure with respect to the message persistence. If you lose the entire machine, disk or database, you have lost messages. For some high end </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Resource+Adapter">Resource Adapter</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Introduction ActiveMQ includes a Java Connector Architecture (JCA) 1.5 Resource Adapter. JCA 1.5 defines the contract between an J2EE application server and external resources such as databases and messaging middleware. It allows the application server to</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Resource+Adapter+does+not+seem+to+pool+connections">Resource Adapter does not seem to pool connections</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">It may seem like the resource adapter when used in an app server like geronimo or jboss is not pooling connections. Looking the the ActiveMQ broker logs, it will show multiple message for each use of a pooled conntion simlilar to: 16:43:07 INFO Adding new</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Resource+Adapter+Properties">Resource Adapter Properties</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The ActiveMQ Resource Adapter allows you to configure several properties that: sets the options used for connection used for inbound message delivery sets the default options used for the outbound connection factory objects. The properties that can be con</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/REST">REST</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ implements a RESTful API to messaging which allows any web capable device to publish or consume messages using a regular HTTP POST or GET. If you are interested in messaging directly from web browsers you might wanna check out our Ajax or WebSock</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/REST+protocols">REST protocols</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are many ways to map JMS to REST... Crappy non-REST Send via POST /queue/Destination Consume GET /queue/Destination This is bad as the GET is not idempotent. We can add a user ID or use a cookie GET /queue/Destination?jsessionId=.... though a cachin</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/RESTful+Queue">RESTful Queue</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">RESTful Queue This document is intended to document the ideal RESTful interface to message queues in light of the discussion on rest-discuss http://tech.groups.yahoo.com/group/rest-discuss/message/8955 Atom Publishing Protocol http://bitworking.org/projec</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Retroactive+Consumer">Retroactive Consumer</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Background A retroactive consumer is just a regular JMS Topic consumer who indicates that at the start of a subscription every attempt should be used to go back in time and send any old messages (or the last message sent on that topic) that the consumer m</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/RSS+and+Atom">RSS and Atom</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We have added support for the RESTful browsing of message queues in the activemq-web module. To try out this feature try the Web Samples. Browsing of queues is implemented by a servlet, QueueBrowseServlet which allows queues to be browsed using pluggable </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Run+Broker">Run Broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Running an ActiveMQ Broker Note if you want to use an embedded broker then see How do I embed a Broker inside a Connection This page describes how to run a broker using 4.x or later of ActiveMQ. Running the broker as a Unix Service See the Unix Shell Scr</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Runtime+Configuration">Runtime Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">From version 5.9.0 a new broker plugin will allow selective changes to a broker xml configuration to take effect without broker restart. Consider a retail environment where there are central processors (hubs) and stores(spokes). It is advantageous to be a</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-S"></a>S</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Sample+Camel+Routes">Sample Camel Routes</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Example of a configuration that show how to use Camel routes with Juel and Xpath. <beans> <!-- Allows us to use system properties as variables in this configuration file --> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigur</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/sample+report">sample report</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Performance Test Report Template <testResult> <property name='systemSettings'> <props> <prop key='java.runtime.name'>Java(TM) 2 Runtime Environment, Standard Edition</prop> <prop key='java.vm.version'>1.4.2_10-b03</prop> . . . <prop key='os.arch'>x86</pro</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Sandbox">Sandbox</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Scaling+Queues">Scaling Queues</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Scaling to tens of thousands of Queues in a single broker is relatively straightforward - but requires some configuration changes from the default. Reducing Threads With the default configuration, ActiveMQ is configured to use a dispatch thread per Queue </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Scaling+the+Depth+of+a+Queue">Scaling the Depth of a Queue</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Nearly all messaging systems (certainly open source ones) hold either a copy of a persistent message or a reference to a persisted message in memory. This is primarily to try and improve performance, but it also can significantly decrease the complexity o</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Security">Security</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ 4.x and greater provides pluggable security through various different providers. The most common providers are JAAS http://java.sun.com/products/jaas/ for authentication a default authorization mechanism using a simple XML configuration file. Aut</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Security+Advisories">Security Advisories</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache ActiveMQ 2017 CVE-2015-7559 - DoS in client via shutdown command 2016 CVE-2016-6810 - ActiveMQ Web Console - Cross-Site Scripting CVE-2016-0734 - ActiveMQ Web Console - Clickjacking CVE-2016-0782 - ActiveMQ Web Console - Cross-Site Scripting CVE-20</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/SEDA">SEDA</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Staged Event Driven Architecture which is a design pattern for building high performance and scalable distributed systems. See this paper http://www.eecs.harvard.edu/~mdw/proj/seda/ for more details.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Selectors">Selectors</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JMS Selectors Selectors are a way of attaching a filter to a subscription to perform content based routing. Selectors are defined using SQL 92 syntax and typically apply to message headers; whether the standard properties available on a JMS message or cus</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Setting+up+ActiveMQ+with+Tomcat+5.5.9">Setting up ActiveMQ with Tomcat 5.5.9</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Create the file <webapp-root>/META-INF/context.xml. Here is an example: <Context antiJARLocking="true"> <Resource name="jms/ConnectionFactory" auth="Container" type="org.apache.activemq.ActiveMQConnectionFactory" description="JMS Connection Factory" facto</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Shared+File+System+Master+Slave">Shared File System Master Slave</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Shared File System Master Slave If you have a SAN or shared file system it can be used to provide high availability such that if a broker is killed, another broker can take over immediately. Note that the requirements of this failover system are a distrib</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Shiro">Shiro</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"> ActiveMQ 5.10 and later provides a fully customizable security experience using Apache Shiro http://shiro.apache.org. The ActiveMQ Shiro plugin can secure the ActiveMQ broker, from authenticating transport connections to authorizing behavior with topics</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Should+I+deploy+Enterprise+Integration+Patterns+in+the+broker+or+another+application">Should I deploy Enterprise Integration Patterns in the broker or another application</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Should I deploy Enterprise Integration Patterns in the broker or another application Whether you deploy the Enterprise Integration Patterns inside the ActiveMQ Broker or in a separate application depends on your requirements. Advantages of deploying EIP i</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Should+I+deploy+the+broker+inside+my+JVM+or+AppServer">Should I deploy the broker inside my JVM or AppServer</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You can deploy the ActiveMQ Broker inside your JVM or Application Server. Whether you do or not has pros and cons depending on how many JVMs you have and what your backup & recovery policy is. Advantages of embedding the broker embedding a broker means yo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Should+I+run+ActiveMQ+on+Windows+in+a+directory+with+spaces">Should I run ActiveMQ on Windows in a directory with spaces</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Should I run ActiveMQ on Windows in a directory with spaces No. Its not a good idea to install and run application in paths on Windows which have spaces.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Should+I+use+transactions">Should I use transactions</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are four main approaches as to a client can consume messages. They are: Auto-acknowledgement Explicit acknowledgement via Message.acknowledge() JMS Transactions XA For a discussion on XA see: Should I use XA The main difference between 1 & 2 and 3 &</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Should+I+use+XA">Should I use XA</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Should I use XA transactions (two phase commit?) A common use of JMS is to consume messages from a queue or topic, process them using a database or EJB, then acknowledge / commit the message. If you are using more than one resource; e.g. reading a JMS mes</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Site">Site</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/SiteIndex">SiteIndex</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">{index}{index}</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/SiteMap">SiteMap</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Using ActiveMQ Using ActiveMQ Community Community Overview Overview Features Features Connectivity Connectivity Tools Tools Developers Developers Site Site</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/SJSAS+with+GenericJMSRA">SJSAS with GenericJMSRA</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Using ActiveMQ, Generic JMS RA and SJSAS (Glassfish) This document is my notes on making ActiveMQ and SJSAS work together using GenericJMSRA. The objectives is to make ActiveMQ as the JMS provider and MDB can be deployed in SJSAS, listening messages from </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Slow+Consumer+Handling">Slow Consumer Handling</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Slow Consumers can cause problems on non-durable topics since they can force the broker to keep old messages in RAM which once it fills up, forces the broker to slow down producers, causing the fast consumers to be slowed down. One option we could impleme</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Slow+Consumers">Slow Consumers</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Blocked Transport when using TCP there can be occasions when a network outage can result in a blocked write. This can cause the entire broker to freeze - and the socket may never be unblocked. Currently we have a Thread that checks for blocked sockets - u</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Slow+networks+drop+large+messages">Slow networks drop large messages</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This article only applies to older versions of ActiveMQ, i.e. 5.3 and 5.4.0. From 5.4.2 onwards this issue has been adressed in the bugs AMQ-2511 https://issues.apache.org/jira/browse/AMQ-2511 and AMQ-2088 https://issues.apache.org/jira/browse/AMQ-2088. Y</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Source">Source</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ 5 Web Browsing of the git Repo To browse via the web: https://git-wip-us.apache.org/repos/asf?p=activemq.git https://git-wip-us.apache.org/repos/asf?p=activemq.git Checking out from the git Repo git clone https://git-wip-us.apache.org/repos/asf/a</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Source+XRef">Source XRef</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ Core http://activemq.apache.org/maven/activemq-core/xref/ ActiveMQ Resource Adapter http://activemq.apache.org/maven/activemq-ra/xref/ ActiveMQ Web http://activemq.apache.org/maven/activemq-web/xref/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Sponsorship">Sponsorship</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Thank you to all the folks http://www.apache.org/foundation/thanks.html who have sponsored http://www.apache.org/foundation/sponsorship.html the Apache Software Foundation. Want to help sponsor the foundation? Click here for more info http://www.apache.or</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Spring+Support">Spring Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We fully support Spring for configuration of the JMS client side as well as for configuring the JMS Message Broker. There is a great article http://codedependents.com/2009/10/16/efficient-lightweight-jms-with-spring-and-activemq/ on using Spring with Acti</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/SQLServer">SQLServer</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">SQL Server SQL Server 2000 Drivers Here is an example of a configuration for SQLServer kindly supplied by Ning Li <persistenceAdapter> <journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data" dataSource="#mssql-ds"> <adapter><imageBasedJDBCAda</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/SSL+Transport+Reference">SSL Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The SSL Transport The SSL transport allows clients to connect to a remote ActiveMQ broker using SSL over a TCP socket. Configuration Syntax ssl://hostname:port?transportOptions Transport Options The configuration options from TCP are relevant. Example URI</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Static+Transport+Reference">Static Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Static Transport The static transport provides a hard coded mechanism to discover other connections using a list of URIs. A connection using this discovery mechanism will attempt to connect to all URIs in the list until it is succesful. Configuration </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/StatisticsPlugin">StatisticsPlugin</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Beginning in ActiveMQ 5.3, a statistics plugin is included that can be used to retrieve statistics from the broker or its destinations. Note that the message must contain a replyTo header (the jmsReplyTo header if you're using JMS) else the message will b</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Stomp">Stomp</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ supports the Stomp http://stomp.github.com/ protocol and the Stomp - JMS mapping. This makes it easy to write a client in pure Ruby, Perl, Python or PHP for working with ActiveMQ. Please see the Stomp site http://stomp.github.io/ for more details</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Structured+Message+Properties+and+MapMessages">Structured Message Properties and MapMessages</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Structured Message Properties and MapMessages This JMS extension feature allows you to attach Map and List properties to any JMS Message or to use nested Maps and Lists inside a MapMessage. This allows you to efficiently send typesafe structured informati</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Subscription+Recovery+Policy">Subscription Recovery Policy</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The subscription recovery policy allows you to go back in time when you subscribe to a topic. For example imagine you are processing a price feed; you're using a federated network and either a network glitch occurs or someone kills the broker you're talki</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Sun+JNDI">Sun JNDI</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">here's an example jndi.properties file: java.naming.factory.initial = com.sun.jndi.fscontext.RefFSContextFactory Here's an example .bindind file: For ActiveMQ 4.x its Archive/ClassName=org.apache.activemq.command.ActiveMQQueue Archive/FactoryName=org.apac</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Support">Support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Getting Help If you are experiencing problems using ActiveMQ then please report your problem to our Issue Tracker http://issues.apache.org/activemq/browse/AMQ. You may also find it useful to discuss your issues with the community on the Discussion Forums </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Supporting+IO+Streams">Supporting IO Streams</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">It'd be great to offer kick ass support for streaming files over ActiveMQ of any arbitrary size. The basic idea is to fragment the stream into multiple messages and send/receive those over JMS. There are a few issues to consider... Use casess many produce</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/SVN">SVN</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Source</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Sybase">Sybase</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Sybase A dataSource targetting a Sybase ASE database can be configured as follows: <bean id="sybase-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close"> <!-- using jConnect --> <property name="driverClassName" value="com.sybase.jdbc</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-T"></a>T</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/TCP+Transport+Reference">TCP Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The TCP Transport The TCP transport allows clients to connect to a remote ActiveMQ broker using a TCP socket. These configuration options can be used to tune the underlying TCP transport on either the client-side using the JMS client's connection URI stri</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Team">Team</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ Community This page lists who we are. By all means add yourself to the list - lets sort it in alphabetical order Committers "A committer is a developer that was given write access to the code repository and has a signed Contributor License Agreem</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Terminology">Terminology</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Questions on Message Orientated Middleware and ActiveMQ terminology Store and Forward brokers receive messages, store them locally and forwards the message to a recipient (in this case another broker) when it is able to do so. The message is only deleted </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Test+Source+XRef">Test Source XRef</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ Resource Adapter http://activemq.codehaus.org/maven/activemq-ra/xref-test/ ActiveMQ Web http://activemq.codehaus.org/maven/activemq-web/xref-test/</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Thanks">Thanks</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ is a successful project because of the large and diverse community that contributes to it. There are a handful of tools that developers in the community use; some are open-source and some are commercial. We'd like to extend a special thanks to t</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/The+ActiveBlaze+Message+type">The ActiveBlaze Message type</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The foundation of message and event parsing in ActiveBlaze is the BlazeMessage. A BlazeMessage is a a Map of key value pairs, where the keys are strings and the values are primitive objects. The values supported are: byte bytes[] char short int long float</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/The+Broker+will+not+start">The Broker will not start</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">It's been reported that during broker start some users get a message similar to: 15:26:29 INFO Opening journal. Caught: javax.jms.JMSException: Failed to open transaction journal: java.io.IOException: Invalid argument It could be this problem or the probl</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/The+JMS+Connector">The JMS Connector</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">JMS to JMS Bridge</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/The+Proxy+Connector">The Proxy Connector</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Proxy Connector Many of the more advanced ActiveMQ features are implemented in the transports. Sometimes it's desirable to accept one kind of ActiveMQ connection and establish a different kind of connection to another broker. The Proxy Connector allow</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/The+vm+transport+starts+a+broker+before+my+configured+broker+starts">The vm transport starts a broker before my configured broker starts</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Scenario You are using the vm: transport and a broker is auto-started for you so that your configured embedded broker doesn't start. Solution Its most likely a dependency issue; your JMS connection is starting before your embedded broker. So just make sur</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Throughput">Throughput</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">How many messages can we process per second. Normally MOM style applications focus on asynchronous messaging and SEDA style architectures which aim for massive throughput numbers at the cost of some Latency</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/TimeStampPlugin">TimeStampPlugin</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The TimeStampPlugin is a Broker interceptor which updates a JMS Client's time stamp on the message with a broker time stamp. This can be useful when the clocks on client machines are known to not be correct and you can only trust the time set on the broke</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Tips+for+getting+help">Tips for getting help</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We are a community based open source project and we really welcome and value your Contributions. We have various ways of getting help via the Discussion Forums or Mailing Lists. Here are a few tips to help us to help you which version of ActiveMQ are you </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Tomcat">Tomcat</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Configuration issues for Tomcat 7 and later Tomcat needs to be configured to ignore Jetty SCI annotations so that the Jetty WebSocket ServerContainerInitializer class is not inadvertently picked up by Tomcat. For more information on this problem see AMQ-6</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/TomEE">TomEE</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Apache TomEE is a distribution of Tomcat with fully integrated ActiveMQ offering full JMS support to plain war files, Servlets and more. No setup is required and code like the following will work out of the box. import javax.annotation.Resource; import ja</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Tools">Tools</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Topologies">Topologies</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ supports a wide range of different deployment topologies as well as protocols & wire formats. The following diagram shows a federated network of brokers with a few different kinds of topology. BrokerTopology-1.png http://activemq.org/BrokerTopolo</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Total+Ordering">Total Ordering</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Sometimes it can be useful to ensure that every topic consumer sees messages arriving on the topic in exactly the same order. Normally the broker will guarantee the order of all messages sent by the same producer. However, owing to the broker's use of mul</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-U"></a>U</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/UDP+Transport+Reference">UDP Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The UDP Transport The UDP transport allows clients to connect to a remote ActiveMQ broker using raw UDP Note that by default UDP is not reliable; datagrams can be lost so you should add a reliability layer to ensure the JMS contract can be implemented on </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Unix">Unix</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page contains resources that will make you adapt ActiveMQ to your Unix-based operating system.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Unix+Service">Unix Service</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page contained a very basic procedure to create a unix service for activemq. Due to the fact that ActiveMQ contains a very functional init script - this is not needed anymore. Review the documentation of the init script: Unix Shell Script</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Unix+Shell+Script">Unix Shell Script</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Functional overview From version 5.4.0 onwards, ActiveMQ comes with a enhanced shell script for starting, stopping and managing the broker in Unix environment. For basic activemq and activemq-admin scripts functionality take a look at ActiveMQ Command Lin</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/URI+Protocols">URI Protocols</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ is designed to support mutliple different topologies and protocols. Which one you use depends on your messaging requirements, quality of service and network topology. The following table describes the different network protocols available for JMS</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Use+Cases">Use Cases</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Messaging is a diverse and wide ranging subject - there are many different use cases, requirements and deployment options. This is one of the reasons why its so interesting to work on This document tries to highlight some of the main use cases we are tryi</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/User+Forum">User Forum</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px"><a id="nabblelink" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html">ActiveMQ - User</a> <script src="http://activemq.2283324.n4.nabble.com/embed/f2341805"></script></div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/User+Submitted+Configurations">User Submitted Configurations</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Please add any configurations of ActiveMQ you wish to share with other users here... Complex Single Broker Configuration (STOMP only) - Example of an ActiveMQ configuration with predefined queues, simple destination security. JMS and JDBC operations in on</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Users">Users</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page contains a list of some of our users and gives a brief overview of how they are using ActiveMQ. The purpose of this page is to help the ActiveMQ community get to know each other & find out what we're all doing with ActiveMQ and for the developer</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Using+ActiveMQ">Using ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Using Apache ActiveMQ To help you get started using Apache ActiveMQ you may wish to start off with the Getting Started guide or the Configuring Transports. Otherwise here is a complete list of the guides.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Using+ActiveMQ+5">Using ActiveMQ 5</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Using Apache ActiveMQ To help you get started using Apache ActiveMQ version 5 you may wish to start off with the Version 5 Getting Started guide or the Configuring version 5 Transports. Otherwise here is a complete list of the guides. Commercial Documenta</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="using-activemq-with-ejb3-jboss-example.xml">Using ActiveMQ with EJB3 (JBoss Example)</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">I've seen numerous postings regarding ActiveMQ with EJB3, and variations of a datasource XML file for use with JBoss integration. However, they don't quite work. Here is what worked for me, it is actually quite simple: 1. Don't use any datasource file - o</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Using+Apache+ActiveMQ">Using Apache ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Questions on using Apache ActiveMQ</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-V"></a>V</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Verify+Downloads">Verify Downloads</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Verify the Integrity of Downloads It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps: Download the KEYS http://www.apac</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Examples">Version 5 Examples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Since version 5.12.0, Apache ActiveMQ comes with the new tool that can be used to produce and consume messages from the broker. Prerequisites Before running the examples you should try running a JMS broker on your machine. Follow the Installation instru</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Getting+Started">Version 5 Getting Started</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Introduction This document describes how to install and configure ActiveMQ for both Unix and Windows' platforms. Document Organization The Getting Started Guide for ActiveMQ contains the following sections: Pre-Installation Requirements Hardware: 60 MB of</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Hello+World">Version 5 Hello World</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Hello World</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Initial+Configuration">Version 5 Initial Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Document Organization Firstly you need to add the jars to your classpath. Required JARs To make ActiveMQ easy to use, the default activemq-all.jar comes complete with all the libraries required. If you prefer to have explicit control over all the jars use</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Installation">Version 5 Installation</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Installation</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Performance+Tuning">Version 5 Performance Tuning</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For a more complete overview see Performance. There are trade-offs between performance and reliabilty. By default, activemq strikes a balance between the two, so there are some things you can change to increase throughput. Async publishing First some back</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Run+Broker">Version 5 Run Broker</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Running an ActiveMQ Broker Note if you want to use an embedded broker then see How do I embed a Broker inside a Connection The binary distribution of ActiveMQ comes with a script called 'activemq' which allows you to run a broker. For details regarding th</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Topologies">Version 5 Topologies</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Topologies</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+Web+Samples">Version 5 Web Samples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are a few example programs demonstrating the REST messaging or Ajax in the activemq/activemq-web-demo https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/ module. Running the Web Samples We have integrated the Web Samples into the bina</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Version+5+XML+Configuration">Version 5 XML Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">transport connectors which consist of transport channels and wire formats TODO: add a link to a page explaining what transport connectors are how to configure and use them. network connectors using network channels or discovery TODO: add a link to a page </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Virtual+Destinations">Virtual Destinations</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Virtual Destinations allow us to create logical destinations that clients can use to produce and consume from but which map onto one or more physical destinations. It allows us to provide more flexible loosely coupled messaging configurations. Virtual Top</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Visualisation">Visualisation</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Inspired greatly by Gregor and Erik's great talk at TSSJS 2006 http://www.enterpriseintegrationpatterns.com/talks.html we've started to add some visualisation plugins into Apache ActiveMQ. Connection visualisation There is a <connectionDotFilePlugin/> bro</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Visualisation+Wish+List">Visualisation Wish List</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are a zillion different things we could do to visualise the system. Lets use this page to braindump ideas for what kinds of visualisations we could do show visually the popularity of certain destinations; using size/color/position/stats to indicate </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/VM+Protocol">VM Protocol</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Protocol syntax : vm://logicalname Javadocs : org.codehaus.activemq.transport.vm http://activemq.codehaus.org/maven/apidocs/org/codehaus/activemq/transport/vm/package-frame.html The VM protocol allows clients to connect to each other inside the VM without</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/VM+Transport+Reference">VM Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The VM Transport The VM transport allows clients to connect to each other inside the VM without the overhead of the network communication. The connection used is not a socket connection but use direct method invocations which enables a high performance em</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-W"></a>W</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Web+Console">Web Console</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The ActiveMQ Web Console is a web based administration tool for working with ActiveMQ. When used with the JMX support it can be an invaluable tool for working with ActiveMQ Running the Web Console on ActiveMQ 5.0 or later We have integrated the Web Consol</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Web+Samples">Web Samples</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">There are a few example programs demonstrating the REST, Ajax and WebSockets messaging that comes with the ActiveMQ distribution. Up until version 5.8 web demos were included in the default configuration and could be accessed directly using http://localho</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/WebLogic+Integration">WebLogic Integration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ WebLogic Integration ActiveMQ clients and brokers can be run in WebLogic Server or WebLogic Express. This is usually done for licensing reasons: WebLogic Server includes JMS client and server features, but it may cost extra to use these JMS featu</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/WebSockets">WebSockets</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Introduction Besides Ajax API, starting with version 5.4.0 onwards, you can use HTML5 WebSockets http://dev.w3.org/html5/websockets/ to exchange messages with the broker from your browser. HTML 5 introduced web sockets, as a standardized way to communicat</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+are+administered+objects">What are administered objects</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What are administered objects? Administered objects refers to objects that are configured in JNDI and then accessed by a JMS client. So they are simply client-side objects typically either a ConnectionFactory or a Destination (such as a Queue or Topic). N</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+are+those+topics+ActiveMQ.Advisory">What are those topics ActiveMQ.Advisory</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">When you look at a broker using JMX you will see a number of topics starting with ActiveMQ.Advisory.. These are the destinations used by the Advisory Message feature of ActiveMQ which allows you to listen to the behaviour of the system.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+happens+when+the+journal+size+is+exceeded">What happens when the journal size is exceeded</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">If the "preferred" size is exceeded then the last log files keeps growing until the first log files can be overwritten. When a log file is overwritten, it's size is reset to the "preferred" size.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+happens+with+a+fast+producer+and+slow+consumer">What happens with a fast producer and slow consumer</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">It depends a little on the QoS but in general we implement flow control which means that when we have a very fast producer and a slow consumer, when we get to a high water mark of outstanding messages we will start to tell the producer to slow down (which</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+is+ActiveMQ">What is ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ is an open sourced implementation of JMS 1.1 as part of the J2EE 1.4 specification.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+is+the+difference+between+a+Virtual+Topic+and+a+Composite+Destination">What is the difference between a Virtual Topic and a Composite Destination</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What is the difference between a Virtual Topic and a Composite Destination Both kinds of Virtual Destinations offer similar capabilities, namely that the producer sees a single Destination to send to and the consumer sees a different Destination to consum</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+is+the+difference+between+discovery%2C+multicast+and+zeroconf">What is the difference between discovery, multicast and zeroconf</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Discovery refers to either a client (producer or consumer) establishing a 'transport connector' to the broker or a broker establishing 'network connector' to another broker without explicit static configuration of broker (IP or hostname). The scheme 'mult</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+is+the+difference+between+persistent+and+non-persistent+delivery">What is the difference between persistent and non-persistent delivery</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What is the difference between persistent and non-persistent delivery? ActiveMQ supports both persistent and non-persistent delivery. As per the JMS specification, the default delivery mode is persistent. The persistence flag is set on the MessageProducer</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+is+the+license">What is the license</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What is the license? This software is open source using the Apache 2.0 licence http://www.apache.org/licenses/LICENSE-2.0.html (a liberal BSD style license which is very commercial friendly)</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="what-is-the-prefetch-limit-for.xml">What is the Prefetch Limit For?</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">One of the design goals of ActiveMQ is to be a highly performant message bus. This means using a SEDA architecture to perform as much work as possible asynchronously. To make efficient use of network resources the broker utilizes a 'push' model to dispatc</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+jars+do+I+need">What jars do I need</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What jars do I need The basic jars you need to use are described on the Initial Configuration page.</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+open+source+integration+solution+works+best+with+ActiveMQ">What open source integration solution works best with ActiveMQ</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Apache Camel http://camel.apache.org project has been designed to work easily with ActiveMQ - and comes embedded http://activemq.apache.org/camel/how-does-camel-work-with-activemq.html in both the clients and the broker from ActiveMQ 5.0 onwards. Apac</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+platforms+does+ActiveMQ+support">What platforms does ActiveMQ support</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">What platforms does ActiveMQ Support? ActiveMQ 5.0-5.7 supports any Java platform of Java 5.0 or later. To run on 1.4 see these instructions. ActiveMQ 5.8-5.10 require Java 6 or higher and the releases from 5.11 onwards require Java 7 or later. ActiveMQ </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/What+version+should+I+use">What version should I use</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ version numbers follow the MAJOR.MINOR.PATCH convention used by many software projects. In general, patch releases are done only when there are significant enough bugs found in the current minor version to justify a release sooner than the next </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/While+posting+large+binary+file+to+activeMQ%2C+is+there+a+way+to+measure+its+progress">While posting large binary file to activeMQ, is there a way to measure its progress</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">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 in</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Why+do+I+not+get+all+of+the+messages+I+sent">Why do I not get all of the messages I sent</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">For ActiveMQ 3.x/4.x As Matt reported http://forums.logicblaze.com/posts/list/0/14.page#37 its possible that there is a race condition in your application; are you sure you had created your consumer and called start() on the JMS Connection before the prod</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Why+do+I+not+receive+messages+on+my+durable+topic+subscription">Why do I not receive messages on my durable topic subscription</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">You follow these steps Create a durable topic subscription Kill the consumer Publish some messages to the topic Restart the subscriber But you don't receive the messages? Fix To be able to deliver messages to offline durable topic subscribers you must mar</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Why+do+KahaDB+log+files+remain+after+cleanup">Why do KahaDB log files remain after cleanup</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Clean-up of un-referenced KahaDB journal log files data-<id>.log will occur every 30 seconds by default. If a data file is in-use it will not be cleaned up. A data file may be in-use because: It contains a pending message for a destination or durable topi</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Wildcards">Wildcards</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We support destination wildcards to provide easy support for federated name hierarchies. This concept has been popular in financial market data for some time as a way of organizing events (such as price changes) into hierarchies and to use wildcards for e</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Wire+Protocol">Wire Protocol</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">This page describes the logical OpenWire protocol for users developing clients in other languages than Java such as C# or C native clients. Note that OpenWire is designed for maximum performance and features; its the protocol used inside ActiveMQ. If you </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/WS+Notification">WS Notification</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">WS-Notification This page has now moved to the ServiceMix site http://servicemix.apache.org/. You can read about WS-Notification support here http://incubator.apache.org/servicemix/ws-notification.html</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/WSIF">WSIF</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The Apache Web Service Invocation Framework (WSIF) http://ws.apache.org/wsif/ allows you to perform web service invocations using a number of different implementation protocols like Axis, local Java, EJB, JMS, JCA CCI etc. For more information on how to u</div>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-X"></a>X</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/XBean+XML+Reference+4.1">XBean XML Reference 4.1</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Elements By Type The org.apache.activemq.network.jms.InboundQueueBridge Type Implementations <inboundQueueBridge> Create an Inbound Queue Bridge The org.apache.activemq.broker.BrokerService Type Implementations <broker> An ActiveMQ Message Broker which co</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/XBean+XML+Reference+5.0">XBean XML Reference 5.0</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Elements By Type The org.apache.activemq.broker.TransportConnector Type Implementations <transportConnector> The org.apache.activemq.network.jms.InboundQueueBridge Type Implementations <inboundQueueBridge> Create an Inbound Queue Bridge The org.apache.act</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Xml+Configuration">Xml Configuration</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">We support an XML deployment descriptor for configuring the ActiveMQ Message Broker. There are many things which can be configured such as transport connectors which consist of transport channels and wire formats network connectors using network channels </div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/Xml+Reference">Xml Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ActiveMQ Xml Reference This page contains a link to the XML reference guides and XML schema documents for Xml Configuration with ActiveMQ releases Released Schemas Reference Document Reference XML Schema XML Schema namespace XBean XML Reference 4.1 Refere</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/XMPP">XMPP</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">XMPP Protocol Support (Jabber!) This transport was deprecated in 5.8.0 and has been removed in a 5.9.0! We have support for XMPP http://www.xmpp.org/ (Jabber) as a transport in ActiveMQ. To use just add a connector as follows <broker xmlns="http://activem</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Y"></a>Y</h4>
- </td></tr><tr valign="top"><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-Z"></a>Z</h4>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ZeroConf">ZeroConf</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">ZeroConf ZeroConf http://www.zeroconf.org/ is a standard service discovery mechanism. ZeroConf is used on Apple's OS X; which used to call it Rendezvous but now calls it Bonjour. Support for ZeroConf is deprecated and scheduled to be removed from ActiveMQ</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/ZeroConf+Transport+Reference">ZeroConf Transport Reference</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">The ZeroConf Transport The ZeroConf transport works just like Discovery Transport, except that it uses a ZeroConf based discovery agent to locate the list of broker uris to connect to. Configuration Syntax zeroconf:serviceName?transportOptions or zeroconf</div>
- <span class="icon aui-icon aui-icon-small aui-iconfont-page-default" title="Page">Page:</span> <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/zOS">zOS</a>
- <br clear="none">
- <div class="smalltext" style="margin: 0 0 0 36px">Running ActiveMQ on z/OS It is relatively straightforward to run the ActiveMQ broker on z/OS. There are a couple of steps: 1. Copy ActiveMQ to z/OS 2. Modify the configuration 3. Run using JZOS 4. Test Copy ActiveMQ to z/OS Ensure that the 1.5 JVM is avai</div>
- </td><td colspan="1" rowspan="1"><h4 style="margin-top: 0px"><a shape="rect" name="index-%21@%23%24"></a>!@#$</h4>
- </td></tr></table>
-</p></div>
+<structured-macro ac:macro-id="d0e35116-a387-44a7-b0f8-db1024714946" ac:name="unmigrated-inline-wiki-markup" ac:schema-version="1"><plain-text-body>{index}{index}</plain-text-body></structured-macro></div>
diff --git a/sitemap.xml b/sitemap.xml
index 5d9b2d2..e245f2a 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,24 +1,25 @@
-<div class="wiki-content maincontent"><h2 id="SiteMap-UsingActiveMQ">Using ActiveMQ</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="configuring-brokers.xml">Configuring Brokers</a></li><li><a shape="rect" href="configuring-transports.xml">Configuring Transports</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-connection-uris.xml">ActiveMQ Connection URIs</a><ul class="childpages-macro"><li><a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a><ul class="childpages-macro"><li><a shape="rect" href="broker-properties-uri.xml">Broker Properties URI</a></li><li><a shape="rect" href="broker-uri.xml">Broker URI</a></li><li><a shape="rect" href="broker-xbean-uri.xml">Broker XBean URI</a></li></ul></li><li><a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a></li><li><a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a></li><li><a shape="rect" href="discovery-transport-reference.xml">Discovery Transport Reference</a></li><li><a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></li><li><a shape="rect" href="fanout-transport-reference.xml">Fanout Transport Reference</a></li><li><a shape="rect" href="http-and-https-transports-reference.xml">HTTP and HTTPs Transports Reference</a></li><li><a shape="rect" href="multicast-transport-reference.xml">Multicast Transport Reference</a></li><li><a shape="rect" href="nio-transport-reference.xml">NIO Transport Reference</a></li><li><a shape="rect" href="peer-transport-reference.xml">Peer Transport Reference</a></li><li><a shape="rect" href="ssl-transport-reference.xml">SSL Transport Reference</a></li><li><a shape="rect" href="static-transport-reference.xml">Static Transport Reference</a></li><li><a shape="rect" href="tcp-transport-reference.xml">TCP Transport Reference</a></li><li><a shape="rect" href="udp-transport-reference.xml">UDP Transport Reference</a></li><li><a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a></li></ul></li><li><a shape="rect" href="activemq-inactivitymonitor.xml">ActiveMQ InactivityMonitor</a></li><li><a shape="rect" href="zeroconf-transport-reference.xml">ZeroConf Transport Reference</a><ul class="childpages-macro"><li><a shape="rect" href="zeroconf.xml">ZeroConf</a></li></ul></li></ul></li><li><a shape="rect" href="examples.xml">Examples</a></li><li><a shape="rect" href="getting-started.xml">Getting Started</a><ul class="childpages-macro"><li><a shape="rect" href="monitoring-activemq.xml">Monitoring ActiveMQ</a></li></ul></li><li><a shape="rect" href="hello-world.xml">Hello World</a></li><li><a shape="rect" href="initial-configuration.xml">Initial Configuration</a></li><li><a shape="rect" href="installation.xml">Installation</a></li><li><a shape="rect" href="known-bad-os-and-jvm-combinations.xml">Known Bad OS and JVM Combinations</a></li><li><a shape="rect" href="performance-tuning.xml">Performance Tuning</a></li><li><a shape="rect" href="run-broker.xml">Run Broker</a></li><li><a shape="rect" href="topologies.xml">Topologies</a></li><li><a shape="rect" href="use-cases.xml">Use Cases</a></li><li><a shape="rect" href="user-submitted-configurations.xml">User Submitted Configurations</a><ul class="childpages-macro"><li><a shape="rect" href="complex-single-broker-configuration-stomp-only.xml">Complex Single Broker Configuration (STOMP only)</a></li><li><a shape="rect" href="jms-and-jdbc-operations-in-one-transaction.xml">JMS and JDBC operations in one transaction</a></li><li><a shape="rect" href="jms-bridge-with-local-broker.xml">JMS Bridge With Local Broker</a></li><li><a shape="rect" href="jms-bridge-with-oracle-aq.xml">JMS Bridge With Oracle AQ</a></li><li><a shape="rect" href="jms-bridge-with-remote-broker.xml">JMS Bridge With Remote Broker</a></li><li><a shape="rect" href="jms-bridge-with-remote-tibco-broker.xml">JMS Bridge With Remote TIBCO Broker</a></li><li><a shape="rect" href="sample-camel-routes.xml">Sample Camel Routes</a></li></ul></li><li><a shape="rect" href="web-samples.xml">Web Samples</a></li><li><a shape="rect" href="xml-configuration.xml">Xml Configuration</a></li><li><a shape="rect" href="xml-reference.xml">Xml Reference</a><ul class="childpages-macro"><li><a shape="rect" href="xbean-xml-reference-41.xml">XBean XML Reference 4.1</a></li><li><a shape="rect" href="xbean-xml-reference-50.xml">XBean XML Reference 5.0</a></li></ul></li></ul>
+<div class="wiki-content maincontent"><h2>Using ActiveMQ</h2>
+<structured-macro ac:macro-id="693fd30f-3017-4bdf-a901-da89d34a865c" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Using ActiveMQ"></page></link></parameter></structured-macro>
-<h2 id="SiteMap-Community">Community</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="articles.xml">Articles</a></li><li><a shape="rect" href="books.xml">Books</a></li><li><a shape="rect" href="contributing.xml">Contributing</a></li><li><a shape="rect" href="discussion-forums.xml">Discussion Forums</a></li><li><a shape="rect" href="faq.xml">FAQ</a><ul class="childpages-macro"><li><a shape="rect" href="configuration.xml">Configuration</a><ul class="childpages-macro"><li><a shape="rect" href="how-can-i-enable-detailed-logging.xml">How can I enable detailed logging</a></li><li><a shape="rect" href="how-does-xbean-compare-to-spring-2.xml">How does XBean compare to Spring 2</a></li><li><a shape="rect" href="how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker.xml">How do I configure 10s of 1000s of Queues in a single broker</a></li><li><a shape="rect" href="how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages.xml">How do I configure ActiveMQ to hold 100s of millions of Queue Messages</a></li><li><a shape="rect" href="how-do-i-configure-activemq-to-use-aio-server-transport.xml">How do I configure ActiveMQ to use AIO server transport</a></li><li><a shape="rect" href="how-do-i-configure-automatic-reconnection.xml">How do I configure automatic reconnection</a></li><li><a shape="rect" href="how-do-i-configure-distributed-queues-or-topics.xml">How do I configure distributed queues or topics</a></li><li><a shape="rect" href="how-do-i-configure-the-queues-i-want.xml">How do I configure the queues I want</a></li><li><a shape="rect" href="how-do-i-define-a-local-address-and-local-port-for-tcp-or-ssl.xml">How do I define a local address and local port for TCP or SSL</a></li><li><a shape="rect" href="how-do-i-disable-persistence.xml">How do I disable persistence</a></li><li><a shape="rect" href="how-do-i-run-activemq-under-the-kaffe-jvm.xml">How do I run ActiveMQ under the Kaffe JVM</a></li><li><a shape="rect" href="how-to-configure-a-new-database.xml">How to configure a new database</a></li><li><a shape="rect" href="how-to-deploy-activemq-ra-versionrar-to-weblogic.xml">How to deploy activemq-ra-version.rar to weblogic</a></li><li><a shape="rect" href="how-to-disable-multicast-discovery.xml">How to disable multicast discovery</a></li></ul></li><li><a shape="rect" href="developing-activemq.xml">Developing ActiveMQ</a><ul class="childpages-macro"><li><a shape="rect" href="how-can-i-add-a-new-type-of-transport.xml">How can I add a new type of transport</a></li><li><a shape="rect" href="how-can-i-contribute.xml">How can I contribute</a></li><li><a shape="rect" href="how-do-i-add-my-own-plugins.xml">How do I add my own plugins</a></li><li><a shape="rect" href="how-do-i-debug-activemq-from-my-ide.xml">How do I debug ActiveMQ from my IDE</a></li></ul></li><li><a shape="rect" href="errors.xml">Errors</a><ul class="childpages-macro"><li><a shape="rect" href="could-not-find-packetreader-for-packet-type-unknown-packet-type.xml">Could not find PacketReader for packet type - UNKNOWN PACKET TYPE</a></li><li><a shape="rect" href="exceptions.xml">Exceptions</a><ul class="childpages-macro"><li><a shape="rect" href="certificateunknown.xml">certificate_unknown</a></li><li><a shape="rect" href="ioexception-could-not-find-class-for-resource.xml">IOException - could not find class for resource</a></li><li><a shape="rect" href="javaiointerruptedioexception.xml">java.io.InterruptedIOException</a></li><li><a shape="rect" href="javaioioexception-failed-to-create-database-derbydb-see-the-next-exception-for-details.xml">java.io.IOException Failed to create database 'derbydb', see the next exception for details</a></li><li><a shape="rect" href="javalangnosuchmethoderror.xml">java.lang.NoSuchMethodError</a></li><li><a shape="rect" href="javalangnosuchmethodexception-orgactivemqraactivemqresourceadaptersetuseembeddedbroker.xml">java.lang.NoSuchMethodException org.activemq.ra.ActiveMQResourceAdapter.setUseEmbeddedBroker</a></li><li><a shape="rect" href="javalangoutofmemory.xml">java.lang.OutOfMemory</a></li><li><a shape="rect" href="javaxjmsjmsexception-wire-format-negociation-timeout-peer-did-not-send-his-wire-format.xml">javax.jms.JMSException - Wire format negociation timeout - peer did not send his wire format.</a></li><li><a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI () needs 2.1 API.</a></li><li><a shape="rect" href="jaxb-20-api-is-being-loaded-from-the-bootstrap-classloader-but-this-ri-xxx-needs-21-api.xml">JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (xxx) needs 2.1 API</a></li><li><a shape="rect" href="journal-is-already-opened-by-this-application.xml">Journal is already opened by this application</a></li><li><a shape="rect" href="noclassdeffounderror-orgspringframeworkcoreioresource.xml">NoClassDefFoundError - org.springframework.core.io.Resource</a></li><li><a shape="rect" href="no-suitable-driver.xml">No suitable driver</a></li></ul></li><li><a shape="rect" href="i-am-having-problems-with-the-spring-jmstemplate.xml">I am having problems with the Spring JmsTemplate</a></li><li><a shape="rect" href="i-am-not-receiving-any-messages-what-is-wrong.xml">I am not receiving any messages, what is wrong</a></li><li><a shape="rect" href="i-cannot-connect-to-activemq-from-jconsole.xml">I cannot connect to ActiveMQ from JConsole</a></li><li><a shape="rect" href="i-do-not-receive-messages-in-my-second-consumer.xml">I do not receive messages in my second consumer</a></li><li><a shape="rect" href="i-get-errors-building-the-code-whats-wrong.xml">I get errors building the code whats wrong</a></li><li><a shape="rect" href="log4j-warn-no-appenders-could-be-found-for-logger.xml">log4j-WARN No appenders could be found for logger</a></li><li><a shape="rect" href="multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.xml">Multicast - Watch out for IPV6 vs IPV4 support on your operating system or distribution or network</a></li><li><a shape="rect" href="my-producer-blocks.xml">My producer blocks</a></li><li><a shape="rect" href="onmessage-method-of-messagelistener-is-never-called.xml">onMessage method of MessageListener is never called</a></li><li><a shape="rect" href="resource-adapter-does-not-seem-to-pool-connections.xml">Resource Adapter does not seem to pool connections</a></li><li><a shape="rect" href="slow-networks-drop-large-messages.xml">Slow networks drop large messages</a></li><li><a shape="rect" href="the-broker-will-not-start.xml">The Broker will not start</a></li><li><a shape="rect" href="the-vm-transport-starts-a-broker-before-my-configured-broker-starts.xml">The vm transport starts a broker before my configured broker starts</a></li><li><a shape="rect" href="why-do-i-not-get-all-of-the-messages-i-sent.xml">Why do I not get all of the messages I sent</a></li><li><a shape="rect" href="why-do-i-not-receive-messages-on-my-durable-topic-subscription.xml">Why do I not receive messages on my durable topic subscription</a></li><li><a shape="rect" href="why-do-kahadb-log-files-remain-after-cleanup.xml">Why do KahaDB log files remain after cleanup</a></li></ul></li><li><a shape="rect" href="general.xml">General</a><ul class="childpages-macro"><li><a shape="rect" href="can-i-get-commercial-support.xml">Can I get commercial support</a></li><li><a shape="rect" href="how-can-i-get-help.xml">How can I get help</a></li><li><a shape="rect" href="how-can-i-get-the-source-code-from-subversion.xml">How can I get the source code from subversion</a></li><li><a shape="rect" href="how-does-activemq-compare-to-amqp.xml">How does ActiveMQ compare to AMQP</a></li><li><a shape="rect" href="how-does-activemq-compare-to-artemis.xml">How does ActiveMQ compare to Artemis</a></li><li><a shape="rect" href="how-does-activemq-compare-to-fuse-message-broker.xml">How does ActiveMQ compare to Fuse Message Broker</a></li><li><a shape="rect" href="how-does-activemq-compare-to-jbossmq.xml">How does ActiveMQ compare to JBossMQ</a></li><li><a shape="rect" href="how-does-activemq-compare-to-mantaray.xml">How does ActiveMQ compare to Mantaray</a></li><li><a shape="rect" href="how-does-activemq-compare-to-mule.xml">How does ActiveMQ compare to Mule</a></li><li><a shape="rect" href="how-does-activemq-compare-to-spread-toolkit.xml">How does ActiveMQ compare to Spread Toolkit</a></li><li><a shape="rect" href="how-does-openwire-compare-to-stomp.xml">How does OpenWire compare to Stomp</a></li><li><a shape="rect" href="how-does-the-website-work.xml">How does the website work</a></li><li><a shape="rect" href="how-do-i-avoid-maven-downloading-latest-jars.xml">How do I avoid Maven downloading latest jars</a></li><li><a shape="rect" href="how-do-i-build-but-disable-the-unit-tests.xml">How do I build but disable the unit tests</a></li><li><a shape="rect" href="how-do-i-compile-from-the-source.xml">How do I compile from the source</a></li><li><a shape="rect" href="how-do-i-edit-the-website.xml">How do I edit the website</a></li><li><a shape="rect" href="how-fast-is-activemq.xml">How fast is ActiveMQ</a></li><li><a shape="rect" href="should-i-run-activemq-on-windows-in-a-directory-with-spaces.xml">Should I run ActiveMQ on Windows in a directory with spaces</a></li><li><a shape="rect" href="what-is-activemq.xml">What is ActiveMQ</a></li><li><a shape="rect" href="what-is-the-license.xml">What is the license</a></li><li><a shape="rect" href="what-jars-do-i-need.xml">What jars do I need</a></li><li><a shape="rect" href="what-open-source-integration-solution-works-best-with-activemq.xml">What open source integration solution works best with ActiveMQ</a></li><li><a shape="rect" href="what-platforms-does-activemq-support.xml">What platforms does ActiveMQ support</a></li><li><a shape="rect" href="what-version-should-i-use.xml">What version should I use</a></li></ul></li><li><a shape="rect" href="jms.xml">JMS</a><ul class="childpages-macro"><li><a shape="rect" href="can-i-modify-messages-on-a-queue.xml">Can I modify messages on a queue</a></li><li><a shape="rect" href="can-i-send-and-receive-messages-concurrently-on-one-jms-connection.xml">Can I send and receive messages concurrently on one JMS Connection</a></li><li><a shape="rect" href="can-you-browse-a-topic.xml">Can you browse a topic</a></li><li><a shape="rect" href="how-do-durable-queues-and-topics-work.xml">How do durable queues and topics work</a></li><li><a shape="rect" href="how-does-a-queue-compare-to-a-topic.xml">How does a Queue compare to a Topic</a></li><li><a shape="rect" href="how-does-connectionfactory-relate-to-the-broker.xml">How does ConnectionFactory relate to the Broker</a></li><li><a shape="rect" href="how-does-jms-compare-with-email.xml">How does JMS compare with email</a></li><li><a shape="rect" href="how-do-i-consume-a-specific-message.xml">How do I consume a specific message</a></li><li><a shape="rect" href="how-do-i-get-started-with-jms.xml">How do I get started with JMS</a></li><li><a shape="rect" href="how-do-i-make-messages-durable.xml">How do I make messages durable</a></li><li><a shape="rect" href="how-do-i-send-messages-to-different-destinations-from-a-single-messageproducer.xml">How do I send messages to different Destinations from a single MessageProducer</a></li><li><a shape="rect" href="how-do-i-use-jms-efficiently.xml">How do I use JMS efficiently</a></li><li><a shape="rect" href="how-should-i-implement-request-response-with-jms.xml">How should I implement request response with JMS</a></li><li><a shape="rect" href="how-to-unit-test-jms-code.xml">How To Unit Test JMS Code</a></li><li><a shape="rect" href="multiple-consumers-on-a-queue.xml">Multiple consumers on a queue</a></li><li><a shape="rect" href="should-i-use-transactions.xml">Should I use transactions</a></li><li><a shape="rect" href="should-i-use-xa.xml">Should I use XA</a></li><li><a shape="rect" href="what-are-administered-objects.xml">What are administered objects</a></li></ul></li><li><a shape="rect" href="persistence-questions.xml">Persistence Questions</a><ul class="childpages-macro"><li><a shape="rect" href="are-messages-read-directly-from-the-journal.xml">Are messages read directly from the journal</a></li><li><a shape="rect" href="does-activemq-support-my-sql-database.xml">Does ActiveMQ support my SQL database</a></li><li><a shape="rect" href="how-does-journaling-work-with-multiple-brokers.xml">How does journaling work with multiple brokers</a></li><li><a shape="rect" href="how-does-the-journal-work.xml">How does the journal work</a></li><li><a shape="rect" href="how-do-i-back-up-kahadb.xml">How do I back-up KahaDB</a></li><li><a shape="rect" href="how-do-i-change-the-message-store-directory-for-an-embedded-broker.xml">How do I change the message store directory for an embedded broker</a></li><li><a shape="rect" href="is-there-a-specified-size-of-the-journal.xml">Is there a specified size of the journal</a></li><li><a shape="rect" href="what-happens-when-the-journal-size-is-exceeded.xml">What happens when the journal size is exceeded</a></li><li><a shape="rect" href="what-is-the-difference-between-persistent-and-non-persistent-delivery.xml">What is the difference between persistent and non-persistent delivery</a></li></ul></li><li><a shape="rect" href="terminology.xml">Terminology</a><ul class="childpages-macro"><li><a shape="rect" href="dr.xml">DR</a></li><li><a shape="rect" href="ha.xml">HA</a></li><li><a shape="rect" href="latency.xml">Latency</a></li><li><a shape="rect" href="mom.xml">MOM</a></li><li><a shape="rect" href="qos.xml">QoS</a></li><li><a shape="rect" href="seda.xml">SEDA</a></li><li><a shape="rect" href="throughput.xml">Throughput</a></li></ul></li><li><a shape="rect" href="using-apache-activemq.xml">Using Apache ActiveMQ</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-command-line-tools-reference.xml">ActiveMQ Command Line Tools Reference</a></li><li><a shape="rect" href="are-destinations-case-sensitive.xml">Are destinations case sensitive</a></li><li><a shape="rect" href="can-i-send-really-large-files-over-activemq.xml">Can I send really large files over ActiveMQ</a></li><li><a shape="rect" href="can-i-use-activemq-5x-or-later-on-java-14.xml">Can I use ActiveMQ 5.x or later on Java 1.4</a></li><li><a shape="rect" href="can-two-brokers-share-the-same-database.xml">Can two brokers share the same database</a></li><li><a shape="rect" href="does-activemq-support-clustering.xml">Does ActiveMQ support clustering</a></li><li><a shape="rect" href="how-can-i-avoid-serialization-of-objects-in-objectmessage.xml">How can I avoid serialization of Objects in ObjectMessage</a></li><li><a shape="rect" href="how-can-i-get-a-list-of-the-topics-and-queues-in-a-broker.xml">How can I get a list of the topics and queues in a broker</a></li><li><a shape="rect" href="how-can-i-make-activemq-faster.xml">How can I make ActiveMQ faster</a></li><li><a shape="rect" href="how-can-i-monitor-activemq.xml">How can I monitor ActiveMQ</a></li><li><a shape="rect" href="how-can-i-monitor-the-connection-with-the-broker.xml">How can I monitor the connection with the broker</a></li><li><a shape="rect" href="how-can-i-see-what-destinations-are-used.xml">How can I see what destinations are used</a></li><li><a shape="rect" href="how-can-i-support-auto-reconnection.xml">How can I support auto reconnection</a></li><li><a shape="rect" href="how-can-i-support-priority-queues.xml">How can I support priority queues</a></li><li><a shape="rect" href="how-can-i-use-different-network-protocols.xml">How can I use different network protocols</a></li><li><a shape="rect" href="how-do-distributed-queues-work.xml">How do distributed queues work</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-c.xml">How do I access ActiveMQ from C</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-csharp-or-dotnet.xml">How do I access ActiveMQ from CSharp or dotNet</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-ruby-perl-python-php.xml">How do I access ActiveMQ from Ruby, Perl, Python, PHP</a></li><li><a shape="rect" href="how-do-i-bridge-different-jms-providers.xml">How do I bridge different JMS providers</a></li><li><a shape="rect" href="how-do-i-change-dispatch-policy.xml">How do I change dispatch policy</a></li><li><a shape="rect" href="how-do-i-change-the-logging.xml">How do I change the logging</a></li><li><a shape="rect" href="how-do-i-connect-to-one-of-a-number-of-message-brokers.xml">How do I connect to one of a number of message brokers</a></li><li><a shape="rect" href="how-do-i-create-new-destinations.xml">How do I create new destinations</a></li><li><a shape="rect" href="how-do-i-delete-a-destination.xml">How do I delete a destination</a></li><li><a shape="rect" href="how-do-i-disable-logging.xml">How do I disable logging</a></li><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li><li><a shape="rect" href="how-do-i-enable-asynchronous-sending.xml">How do I enable asynchronous sending</a></li><li><a shape="rect" href="how-do-i-enable-debug-logging.xml">How do I enable debug logging</a></li><li><a shape="rect" href="how-do-i-find-the-size-of-a-queue.xml">How do I find the Size of a Queue</a></li><li><a shape="rect" href="how-do-i-preserve-order-of-messages.xml">How do I preserve order of messages</a></li><li><a shape="rect" href="how-do-i-purge-a-queue.xml">How do I purge a queue</a></li><li><a shape="rect" href="how-do-i-restart-embedded-broker.xml">How do I restart embedded broker</a></li><li><a shape="rect" href="how-do-i-restrict-connections-from-creating-new-queues-or-topics.xml">How do I restrict connections from creating new queues or topics</a></li><li><a shape="rect" href="how-do-i-run-a-broker.xml">How do I run a broker</a></li><li><a shape="rect" href="how-do-i-set-the-message-expiration.xml">How do I set the message expiration</a></li><li><a shape="rect" href="how-do-i-turn-off-creating-an-embedded-activemq-broker-when-using-the-vm-transport.xml">How do I turn off creating an embedded ActiveMQ broker when using the VM transport</a></li><li><a shape="rect" href="how-do-i-unack-the-message-with-stomp.xml">How do I unack the message with Stomp</a></li><li><a shape="rect" href="how-do-i-use-activemq-using-in-jvm-messaging.xml">How do I use ActiveMQ using in JVM messaging</a></li><li><a shape="rect" href="how-do-i-use-durable-subscribers-in-a-network-of-brokers.xml">How do I use durable subscribers in a network of brokers</a></li><li><a shape="rect" href="how-do-i-use-ivy-with-activemq.xml">How do I use Ivy with ActiveMQ</a></li><li><a shape="rect" href="how-do-i-use-log4j-jms-appender-with-activemq.xml">How do I use log4j JMS appender with ActiveMQ</a></li><li><a shape="rect" href="how-do-i-use-ssl.xml">How do I use SSL</a></li><li><a shape="rect" href="how-do-message-groups-compare-to-selectors.xml">How do Message Groups compare to Selectors</a></li><li><a shape="rect" href="how-do-multiple-transports-work.xml">How do multiple transports work</a></li><li><a shape="rect" href="how-do-transactions-work.xml">How Do Transactions Work</a></li><li><a shape="rect" href="how-lightweight-is-sending-a-message.xml">How lightweight is sending a message</a></li><li><a shape="rect" href="how-should-i-package-applications-using-camel-and-activemq.xml">How should I package applications using Camel and ActiveMQ</a></li><li><a shape="rect" href="how-should-i-use-the-vm-transport.xml">How should I use the VM transport</a></li><li><a shape="rect" href="how-to-deal-with-large-number-of-threads-in-clients.xml">How to deal with large number of threads in clients</a></li><li><a shape="rect" href="how-to-disable-auto-destination-creation.xml">How to disable auto destination creation</a></li><li><a shape="rect" href="i-see-nc-client-ids-what-does-that-mean.xml">I see NC_ client-ids, what does that mean</a></li><li><a shape="rect" href="should-i-deploy-enterprise-integration-patterns-in-the-broker-or-another-application.xml">Should I deploy Enterprise Integration Patterns in the broker or another application</a></li><li><a shape="rect" href="should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml">Should I deploy the broker inside my JVM or AppServer</a></li><li><a shape="rect" href="what-are-those-topics-activemqadvisory.xml">What are those topics ActiveMQ.Advisory</a></li><li><a shape="rect" href="what-happens-with-a-fast-producer-and-slow-consumer.xml">What happens with a fast producer and slow consumer</a></li><li><a shape="rect" href="what-is-the-difference-between-a-virtual-topic-and-a-composite-destination.xml">What is the difference between a Virtual Topic and a Composite Destination</a></li><li><a shape="rect" href="what-is-the-difference-between-discovery-multicast-and-zeroconf.xml">What is the difference between discovery, multicast and zeroconf</a></li><li><a shape="rect" href="what-is-the-prefetch-limit-for.xml">What is the Prefetch Limit For?</a></li><li><a shape="rect" href="while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.xml">While posting large binary file to activeMQ, is there a way to measure its progress</a></li></ul></li></ul></li><li><a shape="rect" href="mailing-lists.xml">Mailing Lists</a><ul class="childpages-macro"><li><a shape="rect" href="all-forums.xml">All Forums</a></li><li><a shape="rect" href="developer-forum.xml">Developer Forum</a></li><li><a shape="rect" href="user-forum.xml">User Forum</a></li></ul></li><li><a shape="rect" href="pmc-templates.xml">PMC Templates</a></li><li><a shape="rect" href="privacy-policy.xml">Privacy Policy</a></li><li><a shape="rect" href="projects-using-activemq.xml">Projects Using ActiveMQ</a></li><li><a shape="rect" href="security-advisories.xml">Security Advisories</a></li><li><a shape="rect" href="sponsorship.xml">Sponsorship</a></li><li><a shape="rect" href="support.xml">Support</a></li><li><a shape="rect" href="team.xml">Team</a></li><li><a shape="rect" href="tips-for-getting-help.xml">Tips for getting help</a></li><li><a shape="rect" href="users.xml">Users</a></li></ul>
+<h2>Community</h2>
+<structured-macro ac:macro-id="2dbd1e2b-6b04-44a5-af43-dd5dda992568" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Community"></page></link></parameter></structured-macro>
-<h2 id="SiteMap-Overview">Overview</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="download.xml">Download</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-11-release.xml">ActiveMQ 1.1 Release</a></li><li><a shape="rect" href="activemq-12-release.xml">ActiveMQ 1.2 Release</a></li><li><a shape="rect" href="activemq-13-release.xml">ActiveMQ 1.3 Release</a></li><li><a shape="rect" href="activemq-14-release.xml">ActiveMQ 1.4 Release</a></li><li><a shape="rect" href="activemq-15-release.xml">ActiveMQ 1.5 Release</a></li><li><a shape="rect" href="activemq-20-release.xml">ActiveMQ 2.0 Release</a></li><li><a shape="rect" href="activemq-21-release.xml">ActiveMQ 2.1 Release</a></li><li><a shape="rect" href="activemq-30-release.xml">ActiveMQ 3.0 Release</a></li><li><a shape="rect" href="activemq-31-release.xml">ActiveMQ 3.1 Release</a></li><li><a shape="rect" href="activemq-321-release.xml">ActiveMQ 3.2.1 Release</a></li><li><a shape="rect" href="activemq-322-release.xml">ActiveMQ 3.2.2 Release</a></li><li><a shape="rect" href="activemq-32-release.xml">ActiveMQ 3.2 Release</a></li><li><a shape="rect" href="activemq-401-release.xml">ActiveMQ 4.0.1 Release</a></li><li><a shape="rect" href="activemq-402-release.xml">ActiveMQ 4.0.2 Release</a></li><li><a shape="rect" href="activemq-40-m4-release.xml">ActiveMQ 4.0 M4 Release</a></li><li><a shape="rect" href="activemq-40-rc2-release.xml">ActiveMQ 4.0 RC2 Release</a></li><li><a shape="rect" href="activemq-40-release.xml">ActiveMQ 4.0 Release</a></li><li><a shape="rect" href="activemq-410-release.xml">ActiveMQ 4.1.0 Release</a></li><li><a shape="rect" href="activemq-411-release.xml">ActiveMQ 4.1.1 Release</a></li><li><a shape="rect" href="activemq-412-release.xml">ActiveMQ 4.1.2 Release</a></li><li><a shape="rect" href="activemq-500-release.xml">ActiveMQ 5.0.0 Release</a></li><li><a shape="rect" href="activemq-510-release.xml">ActiveMQ 5.1.0 Release</a></li><li><a shape="rect" href="activemq-520-release.xml">ActiveMQ 5.2.0 Release</a></li><li><a shape="rect" href="activemq-530-release.xml">ActiveMQ 5.3.0 Release</a></li><li><a shape="rect" href="activemq-531-release.xml">ActiveMQ 5.3.1 Release</a></li><li><a shape="rect" href="activemq-532-release.xml">ActiveMQ 5.3.2 Release</a></li><li><a shape="rect" href="activemq-540-release.xml">ActiveMQ 5.4.0 Release</a></li><li><a shape="rect" href="activemq-541-release.xml">ActiveMQ 5.4.1 Release</a></li><li><a shape="rect" href="activemq-542-release.xml">ActiveMQ 5.4.2 Release</a></li><li><a shape="rect" href="activemq-543-release.xml">ActiveMQ 5.4.3 Release</a></li><li><a shape="rect" href="activemq-550-release.xml">ActiveMQ 5.5.0 Release</a></li><li><a shape="rect" href="activemq-551-release.xml">ActiveMQ 5.5.1 Release</a></li><li><a shape="rect" href="activemq-560-release.xml">ActiveMQ 5.6.0 Release</a></li><li><a shape="rect" href="activemq-570-release.xml">ActiveMQ 5.7.0 Release</a></li><li><a shape="rect" href="activemq-580-release.xml">ActiveMQ 5.8.0 Release</a><ul class="childpages-macro"><li><a shape="rect" href="58-migration-guide.xml">5.8 Migration Guide</a></li></ul></li><li><a shape="rect" href="activemq-590-release.xml">ActiveMQ 5.9.0 Release</a><ul class="childpages-macro"><li><a shape="rect" href="59-migration-guide.xml">5.9 Migration Guide</a></li></ul></li><li><a shape="rect" href="activemq-591-release.xml">ActiveMQ 5.9.1 Release</a></li><li><a shape="rect" href="activemq-5100-release.xml">ActiveMQ 5.10.0 Release</a></li><li><a shape="rect" href="activemq-5101-release.xml">ActiveMQ 5.10.1 Release</a></li><li><a shape="rect" href="activemq-5102-release.xml">ActiveMQ 5.10.2 Release</a></li><li><a shape="rect" href="activemq-5110-release.xml">ActiveMQ 5.11.0 Release</a></li><li><a shape="rect" href="activemq-5111-release.xml">ActiveMQ 5.11.1 Release</a></li><li><a shape="rect" href="activemq-5112-release.xml">ActiveMQ 5.11.2 Release</a></li><li><a shape="rect" href="activemq-5113-release.xml">ActiveMQ 5.11.3 Release</a></li><li><a shape="rect" href="activemq-5120-release.xml">ActiveMQ 5.12.0 Release</a></li><li><a shape="rect" href="activemq-5121-release.xml">ActiveMQ 5.12.1 Release</a></li><li><a shape="rect" href="activemq-5122-release.xml">ActiveMQ 5.12.2 Release</a></li><li><a shape="rect" href="activemq-5130-release.xml">ActiveMQ 5.13.0 Release</a></li><li><a shape="rect" href="activemq-5131-release.xml">ActiveMQ 5.13.1 Release</a></li><li><a shape="rect" href="activemq-5132-release.xml">ActiveMQ 5.13.2 Release</a></li><li><a shape="rect" href="activemq-5133-release.xml">ActiveMQ 5.13.3 Release</a></li><li><a shape="rect" href="activemq-5134-release.xml">ActiveMQ 5.13.4 Release</a></li><li><a shape="rect" href="activemq-5140-release.xml">ActiveMQ 5.14.0 Release</a></li><li><a shape="rect" href="activemq-5141-release.xml">ActiveMQ 5.14.1 Release</a></li><li><a shape="rect" href="activemq-5142-release.xml">ActiveMQ 5.14.2 Release</a></li><li><a shape="rect" href="activemq-5143-release.xml">ActiveMQ 5.14.3 Release</a></li><li><a shape="rect" href="activemq-5144-release.xml">ActiveMQ 5.14.4 Release</a></li><li><a shape="rect" href="activemq-5145-release.xml">ActiveMQ 5.14.5 Release</a></li><li><a shape="rect" href="activemq-5150-release.xml">ActiveMQ 5.15.0 Release</a></li><li><a shape="rect" href="activemq-5151-release.xml">ActiveMQ 5.15.1 Release</a></li><li><a shape="rect" href="activemq-5152-release.xml">ActiveMQ 5.15.2 Release</a></li><li><a shape="rect" href="in-progress.xml">In Progress</a></li></ul></li><li><a shape="rect" href="download-archives.xml">Download Archives</a></li><li><a shape="rect" href="javadocs.xml">JavaDocs</a></li><li><a shape="rect" href="news.xml">News</a></li></ul>
+<h2>Overview</h2>
+<structured-macro ac:macro-id="dbbb82aa-b474-4a65-ba2c-dc3a90a4028b" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Overview"></page></link></parameter></structured-macro>
-<h2 id="SiteMap-Features">Features</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="active-groups.xml">Active Groups</a></li><li><a shape="rect" href="activemq-real-time.xml">ActiveMQ Real Time</a><ul class="childpages-macro"><li><a shape="rect" href="broadcasting.xml">Broadcasting</a></li><li><a shape="rect" href="group-membership.xml">Group Membership</a></li><li><a shape="rect" href="life-cycle.xml">Life Cycle</a></li><li><a shape="rect" href="the-activeblaze-message-type.xml">The ActiveBlaze Message type</a></li></ul></li><li><a shape="rect" href="broker-camel-component.xml">Broker Camel Component</a></li><li><a shape="rect" href="clustering.xml">Clustering</a><ul class="childpages-macro"><li><a shape="rect" href="masterslave.xml">MasterSlave</a><ul class="childpages-macro"><li><a shape="rect" href="jdbc-master-slave.xml">JDBC Master Slave</a></li><li><a shape="rect" href="kahadb-replication-experimental.xml">KahaDB Replication (Experimental)</a></li><li><a shape="rect" href="pure-master-slave.xml">Pure Master Slave</a></li><li><a shape="rect" href="shared-file-system-master-slave.xml">Shared File System Master Slave</a></li></ul></li><li><a shape="rect" href="networks-of-brokers.xml">Networks of Brokers</a></li><li><a shape="rect" href="replicated-message-store.xml">Replicated Message Store</a></li></ul></li><li><a shape="rect" href="command-agent.xml">Command Agent</a></li><li><a shape="rect" href="consumer-features.xml">Consumer Features</a><ul class="childpages-macro"><li><a shape="rect" href="consumer-dispatch-async.xml">Consumer Dispatch Async</a></li><li><a shape="rect" href="consumer-priority.xml">Consumer Priority</a></li><li><a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a></li><li><a shape="rect" href="manage-durable-subscribers.xml">Manage Durable Subscribers</a></li><li><a shape="rect" href="message-groups.xml">Message Groups</a></li><li><a shape="rect" href="redelivery-policy.xml">Redelivery Policy</a></li><li><a shape="rect" href="retroactive-consumer.xml">Retroactive Consumer</a></li><li><a shape="rect" href="selectors.xml">Selectors</a></li><li><a shape="rect" href="slow-consumer-handling.xml">Slow Consumer Handling</a></li><li><a shape="rect" href="subscription-recovery-policy.xml">Subscription Recovery Policy</a></li></ul></li><li><a shape="rect" href="destination-features.xml">Destination Features</a><ul class="childpages-macro"><li><a shape="rect" href="composite-destinations.xml">Composite Destinations</a></li><li><a shape="rect" href="configure-startup-destinations.xml">Configure Startup Destinations</a></li><li><a shape="rect" href="delete-inactive-destinations.xml">Delete Inactive Destinations</a></li><li><a shape="rect" href="destination-options.xml">Destination Options</a></li><li><a shape="rect" href="mirrored-queues.xml">Mirrored Queues</a></li><li><a shape="rect" href="per-destination-policies.xml">Per Destination Policies</a></li><li><a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a></li><li><a shape="rect" href="wildcards.xml">Wildcards</a></li></ul></li><li><a shape="rect" href="discovery.xml">Discovery</a></li><li><a shape="rect" href="enterprise-integration-patterns.xml">Enterprise Integration Patterns</a></li><li><a shape="rect" href="features-overview.xml">Features Overview</a></li><li><a shape="rect" href="horizontal-scaling.xml">Horizontal Scaling</a><ul class="childpages-macro"><li><a shape="rect" href="scaling-queues.xml">Scaling Queues</a></li></ul></li><li><a shape="rect" href="interceptors.xml">Interceptors</a><ul class="childpages-macro"><li><a shape="rect" href="destinations-plugin.xml">Destinations Plugin</a></li><li><a shape="rect" href="logging-interceptor.xml">Logging Interceptor</a></li><li><a shape="rect" href="statisticsplugin.xml">StatisticsPlugin</a></li><li><a shape="rect" href="timestampplugin.xml">TimeStampPlugin</a></li></ul></li><li><a shape="rect" href="jmsxuserid.xml">JMSXUserID</a></li><li><a shape="rect" href="jmx.xml">JMX</a><ul class="childpages-macro"><li><a shape="rect" href="jmx-support.xml">JMX Support</a></li></ul></li><li><a shape="rect" href="logging-a-warning-if-you-forget-to-start-a-connection.xml">Logging a warning if you forget to start a Connection</a></li><li><a shape="rect" href="mdc-logging.xml">MDC Logging</a></li><li><a shape="rect" href="message-dispatching-features.xml">Message Dispatching Features</a><ul class="childpages-macro"><li><a shape="rect" href="async-sends.xml">Async Sends</a></li><li><a shape="rect" href="dispatch-policies.xml">Dispatch Policies</a></li><li><a shape="rect" href="message-cursors.xml">Message Cursors</a></li><li><a shape="rect" href="optimized-acknowledgement.xml">Optimized Acknowledgement</a></li><li><a shape="rect" href="producer-flow-control.xml">Producer Flow Control</a></li><li><a shape="rect" href="total-ordering.xml">Total Ordering</a></li></ul></li><li><a shape="rect" href="message-features.xml">Message Features</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-message-properties.xml">ActiveMQ Message Properties</a></li><li><a shape="rect" href="advisory-message.xml">Advisory Message</a></li><li><a shape="rect" href="blob-messages.xml">Blob Messages</a></li><li><a shape="rect" href="delay-and-schedule-message-delivery.xml">Delay and Schedule Message Delivery</a></li><li><a shape="rect" href="jms-streams.xml">JMS Streams</a></li><li><a shape="rect" href="message-transformation.xml">Message Transformation</a></li><li><a shape="rect" href="objectmessage.xml">ObjectMessage</a></li><li><a shape="rect" href="structured-message-properties-and-mapmessages.xml">Structured Message Properties and MapMessages</a></li></ul></li><li><a shape="rect" href="new-features.xml">New Features</a><ul class="childpages-macro"><li><a shape="rect" href="changes-in-40.xml">Changes in 4.0</a></li><li><a shape="rect" href="new-features-in-41.xml">New Features in 4.1</a></li><li><a shape="rect" href="new-features-in-50.xml">New Features in 5.0</a></li><li><a shape="rect" href="new-features-in-51.xml">New Features in 5.1</a></li><li><a shape="rect" href="new-features-in-52.xml">New Features in 5.2</a></li><li><a shape="rect" href="new-features-in-53.xml">New Features in 5.3</a></li><li><a shape="rect" href="new-features-in-54.xml">New Features in 5.4</a></li><li><a shape="rect" href="new-features-in-55.xml">New Features in 5.5</a></li><li><a shape="rect" href="new-features-in-56.xml">New Features in 5.6</a></li><li><a shape="rect" href="new-features-in-57.xml">New Features in 5.7</a></li><li><a shape="rect" href="new-features-in-58.xml">New Features in 5.8</a></li><li><a shape="rect" href="new-features-in-59.xml">New Features in 5.9</a><ul class="childpages-macro"><li><a shape="rect" href="runtime-configuration.xml">Runtime Configuration</a></li></ul></li><li><a shape="rect" href="new-features-in-511.xml">New Features in 5.11</a></li><li><a shape="rect" href="new-features-in-513.xml">New Features in 5.13</a></li><li><a shape="rect" href="new-features-in-60.xml">New Features in 6.0</a></li></ul></li><li><a shape="rect" href="performance.xml">Performance</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Module Users Manual</a><ul class="childpages-macro"><li><a shape="rect" href="sample-report.xml">sample report</a></li></ul></li><li><a shape="rect" href="load-testing-with-camel.xml">Load Testing with Camel</a></li><li><a shape="rect" href="performance-report.xml">Performance report</a></li></ul></li><li><a shape="rect" href="persistence.xml">Persistence</a><ul class="childpages-macro"><li><a shape="rect" href="amq-message-store.xml">AMQ Message Store</a></li><li><a shape="rect" href="configurable-ioexception-handling.xml">Configurable IOException Handling</a></li><li><a shape="rect" href="jdbc-support.xml">JDBC Support</a><ul class="childpages-macro"><li><a shape="rect" href="sqlserver.xml">SQLServer</a></li><li><a shape="rect" href="sybase.xml">Sybase</a></li></ul></li><li><a shape="rect" href="kahadb.xml">KahaDB</a></li><li><a shape="rect" href="kaha-persistence.xml">Kaha Persistence</a></li><li><a shape="rect" href="leveldb-store.xml">LevelDB Store</a></li><li><a shape="rect" href="periodically-checking-disk-limits.xml">Periodically checking disk limits</a></li><li><a shape="rect" href="pluggable-storage-lockers.xml">Pluggable storage lockers</a></li><li><a shape="rect" href="replicated-leveldb-store.xml">Replicated LevelDB Store</a></li></ul></li><li><a shape="rect" href="scaling-the-depth-of-a-queue.xml">Scaling the Depth of a Queue</a></li><li><a shape="rect" href="security.xml">Security</a><ul class="childpages-macro"><li><a shape="rect" href="audit-logging.xml">Audit Logging</a></li><li><a shape="rect" href="cached-ldap-authorization-module.xml">Cached LDAP Authorization Module</a></li><li><a shape="rect" href="encrypted-passwords.xml">Encrypted passwords</a></li><li><a shape="rect" href="shiro.xml">Shiro</a></li></ul></li><li><a shape="rect" href="the-proxy-connector.xml">The Proxy Connector</a></li><li><a shape="rect" href="unix.xml">Unix</a><ul class="childpages-macro"><li><a shape="rect" href="unix-service.xml">Unix Service</a></li><li><a shape="rect" href="unix-shell-script.xml">Unix Shell Script</a></li></ul></li><li><a shape="rect" href="uri-protocols.xml">URI Protocols</a><ul class="childpages-macro"><li><a shape="rect" href="vm-protocol.xml">VM Protocol</a></li></ul></li><li><a shape="rect" href="visualisation.xml">Visualisation</a><ul class="childpages-macro"><li><a shape="rect" href="visualisation-wish-list.xml">Visualisation Wish List</a></li></ul></li></ul>
+<h2>Features</h2>
+<structured-macro ac:macro-id="587dc780-207d-4c75-a8fa-762b53190527" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Features"></page></link></parameter></structured-macro>
-<h2 id="SiteMap-Connectivity">Connectivity</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="ajax.xml">Ajax</a></li><li><a shape="rect" href="containers.xml">Containers</a><ul class="childpages-macro"><li><a shape="rect" href="axis-and-cxf-support.xml">Axis and CXF Support</a></li><li><a shape="rect" href="blazeds.xml">BlazeDS</a></li><li><a shape="rect" href="geronimo.xml">Geronimo</a></li><li><a shape="rect" href="integrating-apache-activemq-with-glassfish.xml">Integrating Apache ActiveMQ with Glassfish</a></li><li><a shape="rect" href="integrating-apache-activemq-with-jboss.xml">Integrating Apache ActiveMQ with JBoss</a></li><li><a shape="rect" href="j2ee.xml">J2EE</a></li><li><a shape="rect" href="jboss-integration.xml">JBoss Integration</a><ul class="childpages-macro"><li><a shape="rect" href="inbound-communication.xml">Inbound Communication</a></li><li><a shape="rect" href="outbound-communication.xml">Outbound Communication</a></li></ul></li><li><a shape="rect" href="jca-container.xml">JCA Container</a></li><li><a shape="rect" href="jndi-support.xml">JNDI Support</a></li><li><a shape="rect" href="old-osgi-integration.xml">Old OSGi Integration</a></li><li><a shape="rect" href="osgi-integration.xml">OSGi Integration</a></li><li><a shape="rect" href="resource-adapter.xml">Resource Adapter</a><ul class="childpages-macro"><li><a shape="rect" href="activation-spec-properties.xml">Activation Spec Properties</a></li><li><a shape="rect" href="connection-factory-properties.xml">Connection Factory Properties</a></li><li><a shape="rect" href="resource-adapter-properties.xml">Resource Adapter Properties</a></li><li><a shape="rect" href="tomee.xml">TomEE</a></li></ul></li><li><a shape="rect" href="sjsas-with-genericjmsra.xml">SJSAS with GenericJMSRA</a></li><li><a shape="rect" href="spring-support.xml">Spring Support</a><ul class="childpages-macro"><li><a shape="rect" href="jmstemplate-gotchas.xml">JmsTemplate Gotchas</a></li></ul></li><li><a shape="rect" href="sun-jndi.xml">Sun JNDI</a></li><li><a shape="rect" href="tomcat.xml">Tomcat</a><ul class="childpages-macro"><li><a shape="rect" href="setting-up-activemq-with-tomcat-559.xml">Setting up ActiveMQ with Tomcat 5.5.9</a></li></ul></li><li><a shape="rect" href="weblogic-integration.xml">WebLogic Integration</a></li><li><a shape="rect" href="zos.xml">zOS</a></li></ul></li><li><a shape="rect" href="cross-language-clients.xml">Cross Language Clients</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-c-clients.xml">ActiveMQ C++ Clients</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-c-development.xml">ActiveMQ C Development</a></li><li><a shape="rect" href="building-activemq-cpp.xml">Building ActiveMQ CPP</a></li><li><a shape="rect" href="configuring-activemq-cpp.xml">Configuring ActiveMQ CPP</a></li><li><a shape="rect" href="downloading-activemq-cpp.xml">Downloading ActiveMQ CPP</a></li><li><a shape="rect" href="openwire-cpp-client.xml">OpenWire CPP Client</a></li></ul></li><li><a shape="rect" href="c-integration.xml">C Integration</a><ul class="childpages-macro"><li><a shape="rect" href="c-integration-scenarios.xml">C integration scenarios</a></li><li><a shape="rect" href="compile-activemq-with-gcj.xml">Compile ActiveMQ with GCJ</a></li><li><a shape="rect" href="openwire-c-client.xml">OpenWire C Client</a></li></ul></li><li><a shape="rect" href="delphi-and-freepascal.xml">Delphi and FreePascal</a></li></ul></li><li><a shape="rect" href="jms-to-jms-bridge.xml">JMS to JMS Bridge</a></li><li><a shape="rect" href="protocols.xml">Protocols</a><ul class="childpages-macro"><li><a shape="rect" href="amqp.xml">AMQP</a></li><li><a shape="rect" href="auto.xml">AUTO</a></li><li><a shape="rect" href="mqtt.xml">MQTT</a></li><li><a shape="rect" href="openwire.xml">OpenWire</a><ul class="childpages-macro"><li><a shape="rect" href="openwire-version-2-specification.xml">OpenWire Version 2 Specification</a></li></ul></li><li><a shape="rect" href="rest.xml">REST</a></li><li><a shape="rect" href="rss-and-atom.xml">RSS and Atom</a></li><li><a shape="rect" href="stomp.xml">Stomp</a></li><li><a shape="rect" href="wsif.xml">WSIF</a></li><li><a shape="rect" href="ws-notification.xml">WS Notification</a></li><li><a shape="rect" href="xmpp.xml">XMPP</a></li></ul></li><li><a shape="rect" href="websockets.xml">WebSockets</a></li></ul>
+<h2>Connectivity</h2>
+<structured-macro ac:macro-id="4d30d935-39e9-454b-aeb4-a38c783603b8" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Connectivity"></page></link></parameter></structured-macro>
-<h2 id="SiteMap-Tools">Tools</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="hermes-jms.xml">Hermes Jms</a></li><li><a shape="rect" href="hermes-screenshot.xml">Hermes Screenshot</a></li><li><a shape="rect" href="java-service-wrapper.xml">Java Service Wrapper</a></li><li><a shape="rect" href="maven2-activemq-broker-plugin.xml">Maven2 ActiveMQ Broker Plugin</a></li><li><a shape="rect" href="web-console.xml">Web Console</a></li></ul>
+<h2>Tools</h2>
+<structured-macro ac:macro-id="795f61fc-303f-495f-9412-40e98d8720ed" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Tools"></page></link></parameter></structured-macro>
-<h2 id="SiteMap-Developers">Developers</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="becoming-a-committer.xml">Becoming a committer</a></li><li><a shape="rect" href="benchmark-tests.xml">Benchmark Tests</a></li><li><a shape="rect" href="board-reports.xml">Board Reports</a><ul class="childpages-macro"><li><a shape="rect" href="2007-april.xml">2007 April</a></li></ul></li><li><a shape="rect" href="building.xml">Building</a></li><li><a shape="rect" href="code-overview.xml">Code Overview</a></li><li><a shape="rect" href="developer-guide.xml">Developer Guide</a><ul class="childpages-macro"><li><a shape="rect" href="design-documents.xml">Design Documents</a><ul class="childpages-macro"><li><a shape="rect" href="class-diagrams-for-activemq-40-m4-source-code.xml">Class Diagrams for activemq-4.0-M4 source code</a></li><li><a shape="rect" href="durable-queue-memory-management.xml">Durable Queue Memory Management</a></li><li><a shape="rect" href="message-redelivery-and-dlq-handling.xml">Message Redelivery and DLQ Handling</a></li><li><a shape="rect" href="multicast-transport.xml">Multicast Transport</a></li><li><a shape="rect" href="proposed-c-client-architecture.xml">Proposed C Client Architecture</a></li><li><a shape="rect" href="rest-protocols.xml">REST protocols</a></li><li><a shape="rect" href="slow-consumers.xml">Slow Consumers</a></li><li><a shape="rect" href="supporting-io-streams.xml">Supporting IO Streams</a></li></ul></li><li><a shape="rect" href="developing-plugins.xml">Developing Plugins</a></li><li><a shape="rect" href="maven-snapshot-repository-in-your-pom.xml">Maven SNAPSHOT Repository in your POM</a></li><li><a shape="rect" href="release-plans.xml">Release Plans</a><ul class="childpages-macro"><li><a shape="rect" href="40-rc-1-guide.xml">4.0 RC 1 Guide</a></li><li><a shape="rect" href="how-you-can-help-release.xml">How you can help release</a></li><li><a shape="rect" href="release-info.xml">Release Info</a></li></ul></li></ul></li><li><a shape="rect" href="ideas.xml">Ideas</a><ul class="childpages-macro"><li><a shape="rect" href="restful-queue.xml">RESTful Queue</a></li></ul></li><li><a shape="rect" href="integration-tests.xml">Integration Tests</a><ul class="childpages-macro"><li><a shape="rect" href="example-testing-scenario.xml">Example Testing Scenario</a></li></ul></li><li><a shape="rect" href="jmeter-performance-tests.xml">JMeter Performance Tests</a></li><li><a shape="rect" href="jmeter-system-tests.xml">JMeter System Tests</a></li><li><a shape="rect" href="junit-reports.xml">JUnit Reports</a></li><li><a shape="rect" href="release-guide.xml">Release Guide</a></li><li><a shape="rect" href="sandbox.xml">Sandbox</a></li><li><a shape="rect" href="source.xml">Source</a></li><li><a shape="rect" href="source-xref.xml">Source XRef</a></li><li><a shape="rect" href="svn.xml">SVN</a></li><li><a shape="rect" href="test-source-xref.xml">Test Source XRef</a></li><li><a shape="rect" href="wire-protocol.xml">Wire Protocol</a></li></ul>
+<h2>Developers</h2>
+<structured-macro ac:macro-id="88becea1-5d27-4391-b572-285d7bcb471b" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Developers"></page></link></parameter></structured-macro>
-<h2 id="SiteMap-Site">Site</h2>
-<ul class="childpages-macro"><li><a shape="rect" href="banner.xml">Banner</a></li><li><a shape="rect" href="navigation.xml">Navigation</a><ul class="childpages-macro"><li><a shape="rect" href="irc.xml">IRC</a></li></ul></li><li><a shape="rect" href="quicklinks.xml">QuickLinks</a></li><li><a shape="rect" href="siteindex.xml">SiteIndex</a></li><li><a shape="rect" href="sitemap.xml">SiteMap</a></li></ul></div>
+<h2>Site</h2>
+<structured-macro ac:macro-id="8e591c4f-d247-4ac7-85c5-8cc12c1e2000" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter><parameter ac:name="page"><link><page ri:content-title="Site"></page></link></parameter></structured-macro>
+</div>
diff --git a/sjsas-with-genericjmsra.xml b/sjsas-with-genericjmsra.xml
index af1a534..5658981 100644
--- a/sjsas-with-genericjmsra.xml
+++ b/sjsas-with-genericjmsra.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><h1 id="SJSASwithGenericJMSRA-UsingActiveMQ,GenericJMSRAandSJSAS(Glassfish)">Using ActiveMQ, Generic JMS RA and SJSAS (Glassfish)</h1>
+<div class="wiki-content maincontent"><h1>Using ActiveMQ, Generic JMS RA and SJSAS (Glassfish)</h1>
<p>This document is my notes on making ActiveMQ and SJSAS work together using GenericJMSRA. The objectives is to make ActiveMQ as the JMS provider and MDB can be deployed in SJSAS, listening messages from ActiveMQ. Please note that, the SJSAS version I use is 9.0 Update 1. I don't have time to test it with SJSAS 9.1 or Glassfish v2.</p>
-<h2 id="SJSASwithGenericJMSRA-Theprocedures">The procedures</h2>
+<h2>The procedures</h2>
<p>First, download all binaries:</p>
<ul><li>genericra 1.7 (rar)</li><li>activemq 4.1.1 (zip or tar.gz)</li></ul>
@@ -15,8 +15,7 @@
<p>In order to use genericra you need to first create a resource adapter config using asadmin (Command line tools of SJSAS).</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d65d9015-c231-4d9a-ba45-27e17013ab07" ac:name="code" ac:schema-version="1"><plain-text-body>
asadmin create-resource-adapter-config
--property
SupportsXA=false
@@ -34,26 +33,20 @@
:ConnectionFactoryProperties=brokerURL\\=tcp\\://127.0.0.1\\:61616
:LogLevel=FINE
myapp#genericra
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>You should note that, the above command should executed as one single line and no space around ':'. Just like:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="74e30e38-1931-42cc-8b5d-3992951786eb" ac:name="code" ac:schema-version="1"><plain-text-body>
asadmin create-resource-adapter-config --property SupportsXA=false:ConnectionFactoryProperties=brokerURL\\=tcp\\://127.0.0.1\\:61616 myapp#genericra
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Under DOS prompt, you should use ONLY ONE '/' to do espcape, like this.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="3420b706-4660-4803-b168-f70ff659d3b2" ac:name="code" ac:schema-version="1"><plain-text-body>
asadmin create-resource-adapter-config --property SupportsXA=false:ConnectionFactoryProperties=brokerURL\=tcp\://127.0.0.1\:61616 myapp#genericra
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Package your application, genericra.rar and activemq dependencies in one single EAR. The structure of the EAR should like this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="635b2f67-7289-4173-8aaa-db488218a426" ac:name="code" ac:schema-version="1"><plain-text-body>
lib/activemq-core-4.1.1.jar
lib/log4j-1.2.13.jar
lib/commons-logging-1.1.jar
@@ -62,17 +55,15 @@
META-INF/application.xml
genericra.rar
mymodules.jar
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Inside the mymodules.jar (where I put my MDB), the sun-ejb-jar.xml should look like this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
+<structured-macro ac:macro-id="f5cfa6c7-08a0-431d-9364-e18d42f5ecc5" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar
- PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 EJB 2.1//EN"
- "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_2_1-1.dtd">
+ PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 EJB 2.1//EN"
+ "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_2_1-1.dtd">
<sun-ejb-jar>
<enterprise-beans>
<ejb>
@@ -96,19 +87,17 @@
</ejb>
</enterprise-beans>
</sun-ejb-jar>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>And the application.xml should look like this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
+<structured-macro ac:macro-id="263c700b-ccb7-4965-b7d4-d13646bad342" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
<application
- xmlns="http://java.sun.com/xml/ns/javaee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
- version="5">
+ xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
+ version="5">
<description>Example DD</description>
<display-name>sample app with amq and genericra</display-name>
<module>
@@ -118,42 +107,35 @@
<connector>genericra.rar</connector>
</module>
</application>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Deploy the genericra:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b039963c-3b76-42ad-a184-34d0eedf61c5" ac:name="code" ac:schema-version="1"><plain-text-body>
asadmin deploy --name myapp myapp.ear
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Create connection pool. Run the following command in one single line:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c13f51cd-e124-4983-80b4-0aef8c78207e" ac:name="code" ac:schema-version="1"><plain-text-body>
asadmin create-connector-connection-pool
--raname myapp#genericra
--connectiondefinition javax.jms.QueueConnectionFactory
--transactionsupport LocalTransaction
ActiveMQQueueConnectionFactoryPool
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Create connection factory admin object. Run the following command in one single line, note that, "jms/SimpleQueueConnectionFactory" need to match in your sun-ejb-jar.xml:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="d9e007e0-971d-41af-a9ce-55dc969c4eee" ac:name="code" ac:schema-version="1"><plain-text-body>
asadmin create-connector-resource
--poolname ActiveMQQueueConnectionFactoryPool
jms/SimpleQueueConnectionFactory
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="SJSASwithGenericJMSRA-Classloader/commons-logging+log4jissue">Classloader / commons-logging+log4j issue</h2>
+<h2>Classloader / commons-logging+log4j issue</h2>
<p>In the procedure shown above, you should notice one thing, ie, the RA, ActiveMQ and my MDB is deployed as one single EAR. You can deploy the genericra standalone without putting it into the ear, provided that you are not using commons-logging and log4j (directly or indirectly).</p>
<p>In the application I'm working on, commons-logging is used, and ActiveMQ also use commons-logging. In SJSAS, connector classloader is parent of the application classloader, as a result, if you deploy genericra independently, and then you deploy your application, log4j.xml will never get loaded except you put your application log4j.xml along with the ActiveMQ jars.</p>
@@ -169,14 +151,15 @@
<p>If you deploy the RA independently, the ra name is just genericra (as shown in the example by Ramesh).</p>
-<h2 id="SJSASwithGenericJMSRA-LocalTransaction">LocalTransaction</h2>
+<h2>LocalTransaction</h2>
<p>In the instruction described above, LocalTransaction is used. (SupportsXA=false and --transactionsupport LocalTransaction) as I am currently using Non-XA transaction, however, as example shown by Ramesh, XA should also work.</p>
-<h2 id="SJSASwithGenericJMSRA-Configuringgenericra">Configuring genericra</h2>
+<h2>Configuring genericra</h2>
<p>When you create the resource-adapter-config, there is two way to configure. One way is using JNDI, another way is using JavaBean introspection feature of genericra. In the example above, I go with JavaBean introspection feature (so 'ProviderIntegrationMode=javabean'). For more details on this, please checkout the user guide of genericra. Also, I found that expample provided on the genericra website is also valuable resource.</p>
-<h2 id="SJSASwithGenericJMSRA-Reference">Reference</h2>
-<ul><li><a shape="rect" class="external-link" href="http://weblogs.java.net/blog/rampsarathy/archive/2007/03/glassfish_v2_an_1.html" rel="nofollow">Another example on using genericjmsra and activemq by Ramesh</a></li><li><a shape="rect" class="external-link" href="https://genericjmsra.dev.java.net/docs/userguide/userguide.html" rel="nofollow">Official user guide on configuring genericjmsra</a></li><li><a shape="rect" class="external-link" href="http://forums.java.net/jive/thread.jspa?messageID=211849" rel="nofollow">The thread in Glassfish forum which I found my answer</a></li></ul></div>
+<h2>Reference</h2>
+<ul><li><a shape="rect" href="http://weblogs.java.net/blog/rampsarathy/archive/2007/03/glassfish_v2_an_1.html">Another example on using genericjmsra and activemq by Ramesh</a></li><li><a shape="rect" href="https://genericjmsra.dev.java.net/docs/userguide/userguide.html">Official user guide on configuring genericjmsra</a></li><li><a shape="rect" href="http://forums.java.net/jive/thread.jspa?messageID=211849">The thread in Glassfish forum which I found my answer</a></li></ul>
+</div>
diff --git a/slow-consumer-handling.xml b/slow-consumer-handling.xml
index 9d12fce..a749009 100644
--- a/slow-consumer-handling.xml
+++ b/slow-consumer-handling.xml
@@ -1,9 +1,9 @@
-<div class="wiki-content maincontent"><p><a shape="rect" href="slow-consumers.xml">Slow Consumers</a> can cause problems on non-durable topics since they can force the broker to keep old messages in RAM which once it fills up, forces the broker to slow down producers, causing the fast consumers to be slowed down. One option we could implement in the future is spooling to disk - but then spooling to disk could slow down the fast consumers too.</p><p>Currently we have a strategy that lets you configure the maximum number of matched messages the broker will keep around for a consumer in addition to its prefetch buffer. Once this maximum is reached, as new messages come in, older messages are discarded. This allows you to keep the RAM for current messages and keep sending messages to a slow consumer but to discard old messages.</p><h2 id="SlowConsumerHandling-PendingMessageLimitStrategy">Pending Message Limit Strategy</h2><p>You can configure the <strong><code>PendingMessageLimitStrategy</code></strong> implementation class on the destination map so that different regions of your topic namespace can have different strategies for dealing with slow consumers. For example you may want to use this strategy for prices which are very high volume but for orders and trades which are lower volume you might not wish to discard old messages.</p><p>The strategy calculates the maximum number of pending messages to be kept in RAM for a consumer (above its prefetch size). A value of zero means keep no messages around other than the prefetch amount. A value greater than zero will keep up to that amount of messages around, discarding the older messages as new messages come in. A value of <strong><code>-1</code></strong> disables the discarding of messages.</p><p>There are currently two different implementations of the strategy:</p><ul><li><strong><code>ConstantPendingMessageLimitStrategy</code></strong></li><li><strong><code>PrefetchRatePendingMessageLimitStrategy</code></strong></li></ul><h3 id="SlowConsumerHandling-ConstantPendingMessageLimitStrategy">ConstantPendingMessageLimitStrategy</h3><p>This strategy uses a constant limit for all consumers (above their prefetch size).</p><p>Example:</p><parameter ac:name="language">xml</parameter><plain-text-body><constantPendingMessageLimitStrategy limit="50"/>
-</plain-text-body><h3 id="SlowConsumerHandling-PrefetchRatePendingMessageLimitStrategy">PrefetchRatePendingMessageLimitStrategy</h3><p>This strategy calculates the maximum number of pending messages using a multiplier of the consumers prefetch size. So you could for example keep around 2.5 times the prefetch count for each consumer.</p><parameter ac:name="language">xml</parameter><plain-text-body><prefetchRatePendingMessageLimitStrategy multiplier="2.5"/>
-</plain-text-body><h3 id="SlowConsumerHandling-UsingthePrefetchPolicytoConfiguretheLimit">Using the Prefetch Policy to Configure the Limit</h3><p>The JMS Client has a <a shape="rect" href="what-is-the-prefetch-limit-for.xml">prefetch policy</a> you can use to configure the various prefetch limits for persistent and non persistent queues and topics. The prefetch policy also allows you to specify the <strong><code>maximumPendingMessageLimit</code></strong> on a per connection/consumer basis. One minor difference with configuring this value; to simplify operation with non-JMS clients such as with <a shape="rect" href="openwire.xml">OpenWire</a> the value of zero is ignored; so the lowest value you can configure is <strong><code>1</code></strong>.</p><h3 id="SlowConsumerHandling-ConfiguringtheEvictionPolicy">Configuring the Eviction Policy</h3><p>We have a <strong><code>MessageEvictionStrategy</code></strong> which is used to decide which message should be evicted on a slow consumer. The default implementation is:</p><parameter ac:name="language">xml</parameter><plain-text-body><oldestMessageEvictionStrategy/>
+<div class="wiki-content maincontent"><p><link><page ri:content-title="Slow Consumers"></page></link> can cause problems on non-durable topics since they can force the broker to keep old messages in RAM which once it fills up, forces the broker to slow down producers, causing the fast consumers to be slowed down. One option we could implement in the future is spooling to disk - but then spooling to disk could slow down the fast consumers too.</p><p>Currently we have a strategy that lets you configure the maximum number of matched messages the broker will keep around for a consumer in addition to its prefetch buffer. Once this maximum is reached, as new messages come in, older messages are discarded. This allows you to keep the RAM for current messages and keep sending messages to a slow consumer but to discard old messages.</p><h2>Pending Message Limit Strategy</h2><p>You can configure the <strong><code>PendingMessageLimitStrategy</code></strong> implementation class on the destination map so that different regions of your topic namespace can have different strategies for dealing with slow consumers. For example you may want to use this strategy for prices which are very high volume but for orders and trades which are lower volume you might not wish to discard old messages.</p><p>The strategy calculates the maximum number of pending messages to be kept in RAM for a consumer (above its prefetch size). A value of zero means keep no messages around other than the prefetch amount. A value greater than zero will keep up to that amount of messages around, discarding the older messages as new messages come in. A value of <strong><code>-1</code></strong> disables the discarding of messages.</p><p>There are currently two different implementations of the strategy:</p><ul><li><strong><code>ConstantPendingMessageLimitStrategy</code></strong></li><li><strong><code>PrefetchRatePendingMessageLimitStrategy</code></strong></li></ul><h3>ConstantPendingMessageLimitStrategy</h3><p>This strategy uses a constant limit for all consumers (above their prefetch size).</p><p>Example:</p><parameter ac:name="language">xml</parameter><plain-text-body><constantPendingMessageLimitStrategy limit="50"/>
+</plain-text-body><h3>PrefetchRatePendingMessageLimitStrategy</h3><p>This strategy calculates the maximum number of pending messages using a multiplier of the consumers prefetch size. So you could for example keep around 2.5 times the prefetch count for each consumer.</p><parameter ac:name="language">xml</parameter><plain-text-body><prefetchRatePendingMessageLimitStrategy multiplier="2.5"/>
+</plain-text-body><h3>Using the Prefetch Policy to Configure the Limit</h3><p>The JMS Client has a <link><page ri:content-title="What is the Prefetch Limit For?"></page><plain-text-link-body>prefetch policy</plain-text-link-body></link> you can use to configure the various prefetch limits for persistent and non persistent queues and topics. The prefetch policy also allows you to specify the <strong><code>maximumPendingMessageLimit</code></strong> on a per connection/consumer basis. One minor difference with configuring this value; to simplify operation with non-JMS clients such as with <link><page ri:content-title="OpenWire"></page></link> the value of zero is ignored; so the lowest value you can configure is <strong><code>1</code></strong>.</p><h3>Configuring the Eviction Policy</h3><p>We have a <strong><code>MessageEvictionStrategy</code></strong> which is used to decide which message should be evicted on a slow consumer. The default implementation is:</p><parameter ac:name="language">xml</parameter><plain-text-body><oldestMessageEvictionStrategy/>
</plain-text-body><p>However, you can write your own to use some application specific way of choosing messages for eviction. For example, if you are sending market data price updates you may wish to find an older price value, which might not be the oldest message.</p><p>Example:</p><parameter ac:name="language">xml</parameter><plain-text-body><uniquePropertyMessageEvictionStrategy propertyName="STOCK"/>
</plain-text-body><p>where <strong><code>propertyName</code></strong> is the JMS message property that specifies the price.</p><p>Another option could be to use the oldest message with the lowest priority message. Therefore if you have some high priority messages, evict the lower priority messages first even if they are newer.</p><parameter ac:name="language">xml</parameter><plain-text-body><oldestMessageWithLowestPriorityEvictionStrategy/>
-</plain-text-body><h2 id="SlowConsumerHandling-Example">Example</h2><p>The following example shows an ActiveMQ broker configuration file. Notice that for topics in the <strong><code>PRICES.></code></strong> wildcard range the <strong><code>pendingMessageLimitStrategy</code></strong> property is set to only keep around <strong><code>10</code></strong> messages for each consumer above their prefetch buffer size.</p><parameter ac:name="">xml</parameter><plain-text-body><beans xmlns="http://www.springframework.org/schema/beans"
+</plain-text-body><h2>Example</h2><p>The following example shows an ActiveMQ broker configuration file. Notice that for topics in the <strong><code>PRICES.></code></strong> wildcard range the <strong><code>pendingMessageLimitStrategy</code></strong> property is set to only keep around <strong><code>10</code></strong> messages for each consumer above their prefetch buffer size.</p><parameter ac:name="">xml</parameter><plain-text-body><beans xmlns="http://www.springframework.org/schema/beans"
xmlns:amq="http://activemq.apache.org/schema/core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
@@ -61,5 +61,5 @@
</policyMap>
</destinationPolicy>
</broker>
-</beans></plain-text-body><h2 id="SlowConsumerHandling-UsageTips">Usage Tips</h2><p> </p><rich-text-body><p>It is advisable that if you know a particular consumer is going to be slow then set its prefetch size to something smaller than the fast consumers!</p><p>For example, if you know a particular server is quite slow and you have very high message rates<em> and</em> you have some very fast consumers then you might want to enable this feature and set the prefetch on the slow servers to be a <em>little</em> lower than on the fast servers.</p></rich-text-body><h3 id="SlowConsumerHandling-MonitoringtheStatusofSlowConsumers">Monitoring the Status of Slow Consumers</h3><p>You can also use a <a shape="rect" href="jmx.xml">JMX</a> Console to view the statistics of the active subscriptions. This allows you to view the following statistics on a <strong><code>TopicSubscriptionViewMBean</code></strong>:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Statistic</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Definition</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>discarded</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The count of how many messages have been discarded during the lifetime of the subscription due to it being a slow consumer</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>matched</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The current number of messages matched and to be dispatched to the subscription as soon as some capacity is available in the prefetch buffer. So a non-zero value implies that the prefetch buffer is full for this subscription</p></td></tr></tbody></table></div></div>
+</beans></plain-text-body><h2>Usage Tips</h2><p> </p><rich-text-body><p>It is advisable that if you know a particular consumer is going to be slow then set its prefetch size to something smaller than the fast consumers!</p><p>For example, if you know a particular server is quite slow and you have very high message rates<em> and</em> you have some very fast consumers then you might want to enable this feature and set the prefetch on the slow servers to be a <em>little</em> lower than on the fast servers.</p></rich-text-body><h3>Monitoring the Status of Slow Consumers</h3><p>You can also use a <link><page ri:content-title="JMX"></page></link> Console to view the statistics of the active subscriptions. This allows you to view the following statistics on a <strong><code>TopicSubscriptionViewMBean</code></strong>:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Statistic</p></th><th colspan="1" rowspan="1"><p>Definition</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>discarded</code></p></td><td colspan="1" rowspan="1"><p>The count of how many messages have been discarded during the lifetime of the subscription due to it being a slow consumer</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>matched</code></p></td><td colspan="1" rowspan="1"><p>The current number of messages matched and to be dispatched to the subscription as soon as some capacity is available in the prefetch buffer. So a non-zero value implies that the prefetch buffer is full for this subscription</p></td></tr></tbody></table></div>
diff --git a/slow-consumers.xml b/slow-consumers.xml
index 76723bc..e12a372 100644
--- a/slow-consumers.xml
+++ b/slow-consumers.xml
@@ -1,22 +1,22 @@
<div class="wiki-content maincontent">
-<h2 id="SlowConsumers-BlockedTransport">Blocked Transport</h2>
+<h2>Blocked Transport</h2>
<p>when using TCP there can be occasions when a network outage can result in a blocked write. This can cause the entire broker to freeze - and the socket may never be unblocked. Currently we have a Thread that checks for blocked sockets - using a sweep protocol to detect if there are connections that are blocked writing for more than a configurable period. This can work but there is no way to unblock the calling thread that is associated with the send down the socket (which will be the publishing thread in non-durable topics).</p>
-<div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Need to check if closing out the socket unblock the send.</p></div></div>
+<structured-macro ac:macro-id="398bd1a2-5c6b-448e-a7a5-f119ded4da45" ac:name="note" ac:schema-version="1"><rich-text-body>
+<p>Need to check if closing out the socket unblock the send.</p></rich-text-body></structured-macro>
<p>TCP transports also use the InactivityMontor class as TransportFilter which detects dead sockets by forcing KeepAliveInfo commands periodically through the transport when it is idle. Therefore, the InactivityMontor can assume that if packets are not being received periodically, it means that the transport is dead and transport exception is generated.</p>
-<h2 id="SlowConsumers-BlockedConsumer">Blocked Consumer</h2>
+<h2>Blocked Consumer</h2>
<p>This is slightly different from above - The Consumer is blocked or very slow in processing a message. On the Client side the limit to how many messages a connection can hold is limited by the pre-fetch (which for non-durable topics is in the thousands).</p>
-<h2 id="SlowConsumers-BackgroundonSlowConsumers">Background on Slow Consumers</h2>
+<h2>Background on Slow Consumers</h2>
<p>Slow consumers can cause problems in the broker. Here's the various things we can do.</p>
<p>In general slow consumers don't affect queues that much as consumers compete for messages; so a slow consumer just gets less than the others.</p>
-<h3 id="SlowConsumers-Non-DurableTopics">Non-Durable Topics</h3>
+<h3>Non-Durable Topics</h3>
<p>Non-durable topics are the scenario which is most affected by slow consumers since the messages are not persistent and messages generally go to all consumers (who have a valid selector)</p>
@@ -26,16 +26,16 @@
<p>These will be exposed as a pluggable policy for the user. It might be worth doing one on a destination by destination basis?</p>
-<h3 id="SlowConsumers-DurableTopics">Durable Topics</h3>
+<h3>Durable Topics</h3>
<p>We can drop messages from RAM since they are persistent so we can deal with slow consumers well (assuming you have enough disk).<br clear="none">
If consumers get too far behind we could consider killing consumers; but I think thats more of a background operator issue?</p>
-<h3 id="SlowConsumers-Durablequeues">Durable queues</h3>
+<h3>Durable queues</h3>
<p>Since all messages are persisted, they can be evicted from memory.</p>
-<h3 id="SlowConsumers-Non-durablequeues">Non-durable queues</h3>
+<h3>Non-durable queues</h3>
<p>A slow consumer is not really an issue with queues. But all of the consumers being slow is. In this case we eventually block the producer until messages are consumed.</p>
@@ -43,7 +43,7 @@
<ul><li>spool messages to disk</li><li>discard messages</li></ul>
-<h2 id="SlowConsumers-ImplementationSolutions">Implementation Solutions</h2>
+<h2>Implementation Solutions</h2>
<p>For persistent messages: Introduce a different dispatching model where we have a thread per destination with it's own memory allocation. This would allow us more control over dispatching, and allow us to set different priorities to different destinations.</p>
@@ -60,7 +60,7 @@
<p> </p>
-<h3 id="SlowConsumers-SlowConsumerDetector">Slow Consumer Detector</h3>
+<h3>Slow Consumer Detector</h3>
<p>We need a good way of detecting that a consumer is slow - together with knowing when the consumer speeds up again</p></div>
diff --git a/slow-networks-drop-large-messages.xml b/slow-networks-drop-large-messages.xml
index d695391..c86525a 100644
--- a/slow-networks-drop-large-messages.xml
+++ b/slow-networks-drop-large-messages.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><div class="confluence-information-macro confluence-information-macro-note"><p class="title">Note</p><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p> This article only applies to older versions of ActiveMQ, i.e. 5.3 and 5.4.0. From 5.4.2 onwards this issue has been adressed in the bugs <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-2511">AMQ-2511</a> and <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-2088">AMQ-2088</a>. </p></div></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="e2358d29-392c-4d4e-ad46-a9bc2b143363" ac:name="note" ac:schema-version="1"><parameter ac:name="title">Note</parameter><rich-text-body><p> This article only applies to older versions of ActiveMQ, i.e. 5.3 and 5.4.0. From 5.4.2 onwards this issue has been adressed in the bugs <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-2511">AMQ-2511</a> and <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-2088">AMQ-2088</a>. </p></rich-text-body></structured-macro>
<p>You may experience problems sending large messages using networks across slow links.</p>
<p>The symptoms are usually that the network connection will be dropped and continuously re-established.</p>
-<p>This problem arises because the ActiveMQ message broker continuously checks for activity on a socket, and whilst building a large message in the TCP socket buffer, the <a shape="rect" href="activemq-inactivitymonitor.xml">inactivity</a> monitor will time out - see <a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a> and the <a shape="rect" href="tcp-transport-reference.xml">TCP Transport Reference</a>.<br clear="none">
-The <a shape="rect" href="activemq-inactivitymonitor.xml">inactivity monitor</a> uses an activity flag that is only updated after a message is received (in case the connection is not idle).<br clear="none">
+<p>This problem arises because the ActiveMQ message broker continuously checks for activity on a socket, and whilst building a large message in the TCP socket buffer, the <link><page ri:content-title="ActiveMQ InactivityMonitor"></page><link-body>inactivity</link-body></link> monitor will time out - see <link><page ri:content-title="Configuring Wire Formats"></page></link> and the <link><page ri:content-title="TCP Transport Reference"></page></link>.<br clear="none">
+The <link><page ri:content-title="ActiveMQ InactivityMonitor"></page><link-body>inactivity monitor</link-body></link> uses an activity flag that is only updated after a message is received (in case the connection is not idle).<br clear="none">
The monitor then clears the activity flag, waits the timeout amount and peeks at the activity flag. If it's still cleared, then we assume the connection was inactive. When the connection is NOT in use, a keep alive message is sent. But in case the connection is in use because of a larger message being sent/received, no keep alive will be sent and the activity flag will not be updated. That can lead to inactivity timeouts.<br clear="none">
Ideally the activity flag would get cleared every time a few bytes arrive from the network... but right now it is only cleared when an entire message is assembled.</p>
@@ -12,19 +12,18 @@
<p>e.g. configure your network connection like this:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
+<structured-macro ac:macro-id="fd790009-2e60-4165-b17f-51be3cb3ee05" ac:name="code" ac:schema-version="1"><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<beans xmlns="http://activemq.org/config/1.0">
- <broker brokerName="receiver">
+ <broker brokerName="receiver">
<transportConnectors>
- <transportConnector uri="tcp://localhost:62002"/>
+ <transportConnector uri="tcp://localhost:62002"/>
</transportConnectors>
<networkConnectors>
- <networkConnector uri="static:(tcp://somehost:62001?wireFormat.maxInactivityDuration=0)"/>
+ <networkConnector uri="static:(tcp://somehost:62001?wireFormat.maxInactivityDuration=0)"/>
</networkConnectors>
<persistenceAdapter>
@@ -33,9 +32,8 @@
</broker>
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="Slownetworksdroplargemessages-Seealso">See also</h3>
-<p><a shape="rect" href="activemq-inactivitymonitor.xml">ActiveMQ InactivityMonitor</a></p></div>
+<h3>See also</h3>
+<p><link><page ri:content-title="ActiveMQ InactivityMonitor"></page></link></p></div>
diff --git a/source-xref.xml b/source-xref.xml
index 3abf8ca..975fca2 100644
--- a/source-xref.xml
+++ b/source-xref.xml
@@ -1,2 +1,3 @@
-<div class="wiki-content maincontent"><ul><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/xref/">ActiveMQ Core</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-ra/xref/">ActiveMQ Resource Adapter</a></li><li><a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-web/xref/">ActiveMQ Web</a></li></ul></div>
+<div class="wiki-content maincontent"><ul><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-core/xref/">ActiveMQ Core</a></li><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-ra/xref/">ActiveMQ Resource Adapter</a></li><li><a shape="rect" href="http://activemq.apache.org/maven/activemq-web/xref/">ActiveMQ Web</a></li></ul>
+</div>
diff --git a/source.xml b/source.xml
index c0e962e..883ef41 100644
--- a/source.xml
+++ b/source.xml
@@ -1,12 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="Source-ActiveMQ5">ActiveMQ 5</h1><h2 id="Source-WebBrowsingofthegitRepo">Web Browsing of the git Repo</h2><p>To browse via the web:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git">https://git-wip-us.apache.org/repos/asf?p=activemq.git</a></p>
-</div></div><h2 id="Source-CheckingoutfromthegitRepo">Checking out from the git Repo</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq.git">https://git-wip-us.apache.org/repos/asf/activemq.git</a></p>
-</div></div><p>Only project developers can commit to the git repo via this method. SSH must be installed on your client machine. Enter your site password when prompted.</p><h2 id="Source-Buildingthecode">Building the code</h2><p>To then build the code, see <a shape="rect" href="building.xml">Building</a>.</p><p> </p><h1 id="Source-ActiveMQArtemis">ActiveMQ Artemis</h1><h2 id="Source-WebBrowsingoftheASFgitRepo">Web Browsing of the ASF git Repo</h2><p>To browse via the web:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git">https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git</a></p>
-</div></div><h2 id="Source-BrowsingtheGithubRepo">Browsing the Github Repo </h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">https://github.com/apache/activemq-artemis</a></p>
-</div></div><h2 id="Source-CheckingoutfromtheGithubRepo">Checking out from the Github Repo</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">https://github.com/apache/activemq-artemis</a></p>
-</div></div><p><strong>Committers:</strong> Please follow the instructions for properly configuring the <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/SUMMARY.md" rel="nofollow">Instructions for Core Contributors/Hacking Guide</a></p><p><strong>Contributors:</strong> Please create a <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">pull request</a> to contribute changes to the source code. </p><h2 id="Source-Buildingthecode.1">Building the code</h2><p>To then build the code, take a look at <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/building.md" rel="nofollow">Building the distribution</a></p></div>
+<div class="wiki-content maincontent"><h1>ActiveMQ 5</h1><h2>Web Browsing of the git Repo</h2><p>To browse via the web:</p><structured-macro ac:macro-id="f4ecef8e-93fd-4f7e-a460-d2d2cfd7b688" ac:name="panel" ac:schema-version="1"><rich-text-body><p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git">https://git-wip-us.apache.org/repos/asf?p=activemq.git</a></p></rich-text-body></structured-macro><h2>Checking out from the git Repo</h2><structured-macro ac:macro-id="6316f7d8-b6df-45fb-91a0-fbea891ff0e7" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq.git">https://git-wip-us.apache.org/repos/asf/activemq.git</a></p></rich-text-body></structured-macro><p>Only project developers can commit to the git repo via this method. SSH must be installed on your client machine. Enter your site password when prompted.</p><h2>Building the code</h2><p>To then build the code, see <link><page ri:content-title="Building"></page></link>.</p><p> </p><h1>ActiveMQ Artemis</h1><h2>Web Browsing of the ASF git Repo</h2><p>To browse via the web:</p><structured-macro ac:macro-id="ea717559-d943-46ac-b20a-59a4d3362f16" ac:name="panel" ac:schema-version="1"><rich-text-body><p><a shape="rect" href="https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git">https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git</a></p></rich-text-body></structured-macro><h2>Browsing the Github Repo </h2><structured-macro ac:macro-id="07e8348d-fd9a-4fc5-8c04-c690f71dc973" ac:name="panel" ac:schema-version="1"><rich-text-body><p><a shape="rect" href="https://github.com/apache/activemq-artemis">https://github.com/apache/activemq-artemis</a></p></rich-text-body></structured-macro><h2>Checking out from the Github Repo</h2><structured-macro ac:macro-id="a729b0da-d3ef-4a95-80aa-2c8e3b8165b9" ac:name="panel" ac:schema-version="1"><rich-text-body><p>git clone <a shape="rect" href="https://github.com/apache/activemq-artemis">https://github.com/apache/activemq-artemis</a></p></rich-text-body></structured-macro><p><strong>Committers:</strong> Please follow the instructions for properly configuring the <a shape="rect" href="https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/SUMMARY.md">Instructions for Core Contributors/Hacking Guide</a></p><p><strong>Contributors:</strong> Please create a <a shape="rect" href="https://github.com/apache/activemq-artemis">pull request</a> to contribute changes to the source code. </p><h2>Building the code</h2><p>To then build the code, take a look at <a shape="rect" href="https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/building.md">Building the distribution</a></p></div>
diff --git a/sponsorship.xml b/sponsorship.xml
index c708594..c0e2f46 100644
--- a/sponsorship.xml
+++ b/sponsorship.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>Thank you to <a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">all the folks</a> who have <a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">sponsored</a> the Apache Software Foundation. </p>
+<div class="wiki-content maincontent"><p>Thank you to <a shape="rect" href="http://www.apache.org/foundation/thanks.html">all the folks</a> who have <a shape="rect" href="http://www.apache.org/foundation/sponsorship.html">sponsored</a> the Apache Software Foundation. </p>
-<p>Want to help sponsor the foundation? <a shape="rect" class="external-link" href="http://www.apache.org/foundation/sponsorship.html">Click here for more info</a>.</p></div>
+<p>Want to help sponsor the foundation? <a shape="rect" href="http://www.apache.org/foundation/sponsorship.html">Click here for more info</a>.</p></div>
diff --git a/spring-support.xml b/spring-support.xml
index d19ec02..20acbcc 100644
--- a/spring-support.xml
+++ b/spring-support.xml
@@ -1,40 +1,33 @@
-<div class="wiki-content maincontent"><p>We fully support Spring for configuration of the JMS client side as well as for configuring the JMS Message Broker.<br clear="none"> There is a great <a shape="rect" class="external-link" href="http://codedependents.com/2009/10/16/efficient-lightweight-jms-with-spring-and-activemq/" rel="nofollow">article</a> on using Spring with ActiveMQ - I'd recommend reading it first.</p><h2 id="SpringSupport-ConfiguringtheJMSclient">Configuring the JMS client</h2><p>To configure an ActiveMQ JMS client in Spring it is just a simple matter of configuring an instance of ActiveMQConnectionFactory within a standard Spring XML configuration file like any other bean. There are <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/spring/">several examples and test cases</a> available and <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/xbean/spring.xml">this one</a> shows how to construct an ActiveMQConnectionFactory in Spring which is then passed into a Spring JmsTemplate for use by some POJOs.</p><p>e.g. the following fragment of XML shows us creating a JMS connection factory for ActiveMQ connecting to a remote broker on a specific host name and port.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="jmsFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL">
+<div class="wiki-content maincontent"><p>We fully support Spring for configuration of the JMS client side as well as for configuring the JMS Message Broker.<br clear="none"> There is a great <a shape="rect" href="http://codedependents.com/2009/10/16/efficient-lightweight-jms-with-spring-and-activemq/">article</a> on using Spring with ActiveMQ - I'd recommend reading it first.</p><h2>Configuring the JMS client</h2><p>To configure an ActiveMQ JMS client in Spring it is just a simple matter of configuring an instance of ActiveMQConnectionFactory within a standard Spring XML configuration file like any other bean. There are <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/spring/">several examples and test cases</a> available and <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/xbean/spring.xml">this one</a> shows how to construct an ActiveMQConnectionFactory in Spring which is then passed into a Spring JmsTemplate for use by some POJOs.</p><p>e.g. the following fragment of XML shows us creating a JMS connection factory for ActiveMQ connecting to a remote broker on a specific host name and port.</p><structured-macro ac:macro-id="6b350c16-e02b-4b9c-ae89-0c6d63a34f67" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><bean id="jmsFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL">
<value>tcp://localhost:61616</value>
</property>
</bean>
-]]></script>
-</div></div><p>The following shows how to use Zeroconf to discover the available brokers to connect to.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="jmsFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL">
+</plain-text-body></structured-macro><p>The following shows how to use Zeroconf to discover the available brokers to connect to.</p><structured-macro ac:macro-id="1bb25c22-6ae3-4534-b2d5-aa173d68a571" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><bean id="jmsFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL">
<value>zeroconf://_activemq.broker.development.</value>
</property>
</bean>
-]]></script>
-</div></div><p>From 1.1 of ActiveMQ onwards you can also use JNDI to configure ActiveMQ within Spring. <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/spring-jndi.xml">This example</a> shows how to configure Spring using ActiveMQ's <a shape="rect" href="jndi-support.xml">JNDI Support</a>.</p><h3 id="SpringSupport-UsingSpring">Using Spring</h3><p>If you are using the new <a shape="rect" class="external-link" href="http://static.springframework.org/spring/docs/2.0.x/reference/xsd-config.html" rel="nofollow">XML Schema-based configuration</a> of Spring 2.0 you can embed the ActiveMQ broker XML inside any regular Spring.xml file without requiring the above factory bean. e.g. here is an example of a regular Spring XML file in Spring 2.0 which also configures a broker.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans
- xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
+</plain-text-body></structured-macro><p>From 1.1 of ActiveMQ onwards you can also use JNDI to configure ActiveMQ within Spring. <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/resources/spring-jndi.xml">This example</a> shows how to configure Spring using ActiveMQ's <link><page ri:content-title="JNDI Support"></page></link>.</p><h3>Using Spring</h3><p>If you are using the new <a shape="rect" href="http://static.springframework.org/spring/docs/2.0.x/reference/xsd-config.html">XML Schema-based configuration</a> of Spring 2.0 you can embed the ActiveMQ broker XML inside any regular Spring.xml file without requiring the above factory bean. e.g. here is an example of a regular Spring XML file in Spring 2.0 which also configures a broker.</p><structured-macro ac:macro-id="274a6400-3e58-4239-9a63-9514b52498ff" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><beans
+ xmlns="http://www.springframework.org/schema/beans"
+ xmlns:amq="http://activemq.apache.org/schema/core"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+ http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
- <amq:broker useJmx="false" persistent="false">
+ <amq:broker useJmx="false" persistent="false">
<amq:transportConnectors>
- <amq:transportConnector uri="tcp://localhost:0" />
+ <amq:transportConnector uri="tcp://localhost:0" />
</amq:transportConnectors>
</amq:broker>
- <amq:connectionFactory id="jmsFactory" brokerURL="vm://localhost"/>
+ <amq:connectionFactory id="jmsFactory" brokerURL="vm://localhost"/>
</beans>
-]]></script>
-</div></div><p>This allows you to configure JMS artifacts like destinations and connection factories together with the entire broker.</p><h2 id="SpringSupport-WorkingwithSpring'sJmsTemplate">Working with Spring's JmsTemplate</h2><p>Spring supports a handy abstraction, JmsTemplate, which allows you to hide some of the lower level JMS details when sending messages etc.</p><p>Please be aware that there are a number of <a shape="rect" href="jmstemplate-gotchas.xml">JmsTemplate Gotchas</a> to be careful of.</p><p>One thing to bear in mind with JmsTemplate is that by default it will create a new connection, session, producer for each message sent - then close them all down again. This is very inefficient! It is done like this to work in EJB containers which tend to use a special ConnectionFactory which does pooling.</p><p>If you are not using a JCA container to manage your JMS connections, we recommend you use our pooling JMS connection provider, (org.apache.activemq.pool.PooledConnectionFactory) from the <code>activemq-pool</code> library, which will pool the JMS resources to work efficiently with Spring's JmsTemplate or with EJBs.</p><p>e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<!-- a pooling based JMS provider -->
- <bean id="jmsFactory" class="org.apache.activemq.pool.PooledConnectionFactory" destroy-method="stop">
- <property name="connectionFactory">
- <bean class="org.apache.activemq.ActiveMQConnectionFactory">
- <property name="brokerURL">
+</plain-text-body></structured-macro><p>This allows you to configure JMS artifacts like destinations and connection factories together with the entire broker.</p><h2>Working with Spring's JmsTemplate</h2><p>Spring supports a handy abstraction, JmsTemplate, which allows you to hide some of the lower level JMS details when sending messages etc.</p><p>Please be aware that there are a number of <link><page ri:content-title="JmsTemplate Gotchas"></page></link> to be careful of.</p><p>One thing to bear in mind with JmsTemplate is that by default it will create a new connection, session, producer for each message sent - then close them all down again. This is very inefficient! It is done like this to work in EJB containers which tend to use a special ConnectionFactory which does pooling.</p><p>If you are not using a JCA container to manage your JMS connections, we recommend you use our pooling JMS connection provider, (org.apache.activemq.pool.PooledConnectionFactory) from the <code>activemq-pool</code> library, which will pool the JMS resources to work efficiently with Spring's JmsTemplate or with EJBs.</p><p>e.g.</p><structured-macro ac:macro-id="aa39875d-0c29-419b-8302-b1e5feea7803" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><!-- a pooling based JMS provider -->
+ <bean id="jmsFactory" class="org.apache.activemq.pool.PooledConnectionFactory" destroy-method="stop">
+ <property name="connectionFactory">
+ <bean class="org.apache.activemq.ActiveMQConnectionFactory">
+ <property name="brokerURL">
<value>tcp://localhost:61616</value>
</property>
</bean>
@@ -42,11 +35,10 @@
</bean>
<!-- Spring JMS Template -->
- <bean id="myJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
- <property name="connectionFactory">
- <ref local="jmsFactory"/>
+ <bean id="myJmsTemplate" class="org.springframework.jms.core.JmsTemplate">
+ <property name="connectionFactory">
+ <ref local="jmsFactory"/>
</property>
</bean>
-]]></script>
-</div></div><p>The <code>PooledConnectionFactory</code> supports the pooling of Connection, Session and MessageProducer instances so it can be used with tools like <a shape="rect" class="external-link" href="http://camel.apache.org/activemq.html">Camel</a> and Spring's <a shape="rect" class="external-link" href="http://activemq.apache.org/spring-support.html">JmsTemplate and MessagListenerContainer </a>. Connections, sessions and producers are returned to a pool after use so that they can be reused later without having to undergo the cost of creating them again.</p><p>Note: while the <code>PooledConnectionFactory</code> does allow the creation of a collection of active consumers, it does not 'pool' consumers. Pooling makes sense for connections, sessions and producers, which can be seldom-used resources, are expensive to create and can remain idle a minimal cost. Consumers, on the other hand, are usually just created at startup and left going, handling incoming messages as they come. When a consumer is complete, it's preferred to shut down it down rather than leave it idle and return it to a pool for later reuse: this is because, even if the consumer is idle, ActiveMQ will keep delivering messages to the consumer's prefetch buffer, where they'll get held up until the consumer is active again.</p><p>If you are creating a collection of consumers (for example, for multi-threaded message consumption), you should consider keeping a low prefetch value (e.g. 10 or 20), to ensure that all messages don't end up going to just one of the consumers.</p><p>We do also have a pooling JMS ConnectionFactory for use inside a JCA / MDB container (org.apache.activemq.ra.InboundConnectionProxyFactory), when using our JCA Resource Adapter which will reuse the same JMS connection/session which is being used for inbound messages.</p><h2 id="SpringSupport-ConsumingJMSfrominsideSpring">Consuming JMS from inside Spring</h2><p>Spring's <a shape="rect" class="external-link" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-mdp" rel="nofollow">MessagListenerContainer</a> should be used for message consumption. This provides all the power of MDBs - efficient JMS consumption and pooling of the message listeners - but without requiring a full EJB container.</p><p>You can use the <code>activemq-pool</code> <code>org.apache.activemq.pool.PooledConnectionFactory</code> for efficient pooling of the connections and sessions for your collection of consumers, or you can use the Spring JMS <code>org.springframework.jms.connection.CachingConnectionFactory</code> to achieve the same effect.</p><h2 id="SpringSupport-MoreInformation">More Information</h2><p>Also check out the following blogs for information about using Spring JMS with ActiveMQ:</p><ul><li><a shape="rect" class="external-link" href="http://codedependents.com/2010/03/04/synchronous-request-response-with-activemq-and-spring/" rel="nofollow">Synchronous Request Response with ActiveMQ and Spring</a></li><li><a shape="rect" class="external-link" href="http://bsnyderblog.blogspot.com/2010/02/using-spring-jmstemplate-to-send-jms.html" rel="nofollow">Using Spring to Send JMS Messages</a></li><li><a shape="rect" class="external-link" href="http://bsnyderblog.blogspot.com/2010/02/using-spring-to-receive-jms-messages.html" rel="nofollow">Using Spring to Receive JMS Messages</a></li><li><a shape="rect" class="external-link" href="http://bsnyderblog.blogspot.com/2010/05/tuning-jms-message-consumption-in.html" rel="nofollow">Tuning JMS Message Consumption In Spring</a></li></ul></div>
+</plain-text-body></structured-macro><p>The <code>PooledConnectionFactory</code> supports the pooling of Connection, Session and MessageProducer instances so it can be used with tools like <a shape="rect" href="http://camel.apache.org/activemq.html">Camel</a> and Spring's <a shape="rect" href="http://activemq.apache.org/spring-support.html">JmsTemplate and MessagListenerContainer </a>. Connections, sessions and producers are returned to a pool after use so that they can be reused later without having to undergo the cost of creating them again.</p><p>Note: while the <code>PooledConnectionFactory</code> does allow the creation of a collection of active consumers, it does not 'pool' consumers. Pooling makes sense for connections, sessions and producers, which can be seldom-used resources, are expensive to create and can remain idle a minimal cost. Consumers, on the other hand, are usually just created at startup and left going, handling incoming messages as they come. When a consumer is complete, it's preferred to shut down it down rather than leave it idle and return it to a pool for later reuse: this is because, even if the consumer is idle, ActiveMQ will keep delivering messages to the consumer's prefetch buffer, where they'll get held up until the consumer is active again.</p><p>If you are creating a collection of consumers (for example, for multi-threaded message consumption), you should consider keeping a low prefetch value (e.g. 10 or 20), to ensure that all messages don't end up going to just one of the consumers.</p><p>We do also have a pooling JMS ConnectionFactory for use inside a JCA / MDB container (org.apache.activemq.ra.InboundConnectionProxyFactory), when using our JCA Resource Adapter which will reuse the same JMS connection/session which is being used for inbound messages.</p><h2>Consuming JMS from inside Spring</h2><p>Spring's <a shape="rect" href="http://static.springsource.org/spring/docs/2.5.x/reference/jms.html#jms-mdp">MessagListenerContainer</a> should be used for message consumption. This provides all the power of MDBs - efficient JMS consumption and pooling of the message listeners - but without requiring a full EJB container.</p><p>You can use the <code>activemq-pool</code> <code>org.apache.activemq.pool.PooledConnectionFactory</code> for efficient pooling of the connections and sessions for your collection of consumers, or you can use the Spring JMS <code>org.springframework.jms.connection.CachingConnectionFactory</code> to achieve the same effect.</p><h2>More Information</h2><p>Also check out the following blogs for information about using Spring JMS with ActiveMQ:</p><ul><li><a shape="rect" href="http://codedependents.com/2010/03/04/synchronous-request-response-with-activemq-and-spring/">Synchronous Request Response with ActiveMQ and Spring</a></li><li><a shape="rect" href="http://bsnyderblog.blogspot.com/2010/02/using-spring-jmstemplate-to-send-jms.html">Using Spring to Send JMS Messages</a></li><li><a shape="rect" href="http://bsnyderblog.blogspot.com/2010/02/using-spring-to-receive-jms-messages.html">Using Spring to Receive JMS Messages</a></li><li><a shape="rect" href="http://bsnyderblog.blogspot.com/2010/05/tuning-jms-message-consumption-in.html">Tuning JMS Message Consumption In Spring</a></li></ul></div>
diff --git a/sqlserver.xml b/sqlserver.xml
index e144f8c..8075e77 100644
--- a/sqlserver.xml
+++ b/sqlserver.xml
@@ -1,67 +1,62 @@
-<div class="wiki-content maincontent"><h2 id="SQLServer-SQLServer">SQL Server</h2>
+<div class="wiki-content maincontent"><h2>SQL Server</h2>
-<h3 id="SQLServer-SQLServer2000Drivers">SQL Server 2000 Drivers </h3>
+<h3>SQL Server 2000 Drivers </h3>
<p>Here is an example of a configuration for SQLServer kindly supplied by Ning Li</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="68c6db6b-f866-4826-94a7-705146d7057e" ac:name="code" ac:schema-version="1"><plain-text-body>
<persistenceAdapter>
- <journaledJDBC journalLogFiles="5"
-dataDirectory="../activemq-data" dataSource="#mssql-ds">
+ <journaledJDBC journalLogFiles="5"
+dataDirectory="../activemq-data" dataSource="#mssql-ds">
<adapter><imageBasedJDBCAdaptor/></adapter>
</journaledJDBC>
</persistenceAdapter>
- <bean id="mssql-ds" class="org.apache.commons.dbcp.BasicDataSource"
-destroy-method="close">
- <property name="driverClassName"
-value="com.microsoft.jdbc.sqlserver.SQLServerDriver"/>
- <property name="url" value="jdbc:microsoft:sqlserver://HOSTNAME
-\\INSTANCE;DataBaseName=DBNAME"/>
- <property name="username" value="sa"/>
- <property name="password" value="password"/>
+ <bean id="mssql-ds" class="org.apache.commons.dbcp.BasicDataSource"
+destroy-method="close">
+ <property name="driverClassName"
+value="com.microsoft.jdbc.sqlserver.SQLServerDriver"/>
+ <property name="url" value="jdbc:microsoft:sqlserver://HOSTNAME
+\\INSTANCE;DataBaseName=DBNAME"/>
+ <property name="username" value="sa"/>
+ <property name="password" value="password"/>
</bean>
-]]></script>
-</div></div>
-<p>Information about the Microsoft SqlServer 2000 drivers can be found <a shape="rect" class="external-link" href="http://support.microsoft.com/kb/313100/" rel="nofollow">here</a></p>
+</plain-text-body></structured-macro>
+<p>Information about the Microsoft SqlServer 2000 drivers can be found <a shape="rect" href="http://support.microsoft.com/kb/313100/">here</a></p>
-<h3 id="SQLServer-SQLServer2005Drivers">SQL Server 2005 Drivers</h3>
+<h3>SQL Server 2005 Drivers</h3>
<p>Here is an example of the configuration for Microsoft SQL Server 2005 drivers</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="4153d4ca-cbd0-483a-981c-76bda5c2c0d5" ac:name="code" ac:schema-version="1"><plain-text-body>
<persistenceAdapter>
- <journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data" dataSource="#mssql-ds">
+ <journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data" dataSource="#mssql-ds">
<adapter><imageBasedJDBCAdaptor/></adapter>
</journaledJDBC>
</persistenceAdapter>
-<bean id="mssql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
- <property name="driverClassName" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
- <property name="url" value="jdbc:sqlserver://HOST:PORT;databaseName=DBNAME;user=USER;password=PASSWORD"/>
- <property name="username" value="USER"/>
- <property name="password" value="PASSWORD"/>
+<bean id="mssql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
+ <property name="driverClassName" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
+ <property name="url" value="jdbc:sqlserver://HOST:PORT;databaseName=DBNAME;user=USER;password=PASSWORD"/>
+ <property name="username" value="USER"/>
+ <property name="password" value="PASSWORD"/>
</bean>
-]]></script>
-</div></div>
-<p>Information about the Microsoft SqlServer 2005 drivers can be found <a shape="rect" class="external-link" href="http://msdn.microsoft.com/data/ref/jdbc/" rel="nofollow">here</a></p>
+</plain-text-body></structured-macro>
+<p>Information about the Microsoft SqlServer 2005 drivers can be found <a shape="rect" href="http://msdn.microsoft.com/data/ref/jdbc/">here</a></p>
-<h3 id="SQLServer-jTDSDrivers">jTDS Drivers</h3>
+<h3>jTDS Drivers</h3>
<p>Here's an example of the configuration for the jTDS drivers:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<bean id="mssql-ds" class="net.sourceforge.jtds.jdbcx.JtdsDataSource">
- <property name="serverName" value="SERVERNAME"/>
- <property name="portNumber" value="PORTNUMBER"/>
- <property name="databaseName" value="DATABASENAME"/>
- <property name="user" value="USER"/>
- <property name="password" value="PASSWORD"/>
+<structured-macro ac:macro-id="bb9583c5-c6e6-4128-b919-d4ffad77ab5e" ac:name="code" ac:schema-version="1"><plain-text-body>
+<bean id="mssql-ds" class="net.sourceforge.jtds.jdbcx.JtdsDataSource">
+ <property name="serverName" value="SERVERNAME"/>
+ <property name="portNumber" value="PORTNUMBER"/>
+ <property name="databaseName" value="DATABASENAME"/>
+ <property name="user" value="USER"/>
+ <property name="password" value="PASSWORD"/>
</bean>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>A note about the jTDS Drivers: Using both the JtdsDataSource and the DBCP BasicDataSource seem to result in client connection starvation on Windows. The JtdsDataSource is better behaved, though, i.e. it doesn't throw an exception. There is mileage in upping the maximum number of client ports and dropping the Tcp wait delay down to 30 seconds. Use RegEdit to add the following values:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Key </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Value </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> TcpTimedWaitDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> DWORD </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 30 (Decimal) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Reduces the time a connection spends in TIME_WAIT to 30 seconds </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> MaxUserPort </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> DWORD </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 32768 (Decimal) </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Increases the number of ports a client application can use to 32768 </p></td></tr></tbody></table></div></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Key </p></th><th colspan="1" rowspan="1"><p> Value </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> TcpTimedWaitDelay </p></td><td colspan="1" rowspan="1"><p> DWORD </p></td><td colspan="1" rowspan="1"><p> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters </p></td><td colspan="1" rowspan="1"><p> 30 (Decimal) </p></td><td colspan="1" rowspan="1"><p> Reduces the time a connection spends in TIME_WAIT to 30 seconds </p></td></tr><tr><td colspan="1" rowspan="1"><p> MaxUserPort </p></td><td colspan="1" rowspan="1"><p> DWORD </p></td><td colspan="1" rowspan="1"><p> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\TCPIP\Parameters </p></td><td colspan="1" rowspan="1"><p> 32768 (Decimal) </p></td><td colspan="1" rowspan="1"><p> Increases the number of ports a client application can use to 32768 </p></td></tr></tbody></table>
+</div>
diff --git a/ssl-transport-reference.xml b/ssl-transport-reference.xml
index c2e5ec2..959b998 100644
--- a/ssl-transport-reference.xml
+++ b/ssl-transport-reference.xml
@@ -1,27 +1,17 @@
-<div class="wiki-content maincontent"><h3 id="SSLTransportReference-TheSSLTransport">The SSL Transport</h3><p>The SSL transport allows clients to connect to a remote ActiveMQ broker using SSL over a TCP socket.</p><h4 id="SSLTransportReference-ConfigurationSyntax">Configuration Syntax</h4><p><strong>ssl://hostname:port?transportOptions</strong></p><h4 id="SSLTransportReference-TransportOptions">Transport Options</h4><p>The configuration options from <a shape="rect" href="tcp-transport-reference.xml">TCP</a> are relevant.</p><h4 id="SSLTransportReference-ExampleURI">Example URI</h4><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>ssl://localhost:61616?trace=false
-</pre>
-</div></div><h4 id="SSLTransportReference-SSLServerSocketoptions">SSLServerSocket options</h4><p>From version 5.4 any <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/api/javax/net/ssl/SSLServerSocket.html" rel="nofollow">SSLServerSocket</a> option may be set on a TransportConnection via <strong>?transport.XXX</strong>, for example:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>ssl://localhost:61616?transport.enabledCipherSuites=SSL_RSA_WITH_RC4_128_SHA,SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
+<div class="wiki-content maincontent"><h3>The SSL Transport</h3><p>The SSL transport allows clients to connect to a remote ActiveMQ broker using SSL over a TCP socket.</p><h4>Configuration Syntax</h4><p><strong>ssl://hostname:port?transportOptions</strong></p><h4>Transport Options</h4><p>The configuration options from <link><page ri:content-title="TCP Transport Reference"></page><plain-text-link-body>TCP</plain-text-link-body></link> are relevant.</p><h4>Example URI</h4><structured-macro ac:macro-id="6c15c74e-ae37-4e27-8bd7-389c92691762" ac:name="noformat" ac:schema-version="1"><plain-text-body>ssl://localhost:61616?trace=false
+</plain-text-body></structured-macro><h4>SSLServerSocket options</h4><p>From version 5.4 any <a shape="rect" href="http://java.sun.com/j2se/1.4.2/docs/api/javax/net/ssl/SSLServerSocket.html">SSLServerSocket</a> option may be set on a TransportConnection via <strong>?transport.XXX</strong>, for example:</p><structured-macro ac:macro-id="da6558b0-9572-4e6f-8e5e-1af659b3305e" ac:name="noformat" ac:schema-version="1"><plain-text-body>ssl://localhost:61616?transport.enabledCipherSuites=SSL_RSA_WITH_RC4_128_SHA,SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
ssl://localhost:61616?transport.needClientAuth=true
-</pre>
-</div></div><p> </p><h4 id="SSLTransportReference-Clientconfiguration">Client configuration</h4><p>JMS clients can simply use the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/5.9.0/apidocs/org/apache/activemq/ActiveMQSslConnectionFactory.html">ActiveMQSslConnectionFactory</a> together with an ssl:// broker url as the following Spring configuration illustrates</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<bean id="AMQJMSConnectionFactory" class="org.apache.activemq.ActiveMQSslConnectionFactory">
- <property name="trustStore" value="/path/to/truststore.ts" />
- <property name="trustStorePassword" value="password" />
- <property name="keyStore" value="/path/to/keystore.ks" />
- <property name="keyStorePassword" value="password" />
- <property name="brokerURL" value="ssl://localhost:61616" />
- <property name="userName" value="admin" />
- <property name="password" value="admin" />
+</plain-text-body></structured-macro><p> </p><h4>Client configuration</h4><p>JMS clients can simply use the <a shape="rect" href="http://activemq.apache.org/maven/5.9.0/apidocs/org/apache/activemq/ActiveMQSslConnectionFactory.html">ActiveMQSslConnectionFactory</a> together with an ssl:// broker url as the following Spring configuration illustrates</p><structured-macro ac:macro-id="e66bf756-3630-49f9-9c18-a34f6c528232" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<bean id="AMQJMSConnectionFactory" class="org.apache.activemq.ActiveMQSslConnectionFactory">
+ <property name="trustStore" value="/path/to/truststore.ts" />
+ <property name="trustStorePassword" value="password" />
+ <property name="keyStore" value="/path/to/keystore.ks" />
+ <property name="keyStorePassword" value="password" />
+ <property name="brokerURL" value="ssl://localhost:61616" />
+ <property name="userName" value="admin" />
+ <property name="password" value="admin" />
</bean>
-]]></script>
-</div></div><p>Unless the broker's SSL transport is configured for transport.needClientAuth=true, the client won't need a keystore but requires a truststore in order to validate the broker's certificate.</p><p>Similar to the broker transport configuration you can pass on SSL transport options using <strong>?socket.XXX</strong>, such as</p><pre>ssl://localhost:61616?socket.enabledCipherSuites=SSL_RSA_WITH_RC4_128_SHA,SSL_DH_anon_WITH_3DES_EDE_CBC_SHA</pre><h4 id="SSLTransportReference-OtherLinks">Other Links</h4><ul><li><a shape="rect" href="how-do-i-use-ssl.xml">How do I use SSL</a></li></ul><p>You can also turn on SSL debug informations this way by adding:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[-Djavax.net.debug=ssl
-]]></script>
-</div></div><p>this way you can see what goes wrong and why you get connections closed.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">"Be careful with multicast discovery"</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If your XML configuration file contains the following and you wish to use SSL</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <networkConnector uri="multicast://default"/>
-]]></script>
-</div></div><p>Then you will currently need to comment that out.<br clear="none"> The reason is to prevent ActiveMQ atempting to connect to itself - if you do this with a self-signed<br clear="none"> certificate, you will get a constant spam of certificate_unknown<br clear="none"> stacktraces to the console, as the broker is not configured with the<br clear="none"> truststore,</p></div></div></div>
+</plain-text-body></structured-macro><p>Unless the broker's SSL transport is configured for transport.needClientAuth=true, the client won't need a keystore but requires a truststore in order to validate the broker's certificate.</p><p>Similar to the broker transport configuration you can pass on SSL transport options using <strong>?socket.XXX</strong>, such as</p><pre>ssl://localhost:61616?socket.enabledCipherSuites=SSL_RSA_WITH_RC4_128_SHA,SSL_DH_anon_WITH_3DES_EDE_CBC_SHA</pre><h4>Other Links</h4><ul><li><link><page ri:content-title="How do I use SSL"></page></link></li></ul><p>You can also turn on SSL debug informations this way by adding:</p><structured-macro ac:macro-id="60cc214c-95c0-46ac-9d16-589497309ff5" ac:name="code" ac:schema-version="1"><plain-text-body>-Djavax.net.debug=ssl
+</plain-text-body></structured-macro><p>this way you can see what goes wrong and why you get connections closed.</p><structured-macro ac:macro-id="ed0bb968-b677-4fef-8132-ce41c9fc8dce" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">"Be careful with multicast discovery"</parameter><rich-text-body><p>If your XML configuration file contains the following and you wish to use SSL</p><structured-macro ac:macro-id="ae3f1c52-2314-40b4-b23e-a8c9da458e4c" ac:name="code" ac:schema-version="1"><plain-text-body> <networkConnector uri="multicast://default"/>
+</plain-text-body></structured-macro><p>Then you will currently need to comment that out.<br clear="none"> The reason is to prevent ActiveMQ atempting to connect to itself - if you do this with a self-signed<br clear="none"> certificate, you will get a constant spam of certificate_unknown<br clear="none"> stacktraces to the console, as the broker is not configured with the<br clear="none"> truststore,</p></rich-text-body></structured-macro></div>
diff --git a/static-transport-reference.xml b/static-transport-reference.xml
index 7f2c9a3..d50d100 100644
--- a/static-transport-reference.xml
+++ b/static-transport-reference.xml
@@ -1,24 +1,23 @@
-<div class="wiki-content maincontent"><h3 id="StaticTransportReference-TheStaticTransport">The Static Transport</h3>
+<div class="wiki-content maincontent"><h3>The Static Transport</h3>
<p>The static transport provides a hard coded mechanism to discover other connections using a list of URIs. A connection using this discovery mechanism will attempt to connect to all URIs in the list until it is succesful.</p>
-<h4 id="StaticTransportReference-ConfigurationSyntax">Configuration Syntax</h4>
+<h4>Configuration Syntax</h4>
<p><strong>static:(uri1,uri2,uri3,...)?options</strong></p>
-<h4 id="StaticTransportReference-ExampleURI">Example URI</h4>
+<h4>Example URI</h4>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>static:(tcp://localhost:61616,tcp://remotehost:61617?trace=false,vm://localbroker)?initialReconnectDelay=100
-</pre>
-</div></div>
+<structured-macro ac:macro-id="9abadd5a-ba82-42f6-9c39-d6ce7a4fbc14" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+static:(tcp://localhost:61616,tcp://remotehost:61617?trace=false,vm://localbroker)?initialReconnectDelay=100
+</plain-text-body></structured-macro>
-<h5 id="StaticTransportReference-Options">Options</h5>
+<h5>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> useExponentialBackOff </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> backOffMultiplier </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 2 </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> 0 </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 </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> minConnectTime </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 500 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> If a connaction fails faster than this amount of time then it is considered a connection failure </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default Value </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> initialReconnectDelay </p></td><td colspan="1" rowspan="1"><p> 10 </p></td><td colspan="1" rowspan="1"><p> How long to wait before the first reconnect attempt (in ms) </p></td></tr><tr><td colspan="1" rowspan="1"><p> maxReconnectDelay </p></td><td colspan="1" rowspan="1"><p> 30000 </p></td><td colspan="1" rowspan="1"><p> The maximum amount of time we ever wait between reconnect attempts (in ms) </p></td></tr><tr><td colspan="1" rowspan="1"><p> useExponentialBackOff </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> Should an exponential backoff be used btween reconnect attempts </p></td></tr><tr><td colspan="1" rowspan="1"><p> backOffMultiplier </p></td><td colspan="1" rowspan="1"><p> 2 </p></td><td colspan="1" rowspan="1"><p> The exponent used in the exponential backoff attempts </p></td></tr><tr><td colspan="1" rowspan="1"><p> maxReconnectAttempts </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> If not 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"><p> minConnectTime </p></td><td colspan="1" rowspan="1"><p> 500 </p></td><td colspan="1" rowspan="1"><p> If a connaction fails faster than this amount of time then it is considered a connection failure </p></td></tr></tbody></table>
-<h5 id="StaticTransportReference-Notes">Notes</h5>
+<h5>Notes</h5>
-<p>As the static transport protocol is for broker discovery, it should not be used by client programs. Clients wishing to failover to a static list of broker instances, should use the <a shape="rect" class="external-link" href="http://activemq.apache.org/failover-transport-reference.html">failover://</a> transport instead. </p></div>
+<p>As the static transport protocol is for broker discovery, it should not be used by client programs. Clients wishing to failover to a static list of broker instances, should use the <a shape="rect" href="http://activemq.apache.org/failover-transport-reference.html">failover://</a> transport instead. </p></div>
diff --git a/statisticsplugin.xml b/statisticsplugin.xml
index 0b97357..8f1bd29 100644
--- a/statisticsplugin.xml
+++ b/statisticsplugin.xml
@@ -1,15 +1,12 @@
-<div class="wiki-content maincontent"><p>Beginning in ActiveMQ 5.3, a statistics plugin is included that can be used to retrieve statistics from the broker or its destinations. Note that the message must contain a <code>replyTo</code> header (the <code>jmsReplyTo</code> header if you're using JMS) else the message will be ignored. The <code>replyTo</code> header must contain the name of the destination from which you want to retrieve the stats message(s). The statistics message is a <code>MapMessage</code> populated with statistics for the target (i.e., a broker or a destination).</p><p>To retrieve stats for the broker, just send an empty message to the destination named <code>ActiveMQ.Statistics.Broker</code> along with a <code>replyTo</code> header. To retrieve stats for a destination, just send an empty message to the destination named <code>ActiveMQ.Statistics.Destination.<destination-name></code> or <code>ActiveMQ.Statistics.Destination.<wildcard-expression></code> along with a <code>replyTo</code> header. If many destinations match a given wildcard expression, one stats message for each destination will be sent to the <code>replyTo</code> destination.</p><p>To configure ActiveMQ to use the statistics plugin, just add the following to the ActiveMQ XML configuration:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<broker ...>
+<div class="wiki-content maincontent"><p>Beginning in ActiveMQ 5.3, a statistics plugin is included that can be used to retrieve statistics from the broker or its destinations. Note that the message must contain a <code>replyTo</code> header (the <code>jmsReplyTo</code> header if you're using JMS) else the message will be ignored. The <code>replyTo</code> header must contain the name of the destination from which you want to retrieve the stats message(s). The statistics message is a <code>MapMessage</code> populated with statistics for the target (i.e., a broker or a destination).</p><p>To retrieve stats for the broker, just send an empty message to the destination named <code>ActiveMQ.Statistics.Broker</code> along with a <code>replyTo</code> header. To retrieve stats for a destination, just send an empty message to the destination named <code>ActiveMQ.Statistics.Destination.<destination-name></code> or <code>ActiveMQ.Statistics.Destination.<wildcard-expression></code> along with a <code>replyTo</code> header. If many destinations match a given wildcard expression, one stats message for each destination will be sent to the <code>replyTo</code> destination.</p><p>To configure ActiveMQ to use the statistics plugin, just add the following to the ActiveMQ XML configuration:</p><structured-macro ac:macro-id="9b833d54-8583-4209-be70-3b30ba65868e" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><broker ...>
<plugins>
<statisticsBrokerPlugin/>
</plugins>
</broker>
-]]></script>
-</div></div><p>The statistics plugin looks for messages sent to particular destinations. Below is an example of using the statistics plugin to grab stats from a broker:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Queue replyTo = session.createTemporaryQueue();
+</plain-text-body></structured-macro><p>The statistics plugin looks for messages sent to particular destinations. Below is an example of using the statistics plugin to grab stats from a broker:</p><structured-macro ac:macro-id="cd4e5c3d-a06e-4f86-b01c-1dc08211a541" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>Queue replyTo = session.createTemporaryQueue();
MessageConsumer consumer = session.createConsumer(replyTo);
-String queueName = "ActiveMQ.Statistics.Broker";
+String queueName = "ActiveMQ.Statistics.Broker";
Queue testQueue = session.createQueue(queueName);
MessageProducer producer = session.createProducer(testQueue);
Message msg = session.createMessage();
@@ -21,19 +18,15 @@
for (Enumeration e = reply.getMapNames();e.hasMoreElements();) {
String name = e.nextElement().toString();
- System.out.println(name + "=" + reply.getObject(name));
+ System.out.println(name + "=" + reply.getObject(name));
}
-]]></script>
-</div></div><p>The output from the code above is shown below:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>vm=vm://localhost<br clear="none"> memoryUsage=0<br clear="none"> storeUsage=3330<br clear="none"> tempPercentUsage=0<br clear="none"> ssl=<br clear="none"> openwire=tcp://localhost:50059<br clear="none"> brokerId=ID:bigmac-50057-1253605065511-0:0<br clear="none"> consumerCount=2<br clear="none"> brokerName=localhost<br clear="none"> expiredCount=0<br clear="none"> dispatchCount=1<br clear="none"> maxEnqueueTime=5.0<br clear="none"> storePercentUsage=0<br clear="none"> dequeueCount=0<br clear="none"> inflightCount=1<br clear="none"> messagesCached=0<br clear="none"> tempLimit=107374182400<br clear="none"> averageEnqueueTime=5.0<br clear="none"> stomp+ssl=<br clear="none"> memoryPercentUsage=0<br clear="none"> size=10<br clear="none"> tempUsage=0<br clear="none"> producerCount=1<br clear="none"> minEnqueueTime=5.0<br clear="none"> dataDirectory=/Users/rajdavies/dev/projects/activemq/activemq-core/activemq-data<br clear="none"> enqueueCount=10<br clear="none"> stomp=<br clear="none"> storeLimit=107374182400<br clear="none"> memoryLimit=67108864</p>
-</div></div><p>Similarly, to query the statistics for a destination just send a message to the destination name prepended with <code>ActiveMQ.Statistics.Destination</code>. For example, to retrieve the statistics for a queue whose name is TEST.FOO, send an empty message to the queue named <code>ActiveMQ.Statistics.Destination.TEST.FOO</code>. Below is an example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Queue replyTo = session.createTemporaryQueue();
+</plain-text-body></structured-macro><p>The output from the code above is shown below:</p><structured-macro ac:macro-id="f559467a-2966-41d1-abd6-e5c7963b3a4e" ac:name="panel" ac:schema-version="1"><rich-text-body><p>vm=vm://localhost<br clear="none"> memoryUsage=0<br clear="none"> storeUsage=3330<br clear="none"> tempPercentUsage=0<br clear="none"> ssl=<br clear="none"> openwire=tcp://localhost:50059<br clear="none"> brokerId=ID:bigmac-50057-1253605065511-0:0<br clear="none"> consumerCount=2<br clear="none"> brokerName=localhost<br clear="none"> expiredCount=0<br clear="none"> dispatchCount=1<br clear="none"> maxEnqueueTime=5.0<br clear="none"> storePercentUsage=0<br clear="none"> dequeueCount=0<br clear="none"> inflightCount=1<br clear="none"> messagesCached=0<br clear="none"> tempLimit=107374182400<br clear="none"> averageEnqueueTime=5.0<br clear="none"> stomp+ssl=<br clear="none"> memoryPercentUsage=0<br clear="none"> size=10<br clear="none"> tempUsage=0<br clear="none"> producerCount=1<br clear="none"> minEnqueueTime=5.0<br clear="none"> dataDirectory=/Users/rajdavies/dev/projects/activemq/activemq-core/activemq-data<br clear="none"> enqueueCount=10<br clear="none"> stomp=<br clear="none"> storeLimit=107374182400<br clear="none"> memoryLimit=67108864</p></rich-text-body></structured-macro><p>Similarly, to query the statistics for a destination just send a message to the destination name prepended with <code>ActiveMQ.Statistics.Destination</code>. For example, to retrieve the statistics for a queue whose name is TEST.FOO, send an empty message to the queue named <code>ActiveMQ.Statistics.Destination.TEST.FOO</code>. Below is an example:</p><structured-macro ac:macro-id="abaf6b69-f295-48d4-bf25-62fcb51cca54" ac:name="code" ac:schema-version="1"><plain-text-body>Queue replyTo = session.createTemporaryQueue();
MessageConsumer consumer = session.createConsumer(replyTo);
-Queue testQueue = session.createQueue("TEST.FOO");
+Queue testQueue = session.createQueue("TEST.FOO");
MessageProducer producer = session.createProducer(null);
-String queueName = "ActiveMQ.Statistics.Destination." + testQueue.getQueueName()
+String queueName = "ActiveMQ.Statistics.Destination." + testQueue.getQueueName()
Queue query = session.createQueue(queueName);
Message msg = session.createMessage();
@@ -47,16 +40,12 @@
for (Enumeration e = reply.getMapNames();e.hasMoreElements();) {
String name = e.nextElement().toString();
- System.err.println(name + "=" + reply.getObject(name));
+ System.err.println(name + "=" + reply.getObject(name));
}
-]]></script>
-</div></div><p>The output from the code above is shown below:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>memoryUsage=0<br clear="none"> dequeueCount=0<br clear="none"> inflightCount=0<br clear="none"> messagesCached=0<br clear="none"> averageEnqueueTime=0.0<br clear="none"> destinationName=queue://TEST.FOO<br clear="none"> size=1<br clear="none"> memoryPercentUsage=0<br clear="none"> producerCount=0<br clear="none"> consumerCount=0<br clear="none"> minEnqueueTime=0.0<br clear="none"> maxEnqueueTime=0.0<br clear="none"> dispatchCount=0<br clear="none"> expiredCount=0<br clear="none"> enqueueCount=1<br clear="none"> memoryLimit=67108864</p>
-</div></div><p>You can also use wildcards in the queue name, too. This will result in a separate stats message for every destination that is matched by the wildcard. Very handy indeed.</p><h3 id="StatisticsPlugin-Subscriptionsstatistics">Subscriptions statistics</h3><p>Since 5.6.0 you can also retrieve statistics on all queue and topic subscriptions. All you need to do it send an empty message to the destination named <code>ActiveMQ.Statistics. Subscription</code> along with a <code>replyTo</code> header.  The response will come in the form of one or more messages each containing the statistics for exactly one subscription on the Broker. </p><p>Below is an example of using the statistics plugin to grab stats from a broker:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Queue replyTo = session.createTemporaryQueue();
+</plain-text-body></structured-macro><p>The output from the code above is shown below:</p><structured-macro ac:macro-id="40e17065-b8ac-4950-ad47-489493ffca5f" ac:name="panel" ac:schema-version="1"><rich-text-body><p>memoryUsage=0<br clear="none"> dequeueCount=0<br clear="none"> inflightCount=0<br clear="none"> messagesCached=0<br clear="none"> averageEnqueueTime=0.0<br clear="none"> destinationName=queue://TEST.FOO<br clear="none"> size=1<br clear="none"> memoryPercentUsage=0<br clear="none"> producerCount=0<br clear="none"> consumerCount=0<br clear="none"> minEnqueueTime=0.0<br clear="none"> maxEnqueueTime=0.0<br clear="none"> dispatchCount=0<br clear="none"> expiredCount=0<br clear="none"> enqueueCount=1<br clear="none"> memoryLimit=67108864</p></rich-text-body></structured-macro><p>You can also use wildcards in the queue name, too. This will result in a separate stats message for every destination that is matched by the wildcard. Very handy indeed.</p><h3>Subscriptions statistics</h3><p>Since 5.6.0 you can also retrieve statistics on all queue and topic subscriptions. All you need to do it send an empty message to the destination named <code>ActiveMQ.Statistics. Subscription</code> along with a <code>replyTo</code> header.  The response will come in the form of one or more messages each containing the statistics for exactly one subscription on the Broker. </p><p>Below is an example of using the statistics plugin to grab stats from a broker:</p><structured-macro ac:macro-id="09cc56b7-53b1-45bc-8c10-704530f03f01" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>Queue replyTo = session.createTemporaryQueue();
MessageConsumer consumer = session.createConsumer(replyTo);
-String queueName = "ActiveMQ.Statistics.Subscription";
+String queueName = "ActiveMQ.Statistics.Subscription";
Queue testQueue = session.createQueue(queueName);
MessageProducer producer = session.createProducer(testQueue);
Message msg = session.createMessage();
@@ -68,10 +57,7 @@
for (Enumeration e = reply.getMapNames();e.hasMoreElements();) {
String name = e.nextElement().toString();
- System.out.println(name + "=" + reply.getObject(name));
+ System.out.println(name + "=" + reply.getObject(name));
}
-]]></script>
-</div></div><p>An example output from the code above is shown below:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>selector=null<br clear="none"> dispatchedQueueSize=1<br clear="none"> maximumPendingMessageLimit=0<br clear="none"> exclusive=false<br clear="none"> connectionId=ID:dejan-bosanacs-macbook-pro-2.local-64989-1335528942875-4:1<br clear="none"> destinationName=Test.Queue<br clear="none"> clientId=ID:dejan-bosanacs-macbook-pro-2.local-64989-1335528942875-3:1<br clear="none"> slowConsumer=false<br clear="none"> prefetchSize=1000<br clear="none"> sessionId=1<br clear="none"> dequeueCounter=0<br clear="none"> enqueueCounter=1<br clear="none"> retroactive=false<br clear="none"> dispatchedCounter=1</p>
-</div></div></div>
+</plain-text-body></structured-macro><p>An example output from the code above is shown below:</p><structured-macro ac:macro-id="a132f3d3-5185-421b-97d1-71ad914bd8e4" ac:name="panel" ac:schema-version="1"><rich-text-body><p>selector=null<br clear="none"> dispatchedQueueSize=1<br clear="none"> maximumPendingMessageLimit=0<br clear="none"> exclusive=false<br clear="none"> connectionId=ID:dejan-bosanacs-macbook-pro-2.local-64989-1335528942875-4:1<br clear="none"> destinationName=Test.Queue<br clear="none"> clientId=ID:dejan-bosanacs-macbook-pro-2.local-64989-1335528942875-3:1<br clear="none"> slowConsumer=false<br clear="none"> prefetchSize=1000<br clear="none"> sessionId=1<br clear="none"> dequeueCounter=0<br clear="none"> enqueueCounter=1<br clear="none"> retroactive=false<br clear="none"> dispatchedCounter=1</p></rich-text-body></structured-macro></div>
diff --git a/stomp.xml b/stomp.xml
index 2f9a200..a94f17e 100644
--- a/stomp.xml
+++ b/stomp.xml
@@ -1,65 +1,44 @@
-<div class="wiki-content maincontent"><p>ActiveMQ supports the <a shape="rect" class="external-link" href="http://stomp.github.com/" rel="nofollow">Stomp</a> protocol and the Stomp - JMS mapping. This makes it easy to write a client in pure <a shape="rect" class="unresolved" href="#">Ruby</a>, <a shape="rect" class="unresolved" href="#">Perl</a>, <a shape="rect" class="unresolved" href="#">Python</a> or <a shape="rect" class="unresolved" href="#">PHP</a> for working with ActiveMQ.</p><p>Please see the <a shape="rect" class="external-link" href="http://stomp.github.io/" rel="nofollow">Stomp site</a> for more details</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Spec Compliance</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>ActiveMQ v5.6 implements the Stomp v1.1 spec except for allowing spaces at the beginning or end of message header keys, they are preserved in the header values however. In future releases this will not be the case, clients should be updated and user code checked to ensure that spaces in the headers are there intentionally and not as a accident or a client "feature".</p></div></div><h3 id="Stomp-EnablingtheActiveMQBrokerforStomp">Enabling the ActiveMQ Broker for Stomp</h3><p>To enable STOMP protocol support in the broker add a transport connector definition whose URI scheme is <strong><code>stomp</code></strong>.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnectors>
- <transportConnector name="stomp" uri="stomp://localhost:61613"/>
+<div class="wiki-content maincontent"><p>ActiveMQ supports the <a shape="rect" href="http://stomp.github.com/">Stomp</a> protocol and the Stomp - JMS mapping. This makes it easy to write a client in pure <link><page ri:content-title="Ruby"></page><plain-text-link-body>Ruby</plain-text-link-body></link>, <link><page ri:content-title="Perl"></page><plain-text-link-body>Perl</plain-text-link-body></link>, <link><page ri:content-title="Python"></page><plain-text-link-body>Python</plain-text-link-body></link> or <link><page ri:content-title="PHP"></page><plain-text-link-body>PHP</plain-text-link-body></link> for working with ActiveMQ.</p><p>Please see the <a shape="rect" href="http://stomp.github.io/">Stomp site</a> for more details</p><structured-macro ac:macro-id="ec1411e3-961d-47ce-9c02-a9f2a5678ad1" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Spec Compliance</parameter><rich-text-body><p>ActiveMQ v5.6 implements the Stomp v1.1 spec except for allowing spaces at the beginning or end of message header keys, they are preserved in the header values however. In future releases this will not be the case, clients should be updated and user code checked to ensure that spaces in the headers are there intentionally and not as a accident or a client "feature".</p></rich-text-body></structured-macro><h3>Enabling the ActiveMQ Broker for Stomp</h3><p>To enable STOMP protocol support in the broker add a transport connector definition whose URI scheme is <strong><code>stomp</code></strong>.</p><p>Example:</p><structured-macro ac:macro-id="5355129f-14ce-402d-b6f5-97a47958697f" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnectors>
+ <transportConnector name="stomp" uri="stomp://localhost:61613"/>
</transportConnectors>
-]]></script>
-</div></div><p>To see a full example, try <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/example/conf/activemq.xml">this XML</a>. If you save that XML as <strong><code>foo.xml</code></strong> then you can run stomp via the command line as</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[activemq xbean:foo.xml
-]]></script>
-</div></div><p>For more help see <a shape="rect" href="run-broker.xml">Run Broker</a>.</p><h3 id="Stomp-TheStompWireFormat">The Stomp Wire Format</h3><p>Stomp uses a text based wire format that can be configured with the following options.  All options can be configured on a Brokers transport bind URI.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter 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><code>maxDataLength</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>104857600</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Maximum size of the message body (content) that can be sent.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maxFrameSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>MAX_LONG</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>From ActiveMQ 5.12.0</strong>: maximum frame size that can be sent. A Stomp frame includes a command, optional headers, and an optional body. Can help help prevent OOM DOS attacks</p></td></tr></tbody></table></div><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="stomp+ssl" uri="stomp+ssl://localhost:61612?wireFormat.maxFrameSize=1000000"/>]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Use the Correct Prefix!</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Wire format options must have the prefix <strong><code>wireFormat.</code></strong> to take effect, e.g., <strong><code>wireFormat.<code>maxDataLength</code>=100000</code></strong>. Options missing this prefix will be ignored.</p></div></div><h3 id="Stomp-Security">Security</h3><p><strong>From ActiveMQ 5.1</strong>: Stomp fully supports <a shape="rect" href="security.xml">ActiveMQ's security</a> mechanism. This means that the <strong><code>CONNECT</code></strong> command will return an <strong><code>ERROR</code></strong> STOMP frame on unsuccessful authentication. Also, the authorization policies will be applied when you try to access (read/write) certain destinations. If you use synchronous operations (by using <a shape="rect" class="external-link" href="http://stomp.github.com/stomp-specification-1.1.html#RECEIPT" rel="nofollow">receipts</a>), you can expect an <strong><code>ERROR</code></strong> frame in case of unauthorized access attempt. In other case, operations will be discarded but the client will not be informed of errors. This applies to all errors that can occur broker-side.</p><div class="confluence-information-macro confluence-information-macro-tip"><p class="title">SSL</p><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>For additional security, you can use Stomp over SSL as described in the following section.</p></div></div><h3 id="Stomp-EnablingStompoverNIO">Enabling Stomp over NIO</h3><p><strong>From ActiveMQ 5.3</strong>: for better scalability and performance the Stomp protocol can be configured to be run over the NIO transport. The <a shape="rect" class="external-link" href="http://activemq.apache.org/configuring-transports.html#ConfiguringTransports-TheNIOTransport">NIO transport</a> will use far fewer threads than the corresponding TCP connector. This can help when support for a <a shape="rect" class="external-link" href="http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html">large number of queues</a> is required. To use NIO change the URI scheme of the transport connector to <strong><code>stomp+nio</code></strong>.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="stomp+nio" uri="stomp+nio://localhost:61612"/>
-]]></script>
-</div></div><h3 id="Stomp-EnablingStompoverSSL">Enabling Stomp over SSL</h3><p>To configure ActiveMQ to use Stomp over an SSL connection change the URI scheme to <strong><code>stomp+ssl</code></strong>.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnector name="stomp+ssl" uri="stomp+ssl://localhost:61612"/>
-]]></script>
-</div></div><p>For more details on using SSL with ActiveMQ see the following article (<a shape="rect" class="external-link" href="http://activemq.apache.org/how-do-i-use-ssl.html">How do I use SSL</a>). An example of using Stomp over SSL on the client side can be found in the <a shape="rect" class="external-link" href="http://stomp.fusesource.org/documentation/php/book.html#SSL" rel="nofollow">PHP Stomp client example</a>.</p><h3 id="Stomp-Heart-BeatGracePeriod">Heart-Beat Grace Period</h3><p>The STOMP protocol (version 1.1 or greater) <a shape="rect" class="external-link" href="http://stomp.github.io/stomp-specification-1.2.html#Heart-beating" rel="nofollow">defines the concept of heart beats</a> as a method by which a client and broker can determine the health of the underlying TCP connection between them. ActiveMQ supports STOMP heart beating provided the client is using version 1.1 (or greater) of the protocol.</p><p><strong>Before ActiveMQ 5.9.0</strong>: enforcement of the 'read' heart-beat timeout (that is, a heart-beat sent from the client to the broker) was strict. In other words, the broker was intolerant of late arriving read heart-beats from the client. This resulted in the broker concluding that the client was no longer present causing it to close its side of the client's connection when the client failed to honor it's configured heart-beat settings.</p><p><strong>From ActiveMQ 5.9.0</strong>: the timeout enforcement for read heart-beats is now configurable via a new transport option <strong><code>transport.hbGracePeriodMultiplier</code></strong>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnectors>
- <transportConnector name="stomp" uri="stomp://localhost:61613?transport.hbGracePeriodMultiplier=1.5"/>
+</plain-text-body></structured-macro><p>To see a full example, try <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/example/conf/activemq.xml">this XML</a>. If you save that XML as <strong><code>foo.xml</code></strong> then you can run stomp via the command line as</p><structured-macro ac:macro-id="99818d3e-990b-410b-a51b-68619d0ab5a7" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>activemq xbean:foo.xml
+</plain-text-body></structured-macro><p>For more help see <link><page ri:content-title="Run Broker"></page></link>.</p><h3>The Stomp Wire Format</h3><p>Stomp uses a text based wire format that can be configured with the following options.  All options can be configured on a Brokers transport bind URI.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Parameter Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>maxDataLength</code></p></td><td colspan="1" rowspan="1"><p><code>104857600</code></p></td><td colspan="1" rowspan="1"><p>Maximum size of the message body (content) that can be sent.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maxFrameSize</code></p></td><td colspan="1" rowspan="1"><p><code>MAX_LONG</code></p></td><td colspan="1" rowspan="1"><p><strong>From ActiveMQ 5.12.0</strong>: maximum frame size that can be sent. A Stomp frame includes a command, optional headers, and an optional body. Can help help prevent OOM DOS attacks</p></td></tr></tbody></table><p>Example:</p><structured-macro ac:macro-id="97b90707-41d7-4520-94a7-7280cb5a58e7" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnector name="stomp+ssl" uri="stomp+ssl://localhost:61612?wireFormat.maxFrameSize=1000000"/></plain-text-body></structured-macro><structured-macro ac:macro-id="5f63c58b-03ae-42b4-acb9-5129da2b15db" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Use the Correct Prefix!</parameter><rich-text-body><p>Wire format options must have the prefix <strong><code>wireFormat.</code></strong> to take effect, e.g., <strong><code>wireFormat.<code>maxDataLength</code>=100000</code></strong>. Options missing this prefix will be ignored.</p></rich-text-body></structured-macro><h3>Security</h3><p><strong>From ActiveMQ 5.1</strong>: Stomp fully supports <link><page ri:content-title="Security"></page><plain-text-link-body>ActiveMQ's security</plain-text-link-body></link> mechanism. This means that the <strong><code>CONNECT</code></strong> command will return an <strong><code>ERROR</code></strong> STOMP frame on unsuccessful authentication. Also, the authorization policies will be applied when you try to access (read/write) certain destinations. If you use synchronous operations (by using <a shape="rect" href="http://stomp.github.com/stomp-specification-1.1.html#RECEIPT">receipts</a>), you can expect an <strong><code>ERROR</code></strong> frame in case of unauthorized access attempt. In other case, operations will be discarded but the client will not be informed of errors. This applies to all errors that can occur broker-side.</p><structured-macro ac:macro-id="be455380-400f-40a9-aa52-f47b0e260c9b" ac:name="tip" ac:schema-version="1"><parameter ac:name="title">SSL</parameter><rich-text-body><p>For additional security, you can use Stomp over SSL as described in the following section.</p></rich-text-body></structured-macro><h3>Enabling Stomp over NIO</h3><p><strong>From ActiveMQ 5.3</strong>: for better scalability and performance the Stomp protocol can be configured to be run over the NIO transport. The <a shape="rect" href="http://activemq.apache.org/configuring-transports.html#ConfiguringTransports-TheNIOTransport">NIO transport</a> will use far fewer threads than the corresponding TCP connector. This can help when support for a <a shape="rect" href="http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html">large number of queues</a> is required. To use NIO change the URI scheme of the transport connector to <strong><code>stomp+nio</code></strong>.</p><p>Example:</p><structured-macro ac:macro-id="72564ff3-2e70-4b20-b697-ad0b42803447" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnector name="stomp+nio" uri="stomp+nio://localhost:61612"/>
+</plain-text-body></structured-macro><h3>Enabling Stomp over SSL</h3><p>To configure ActiveMQ to use Stomp over an SSL connection change the URI scheme to <strong><code>stomp+ssl</code></strong>.</p><p>Example:</p><structured-macro ac:macro-id="31b8598d-adce-464f-85dc-abef45539350" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnector name="stomp+ssl" uri="stomp+ssl://localhost:61612"/>
+</plain-text-body></structured-macro><p>For more details on using SSL with ActiveMQ see the following article (<a shape="rect" href="http://activemq.apache.org/how-do-i-use-ssl.html">How do I use SSL</a>). An example of using Stomp over SSL on the client side can be found in the <a shape="rect" href="http://stomp.fusesource.org/documentation/php/book.html#SSL">PHP Stomp client example</a>.</p><h3>Heart-Beat Grace Period</h3><p>The STOMP protocol (version 1.1 or greater) <a shape="rect" href="http://stomp.github.io/stomp-specification-1.2.html#Heart-beating">defines the concept of heart beats</a> as a method by which a client and broker can determine the health of the underlying TCP connection between them. ActiveMQ supports STOMP heart beating provided the client is using version 1.1 (or greater) of the protocol.</p><p><strong>Before ActiveMQ 5.9.0</strong>: enforcement of the 'read' heart-beat timeout (that is, a heart-beat sent from the client to the broker) was strict. In other words, the broker was intolerant of late arriving read heart-beats from the client. This resulted in the broker concluding that the client was no longer present causing it to close its side of the client's connection when the client failed to honor it's configured heart-beat settings.</p><p><strong>From ActiveMQ 5.9.0</strong>: the timeout enforcement for read heart-beats is now configurable via a new transport option <strong><code>transport.hbGracePeriodMultiplier</code></strong>:</p><structured-macro ac:macro-id="2ff83a5d-31fd-42cc-b253-459be6666a92" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><transportConnectors>
+ <transportConnector name="stomp" uri="stomp://localhost:61613?transport.hbGracePeriodMultiplier=1.5"/>
</transportConnectors>
-]]></script>
-</div></div><p>This multiplier is used to calculate the effective read heart-beat timeout the broker will enforce for each client's connection. The multiplier is applied to the read-timeout interval the client specifies in its <strong><code>CONNECT</code></strong> frame:</p><p><code>  <strong><client specified read heart-beat interval> * <grace periodmultiplier> == <broker enforced read heart-beat timeout interval></strong></code></p><p>For backward compatibility, if the grace period multiplier is not configured the default enforcement mode remains strict, e.g., <strong><code>transport.hbGracePeriodMultiplier=1.0</code></strong>. Attempts to configure the grace period multiplier to a value less than, or equal to <strong><code>1.0</code></strong> will be silently ignored.</p><p>STOMP clients that wish to be tolerant of late arriving heart-beats from the broker must implement their own solution for doing so.</p><ul><li><p>Please check the <a shape="rect" class="external-link" href="http://stomp.github.io/stomp-specification-1.2.html#Heart-beating" rel="nofollow">STOMP specification</a> for the details on heart-beating</p></li><li><p>The JIRA that implemented this: <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-4674">ActiveMQ 5.x does not support the notion of a grace-period for heart beats as supported by the STOMP protocol</a></p></li></ul><h3 id="Stomp-WorkingwithDestinationswithStomp">Working with Destinations with Stomp</h3><p>Note that the prefix in stomp <strong><code>/queue/</code></strong> or <strong><code>/topic/</code></strong> is removed from the string before passing it to ActiveMQ as a JMS destination. Also note that the default separator in MOM systems is <strong><code>.</code></strong> (dot). Whilst <strong><code>FOO.BAR</code></strong> is the normal syntax to identify a queue type destination the Stomp equivalent is <strong><code>/queue/FOO.BAR</code></strong></p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Be careful about starting destinations with /</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If in Stomp world you use <strong><code>/queue/foo/bar</code></strong> then in a JMS world the queue would be called <strong><code>foo/bar</code></strong> not <strong><code>/foo/bar</code></strong>.</p></div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Persistent Messaging in STOMP</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>STOMP messages are non-persistent by default. To use persistent messaging add the following STOMP header to all <strong><code>SEND</code></strong> requests: <strong><code>persistent:true</code></strong>. This default is the opposite of that for JMS messages.</p></div></div><h3 id="Stomp-WorkingwithJMSText/BytesMessagesandStomp">Working with JMS Text/Bytes Messages and Stomp</h3><p>Stomp is a very simple protocol - that's part of the beauty of it! As such, it does not have knowledge of JMS messages such as <strong><code>TextMessage</code></strong>'s or <strong><code>BytesMessage</code></strong>'s. The protocol does however support a <strong><code>content-length</code></strong> header. To provide more robust interaction between STOMP and JMS clients, ActiveMQ keys off of the inclusion of this header to determine what message type to create when sending from Stomp to JMS. The logic is simple:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Inclusion of content-length header</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Resulting Message</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>yes</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>BytesMessage</code></strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>no</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong><code>TextMessage</code></strong></p></td></tr></tbody></table></div><p>This same logic can be followed when going from JMS to Stomp, as well. A Stomp client could be written to key off of the inclusion of the <strong><code>content-length</code></strong> header to determine what type of message structure to provide to the user.</p><h3 id="Stomp-MessageTransformations">Message Transformations</h3><p>The <strong><code>transformation</code></strong> message header on <strong><code>SEND</code></strong> and <strong><code>SUBSCRIBE</code></strong> messages could be used to instruct ActiveMQ to transform messages from text to the format of your desire. Currently, ActiveMQ comes with a transformer that can transform XML/JSON text to Java objects, but you can add your own transformers as well.</p><p>Here's a quick example of how to use built-in transformer (taken from test cases)</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ private String xmlObject = "<pojo>\n"
- + " <name>Dejan</name>\n"
- + " <city>Belgrade</city>\n"
- + "</pojo>";
+</plain-text-body></structured-macro><p>This multiplier is used to calculate the effective read heart-beat timeout the broker will enforce for each client's connection. The multiplier is applied to the read-timeout interval the client specifies in its <strong><code>CONNECT</code></strong> frame:</p><p><code>  <strong><client specified read heart-beat interval> * <grace periodmultiplier> == <broker enforced read heart-beat timeout interval></strong></code></p><p>For backward compatibility, if the grace period multiplier is not configured the default enforcement mode remains strict, e.g., <strong><code>transport.hbGracePeriodMultiplier=1.0</code></strong>. Attempts to configure the grace period multiplier to a value less than, or equal to <strong><code>1.0</code></strong> will be silently ignored.</p><p>STOMP clients that wish to be tolerant of late arriving heart-beats from the broker must implement their own solution for doing so.</p><ul><li><p>Please check the <a shape="rect" href="http://stomp.github.io/stomp-specification-1.2.html#Heart-beating">STOMP specification</a> for the details on heart-beating</p></li><li><p>The JIRA that implemented this: <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-4674">ActiveMQ 5.x does not support the notion of a grace-period for heart beats as supported by the STOMP protocol</a></p></li></ul><h3>Working with Destinations with Stomp</h3><p>Note that the prefix in stomp <strong><code>/queue/</code></strong> or <strong><code>/topic/</code></strong> is removed from the string before passing it to ActiveMQ as a JMS destination. Also note that the default separator in MOM systems is <strong><code>.</code></strong> (dot). Whilst <strong><code>FOO.BAR</code></strong> is the normal syntax to identify a queue type destination the Stomp equivalent is <strong><code>/queue/FOO.BAR</code></strong></p><structured-macro ac:macro-id="24b131c7-cd50-4a3a-8351-be5eef6d513e" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Be careful about starting destinations with /</parameter><rich-text-body><p>If in Stomp world you use <strong><code>/queue/foo/bar</code></strong> then in a JMS world the queue would be called <strong><code>foo/bar</code></strong> not <strong><code>/foo/bar</code></strong>.</p></rich-text-body></structured-macro><structured-macro ac:macro-id="02cf3683-0949-41b0-8a12-e0e9b15f5f46" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Persistent Messaging in STOMP</parameter><rich-text-body><p>STOMP messages are non-persistent by default. To use persistent messaging add the following STOMP header to all <strong><code>SEND</code></strong> requests: <strong><code>persistent:true</code></strong>. This default is the opposite of that for JMS messages.</p></rich-text-body></structured-macro><h3>Working with JMS Text/Bytes Messages and Stomp</h3><p>Stomp is a very simple protocol - that's part of the beauty of it! As such, it does not have knowledge of JMS messages such as <strong><code>TextMessage</code></strong>'s or <strong><code>BytesMessage</code></strong>'s. The protocol does however support a <strong><code>content-length</code></strong> header. To provide more robust interaction between STOMP and JMS clients, ActiveMQ keys off of the inclusion of this header to determine what message type to create when sending from Stomp to JMS. The logic is simple:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Inclusion of content-length header</p></th><th colspan="1" rowspan="1"><p>Resulting Message</p></th></tr><tr><td colspan="1" rowspan="1"><p>yes</p></td><td colspan="1" rowspan="1"><p><strong><code>BytesMessage</code></strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>no</p></td><td colspan="1" rowspan="1"><p><strong><code>TextMessage</code></strong></p></td></tr></tbody></table><p>This same logic can be followed when going from JMS to Stomp, as well. A Stomp client could be written to key off of the inclusion of the <strong><code>content-length</code></strong> header to determine what type of message structure to provide to the user.</p><h3>Message Transformations</h3><p>The <strong><code>transformation</code></strong> message header on <strong><code>SEND</code></strong> and <strong><code>SUBSCRIBE</code></strong> messages could be used to instruct ActiveMQ to transform messages from text to the format of your desire. Currently, ActiveMQ comes with a transformer that can transform XML/JSON text to Java objects, but you can add your own transformers as well.</p><p>Here's a quick example of how to use built-in transformer (taken from test cases)</p><structured-macro ac:macro-id="d0aeb29a-a196-4013-be0d-838de37b159f" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body> private String xmlObject = "<pojo>\n"
+ + " <name>Dejan</name>\n"
+ + " <city>Belgrade</city>\n"
+ + "</pojo>";
public void testTransformationReceiveXMLObject() throws Exception {
- MessageProducer producer = session.createProducer(new ActiveMQQueue("USERS." + getQueueName()));
- ObjectMessage message = session.createObjectMessage(new SamplePojo("Dejan", "Belgrade"));
+ MessageProducer producer = session.createProducer(new ActiveMQQueue("USERS." + getQueueName()));
+ ObjectMessage message = session.createObjectMessage(new SamplePojo("Dejan", "Belgrade"));
producer.send(message);
- String frame = "CONNECT\n" + "login: system\n" + "passcode: manager\n\n" + Stomp.NULL;
+ String frame = "CONNECT\n" + "login: system\n" + "passcode: manager\n\n" + Stomp.NULL;
stompConnection.sendFrame(frame);
frame = stompConnection.receiveFrame();
- assertTrue(frame.startsWith("CONNECTED"));
+ assertTrue(frame.startsWith("CONNECTED"));
- frame = "SUBSCRIBE\n" + "destination:/queue/USERS." + getQueueName() + "\n" + "ack:auto" + "\n" + "transformation:jms-object-xml\n\n" + Stomp.NULL;
+ frame = "SUBSCRIBE\n" + "destination:/queue/USERS." + getQueueName() + "\n" + "ack:auto" + "\n" + "transformation:jms-object-xml\n\n" + Stomp.NULL;
stompConnection.sendFrame(frame);
frame = stompConnection.receiveFrame();
assertTrue(frame.trim().endsWith(xmlObject));
- frame = "DISCONNECT\n" + "\n\n" + Stomp.NULL;
+ frame = "DISCONNECT\n" + "\n\n" + Stomp.NULL;
stompConnection.sendFrame(frame);
}
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Dependencies</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>ActiveMQ uses <a shape="rect" class="external-link" href="http://xstream.codehaus.org" rel="nofollow">XStream</a> for its transformation needs. Since it's the optional dependency you have to add it to broker's classpath by putting the appropriate JAR into the <strong><code>lib/</code></strong> folder. Additionally, if you plan to use JSON transformations you have to add <a shape="rect" class="external-link" href="http://jettison.codehaus.org/" rel="nofollow">Jettison</a> JSON parser to the classpath.</p></div></div><p>In order to create your own transformer, you have to do the following:</p><ol><li><p>Build your transformer by implementing a <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/transport/stomp/FrameTranslator.html">FrameTranslator</a> interface</p></li><li><p>Associate it with the appropriate header value by creating a file named as a value you want to use in the <strong><code>META-INF/services/org/apache/activemq/transport/frametranslator/</code></strong> folder of your JAR which will contain the value <strong><code>class=<em>fully qualified classname of your transformer</em></code></strong></p></li></ol><p>For example the built-in transformer contains the following value:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[class=org.apache.activemq.transport.stomp.XStreamFrameTranslator]]></script>
-</div></div><p>in the <strong><code>META-INF/services/org/apache/activemq/transport/frametranslator/jms-xml</code></strong> file.</p><h3 id="Stomp-Debugging"><span style="line-height: 1.5625;">Debugging</span></h3><p>In case you want to debug Stomp communication between broker and clients you should configure the Stomp connector with the <strong><code>trace</code></strong> parameter, like this:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnectors>
- <transportConnector name="stomp" uri="stomp://localhost:61613?trace=true"/>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="0fcad07a-60de-4f13-a543-515b7486bb50" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Dependencies</parameter><rich-text-body><p>ActiveMQ uses <a shape="rect" href="http://xstream.codehaus.org">XStream</a> for its transformation needs. Since it's the optional dependency you have to add it to broker's classpath by putting the appropriate JAR into the <strong><code>lib/</code></strong> folder. Additionally, if you plan to use JSON transformations you have to add <a shape="rect" href="http://jettison.codehaus.org/">Jettison</a> JSON parser to the classpath.</p></rich-text-body></structured-macro><p>In order to create your own transformer, you have to do the following:</p><ol><li><p>Build your transformer by implementing a <a shape="rect" href="http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/transport/stomp/FrameTranslator.html">FrameTranslator</a> interface</p></li><li><p>Associate it with the appropriate header value by creating a file named as a value you want to use in the <strong><code>META-INF/services/org/apache/activemq/transport/frametranslator/</code></strong> folder of your JAR which will contain the value <strong><code>class=<em>fully qualified classname of your transformer</em></code></strong></p></li></ol><p>For example the built-in transformer contains the following value:</p><structured-macro ac:macro-id="1f17ea64-04cd-4063-94d9-ba08a9e0940a" ac:name="code" ac:schema-version="1"><plain-text-body>class=org.apache.activemq.transport.stomp.XStreamFrameTranslator</plain-text-body></structured-macro><p>in the <strong><code>META-INF/services/org/apache/activemq/transport/frametranslator/jms-xml</code></strong> file.</p><h3><span style="line-height: 1.5625;">Debugging</span></h3><p>In case you want to debug Stomp communication between broker and clients you should configure the Stomp connector with the <strong><code>trace</code></strong> parameter, like this:</p><structured-macro ac:macro-id="75e81c40-b1ae-4385-82f9-650f43c26a58" ac:name="code" ac:schema-version="1"><plain-text-body><transportConnectors>
+ <transportConnector name="stomp" uri="stomp://localhost:61613?trace=true"/>
</transportConnectors>
-]]></script>
-</div></div><p>This will instruct the broker to trace all packets it sends and receives.</p><p>Furthermore, you have to enable tracing for the appropriate log. You can achieve that by adding the following to your <strong><code>conf/log4j.properties</code></strong></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[log4j.logger.org.apache.activemq.transport.stomp=TRACE
-]]></script>
-</div></div><p>Finally, you will probably want to keep these messages in the separate file instead of polluting the standard broker's log. You can achieve that with the following log4j configuration:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[log4j.appender.stomp=org.apache.log4j.RollingFileAppender
+</plain-text-body></structured-macro><p>This will instruct the broker to trace all packets it sends and receives.</p><p>Furthermore, you have to enable tracing for the appropriate log. You can achieve that by adding the following to your <strong><code>conf/log4j.properties</code></strong></p><structured-macro ac:macro-id="e99699a1-cd23-46f0-a4f1-7f9339f823cc" ac:name="code" ac:schema-version="1"><plain-text-body>log4j.logger.org.apache.activemq.transport.stomp=TRACE
+</plain-text-body></structured-macro><p>Finally, you will probably want to keep these messages in the separate file instead of polluting the standard broker's log. You can achieve that with the following log4j configuration:</p><structured-macro ac:macro-id="dbd7b5c2-280a-4dcb-9372-0edbf7dbc8c2" ac:name="code" ac:schema-version="1"><plain-text-body>log4j.appender.stomp=org.apache.log4j.RollingFileAppender
log4j.appender.stomp.file=${activemq.base}/data/stomp.log
log4j.appender.stomp.maxFileSize=1024KB
log4j.appender.stomp.maxBackupIndex=5
@@ -73,41 +52,36 @@
# Enable these two lines and disable the above two if you want the frame IO ONLY (e.g., no heart beat messages, inactivity monitor etc).
#log4j.logger.org.apache.activemq.transport.stomp.StompIO=TRACE, stomp
#log4j.additivity.org.apache.activemq.transport.stomp.StompIO=false
-]]></script>
-</div></div><p>After this, all your Stomp packets will be logged to the <strong><code>data/stomp.log</code></strong></p><h3 id="Stomp-JavaAPI">Java API</h3><p><strong>From ActiveMQ 5.2</strong>: there is a simple Java Stomp API distributed with ActiveMQ. Note that this API is provided purely for testing purposes and you should always consider using standard JMS API from Java instead of this one. The following code snippet provides a simple example of using this API:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[StompConnection connection = new StompConnection();
-connection.open("localhost", 61613);
+</plain-text-body></structured-macro><p>After this, all your Stomp packets will be logged to the <strong><code>data/stomp.log</code></strong></p><h3>Java API</h3><p><strong>From ActiveMQ 5.2</strong>: there is a simple Java Stomp API distributed with ActiveMQ. Note that this API is provided purely for testing purposes and you should always consider using standard JMS API from Java instead of this one. The following code snippet provides a simple example of using this API:</p><structured-macro ac:macro-id="942bf7ca-70ee-4437-9a9f-6dc4c344af29" ac:name="code" ac:schema-version="1"><plain-text-body>StompConnection connection = new StompConnection();
+connection.open("localhost", 61613);
-connection.connect("system", "manager");
+connection.connect("system", "manager");
StompFrame connect = connection.receive();
if(!connect.getAction().equals(Stomp.Responses.CONNECTED)) {
- throw new Exception ("Not connected");
+ throw new Exception ("Not connected");
}
-connection.begin("tx1");
-connection.send("/queue/test", "message1", "tx1", null);
-connection.send("/queue/test", "message2", "tx1", null);
-connection.commit("tx1");
+connection.begin("tx1");
+connection.send("/queue/test", "message1", "tx1", null);
+connection.send("/queue/test", "message2", "tx1", null);
+connection.commit("tx1");
-connection.subscribe("/queue/test", Subscribe.AckModeValues.CLIENT);
+connection.subscribe("/queue/test", Subscribe.AckModeValues.CLIENT);
-connection.begin("tx2");
+connection.begin("tx2");
StompFrame message = connection.receive();
System.out.println(message.getBody());
-connection.ack(message, "tx2");
+connection.ack(message, "tx2");
message = connection.receive();
System.out.println(message.getBody());
-connection.ack(message, "tx2");
+connection.ack(message, "tx2");
-connection.commit("tx2");
+connection.commit("tx2");
connection.disconnect();
-]]></script>
-</div></div><p>This example is part of the standard ActiveMQ distribution. You can run it from the <strong><code>./example</code></strong> folder with:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ant stomp
-]]></script>
-</div></div><h3 id="Stomp-StompExtensionsforJMSMessageSemantics">Stomp Extensions for JMS Message Semantics</h3><p>Note that STOMP is designed to be as simple as possible - so any scripting language/platform can message any other with minimal effort. STOMP allows pluggable headers on each request such as sending & receiving messages. ActiveMQ has several extensions to the Stomp protocol, so that JMS semantics can be supported by Stomp clients. An OpenWire JMS producer can send messages to a Stomp consumer, and a Stomp producer can send messages to an OpenWire JMS consumer. And Stomp to Stomp configurations, can use the richer JMS message control.</p><p>STOMP supports the following standard JMS properties on <strong><code>SENT</code></strong> messages:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>STOMP Header</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>JMS Header</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>correlation-id</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSCorrelationID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Good consumers will add this header to any responses they send.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>expires</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSExpiration</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Expiration time of the message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupID</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the <a shape="rect" href="message-groups.xml">Message Groups.</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupSeq</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSXGroupSeq</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Optional header that specifies the sequence number in the <a shape="rect" href="message-groups.xml">Message Groups.</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>persistent</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSDeliveryMode</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Whether or not the message is persistent.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>priority</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSPriority</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Priority on the message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>reply-to</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSReplyTo</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Destination you should send replies to.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>type</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>JMSType</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Type of the message.</p></td></tr></tbody></table></div><h3 id="Stomp-ActiveMQExtensionstoSTOMP">ActiveMQ Extensions to STOMP</h3><p>You can add custom headers to STOMP commands to configure the ActiveMQ protocol. Here are some examples:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Verb</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Header</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>CONNECT</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>client-id</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>string</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the JMS clientID which is used in combination with the <strong><code>activemq.subcriptionName</code></strong> to denote a durable subscriber.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.dispatchAsync</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Should messages be dispatched synchronously or asynchronously from the producer thread for non-durable topics in the broker?</p><p>For fast consumers set this to <strong><code>false</code></strong>.</p><p>For slow consumers set it to <strong><code>true</code></strong> so that dispatching will not block fast consumers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.exclusive</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>I would like to be an <a shape="rect" href="exclusive-consumer.xml">Exclusive Consumer</a> on the queue.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.maximumPendingMessageLimit</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For <a shape="rect" href="slow-consumer-handling.xml">Slow Consumer Handling</a> on non-durable topics by dropping old messages - we can set a maximum-pending limit, such that once a slow consumer backs up to this high water mark we begin to discard old messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.noLocal</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies whether or not locally sent messages should be ignored for subscriptions.</p><p>Set to <strong><code>true</code></strong> to filter out locally sent messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.prefetchSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>int</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the maximum number of pending messages that will be dispatched to the client. Once this maximum is reached no more messages are dispatched until the client acknowledges a message.</p><p>Set to a low value > <strong>1</strong> for fair distribution of messages across consumers when processing messages can be slow</p><p><strong>Note</strong>: if your STOMP client is implemented using a dynamic scripting language like Ruby, say, then this parameter <strong><em>must</em></strong> be set to <strong><code>1</code></strong> as there is no notion of a client-side message size to be sized.</p><p>STOMP does not support a value of <strong><code>0</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.priority</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>byte</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the priority of the consumer so that dispatching can be weighted in priority order.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.retroactive</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>boolean</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For non-durable topics make this subscription <a shape="rect" href="retroactive-consumer.xml">retroactive</a>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>activemq.subscriptionName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>string</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>For durable topic subscriptions you must specify the same <strong><code>activemq.client-id</code></strong> on the connection and <strong><code>activemq.subcriptionName</code></strong> on the subscribe prior to v5.7.0.</p><p><strong>Note</strong>: the spelling <strong><code>subcriptionName</code></strong> NOT <strong><code>subscriptionName</code></strong>. This is not intuitive, but it is how it is implemented in ActiveMQ 4.x.</p><p>For the 5.0 release of ActiveMQ, both <strong><code>subcriptionName</code></strong> and <strong><code>subscriptionName</code></strong> will be supported (<strong><code>subcriptionName</code></strong> was removed as of v5.6.0).</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>selector</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>string</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies a JMS Selector using SQL 92 syntax as specified in the JMS 1.1 specification. This allows a filter to be applied to each message as part of the subscription.</p></td></tr></tbody></table></div></div>
+</plain-text-body></structured-macro><p>This example is part of the standard ActiveMQ distribution. You can run it from the <strong><code>./example</code></strong> folder with:</p><structured-macro ac:macro-id="afbce1e9-352a-434d-b1e6-14159bd18a7b" ac:name="code" ac:schema-version="1"><plain-text-body>ant stomp
+</plain-text-body></structured-macro><h3>Stomp Extensions for JMS Message Semantics</h3><p>Note that STOMP is designed to be as simple as possible - so any scripting language/platform can message any other with minimal effort. STOMP allows pluggable headers on each request such as sending & receiving messages. ActiveMQ has several extensions to the Stomp protocol, so that JMS semantics can be supported by Stomp clients. An OpenWire JMS producer can send messages to a Stomp consumer, and a Stomp producer can send messages to an OpenWire JMS consumer. And Stomp to Stomp configurations, can use the richer JMS message control.</p><p>STOMP supports the following standard JMS properties on <strong><code>SENT</code></strong> messages:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>STOMP Header</p></th><th colspan="1" rowspan="1"><p>JMS Header</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>correlation-id</code></p></td><td colspan="1" rowspan="1"><p><code>JMSCorrelationID</code></p></td><td colspan="1" rowspan="1"><p>Good consumers will add this header to any responses they send.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>expires</code></p></td><td colspan="1" rowspan="1"><p><code>JMSExpiration</code></p></td><td colspan="1" rowspan="1"><p>Expiration time of the message.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSXGroupID</code></p></td><td colspan="1" rowspan="1"><p><code>JMSXGroupID</code></p></td><td colspan="1" rowspan="1"><p>Specifies the <link><page ri:content-title="Message Groups"></page><plain-text-link-body>Message Groups.</plain-text-link-body></link></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>JMSXGroupSeq</code></p></td><td colspan="1" rowspan="1"><p><code>JMSXGroupSeq</code></p></td><td colspan="1" rowspan="1"><p>Optional header that specifies the sequence number in the <link><page ri:content-title="Message Groups"></page><plain-text-link-body>Message Groups.</plain-text-link-body></link></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>persistent</code></p></td><td colspan="1" rowspan="1"><p><code>JMSDeliveryMode</code></p></td><td colspan="1" rowspan="1"><p>Whether or not the message is persistent.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>priority</code></p></td><td colspan="1" rowspan="1"><p><code>JMSPriority</code></p></td><td colspan="1" rowspan="1"><p>Priority on the message.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>reply-to</code></p></td><td colspan="1" rowspan="1"><p><code>JMSReplyTo</code></p></td><td colspan="1" rowspan="1"><p>Destination you should send replies to.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>type</code></p></td><td colspan="1" rowspan="1"><p><code>JMSType</code></p></td><td colspan="1" rowspan="1"><p>Type of the message.</p></td></tr></tbody></table><h3>ActiveMQ Extensions to STOMP</h3><p>You can add custom headers to STOMP commands to configure the ActiveMQ protocol. Here are some examples:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Verb</p></th><th colspan="1" rowspan="1"><p>Header</p></th><th colspan="1" rowspan="1"><p>Type</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>CONNECT</code></p></td><td colspan="1" rowspan="1"><p><code>client-id</code></p></td><td colspan="1" rowspan="1"><p><code>string</code></p></td><td colspan="1" rowspan="1"><p>Specifies the JMS clientID which is used in combination with the <strong><code>activemq.subcriptionName</code></strong> to denote a durable subscriber.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>activemq.dispatchAsync</code></p></td><td colspan="1" rowspan="1"><p><code>boolean</code></p></td><td colspan="1" rowspan="1"><p>Should messages be dispatched synchronously or asynchronously from the producer thread for non-durable topics in the broker?</p><p>For fast consumers set this to <strong><code>false</code></strong>.</p><p>For slow consumers set it to <strong><code>true</code></strong> so that dispatching will not block fast consumers.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>activemq.exclusive</code></p></td><td colspan="1" rowspan="1"><p><code>boolean</code></p></td><td colspan="1" rowspan="1"><p>I would like to be an <link><page ri:content-title="Exclusive Consumer"></page></link> on the queue.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>activemq.maximumPendingMessageLimit</code></p></td><td colspan="1" rowspan="1"><p><code>int</code></p></td><td colspan="1" rowspan="1"><p>For <link><page ri:content-title="Slow Consumer Handling"></page></link> on non-durable topics by dropping old messages - we can set a maximum-pending limit, such that once a slow consumer backs up to this high water mark we begin to discard old messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>activemq.noLocal</code></p></td><td colspan="1" rowspan="1"><p><code>boolean</code></p></td><td colspan="1" rowspan="1"><p>Specifies whether or not locally sent messages should be ignored for subscriptions.</p><p>Set to <strong><code>true</code></strong> to filter out locally sent messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>activemq.prefetchSize</code></p></td><td colspan="1" rowspan="1"><p><code>int</code></p></td><td colspan="1" rowspan="1"><p>Specifies the maximum number of pending messages that will be dispatched to the client. Once this maximum is reached no more messages are dispatched until the client acknowledges a message.</p><p>Set to a low value > <strong>1</strong> for fair distribution of messages across consumers when processing messages can be slow</p><p><strong>Note</strong>: if your STOMP client is implemented using a dynamic scripting language like Ruby, say, then this parameter <strong><em>must</em></strong> be set to <strong><code>1</code></strong> as there is no notion of a client-side message size to be sized.</p><p>STOMP does not support a value of <strong><code>0</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>activemq.priority</code></p></td><td colspan="1" rowspan="1"><p><code>byte</code></p></td><td colspan="1" rowspan="1"><p>Sets the priority of the consumer so that dispatching can be weighted in priority order.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>activemq.retroactive</code></p></td><td colspan="1" rowspan="1"><p><code>boolean</code></p></td><td colspan="1" rowspan="1"><p>For non-durable topics make this subscription <link><page ri:content-title="Retroactive Consumer"></page><plain-text-link-body>retroactive</plain-text-link-body></link>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>activemq.subscriptionName</code></p></td><td colspan="1" rowspan="1"><p><code>string</code></p></td><td colspan="1" rowspan="1"><p>For durable topic subscriptions you must specify the same <strong><code>activemq.client-id</code></strong> on the connection and <strong><code>activemq.subcriptionName</code></strong> on the subscribe prior to v5.7.0.</p><p><strong>Note</strong>: the spelling <strong><code>subcriptionName</code></strong> NOT <strong><code>subscriptionName</code></strong>. This is not intuitive, but it is how it is implemented in ActiveMQ 4.x.</p><p>For the 5.0 release of ActiveMQ, both <strong><code>subcriptionName</code></strong> and <strong><code>subscriptionName</code></strong> will be supported (<strong><code>subcriptionName</code></strong> was removed as of v5.6.0).</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>SUBSCRIBE</code></p></td><td colspan="1" rowspan="1"><p><code>selector</code></p></td><td colspan="1" rowspan="1"><p><code>string</code></p></td><td colspan="1" rowspan="1"><p>Specifies a JMS Selector using SQL 92 syntax as specified in the JMS 1.1 specification. This allows a filter to be applied to each message as part of the subscription.</p></td></tr></tbody></table></div>
diff --git a/structured-message-properties-and-mapmessages.xml b/structured-message-properties-and-mapmessages.xml
index 5294179..67198aa 100644
--- a/structured-message-properties-and-mapmessages.xml
+++ b/structured-message-properties-and-mapmessages.xml
@@ -1,13 +1,14 @@
-<div class="wiki-content maincontent"><h2 id="StructuredMessagePropertiesandMapMessages-StructuredMessagePropertiesandMapMessages">Structured Message Properties and MapMessages</h2>
+<div class="wiki-content maincontent"><h2>Structured Message Properties and MapMessages</h2>
<p>This JMS extension feature allows you to attach Map and List properties to any JMS Message or to use nested Maps and Lists inside a MapMessage. This allows you to efficiently send typesafe structured information in your messages without requiring the overhead of XML/XSD parsing which are parseable in other languages like C, C++, C# etc.</p>
<p>This enhancement allows any Map or List implementation to be used in the value parameter of these JMS methods</p>
-<ul><li><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html#setObjectProperty(java.lang.String,%20java.lang.Object)" rel="nofollow">Message.setObjectProperty(key, value)</a></li><li><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MapMessage.html#setObject(java.lang.String,%20java.lang.Object)" rel="nofollow">MapMessage.setObject(key, value)</a></li></ul>
+<ul><li><a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html#setObjectProperty(java.lang.String,%20java.lang.Object)">Message.setObjectProperty(key, value)</a></li><li><a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MapMessage.html#setObject(java.lang.String,%20java.lang.Object)">MapMessage.setObject(key, value)</a></li></ul>
<p>The value can be an arbitrarily nested structure of Maps, Lists and primitive objects (numbers and strings). To give you an idea of the kinds of things you can do you could try looking at these unit test cases</p>
-<ul><li><a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/test/message/NestedMapMessageTest.java">NestedMapMessageTest</a></li><li><a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/test/message/NestedMapAndListPropertyTest.java">NestedMapAndListPropertyTest</a></li></ul></div>
+<ul><li><a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/test/message/NestedMapMessageTest.java">NestedMapMessageTest</a></li><li><a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/test/message/NestedMapAndListPropertyTest.java">NestedMapAndListPropertyTest</a></li></ul>
+</div>
diff --git a/subscription-recovery-policy.xml b/subscription-recovery-policy.xml
index 1d5f17f..d8521ca 100644
--- a/subscription-recovery-policy.xml
+++ b/subscription-recovery-policy.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The subscription recovery policy allows you to go back in time when you subscribe to a topic.</p><p>For example imagine you are processing a price feed; you're using a federated network and either a network glitch occurs or someone kills the broker you're talking to. If you reconnect to another broker in the cluster you may have lost messages.</p><p>So we support a timed or fixed size recovery buffer so that if you reconnect to another broker within some time period (depending on volume & RAM this could be 30 seconds to 5 minutes), then any messages you missed during the downtime are redelivered before new messages are delivered to you.</p><p>For more information see <a shape="rect" href="retroactive-consumer.xml">Retroactive Consumer</a></p><h3 id="SubscriptionRecoveryPolicy-Lastimagecaching">Last image caching</h3><p>Its often common in financial market data type worlds to want to know the latest price of say IBM stock along with get all the future updates to the price. Historically you often had a request-reply snapshot quote service for the latest price, then you subscribe to a topic for updates. The issue is the client then has 2 APIs / middlewares to deal with - often quite different things - plus you have an ordering issue (race condition) - the update could beat the last price request so you can get out of order (going back in time to an old price, which could be very old).</p><p>One of our <em>subscription recovery policy</em> implementations is called <strong>Last Image Subscription Policy</strong> which will ensure that when you subscribe to a topic (say PRICES.NASDAQ.IBM), you will receive the last image (the last message that was sent on that topic) plus any updates which occur in the future, with ordering to ensure that the last image is always first before any new messages arrive.</p><p>A common problem in market data type situations is that you may have a cache of last image prices, then a feed of new price changes; if you request the last price from the cache and subscribe to new prices; depending on how you do it you can either, miss an update or receive a newer update before the old last image arrives (so either get out of order messages).</p><p>Note that you can configure the subscription recovery policy, and most other policies on different destinations or wildcards. So you may use last image policy for prices on topics only and use a buffered fixed size policy for other notifications on different topics etc.</p><h3 id="SubscriptionRecoveryPolicy-SummaryofAvailableRecoveryPolicies">Summary of Available Recovery Policies</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Policy Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Sample Configuration</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>FixedSizedSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><fixedSizedSubscriptionRecoveryPolicy maximumSize="1024"/></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Keep a fixed amount of memory in RAM for message history which is evicted in time order.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>FixedCountSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><fixedCountSubscriptionRecoveryPolicy maximumSize="100"/></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Keep a fixed count of last messages.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>LastImageSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><lastImageSubscriptionRecoveryPolicy/></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Keep only the last message.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>NoSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><noSubscriptionRecoveryPolicy/></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Disables message recovery.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>QueryBasedSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><queryBasedSubscriptionRecoveryPolicy query="JMSType = 'car' AND color = 'blue'"/></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Perform a user specific query mechanism to load any message they may have missed. Details on message selectors are available here:</p><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html" rel="nofollow">http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html</a><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>TimedSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><timedSubscriptionRecoveryPolicy recoverDuration="60000" /></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Keep a timed buffer of messages around in memory and use that to recover new subscriptions. Recovery time is in milliseconds.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">RetainedMessageSubscriptionRecoveryPolicy</td><td colspan="1" rowspan="1" class="confluenceTd"><r<span>etainedMessageSubscriptionRecoveryPolicy/></span></td><td colspan="1" rowspan="1" class="confluenceTd">Keep the last message with ActiveMQ.Retain property set to true</td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><p>The subscription recovery policy allows you to go back in time when you subscribe to a topic.</p><p>For example imagine you are processing a price feed; you're using a federated network and either a network glitch occurs or someone kills the broker you're talking to. If you reconnect to another broker in the cluster you may have lost messages.</p><p>So we support a timed or fixed size recovery buffer so that if you reconnect to another broker within some time period (depending on volume & RAM this could be 30 seconds to 5 minutes), then any messages you missed during the downtime are redelivered before new messages are delivered to you.</p><p>For more information see <link><page ri:content-title="Retroactive Consumer"></page></link></p><h3>Last image caching</h3><p>Its often common in financial market data type worlds to want to know the latest price of say IBM stock along with get all the future updates to the price. Historically you often had a request-reply snapshot quote service for the latest price, then you subscribe to a topic for updates. The issue is the client then has 2 APIs / middlewares to deal with - often quite different things - plus you have an ordering issue (race condition) - the update could beat the last price request so you can get out of order (going back in time to an old price, which could be very old).</p><p>One of our <em>subscription recovery policy</em> implementations is called <strong>Last Image Subscription Policy</strong> which will ensure that when you subscribe to a topic (say PRICES.NASDAQ.IBM), you will receive the last image (the last message that was sent on that topic) plus any updates which occur in the future, with ordering to ensure that the last image is always first before any new messages arrive.</p><p>A common problem in market data type situations is that you may have a cache of last image prices, then a feed of new price changes; if you request the last price from the cache and subscribe to new prices; depending on how you do it you can either, miss an update or receive a newer update before the old last image arrives (so either get out of order messages).</p><p>Note that you can configure the subscription recovery policy, and most other policies on different destinations or wildcards. So you may use last image policy for prices on topics only and use a buffered fixed size policy for other notifications on different topics etc.</p><h3>Summary of Available Recovery Policies</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Policy Name</p></th><th colspan="1" rowspan="1"><p>Sample Configuration</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>FixedSizedSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1"><p><fixedSizedSubscriptionRecoveryPolicy maximumSize="1024"/></p></td><td colspan="1" rowspan="1"><p>Keep a fixed amount of memory in RAM for message history which is evicted in time order.</p></td></tr><tr><td colspan="1" rowspan="1"><p>FixedCountSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1"><p><fixedCountSubscriptionRecoveryPolicy maximumSize="100"/></p></td><td colspan="1" rowspan="1"><p>Keep a fixed count of last messages.</p></td></tr><tr><td colspan="1" rowspan="1"><p>LastImageSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1"><p><lastImageSubscriptionRecoveryPolicy/></p></td><td colspan="1" rowspan="1"><p>Keep only the last message.</p></td></tr><tr><td colspan="1" rowspan="1"><p>NoSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1"><p><noSubscriptionRecoveryPolicy/></p></td><td colspan="1" rowspan="1"><p>Disables message recovery.</p></td></tr><tr><td colspan="1" rowspan="1"><p>QueryBasedSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1"><p><queryBasedSubscriptionRecoveryPolicy query="JMSType = 'car' AND color = 'blue'"/></p></td><td colspan="1" rowspan="1"><p>Perform a user specific query mechanism to load any message they may have missed. Details on message selectors are available here:</p><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html" rel="nofollow">http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html</a><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>TimedSubscriptionRecoveryPolicy</p></td><td colspan="1" rowspan="1"><p><timedSubscriptionRecoveryPolicy recoverDuration="60000" /></p></td><td colspan="1" rowspan="1"><p>Keep a timed buffer of messages around in memory and use that to recover new subscriptions. Recovery time is in milliseconds.</p></td></tr><tr><td colspan="1" rowspan="1">RetainedMessageSubscriptionRecoveryPolicy</td><td colspan="1" rowspan="1"><r<span>etainedMessageSubscriptionRecoveryPolicy/></span></td><td colspan="1" rowspan="1">Keep the last message with ActiveMQ.Retain property set to true</td></tr></tbody></table></div>
diff --git a/sun-jndi.xml b/sun-jndi.xml
index 5fa098b..8a090fd 100644
--- a/sun-jndi.xml
+++ b/sun-jndi.xml
@@ -2,18 +2,15 @@
<p>here's an example jndi.properties file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="b2ea7c88-9510-4469-a2f2-0687d16e3fc7" ac:name="code" ac:schema-version="1"><plain-text-body>
java.naming.factory.initial = com.sun.jndi.fscontext.RefFSContextFactory
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Here's an example .bindind file:</p>
<p>For ActiveMQ 4.x its </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="2defed32-5b5e-422b-8bf7-d46b8ab93991" ac:name="code" ac:schema-version="1"><plain-text-body>
Archive/ClassName=org.apache.activemq.command.ActiveMQQueue
Archive/FactoryName=org.apache.activemq.jndi.JNDIReferenceFactory
Archive/RefAddr/0/Type=physicalName
@@ -52,13 +49,11 @@
QueueConnectionFactory/RefAddr/3/Type=userName
QueueConnectionFactory/RefAddr/3/Content=defaultUser
QueueConnectionFactory/RefAddr/3/Encoding=String
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>For ActiveMQ 3.x it is </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="e1aa7918-9437-49e6-aafc-6795f88d1d3f" ac:name="code" ac:schema-version="1"><plain-text-body>
Archive/ClassName=org.activemq.message.ActiveMQQueue
Archive/FactoryName=org.activemq.jndi.JNDIReferenceFactory
Archive/RefAddr/0/Type=physicalName
@@ -103,6 +98,5 @@
QueueConnectionFactory/RefAddr/5/Type=useAsyncSend
QueueConnectionFactory/RefAddr/5/Content=true
QueueConnectionFactory/RefAddr/5/Encoding=String
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/support.xml b/support.xml
index b888756..14bfb82 100644
--- a/support.xml
+++ b/support.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Support-GettingHelp">Getting Help</h2><p>If you are experiencing problems using ActiveMQ then please report your problem to our <a shape="rect" class="external-link" href="http://issues.apache.org/activemq/browse/AMQ">Issue Tracker</a>. You may also find it useful to discuss your issues with the community on the <a shape="rect" href="discussion-forums.xml">Discussion Forums</a> or join one of our <a shape="rect" href="mailing-lists.xml">Mailing Lists</a>.</p><ul><li><a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ">Issue Tracker</a></li><li><a shape="rect" href="discussion-forums.xml">Discussion Forums</a></li><li><a shape="rect" href="mailing-lists.xml">Mailing Lists</a></li><li><a shape="rect" href="faq.xml">FAQ</a></li></ul><h3 id="Support-Howtogethelp">How to get help</h3><p>Before you report a problem you might want to read the <a shape="rect" href="faq.xml">FAQ</a>.<br clear="none"> Whenever you are reporting a problem please be sure to include as much information as possible; the more we know the more chance of a quicker resolution.</p><ul><li>Which <a shape="rect" class="external-link" href="http://activemq.apache.org/download.html">version</a> of ActiveMQ</li><li>What platform of Java (e.g., Java SE 6 with JRE/<a shape="rect" class="unresolved" href="#">JDK</a> 1.6.0 or J2SE 5 with JRE/<a shape="rect" class="unresolved" href="#">JDK</a> 1.5.0)</li><li>Any particular application/web server or container being used - if so what version?</li><li>Stack traces generally really help! If in doubt include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. It's very easy for us to skim-read past unnecessary parts of a stack trace.</li><li>Log output (e.g., <code>data/activemq.log</code>) can be useful too; sometimes <a shape="rect" href="how-do-i-change-the-logging.xml">enabling DEBUG logging</a> can help</li><li>Your code & configuration files are often useful</li></ul><h3 id="Support-Howtogethelpfaster">How to get help faster</h3><p>We can help you much quicker if you try the following</p><ul><li>Provide us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug, can you create a test case to demonstrate the bug?</li><li><a shape="rect" href="contributing.xml">Submit a patch</a> fixing the bug! (We also buy you beer when we meet you if you submit bug fixes <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"> )</li><li>For memory leaks or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if it's huge) to the JIRA we can normally fix things much faster. e.g. you could run <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html" rel="nofollow">jmap</a>/<a shape="rect" class="external-link" href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html" rel="nofollow">jhat</a>, JProfiler or YourKit on your code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that.</li></ul><h2 id="Support-CommercialSupport">Commercial Support</h2><p>This is an open source project, so the amount of time we have available to help resolve your issue is often limited as all help is provided on a volunteer basis. If you want to get priority help, need to get up to speed quickly, require some training or mentoring, or need full 24 x 7 production support you should contact a commercial company specializing in ActiveMQ support such as...</p><ul><li><a shape="rect" class="external-link" href="https://apifocal.com" rel="nofollow">apifocal</a> is a Professional Services company. Headquartered near Washington, DC, USA, APIfocal provides consulting and training for leveraging the Apache Integration stack and commercial ESBs at large scale, adding automation and devops capabilities.</li><li><a shape="rect" class="external-link" href="http://mediadriver.com" rel="nofollow">Media Driver</a> provides consulting services and management tools for Apache ActiveMQ and the Apache Integration stack for both the commercial and public sector.  We bring a full suite of project delivery services including business and technical analysis, proof of concepts, architectural guidance, best practice integration, and project management.  Media Driver offers training classes for developers and administrators, as well as middleware management software.</li><li><a shape="rect" class="external-link" href="http://www.openlogic.com/" rel="nofollow">Rogue Wave / OpenLogic</a> <span style="line-height: 1.4285715;">has a dedicated team of OSS experts offering </span><span style="line-height: 1.4285715;">round-the-clock Production Support with competitive SLAs for </span><span style="line-height: 1.4285715;">troubleshooting ActiveMQ issues and outages. Rogue </span><span style="line-height: 1.4285715;">Wave offers a comprehensive week-long instructor-led training program for </span><span style="line-height: 1.4285715;">developers and admins. Rogue Wave OpenLogic also provides Architecture </span><span style="line-height: 1.4285715;">and Design Consulting, and a Developer Support contract to assist in the </span><span style="line-height: 1.4285715;">development of messaging applications.</span></li><li><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/amq/" rel="nofollow">Red Hat</a> offers JBoss A-MQ, a supported distribution of Apache ActiveMQ, that include Enterprise Developer and Production Support, and offer training and consultancy for enterprise deployments.</li><li><a shape="rect" class="external-link" href="http://www.savoirtech.com" rel="nofollow">Savoir Technologies, Inc</a> provides enterprise consulting, training and support for ActiveMQ and a host of other Apache service containers. Savoir can provide best practice mentoring for developing with ActiveMQ, as well as architectural/design reviews, troubleshooting and SOA infrastructure implementations. Savoir's staff includes some of the contributors of ActiveMQ who are on the ground consulting and are familiar with real world implementations and issues.</li><li><a shape="rect" class="external-link" href="http://www.ttmsolutions.com/" rel="nofollow">Total Transaction Management (TTM)</a> provides ActiveMQ consulting and support, as well as security and <a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor_AMon.php/" rel="nofollow">monitoring</a> add-on products and <a shape="rect" class="external-link" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php" rel="nofollow">reference guide</a> for ActiveMQ.</li><li><a shape="rect" class="external-link" href="http://tomitribe.com" rel="nofollow">Tomitribe</a> are experts in Tomcat and ActiveMQ integration, champions of Open Source and Java EE.  Tomitribe offers consulting, training and support for TomEE, Tomcat, ActiveMQ, CXF and more.</li><li><a shape="rect" class="external-link" href="http://www.tytoease.com/activemq" rel="nofollow">TytoEASE</a> offers support, consulting and training on enterprise ready open source projects including ActiveMQ.   Support offerings are at three levels with guaranteed SLA's. The company's consulting work is short term to help troubleshoot, fine-tune, do architectural reviews or help with initial design.  TytoEASE's focus is on the Enterprise with how customers integrate open source with their current technologies.</li></ul></div>
+<div class="wiki-content maincontent"><h2>Getting Help</h2><p>If you are experiencing problems using ActiveMQ then please report your problem to our <a shape="rect" href="http://issues.apache.org/activemq/browse/AMQ">Issue Tracker</a>. You may also find it useful to discuss your issues with the community on the <link><page ri:content-title="Discussion Forums"></page></link> or join one of our <link><page ri:content-title="Mailing Lists"></page></link>.</p><ul><li><a shape="rect" href="https://issues.apache.org/jira/browse/AMQ">Issue Tracker</a></li><li><link><page ri:content-title="Discussion Forums"></page></link></li><li><link><page ri:content-title="Mailing Lists"></page></link></li><li><link><page ri:content-title="FAQ"></page></link></li></ul><h3>How to get help</h3><p>Before you report a problem you might want to read the <link><page ri:content-title="FAQ"></page></link>.<br clear="none"> Whenever you are reporting a problem please be sure to include as much information as possible; the more we know the more chance of a quicker resolution.</p><ul><li>Which <a shape="rect" href="http://activemq.apache.org/download.html">version</a> of ActiveMQ</li><li>What platform of Java (e.g., Java SE 6 with JRE/<link><page ri:content-title="JDK"></page><plain-text-link-body>JDK</plain-text-link-body></link> 1.6.0 or J2SE 5 with JRE/<link><page ri:content-title="JDK"></page><plain-text-link-body>JDK</plain-text-link-body></link> 1.5.0)</li><li>Any particular application/web server or container being used - if so what version?</li><li>Stack traces generally really help! If in doubt include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. It's very easy for us to skim-read past unnecessary parts of a stack trace.</li><li>Log output (e.g., <code>data/activemq.log</code>) can be useful too; sometimes <link><page ri:content-title="How do I change the logging"></page><plain-text-link-body>enabling DEBUG logging</plain-text-link-body></link> can help</li><li>Your code & configuration files are often useful</li></ul><h3>How to get help faster</h3><p>We can help you much quicker if you try the following</p><ul><li>Provide us with a JUnit test case that demonstrates your issue. e.g. if you think you've found a bug, can you create a test case to demonstrate the bug?</li><li><link><page ri:content-title="Contributing"></page><plain-text-link-body>Submit a patch</plain-text-link-body></link> fixing the bug! (We also buy you beer when we meet you if you submit bug fixes <emoticon ac:name="smile"></emoticon> )</li><li>For memory leaks or performance related issues, if you can run a profiler on your test case and attach the output as a file (or zipped file if it's huge) to the JIRA we can normally fix things much faster. e.g. you could run <a shape="rect" href="http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jmap.html">jmap</a>/<a shape="rect" href="http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html">jhat</a>, JProfiler or YourKit on your code and send us the output. To find memory leaks it's quicker to resolve if you can tell us what classes are taking up all of the RAM; we can normally figure out what's wrong from that.</li></ul><h2>Commercial Support</h2><p>This is an open source project, so the amount of time we have available to help resolve your issue is often limited as all help is provided on a volunteer basis. If you want to get priority help, need to get up to speed quickly, require some training or mentoring, or need full 24 x 7 production support you should contact a commercial company specializing in ActiveMQ support such as...</p><ul><li><a shape="rect" href="https://apifocal.com">apifocal</a> is a Professional Services company. Headquartered near Washington, DC, USA, APIfocal provides consulting and training for leveraging the Apache Integration stack and commercial ESBs at large scale, adding automation and devops capabilities.</li><li><a shape="rect" href="http://mediadriver.com">Media Driver</a> provides consulting services and management tools for Apache ActiveMQ and the Apache Integration stack for both the commercial and public sector.  We bring a full suite of project delivery services including business and technical analysis, proof of concepts, architectural guidance, best practice integration, and project management.  Media Driver offers training classes for developers and administrators, as well as middleware management software.</li><li><a shape="rect" href="http://www.openlogic.com/">Rogue Wave / OpenLogic</a> <span style="line-height: 1.4285715;">has a dedicated team of OSS experts offering </span><span style="line-height: 1.4285715;">round-the-clock Production Support with competitive SLAs for </span><span style="line-height: 1.4285715;">troubleshooting ActiveMQ issues and outages. Rogue </span><span style="line-height: 1.4285715;">Wave offers a comprehensive week-long instructor-led training program for </span><span style="line-height: 1.4285715;">developers and admins. Rogue Wave OpenLogic also provides Architecture </span><span style="line-height: 1.4285715;">and Design Consulting, and a Developer Support contract to assist in the </span><span style="line-height: 1.4285715;">development of messaging applications.</span></li><li><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/amq/">Red Hat</a> offers JBoss A-MQ, a supported distribution of Apache ActiveMQ, that include Enterprise Developer and Production Support, and offer training and consultancy for enterprise deployments.</li><li><a shape="rect" href="http://www.savoirtech.com">Savoir Technologies, Inc</a> provides enterprise consulting, training and support for ActiveMQ and a host of other Apache service containers. Savoir can provide best practice mentoring for developing with ActiveMQ, as well as architectural/design reviews, troubleshooting and SOA infrastructure implementations. Savoir's staff includes some of the contributors of ActiveMQ who are on the ground consulting and are familiar with real world implementations and issues.</li><li><a shape="rect" href="http://www.ttmsolutions.com/">Total Transaction Management (TTM)</a> provides ActiveMQ consulting and support, as well as security and <a shape="rect" href="http://www.ttmsolutions.com/Transactional_Software_Solutions/Active_Monitor_AMon.php/">monitoring</a> add-on products and <a shape="rect" href="http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php">reference guide</a> for ActiveMQ.</li><li><a shape="rect" href="http://tomitribe.com">Tomitribe</a> are experts in Tomcat and ActiveMQ integration, champions of Open Source and Java EE.  Tomitribe offers consulting, training and support for TomEE, Tomcat, ActiveMQ, CXF and more.</li><li><a shape="rect" href="http://www.tytoease.com/activemq">TytoEASE</a> offers support, consulting and training on enterprise ready open source projects including ActiveMQ.   Support offerings are at three levels with guaranteed SLA's. The company's consulting work is short term to help troubleshoot, fine-tune, do architectural reviews or help with initial design.  TytoEASE's focus is on the Enterprise with how customers integrate open source with their current technologies.</li></ul></div>
diff --git a/supporting-io-streams.xml b/supporting-io-streams.xml
index 6805a9b..4de4a8e 100644
--- a/supporting-io-streams.xml
+++ b/supporting-io-streams.xml
@@ -3,19 +3,19 @@
<p>There are a few issues to consider...</p>
-<h3 id="SupportingIOStreams-Usecasess">Use casess</h3>
+<h3>Use casess</h3>
<ol><li>many producers writing and only 1 consumer. Each consumer ideally should completely process 1 stream at once (IO streams are often blocking IO, so the client thread can't do much with other streams while its reading 1).</li><li>if a consumer gets 1Gb through a 10Gb file and dies, we need to re-deliver the messages to another consumer.</li></ol>
-<h3 id="SupportingIOStreams-Goal">Goal</h3>
+<h3>Goal</h3>
<p>Our goal should be</p>
<ul><li>for each consumer to process a single stream in one go before trying to process another.</li></ul>
-<h3 id="SupportingIOStreams-PossibleFailureConditions">Possible Failure Conditions</h3>
+<h3>Possible Failure Conditions</h3>
<ul><li>Consumer could die in the middle of reading a stream. Recovery options:
<ol><li>Trash the rest of the stream</li><li>Restart delivery of the stream to the next consumer</li><li>Continue delivery of the steam to the next consumer at the point of failure.</li></ol>
@@ -27,10 +27,11 @@
-<h3 id="SupportingIOStreams-ImplementationIssues">Implementation Issues</h3>
+<h3>Implementation Issues</h3>
<ul><li>we can use message groups to ensure the same consumer processes all messages for a given stream - but unfortunately message groups does not prevent a consumer being overloaded with more than one message group at a time - maybe thats a new feature we can add?</li><li>avoid the broker running out of RAM - so spool to disk (or throttle the producer) if the only consumer is working on a different stream.
<ul><li>If messages sent using transactions, major chanages need may need to be made to how we do transaction management and message journaling. Currently, all messages in a in progress transaction are held in memory until it commits (Synchronization callbacks are holding on the the messages). The journal currently holds on to all transacted messages in it's journal + memory until commit, it does now allow the journal to rollover messages that are part of transaction that is in progess.</li></ul>
</li><li>given that the entire stream must be processed in one go, we can only ACK the entire stream of messages - so we need to disable pre-fetch?
<ul><li>Prefetch disabling is not needed as the consumers send back a special kind of ack which only temporarily expands the prefetch window.</li></ul>
- </li></ul></div>
+ </li></ul>
+</div>
diff --git a/svn.xml b/svn.xml
index 593d620..5aff239 100644
--- a/svn.xml
+++ b/svn.xml
@@ -1,13 +1,3 @@
<div class="wiki-content maincontent">
-<h1 id="SVN-ActiveMQ5">ActiveMQ 5</h1><h2 id="SVN-WebBrowsingofthegitRepo">Web Browsing of the git Repo</h2><p>To browse via the web:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq.git">https://git-wip-us.apache.org/repos/asf?p=activemq.git</a></p>
-</div></div><h2 id="SVN-CheckingoutfromthegitRepo">Checking out from the git Repo</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf/activemq.git">https://git-wip-us.apache.org/repos/asf/activemq.git</a></p>
-</div></div><p>Only project developers can commit to the git repo via this method. SSH must be installed on your client machine. Enter your site password when prompted.</p><h2 id="SVN-Buildingthecode">Building the code</h2><p>To then build the code, see <a shape="rect" href="building.xml">Building</a>.</p><p> </p><h1 id="SVN-ActiveMQArtemis">ActiveMQ Artemis</h1><h2 id="SVN-WebBrowsingoftheASFgitRepo">Web Browsing of the ASF git Repo</h2><p>To browse via the web:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git">https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git</a></p>
-</div></div><h2 id="SVN-BrowsingtheGithubRepo">Browsing the Github Repo </h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p><a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">https://github.com/apache/activemq-artemis</a></p>
-</div></div><h2 id="SVN-CheckingoutfromtheGithubRepo">Checking out from the Github Repo</h2><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>git clone <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">https://github.com/apache/activemq-artemis</a></p>
-</div></div><p><strong>Committers:</strong> Please follow the instructions for properly configuring the <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/SUMMARY.md" rel="nofollow">Instructions for Core Contributors/Hacking Guide</a></p><p><strong>Contributors:</strong> Please create a <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis" rel="nofollow">pull request</a> to contribute changes to the source code. </p><h2 id="SVN-Buildingthecode.1">Building the code</h2><p>To then build the code, take a look at <a shape="rect" class="external-link" href="https://github.com/apache/activemq-artemis/blob/master/docs/hacking-guide/en/building.md" rel="nofollow">Building the distribution</a></p></div>
+<structured-macro ac:macro-id="446bf52c-1430-4084-b1cf-c71996cbb763" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Source"></page></link></parameter></structured-macro></div>
diff --git a/sybase.xml b/sybase.xml
index 0c40d81..6e4e76d 100644
--- a/sybase.xml
+++ b/sybase.xml
@@ -1,29 +1,25 @@
-<div class="wiki-content maincontent"><h2 id="Sybase-Sybase">Sybase</h2>
+<div class="wiki-content maincontent"><h2>Sybase</h2>
<p>A dataSource targetting a Sybase ASE database can be configured as follows:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Sybase Datasource</b></div><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <bean id="sybase-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
+<structured-macro ac:macro-id="9f1d2886-7bd4-47e4-a25e-9395e8f70bb8" ac:name="code" ac:schema-version="1"><parameter ac:name="lang">xml</parameter><parameter ac:name="title">Sybase Datasource</parameter><plain-text-body> <bean id="sybase-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
<!-- using jConnect -->
- <property name="driverClassName" value="com.sybase.jdbc4.jdbc.SybDriver"/>
- <property name="url" value="jdbc:sybase:Tds:localhost:4000/activemq"/>
+ <property name="driverClassName" value="com.sybase.jdbc4.jdbc.SybDriver"/>
+ <property name="url" value="jdbc:sybase:Tds:localhost:4000/activemq"/>
<!-- using JTDS -->
- <!-- <property name="driverClassName" value="net.sourceforge.jtds.jdbc.Driver"/> -->
- <!-- <property name="url" value="jdbc:jtds:sybase://localhost:4000/activemq"/> -->
+ <!-- <property name="driverClassName" value="net.sourceforge.jtds.jdbc.Driver"/> -->
+ <!-- <property name="url" value="jdbc:jtds:sybase://localhost:4000/activemq"/> -->
- <property name="username" value="XXX" />
- <property name="password" value="YYY" />
+ <property name="username" value="XXX" />
+ <property name="password" value="YYY" />
<!-- and so on with pool config -->
</bean>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>When working on a given Sybase ASE database, each operation (e.g. statement execution) is appended to the transaction log. This log grows over time, and space has to be freed in order to let the server keep running. ASE is able to free space up to the oldest opened transaction; that is, if you keep a transaction open for too long, the transaction log only grows - until the allocated space is full and the database goes down. So when using the Master-Slave feature of ActiveMQ with a database lock on table ACTIVEMQ_LOCK a synchronization monitor (see <a shape="rect" class="external-link" href="http://activemq.apache.org/jdbc-master-slave.html">http://activemq.apache.org/jdbc-master-slave.html</a>), you have to be careful. If you use only one dataSource, hence only one database, then the lock mechanism shall keep a transaction indefinitely open, and while messages are persisted the transaction log shall grow until you run out of space. It is therefore strongly advised to use a dedicated database for this lock: just define another dataSource targeting a minimal database holding no data (only the ACTIVEMQ_LOCK table) and use it as a lockDataSource in your configuration.</p>
+<p>When working on a given Sybase ASE database, each operation (e.g. statement execution) is appended to the transaction log. This log grows over time, and space has to be freed in order to let the server keep running. ASE is able to free space up to the oldest opened transaction; that is, if you keep a transaction open for too long, the transaction log only grows - until the allocated space is full and the database goes down. So when using the Master-Slave feature of ActiveMQ with a database lock on table ACTIVEMQ_LOCK a synchronization monitor (see <a shape="rect" href="http://activemq.apache.org/jdbc-master-slave.html">http://activemq.apache.org/jdbc-master-slave.html</a>), you have to be careful. If you use only one dataSource, hence only one database, then the lock mechanism shall keep a transaction indefinitely open, and while messages are persisted the transaction log shall grow until you run out of space. It is therefore strongly advised to use a dedicated database for this lock: just define another dataSource targeting a minimal database holding no data (only the ACTIVEMQ_LOCK table) and use it as a lockDataSource in your configuration.</p>
<p>Example:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<persistenceAdapter>
- <jdbcPersistenceAdapter dataSource="#sybase-ds" lockDataSource="#another-sybase-ds"/>
-</persistenceAdapter>]]></script>
-</div></div></div>
+<structured-macro ac:macro-id="13c733a6-b72d-4c63-952e-97d01ac32f2e" ac:name="code" ac:schema-version="1"><parameter ac:name="lang">xml</parameter><plain-text-body><persistenceAdapter>
+ <jdbcPersistenceAdapter dataSource="#sybase-ds" lockDataSource="#another-sybase-ds"/>
+</persistenceAdapter></plain-text-body></structured-macro></div>
diff --git a/tcp-transport-reference.xml b/tcp-transport-reference.xml
index 70027d5..5de9955 100644
--- a/tcp-transport-reference.xml
+++ b/tcp-transport-reference.xml
@@ -1,8 +1,4 @@
-<div class="wiki-content maincontent"><h3 id="TCPTransportReference-TheTCPTransport">The TCP Transport</h3><p>The TCP transport allows clients to connect to a remote ActiveMQ broker using a TCP socket. These configuration options can be used to tune the underlying TCP transport on either the client-side using the JMS client's connection URI string or on a broker's transport connector URI.</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">Use Correct Prefix!</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The options below should be prefixed with <code><strong>transport.*</strong></code> when used on a broker's transport connector definition. On the client-side, however, the <strong><code>transport.*</code></strong> prefix <em>must</em> be omitted.</p></div></div><h4 id="TCPTransportReference-ConfigurationSyntax">Configuration Syntax</h4><p><code><strong>tcp://hostname:port?key=value</strong></code></p><h5 id="TCPTransportReference-Examples">Examples</h5><p>Broker side (in <strong><code>TransportConnector</code></strong>):</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>tcp://localhost:61616?transport.threadName&transport.trace=false&transport.soTimeout=60000
-</pre>
-</div></div><p>Client side (in <strong><code>brokerURL</code></strong>):</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>tcp://localhost:61616?threadName&trace=false&soTimeout=60000
-</pre>
-</div></div><h5 id="TCPTransportReference-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><code>backlog</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>5000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the maximum number of connections waiting to be accepted by the transport server socket.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>closeAsync</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> the socket close call happens asynchronously. This parameter should be set to <strong><code>false</code></strong> for protocols like STOMP, that are commonly used in situations where a new connection is created for each read or write. Doing so ensures the socket close call happens synchronously. A synchronous close prevents the broker from running out of available sockets owing to the rapid cycling of connections. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>connectionTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>>=1</code></strong> the value sets the connection timeout in milliseconds. A value of <strong><code>0</code></strong> denotes no timeout. Negative values are ignored.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>daemon</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> the transport thread will run in daemon mode. Set this parameter to <strong><code>true</code></strong> when embedding the broker in a Spring container or a web container to allow the container to shut down correctly.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>diffServ</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(Client only) The preferred Differentiated Services traffic class to be set on outgoing packets, as described in RFC 2475. Valid integer values: <strong><code>[0,64]</code></strong>. Valid string values: <strong><code>EF</code>, <code>AF[1-3][1-4]</code></strong> or <strong><code>CS[0-7]</code></strong>.</p><p>With JDK 6, only works when the JVM uses the IPv4 stack. To use the IPv4 stack set the system property <strong><code><a shape="rect" class="external-link" href="http://java.net" rel="nofollow">java.net</a>.preferIPv4Stack=true</code></strong>.</p><p><strong>Note</strong>: it's invalid to specify both <strong><code>diffServ</code></strong> and <strong><code>typeOfService</code></strong> at the same time as they share the same position in the TCP/IP packet headers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>dynamicManagement</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> the <strong><code>TransportLogger</code></strong> can be managed by JMX.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ioBufferSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>8 * 1024</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the size of the buffer to be used between the TCP layer and the OpenWire layer where <strong><code>wireFormat</code></strong> based marshaling occurs.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>jmxPort</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1099</code></p></td><td colspan="1" rowspan="1" class="confluenceTd" style="text-align: left;"><p>(Client Only)</p><p>Specifies the port that will be used by the JMX server to manage the <strong><code>TransportLoggers</code></strong>. This should only be set, via URI, by either a client producer or consumer as the broker creates its own JMX server.</p><p>Specifying an alternate JMX port is useful for developers that test a broker and client on the same machine and need to control both via JMX.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>keepAlive</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code>, </strong>enables <a shape="rect" class="external-link" href="http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html" rel="nofollow">TCP KeepAlive</a> on the broker connection to prevent connections from timing out at the TCP level.</p><p>This should <em>not</em> be confused with <strong><code>KeepAliveInfo</code></strong> messages as used by the <strong><code>InactivityMonitor</code>.</strong></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>logWriterName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>default</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the name of the <strong><code>org.apache.activemq.transport.LogWriter</code></strong> implementation to use.</p><p>Names are mapped to classes in the <strong><code>resources/META-INF/services/org/apache/activemq/transport/logwriters</code></strong> directory.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>maximumConnections</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Integer.MAX_VALUE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of sockets allowed for this broker.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>minmumWireFormatVersion</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The minimum remote <strong><code>wireFormat</code></strong> version that will be accepted (note the misspelling).</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><strong>Note</strong>: when the remote <strong><code>wireFormat</code></strong> version is lower than the configured minimum acceptable version an exception will be thrown and the connection attempt will be refused.</p></div></div><p>A value of <code><strong>0</strong></code> denotes no checking of the remote <strong><code>wireFormat</code></strong> version.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>socketBufferSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>64 * 1024</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the size, in bytes, for the accepted socket's read and write buffers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>soLinger</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>Integer.MIN_VALUE</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the socket's option <strong><code>soLinger</code></strong> when the value is <strong><code>> -1</code></strong>.</p><p>When set to <strong><code>-1</code></strong> the <strong><code>soLinger</code></strong> socket option is disabled.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>soTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the socket's read timeout in milliseconds.</p><p>A value of <code><strong>0</strong></code> denotes no timeout.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>soWriteTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the socket's write timeout in milliseconds. If the socket write operation does not complete before the specified timeout, the socket will be closed.</p><p>A value of <strong>0</strong> denotes no timeout.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>stackSize</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Set the stack size of the transport's background reading thread. Must be specified in multiples of <strong><code>128K</code></strong>.</p><p>A value of <code><strong>0</strong></code> indicates that this parameter is ignored.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>startLogging</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> the <strong><code>TransportLogger</code></strong> object of the Transport stack will initially write messages to the log.</p><p>This parameter is ignored unless <strong><code>trace=true</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>tcpNoDelay</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If <strong><code>true</code></strong> the socket's option <strong><code>TCP_NODELAY</code></strong> is set. This disables Nagle's algorithm for small packet transmission.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>threadName</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>N/A</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When this parameter is specified the name of the thread is modified during the invocation of a transport. The remote address is appended so that a call stuck in a transport method will have the destination information in the thread name. This is extremely useful when using thread dumps for degugging.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trace</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Causes all commands that are sent over the transport to be logged.</p><p>To view the logged output define the <strong><code>Log4j</code></strong> logger: <strong><code>log4j.logger.org.apache.activemq.transport.TransportLogger=DEBUG</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>trafficClass</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The Traffic Class to be set on the socket.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>typeOfService</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(Client only) The preferred Type of Service value to be set on outgoing packets. Valid integer values: <strong><code>[0,256]</code></strong>.</p><p>With JDK 6, only works when the JVM is configured to use the IPv4 stack. To use the IPv4 stack set the system property <strong><code><a shape="rect" class="external-link" href="http://java.net" rel="nofollow">java.net</a>.preferIPv4Stack=true</code></strong>.</p><p><strong>Note</strong>: it's invalid to specify both <strong><code>diffServ</code></strong> and <strong><code>typeOfService</code></strong> at the same time as they share the same position in the TCP/IP packet headers.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useInactivityMonitor</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>false</code></strong> the <code><strong>InactivityMonitor</strong></code> is disabled and connections will never time out.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useKeepAlive</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code> <code> KeepAliveInfo</code></strong> messages are sent on an idle connection to prevent it from timing out.</p><p>If this parameter is <strong><code>false</code></strong> connections will still timeout if no data was received on the connection for the specified amount of time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useLocalHost</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong> local connections will be made using the value <strong><code>localhost</code></strong> instead of the actual local host name.</p><p>On some operating systems, such as <strong><code>OS X</code></strong>, it's not possible to connect as the local host name so <strong><code>localhost</code></strong> is better.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>useQueueForAccept</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong> accepted sockets are placed onto a queue for asynchronous processing using a separate thread.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>wireFormat</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>default</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the <strong><code>wireFormat</code></strong> factory to use.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>wireFormat.*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>N/A</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Properties with this prefix are used to configure the <strong><code>wireFormat</code></strong>.</p><p>See <a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a> for more information.</p></td></tr></tbody></table></div><p> </p><h5 id="TCPTransportReference-DifferentiatedServicesorTypesofService">Differentiated Services or Types of Service</h5><p>There is support for setting Differentiated Services - as outlined in <a shape="rect" class="external-link" href="http://tools.ietf.org/html/rfc2475" rel="nofollow">IETF RCF 2475</a>. In order to configure the broker so that all outgoing packets from the broker match the DSCP values set on incoming packets - you will need to apply IP Tables scripts - found <a shape="rect" href="tcp-transport-reference.data/brokerConfig.tar.gz?version=1&modificationDate=1273219000000&api=v2" data-linked-resource-id="20873268" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="brokerConfig.tar.gz" data-linked-resource-content-type="application/x-gzip" data-linked-resource-container-id="35993" data-linked-resource-container-version="57">here</a>.</p></div>
+<div class="wiki-content maincontent"><h3>The TCP Transport</h3><p>The TCP transport allows clients to connect to a remote ActiveMQ broker using a TCP socket. These configuration options can be used to tune the underlying TCP transport on either the client-side using the JMS client's connection URI string or on a broker's transport connector URI.</p><structured-macro ac:macro-id="421bb327-b312-423e-a169-8efdc1388614" ac:name="info" ac:schema-version="1"><parameter ac:name="title">Use Correct Prefix!</parameter><rich-text-body><p>The options below should be prefixed with <code><strong>transport.*</strong></code> when used on a broker's transport connector definition. On the client-side, however, the <strong><code>transport.*</code></strong> prefix <em>must</em> be omitted.</p></rich-text-body></structured-macro><h4>Configuration Syntax</h4><p><code><strong>tcp://hostname:port?key=value</strong></code></p><h5>Examples</h5><p>Broker side (in <strong><code>TransportConnector</code></strong>):</p><structured-macro ac:macro-id="a3b112f3-a242-4215-b9ce-e71c237f4230" ac:name="noformat" ac:schema-version="1"><plain-text-body>tcp://localhost:61616?transport.threadName&transport.trace=false&transport.soTimeout=60000
+</plain-text-body></structured-macro><p>Client side (in <strong><code>brokerURL</code></strong>):</p><structured-macro ac:macro-id="7141b5fe-2dae-4b37-9f62-99f97ff7422e" ac:name="noformat" ac:schema-version="1"><plain-text-body>tcp://localhost:61616?threadName&trace=false&soTimeout=60000
+</plain-text-body></structured-macro><h5>Transport Options</h5><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>backlog</code></p></td><td colspan="1" rowspan="1"><p><code>5000</code></p></td><td colspan="1" rowspan="1"><p>Specifies the maximum number of connections waiting to be accepted by the transport server socket.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>closeAsync</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> the socket close call happens asynchronously. This parameter should be set to <strong><code>false</code></strong> for protocols like STOMP, that are commonly used in situations where a new connection is created for each read or write. Doing so ensures the socket close call happens synchronously. A synchronous close prevents the broker from running out of available sockets owing to the rapid cycling of connections. </p></td></tr><tr><td colspan="1" rowspan="1"><p><code>connectionTimeout</code></p></td><td colspan="1" rowspan="1"><p><code>30000</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>>=1</code></strong> the value sets the connection timeout in milliseconds. A value of <strong><code>0</code></strong> denotes no timeout. Negative values are ignored.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>daemon</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> the transport thread will run in daemon mode. Set this parameter to <strong><code>true</code></strong> when embedding the broker in a Spring container or a web container to allow the container to shut down correctly.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>diffServ</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>(Client only) The preferred Differentiated Services traffic class to be set on outgoing packets, as described in RFC 2475. Valid integer values: <strong><code>[0,64]</code></strong>. Valid string values: <strong><code>EF</code>, <code>AF[1-3][1-4]</code></strong> or <strong><code>CS[0-7]</code></strong>.</p><p>With JDK 6, only works when the JVM uses the IPv4 stack. To use the IPv4 stack set the system property <strong><code><a shape="rect" href="http://java.net">java.net</a>.preferIPv4Stack=true</code></strong>.</p><p><strong>Note</strong>: it's invalid to specify both <strong><code>diffServ</code></strong> and <strong><code>typeOfService</code></strong> at the same time as they share the same position in the TCP/IP packet headers.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>dynamicManagement</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> the <strong><code>TransportLogger</code></strong> can be managed by JMX.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ioBufferSize</code></p></td><td colspan="1" rowspan="1"><p><code>8 * 1024</code></p></td><td colspan="1" rowspan="1"><p>Specifies the size of the buffer to be used between the TCP layer and the OpenWire layer where <strong><code>wireFormat</code></strong> based marshaling occurs.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>jmxPort</code></p></td><td colspan="1" rowspan="1"><p><code>1099</code></p></td><td colspan="1" rowspan="1" style="text-align: left;"><p>(Client Only)</p><p>Specifies the port that will be used by the JMX server to manage the <strong><code>TransportLoggers</code></strong>. This should only be set, via URI, by either a client producer or consumer as the broker creates its own JMX server.</p><p>Specifying an alternate JMX port is useful for developers that test a broker and client on the same machine and need to control both via JMX.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>keepAlive</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code>, </strong>enables <a shape="rect" href="http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html">TCP KeepAlive</a> on the broker connection to prevent connections from timing out at the TCP level.</p><p>This should <em>not</em> be confused with <strong><code>KeepAliveInfo</code></strong> messages as used by the <strong><code>InactivityMonitor</code>.</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><code>logWriterName</code></p></td><td colspan="1" rowspan="1"><p><code>default</code></p></td><td colspan="1" rowspan="1"><p>Sets the name of the <strong><code>org.apache.activemq.transport.LogWriter</code></strong> implementation to use.</p><p>Names are mapped to classes in the <strong><code>resources/META-INF/services/org/apache/activemq/transport/logwriters</code></strong> directory.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>maximumConnections</code></p></td><td colspan="1" rowspan="1"><p><code>Integer.MAX_VALUE</code></p></td><td colspan="1" rowspan="1"><p>The maximum number of sockets allowed for this broker.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>minmumWireFormatVersion</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>The minimum remote <strong><code>wireFormat</code></strong> version that will be accepted (note the misspelling).</p><structured-macro ac:macro-id="36e9c7c5-139c-4f68-8e81-947517332577" ac:name="info" ac:schema-version="1"><rich-text-body><p><strong>Note</strong>: when the remote <strong><code>wireFormat</code></strong> version is lower than the configured minimum acceptable version an exception will be thrown and the connection attempt will be refused.</p></rich-text-body></structured-macro><p>A value of <code><strong>0</strong></code> denotes no checking of the remote <strong><code>wireFormat</code></strong> version.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>socketBufferSize</code></p></td><td colspan="1" rowspan="1"><p><code>64 * 1024</code></p></td><td colspan="1" rowspan="1"><p>Sets the size, in bytes, for the accepted socket's read and write buffers.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>soLinger</code></p></td><td colspan="1" rowspan="1"><p><code>Integer.MIN_VALUE</code></p></td><td colspan="1" rowspan="1"><p>Sets the socket's option <strong><code>soLinger</code></strong> when the value is <strong><code>> -1</code></strong>.</p><p>When set to <strong><code>-1</code></strong> the <strong><code>soLinger</code></strong> socket option is disabled.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>soTimeout</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Sets the socket's read timeout in milliseconds.</p><p>A value of <code><strong>0</strong></code> denotes no timeout.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>soWriteTimeout</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Sets the socket's write timeout in milliseconds. If the socket write operation does not complete before the specified timeout, the socket will be closed.</p><p>A value of <strong>0</strong> denotes no timeout.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>stackSize</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>Set the stack size of the transport's background reading thread. Must be specified in multiples of <strong><code>128K</code></strong>.</p><p>A value of <code><strong>0</strong></code> indicates that this parameter is ignored.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>startLogging</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> the <strong><code>TransportLogger</code></strong> object of the Transport stack will initially write messages to the log.</p><p>This parameter is ignored unless <strong><code>trace=true</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>tcpNoDelay</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>If <strong><code>true</code></strong> the socket's option <strong><code>TCP_NODELAY</code></strong> is set. This disables Nagle's algorithm for small packet transmission.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>threadName</code></p></td><td colspan="1" rowspan="1"><p><code>N/A</code></p></td><td colspan="1" rowspan="1"><p>When this parameter is specified the name of the thread is modified during the invocation of a transport. The remote address is appended so that a call stuck in a transport method will have the destination information in the thread name. This is extremely useful when using thread dumps for degugging.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>trace</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>Causes all commands that are sent over the transport to be logged.</p><p>To view the logged output define the <strong><code>Log4j</code></strong> logger: <strong><code>log4j.logger.org.apache.activemq.transport.TransportLogger=DEBUG</code></strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>trafficClass</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>The Traffic Class to be set on the socket.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>typeOfService</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>(Client only) The preferred Type of Service value to be set on outgoing packets. Valid integer values: <strong><code>[0,256]</code></strong>.</p><p>With JDK 6, only works when the JVM is configured to use the IPv4 stack. To use the IPv4 stack set the system property <strong><code><a shape="rect" href="http://java.net">java.net</a>.preferIPv4Stack=true</code></strong>.</p><p><strong>Note</strong>: it's invalid to specify both <strong><code>diffServ</code></strong> and <strong><code>typeOfService</code></strong> at the same time as they share the same position in the TCP/IP packet headers.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useInactivityMonitor</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>false</code></strong> the <code><strong>InactivityMonitor</strong></code> is disabled and connections will never time out.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useKeepAlive</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code> <code> KeepAliveInfo</code></strong> messages are sent on an idle connection to prevent it from timing out.</p><p>If this parameter is <strong><code>false</code></strong> connections will still timeout if no data was received on the connection for the specified amount of time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useLocalHost</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code></strong> local connections will be made using the value <strong><code>localhost</code></strong> instead of the actual local host name.</p><p>On some operating systems, such as <strong><code>OS X</code></strong>, it's not possible to connect as the local host name so <strong><code>localhost</code></strong> is better.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>useQueueForAccept</code></p></td><td colspan="1" rowspan="1"><p><code>true</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code></strong> accepted sockets are placed onto a queue for asynchronous processing using a separate thread.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>wireFormat</code></p></td><td colspan="1" rowspan="1"><p><code>default</code></p></td><td colspan="1" rowspan="1"><p>The name of the <strong><code>wireFormat</code></strong> factory to use.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>wireFormat.*</code></p></td><td colspan="1" rowspan="1"><p><code>N/A</code></p></td><td colspan="1" rowspan="1"><p>Properties with this prefix are used to configure the <strong><code>wireFormat</code></strong>.</p><p>See <link><page ri:content-title="Configuring Wire Formats"></page></link> for more information.</p></td></tr></tbody></table><p> </p><h5>Differentiated Services or Types of Service</h5><p>There is support for setting Differentiated Services - as outlined in <a shape="rect" href="http://tools.ietf.org/html/rfc2475">IETF RCF 2475</a>. In order to configure the broker so that all outgoing packets from the broker match the DSCP values set on incoming packets - you will need to apply IP Tables scripts - found <link><attachment ri:filename="brokerConfig.tar.gz"></attachment><plain-text-link-body>here</plain-text-link-body></link>.</p></div>
diff --git a/team.xml b/team.xml
index db0ec04..29494b1 100644
--- a/team.xml
+++ b/team.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h1 id="Team-ActiveMQCommunity">ActiveMQ Community</h1><p>This page lists who we are. By all means add yourself to the list - lets sort it in alphabetical order</p><h3 id="Team-Committers">Committers</h3><p>"A committer is a developer that was given write access to the code repository and has a signed Contributor License Agreement (<a shape="rect" class="external-link" href="http://www.apache.org/licenses/icla.txt">CLA</a>) on file. They have an apache.org mail address. Not needing to depend on other people for the patches, they are actually making short-term decisions for the project. The PMC can (even tacitly) agree and approve it into permanency, or they can reject it. Remember that the PMC makes the decisions, not the individual people." – from <a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Name</th><th colspan="1" rowspan="1" class="confluenceTh">ID</th><th colspan="1" rowspan="1" class="confluenceTh">Organisation</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Aaron Mulder</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ammulder">ammulder</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://chariotsolutions.com" rel="nofollow">Chariot Solutions</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Adrian Co</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aco">aco</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Alan D. Cabrera</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maguro">maguro</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Arthur Naseef</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=artnaseef">artnaseef</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.savoirtech.com/" rel="nofollow">Savoir Technologies</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Brian McCallister</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brianm">brianm</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://ning.com" rel="nofollow">Ning</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Bruce Snyder</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bsnyder">bsnyder </a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://springsource.com/" rel="nofollow">SpringSource</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://cmoulliard.blogspot.com" rel="nofollow">Charles Moulliard</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cmoulliard">cmoulliard</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a> <span> </span></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Christopher Shannon</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cshannon">cshannon</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Christian Posta</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ceposta">ceposta</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://davsclaus.blogspot.com/" rel="nofollow">Claus Ibsen</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=davsclaus">davsclaus </a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Colin MacNaughton</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cmacnaug">cmacnaug</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.nighttale.net" rel="nofollow">Dejan Bosanac</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dejanb">dejanb </a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Dag Liodden</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=daggerrz">daggerrz </a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.giantleap.no" rel="nofollow">Giant Leap Technologies</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Dain Sundstrom</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dain">dain </a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Darwin Flores</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dflores">dflores </a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">David Jencks</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=djencks">djencks </a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.ibm.com" rel="nofollow">IBM</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Dennis Cook</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dcook">dcook</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://bevocal.com" rel="nofollow">BeVocal</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Frederick Oconer</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=foconer">foconer </a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Gary Tully</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gtully">gtully</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Geir Magnusson Jr.</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=geir">geir</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Greg Wilkins</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gregw">gregw</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://mortbay.com" rel="nofollow">MortBay</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Guillaume Nodet</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gnodet">gnodet</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Hadrian Zbarcea</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hadrian">hadrian</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.talend.com/" rel="nofollow">Talend</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://hiramchirino.com" rel="nofollow">Hiram Chirino</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=chirino">chirino</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.JacekLaskowski.pl" rel="nofollow">Jacek Laskowski</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jlaskowski">jlaskowski</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://macstrac.blogspot.com/" rel="nofollow">James Strachan</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jstrachan">jstrachan</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jason van Zyl</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jason">jason</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jean-Baptiste Onofré</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jbonofre">jbonofre</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.talend.com/" rel="nofollow">Talend</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jeff Genender</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jgenender">jgenender</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.savoirtech.com/" rel="nofollow">Savoir Technologies</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://plus.google.com/113674252934234025601/posts" rel="nofollow">Jim Gomes</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jgomes">jgomes</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Joe Walnes</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=joe">joe</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.google.com" rel="nofollow">Google</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jonas Lim</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jlim">jlim</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://janstey.blogspot.com/" rel="nofollow">Jonathan Anstey</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=janstey">janstey</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Joseph Gapuz</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jgapuz">jgapuz</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Matt Pavlovich</td><td colspan="1" rowspan="1" class="confluenceTd">mattrpav</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.mediadriver.com" rel="nofollow">Media Driver</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Max Kington</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mkington">mkington</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://betfair.com" rel="nofollow">BetFair</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Merwin Yap</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=myap">myap</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.gaffneyware.com/" rel="nofollow">Michael Gaffney</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mgaffney">mgaffney</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.boxtone.com" rel="nofollow">BoxTone</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Nathan Mittler</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nmittler">nmittler</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Nicky Sandhu</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nsandhu">nsandhu</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Patrick Villacorta</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pvillacorta">pvillacorta</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Peter Brooke</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pbrooke">pbrooke</a></td><td colspan="1" rowspan="1" class="confluenceTd">Prepulse</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ramzi Saba</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rsaba">rsaba</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.optaros.com" rel="nofollow">Optaros</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://rajdavies.blogspot.com/" rel="nofollow">Rob Davies</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rajdavies">rajdavies</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Roman Kalukiewicz</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=romkal">romkal</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Tatu Saloranta</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowtowncoder">cowtowncoder</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://timbish.blogspot.com/" rel="nofollow">Timothy Bish</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tabish">tabish</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://willemjiang.blogspot.com/" rel="nofollow">Willem Jiang</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ningjiang">ningjiang</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">William Tam</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wtam">wtam</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Marc Schöchlin</td><td colspan="1" rowspan="1" class="confluenceTd">mschoechlin</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr></tbody></table></div><h3 id="Team-Contributors">Contributors</h3><p>"A developer is a user who contributes to a project in the form of code or documentation. They take extra steps to participate in a project, are active on the developer mailing list, participate in discussions, provide patches, documentation, suggestions, and criticism. Developers are also known as contributors." – from <a shape="rect" class="external-link" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a></p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Name</th><th colspan="1" rowspan="1" class="confluenceTh">Organisation</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Aaron Crickenberger</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Al Maw</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Aleksi Kallio</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.deanspot.org/blog/alex" rel="nofollow">Alex Dean</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.meteostar.com" rel="nofollow">IPS Meteostar</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Andrew Deason</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Andy Depue</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Axel Hohaus</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Arjan Moraal</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Barry Kaplan</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://twitter.com/bennetelli" rel="nofollow">Bennet Schulz</a></td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="https://www.codecentric.de/" rel="nofollow">codecentric</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Brian Diesenhaus</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Brian Guan</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Brian D. Johnson</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Brian Madigan</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Bryan Schmidt</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Chris Kingsbury</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.tradingscreen.com" rel="nofollow">TradingScreen</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Christopher G. Stach II</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Charles Anthony</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Charles Moulliard</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.xpectis.com" rel="nofollow">Xpectis</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Claus Ibsen</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Dennis Byrne</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.thoughtworks.com" rel="nofollow">Thoughtworks</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Erik Onnen</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Gert Vanthienen</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Glen Klyuzner</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.tullib.com" rel="nofollow">Tullib</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Hakan Guleryuz</td><td colspan="1" rowspan="1" class="confluenceTd">ASPone</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jakub Korab</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://ameliant.com" rel="nofollow">Ameliant</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">James Chamberlain</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">James Zhang</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jamie McCrindle</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jason Anderson</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jason Carreira</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jason Sherman</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jérôme Delagnes</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jeff Sparkes</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jeff Lansing</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.systechnologies.com/" rel="nofollow">SYS Technologies</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Jeremy Volkman</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Joe Fernandez</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.redhat.com/en/technologies/jboss-middleware/amq" rel="nofollow">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">John Heitmann</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Juraj Tomasov</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Kevin Ross</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Leo Pechersky</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Li Ma</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Marco Buss</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.productandconcept.com/" rel="nofollow">product + concept</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Marco Luebcke</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Mark Bucayan</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Mark Frazier</td><td colspan="1" rowspan="1" class="confluenceTd">Savoir Technologies</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Mark Timmings</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Mario Siegenthaler</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Martin Krasser</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Mats Henricson</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Matt Hoffman</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Matthew Vincent</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Mathew Kuppe</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.360t.com/" rel="nofollow">360 Treasury Systems</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Mike Perham</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Neil Clayton</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.rbs.co.uk/CBFM" rel="nofollow">Royal Bank of Scotland</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Neil Thorne</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Nick Reid</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.evolution.net" rel="nofollow">Evolution</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Niklas Gustavsson</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ning Li</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Noah Nordrum</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Oliver Belikan</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ozgur Cetinturk</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Paul Smith</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Paul Wai</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Pawel Tucholski</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Peter Henning</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Przemyslaw Budzik</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Radek Sedmak</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Robin Roos</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.drkw.com/" rel="nofollow">Dresdner Kleinwort Wasserstein</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.oreillynet.com/pub/au/3212" rel="nofollow">Robert Liguori</a></td><td colspan="1" rowspan="1" class="confluenceTd">STG Technologies, Inc.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ross Mason</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Sami Dalouche</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Sanjiv Jivan</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Steven Marcus</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Taylor Gautier</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Thomas Heller</td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.trevorpounds.com" rel="nofollow">Trevor Pounds</a></td><td colspan="1" rowspan="1" class="confluenceTd"> </td></tr></tbody></table></div><h3 id="Team-Contributing">Contributing</h3><p>We welcome contributions, please do come and <a shape="rect" class="external-link" href="http://activemq.apache.org/contributing.html">join the fun</a>.</p></div>
+<div class="wiki-content maincontent"><h1>ActiveMQ Community</h1><p>This page lists who we are. By all means add yourself to the list - lets sort it in alphabetical order</p><h3>Committers</h3><p>"A committer is a developer that was given write access to the code repository and has a signed Contributor License Agreement (<a shape="rect" href="http://www.apache.org/licenses/icla.txt">CLA</a>) on file. They have an apache.org mail address. Not needing to depend on other people for the patches, they are actually making short-term decisions for the project. The PMC can (even tacitly) agree and approve it into permanency, or they can reject it. Remember that the PMC makes the decisions, not the individual people." – from <a shape="rect" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a></p><table><tbody><tr><th colspan="1" rowspan="1">Name</th><th colspan="1" rowspan="1">ID</th><th colspan="1" rowspan="1">Organisation</th></tr><tr><td colspan="1" rowspan="1">Aaron Mulder</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ammulder">ammulder</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://chariotsolutions.com">Chariot Solutions</a></td></tr><tr><td colspan="1" rowspan="1">Adrian Co</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aco">aco</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Alan D. Cabrera</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maguro">maguro</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Arthur Naseef</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=artnaseef">artnaseef</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.savoirtech.com/">Savoir Technologies</a></td></tr><tr><td colspan="1" rowspan="1">Brian McCallister</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brianm">brianm</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://ning.com">Ning</a></td></tr><tr><td colspan="1" rowspan="1">Bruce Snyder</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bsnyder">bsnyder </a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://springsource.com/">SpringSource</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://cmoulliard.blogspot.com">Charles Moulliard</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cmoulliard">cmoulliard</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a> <span> </span></td></tr><tr><td colspan="1" rowspan="1">Christopher Shannon</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cshannon">cshannon</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Christian Posta</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ceposta">ceposta</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://davsclaus.blogspot.com/">Claus Ibsen</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=davsclaus">davsclaus </a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">Colin MacNaughton</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cmacnaug">cmacnaug</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://www.nighttale.net">Dejan Bosanac</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dejanb">dejanb </a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">Dag Liodden</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=daggerrz">daggerrz </a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.giantleap.no">Giant Leap Technologies</a></td></tr><tr><td colspan="1" rowspan="1">Dain Sundstrom</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dain">dain </a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Darwin Flores</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dflores">dflores </a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">David Jencks</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=djencks">djencks </a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.ibm.com">IBM</a></td></tr><tr><td colspan="1" rowspan="1">Dennis Cook</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dcook">dcook</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://bevocal.com">BeVocal</a></td></tr><tr><td colspan="1" rowspan="1">Frederick Oconer</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=foconer">foconer </a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Gary Tully</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gtully">gtully</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">Geir Magnusson Jr.</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=geir">geir</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Greg Wilkins</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gregw">gregw</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://mortbay.com">MortBay</a></td></tr><tr><td colspan="1" rowspan="1">Guillaume Nodet</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gnodet">gnodet</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">Hadrian Zbarcea</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hadrian">hadrian</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.talend.com/">Talend</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://hiramchirino.com">Hiram Chirino</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=chirino">chirino</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://www.JacekLaskowski.pl">Jacek Laskowski</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jlaskowski">jlaskowski</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://macstrac.blogspot.com/">James Strachan</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jstrachan">jstrachan</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">Jason van Zyl</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jason">jason</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Jean-Baptiste Onofré</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jbonofre">jbonofre</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.talend.com/">Talend</a></td></tr><tr><td colspan="1" rowspan="1">Jeff Genender</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jgenender">jgenender</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.savoirtech.com/">Savoir Technologies</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="https://plus.google.com/113674252934234025601/posts">Jim Gomes</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jgomes">jgomes</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Joe Walnes</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=joe">joe</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.google.com">Google</a></td></tr><tr><td colspan="1" rowspan="1">Jonas Lim</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jlim">jlim</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://janstey.blogspot.com/">Jonathan Anstey</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=janstey">janstey</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">Joseph Gapuz</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jgapuz">jgapuz</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Matt Pavlovich</td><td colspan="1" rowspan="1">mattrpav</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.mediadriver.com">Media Driver</a></td></tr><tr><td colspan="1" rowspan="1">Max Kington</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mkington">mkington</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://betfair.com">BetFair</a></td></tr><tr><td colspan="1" rowspan="1">Merwin Yap</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=myap">myap</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://www.gaffneyware.com/">Michael Gaffney</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mgaffney">mgaffney</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.boxtone.com">BoxTone</a></td></tr><tr><td colspan="1" rowspan="1">Nathan Mittler</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nmittler">nmittler</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Nicky Sandhu</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nsandhu">nsandhu</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Patrick Villacorta</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pvillacorta">pvillacorta</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Peter Brooke</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pbrooke">pbrooke</a></td><td colspan="1" rowspan="1">Prepulse</td></tr><tr><td colspan="1" rowspan="1">Ramzi Saba</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rsaba">rsaba</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.optaros.com">Optaros</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://rajdavies.blogspot.com/">Rob Davies</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rajdavies">rajdavies</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">Roman Kalukiewicz</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=romkal">romkal</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Tatu Saloranta</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowtowncoder">cowtowncoder</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://timbish.blogspot.com/">Timothy Bish</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tabish">tabish</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://willemjiang.blogspot.com/">Willem Jiang</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ningjiang">ningjiang</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/products/jbossenterprisemiddleware/fuse/">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">William Tam</td><td colspan="1" rowspan="1"><a shape="rect" href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wtam">wtam</a></td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Marc Schöchlin</td><td colspan="1" rowspan="1">mschoechlin</td><td colspan="1" rowspan="1"> </td></tr></tbody></table><h3>Contributors</h3><p>"A developer is a user who contributes to a project in the form of code or documentation. They take extra steps to participate in a project, are active on the developer mailing list, participate in discussions, provide patches, documentation, suggestions, and criticism. Developers are also known as contributors." – from <a shape="rect" href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a></p><table><tbody><tr><th colspan="1" rowspan="1">Name</th><th colspan="1" rowspan="1">Organisation</th></tr><tr><td colspan="1" rowspan="1">Aaron Crickenberger</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Al Maw</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Aleksi Kallio</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://www.deanspot.org/blog/alex">Alex Dean</a></td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.meteostar.com">IPS Meteostar</a></td></tr><tr><td colspan="1" rowspan="1">Andrew Deason</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Andy Depue</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Axel Hohaus</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Arjan Moraal</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Barry Kaplan</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="https://twitter.com/bennetelli">Bennet Schulz</a></td><td colspan="1" rowspan="1"><a shape="rect" href="https://www.codecentric.de/">codecentric</a></td></tr><tr><td colspan="1" rowspan="1">Brian Diesenhaus</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Brian Guan</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Brian D. Johnson</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Brian Madigan</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Bryan Schmidt</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Chris Kingsbury</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.tradingscreen.com">TradingScreen</a></td></tr><tr><td colspan="1" rowspan="1">Christopher G. Stach II</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Charles Anthony</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Charles Moulliard</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.xpectis.com">Xpectis</a></td></tr><tr><td colspan="1" rowspan="1">Claus Ibsen</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Dennis Byrne</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.thoughtworks.com">Thoughtworks</a></td></tr><tr><td colspan="1" rowspan="1">Erik Onnen</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Gert Vanthienen</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Glen Klyuzner</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.tullib.com">Tullib</a></td></tr><tr><td colspan="1" rowspan="1">Hakan Guleryuz</td><td colspan="1" rowspan="1">ASPone</td></tr><tr><td colspan="1" rowspan="1">Jakub Korab</td><td colspan="1" rowspan="1"><a shape="rect" href="http://ameliant.com">Ameliant</a></td></tr><tr><td colspan="1" rowspan="1">James Chamberlain</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">James Zhang</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Jamie McCrindle</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Jason Anderson</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Jason Carreira</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Jason Sherman</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Jérôme Delagnes</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Jeff Sparkes</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Jeff Lansing</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.systechnologies.com/">SYS Technologies</a></td></tr><tr><td colspan="1" rowspan="1">Jeremy Volkman</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Joe Fernandez</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.redhat.com/en/technologies/jboss-middleware/amq">Red Hat</a></td></tr><tr><td colspan="1" rowspan="1">John Heitmann</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Juraj Tomasov</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Kevin Ross</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Leo Pechersky</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Li Ma</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Marco Buss</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.productandconcept.com/">product + concept</a></td></tr><tr><td colspan="1" rowspan="1">Marco Luebcke</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Mark Bucayan</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Mark Frazier</td><td colspan="1" rowspan="1">Savoir Technologies</td></tr><tr><td colspan="1" rowspan="1">Mark Timmings</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Mario Siegenthaler</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Martin Krasser</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Mats Henricson</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Matt Hoffman</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Matthew Vincent</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Mathew Kuppe</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.360t.com/">360 Treasury Systems</a></td></tr><tr><td colspan="1" rowspan="1">Mike Perham</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Neil Clayton</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.rbs.co.uk/CBFM">Royal Bank of Scotland</a></td></tr><tr><td colspan="1" rowspan="1">Neil Thorne</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Nick Reid</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.evolution.net">Evolution</a></td></tr><tr><td colspan="1" rowspan="1">Niklas Gustavsson</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Ning Li</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Noah Nordrum</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Oliver Belikan</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Ozgur Cetinturk</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Paul Smith</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Paul Wai</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Pawel Tucholski</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Peter Henning</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Przemyslaw Budzik</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Radek Sedmak</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Robin Roos</td><td colspan="1" rowspan="1"><a shape="rect" href="http://www.drkw.com/">Dresdner Kleinwort Wasserstein</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://www.oreillynet.com/pub/au/3212">Robert Liguori</a></td><td colspan="1" rowspan="1">STG Technologies, Inc.</td></tr><tr><td colspan="1" rowspan="1">Ross Mason</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Sami Dalouche</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Sanjiv Jivan</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Steven Marcus</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Taylor Gautier</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1">Thomas Heller</td><td colspan="1" rowspan="1"> </td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://www.trevorpounds.com">Trevor Pounds</a></td><td colspan="1" rowspan="1"> </td></tr></tbody></table><h3>Contributing</h3><p>We welcome contributions, please do come and <a shape="rect" href="http://activemq.apache.org/contributing.html">join the fun</a>.</p></div>
diff --git a/terminology.xml b/terminology.xml
index d48617e..176c5a5 100644
--- a/terminology.xml
+++ b/terminology.xml
@@ -1,60 +1,61 @@
<div class="wiki-content maincontent"><p>Questions on Message Orientated Middleware and ActiveMQ terminology</p>
-<ul class="childpages-macro"><li><a shape="rect" href="dr.xml">DR</a></li><li><a shape="rect" href="ha.xml">HA</a></li><li><a shape="rect" href="latency.xml">Latency</a></li><li><a shape="rect" href="mom.xml">MOM</a></li><li><a shape="rect" href="qos.xml">QoS</a></li><li><a shape="rect" href="seda.xml">SEDA</a></li><li><a shape="rect" href="throughput.xml">Throughput</a></li></ul>
+<structured-macro ac:macro-id="fab5b887-ca1f-4717-8fbc-963ce57c14f9" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro>
-<h3 id="Terminology-StoreandForward">Store and Forward</h3>
+<h3>Store and Forward</h3>
<p>brokers receive messages, store them locally and forwards the message to a recipient (in this case another broker) when it is able to do so. The message is only deleted once its been sucessfully delivered.</p>
-<h3 id="Terminology-Reliablemessaging">Reliable messaging</h3>
+<h3>Reliable messaging</h3>
<p>Best efforts are made to deliver a message whilst the system (broker/cluster/network) is running.</p>
-<h3 id="Terminology-Guaranteed">Guaranteed</h3>
+<h3>Guaranteed</h3>
<p>No matter what happens to the physical network connections or the destination service the message will be delivered to the receiptant - provided there is no catastraphic loss to the persistent data store of a broker along the message(s) route. This means a message could be lost if there was a catastrophic failure to a broker's activemq data disk.</p>
-<h3 id="Terminology-FaultTolerance">Fault Tolerance</h3>
+<h3>Fault Tolerance</h3>
<p>Unexpected failures never lead to lost or corrupted data - for a messaging system - there are additional caveats for corrupted data - message ordering and once and only once message delivery.</p>
-<h3 id="Terminology-NetworkOrphan">Network Orphan</h3>
+<h3>Network Orphan</h3>
<p>A broker can become isolated from other brokers in the cluster due to an network outage. The broker and it's connected clients may not be able to detect if the loss of other brokers in the cluster is due to the broker(or their machines) or simply a router/cable problem. This is a big issue for clustering, as it has the potential to create corrupted data exchanges when the network is re-established.</p>
-<h3 id="Terminology-Clustering">Clustering</h3>
+<h3>Clustering</h3>
<p>multiple brokers are used to provide a single logical service. <br clear="none">
There are three reasons for using clustering:</p>
-<h5 id="Terminology-Increasedcapacity">Increased capacity</h5>
+<h5>Increased capacity</h5>
<p>This is load balancing - this is currently achived by networking brokers together - this won't change in ActiveMQ 4.0 (see below).</p>
-<h5 id="Terminology-GeographicalDistribution">Geographical Distribution</h5>
+<h5>Geographical Distribution</h5>
<p>Again this is achived in ActiveMQ by broker networks.</p>
-<h5 id="Terminology-HighAvailability">High Availability</h5>
+<h5>High Availability</h5>
<p>The guarenteed maximum amount of downtime that will not be exceeded:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Uptime</p></th><td colspan="1" rowspan="1" class="confluenceTd"><p> Average Down time </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> implications </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>95% </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 8 hours a week </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> System will be offline for nightly backups a broker loss could result in loss of all messages since last back-up</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>99%</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1.5 hours a week</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> system maybe offline for backup or maintenance</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>99.9%</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 40 mins/month</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> all back-ups done online</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>99.999% </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 5 mins/year</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> full redundancy</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Uptime</p></th><td colspan="1" rowspan="1"><p> Average Down time </p></td><td colspan="1" rowspan="1"><p> implications </p></td></tr><tr><td colspan="1" rowspan="1"><p>95% </p></td><td colspan="1" rowspan="1"><p> 8 hours a week </p></td><td colspan="1" rowspan="1"><p> System will be offline for nightly backups a broker loss could result in loss of all messages since last back-up</p></td></tr><tr><td colspan="1" rowspan="1"><p>99%</p></td><td colspan="1" rowspan="1"><p> 1.5 hours a week</p></td><td colspan="1" rowspan="1"><p> system maybe offline for backup or maintenance</p></td></tr><tr><td colspan="1" rowspan="1"><p>99.9%</p></td><td colspan="1" rowspan="1"><p> 40 mins/month</p></td><td colspan="1" rowspan="1"><p> all back-ups done online</p></td></tr><tr><td colspan="1" rowspan="1"><p>99.999% </p></td><td colspan="1" rowspan="1"><p> 5 mins/year</p></td><td colspan="1" rowspan="1"><p> full redundancy</p></td></tr></tbody></table>
-<h5 id="Terminology-Architecturebasics">Architecture basics</h5>
+<h5>Architecture basics</h5>
<p>Clusters can be either based around shared storage (shared database or disk) or shared nothing (every broker has their own private storage). There is also two basic mechanisms used for message integrity for failure scenarios:</p>
-<h6 id="Terminology-Master/Slave">Master/Slave</h6>
+<h6>Master/Slave</h6>
<p>A broker has a standby replacement - another broker that is kept in step by the cluster that will take over in the event of a broker failure.</p>
-<h6 id="Terminology-Synchronous">Synchronous</h6>
+<h6>Synchronous</h6>
<p>Every broker is kept exactly in-step with message exchanges across the entire cluster. This is the most secure for failure scenrios, but suffers from performance problems because it the responsibility of the cluster to ensure that messages are fully replicated across every node. This results in higher latency and increased traffic. In practice, it is unsual to have more than 2 brokers in such a cluster, because the performance degradation is directly related to the number of brokers in the cluster.</p>
-<h6 id="Terminology-Hybrid">Hybrid</h6>
+<h6>Hybrid</h6>
<p>A fully synchronous cluster, but it is the responsibility of the client (not the brokers) to ensure every broker is kept up to date. This has advantages for performance, but is complicated by the additional exchange between client and broker(s) to ensure that only one broker does the message dispatching for a client.</p>
+
</div>
diff --git a/test-source-xref.xml b/test-source-xref.xml
index f3d517e..94254ee 100644
--- a/test-source-xref.xml
+++ b/test-source-xref.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent">
-<p><a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/activemq-ra/xref-test/" rel="nofollow">ActiveMQ Resource Adapter</a><br clear="none">
-<a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/activemq-web/xref-test/" rel="nofollow">ActiveMQ Web</a></p></div>
+<p><a shape="rect" href="http://activemq.codehaus.org/maven/activemq-ra/xref-test/">ActiveMQ Resource Adapter</a><br clear="none">
+<a shape="rect" href="http://activemq.codehaus.org/maven/activemq-web/xref-test/">ActiveMQ Web</a></p></div>
diff --git a/thanks.xml b/thanks.xml
index 7431cd6..88b1a64 100644
--- a/thanks.xml
+++ b/thanks.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ is a successful project because of the large and diverse community that contributes to it. </p><p>There are a handful of tools that developers in the community use; some are open-source and some are commercial. We'd like to extend a special thanks to these communities/companies:</p><p> </p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-external-resource" src="http://www.apache.org/images/feather-small.gif" data-image-src="http://www.apache.org/images/feather-small.gif"></span></td><td colspan="1" rowspan="1" class="confluenceTd">All of the <a shape="rect" class="external-link" href="http://www.apache.org/foundation/thanks.html">Platinum/Gold/Silver/Bronze sponsors of the ASF</a></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.yourkit.com/java/profiler/index.jsp" rel="nofollow"><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="thanks.data/yklogo.png" data-image-src="/confluence/download/attachments/44994563/yklogo.png?version=1&modificationDate=1407981111000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="45383758" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="yklogo.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="44994563" data-linked-resource-container-version="1"></span></a></td><td colspan="1" rowspan="1" class="confluenceTd"><span style="color: rgb(34,34,34);">YourKit supports ActiveMQ project with its full-featured Java Profiler.</span><br clear="none"><span style="color: rgb(34,34,34);">YourKit, LLC is the creator of innovative and intelligent tools for profiling</span><br clear="none"><span style="color: rgb(34,34,34);">Java and .NET applications. <a shape="rect" class="external-link" href="http://www.yourkit.com/java/profiler/index.jsp" rel="nofollow">Take a look at YourKit's leading software products</a></span></td></tr></tbody></table></div></div>
+<div class="wiki-content maincontent"><p>ActiveMQ is a successful project because of the large and diverse community that contributes to it. </p><p>There are a handful of tools that developers in the community use; some are open-source and some are commercial. We'd like to extend a special thanks to these communities/companies:</p><p> </p><table><tbody><tr><td colspan="1" rowspan="1"><image><url ri:value="http://www.apache.org/images/feather-small.gif"></url></image></td><td colspan="1" rowspan="1">All of the <a shape="rect" href="http://www.apache.org/foundation/thanks.html">Platinum/Gold/Silver/Bronze sponsors of the ASF</a></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://www.yourkit.com/java/profiler/index.jsp"><image><attachment ri:filename="yklogo.png"></attachment></image></a></td><td colspan="1" rowspan="1"><span style="color: rgb(34,34,34);">YourKit supports ActiveMQ project with its full-featured Java Profiler.</span><br clear="none"><span style="color: rgb(34,34,34);">YourKit, LLC is the creator of innovative and intelligent tools for profiling</span><br clear="none"><span style="color: rgb(34,34,34);">Java and .NET applications. <a shape="rect" href="http://www.yourkit.com/java/profiler/index.jsp">Take a look at YourKit's leading software products</a></span></td></tr></tbody></table></div>
diff --git a/the-activeblaze-message-type.xml b/the-activeblaze-message-type.xml
index da3deca..954c296 100644
--- a/the-activeblaze-message-type.xml
+++ b/the-activeblaze-message-type.xml
@@ -7,29 +7,26 @@
<p>You can create a BlazeMessage by its default constructor - e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="a611d08e-785c-4bdb-861c-cfa37d3c08c8" ac:name="code" ac:schema-version="1"><plain-text-body>
import org.apache.activeblaze.*;
...
BlazeMessage msg = new BlazeMessage();
- msg.setFloatValue("rate",0.94f);
+ msg.setFloatValue("rate",0.94f);
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>There's a few utility methods to support passing around standard objects - e.g.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="94118c88-1bcb-4e3e-bdfc-e352b945c4ea" ac:name="code" ac:schema-version="1"><plain-text-body>
import org.apache.activeblaze.*;
...
- BlazeMessage msg = new BlazeMessage("test string");
+ BlazeMessage msg = new BlazeMessage("test string");
String text = msg.getText();
BlazeMessage msg = new BlazeMessage();
- msg.setText("test string");
+ msg.setText("test string");
String text = msg.getText();
...
@@ -39,7 +36,7 @@
byte[] result = msg.getBytes();
BlazeMessage msg = new BlazeMessage();
- msg.setBytes("data);
+ msg.setBytes("data);
byte[] result = msg.getData();
...
@@ -53,6 +50,5 @@
Object result = msg.getObject();
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></div>
diff --git a/the-broker-will-not-start.xml b/the-broker-will-not-start.xml
index eeb1c37..5a353a2 100644
--- a/the-broker-will-not-start.xml
+++ b/the-broker-will-not-start.xml
@@ -1,10 +1,8 @@
<div class="wiki-content maincontent"><p>It's been reported that during broker start some users get a message similar to:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="8c4d3eee-4425-40ed-b43d-07a41ece98b6" ac:name="code" ac:schema-version="1"><plain-text-body>
15:26:29 INFO Opening journal. Caught: javax.jms.JMSException: Failed to open transaction journal: java.io.IOException: Invalid argument
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>It could be <a shape="rect" href="journal-is-already-opened-by-this-application.xml">this problem</a> or the problem could be due to a bad os/jvm combination. See <a shape="rect" href="known-bad-os-and-jvm-combinations.xml">Known Bad OS and JVM Combinations</a></p></div>
+<p>It could be <link><page ri:content-title="Journal is already opened by this application"></page><link-body>this problem</link-body></link> or the problem could be due to a bad os/jvm combination. See <link><page ri:content-title="Known Bad OS and JVM Combinations"></page></link></p></div>
diff --git a/the-jms-connector.xml b/the-jms-connector.xml
index 49ffe93..5103f00 100644
--- a/the-jms-connector.xml
+++ b/the-jms-connector.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><span class="error">The license could not be verified: License Certificate has expired!</span></p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="92195bfd-c7b0-476f-827e-82b8187bd0b0" ac:name="redirect" ac:schema-version="1"><parameter ac:name="location"><link><page ri:content-title="JMS to JMS Bridge"></page></link></parameter></structured-macro></p></div>
diff --git a/the-proxy-connector.xml b/the-proxy-connector.xml
index 0f68421..4f8f3de 100644
--- a/the-proxy-connector.xml
+++ b/the-proxy-connector.xml
@@ -1,32 +1,31 @@
<div class="wiki-content maincontent">
-<h2 id="TheProxyConnector-TheProxyConnector">The Proxy Connector</h2>
+<h2>The Proxy Connector</h2>
<p>Many of the more advanced ActiveMQ features are implemented in the transports. Sometimes it's desirable to accept one kind of ActiveMQ connection and establish a different kind of connection to another broker. The Proxy Connector allows you to do that by accepting connection on one transport and establishing new connections using a different transport and then just proxying all the commands sent between the two transports.</p>
-<h3 id="TheProxyConnector-ExampleConfiguration">Example Configuration</h3>
+<h3>Example Configuration</h3>
<p>If you wanted to accept normal connection on port 6001, but also wanted to expose port 6002 which in turn was proxied using the fanout transport, the following example is shows you how to do it!</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<beans xmlns="http://activemq.org/config/1.0">
+<structured-macro ac:macro-id="03fd265f-6bdf-41bf-b7ed-e0d9b658354d" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<beans xmlns="http://activemq.org/config/1.0">
<broker>
<persistenceAdapter>
- <journaledJDBC dataDirectory="../data"/>
+ <journaledJDBC dataDirectory="../data"/>
</persistenceAdapter>
<transportConnectors>
- <transportConnector uri="tcp://localhost:6001"/>
+ <transportConnector uri="tcp://localhost:6001"/>
</transportConnectors>
<proxyConnectors>
- <proxyConnector bind="tcp://localhost:6002" remote="fanout:static:(tcp://localhost:61616)"/>
+ <proxyConnector bind="tcp://localhost:6002" remote="fanout:static:(tcp://localhost:61616)"/>
</proxyConnectors>
</broker>
</beans>
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro>
+</div>
diff --git a/the-vm-transport-starts-a-broker-before-my-configured-broker-starts.xml b/the-vm-transport-starts-a-broker-before-my-configured-broker-starts.xml
index a52c9b3..da2268b 100644
--- a/the-vm-transport-starts-a-broker-before-my-configured-broker-starts.xml
+++ b/the-vm-transport-starts-a-broker-before-my-configured-broker-starts.xml
@@ -1,16 +1,17 @@
-<div class="wiki-content maincontent"><h3 id="Thevmtransportstartsabrokerbeforemyconfiguredbrokerstarts-Scenario">Scenario</h3>
+<div class="wiki-content maincontent"><h3>Scenario</h3>
<p>You are using the <strong>vm:</strong> transport and a broker is auto-started for you so that your configured embedded broker doesn't start.</p>
-<h3 id="Thevmtransportstartsabrokerbeforemyconfiguredbrokerstarts-Solution">Solution</h3>
+<h3>Solution</h3>
<p>Its most likely a dependency issue; your JMS connection is starting before your embedded broker. So just make sure your embedded broker is started first.</p>
-<p>Another cause could be that your use of the <a shape="rect" href="vm-transport-reference.xml">VM Transport</a> defines a broker name of localhost whereas your embedded broker uses a different name; so just be consistent in the naming.</p>
+<p>Another cause could be that your use of the <link><page ri:content-title="VM Transport Reference"></page><link-body>VM Transport</link-body></link> defines a broker name of localhost whereas your embedded broker uses a different name; so just be consistent in the naming.</p>
<p>ActiveMQ 5.2 adds the waitForStart='timeout in milliseconds' option to the VM transport which forces the VM transport to wait till the broker is started. Coupled with the "create=false" option, it is possible to ensure that a single embedded broker is auto-started.</p>
-<h3 id="Thevmtransportstartsabrokerbeforemyconfiguredbrokerstarts-Seealso">See also</h3>
+<h3>See also</h3>
-<ul><li><a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a></li></ul></div>
+<ul><li><link><page ri:content-title="VM Transport Reference"></page></link></li></ul>
+</div>
diff --git a/throughput.xml b/throughput.xml
index de9d4db..3a0df53 100644
--- a/throughput.xml
+++ b/throughput.xml
@@ -3,5 +3,5 @@
<p>How many messages can we process per second. </p>
-<p>Normally <a shape="rect" href="mom.xml">MOM</a> style applications focus on asynchronous messaging and <a shape="rect" href="seda.xml">SEDA</a> style architectures which aim for massive throughput numbers at the cost of some <a shape="rect" href="latency.xml">Latency</a></p></div>
+<p>Normally <link><page ri:content-title="MOM"></page></link> style applications focus on asynchronous messaging and <link><page ri:content-title="SEDA"></page></link> style architectures which aim for massive throughput numbers at the cost of some <link><page ri:content-title="Latency"></page></link></p></div>
diff --git a/timestampplugin.xml b/timestampplugin.xml
index 66483ce..30cb192 100644
--- a/timestampplugin.xml
+++ b/timestampplugin.xml
@@ -1,8 +1,6 @@
-<div class="wiki-content maincontent"><p>The TimeStampPlugin is a Broker interceptor which updates a JMS Client's time stamp on the message with a broker time stamp. This can be useful when the clocks on client machines are known to not be correct and you can only trust the time set on the broker machines.</p><p>Enabling this plugin will break JMS compliance since the time stamp that the producer sees on the messages after as <strong><code>send()</code></strong> will be different from the time stamp the consumer will observe when he receives the message.</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">By default this plugin is <em>not</em> enabled in ActiveMQ.</div></div><h4 id="TimeStampPlugin-Options">Options</h4><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p><strong>Attribute</strong></p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><strong>Default Value</strong></p></th><th colspan="1" rowspan="1" class="confluenceTh"><p><strong>Description</strong></p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>futureOnly</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>false</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When <strong><code>true</code></strong> the plugin will <em>never</em> set a message's time stamp and expiration time to a value lower than the original values.</p><p>When <strong><code>false</code></strong> the plugin <em>always</em> update a message's time stamp and expiration time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>ttlCeiling</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When not zero, this value (in ms) limit the expiration time.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>zeroExpirationOverride</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>0</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When not zero this value (in ms) will override the expiration time for messages that do not have an expiration already set.</p></td></tr></tbody></table></div><p>To enable the TimeStampPlugin add the following to your ActiveMQ Broker configuration.</p><p>Example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: xml; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<plugins>
+<div class="wiki-content maincontent"><p>The TimeStampPlugin is a Broker interceptor which updates a JMS Client's time stamp on the message with a broker time stamp. This can be useful when the clocks on client machines are known to not be correct and you can only trust the time set on the broker machines.</p><p>Enabling this plugin will break JMS compliance since the time stamp that the producer sees on the messages after as <strong><code>send()</code></strong> will be different from the time stamp the consumer will observe when he receives the message.</p><structured-macro ac:macro-id="d8a6fa35-c580-419b-889d-e4ace8a7a0f0" ac:name="info" ac:schema-version="1"><rich-text-body>By default this plugin is <em>not</em> enabled in ActiveMQ.</rich-text-body></structured-macro><h4>Options</h4><table><tbody><tr><th colspan="1" rowspan="1"><p><strong>Attribute</strong></p></th><th colspan="1" rowspan="1"><p><strong>Default Value</strong></p></th><th colspan="1" rowspan="1"><p><strong>Description</strong></p></th></tr><tr><td colspan="1" rowspan="1"><p><code>futureOnly</code></p></td><td colspan="1" rowspan="1"><p><code>false</code></p></td><td colspan="1" rowspan="1"><p>When <strong><code>true</code></strong> the plugin will <em>never</em> set a message's time stamp and expiration time to a value lower than the original values.</p><p>When <strong><code>false</code></strong> the plugin <em>always</em> update a message's time stamp and expiration time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>ttlCeiling</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>When not zero, this value (in ms) limit the expiration time.</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>zeroExpirationOverride</code></p></td><td colspan="1" rowspan="1"><p><code>0</code></p></td><td colspan="1" rowspan="1"><p>When not zero this value (in ms) will override the expiration time for messages that do not have an expiration already set.</p></td></tr></tbody></table><p>To enable the TimeStampPlugin add the following to your ActiveMQ Broker configuration.</p><p>Example:</p><structured-macro ac:macro-id="4aed805d-2fd7-4445-ac97-02362c11d191" ac:name="code" ac:schema-version="1"><parameter ac:name="language">xml</parameter><plain-text-body><plugins>
<!-- 86,400,000 ms = 1 day -->
- <timeStampingBrokerPlugin ttlCeiling="86400000" zeroExpirationOverride="86400000"/>
+ <timeStampingBrokerPlugin ttlCeiling="86400000" zeroExpirationOverride="86400000"/>
</plugins>
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title"> Broker/Consumer Clock Synchronization</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When the consumer’s local clock is running ahead of the broker’s local clock then messages might not be consumed by your consumer when this plug-in is loaded with default configuration as the consumer could perceive the messages as already expired.</p><p>If the clock difference between broker and consumer is <em>greater than</em> the message expiration time <em>and</em> if the consumer’s clock is running ahead, then set <strong><code>futureOnly="true"</code></strong>.</p><p>See the following <a shape="rect" class="external-link" href="http://tmielke.blogspot.com/2011/01/sync-your-machine-clocks.html" rel="nofollow">blog post</a> for more details.</p></div></div></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="6828683a-39ac-4239-9d55-d851e3fbcfa0" ac:name="info" ac:schema-version="1"><parameter ac:name="title"> Broker/Consumer Clock Synchronization</parameter><rich-text-body><p>When the consumer’s local clock is running ahead of the broker’s local clock then messages might not be consumed by your consumer when this plug-in is loaded with default configuration as the consumer could perceive the messages as already expired.</p><p>If the clock difference between broker and consumer is <em>greater than</em> the message expiration time <em>and</em> if the consumer’s clock is running ahead, then set <strong><code>futureOnly="true"</code></strong>.</p><p>See the following <a shape="rect" href="http://tmielke.blogspot.com/2011/01/sync-your-machine-clocks.html">blog post</a> for more details.</p></rich-text-body></structured-macro></div>
diff --git a/tips-for-getting-help.xml b/tips-for-getting-help.xml
index a1951ab..54bdbe2 100644
--- a/tips-for-getting-help.xml
+++ b/tips-for-getting-help.xml
@@ -1,8 +1,9 @@
-<div class="wiki-content maincontent"><p>We are a community based open source project and we really welcome and value your <a shape="rect" href="contributing.xml">Contributions</a>. We have various ways of getting help via the <a shape="rect" href="discussion-forums.xml">Discussion Forums</a> or <a shape="rect" href="mailing-lists.xml">Mailing Lists</a>. </p>
+<div class="wiki-content maincontent"><p>We are a community based open source project and we really welcome and value your <link><page ri:content-title="Contributing"></page><link-body>Contributions</link-body></link>. We have various ways of getting help via the <link><page ri:content-title="Discussion Forums"></page></link> or <link><page ri:content-title="Mailing Lists"></page></link>. </p>
<p>Here are a few tips to help us to help you</p>
<ul><li>which version of ActiveMQ are you using? (and if you are using a SNAPSHOT, which date?)</li><li>are you using queues or topics and are you using persistent or non persistent messaging?</li><li>details of your environment can help too such as
<ul><li>operating system</li><li>JVM version (1.6, 1.5, or 1.4)</li><li>application server; spring, tomcat, J2EE etc?</li></ul>
- </li><li>remember you can always get full <a shape="rect" href="support.xml#Support-CommercialSupport">commercial support</a> if you want a dedicated support team.</li></ul></div>
+ </li><li>remember you can always get full <link ac:anchor="Commercial Support"><page ri:content-title="Support"></page><link-body>commercial support</link-body></link> if you want a dedicated support team.</li></ul>
+</div>
diff --git a/tomcat.xml b/tomcat.xml
index e034549..2f768db 100644
--- a/tomcat.xml
+++ b/tomcat.xml
@@ -1,5 +1,4 @@
-<div class="wiki-content maincontent"><h4 id="Tomcat-ConfigurationissuesforTomcat7andlater">Configuration issues for Tomcat 7 and later</h4><div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Tomcat needs to be configured to ignore Jetty SCI annotations so that the Jetty WebSocket ServerContainerInitializer class is not inadvertently picked up by Tomcat. For more information on this problem see <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-6154">AMQ-6154</a> and <a shape="rect" class="external-link" href="https://wiki.apache.org/tomcat/HowTo/FasterStartUp">https://wiki.apache.org/tomcat/HowTo/FasterStartUp</a> and consult the Tomcat documentation for the version you are using to properly exclude the Jetty jar files from being scanned by Tomcat.</p></div></div><h2 id="Tomcat-Pre-integratedTomcatwithActiveMQ">Pre-integrated Tomcat with ActiveMQ</h2><p>Apache TomEE is a distribution of <a shape="rect" class="external-link" href="http://tomee.apache.org/tomcat-jms.html">Tomcat with fully integrated ActiveMQ</a>. All integration steps detailed here have already been done. The stack supports injection of Topic, Queue and ConnectionFactory references as well as transactional sending and delivery.</p><p>Something like the following works out of the box with no configuration:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[import javax.annotation.Resource;
+<div class="wiki-content maincontent"><h4>Configuration issues for Tomcat 7 and later</h4><structured-macro ac:macro-id="2d3a18bd-173c-4ea9-8852-7e57cded973c" ac:name="warning" ac:schema-version="1"><rich-text-body><p>Tomcat needs to be configured to ignore Jetty SCI annotations so that the Jetty WebSocket ServerContainerInitializer class is not inadvertently picked up by Tomcat. For more information on this problem see <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-6154">AMQ-6154</a> and <a shape="rect" href="https://wiki.apache.org/tomcat/HowTo/FasterStartUp">https://wiki.apache.org/tomcat/HowTo/FasterStartUp</a> and consult the Tomcat documentation for the version you are using to properly exclude the Jetty jar files from being scanned by Tomcat.</p></rich-text-body></structured-macro><h2>Pre-integrated Tomcat with ActiveMQ</h2><p>Apache TomEE is a distribution of <a shape="rect" href="http://tomee.apache.org/tomcat-jms.html">Tomcat with fully integrated ActiveMQ</a>. All integration steps detailed here have already been done. The stack supports injection of Topic, Queue and ConnectionFactory references as well as transactional sending and delivery.</p><p>Something like the following works out of the box with no configuration:</p><structured-macro ac:macro-id="24bb04f8-4aa8-41f0-9c8a-64f57792e4d0" ac:name="code" ac:schema-version="1"><plain-text-body>import javax.annotation.Resource;
import javax.servlet.http.HttpServlet;
import javax.jms.Topic;
import javax.jms.Queue;
@@ -7,21 +6,19 @@
public class MyServet extends HttpServlet {
- @Resource(name = "foo")
+ @Resource(name = "foo")
private Topic fooTopic;
- @Resource(name = "bar")
+ @Resource(name = "bar")
private Queue barQueue;
@Resource
private ConnectionFactory connectionFactory;
-]]></script>
-</div></div><h2 id="Tomcat-ManuallyintegratingTomcatandActiveMQ">Manually integrating Tomcat and ActiveMQ</h2><p>Note, manually integrating ActiveMQ with Tomcat does allow for Topic, Queue, and ConnectionFactory injection but does not support transactional sending and delivery.</p><p>You should go to Tomcat documentation and read JNDI Resources HOW-TO, especially part: Configure Tomcat's Resource Factory.</p><p>ActiveMQ has ready JNDI resource factory for all its administered objects: ConnectionFactory and destinations.</p><p>You must provide it as a parameter factory for your resources:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<Context ...>
+</plain-text-body></structured-macro><h2>Manually integrating Tomcat and ActiveMQ</h2><p>Note, manually integrating ActiveMQ with Tomcat does allow for Topic, Queue, and ConnectionFactory injection but does not support transactional sending and delivery.</p><p>You should go to Tomcat documentation and read JNDI Resources HOW-TO, especially part: Configure Tomcat's Resource Factory.</p><p>ActiveMQ has ready JNDI resource factory for all its administered objects: ConnectionFactory and destinations.</p><p>You must provide it as a parameter factory for your resources:</p><structured-macro ac:macro-id="5e448eca-234d-4151-b605-c11188458cf1" ac:name="code" ac:schema-version="1"><plain-text-body><Context ...>
...
- <Resource name="jms/ConnectionFactory" auth="Container"
- type="org.apache.activemq.ActiveMQConnectionFactory"/>
- <ResourceParams name="jms/ConnectionFactory">
+ <Resource name="jms/ConnectionFactory" auth="Container"
+ type="org.apache.activemq.ActiveMQConnectionFactory"/>
+ <ResourceParams name="jms/ConnectionFactory">
<parameter>
<name>factory</name>
<value>org.activemq.jndi.JNDIReferenceFactory</value>
@@ -41,29 +38,22 @@
</ResourceParams>
...
</Context>
-]]></script>
-</div></div><p> </p><p>If you are using Tomcat 5.5 or later then try this instead...</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<Context>
+</plain-text-body></structured-macro><p> </p><p>If you are using Tomcat 5.5 or later then try this instead...</p><structured-macro ac:macro-id="00c87efb-6eec-496e-a4af-d3a070c87f72" ac:name="code" ac:schema-version="1"><plain-text-body><Context>
...
- <Resource name="jms/ConnectionFactory" auth="Container" type="org.apache.activemq.ActiveMQConnectionFactory" description="JMS Connection Factory"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory" brokerURL="vm://localhost" brokerName="LocalActiveMQBroker"/>
+ <Resource name="jms/ConnectionFactory" auth="Container" type="org.apache.activemq.ActiveMQConnectionFactory" description="JMS Connection Factory"
+ factory="org.apache.activemq.jndi.JNDIReferenceFactory" brokerURL="vm://localhost" brokerName="LocalActiveMQBroker"/>
....
</Context>
-]]></script>
-</div></div><p> </p><p>Also, don't forget to put ActiveMQ and dependent jars to tomcat shared lib directory.</p><h3 id="Tomcat-CreatingdestinationsinTomcat5.5orlater">Creating destinations in Tomcat 5.5 or later</h3><p>This is completely untested but should work <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<Context>
+</plain-text-body></structured-macro><p> </p><p>Also, don't forget to put ActiveMQ and dependent jars to tomcat shared lib directory.</p><h3>Creating destinations in Tomcat 5.5 or later</h3><p>This is completely untested but should work <emoticon ac:name="smile"></emoticon></p><structured-macro ac:macro-id="22a959cc-c88b-4377-8d5b-e6f308eb1deb" ac:name="code" ac:schema-version="1"><plain-text-body><Context>
...
- <Resource name="jms/someTopic" auth="Container" type="org.apache.activemq.command.ActiveMQTopic" description="my Topic"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="FOO.BAR"/>
+ <Resource name="jms/someTopic" auth="Container" type="org.apache.activemq.command.ActiveMQTopic" description="my Topic"
+ factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="FOO.BAR"/>
- <Resource name="jms/aQueue" auth="Container" type="org.apache.activemq.command.ActiveMQQueue" description="my Queue"
- factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="FOO.BAR"/>
+ <Resource name="jms/aQueue" auth="Container" type="org.apache.activemq.command.ActiveMQQueue" description="my Queue"
+ factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="FOO.BAR"/>
....
</Context>
-]]></script>
-</div></div><div class="confluence-information-macro confluence-information-macro-information"><p class="title">JMX Tip when working with Tomcat</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you want to use JMX with Tomcat and then connect via JConsole to view the <a shape="rect" href="jmx.xml">JMX</a> MBeans of the server then set the following</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 \
- -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
-]]></script>
-</div></div></div></div></div>
+</plain-text-body></structured-macro><structured-macro ac:macro-id="73b03045-8f8e-45c9-b824-5aa7e922affb" ac:name="info" ac:schema-version="1"><parameter ac:name="title">JMX Tip when working with Tomcat</parameter><rich-text-body><p>If you want to use JMX with Tomcat and then connect via JConsole to view the <link><page ri:content-title="JMX"></page></link> MBeans of the server then set the following</p><structured-macro ac:macro-id="6fdc53cc-6f94-41e2-8539-04ffa0128942" ac:name="code" ac:schema-version="1"><plain-text-body>CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 \
+ -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
+</plain-text-body></structured-macro></rich-text-body></structured-macro></div>
diff --git a/tomee.xml b/tomee.xml
index c373fb6..dc7cc84 100644
--- a/tomee.xml
+++ b/tomee.xml
@@ -1,7 +1,6 @@
<div class="wiki-content maincontent"><p>Apache TomEE is a distribution of Tomcat with fully integrated ActiveMQ offering full JMS support to plain war files, Servlets and more. No setup is required and code like the following will work out of the box.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="5101179b-fd6d-4929-a474-8fd1914439b9" ac:name="code" ac:schema-version="1"><plain-text-body>
import javax.annotation.Resource;
import javax.servlet.http.HttpServlet;
import javax.jms.Topic;
@@ -10,10 +9,10 @@
public class MyServet extends HttpServlet {
- @Resource(name = "foo")
+ @Resource(name = "foo")
private Topic fooTopic;
- @Resource(name = "bar")
+ @Resource(name = "bar")
private Queue barQueue;
@Resource
@@ -34,7 +33,7 @@
producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
// Create a message
- TextMessage message = session.createTextMessage("Hello World!");
+ TextMessage message = session.createTextMessage("Hello World!");
// Tell the producer to send the message
producer.send(message);
@@ -42,66 +41,57 @@
//...
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>All topics and queues are created automatically when declared properly in code as above. For example, the following reference in code:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- @Resource(name = "foo")
+<structured-macro ac:macro-id="a447851b-470b-49ea-bdf2-98e354d90539" ac:name="code" ac:schema-version="1"><plain-text-body>
+ @Resource(name = "foo")
private Topic fooTopic;
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Is identical to the following declaration in the <tomee.home>/conf/tomee.xml file or WEB-INF/resources.xml file:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
- <Resource id="foo" type="javax.jms.Topic" />
-]]></script>
-</div></div>
+<structured-macro ac:macro-id="7d741179-b9fc-46f5-a40e-98cdfc961c53" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+ <Resource id="foo" type="javax.jms.Topic" />
+</plain-text-body></structured-macro>
<p>In both situations Topic name would be 'foo'.</p>
-<h2 id="TomEE-ConfiguringanEmbeddedBroker">Configuring an Embedded Broker</h2>
+<h2>Configuring an Embedded Broker</h2>
<p>If no broker is configured and JMS is used in the webapp, TomEE will create a broker equivalent to the following declaration:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="7c13fdba-cf0d-414c-af75-c52ffe1af967" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<tomee>
- <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter">
+ <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter">
BrokerXmlConfig = broker:(tcp://someHostName:61616)
ServerUrl = vm://localhost
</Resource>
- <Resource id="MyJmsConnectionFactory" type="javax.jms.ConnectionFactory">
+ <Resource id="MyJmsConnectionFactory" type="javax.jms.ConnectionFactory">
ResourceAdapter = MyJmsResourceAdapter
</Resource>
</tomee>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>This creates an ActiveMQ Broker that runs inside TomEE and is bound to the address <code>someHostName:61616</code>. This broker will start when TomEE starts and shutdown when TomEE shuts down. All JMS communication happening inside TomEE itself will happen using the embedded ActiveMQ Broker over the ActiveMQ "vm" transport which is optimized for sending and receiving messages when in the same JVM as the Broker.</p>
-<h2 id="TomEE-ConnectingtoanExternalBroker">Connecting to an External Broker</h2>
+<h2>Connecting to an External Broker</h2>
<p>It is possible to connect to an ActiveMQ Broker running externally. The setup is similar to the above with only two changes.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="07bc00ae-86a8-4e8e-b991-f2b7e2ebb733" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
<tomee>
- <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter">
+ <Resource id="MyJmsResourceAdapter" type="ActiveMQResourceAdapter">
BrokerXmlConfig =
ServerUrl = tcp://someHostName:61616
</Resource>
- <Resource id="MyJmsConnectionFactory" type="javax.jms.ConnectionFactory">
+ <Resource id="MyJmsConnectionFactory" type="javax.jms.ConnectionFactory">
ResourceAdapter = MyJmsResourceAdapter
</Resource>
</tomee>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Here the <code>BrokerXmlConfig</code> property is empty as we are not configuring an embedded broker to be run inside TomEE. The <code>ServerUrl</code> now points to an explicit remote host and port <code>someHostName:61616</code> where an ActiveMQ Broker must be running. This Broker can be a plain ActiveMQ install or an ActiveMQ Broker embedded in a TomEE install.</p></div>
diff --git a/tools.xml b/tools.xml
index 84ee710..38c5026 100644
--- a/tools.xml
+++ b/tools.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><ul class="childpages-macro"><li><a shape="rect" href="hermes-jms.xml">Hermes Jms</a></li><li><a shape="rect" href="hermes-screenshot.xml">Hermes Screenshot</a></li><li><a shape="rect" href="java-service-wrapper.xml">Java Service Wrapper</a></li><li><a shape="rect" href="maven2-activemq-broker-plugin.xml">Maven2 ActiveMQ Broker Plugin</a></li><li><a shape="rect" href="web-console.xml">Web Console</a></li></ul> </div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="08cb8ecf-0795-457c-8eff-11319bbd9977" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro> </div>
diff --git a/topologies.xml b/topologies.xml
index 9a30ac2..c0ec4b0 100644
--- a/topologies.xml
+++ b/topologies.xml
@@ -1,17 +1,7 @@
-<div class="wiki-content maincontent"><p>ActiveMQ supports a wide range of different deployment topologies as well as <a shape="rect" href="uri-protocols.xml">protocols</a> & wire formats. The following diagram shows a federated network of brokers with a few different kinds of topology.</p><p><a shape="rect" class="external-link" href="http://activemq.org/BrokerTopology.pdf" rel="nofollow"><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="topologies.data/BrokerTopology-1.png" data-image-src="/confluence/download/attachments/35975/BrokerTopology-1.png?version=1&modificationDate=1160651323000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3262" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="BrokerTopology-1.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35975" data-linked-resource-container-version="21"></span></a></p><p>Which topology you choose is up to you. We'll now describe a few of these protocols in a little more detail.</p><h2 id="Topologies-InVM">In VM</h2><p>A useful option when unit testing is to limit JMS communication to within a single JVM. For this use the protocol</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[vm://localhost
-]]></script>
-</div></div><p>You can segment the VM protocol to different groups - e.g. if you want to have logically different JMS networks within the same JVM, you can group networks using different URIs. e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[vm://localhost/foo
-]]></script>
-</div></div><p>This will ensure that different segments do not interfere with one another. Though typically we use unique topic and queue destinations so that all traffic can coexist happily on the same logical network.</p><h2 id="Topologies-Client-Server">Client-Server</h2><p>This is probably the most efficient and fastest solution for large numbers of clients requiring a diverse range of communication options from publish / subscribe to queue based communication. Typically the clients will connect with a Message Broker using a protocol, typically TCP or SSL but this could be NIO or other protocols.</p><p>We can load balance clients across brokers and provide broker failover so that we have a logical cluster of brokers with <a shape="rect" href="ha.xml">HA</a>.</p><p>e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tcp://somehost:port
-]]></script>
-</div></div><p>Or for SSL</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ssl://somehost:port
-]]></script>
-</div></div><p>You can use <a shape="rect" href="discovery.xml">Discovery</a> to find the brokers available that you can connect to which makes it easier to seamlessly connect to a cluster of brokers.</p><h2 id="Topologies-EmbeddedBroker">Embedded Broker</h2><p>This is logically equivalent to Client-Server but some (or all) clients contain a locally embedded broker. So communcation between the client and server (broker) are all within the same JVM and so do not use real networking - though brokers may communicate with other brokers or clients connected to it.</p><p>This can avoid the extra hop required to go from producer to broker to consumer - which is a great optimisation for RMI / RPC style situations, where you want the performance benefits (reduced latency) of point to point networking but with the scalabilty of a flexible messaging fabric.</p><p>Embedded Brokers can also simplify deployment options as well, its one less process to run.</p><p>Another use case for embedded brokers is to provide store and forward isolation from each service - so that the remote brokers can fail quite happily without affecting the service with the embedded broker. e.g. the entire network could fail, but a service could continue publishing messages to its embedded broker.</p><p>You can find out how to <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">configure an embedded broker here</a></p><h2 id="Topologies-PeertoPeer">Peer to Peer</h2><p>This allows peer based clusters to be created where there is no server - just clients connecting together.<br clear="none"> There are various ways to implement a peer to peer JMS network. One easy way is just to use a multicast transport for communication; then all nodes on the same multicast address will receive all messages and the local embedded message broker will route messages to the necessary MessageConsumers.</p><p>We currently have 3 choices for multicast protocols</p><ul><li>multicast</li><li>jgroups: uses the JGroups library to implement reliable multicast</li><li>jrms: uses Sun's JRMS library to implement reliable multicast</li></ul><p>Multicast is great in development though often you might want to disable this feature in production and have well known servers fixed on specific machines. Often socket based communication (using pointcast) is much faster & better for heavy-lifting - particularly on Java - so we tend to recommend to use multicast mostly for discovery and use TCP / SSL for your heavy duty messaging.</p><p>Often we can use the peer to peer topology as a bootstrap to create a cluster of clients & brokers and then autodeploy servers into the cluster for a true grid style network.</p><p>So you can get the effect of a peer based network using <a shape="rect" href="discovery.xml">Discovery</a> together with either stand alone Brokers or using embedded brokers.</p><h3 id="Topologies-JXTA">JXTA</h3><p>We have a JXTA transport which will use the full JXTA stack for negotiating NAT and across firewalls and so forth for creating a true peer based JMS network.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[jxta://hostname:port
-]]></script>
-</div></div><p>Currently you need to run one server which everyone connects to via JXTA. We've not yet created a pure peer network with JXTA</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ supports a wide range of different deployment topologies as well as <link><page ri:content-title="URI Protocols"></page><plain-text-link-body>protocols</plain-text-link-body></link> & wire formats. The following diagram shows a federated network of brokers with a few different kinds of topology.</p><p><a shape="rect" href="http://activemq.org/BrokerTopology.pdf"><image><attachment ri:filename="BrokerTopology-1.png"></attachment></image></a></p><p>Which topology you choose is up to you. We'll now describe a few of these protocols in a little more detail.</p><h2>In VM</h2><p>A useful option when unit testing is to limit JMS communication to within a single JVM. For this use the protocol</p><structured-macro ac:macro-id="1b41570f-9a1f-41e6-b040-464f0dd2240f" ac:name="code" ac:schema-version="1"><plain-text-body>vm://localhost
+</plain-text-body></structured-macro><p>You can segment the VM protocol to different groups - e.g. if you want to have logically different JMS networks within the same JVM, you can group networks using different URIs. e.g.</p><structured-macro ac:macro-id="5691b39d-b179-4bbf-a5e5-6ba41d9f7718" ac:name="code" ac:schema-version="1"><plain-text-body>vm://localhost/foo
+</plain-text-body></structured-macro><p>This will ensure that different segments do not interfere with one another. Though typically we use unique topic and queue destinations so that all traffic can coexist happily on the same logical network.</p><h2>Client-Server</h2><p>This is probably the most efficient and fastest solution for large numbers of clients requiring a diverse range of communication options from publish / subscribe to queue based communication. Typically the clients will connect with a Message Broker using a protocol, typically TCP or SSL but this could be NIO or other protocols.</p><p>We can load balance clients across brokers and provide broker failover so that we have a logical cluster of brokers with <link><page ri:content-title="HA"></page></link>.</p><p>e.g.</p><structured-macro ac:macro-id="0a091dab-5359-4cd0-9e4e-24c4447f8ed9" ac:name="code" ac:schema-version="1"><plain-text-body>tcp://somehost:port
+</plain-text-body></structured-macro><p>Or for SSL</p><structured-macro ac:macro-id="6b87a182-45dd-46ca-99da-d884dd2b15bc" ac:name="code" ac:schema-version="1"><plain-text-body>ssl://somehost:port
+</plain-text-body></structured-macro><p>You can use <link><page ri:content-title="Discovery"></page></link> to find the brokers available that you can connect to which makes it easier to seamlessly connect to a cluster of brokers.</p><h2>Embedded Broker</h2><p>This is logically equivalent to Client-Server but some (or all) clients contain a locally embedded broker. So communcation between the client and server (broker) are all within the same JVM and so do not use real networking - though brokers may communicate with other brokers or clients connected to it.</p><p>This can avoid the extra hop required to go from producer to broker to consumer - which is a great optimisation for RMI / RPC style situations, where you want the performance benefits (reduced latency) of point to point networking but with the scalabilty of a flexible messaging fabric.</p><p>Embedded Brokers can also simplify deployment options as well, its one less process to run.</p><p>Another use case for embedded brokers is to provide store and forward isolation from each service - so that the remote brokers can fail quite happily without affecting the service with the embedded broker. e.g. the entire network could fail, but a service could continue publishing messages to its embedded broker.</p><p>You can find out how to <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>configure an embedded broker here</plain-text-link-body></link></p><h2>Peer to Peer</h2><p>This allows peer based clusters to be created where there is no server - just clients connecting together.<br clear="none"> There are various ways to implement a peer to peer JMS network. One easy way is just to use a multicast transport for communication; then all nodes on the same multicast address will receive all messages and the local embedded message broker will route messages to the necessary MessageConsumers.</p><p>We currently have 3 choices for multicast protocols</p><ul><li>multicast</li><li>jgroups: uses the JGroups library to implement reliable multicast</li><li>jrms: uses Sun's JRMS library to implement reliable multicast</li></ul><p>Multicast is great in development though often you might want to disable this feature in production and have well known servers fixed on specific machines. Often socket based communication (using pointcast) is much faster & better for heavy-lifting - particularly on Java - so we tend to recommend to use multicast mostly for discovery and use TCP / SSL for your heavy duty messaging.</p><p>Often we can use the peer to peer topology as a bootstrap to create a cluster of clients & brokers and then autodeploy servers into the cluster for a true grid style network.</p><p>So you can get the effect of a peer based network using <link><page ri:content-title="Discovery"></page></link> together with either stand alone Brokers or using embedded brokers.</p><h3>JXTA</h3><p>We have a JXTA transport which will use the full JXTA stack for negotiating NAT and across firewalls and so forth for creating a true peer based JMS network.</p><structured-macro ac:macro-id="9f8fde62-138d-4313-bddb-cc2c495b14c6" ac:name="code" ac:schema-version="1"><plain-text-body>jxta://hostname:port
+</plain-text-body></structured-macro><p>Currently you need to run one server which everyone connects to via JXTA. We've not yet created a pure peer network with JXTA</p></div>
diff --git a/total-ordering.xml b/total-ordering.xml
index 4926cb6..b98d2db 100644
--- a/total-ordering.xml
+++ b/total-ordering.xml
@@ -1,22 +1,16 @@
-<div class="wiki-content maincontent"><p>Sometimes it can be useful to ensure that every topic consumer sees messages arriving on the topic in exactly the same order. Normally the broker will guarantee the order of all messages sent by the same producer. However, owing to the broker's use of multiple threads and asynchronous processing, messages from different producers could arrive in different consumers in different orders.</p><p>For example, if we have producers <strong><code>P</code></strong> and <strong><code>Q</code></strong> sending messages such that at about the same time <strong><code>P</code></strong> sends <strong><code>P1</code>, <code>P2</code></strong>, <strong><code>P3</code></strong> and <strong><code>Q</code></strong> sends <strong><code>Q1</code>, <code>Q2</code></strong>. Therefore, two different consumers <em>could</em> see messages arrive in the following order:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[consumer1: P1 P2 Q1 P3 Q2
+<div class="wiki-content maincontent"><p>Sometimes it can be useful to ensure that every topic consumer sees messages arriving on the topic in exactly the same order. Normally the broker will guarantee the order of all messages sent by the same producer. However, owing to the broker's use of multiple threads and asynchronous processing, messages from different producers could arrive in different consumers in different orders.</p><p>For example, if we have producers <strong><code>P</code></strong> and <strong><code>Q</code></strong> sending messages such that at about the same time <strong><code>P</code></strong> sends <strong><code>P1</code>, <code>P2</code></strong>, <strong><code>P3</code></strong> and <strong><code>Q</code></strong> sends <strong><code>Q1</code>, <code>Q2</code></strong>. Therefore, two different consumers <em>could</em> see messages arrive in the following order:</p><structured-macro ac:macro-id="45e8d2f6-6957-4958-a4e0-e6984dc66a86" ac:name="code" ac:schema-version="1"><plain-text-body>consumer1: P1 P2 Q1 P3 Q2
consumer2: P1 Q1 Q2 P2 P3
-]]></script>
-</div></div><p>In this example each producer's messages are in self-relative order. However, the streams of messages across producers can get intermixed.</p><p><em>Total Ordering</em> of a destination in ActiveMQ ensures that each consumer will see the same total order on that topic. This has a performance cost, since greater synchronization is required. This can be useful, particularly when very fast optimistic transactions are required. With total ordering the messages would arrive like this:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[consumer1: P1 P2 Q1 P3 Q2
+</plain-text-body></structured-macro><p>In this example each producer's messages are in self-relative order. However, the streams of messages across producers can get intermixed.</p><p><em>Total Ordering</em> of a destination in ActiveMQ ensures that each consumer will see the same total order on that topic. This has a performance cost, since greater synchronization is required. This can be useful, particularly when very fast optimistic transactions are required. With total ordering the messages would arrive like this:</p><structured-macro ac:macro-id="34a87d6f-917a-46d7-bc5c-bd6e5b5972a8" ac:name="code" ac:schema-version="1"><plain-text-body>consumer1: P1 P2 Q1 P3 Q2
consumer2: P1 P2 Q1 P3 Q2
-]]></script>
-</div></div><h2 id="TotalOrdering-ConfiguringTotalOrdering">Configuring Total Ordering</h2><p>Enable the <strong><code><strictOrderDispatchPolicy/></code></strong> on the <a shape="rect" href="per-destination-policies.xml">Per Destination Policies</a>. Here's an example</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<destinationPolicy>
+</plain-text-body></structured-macro><h2>Configuring Total Ordering</h2><p>Enable the <strong><code><strictOrderDispatchPolicy/></code></strong> on the <link><page ri:content-title="Per Destination Policies"></page></link>. Here's an example</p><structured-macro ac:macro-id="1ed4c58a-7249-42d8-aeba-968eb69a97ef" ac:name="code" ac:schema-version="1"><plain-text-body><destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry topic=">">
+ <policyEntry topic=">">
<dispatchPolicy>
<strictOrderDispatchPolicy/>
</dispatchPolicy>
</policyEntry>
</policyEntries>
</policyMap>
-</destinationPolicy>]]></script>
-</div></div></div>
+</destinationPolicy></plain-text-body></structured-macro></div>
diff --git a/udp-transport-reference.xml b/udp-transport-reference.xml
index 1b7bd5b..2e303da 100644
--- a/udp-transport-reference.xml
+++ b/udp-transport-reference.xml
@@ -1,23 +1,22 @@
<div class="wiki-content maincontent">
-<h3 id="UDPTransportReference-TheUDPTransport">The UDP Transport</h3>
+<h3>The UDP Transport</h3>
<p>The UDP transport allows clients to connect to a remote ActiveMQ broker using raw UDP</p>
<p>Note that by default UDP is not reliable; datagrams can be lost so you should add a reliability layer to ensure the JMS contract can be implemented on a non-reliable transport.</p>
-<h4 id="UDPTransportReference-ConfigurationSyntax">Configuration Syntax</h4>
+<h4>Configuration Syntax</h4>
<p><strong>udp://hostname:port?transportOptions</strong></p>
-<h5 id="UDPTransportReference-TransportOptions">Transport Options</h5>
+<h5>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> minmumWireFormatVersion </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 0 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The minimum version wireformat that is allowed </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> trace </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> false </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Causes all commands that are sent over the transport to be logged </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useLocalHost </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> true </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> When true, it causes the local machines name to resolve to "localhost". </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> datagramSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 4 * 1024 </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Specifies the size of a datagram </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> default </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> The name of the WireFormat to use </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat.* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> All the properties with this prefix are used to configure the wireFormat. See <a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a> for more information </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Option Name </p></th><th colspan="1" rowspan="1"><p> Default Value </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> minmumWireFormatVersion </p></td><td colspan="1" rowspan="1"><p> 0 </p></td><td colspan="1" rowspan="1"><p> The minimum version wireformat that is allowed </p></td></tr><tr><td colspan="1" rowspan="1"><p> trace </p></td><td colspan="1" rowspan="1"><p> false </p></td><td colspan="1" rowspan="1"><p> Causes all commands that are sent over the transport to be logged </p></td></tr><tr><td colspan="1" rowspan="1"><p> useLocalHost </p></td><td colspan="1" rowspan="1"><p> true </p></td><td colspan="1" rowspan="1"><p> When true, it causes the local machines name to resolve to "localhost". </p></td></tr><tr><td colspan="1" rowspan="1"><p> datagramSize </p></td><td colspan="1" rowspan="1"><p> 4 * 1024 </p></td><td colspan="1" rowspan="1"><p> Specifies the size of a datagram </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat </p></td><td colspan="1" rowspan="1"><p> default </p></td><td colspan="1" rowspan="1"><p> The name of the WireFormat to use </p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat.* </p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p> All the properties with this prefix are used to configure the wireFormat. See <link><page ri:content-title="Configuring Wire Formats"></page></link> for more information </p></td></tr></tbody></table>
-<h5 id="UDPTransportReference-ExampleURI">Example URI</h5>
+<h5>Example URI</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>udp://localhost:8123
-</pre>
-</div></div></div>
+<structured-macro ac:macro-id="00dbfb14-8ec1-4cee-907a-7d2894f960a9" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+udp://localhost:8123
+</plain-text-body></structured-macro></div>
diff --git a/unix-service.xml b/unix-service.xml
index 333cb29..2f8dd25 100644
--- a/unix-service.xml
+++ b/unix-service.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>This page contained a very basic procedure to create a unix service for activemq.</p><p>Due to the fact that ActiveMQ contains a very functional init script - this is not needed anymore.</p><p> </p><p><strong>Review the documentation of the init script: <a shape="rect" href="unix-shell-script.xml">Unix Shell Script</a></strong></p></div>
+<div class="wiki-content maincontent"><p>This page contained a very basic procedure to create a unix service for activemq.</p><p>Due to the fact that ActiveMQ contains a very functional init script - this is not needed anymore.</p><p> </p><p><strong>Review the documentation of the init script: <link><page ri:content-title="Unix Shell Script"></page></link></strong></p></div>
diff --git a/unix-shell-script.xml b/unix-shell-script.xml
index 663627d..622c28d 100644
--- a/unix-shell-script.xml
+++ b/unix-shell-script.xml
@@ -1,66 +1,28 @@
-<div class="wiki-content maincontent"><div class="toc-macro client-side-toc-macro" data-headerelements="H1,H2,H3,H4,H5,H6,H7"></div><h1 id="UnixShellScript-Functionaloverview">Functional overview</h1><p>From version 5.4.0 onwards, ActiveMQ comes with a enhanced shell script for starting, stopping and managing the broker in Unix environment. For basic <a shape="rect" href="activemq-command-line-tools-reference.xml#ActiveMQCommandLineToolsReference-activemq">activemq</a> and <a shape="rect" href="activemq-command-line-tools-reference.xml#ActiveMQCommandLineToolsReference-activemq-admin">activemq-admin</a> scripts functionality take a look at <a shape="rect" href="activemq-command-line-tools-reference.xml">ActiveMQ Command Line Tools Reference</a>.</p><p>This <code>activemq</code> script incorporate these two scripts into one and adds some new functionalities. On top of regular <code>activemq</code> and <code>activemq-admin</code> scripts, it adds the following features:</p><ul><li><p><strong>start</strong> - starts the broker in background. It saves process id in the <code>${ACTIVEMQ_DATA_DIR}/activemq.pid</code> for future reference. It accepts the same command line arguments like the original <code>activemq</code> script, so you can do something like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq start xbean:conf/activemq-stomp.xml]]></script>
-</div></div></li><li><p><strong>console</strong> - starts the broker in foreground. It is basically the replacement for the old <code>activemq</code> script<br clear="none">(you can interrupt the )</p></li></ul><ul><li><strong>stop</strong> - stops the broker that is running in the background. It tries first to stop the broker using <a shape="rect" href="activemq-command-line-tools-reference.xml#ActiveMQCommandLineToolsReference-shutdown">shutdown</a> task. If that task doesn't return in 30 seconds (configurable), it will kill the process.</li></ul><ul><li><strong>restart</strong> - stops the running instance (if there's one) and starts the new one</li></ul><ul><li><strong>status</strong> - checks if activemq process is running<br clear="none">(exitcode: 1 = broker is down, 0 = broker is up)</li></ul><ul><li><p><strong>create</strong> - create an ACTIVEMQ_BASE directory that separates a broker instance from its binaries, i.e., it creates copies of the ActiveMQ configuration files into the command-line specified directory and points to the binaries. You can start the broker with the <code>/bin</code> scripts in the newly created instance.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq create /path/to/brokers/mybroker ]]></script>
-</div></div></li><li><p><strong>browse</strong> - Display selected messages in a specified destination</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq browse FOO.BAR # use broker connection from configuration
-bin/activemq browse --amqurl tcp://localhost:61616 FOO.BAR]]></script>
-</div></div></li><li><p><strong>bstat</strong> - Performs a predefined query that displays useful statistics regarding the specified broker</p></li><li><p><strong>dstat</strong> - Performs a predefined query that displays useful tabular statistics regarding the specified destination type</p></li><li><p><strong>decrypt</strong> - Decrypts given text</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq decrypt --input 'BkiT42A0CZfL1SanJIgxvQ==' --password asdasdasdasd]]></script>
-</div></div></li><li><p><strong>encrypt</strong> - Encrypts given text</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq encrypt --password TESTPASSWORD --input FOOBAR]]></script>
-</div></div></li><li><p><strong>export</strong> - Exports a stopped brokers data files to an archive file for importing to another brokers like ActiveMQ Artemis</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ bin/activemq export --file=archivefile]]></script>
-</div></div></li><li><p><strong>list</strong> - Lists all available brokers in the specified JMX context</p></li><li><p><strong>purge</strong> - Delete selected destination's messages that matches the message selector</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq purge FOO.BAR # use jmx access data from configuration
-bin/activemq purge --jmxurl service:jmx:rmi:///jndi/rmi://127.0.0.1:11098/jmxrmi --jmxuser controlRole --jmxpassword abcd1234 FOO.BAR]]></script>
-</div></div></li><li><p><strong>query</strong> - Display selected broker component's attributes and statistics</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq query # use jmx access data from configuration
-bin/activemq query --jmxurl service:jmx:rmi:///jndi/rmi://127.0.0.1:11098/jmxrmi --jmxuser controlRole --jmxpassword abcd1234]]></script>
-</div></div></li></ul><h1 id="UnixShellScript-Configuringtheinit-script">Configuring the init-script</h1><p>For ActiveMQ server to run properly some basic system variables must be set. These variables define how much memory broker will have, SSL, logging, JAAS options and similar.</p><h2 id="UnixShellScript-Version5.11.0andhigher">Version 5.11.0 and higher</h2><h3 id="UnixShellScript-Configurationfileoftheinit-script">Configuration file of the init-script</h3><p>Since version 5.11.0, all default configuration variables are moved to the new <code>env</code> script file, so that they can be easily inspected and configured in a easy way. <br clear="none">There are also other configuration locations</p><p>The script scans the following locations for configurations in the following order:</p><ol><li>/etc/default/activemq</li><li>$HOME/.activemqrc</li><li>$INSTALLDIR/apache-activemq-<version>/bin/env</li></ol><p>The first existing file is read exclusively - all other files are ignored. <br clear="none">Undefined values are discovered in a automated way.</p><h3 id="UnixShellScript-Versionsprior5.11.0">Versions prior 5.11.0</h3><p>These parameters were configurable in <code>activemq</code> script itself. <br clear="none"><br clear="none">You could use <code>setup</code> command to create additional system wide defaults file to configure the broker.<br clear="none">(modify the settings in this file if neccessary - the default entries look a bit garbled due to an accidentally applied bugfix in this release)</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[./activemq setup /etc/default/activemq]]></script>
-</div></div><p>The configuration of the script can be placed at <code>/etc/default/activemq</code> or <code>$HOME/.activemqrc</code>. Note, this is the configuration for the <em>script</em> not for configuring ActiveMQ.</p><p>To use addtional configurations for running multiple instances on the same operating system rename or symlink script to a name matching to <code>activemq-instance-<INSTANCENAME></code>. This changes the configuration location to <code>/etc/default/activemq-instance-<INSTANCENAME></code> and <code>$HOME/.activemqrc-instance-<INSTANCENAME></code>. Configuration files in /etc have higher precedence.</p><h2 id="UnixShellScript-Runningactivemqasaunixdaemon">Running activemq as a unix daemon</h2><ul><li><p>Install activemq broker as "root" to be run as "activemq"</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[useradd -m activemq -d /srv/activemq
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="4fe7f2d0-8790-4f66-9f98-c49b9473a801" ac:name="toc" ac:schema-version="1"></structured-macro></p><h1>Functional overview</h1><p>From version 5.4.0 onwards, ActiveMQ comes with a enhanced shell script for starting, stopping and managing the broker in Unix environment. For basic <link ac:anchor="activemq"><page ri:content-title="ActiveMQ Command Line Tools Reference"></page><plain-text-link-body>activemq</plain-text-link-body></link> and <link ac:anchor="activemq-admin"><page ri:content-title="ActiveMQ Command Line Tools Reference"></page><plain-text-link-body>activemq-admin</plain-text-link-body></link> scripts functionality take a look at <link><page ri:content-title="ActiveMQ Command Line Tools Reference"></page></link>.</p><p>This <code>activemq</code> script incorporate these two scripts into one and adds some new functionalities. On top of regular <code>activemq</code> and <code>activemq-admin</code> scripts, it adds the following features:</p><ul><li><p><strong>start</strong> - starts the broker in background. It saves process id in the <code>${ACTIVEMQ_DATA_DIR}/activemq.pid</code> for future reference. It accepts the same command line arguments like the original <code>activemq</code> script, so you can do something like</p><structured-macro ac:macro-id="0c704072-5079-4fd6-9810-894f71eead7c" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq start xbean:conf/activemq-stomp.xml</plain-text-body></structured-macro></li><li><p><strong>console</strong> - starts the broker in foreground. It is basically the replacement for the old <code>activemq</code> script<br clear="none">(you can interrupt the )</p></li></ul><ul><li><strong>stop</strong> - stops the broker that is running in the background. It tries first to stop the broker using <link ac:anchor="shutdown"><page ri:content-title="ActiveMQ Command Line Tools Reference"></page><plain-text-link-body>shutdown</plain-text-link-body></link> task. If that task doesn't return in 30 seconds (configurable), it will kill the process.</li></ul><ul><li><strong>restart</strong> - stops the running instance (if there's one) and starts the new one</li></ul><ul><li><strong>status</strong> - checks if activemq process is running<br clear="none">(exitcode: 1 = broker is down, 0 = broker is up)</li></ul><ul><li><p><strong>create</strong> - create an ACTIVEMQ_BASE directory that separates a broker instance from its binaries, i.e., it creates copies of the ActiveMQ configuration files into the command-line specified directory and points to the binaries. You can start the broker with the <code>/bin</code> scripts in the newly created instance.</p><structured-macro ac:macro-id="d1b4e2e2-fc3b-417d-a726-60c0e7ef4b64" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq create /path/to/brokers/mybroker </plain-text-body></structured-macro></li><li><p><strong>browse</strong> - Display selected messages in a specified destination</p><structured-macro ac:macro-id="98c932fe-4a01-48da-83d3-d39c39f56647" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq browse FOO.BAR # use broker connection from configuration
+bin/activemq browse --amqurl tcp://localhost:61616 FOO.BAR</plain-text-body></structured-macro></li><li><p><strong>bstat</strong> - Performs a predefined query that displays useful statistics regarding the specified broker</p></li><li><p><strong>dstat</strong> - Performs a predefined query that displays useful tabular statistics regarding the specified destination type</p></li><li><p><strong>decrypt</strong> - Decrypts given text</p><structured-macro ac:macro-id="5071f416-262d-46d8-9411-9e5735babb7e" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq decrypt --input 'BkiT42A0CZfL1SanJIgxvQ==' --password asdasdasdasd</plain-text-body></structured-macro></li><li><p><strong>encrypt</strong> - Encrypts given text</p><structured-macro ac:macro-id="5807cac9-a043-4279-bc0e-3a9af1e33d68" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq encrypt --password TESTPASSWORD --input FOOBAR</plain-text-body></structured-macro></li><li><p><strong>export</strong> - Exports a stopped brokers data files to an archive file for importing to another brokers like ActiveMQ Artemis</p><structured-macro ac:macro-id="d98f7539-e414-4c95-be60-83c50bfaafcf" ac:name="code" ac:schema-version="1"><plain-text-body>$ bin/activemq export --file=archivefile</plain-text-body></structured-macro></li><li><p><strong>list</strong> - Lists all available brokers in the specified JMX context</p></li><li><p><strong>purge</strong> - Delete selected destination's messages that matches the message selector</p><structured-macro ac:macro-id="f03850c0-26d7-4de8-8cff-b28194e1f301" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq purge FOO.BAR # use jmx access data from configuration
+bin/activemq purge --jmxurl service:jmx:rmi:///jndi/rmi://127.0.0.1:11098/jmxrmi --jmxuser controlRole --jmxpassword abcd1234 FOO.BAR</plain-text-body></structured-macro></li><li><p><strong>query</strong> - Display selected broker component's attributes and statistics</p><structured-macro ac:macro-id="5dd089e1-681c-4780-82b8-077dd70092ed" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq query # use jmx access data from configuration
+bin/activemq query --jmxurl service:jmx:rmi:///jndi/rmi://127.0.0.1:11098/jmxrmi --jmxuser controlRole --jmxpassword abcd1234</plain-text-body></structured-macro></li></ul><h1>Configuring the init-script</h1><p>For ActiveMQ server to run properly some basic system variables must be set. These variables define how much memory broker will have, SSL, logging, JAAS options and similar.</p><h2>Version 5.11.0 and higher</h2><h3>Configuration file of the init-script</h3><p>Since version 5.11.0, all default configuration variables are moved to the new <code>env</code> script file, so that they can be easily inspected and configured in a easy way. <br clear="none">There are also other configuration locations</p><p>The script scans the following locations for configurations in the following order:</p><ol><li>/etc/default/activemq</li><li>$HOME/.activemqrc</li><li>$INSTALLDIR/apache-activemq-<version>/bin/env</li></ol><p>The first existing file is read exclusively - all other files are ignored. <br clear="none">Undefined values are discovered in a automated way.</p><h3>Versions prior 5.11.0</h3><p>These parameters were configurable in <code>activemq</code> script itself. <br clear="none"><br clear="none">You could use <code>setup</code> command to create additional system wide defaults file to configure the broker.<br clear="none">(modify the settings in this file if neccessary - the default entries look a bit garbled due to an accidentally applied bugfix in this release)</p><structured-macro ac:macro-id="d866b6dc-3b3c-474a-91ed-95edf3884735" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>./activemq setup /etc/default/activemq</plain-text-body></structured-macro><p>The configuration of the script can be placed at <code>/etc/default/activemq</code> or <code>$HOME/.activemqrc</code>. Note, this is the configuration for the <em>script</em> not for configuring ActiveMQ.</p><p>To use addtional configurations for running multiple instances on the same operating system rename or symlink script to a name matching to <code>activemq-instance-<INSTANCENAME></code>. This changes the configuration location to <code>/etc/default/activemq-instance-<INSTANCENAME></code> and <code>$HOME/.activemqrc-instance-<INSTANCENAME></code>. Configuration files in /etc have higher precedence.</p><h2>Running activemq as a unix daemon</h2><ul><li><p>Install activemq broker as "root" to be run as "activemq"</p><structured-macro ac:macro-id="30cb19f1-9767-4b15-9df6-3ba3fc98b006" ac:name="code" ac:schema-version="1"><plain-text-body>useradd -m activemq -d /srv/activemq
cd /srv/activemq
tar zxvf apache-activemq-<version>-bin.tar.gz$ ln -snf apache-activemq-<version> current
chown -R activemq:users apache-activemq-<version>
-]]></script>
-</div></div></li><li><p>Create a global default configuration and edit the configuration</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cp apache-activemq-<version>/bin/env /etc/default/activemq
-sed -i '~s/^ACTIVEMQ_USER=""/ACTIVEMQ_USER="activemq"/' /etc/default/activemq
+</plain-text-body></structured-macro></li><li><p>Create a global default configuration and edit the configuration</p><structured-macro ac:macro-id="b45c45da-0f64-4a5b-b8e4-01215a038292" ac:name="code" ac:schema-version="1"><plain-text-body>cp apache-activemq-<version>/bin/env /etc/default/activemq
+sed -i '~s/^ACTIVEMQ_USER=""/ACTIVEMQ_USER="activemq"/' /etc/default/activemq
vim /etc/default/activemq
-chmod 644 /etc/default/activemq]]></script>
-</div></div><ul><li>Configure the java heap to a size suitable to your system environment and usage</li><li>Consider to move the folders "data", "tmp" and "conf" out of the installation path</li></ul></li><li><p>Install the init script</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ln -snf /srv/activemq/current/bin/activemq /etc/init.d/activemq]]></script>
-</div></div></li><li><p>Activate the init script at system startup<br clear="none">(TODO: uncomplete)</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[# RHEL
+chmod 644 /etc/default/activemq</plain-text-body></structured-macro><ul><li>Configure the java heap to a size suitable to your system environment and usage</li><li>Consider to move the folders "data", "tmp" and "conf" out of the installation path</li></ul></li><li><p>Install the init script</p><structured-macro ac:macro-id="a7caa18a-0f98-4b60-960a-3af354196b21" ac:name="code" ac:schema-version="1"><plain-text-body>ln -snf /srv/activemq/current/bin/activemq /etc/init.d/activemq</plain-text-body></structured-macro></li><li><p>Activate the init script at system startup<br clear="none">(TODO: uncomplete)</p><structured-macro ac:macro-id="53b72991-21e7-46b8-b5c5-f19ba2cf94fe" ac:name="code" ac:schema-version="1"><plain-text-body># RHEL
chkconfig --add activemq
chkconfig activemq on
# Debian/Ubuntu
-update-rc.d defaults activemq]]></script>
-</div></div></li></ul><h2 id="UnixShellScript-Runningmultipleinstances">Running multiple instances</h2><p>To use additional configurations for running multiple instances on the same operating system rename or symlink script to a name matching to <code>activemq-instance-<INSTANCENAME></code>.<br clear="none">This changes the configuration location to <code>/etc/default/activemq-instance-<INSTANCENAME></code> and <code>$HOME/.activemqrc-instance-<INSTANCENAME></code>. Configuration files in /etc have higher precedence.</p><p>Example procedure suitable to the procedure "Running activemq as a unix daemon"</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Example</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mkdir /srv/activemq/instance1
+update-rc.d defaults activemq</plain-text-body></structured-macro></li></ul><h2>Running multiple instances</h2><p>To use additional configurations for running multiple instances on the same operating system rename or symlink script to a name matching to <code>activemq-instance-<INSTANCENAME></code>.<br clear="none">This changes the configuration location to <code>/etc/default/activemq-instance-<INSTANCENAME></code> and <code>$HOME/.activemqrc-instance-<INSTANCENAME></code>. Configuration files in /etc have higher precedence.</p><p>Example procedure suitable to the procedure "Running activemq as a unix daemon"</p><structured-macro ac:macro-id="18c288b9-5b51-42aa-b357-898627f9ddf4" ac:name="code" ac:schema-version="1"><parameter ac:name="title">Example</parameter><plain-text-body>mkdir /srv/activemq/instance1
cp -av /srv/activemq/current/conf/ /srv/activemq/instance1/
mkdir /srv/activemq/instance1/{data,tmp}
ln -snf /srv/activemq/current/bin/activemq /etc/init.d/activemq-instance-test1
-cp /srv/activemq/install/bin/env /etc/default/activemq-instance-instance-test1]]></script>
-</div></div><p>Modify the configuration variables in /etc/default/activemq-instance-instance-test1</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ACTIVEMQ_HOME="/srv/activemq/current/"
-ACTIVEMQ_CONF="/srv/activemq/instance1/conf"
-ACTIVEMQ_DATA="/srv/activemq/instance1/data"
-ACTIVEMQ_TMP="/srv/activemq/instance1/tmp"]]></script>
-</div></div><p>Control the instance</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[/etc/init.d/activemq-instance1 start|stop|restart|console|....]]></script>
-</div></div><p> </p><p>Hint: If you are using multiple instances you can only add the main instance to the automatic system start using ("update-rc.d" or "chkconfig") because the LSB Header "Provides" needs to be uniq.</p><h1 id="UnixShellScript-Testingandreportinginteroperabilityproblemsforunixplatforms">Testing and reporting interoperability problems for unix platforms</h1><p> </p><p>The activemq repo provides a testsuite to validate the proper operation of the unix shell script on different platforms.</p><ul><li><p>Download the testsuite<br clear="none">Alternatively clone the sourcecode repo (<a shape="rect" href="source.xml">Source</a>) and pick the file <em>assembly/src/test/scripts/init-script-testsuite</em></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd /tmp
-wget -c "https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob_plain;f=assembly/src/test/scripts/init-script-testsuite;hb=HEAD"]]></script>
-</div></div></li><li><p>Execute the testsuite</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd <Installation Dir of the ActiveMQ Script>
+cp /srv/activemq/install/bin/env /etc/default/activemq-instance-instance-test1</plain-text-body></structured-macro><p>Modify the configuration variables in /etc/default/activemq-instance-instance-test1</p><structured-macro ac:macro-id="8821fd41-4027-440a-a0ba-45ec44a6326f" ac:name="code" ac:schema-version="1"><plain-text-body>ACTIVEMQ_HOME="/srv/activemq/current/"
+ACTIVEMQ_CONF="/srv/activemq/instance1/conf"
+ACTIVEMQ_DATA="/srv/activemq/instance1/data"
+ACTIVEMQ_TMP="/srv/activemq/instance1/tmp"</plain-text-body></structured-macro><p>Control the instance</p><structured-macro ac:macro-id="93b582f7-b195-460a-a35a-0c042543955b" ac:name="code" ac:schema-version="1"><plain-text-body>/etc/init.d/activemq-instance1 start|stop|restart|console|....</plain-text-body></structured-macro><p> </p><p>Hint: If you are using multiple instances you can only add the main instance to the automatic system start using ("update-rc.d" or "chkconfig") because the LSB Header "Provides" needs to be uniq.</p><h1>Testing and reporting interoperability problems for unix platforms</h1><p> </p><p>The activemq repo provides a testsuite to validate the proper operation of the unix shell script on different platforms.</p><ul><li><p>Download the testsuite<br clear="none">Alternatively clone the sourcecode repo (<link><page ri:content-title="Source"></page></link>) and pick the file <em>assembly/src/test/scripts/init-script-testsuite</em></p><structured-macro ac:macro-id="f30725ee-b742-47d8-9c94-832c2d70772e" ac:name="code" ac:schema-version="1"><plain-text-body>cd /tmp
+wget -c "https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob_plain;f=assembly/src/test/scripts/init-script-testsuite;hb=HEAD"</plain-text-body></structured-macro></li><li><p>Execute the testsuite</p><structured-macro ac:macro-id="b90c7b7e-dc6b-4bab-92a5-c5ba69f30c42" ac:name="code" ac:schema-version="1"><plain-text-body>cd <Installation Dir of the ActiveMQ Script>
./activemq stop
-/tmp/init-script-testsuite 2>&1| tee /tmp/test-suite.log]]></script>
-</div></div></li><li><p>Detailed debug information can be provided by the following procedure</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[export PS4=' ${BASH_SOURCE}:${LINENO}(${FUNCNAME[0]}) '
-bash -x ./activemq <argument> 2>&1 |tee /tmp/detailed-debugging.log]]></script>
-</div></div></li><li><p>Create a ticket and attach the logfiles to the ticket.</p></li></ul><p> </p></div>
+/tmp/init-script-testsuite 2>&1| tee /tmp/test-suite.log</plain-text-body></structured-macro></li><li><p>Detailed debug information can be provided by the following procedure</p><structured-macro ac:macro-id="86b4e441-0226-484a-900c-6634c94ae484" ac:name="code" ac:schema-version="1"><plain-text-body>export PS4=' ${BASH_SOURCE}:${LINENO}(${FUNCNAME[0]}) '
+bash -x ./activemq <argument> 2>&1 |tee /tmp/detailed-debugging.log</plain-text-body></structured-macro></li><li><p>Create a ticket and attach the logfiles to the ticket.</p></li></ul><p> </p></div>
diff --git a/unix.xml b/unix.xml
index 0101206..07355f5 100644
--- a/unix.xml
+++ b/unix.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>This page contains resources that will make you adapt ActiveMQ to your Unix-based operating system.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="unix-service.xml">Unix Service</a></li><li><a shape="rect" href="unix-shell-script.xml">Unix Shell Script</a></li></ul></div>
+<structured-macro ac:macro-id="953e5c01-3c22-41fc-b32b-55b266594b5f" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/uri-protocols.xml b/uri-protocols.xml
index 26a9c77..e4e38b7 100644
--- a/uri-protocols.xml
+++ b/uri-protocols.xml
@@ -1,40 +1,34 @@
-<div class="wiki-content maincontent"><p>ActiveMQ is designed to support mutliple different <a shape="rect" href="topologies.xml">topologies</a> and protocols. Which one you use depends on your messaging requirements, quality of service and network topology.</p>
+<div class="wiki-content maincontent"><p>ActiveMQ is designed to support mutliple different <link><page ri:content-title="Topologies"></page><link-body>topologies</link-body></link> 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 shape="rect" href="configuring-transports.xml">transports</a> supported. You can specify the connection URL on an <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> (in a constructor or via the brokerURL property). </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 <link><page ri:content-title="Configuring Transports"></page><link-body>transports</link-body></link> supported. You can specify the connection URL on an <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> (in a constructor or via the brokerURL property). </p>
<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>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-ConnectionFactory factory = new ActiveMQConnectionFactory("tcp://somehost:61616");
+<structured-macro ac:macro-id="c324de2c-ad21-4ce2-a05d-19979b731e52" ac:name="code" ac:schema-version="1"><plain-text-body>
+ConnectionFactory factory = new ActiveMQConnectionFactory("tcp://somehost:61616");
Connection connection = factory.createConnection();
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h2 id="URIProtocols-ProtocolSummary">Protocol Summary</h2>
+<h2>Protocol Summary</h2>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Protocol</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Example</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Server?</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>VM</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>vm://host:port</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Client connect to each other within the same JVM. This does use an asynchronous channel and a separate worker thread. You can enable sync sending using a query parameter, such as </p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[vm://localhost?async=false]]></script>
-</div></div></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Yes</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>TCP</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>tcp://host:port</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Client connects to the broker at the given URL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Yes</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>SSL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ssl://host:port</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Client connects to the broker at the given URL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Yes</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Failover</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>failover:(Uri1,Uri2,Uri3,...,UriN)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Provides a list of possible URIs to connect to and one is randomly chosen. If the connection fails then the transport auto-reconnects to a different one</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Peer</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>peer://serviceName</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Creates a pure peer to peer network of nodes of a given service name. In peer mode there is no server, nodes just automatically connect and make a peer network. The serviceName allows you to keep networks apart from each other, such as development, testing, UAT and production.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Discovery</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>discovery://host:port</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses <a shape="rect" href="discovery.xml">Discovery</a> to connect to an available broker of the correct channel name. If multiple brokers can be found then one is chosen at random. If the connection fails then another broker is chosen, if available</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Zeroconf</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>zeroconf:_activemq.broker.development.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Uses <a shape="rect" href="zeroconf.xml">Zeroconf</a> to connect to an available broker of the correct Zeroconf service name. If multiple brokers can be found then one is chosen at random. If the connection fails then another broker is chosen, if available</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>HTTP</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>http://host:port</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Client connects to the broker using HTTP tunnelling, with XML payloads suitable for going through firewalls</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Yes</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>UDP</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>udp://host:port</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Client connects to the broker at the given URL</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>multicast</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>multicast://host:port</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>No server, though only works for pub/sub. A pure peer based network where all traffic is multicasted around and filtering is performed on the client.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Protocol</p></th><th colspan="1" rowspan="1"><p>Example</p></th><th colspan="1" rowspan="1"><p>Description</p></th><th colspan="1" rowspan="1"><p>Server?</p></th></tr><tr><td colspan="1" rowspan="1"><p>VM</p></td><td colspan="1" rowspan="1"><p>vm://host:port</p></td><td colspan="1" rowspan="1"><p>Client connect to each other within the same JVM. This does use an asynchronous channel and a separate worker thread. You can enable sync sending using a query parameter, such as </p>
+<structured-macro ac:macro-id="5dc9ba8b-03f9-42ef-b042-54331d034cbe" ac:name="code" ac:schema-version="1"><plain-text-body>vm://localhost?async=false</plain-text-body></structured-macro></td><td colspan="1" rowspan="1"><p>Yes</p></td></tr><tr><td colspan="1" rowspan="1"><p>TCP</p></td><td colspan="1" rowspan="1"><p>tcp://host:port</p></td><td colspan="1" rowspan="1"><p>Client connects to the broker at the given URL</p></td><td colspan="1" rowspan="1"><p>Yes</p></td></tr><tr><td colspan="1" rowspan="1"><p>SSL</p></td><td colspan="1" rowspan="1"><p>ssl://host:port</p></td><td colspan="1" rowspan="1"><p>Client connects to the broker at the given URL</p></td><td colspan="1" rowspan="1"><p>Yes</p></td></tr><tr><td colspan="1" rowspan="1"><p>Failover</p></td><td colspan="1" rowspan="1"><p>failover:(Uri1,Uri2,Uri3,...,UriN)</p></td><td colspan="1" rowspan="1"><p>Provides a list of possible URIs to connect to and one is randomly chosen. If the connection fails then the transport auto-reconnects to a different one</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>Peer</p></td><td colspan="1" rowspan="1"><p>peer://serviceName</p></td><td colspan="1" rowspan="1"><p>Creates a pure peer to peer network of nodes of a given service name. In peer mode there is no server, nodes just automatically connect and make a peer network. The serviceName allows you to keep networks apart from each other, such as development, testing, UAT and production.</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>Discovery</p></td><td colspan="1" rowspan="1"><p>discovery://host:port</p></td><td colspan="1" rowspan="1"><p>Uses <link><page ri:content-title="Discovery"></page></link> to connect to an available broker of the correct channel name. If multiple brokers can be found then one is chosen at random. If the connection fails then another broker is chosen, if available</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>Zeroconf</p></td><td colspan="1" rowspan="1"><p>zeroconf:_activemq.broker.development.</p></td><td colspan="1" rowspan="1"><p>Uses <link><page ri:content-title="Zeroconf"></page></link> to connect to an available broker of the correct Zeroconf service name. If multiple brokers can be found then one is chosen at random. If the connection fails then another broker is chosen, if available</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>HTTP</p></td><td colspan="1" rowspan="1"><p>http://host:port</p></td><td colspan="1" rowspan="1"><p>Client connects to the broker using HTTP tunnelling, with XML payloads suitable for going through firewalls</p></td><td colspan="1" rowspan="1"><p>Yes</p></td></tr><tr><td colspan="1" rowspan="1"><p>UDP</p></td><td colspan="1" rowspan="1"><p>udp://host:port</p></td><td colspan="1" rowspan="1"><p>Client connects to the broker at the given URL</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>multicast</p></td><td colspan="1" rowspan="1"><p>multicast://host:port</p></td><td colspan="1" rowspan="1"><p>No server, though only works for pub/sub. A pure peer based network where all traffic is multicasted around and filtering is performed on the client.</p></td><td colspan="1" rowspan="1"><p> </p></td></tr></tbody></table>
<p>The <em>Server?</em> column above indiciates whether or not a protocol can be used in an ActiveMQ 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 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 inside your JVM you can enable the useEmbeddedBroker property on the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a>.</p>
+<p>When connecting to an ActiveMQ 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 inside your JVM you can enable the useEmbeddedBroker property on the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a>.</p>
-<p>Please refer to the <a shape="rect" href="topologies.xml">topologies overview</a> to see how we can use ActiveMQ in many different topologies to suit your messaging needs.</p>
+<p>Please refer to the <link><page ri:content-title="Topologies"></page><link-body>topologies overview</link-body></link> to see how we can use ActiveMQ in many different topologies to suit your messaging needs.</p>
-<h3 id="URIProtocols-SpecifyingmultipleURLstoconnectto">Specifying multiple URLs to connect to</h3>
+<h3>Specifying multiple URLs to connect to</h3>
-<p>If you want full <a shape="rect" href="ha.xml">HA</a> to provide failover and auto-reconnection you can use the <em>failover:</em> prefix</p>
+<p>If you want full <link><page ri:content-title="HA"></page></link> to provide failover and auto-reconnection you can use the <em>failover:</em> prefix</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c4cb2d3e-3e3e-44c1-907d-5cc1903340d2" ac:name="code" ac:schema-version="1"><plain-text-body>
failover:(tcp://foo:61699,tcp://bar:61617,tcp://whatnot:61698)
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>see <a shape="rect" href="configuring-transports.xml">Configuring Transports</a> for more details</p></div>
+<p>see <link><page ri:content-title="Configuring Transports"></page></link> for more details</p></div>
diff --git a/use-cases.xml b/use-cases.xml
index 5194fe5..663c59e 100644
--- a/use-cases.xml
+++ b/use-cases.xml
@@ -1,9 +1,9 @@
<div class="wiki-content maincontent">
-<p>Messaging is a diverse and wide ranging subject - there are many different use cases, requirements and deployment options. This is one of the reasons why its so interesting to work on <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>Messaging is a diverse and wide ranging subject - there are many different use cases, requirements and deployment options. This is one of the reasons why its so interesting to work on <emoticon ac:name="smile"></emoticon></p>
<p>This document tries to highlight some of the main use cases we are trying to tackle with ActiveQM</p>
-<h2 id="UseCases-Transactionalmessaging">Transactional messaging</h2>
+<h2>Transactional messaging</h2>
<p>This use case focusses on transactionality, persistence, never ever missing a message and processing each message exactly once irrespective of system failures.</p>
<p>Typically the JMS connection will be used in an XA way with other JMS connections or other XA resources like JDBC / EJBs etc.</p>
@@ -13,27 +13,27 @@
<p>Typically if any node is offline then all the messages will be persisted for when the node comes back online.</p>
-<h2 id="UseCases-Highperformancemarketdatadistribution">High performance market data distribution</h2>
+<h2>High performance market data distribution</h2>
<p>This use case focusses on throughput and efficient routing. The idea is to distribute massive volumes of rapidly changing data around a large network as quickly as possible.</p>
<p>Typically throughtput and performance is key - as the amount of data and rate of change is very high and so persistence is rarely used and missing a message is often acceptable in times of failure as old data is often not necessary, the latest prices are what matters.</p>
-<h2 id="UseCases-Clusteringandgeneralpurposeasyncmessagingmodel">Clustering and general purpose async messaging model</h2>
+<h2>Clustering and general purpose async messaging model</h2>
<p>This use case focusses on latency and speed.</p>
-<p>When implementing web or EJB based clustering the aim is to maintain a cluster of nodes, typically using multicast for discovery & keep-alive and then using direct socket connections to communicate efficiently between buddies. Please see <a shape="rect" class="external-link" href="http://activecluster.codehaus.org/" rel="nofollow">ActiveCluster</a> for an example API and implementation of this model of clustering.</p>
+<p>When implementing web or EJB based clustering the aim is to maintain a cluster of nodes, typically using multicast for discovery & keep-alive and then using direct socket connections to communicate efficiently between buddies. Please see <a shape="rect" href="http://activecluster.codehaus.org/">ActiveCluster</a> for an example API and implementation of this model of clustering.</p>
<p>This is similar to using a JMS provider as an RMI layer in EJB-style or WS style services - again could end up being mostly multicast for discovery & direct sockets for communication to minimise latency. i.e. rather than having separate servers in between clients, the clients end up talking directly with each other to reduce latency.</p>
-<h2 id="UseCases-WebStreamingofdata">Web Streaming of data</h2>
+<h2>Web Streaming of data</h2>
-<p>This use case focusses on <a shape="rect" href="ajax.xml">Ajax</a> support in ActiveMQ.</p>
+<p>This use case focusses on <link><page ri:content-title="Ajax"></page></link> support in ActiveMQ.</p>
<p>Increasingly folks want to stream data real time right into web browsers. For example streaming financial stock prices, to show live IM conversations, live auctions or to dynamically update live content and news.</p>
<p>In this use case we integrate ActiveMQ into a web container and provide close web-integration to enable HTTP POSTs to publish messages and slow JavaScript HTTP GET operations to receive messages. </p>
-<h2 id="UseCases-RESTfulAPItomessagingusingHTTP">RESTful API to messaging using HTTP</h2>
+<h2>RESTful API to messaging using HTTP</h2>
<p>This use case focusses on connectivity and cross-language & cross-technology connectivity.</p>
diff --git a/user-forum.xml b/user-forum.xml
index 89e93e6..4848e1c 100644
--- a/user-forum.xml
+++ b/user-forum.xml
@@ -1,5 +1,5 @@
-<div class="wiki-content maincontent"><p>
-<a shape="rect" id="nabblelink" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html">ActiveMQ - User</a>
-<script src="http://activemq.2283324.n4.nabble.com/embed/f2341805"></script>
-</p><p></p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="132c2914-5a68-4e9e-8719-937cb704a410" ac:name="html" ac:schema-version="1"><plain-text-body>
+<a id="nabblelink" href="http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html">ActiveMQ - User</a>
+<script src="http://activemq.2283324.n4.nabble.com/embed/f2341805"></script>
+</plain-text-body></structured-macro></p><p></p></div>
diff --git a/user-submitted-configurations.xml b/user-submitted-configurations.xml
index 798ecc1..362a742 100644
--- a/user-submitted-configurations.xml
+++ b/user-submitted-configurations.xml
@@ -1,3 +1,4 @@
<div class="wiki-content maincontent"><p>Please add any configurations of ActiveMQ you wish to share with other users here...</p>
-<ul><li><a shape="rect" href="complex-single-broker-configuration-stomp-only.xml">Complex Single Broker Configuration (STOMP only)</a> - Example of an ActiveMQ configuration with predefined queues, simple destination security.</li><li><a shape="rect" href="jms-and-jdbc-operations-in-one-transaction.xml">JMS and JDBC operations in one transaction</a> - Example using Spring beans.</li><li><a shape="rect" href="jms-bridge-with-local-broker.xml">JMS Bridge With Local Broker</a> - Example jmsBridge connection with the local broker.</li><li><a shape="rect" href="jms-bridge-with-remote-broker.xml">JMS Bridge With Remote Broker</a> - Example jmsBridge connection with a remote broker.</li><li><a shape="rect" href="jms-bridge-with-remote-tibco-broker.xml">JMS Bridge With Remote TIBCO Broker</a> - Example jmsBridge connection to remote TIBCO EMS broker.</li><li><a shape="rect" href="jms-bridge-with-oracle-aq.xml">JMS Bridge With Oracle AQ</a> - Example jmsBridge connection to Oracle AQ queues and topics.</li><li><a shape="rect" href="sample-camel-routes.xml">Sample Camel Routes</a> - Sample configuration showing Juel and XPath Camel routes.</li></ul></div>
+<ul><li><link><page ri:content-title="Complex Single Broker Configuration (STOMP only)"></page></link> - Example of an ActiveMQ configuration with predefined queues, simple destination security.</li><li><link><page ri:content-title="JMS and JDBC operations in one transaction"></page></link> - Example using Spring beans.</li><li><link><page ri:content-title="JMS Bridge With Local Broker"></page></link> - Example jmsBridge connection with the local broker.</li><li><link><page ri:content-title="JMS Bridge With Remote Broker"></page></link> - Example jmsBridge connection with a remote broker.</li><li><link><page ri:content-title="JMS Bridge With Remote TIBCO Broker"></page></link> - Example jmsBridge connection to remote TIBCO EMS broker.</li><li><link><page ri:content-title="JMS Bridge With Oracle AQ"></page></link> - Example jmsBridge connection to Oracle AQ queues and topics.</li><li><link><page ri:content-title="Sample Camel Routes"></page></link> - Sample configuration showing Juel and XPath Camel routes.</li></ul>
+</div>
diff --git a/users.xml b/users.xml
index 48c48da..2636145 100644
--- a/users.xml
+++ b/users.xml
@@ -1,5 +1,6 @@
<div class="wiki-content maincontent"><p>This page contains a list of some of our users and gives a brief overview of how they are using ActiveMQ. The purpose of this page is to help the ActiveMQ community get to know each other & find out what we're all doing with ActiveMQ and for the developers of ActiveMQ to get a better feel for what kinds of things people are doing with ActiveMQ.</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Company name or description</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Use of ActiveMQ</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://fusesource.com/" rel="nofollow">FuseSource</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> FuseSource provide enterprise class support, training and mentoring around an open source Apache SOA stack including <a shape="rect" class="external-link" href="http://servicemix.apache.org/">ServiceMix</a>, <a shape="rect" class="external-link" href="http://activemq.apache.org/">ActiveMQ</a> and <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/">Camel</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> Matt Biddulph </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.dopplr.com/" rel="nofollow">Dopplr</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use ActiveMQ as their messaging provider - see Matt's great presentation <a shape="rect" class="external-link" href="http://www.slideshare.net/carsonified/dopplr-its-made-of-messages-matt-biddulph-presentation" rel="nofollow">Made of Messages</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://gnip.com" rel="nofollow">gnip</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Use <a shape="rect" class="external-link" href="http://www.byteonic.com/2008/gnip-online-message-oriented-middleware-mom/" rel="nofollow">ActiveMQ for their low latency MOM messaging</a> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Peter Brooke</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>RomTrac</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>We are using ActiveMQ and Camel to provider high performance load balancing of requests across a cluster of servers</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Sridhar Komandur</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>University of Washington (UW Tech)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ActiveMQ is being used as backend messaging layer for a variety of distributed applications withing UW</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Gareth Davies</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Daugherty Systems</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>At current client (global agribusiness firm), using ActiveMQ for asynchronous, reliable messaging within in-house SOA application</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Raffe G.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Document archiving/flow systems</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>We try to use ActiveMQ as connectivity option between our FrontEnd (FE) and BackEnd (BE). FE receives requests which processing is normally heavy time-consuming. Thus FE creates a message which is sent to BE for processing and returns a ticket (correlationID) to the user. This will later use the ticket to ask for the response of the processing (again sending a message from FE to BE which will respond synchronously in this case). So we want to have reliable messaging between our FE and BE.<br clear="none">
-So far this is not entirely working for us.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Tom L.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Promotional Marketing</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Here is our flow. The backend systems (written in a propriatery language) send requests to a tomcat server via http. The message servlet from the ActiveMQ's web API connects to an embeded broker instance using the VM connector and places the request on the queue. We don't have a need for clustering yet, but we are planning on using either tomcat's clustering or ActiveCluster if it becomes necessary (since the brokers are embeded anyways). </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Aleksi Kallio</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>CSC, the Finnish IT center for science</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>We are building a bioinformatics system for DNA-microarray data storage and analysis. System contains rich graphical clients, a large database and heavy server machinery for processing analysis jobs. We are trying to use ActiveMQ as a JMS implementation to shuttle data between the servers and clients in an event based manner.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="mailto:frik@gatherworks.com" rel="nofollow">Frik Strecker</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.gatherplace.net" rel="nofollow">GatherPlace</a> provides cost-effective remote application sharing </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>ActiveMQ is used to collect real-time billing and usage information from servers distributed throughout the world. Free accounts are available to active ActiveMQ developers for ActiveMQ purposes. </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://code.google.com/p/golconde/" rel="nofollow">Golconde</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses ActiveMQ to implement a distributed Postgresql replication system </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <a shape="rect" class="external-link" href="http://www.oreillynet.com/pub/au/3212" rel="nofollow">Robert Liguori</a> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> STG Technologies, Inc.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> Uses ActiveMQ in support of the aviation industry.</p></td></tr></tbody></table></div></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>Name</p></th><th colspan="1" rowspan="1"><p>Company name or description</p></th><th colspan="1" rowspan="1"><p>Use of ActiveMQ</p></th></tr><tr><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://fusesource.com/">FuseSource</a> </p></td><td colspan="1" rowspan="1"><p> FuseSource provide enterprise class support, training and mentoring around an open source Apache SOA stack including <a shape="rect" href="http://servicemix.apache.org/">ServiceMix</a>, <a shape="rect" href="http://activemq.apache.org/">ActiveMQ</a> and <a shape="rect" href="http://activemq.apache.org/camel/">Camel</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> Matt Biddulph </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.dopplr.com/">Dopplr</a> </p></td><td colspan="1" rowspan="1"><p> Use ActiveMQ as their messaging provider - see Matt's great presentation <a shape="rect" href="http://www.slideshare.net/carsonified/dopplr-its-made-of-messages-matt-biddulph-presentation">Made of Messages</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://gnip.com">gnip</a> </p></td><td colspan="1" rowspan="1"><p> Use <a shape="rect" href="http://www.byteonic.com/2008/gnip-online-message-oriented-middleware-mom/">ActiveMQ for their low latency MOM messaging</a> </p></td></tr><tr><td colspan="1" rowspan="1"><p>Peter Brooke</p></td><td colspan="1" rowspan="1"><p>RomTrac</p></td><td colspan="1" rowspan="1"><p>We are using ActiveMQ and Camel to provider high performance load balancing of requests across a cluster of servers</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sridhar Komandur</p></td><td colspan="1" rowspan="1"><p>University of Washington (UW Tech)</p></td><td colspan="1" rowspan="1"><p>ActiveMQ is being used as backend messaging layer for a variety of distributed applications withing UW</p></td></tr><tr><td colspan="1" rowspan="1"><p>Gareth Davies</p></td><td colspan="1" rowspan="1"><p>Daugherty Systems</p></td><td colspan="1" rowspan="1"><p>At current client (global agribusiness firm), using ActiveMQ for asynchronous, reliable messaging within in-house SOA application</p></td></tr><tr><td colspan="1" rowspan="1"><p>Raffe G.</p></td><td colspan="1" rowspan="1"><p>Document archiving/flow systems</p></td><td colspan="1" rowspan="1"><p>We try to use ActiveMQ as connectivity option between our FrontEnd (FE) and BackEnd (BE). FE receives requests which processing is normally heavy time-consuming. Thus FE creates a message which is sent to BE for processing and returns a ticket (correlationID) to the user. This will later use the ticket to ask for the response of the processing (again sending a message from FE to BE which will respond synchronously in this case). So we want to have reliable messaging between our FE and BE.<br clear="none">
+So far this is not entirely working for us.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Tom L.</p></td><td colspan="1" rowspan="1"><p>Promotional Marketing</p></td><td colspan="1" rowspan="1"><p>Here is our flow. The backend systems (written in a propriatery language) send requests to a tomcat server via http. The message servlet from the ActiveMQ's web API connects to an embeded broker instance using the VM connector and places the request on the queue. We don't have a need for clustering yet, but we are planning on using either tomcat's clustering or ActiveCluster if it becomes necessary (since the brokers are embeded anyways). </p></td></tr><tr><td colspan="1" rowspan="1"><p>Aleksi Kallio</p></td><td colspan="1" rowspan="1"><p>CSC, the Finnish IT center for science</p></td><td colspan="1" rowspan="1"><p>We are building a bioinformatics system for DNA-microarray data storage and analysis. System contains rich graphical clients, a large database and heavy server machinery for processing analysis jobs. We are trying to use ActiveMQ as a JMS implementation to shuttle data between the servers and clients in an event based manner.</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="mailto:frik@gatherworks.com">Frik Strecker</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.gatherplace.net">GatherPlace</a> provides cost-effective remote application sharing </p></td><td colspan="1" rowspan="1"><p>ActiveMQ is used to collect real-time billing and usage information from servers distributed throughout the world. Free accounts are available to active ActiveMQ developers for ActiveMQ purposes. </p></td></tr><tr><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://code.google.com/p/golconde/">Golconde</a> </p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p> Uses ActiveMQ to implement a distributed Postgresql replication system </p></td></tr><tr><td colspan="1" rowspan="1"><p> <a shape="rect" href="http://www.oreillynet.com/pub/au/3212">Robert Liguori</a> </p></td><td colspan="1" rowspan="1"><p> STG Technologies, Inc.</p></td><td colspan="1" rowspan="1"><p> Uses ActiveMQ in support of the aviation industry.</p></td></tr></tbody></table>
+</div>
diff --git a/using-activemq-5.xml b/using-activemq-5.xml
index 3fc9807..247dc2f 100644
--- a/using-activemq-5.xml
+++ b/using-activemq-5.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><h2 id="UsingActiveMQ5-UsingApacheActiveMQ">Using Apache ActiveMQ</h2>
+<div class="wiki-content maincontent"><h2>Using Apache ActiveMQ</h2>
-<p>To help you get started using Apache ActiveMQ version 5 you may wish to start off with the <a shape="rect" href="version-5-getting-started.xml">Version 5 Getting Started</a> guide or the <a shape="rect" href="configuring-version-5-transports.xml">Configuring version 5 Transports</a>. Otherwise here is a complete list of the guides.</p>
+<p>To help you get started using Apache ActiveMQ version 5 you may wish to start off with the <link><page ri:content-title="Version 5 Getting Started"></page></link> guide or the <link><page ri:content-title="Configuring version 5 Transports"></page></link>. Otherwise here is a complete list of the guides.</p>
-<ul class="childpages-macro"><li><a shape="rect" href="configure-version-5-brokers.xml">Configure version 5 Brokers</a></li><li><a shape="rect" href="configuring-version-5-transports.xml">Configuring Version 5 Transports</a></li><li><a shape="rect" href="ldap-broker-discovery-mechanism.xml">LDAP Broker Discovery Mechanism</a></li><li><a shape="rect" href="version-5-examples.xml">Version 5 Examples</a></li><li><a shape="rect" href="version-5-getting-started.xml">Version 5 Getting Started</a></li><li><a shape="rect" href="version-5-hello-world.xml">Version 5 Hello World</a></li><li><a shape="rect" href="version-5-initial-configuration.xml">Version 5 Initial Configuration</a></li><li><a shape="rect" href="version-5-installation.xml">Version 5 Installation</a></li><li><a shape="rect" href="version-5-performance-tuning.xml">Version 5 Performance Tuning</a></li><li><a shape="rect" href="version-5-run-broker.xml">Version 5 Run Broker</a></li><li><a shape="rect" href="version-5-topologies.xml">Version 5 Topologies</a></li><li><a shape="rect" href="version-5-web-samples.xml">Version 5 Web Samples</a></li><li><a shape="rect" href="version-5-xml-configuration.xml">Version 5 XML Configuration</a></li></ul>
+<structured-macro ac:macro-id="b9c58b39-30e2-4e24-b6a4-21ea6082c45d" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro>
-<h3 id="UsingActiveMQ5-CommercialDocumentation">Commercial Documentation</h3>
+<h3>Commercial Documentation</h3>
-<p>The Commercial Providers listed on the <a shape="rect" href="support.xml">Support</a> page may also have additional documentation, examples, tutorials, etc... that can help you get started using ActiveMQ.</p></div>
+<p>The Commercial Providers listed on the <link><page ri:content-title="Support"></page></link> page may also have additional documentation, examples, tutorials, etc... that can help you get started using ActiveMQ.</p></div>
diff --git a/using-activemq.xml b/using-activemq.xml
index 6961cb1..ec67319 100644
--- a/using-activemq.xml
+++ b/using-activemq.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="UsingActiveMQ-UsingApacheActiveMQ">Using Apache ActiveMQ</h2><p>To help you get started using Apache ActiveMQ you may wish to start off with the <a shape="rect" href="getting-started.xml">Getting Started</a> guide or the <a shape="rect" href="configuring-transports.xml">Configuring Transports</a>. Otherwise here is a complete list of the guides.</p><p></p><ul class="childpages-macro"><li><a shape="rect" href="configuring-brokers.xml">Configuring Brokers</a></li><li><a shape="rect" href="configuring-transports.xml">Configuring Transports</a><ul class="childpages-macro"><li><a shape="rect" href="activemq-connection-uris.xml">ActiveMQ Connection URIs</a><ul class="childpages-macro"><li><a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a><ul class="childpages-macro"><li><a shape="rect" href="broker-properties-uri.xml">Broker Properties URI</a></li><li><a shape="rect" href="broker-uri.xml">Broker URI</a></li><li><a shape="rect" href="broker-xbean-uri.xml">Broker XBean URI</a></li></ul></li><li><a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a></li><li><a shape="rect" href="connection-configuration-uri.xml">Connection Configuration URI</a></li><li><a shape="rect" href="discovery-transport-reference.xml">Discovery Transport Reference</a></li><li><a shape="rect" href="failover-transport-reference.xml">Failover Transport Reference</a></li><li><a shape="rect" href="fanout-transport-reference.xml">Fanout Transport Reference</a></li><li><a shape="rect" href="http-and-https-transports-reference.xml">HTTP and HTTPs Transports Reference</a></li><li><a shape="rect" href="multicast-transport-reference.xml">Multicast Transport Reference</a></li><li><a shape="rect" href="nio-transport-reference.xml">NIO Transport Reference</a></li><li><a shape="rect" href="peer-transport-reference.xml">Peer Transport Reference</a></li><li><a shape="rect" href="ssl-transport-reference.xml">SSL Transport Reference</a></li><li><a shape="rect" href="static-transport-reference.xml">Static Transport Reference</a></li><li><a shape="rect" href="tcp-transport-reference.xml">TCP Transport Reference</a></li><li><a shape="rect" href="udp-transport-reference.xml">UDP Transport Reference</a></li><li><a shape="rect" href="vm-transport-reference.xml">VM Transport Reference</a></li></ul></li><li><a shape="rect" href="activemq-inactivitymonitor.xml">ActiveMQ InactivityMonitor</a></li><li><a shape="rect" href="zeroconf-transport-reference.xml">ZeroConf Transport Reference</a><ul class="childpages-macro"><li><a shape="rect" href="zeroconf.xml">ZeroConf</a></li></ul></li></ul></li><li><a shape="rect" href="examples.xml">Examples</a></li><li><a shape="rect" href="getting-started.xml">Getting Started</a><ul class="childpages-macro"><li><a shape="rect" href="monitoring-activemq.xml">Monitoring ActiveMQ</a></li></ul></li><li><a shape="rect" href="hello-world.xml">Hello World</a></li><li><a shape="rect" href="initial-configuration.xml">Initial Configuration</a></li><li><a shape="rect" href="installation.xml">Installation</a></li><li><a shape="rect" href="known-bad-os-and-jvm-combinations.xml">Known Bad OS and JVM Combinations</a></li><li><a shape="rect" href="performance-tuning.xml">Performance Tuning</a></li><li><a shape="rect" href="run-broker.xml">Run Broker</a></li><li><a shape="rect" href="topologies.xml">Topologies</a></li><li><a shape="rect" href="use-cases.xml">Use Cases</a></li><li><a shape="rect" href="user-submitted-configurations.xml">User Submitted Configurations</a><ul class="childpages-macro"><li><a shape="rect" href="complex-single-broker-configuration-stomp-only.xml">Complex Single Broker Configuration (STOMP only)</a></li><li><a shape="rect" href="jms-and-jdbc-operations-in-one-transaction.xml">JMS and JDBC operations in one transaction</a></li><li><a shape="rect" href="jms-bridge-with-local-broker.xml">JMS Bridge With Local Broker</a></li><li><a shape="rect" href="jms-bridge-with-oracle-aq.xml">JMS Bridge With Oracle AQ</a></li><li><a shape="rect" href="jms-bridge-with-remote-broker.xml">JMS Bridge With Remote Broker</a></li><li><a shape="rect" href="jms-bridge-with-remote-tibco-broker.xml">JMS Bridge With Remote TIBCO Broker</a></li><li><a shape="rect" href="sample-camel-routes.xml">Sample Camel Routes</a></li></ul></li><li><a shape="rect" href="web-samples.xml">Web Samples</a></li><li><a shape="rect" href="xml-configuration.xml">Xml Configuration</a></li><li><a shape="rect" href="xml-reference.xml">Xml Reference</a><ul class="childpages-macro"><li><a shape="rect" href="xbean-xml-reference-41.xml">XBean XML Reference 4.1</a></li><li><a shape="rect" href="xbean-xml-reference-50.xml">XBean XML Reference 5.0</a></li></ul></li></ul></div>
+<div class="wiki-content maincontent"><h2>Using Apache ActiveMQ</h2><p>To help you get started using Apache ActiveMQ you may wish to start off with the <link><page ri:content-title="Getting Started"></page></link> guide or the <link><page ri:content-title="Configuring Transports"></page></link>. Otherwise here is a complete list of the guides.</p><p><structured-macro ac:macro-id="bf1b3811-ddef-4e14-a1d0-cbe3b84aa696" ac:name="children" ac:schema-version="1"><parameter ac:name="depth">4</parameter></structured-macro></p></div>
diff --git a/using-apache-activemq.xml b/using-apache-activemq.xml
index ee47ad3..a78aa17 100644
--- a/using-apache-activemq.xml
+++ b/using-apache-activemq.xml
@@ -1,4 +1,4 @@
<div class="wiki-content maincontent"><p>Questions on using Apache ActiveMQ</p>
-<ul class="childpages-macro"><li><a shape="rect" href="activemq-command-line-tools-reference.xml">ActiveMQ Command Line Tools Reference</a></li><li><a shape="rect" href="are-destinations-case-sensitive.xml">Are destinations case sensitive</a></li><li><a shape="rect" href="can-i-send-really-large-files-over-activemq.xml">Can I send really large files over ActiveMQ</a></li><li><a shape="rect" href="can-i-use-activemq-5x-or-later-on-java-14.xml">Can I use ActiveMQ 5.x or later on Java 1.4</a></li><li><a shape="rect" href="can-two-brokers-share-the-same-database.xml">Can two brokers share the same database</a></li><li><a shape="rect" href="does-activemq-support-clustering.xml">Does ActiveMQ support clustering</a></li><li><a shape="rect" href="how-can-i-avoid-serialization-of-objects-in-objectmessage.xml">How can I avoid serialization of Objects in ObjectMessage</a></li><li><a shape="rect" href="how-can-i-get-a-list-of-the-topics-and-queues-in-a-broker.xml">How can I get a list of the topics and queues in a broker</a></li><li><a shape="rect" href="how-can-i-make-activemq-faster.xml">How can I make ActiveMQ faster</a></li><li><a shape="rect" href="how-can-i-monitor-activemq.xml">How can I monitor ActiveMQ</a></li><li><a shape="rect" href="how-can-i-monitor-the-connection-with-the-broker.xml">How can I monitor the connection with the broker</a></li><li><a shape="rect" href="how-can-i-see-what-destinations-are-used.xml">How can I see what destinations are used</a></li><li><a shape="rect" href="how-can-i-support-auto-reconnection.xml">How can I support auto reconnection</a></li><li><a shape="rect" href="how-can-i-support-priority-queues.xml">How can I support priority queues</a></li><li><a shape="rect" href="how-can-i-use-different-network-protocols.xml">How can I use different network protocols</a></li><li><a shape="rect" href="how-do-distributed-queues-work.xml">How do distributed queues work</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-c.xml">How do I access ActiveMQ from C</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-csharp-or-dotnet.xml">How do I access ActiveMQ from CSharp or dotNet</a></li><li><a shape="rect" href="how-do-i-access-activemq-from-ruby-perl-python-php.xml">How do I access ActiveMQ from Ruby, Perl, Python, PHP</a></li><li><a shape="rect" href="how-do-i-bridge-different-jms-providers.xml">How do I bridge different JMS providers</a></li><li><a shape="rect" href="how-do-i-change-dispatch-policy.xml">How do I change dispatch policy</a></li><li><a shape="rect" href="how-do-i-change-the-logging.xml">How do I change the logging</a></li><li><a shape="rect" href="how-do-i-connect-to-one-of-a-number-of-message-brokers.xml">How do I connect to one of a number of message brokers</a></li><li><a shape="rect" href="how-do-i-create-new-destinations.xml">How do I create new destinations</a></li><li><a shape="rect" href="how-do-i-delete-a-destination.xml">How do I delete a destination</a></li><li><a shape="rect" href="how-do-i-disable-logging.xml">How do I disable logging</a></li><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li><li><a shape="rect" href="how-do-i-enable-asynchronous-sending.xml">How do I enable asynchronous sending</a></li><li><a shape="rect" href="how-do-i-enable-debug-logging.xml">How do I enable debug logging</a></li><li><a shape="rect" href="how-do-i-find-the-size-of-a-queue.xml">How do I find the Size of a Queue</a></li><li><a shape="rect" href="how-do-i-preserve-order-of-messages.xml">How do I preserve order of messages</a></li><li><a shape="rect" href="how-do-i-purge-a-queue.xml">How do I purge a queue</a></li><li><a shape="rect" href="how-do-i-restart-embedded-broker.xml">How do I restart embedded broker</a></li><li><a shape="rect" href="how-do-i-restrict-connections-from-creating-new-queues-or-topics.xml">How do I restrict connections from creating new queues or topics</a></li><li><a shape="rect" href="how-do-i-run-a-broker.xml">How do I run a broker</a></li><li><a shape="rect" href="how-do-i-set-the-message-expiration.xml">How do I set the message expiration</a></li><li><a shape="rect" href="how-do-i-turn-off-creating-an-embedded-activemq-broker-when-using-the-vm-transport.xml">How do I turn off creating an embedded ActiveMQ broker when using the VM transport</a></li><li><a shape="rect" href="how-do-i-unack-the-message-with-stomp.xml">How do I unack the message with Stomp</a></li><li><a shape="rect" href="how-do-i-use-activemq-using-in-jvm-messaging.xml">How do I use ActiveMQ using in JVM messaging</a></li><li><a shape="rect" href="how-do-i-use-durable-subscribers-in-a-network-of-brokers.xml">How do I use durable subscribers in a network of brokers</a></li><li><a shape="rect" href="how-do-i-use-ivy-with-activemq.xml">How do I use Ivy with ActiveMQ</a></li><li><a shape="rect" href="how-do-i-use-log4j-jms-appender-with-activemq.xml">How do I use log4j JMS appender with ActiveMQ</a></li><li><a shape="rect" href="how-do-i-use-ssl.xml">How do I use SSL</a></li><li><a shape="rect" href="how-do-message-groups-compare-to-selectors.xml">How do Message Groups compare to Selectors</a></li><li><a shape="rect" href="how-do-multiple-transports-work.xml">How do multiple transports work</a></li><li><a shape="rect" href="how-do-transactions-work.xml">How Do Transactions Work</a></li><li><a shape="rect" href="how-lightweight-is-sending-a-message.xml">How lightweight is sending a message</a></li><li><a shape="rect" href="how-should-i-package-applications-using-camel-and-activemq.xml">How should I package applications using Camel and ActiveMQ</a></li><li><a shape="rect" href="how-should-i-use-the-vm-transport.xml">How should I use the VM transport</a></li><li><a shape="rect" href="how-to-deal-with-large-number-of-threads-in-clients.xml">How to deal with large number of threads in clients</a></li><li><a shape="rect" href="how-to-disable-auto-destination-creation.xml">How to disable auto destination creation</a></li><li><a shape="rect" href="i-see-nc-client-ids-what-does-that-mean.xml">I see NC_ client-ids, what does that mean</a></li><li><a shape="rect" href="should-i-deploy-enterprise-integration-patterns-in-the-broker-or-another-application.xml">Should I deploy Enterprise Integration Patterns in the broker or another application</a></li><li><a shape="rect" href="should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml">Should I deploy the broker inside my JVM or AppServer</a></li><li><a shape="rect" href="what-are-those-topics-activemqadvisory.xml">What are those topics ActiveMQ.Advisory</a></li><li><a shape="rect" href="what-happens-with-a-fast-producer-and-slow-consumer.xml">What happens with a fast producer and slow consumer</a></li><li><a shape="rect" href="what-is-the-difference-between-a-virtual-topic-and-a-composite-destination.xml">What is the difference between a Virtual Topic and a Composite Destination</a></li><li><a shape="rect" href="what-is-the-difference-between-discovery-multicast-and-zeroconf.xml">What is the difference between discovery, multicast and zeroconf</a></li><li><a shape="rect" href="what-is-the-prefetch-limit-for.xml">What is the Prefetch Limit For?</a></li><li><a shape="rect" href="while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.xml">While posting large binary file to activeMQ, is there a way to measure its progress</a></li></ul></div>
+<structured-macro ac:macro-id="8031138a-2bf4-4b94-b175-23a5c0d8558b" ac:name="children" ac:schema-version="1"><parameter ac:name="all">true</parameter></structured-macro></div>
diff --git a/verify-downloads.xml b/verify-downloads.xml
index ba5619d..f80d0a2 100644
--- a/verify-downloads.xml
+++ b/verify-downloads.xml
@@ -1,14 +1,8 @@
-<div class="wiki-content maincontent"><h2 id="VerifyDownloads-VerifytheIntegrityofDownloads">Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" class="external-link" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgpk -a KEYS
+<div class="wiki-content maincontent"><h2>Verify the Integrity of Downloads</h2><p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:</p><ol><li>Download the <a shape="rect" href="http://www.apache.org/dist/activemq/KEYS">KEYS</a></li><li>Download the asc signature file for the relevant distribution</li><li><p>Verify the signatures using the following commands, depending on your use of PGP or GPG:</p><structured-macro ac:macro-id="065276bc-7d41-4281-8c9d-900abae49b20" ac:name="code" ac:schema-version="1"><plain-text-body>$ pgpk -a KEYS
$ pgpv apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ pgp -ka KEYS
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="eaac57d8-c52b-44a4-8073-18811863ebe3" ac:name="code" ac:schema-version="1"><plain-text-body>$ pgp -ka KEYS
$ pgp apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[$ gpg --import KEYS
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="d4140fb0-aad3-4b64-a603-f33fadb99dd4" ac:name="code" ac:schema-version="1"><plain-text-body>$ gpg --import KEYS
$ gpg --verify apache-activemq-<version>-bin.tar.gz.asc
-]]></script>
-</div></div></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" class="external-link" href="http://www.gnu.org/software/textutils/textutils.html" rel="nofollow">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" class="external-link" href="http://www.fourmilab.ch/md5/" rel="nofollow">md5</a></li><li><a shape="rect" class="external-link" href="http://www.pc-tools.net/win32/md5sums/" rel="nofollow">md5sums</a></li><li><a shape="rect" class="external-link" href="http://www.slavasoft.com/fsum/" rel="nofollow">SlavaSoft FSUM</a></li></ul></div>
+</plain-text-body></structured-macro></li></ol><p>(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).</p><p>Alternatively, you can verify the MD5 signature on the files. A Unix program called <code>md5</code> or <code>md5sum</code> is included in most Linux and Unix distributions. It is also available as part of <a shape="rect" href="http://www.gnu.org/software/textutils/textutils.html">GNU Textutils</a>. Windows users can utilize any of the following md5 programs:</p><ul><li><a shape="rect" href="http://www.fourmilab.ch/md5/">md5</a></li><li><a shape="rect" href="http://www.pc-tools.net/win32/md5sums/">md5sums</a></li><li><a shape="rect" href="http://www.slavasoft.com/fsum/">SlavaSoft FSUM</a></li></ul></div>
diff --git a/version-5-examples.xml b/version-5-examples.xml
index 1d39f38..b343155 100644
--- a/version-5-examples.xml
+++ b/version-5-examples.xml
@@ -1,34 +1,12 @@
-<div class="wiki-content maincontent"><p>Since version<strong> 5.12.0</strong>, Apache ActiveMQ comes with the new tool that can be used to produce and consume messages from the broker.</p><h2 id="Version5Examples-Prerequisites"><span style="color: rgb(34,34,34);">Prerequisites</span></h2><p><span style="color: rgb(34,34,34);"> </span></p><p>Before running the examples you should try <a shape="rect" href="run-broker.xml">running a JMS broker</a> on your machine. Follow the <a shape="rect" href="installation.xml">Installation</a> instructions to use a binary distribution of ActiveMQ. To run the broker in a command shell, type:</p><p><span style="color: rgb(34,34,34);"> </span></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console
-]]></script>
-</div></div><p><span style="color: rgb(34,34,34);"> </span></p><p>This starts up ActiveMQ.</p><h2 id="Version5Examples-Running">Running</h2><p>From the<a shape="rect" href="unix-shell-script.xml"> command line</a> you can run</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[${ACTIVEMQ_HOME}/bin/activemq producer
-${ACTIVEMQ_HOME}/bin/activemq consumer]]></script>
-</div></div><p> </p><p>If you have <code>activemq-all</code> jar available you can achieve the same with</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[java -jar activemq-all-5.x.x.jar producer
-java -jar activemq-all-5.x.x.jar consumer]]></script>
-</div></div><p>If you run inside <a shape="rect" href="osgi-integration.xml">Karaf</a>, you can run the commands as</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[activemq:producer
-activemq:consumer]]></script>
-</div></div><p> </p><h2 id="Version5Examples-Options">Options</h2><p>For all options on the commands, run them with <code>--help</code> parameter. The up to date, options for <a shape="rect" class="external-link" href="https://github.com/apache/activemq/blob/master/activemq-console/src/main/resources/org/apache/activemq/console/command/producer.txt" rel="nofollow">producer</a> and <a shape="rect" class="external-link" href="https://github.com/apache/activemq/blob/master/activemq-console/src/main/resources/org/apache/activemq/console/command/consumer.txt" rel="nofollow">consumer</a> can be found in the source.</p><h2 id="Version5Examples-Examples">Examples</h2><p>Here are a couple of examples of more advanced features.</p><p>To send a text message with custom text use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq producer --message "My message" --messageCount 1
-]]></script>
-</div></div><p>To send byte message of custom length use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq producer --messageSize 100 --messageCount 1
-]]></script>
-</div></div><p>To send a text message with content obtained from an url</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq producer --payloadUrl http://activemq.apache.org/schema/core/activemq-core.xsd --messageCount 1]]></script>
-</div></div><p>To consume in transaction use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq consumer --transacted true
-]]></script>
-</div></div><p>To use client acknowledgment use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq consumer --ackMode CLIENT_ACKNOWLEDGE
-]]></script>
-</div></div><p>To use durable topic subscribers use</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq consumer --durable true --clientId example --destination topic://TEST
-]]></script>
-</div></div><h2 id="Version5Examples-Oldexamples">Old examples</h2><p>In older versions of ActiveMQ, the corresponding examples were located in <code>examples/</code> or <code>examples/openwire/swissarmy/</code> directories, where you can do the similar tasks with an ant script.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ant producer
-ant consumer]]></script>
-</div></div><h2 id="Version5Examples-Otherexamples">Other examples</h2><p>In <code>examples/</code> directory (depending on the version) you can find more examples of using the broker with variety of protocols (mqtt, amqp, ...) and clients (Java, Ruby, JavaScript, ...), so it's the good place to start learning. Also, <code>examples/conf/</code> directory contains a lot of different configuration examples that you can use as a starting point for your deployment.</p><h2 id="Version5Examples-SeeAlso">See Also</h2><ul><li><a shape="rect" href="web-samples.xml">Web Samples</a></li><li><a shape="rect" href="web-console.xml">Web Console</a></li><li><a shape="rect" href="jmx.xml">JMX</a></li></ul></div>
+<div class="wiki-content maincontent"><p>Since version<strong> 5.12.0</strong>, Apache ActiveMQ comes with the new tool that can be used to produce and consume messages from the broker.</p><h2><span style="color: rgb(34,34,34);">Prerequisites</span></h2><p><span style="color: rgb(34,34,34);"> </span></p><p>Before running the examples you should try <link><page ri:content-title="Run Broker"></page><plain-text-link-body>running a JMS broker</plain-text-link-body></link> on your machine. Follow the <link><page ri:content-title="Installation"></page></link> instructions to use a binary distribution of ActiveMQ. To run the broker in a command shell, type:</p><p><span style="color: rgb(34,34,34);"> </span></p><structured-macro ac:macro-id="321061e7-6bae-43a1-a1c4-9e39a20e6875" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq console
+</plain-text-body></structured-macro><p><span style="color: rgb(34,34,34);"> </span></p><p>This starts up ActiveMQ.</p><h2>Running</h2><p>From the<link><page ri:content-title="Unix Shell Script"></page><plain-text-link-body> command line</plain-text-link-body></link> you can run</p><structured-macro ac:macro-id="9211f762-fd59-4fd5-9945-2b7d93fba9fc" ac:name="code" ac:schema-version="1"><plain-text-body>${ACTIVEMQ_HOME}/bin/activemq producer
+${ACTIVEMQ_HOME}/bin/activemq consumer</plain-text-body></structured-macro><p> </p><p>If you have <code>activemq-all</code> jar available you can achieve the same with</p><structured-macro ac:macro-id="577cd72e-bbbc-41eb-9e56-664eaae2d9d7" ac:name="code" ac:schema-version="1"><plain-text-body>java -jar activemq-all-5.x.x.jar producer
+java -jar activemq-all-5.x.x.jar consumer</plain-text-body></structured-macro><p>If you run inside <link><page ri:content-title="OSGi Integration"></page><plain-text-link-body>Karaf</plain-text-link-body></link>, you can run the commands as</p><structured-macro ac:macro-id="584a446b-b8a5-457d-94cb-ab234c40cbe9" ac:name="code" ac:schema-version="1"><plain-text-body>activemq:producer
+activemq:consumer</plain-text-body></structured-macro><p> </p><h2>Options</h2><p>For all options on the commands, run them with <code>--help</code> parameter. The up to date, options for <a shape="rect" href="https://github.com/apache/activemq/blob/master/activemq-console/src/main/resources/org/apache/activemq/console/command/producer.txt">producer</a> and <a shape="rect" href="https://github.com/apache/activemq/blob/master/activemq-console/src/main/resources/org/apache/activemq/console/command/consumer.txt">consumer</a> can be found in the source.</p><h2>Examples</h2><p>Here are a couple of examples of more advanced features.</p><p>To send a text message with custom text use</p><structured-macro ac:macro-id="d7494493-d755-4a0f-ae85-8a372728511c" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq producer --message "My message" --messageCount 1
+</plain-text-body></structured-macro><p>To send byte message of custom length use</p><structured-macro ac:macro-id="48aaea5a-bb54-4305-acc9-b6dbfe86f6c6" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq producer --messageSize 100 --messageCount 1
+</plain-text-body></structured-macro><p>To send a text message with content obtained from an url</p><structured-macro ac:macro-id="83497bb2-e595-4dcf-bcd5-94013a04d173" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq producer --payloadUrl http://activemq.apache.org/schema/core/activemq-core.xsd --messageCount 1</plain-text-body></structured-macro><p>To consume in transaction use</p><structured-macro ac:macro-id="3e42e2a9-0ea5-4c9d-bc31-ba8693d8e538" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq consumer --transacted true
+</plain-text-body></structured-macro><p>To use client acknowledgment use</p><structured-macro ac:macro-id="1fa0d8d2-d7a9-4a83-94e4-a2a3a44b8fc9" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq consumer --ackMode CLIENT_ACKNOWLEDGE
+</plain-text-body></structured-macro><p>To use durable topic subscribers use</p><structured-macro ac:macro-id="18291517-9115-45eb-9846-13b82c06070b" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq consumer --durable true --clientId example --destination topic://TEST
+</plain-text-body></structured-macro><h2>Old examples</h2><p>In older versions of ActiveMQ, the corresponding examples were located in <code>examples/</code> or <code>examples/openwire/swissarmy/</code> directories, where you can do the similar tasks with an ant script.</p><structured-macro ac:macro-id="155e534a-74c1-4258-8ea9-f5631997a987" ac:name="code" ac:schema-version="1"><plain-text-body>ant producer
+ant consumer</plain-text-body></structured-macro><h2>Other examples</h2><p>In <code>examples/</code> directory (depending on the version) you can find more examples of using the broker with variety of protocols (mqtt, amqp, ...) and clients (Java, Ruby, JavaScript, ...), so it's the good place to start learning. Also, <code>examples/conf/</code> directory contains a lot of different configuration examples that you can use as a starting point for your deployment.</p><h2>See Also</h2><ul><li><link><page ri:content-title="Web Samples"></page></link></li><li><link><page ri:content-title="Web Console"></page></link></li><li><link><page ri:content-title="JMX"></page></link></li></ul></div>
diff --git a/version-5-getting-started.xml b/version-5-getting-started.xml
index c06e6c6..d023607 100644
--- a/version-5-getting-started.xml
+++ b/version-5-getting-started.xml
@@ -1,117 +1,51 @@
-<div class="wiki-content maincontent"><h2 id="Version5GettingStarted-Introduction">Introduction</h2><p>This document describes how to install and configure ActiveMQ for both Unix and Windows' platforms.</p><h2 id="Version5GettingStarted-DocumentOrganization">Document Organization</h2><p>The Getting Started Guide for ActiveMQ contains the following sections:</p><p></p><div class="toc-macro client-side-toc-macro" data-headerelements="H1,H2,H3,H4,H5,H6,H7"></div><h2 id="Version5GettingStarted-Pre-InstallationRequirements">Pre-Installation Requirements</h2><p><strong>Hardware:</strong></p><ul><li>60 MB of free disk space for the ActiveMQ binary distribution.</li><li>200 MB of free disk space for the ActiveMQ source or developer's distributions.</li></ul><p><strong>Operating Systems:</strong></p><ul><li>Windows: Windows XP SP2, Windows 2000.</li><li>Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, or any Unix platform that supports Java.</li></ul><p><strong>Environment:</strong></p><ul><li>Java Developer Kit (JDK) 1.7.x or greater for deployment and 1.7.x (Java 7) for compiling/building.</li><li>The JAVA_HOME environment variable must be set to the directory where the JDK is installed, e.g., <code>c:\Program Files\jdk.1.7.0_xx_xx</code>.</li><li>Maven 3.0 or greater (required when installing source or developer's releases).</li><li><a shape="rect" class="external-link" href="http://cvs.apache.org/repository/geronimo-spec/jars/">JARs</a> that will be used must be added to the classpath.</li></ul><h2 id="Version5GettingStarted-InstallationProcedureforWindows">Installation Procedure for Windows</h2><p>This section of the Getting Started Guide explains how to install binary and source distributions of ActiveMQ on a Windows system.</p><h4 id="Version5GettingStarted-WindowsBinaryInstallation">Windows Binary Installation</h4><p>This procedure explains how to download and install the binary distribution on a Windows system.</p><ol><li>From a browser, navigate to <a shape="rect" class="external-link" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <a shape="rect" href="download.xml">Download</a> link in the navigation pane (the left pane).</li><li>Select the latest distribution (for older releases, click the link to the archives).<br clear="none"> For a binary distribution, the filename will be similar to: <code>activemq-x.x.x.zip</code>.</li><li>Extract the files from the ZIP file into a directory of your choice.</li><li>Proceed to the <a shape="rect" href="#Version5GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.</li><li>Following start-up, go to the <a shape="rect" href="#Version5GettingStarted-TestingtheInstallation">#Testing the Installation</a> section of this document.</li></ol><h4 id="Version5GettingStarted-WindowsSourceInstallation">Windows Source Installation</h4><p>This procedure explains how to download and install the source distribution on a Windows system.</p><p><strong>NOTE:</strong> ActiveMQ requires Java 7 to run and to build</p><ol><li>From a browser, navigate to <a shape="rect" class="external-link" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <a shape="rect" href="download.xml">Download</a> link in the navigation pane (the left pane).</li><li>Select the latest distribution (for older releases, click the link to the archives).<br clear="none"> For a source distribution, the filename will be similar to: <code>activemq-x.x-src.zip</code>.</li><li>Extract ActiveMQ from the ZIP file into a directory of your choice.</li><li><span class="confluence-anchor-link" id="Version5GettingStarted-WindowsSourceInstallation"></span> Build ActiveMQ using Maven 2.1 or greater and Java 1.7.</li></ol><p>The recommended method of building ActiveMQ is the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
+<div class="wiki-content maincontent"><h2>Introduction</h2><p>This document describes how to install and configure ActiveMQ for both Unix and Windows' platforms.</p><h2>Document Organization</h2><p>The Getting Started Guide for ActiveMQ contains the following sections:</p><p><structured-macro ac:macro-id="52e79b57-99db-4067-abdb-fb12a26a6bb6" ac:name="toc" ac:schema-version="1"></structured-macro></p><h2>Pre-Installation Requirements</h2><p><strong>Hardware:</strong></p><ul><li>60 MB of free disk space for the ActiveMQ binary distribution.</li><li>200 MB of free disk space for the ActiveMQ source or developer's distributions.</li></ul><p><strong>Operating Systems:</strong></p><ul><li>Windows: Windows XP SP2, Windows 2000.</li><li>Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, or any Unix platform that supports Java.</li></ul><p><strong>Environment:</strong></p><ul><li>Java Developer Kit (JDK) 1.7.x or greater for deployment and 1.7.x (Java 7) for compiling/building.</li><li>The JAVA_HOME environment variable must be set to the directory where the JDK is installed, e.g., <code>c:\Program Files\jdk.1.7.0_xx_xx</code>.</li><li>Maven 3.0 or greater (required when installing source or developer's releases).</li><li><a shape="rect" href="http://cvs.apache.org/repository/geronimo-spec/jars/">JARs</a> that will be used must be added to the classpath.</li></ul><h2>Installation Procedure for Windows</h2><p>This section of the Getting Started Guide explains how to install binary and source distributions of ActiveMQ on a Windows system.</p><h4>Windows Binary Installation</h4><p>This procedure explains how to download and install the binary distribution on a Windows system.</p><ol><li>From a browser, navigate to <a shape="rect" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <link><page ri:content-title="Download"></page></link> link in the navigation pane (the left pane).</li><li>Select the latest distribution (for older releases, click the link to the archives).<br clear="none"> For a binary distribution, the filename will be similar to: <code>activemq-x.x.x.zip</code>.</li><li>Extract the files from the ZIP file into a directory of your choice.</li><li>Proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.</li><li>Following start-up, go to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section of this document.</li></ol><h4>Windows Source Installation</h4><p>This procedure explains how to download and install the source distribution on a Windows system.</p><p><strong>NOTE:</strong> ActiveMQ requires Java 7 to run and to build</p><ol><li>From a browser, navigate to <a shape="rect" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <link><page ri:content-title="Download"></page></link> link in the navigation pane (the left pane).</li><li>Select the latest distribution (for older releases, click the link to the archives).<br clear="none"> For a source distribution, the filename will be similar to: <code>activemq-x.x-src.zip</code>.</li><li>Extract ActiveMQ from the ZIP file into a directory of your choice.</li><li><structured-macro ac:macro-id="1dda15a6-3602-4020-b23e-0ab8b70735fb" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Windows Source Installation</parameter></structured-macro> Build ActiveMQ using Maven 2.1 or greater and Java 1.7.</li></ol><p>The recommended method of building ActiveMQ is the following:</p><structured-macro ac:macro-id="f167e238-f992-4524-9a93-b1c045dc13fb" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
mvn clean install
-]]></script>
-</div></div><p>where [activemq_install_dir] is the directory in which ActiveMQ was installed.</p><p>If the above build fails on some tests, type the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
+</plain-text-body></structured-macro><p>where [activemq_install_dir] is the directory in which ActiveMQ was installed.</p><p>If the above build fails on some tests, type the following:</p><structured-macro ac:macro-id="01275fdd-4d6c-45f7-b862-0542a5a41f61" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
mvn clean install -Dmaven.test.skip=true
-]]></script>
-</div></div><ol><li><p>If you prefer to use an IDE, then you can auto-generate the IDE's project file using maven plugins:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn eclipse:eclipse
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn idea:idea
-]]></script>
-</div></div><p>Feel free to use any other applicable IDE. Please refer to the <a shape="rect" class="external-link" href="http://maven.apache.org/plugins/index.html">plugin reference</a> for more details.</p></li><li><p>Start ActiveMQ from the target directory, for example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]\assembly\target
+</plain-text-body></structured-macro><ol><li><p>If you prefer to use an IDE, then you can auto-generate the IDE's project file using maven plugins:</p><structured-macro ac:macro-id="de3083ba-136c-46b4-82f2-9a18adac7d6f" ac:name="code" ac:schema-version="1"><plain-text-body>mvn eclipse:eclipse
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="6312de16-1c00-4d56-84d4-b049fc17dbdc" ac:name="code" ac:schema-version="1"><plain-text-body>mvn idea:idea
+</plain-text-body></structured-macro><p>Feel free to use any other applicable IDE. Please refer to the <a shape="rect" href="http://maven.apache.org/plugins/index.html">plugin reference</a> for more details.</p></li><li><p>Start ActiveMQ from the target directory, for example:</p><structured-macro ac:macro-id="84062c52-4ed9-4da4-94e3-646bad83d165" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]\assembly\target
unzip activemq-x.x-SNAPSHOT.zip
cd activemq-x.x-SNAPSHOT
bin\activemq
-]]></script>
-</div></div><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create the working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p></li><li>Proceed to the <a shape="rect" href="#Version5GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you are building ActiveMQ 5.x under Windows using Cygwin there is a path name length limitation. If the path name length is exceeded, you may see build errors. To correct this, move the ActiveMQ source directory higher in the file system tree, e.g., /cygdrive/c/d/sm.</p></div></div><h4 id="Version5GettingStarted-WindowsDeveloper'sRelease">Windows Developer's Release</h4><p>This procedure explains how to download and install the latest developer's snapshot.</p><p><strong>NOTE:</strong> ActiveMQ requires Java 7 to run and to build</p><ol><li>From a browser, navigate to <a shape="rect" class="external-link" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <a shape="rect" href="download.xml">Download</a> link in the navigation pane (the left pane).</li><li>Click the Maven ActiveMQ SNAPSHOT link.</li><li>Select the version of ActiveMQ to download</li><li>Extract the files from the ZIP file into a directory of your choice.</li><li>If a binary snapshot was downloaded, proceed to the <a shape="rect" href="#Version5GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.<br clear="none"> If a source snapshot was downloaded, perform step 6 and step 7 of the <a shape="rect" href="#Version5GettingStarted-WindowsSourceInstallation">#Windows Source Installation</a> procedure.</li><li>Following start-up, proceed to the <a shape="rect" href="#Version5GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><h2 id="Version5GettingStarted-InstallationProcedureforUnix">Installation Procedure for Unix</h2><h4 id="Version5GettingStarted-UnixBinaryInstallationUnixBinaryInstallation"><span class="confluence-anchor-link" id="Version5GettingStarted-UnixBinaryInstallation"></span> Unix Binary Installation</h4><p>This procedure explains how to download and install the binary distribution on a Unix system.<br clear="none"> <strong>NOTE:</strong> There are several alternative ways to perform this type of installation.</p><ol><li><p>Download the activemq gzip file to the Unix machine, using either a browser or a tool, i.e., wget, scp, ftp, etc. for example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[> wget http://activemq.apache.org/path/tofile/apache-activemq-5.8-tar.gz
-]]></script>
-</div></div></li><li><p>Extract the files from the gzip file into a directory of your choice. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[> tar zxvf activemq-x.x.x.tar.gz
-]]></script>
-</div></div></li><li><p>If the <code>ActiveMQ</code> start-up script is not executable, change its permissions. The <code>ActiveMQ</code> script is located in the <code>bin</code> directory. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[> cd [activemq_install_dir]/bin
+</plain-text-body></structured-macro><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create the working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p></li><li>Proceed to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><structured-macro ac:macro-id="bc245d60-9eab-4e3a-bd20-72fd9d398cab" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>If you are building ActiveMQ 5.x under Windows using Cygwin there is a path name length limitation. If the path name length is exceeded, you may see build errors. To correct this, move the ActiveMQ source directory higher in the file system tree, e.g., /cygdrive/c/d/sm.</p></rich-text-body></structured-macro><h4>Windows Developer's Release</h4><p>This procedure explains how to download and install the latest developer's snapshot.</p><p><strong>NOTE:</strong> ActiveMQ requires Java 7 to run and to build</p><ol><li>From a browser, navigate to <a shape="rect" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <link><page ri:content-title="Download"></page></link> link in the navigation pane (the left pane).</li><li>Click the Maven ActiveMQ SNAPSHOT link.</li><li>Select the version of ActiveMQ to download</li><li>Extract the files from the ZIP file into a directory of your choice.</li><li>If a binary snapshot was downloaded, proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.<br clear="none"> If a source snapshot was downloaded, perform step 6 and step 7 of the <link ac:anchor="Windows Source Installation"><plain-text-link-body>#Windows Source Installation</plain-text-link-body></link> procedure.</li><li>Following start-up, proceed to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><h2>Installation Procedure for Unix</h2><h4><structured-macro ac:macro-id="3e673d86-a82d-4d40-ae1e-63c7156bb5fc" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Unix Binary Installation</parameter></structured-macro> Unix Binary Installation</h4><p>This procedure explains how to download and install the binary distribution on a Unix system.<br clear="none"> <strong>NOTE:</strong> There are several alternative ways to perform this type of installation.</p><ol><li><p>Download the activemq gzip file to the Unix machine, using either a browser or a tool, i.e., wget, scp, ftp, etc. for example:</p><structured-macro ac:macro-id="5f8ae6fe-ecf7-4088-b04b-6d9f35fb231c" ac:name="code" ac:schema-version="1"><plain-text-body>> wget http://activemq.apache.org/path/tofile/apache-activemq-5.8-tar.gz
+</plain-text-body></structured-macro></li><li><p>Extract the files from the gzip file into a directory of your choice. For example:</p><structured-macro ac:macro-id="0ba895a6-462c-42f0-842c-d15ad7f3e368" ac:name="code" ac:schema-version="1"><plain-text-body>> tar zxvf activemq-x.x.x.tar.gz
+</plain-text-body></structured-macro></li><li><p>If the <code>ActiveMQ</code> start-up script is not executable, change its permissions. The <code>ActiveMQ</code> script is located in the <code>bin</code> directory. For example:</p><structured-macro ac:macro-id="067f2740-6e65-4336-9433-ec216fc1ea81" ac:name="code" ac:schema-version="1"><plain-text-body>> cd [activemq_install_dir]/bin
> chmod 755 activemq
-]]></script>
-</div></div></li><li>Proceed to the <a shape="rect" href="#Version5GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.</li><li>Following start-up, go to the <a shape="rect" href="#Version5GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><h4 id="Version5GettingStarted-UnixSourceInstallation">Unix Source Installation</h4><p>This procedure explains how to download and install the source distribution on a Unix system. This procedure assumes the Unix machine has a browser. Please see the previous <a shape="rect" href="#Version5GettingStarted-UnixBinaryInstallation">#Unix Binary Installation</a> section for details on how to install ActiveMQ without a browser.</p><p><strong>NOTE:</strong> ActiveMQ requires Java 7 to run and to build</p><ol><li>From a browser, navigate to <a shape="rect" class="external-link" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <a shape="rect" href="download.xml">Download</a> link in the navigation pane (the left pane).</li><li>Click the Maven ActiveMQ SNAPSHOT link.</li><li>Select the version of ActiveMQ to download<br clear="none"> For a source distribution, the filename will be similar to: <code>activemq-x.x-src.tar.gz</code>.</li><li><p>Extract the files from the ZIP file into a directory of your choice. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tar zxvf activemq.x.x-src.tar.gz
-]]></script>
-</div></div></li><li><p>Build ActiveMQ using Maven 3.0 or greater and Java 7:<br clear="none"> The preferred method of building ActiveMQ is the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
+</plain-text-body></structured-macro></li><li>Proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.</li><li>Following start-up, go to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><h4>Unix Source Installation</h4><p>This procedure explains how to download and install the source distribution on a Unix system. This procedure assumes the Unix machine has a browser. Please see the previous <link ac:anchor="Unix Binary Installation"><plain-text-link-body>#Unix Binary Installation</plain-text-link-body></link> section for details on how to install ActiveMQ without a browser.</p><p><strong>NOTE:</strong> ActiveMQ requires Java 7 to run and to build</p><ol><li>From a browser, navigate to <a shape="rect" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <link><page ri:content-title="Download"></page></link> link in the navigation pane (the left pane).</li><li>Click the Maven ActiveMQ SNAPSHOT link.</li><li>Select the version of ActiveMQ to download<br clear="none"> For a source distribution, the filename will be similar to: <code>activemq-x.x-src.tar.gz</code>.</li><li><p>Extract the files from the ZIP file into a directory of your choice. For example:</p><structured-macro ac:macro-id="57a84e74-23f7-45cb-b75c-a9ff17fb2fa0" ac:name="code" ac:schema-version="1"><plain-text-body>tar zxvf activemq.x.x-src.tar.gz
+</plain-text-body></structured-macro></li><li><p>Build ActiveMQ using Maven 3.0 or greater and Java 7:<br clear="none"> The preferred method of building ActiveMQ is the following:</p><structured-macro ac:macro-id="535f9e3a-a5c1-467e-8983-0dcbcbd683a2" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
mvn clean install
-]]></script>
-</div></div><p>If Maven crashes with a java.lang.OutOfMemoryError, you you need to do this first (assuming a Bourne-like shell):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[export MAVEN_OPTS=-Xmx1024M
-]]></script>
-</div></div><p>If the above build fails on some tests, do the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
+</plain-text-body></structured-macro><p>If Maven crashes with a java.lang.OutOfMemoryError, you you need to do this first (assuming a Bourne-like shell):</p><structured-macro ac:macro-id="b8a2b546-2300-436e-953f-c6830a183828" ac:name="code" ac:schema-version="1"><plain-text-body>export MAVEN_OPTS=-Xmx1024M
+</plain-text-body></structured-macro><p>If the above build fails on some tests, do the following:</p><structured-macro ac:macro-id="e6fbfa5d-cf32-448c-9ac8-23f9441a57e3" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
mvn clean install -Dmaven.test.skip=true
-]]></script>
-</div></div><p>If you prefer to use an IDE then you can auto-generate the IDE's project file using maven plugins:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn eclipse:eclipse
-]]></script>
-</div></div><p>or</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn idea:idea
-]]></script>
-</div></div><p>Feel free to use any other applicable IDE. Please refer to the <a shape="rect" class="external-link" href="http://maven.apache.org/reference/plugins/plugins.html">plugin reference</a> for more details.<br clear="none"> <strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p></li><li>Proceed to the <a shape="rect" href="#Version5GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.</li><li>Proceed to <a shape="rect" href="#Version5GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><h4 id="Version5GettingStarted-UnixDeveloper'sRelease">Unix Developer's Release</h4><p>This procedure explains how to download and install the latest developer's snapshot.</p><p><strong>NOTE:</strong> ActiveMQ requires Java 7 to run and to build</p><ol><li>From a browser, navigate to <a shape="rect" class="external-link" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <a shape="rect" href="#Version5GettingStarted-Download">#Download</a> link in the navigation pane (the left pane).</li><li>Click the Maven ActiveMQ SNAPSHOT link.</li><li>Select the version of ActiveMQ to download</li><li><p>Extract the files from the gzip file into a directory of your choice. For example:<br clear="none"> For a binary developer's snapshot:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tar zxvf activemq-x.x.x.tar.gz
-]]></script>
-</div></div><p>For a source developer's snapshot:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tar zxvf activemq-x.x.x-src.tar.gz
-]]></script>
-</div></div></li><li><p>If a binary snapshot was downloaded, to make it executable, the <code>ActiveMQ</code> script may need its permissions changed:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]/bin
+</plain-text-body></structured-macro><p>If you prefer to use an IDE then you can auto-generate the IDE's project file using maven plugins:</p><structured-macro ac:macro-id="ee0ee40b-5be1-444b-9e8b-06f1879887a1" ac:name="code" ac:schema-version="1"><plain-text-body>mvn eclipse:eclipse
+</plain-text-body></structured-macro><p>or</p><structured-macro ac:macro-id="0ec34c1f-2d89-4852-8e23-e379ae7a9665" ac:name="code" ac:schema-version="1"><plain-text-body>mvn idea:idea
+</plain-text-body></structured-macro><p>Feel free to use any other applicable IDE. Please refer to the <a shape="rect" href="http://maven.apache.org/reference/plugins/plugins.html">plugin reference</a> for more details.<br clear="none"> <strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p></li><li>Proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.</li><li>Proceed to <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><h4>Unix Developer's Release</h4><p>This procedure explains how to download and install the latest developer's snapshot.</p><p><strong>NOTE:</strong> ActiveMQ requires Java 7 to run and to build</p><ol><li>From a browser, navigate to <a shape="rect" href="http://activemq.apache.org/">activemq.apache.org/</a>.</li><li>Click the <link ac:anchor="Download"><plain-text-link-body>#Download</plain-text-link-body></link> link in the navigation pane (the left pane).</li><li>Click the Maven ActiveMQ SNAPSHOT link.</li><li>Select the version of ActiveMQ to download</li><li><p>Extract the files from the gzip file into a directory of your choice. For example:<br clear="none"> For a binary developer's snapshot:</p><structured-macro ac:macro-id="0f2cce95-b6aa-4595-9836-c86f7e6ec9ef" ac:name="code" ac:schema-version="1"><plain-text-body>tar zxvf activemq-x.x.x.tar.gz
+</plain-text-body></structured-macro><p>For a source developer's snapshot:</p><structured-macro ac:macro-id="3a156489-8800-47d2-b800-6faac69846c9" ac:name="code" ac:schema-version="1"><plain-text-body>tar zxvf activemq-x.x.x-src.tar.gz
+</plain-text-body></structured-macro></li><li><p>If a binary snapshot was downloaded, to make it executable, the <code>ActiveMQ</code> script may need its permissions changed:</p><structured-macro ac:macro-id="e7a6c11a-8297-4dfd-a34a-bedd8aba7ffb" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]/bin
chmod 755 activemq
-]]></script>
-</div></div></li><li>For a binary snapshot, proceed to the <a shape="rect" href="#Version5GettingStarted-StartingActiveMQ">#Starting ActiveMQ</a> section of this document.</li><li>If a source snapshot was downloaded perform steps 6 - 8 of the <a shape="rect" href="#Version5GettingStarted-UnixSourceInstallation">#Unix Source Installation</a> procedure.</li><li>Proceed to the <a shape="rect" href="#Version5GettingStarted-TestingtheInstallation">#Testing the Installation</a> section.</li></ol><h2 id="Version5GettingStarted-StartingActiveMQStartingActiveMQ"><span class="confluence-anchor-link" id="Version5GettingStarted-StartingActiveMQ"></span> Starting ActiveMQ</h2><p>There now follows instructions on how to <a shape="rect" href="run-broker.xml">run the ActiveMQ Message Broker</a>.</p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>See also <a shape="rect" class="unresolved" href="#">Starting ActiveMQ with a different configuration file</a></p></div></div><h3 id="Version5GettingStarted-OnWindows">On Windows</h3><p>From a console window, change to the installation directory and run <code>ActiveMQ</code>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
-]]></script>
-</div></div><p>where <code>activemq_install_dir</code> is the directory in which ActiveMQ was installed, e.g., <code>c:\Program Files\ActiveMQ-5.x</code>.</p><p>Then type (depending on ActiveMQ version):</p><p><strong>ActiveMQ 5.10 onwards</strong></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin\activemq start
-]]></script>
-</div></div><p><strong>ActiveMQ 5.9 or older</strong></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin\activemq
-]]></script>
-</div></div><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p><h3 id="Version5GettingStarted-OnUnix">On Unix</h3><p>From a command shell, change to the installation directory and run <code>ActiveMQ</code>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
-]]></script>
-</div></div><p>where <code>activemq_install_dir</code> is the directory in which ActiveMQ was installed, e.g., <code>/usr/local/activemq-5.x</code>. <br clear="none" class="atl-forced-newline"> Then type:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq start
+</plain-text-body></structured-macro></li><li>For a binary snapshot, proceed to the <link ac:anchor="Starting ActiveMQ"><plain-text-link-body>#Starting ActiveMQ</plain-text-link-body></link> section of this document.</li><li>If a source snapshot was downloaded perform steps 6 - 8 of the <link ac:anchor="Unix Source Installation"><plain-text-link-body>#Unix Source Installation</plain-text-link-body></link> procedure.</li><li>Proceed to the <link ac:anchor="Testing the Installation"><plain-text-link-body>#Testing the Installation</plain-text-link-body></link> section.</li></ol><h2><structured-macro ac:macro-id="5befb636-4253-4229-ba45-d60bcb563393" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Starting ActiveMQ</parameter></structured-macro> Starting ActiveMQ</h2><p>There now follows instructions on how to <link><page ri:content-title="Run Broker"></page><plain-text-link-body>run the ActiveMQ Message Broker</plain-text-link-body></link>.</p><structured-macro ac:macro-id="0492faf5-128a-475a-b3f3-70fb06f687a4" ac:name="tip" ac:schema-version="1"><rich-text-body><p>See also <link><page ri:content-title="Starting ActiveMQ with a different configuration file"></page><plain-text-link-body>Starting ActiveMQ with a different configuration file</plain-text-link-body></link></p></rich-text-body></structured-macro><h3>On Windows</h3><p>From a console window, change to the installation directory and run <code>ActiveMQ</code>:</p><structured-macro ac:macro-id="9d65c810-dc63-48cb-b3dc-c1b0ba1cf5b3" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
+</plain-text-body></structured-macro><p>where <code>activemq_install_dir</code> is the directory in which ActiveMQ was installed, e.g., <code>c:\Program Files\ActiveMQ-5.x</code>.</p><p>Then type (depending on ActiveMQ version):</p><p><strong>ActiveMQ 5.10 onwards</strong></p><structured-macro ac:macro-id="93241836-2e91-42de-8917-400b185ee9d0" ac:name="code" ac:schema-version="1"><plain-text-body>bin\activemq start
+</plain-text-body></structured-macro><p><strong>ActiveMQ 5.9 or older</strong></p><structured-macro ac:macro-id="5be63c1c-4cd7-4baf-9905-bb48bc1d38c5" ac:name="code" ac:schema-version="1"><plain-text-body>bin\activemq
+</plain-text-body></structured-macro><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p><h3>On Unix</h3><p>From a command shell, change to the installation directory and run <code>ActiveMQ</code>:</p><structured-macro ac:macro-id="d586b8c2-494d-4129-bc54-6571caf9c16d" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
+</plain-text-body></structured-macro><p>where <code>activemq_install_dir</code> is the directory in which ActiveMQ was installed, e.g., <code>/usr/local/activemq-5.x</code>. <br clear="none" class="atl-forced-newline"> Then type:</p><structured-macro ac:macro-id="ebc96ce5-e577-4889-982f-4974ec3187ed" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq start
OR
bin/activemq start > /tmp/smlog 2>&1 &;
Note: /tmp/smlog may be changed to another file name.
-]]></script>
-</div></div><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Warning</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Do NOT close the console or shell in which ActiveMQ was started, as that will terminate ActiveMQ (unless ActiveMQ was started with nohup).</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[nohup bin/activemq > /tmp/smlog 2>&1 &
-]]></script>
-</div></div></div></div><h3 id="Version5GettingStarted-Morehelp">More help</h3><p>For other ways of running the broker see <a shape="rect" href="run-broker.xml">Here</a>. For example you can run an <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">embedded broker</a> inside your JMS Connection to avoid starting a separate process.</p><h2 id="Version5GettingStarted-TestingtheInstallationTestingtheInstallation"><span class="confluence-anchor-link" id="Version5GettingStarted-TestingtheInstallation"></span> Testing the Installation</h2><p>If ActiveMQ is up and running without problems, the Window's console window or the Unix command shell will display information similar to the following log line:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[INFO ActiveMQ JMS Message Broker (ID:apple-s-Computer.local-51222-1140729837569-0:0) has started
-]]></script>
-</div></div><p><br clear="none" class="atl-forced-newline"> ActiveMQ's default port is 61616. From another window run netstat and search for port 61616.</p><p>From a Windows console, type:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[netstat -an|find "61616"
-]]></script>
-</div></div><p><strong>OR</strong></p><p>From a Unix command shell, type:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[netstat -an|grep 61616
-]]></script>
-</div></div><h2 id="Version5GettingStarted-MonitoringActiveMQ">Monitoring ActiveMQ</h2><p>You can monitor ActiveMQ using the <a shape="rect" href="web-console.xml">Web Console</a> by pointing your browser at</p><p><a shape="rect" class="external-link" href="http://localhost:8161/admin" rel="nofollow">http://localhost:8161/admin</a></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>From ActiveMQ 5.8 onwards the web apps is secured out of the box.<br clear="none"> The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.</p></div></div><p>Or you can use the <a shape="rect" href="jmx.xml">JMX</a> support to view the running state of ActiveMQ.</p><p>For more information see the file <code>docs/WebConsole-README.txt</code> in the distribution.</p><h2 id="Version5GettingStarted-StoppingActiveMQ">Stopping ActiveMQ</h2><p>For both Windows and Unix installations, terminate ActiveMQ by typing "CTRL-C" in the console or command shell in which it is running.</p><p>If ActiveMQ was started in the background on Unix, the process can be killed, with the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[cd [activemq_install_dir]
-]]></script>
-</div></div><p>where <code>activemq_install_dir</code> is the directory in which ActiveMQ was installed, e.g., <code>/usr/local/activemq-5.x</code>. <br clear="none" class="atl-forced-newline"> Then type:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq stop
-]]></script>
-</div></div><p>Or you can do the following:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ps -ef|grep activemq
+</plain-text-body></structured-macro><p><strong>NOTE:</strong> Working directories get created relative to the current directory. To create working directories in the proper place, ActiveMQ must be launched from its home/installation directory.</p><structured-macro ac:macro-id="bc0a5691-878b-4b62-a043-9ec94a3d26f5" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Warning</parameter><rich-text-body><p>Do NOT close the console or shell in which ActiveMQ was started, as that will terminate ActiveMQ (unless ActiveMQ was started with nohup).</p><structured-macro ac:macro-id="d00d5f4e-0406-4638-91ad-8843e376c8f6" ac:name="code" ac:schema-version="1"><plain-text-body>nohup bin/activemq > /tmp/smlog 2>&1 &
+</plain-text-body></structured-macro></rich-text-body></structured-macro><h3>More help</h3><p>For other ways of running the broker see <link><page ri:content-title="Run Broker"></page><plain-text-link-body>Here</plain-text-link-body></link>. For example you can run an <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>embedded broker</plain-text-link-body></link> inside your JMS Connection to avoid starting a separate process.</p><h2><structured-macro ac:macro-id="fd0878ac-b448-456c-9f3b-344f4604e782" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Testing the Installation</parameter></structured-macro> Testing the Installation</h2><p>If ActiveMQ is up and running without problems, the Window's console window or the Unix command shell will display information similar to the following log line:</p><structured-macro ac:macro-id="4b904af1-4db6-4f95-9ce0-a972130ebd80" ac:name="code" ac:schema-version="1"><plain-text-body>INFO ActiveMQ JMS Message Broker (ID:apple-s-Computer.local-51222-1140729837569-0:0) has started
+</plain-text-body></structured-macro><p><br clear="none" class="atl-forced-newline"> ActiveMQ's default port is 61616. From another window run netstat and search for port 61616.</p><p>From a Windows console, type:</p><structured-macro ac:macro-id="4a13b281-4b1c-45f4-a841-3a631d550af4" ac:name="code" ac:schema-version="1"><plain-text-body>netstat -an|find "61616"
+</plain-text-body></structured-macro><p><strong>OR</strong></p><p>From a Unix command shell, type:</p><structured-macro ac:macro-id="fbfff630-333f-49a4-9418-811a8d38cbe5" ac:name="code" ac:schema-version="1"><plain-text-body>netstat -an|grep 61616
+</plain-text-body></structured-macro><h2>Monitoring ActiveMQ</h2><p><structured-macro ac:macro-id="461bd876-68aa-497a-8eff-96b67e48272f" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Monitoring ActiveMQ"></page></link></parameter></structured-macro></p><h2>Stopping ActiveMQ</h2><p>For both Windows and Unix installations, terminate ActiveMQ by typing "CTRL-C" in the console or command shell in which it is running.</p><p>If ActiveMQ was started in the background on Unix, the process can be killed, with the following:</p><structured-macro ac:macro-id="e1386f76-1f5f-49bc-a688-bf130692fbb3" ac:name="code" ac:schema-version="1"><plain-text-body>cd [activemq_install_dir]
+</plain-text-body></structured-macro><p>where <code>activemq_install_dir</code> is the directory in which ActiveMQ was installed, e.g., <code>/usr/local/activemq-5.x</code>. <br clear="none" class="atl-forced-newline"> Then type:</p><structured-macro ac:macro-id="aa98b67f-ae37-4896-9286-7f28701fdd71" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq stop
+</plain-text-body></structured-macro><p>Or you can do the following:</p><structured-macro ac:macro-id="fefd5a0f-9319-4f75-9b24-187c01aa2e34" ac:name="code" ac:schema-version="1"><plain-text-body>ps -ef|grep activemq
kill [PID]
where [PID] is the process id of the ActiveMQ process.
-]]></script>
-</div></div><h2 id="Version5GettingStarted-StartingActiveMQwithadifferentconfigurationfileStartingActiveMQwithadifferentconfigurationfile"><span class="confluence-anchor-link" id="Version5GettingStarted-StartingActiveMQwithadifferentconfigurationfile"></span> Starting ActiveMQ with a different configuration file</h2><p>By default ActiveMQ uses the <code>conf/activemq.xml</code> as the main configuration file when starting. If you want to use a different configuration file you can specify this as a parameter.</p><h4 id="Version5GettingStarted-ActiveMQ5.8orolder">ActiveMQ 5.8 or older</h4><p>For example to use <code>conf/activemq-demo.xml</code> which includes the web demos, you do as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console xbean:conf/activemq-demo.xml
-]]></script>
-</div></div><p>To start Active in console mode and load the <code>conf/activemq-demo.xml</code> file. Yes you need the <code>xbean:</code> as prefix.</p><p>And to launch as a background process you can do:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq start xbean:conf/activemq-demo.xml
-]]></script>
-</div></div><h4 id="Version5GettingStarted-ActiveMQ5.9onwards">ActiveMQ 5.9 onwards</h4><p>For example to use <code>examples/conf/activemq-demo.xml</code> which includes the web demos, you do as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console xbean:examples/conf/activemq-demo.xml
-]]></script>
-</div></div><p>To start Active in console mode and load the <code>examples/conf/activemq-demo.xml</code> file. Yes you need the <code>xbean:</code> as prefix.</p><p>And to launch as a background process you can do:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq start xbean:examples/conf/activemq-demo.xml
-]]></script>
-</div></div><h2 id="Version5GettingStarted-ConfiguringActiveMQ">Configuring ActiveMQ</h2><p>The ActiveMQ broker should now run. You can configure the broker by specifying an <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> file as a parameter to the <em>activemq</em> command. An alternative is to use the <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a> to configure things on the command line in a concise format (though the configuration options are not as extensive as if you use Java or XML code). You can also</p><p>Also see <a shape="rect" href="configuring-transports.xml">Configuring Transports</a> to see how you can configure the various connection, transport and broker options using the connection URL in the ActiveMQConnectionFactory.</p><p>See the <a shape="rect" href="initial-configuration.xml">Initial Configuration</a> for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code</p><p>If you want to use JNDI to connect to your JMS provider then please view the <a shape="rect" href="jndi-support.xml">JNDI Support</a>. If you are a Spring user you should read about <a shape="rect" href="spring-support.xml">Spring Support</a></p><p>After the installation, ActiveMQ is running with a basic configuration. For details on configuring options, please see refer to the <a shape="rect" href="configuration.xml">Configuration</a> section.</p><h2 id="Version5GettingStarted-AdditionalResources">Additional Resources</h2><p>If you are new to using ActiveMQ, running the <a shape="rect" href="web-samples.xml">Web Samples</a> or the <a shape="rect" href="examples.xml">Examples</a> is a good next step to learn more about ActiveMQ.</p></div>
+</plain-text-body></structured-macro><h2><structured-macro ac:macro-id="edcbd9c1-8895-47b8-920c-8820bb5caf4b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">Starting ActiveMQ with a different configuration file</parameter></structured-macro> Starting ActiveMQ with a different configuration file</h2><p>By default ActiveMQ uses the <code>conf/activemq.xml</code> as the main configuration file when starting. If you want to use a different configuration file you can specify this as a parameter.</p><h4>ActiveMQ 5.8 or older</h4><p>For example to use <code>conf/activemq-demo.xml</code> which includes the web demos, you do as follows:</p><structured-macro ac:macro-id="1245225a-9120-4801-8df4-743139b89f7f" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq console xbean:conf/activemq-demo.xml
+</plain-text-body></structured-macro><p>To start Active in console mode and load the <code>conf/activemq-demo.xml</code> file. Yes you need the <code>xbean:</code> as prefix.</p><p>And to launch as a background process you can do:</p><structured-macro ac:macro-id="1a122978-011e-4c51-9865-0d234caf4668" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq start xbean:conf/activemq-demo.xml
+</plain-text-body></structured-macro><h4>ActiveMQ 5.9 onwards</h4><p>For example to use <code>examples/conf/activemq-demo.xml</code> which includes the web demos, you do as follows:</p><structured-macro ac:macro-id="40feacc6-35e2-4ce9-a166-343607dbd235" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq console xbean:examples/conf/activemq-demo.xml
+</plain-text-body></structured-macro><p>To start Active in console mode and load the <code>examples/conf/activemq-demo.xml</code> file. Yes you need the <code>xbean:</code> as prefix.</p><p>And to launch as a background process you can do:</p><structured-macro ac:macro-id="6dca296b-9877-4d06-aa68-6778a8aedb52" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq start xbean:examples/conf/activemq-demo.xml
+</plain-text-body></structured-macro><h2>Configuring ActiveMQ</h2><p>The ActiveMQ broker should now run. You can configure the broker by specifying an <link><page ri:content-title="Xml Configuration"></page></link> file as a parameter to the <em>activemq</em> command. An alternative is to use the <link><page ri:content-title="Broker Configuration URI"></page></link> to configure things on the command line in a concise format (though the configuration options are not as extensive as if you use Java or XML code). You can also</p><p>Also see <link><page ri:content-title="Configuring Transports"></page></link> to see how you can configure the various connection, transport and broker options using the connection URL in the ActiveMQConnectionFactory.</p><p>See the <link><page ri:content-title="Initial Configuration"></page></link> for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code</p><p>If you want to use JNDI to connect to your JMS provider then please view the <link><page ri:content-title="JNDI Support"></page></link>. If you are a Spring user you should read about <link><page ri:content-title="Spring Support"></page></link></p><p>After the installation, ActiveMQ is running with a basic configuration. For details on configuring options, please see refer to the <link><page ri:content-title="Configuration"></page></link> section.</p><h2>Additional Resources</h2><p>If you are new to using ActiveMQ, running the <link><page ri:content-title="Web Samples"></page></link> or the <link><page ri:content-title="Examples"></page></link> is a good next step to learn more about ActiveMQ.</p></div>
diff --git a/version-5-hello-world.xml b/version-5-hello-world.xml
index e9ecd9e..113740b 100644
--- a/version-5-hello-world.xml
+++ b/version-5-hello-world.xml
@@ -1,152 +1,2 @@
-<div class="wiki-content maincontent">The following is a very simple JMS application with multiple, concurrent, consumers and producers. See the <a shape="rect" href="initial-configuration.xml">Initial Configuration</a> guide for details on how to setup your classpath correctly.
-
-<p>Things you might do after running this example:</p>
-<ul class="alternate"><li><a shape="rect" href="run-broker.xml">Setup a broker</a> instead of using the org.activemq.broker.impl.Main class directly</li><li>Use JNDI to lookup a javax.jms.ConnectionFactory rather than creating ActiveMQConnectionFactory directly.</li><li>Implement the javax.jms.MessageListener interface rather than calling consumer.receive()</li><li>Use transactional sessions</li><li>Use a Topic rather than a queue</li></ul>
-
-
-<p>The point of this example is to show you the basic code required to use JMS in a straightforward way. The Consumers and Producers could very easy be on completely different machines or in different processes.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>App.java</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-import org.apache.activemq.ActiveMQConnectionFactory;
-
-import javax.jms.Connection;
-import javax.jms.DeliveryMode;
-import javax.jms.Destination;
-import javax.jms.ExceptionListener;
-import javax.jms.JMSException;
-import javax.jms.Message;
-import javax.jms.MessageConsumer;
-import javax.jms.MessageProducer;
-import javax.jms.Session;
-import javax.jms.TextMessage;
-
-/**
- * Hello world!
- */
-public class App {
-
- public static void main(String[] args) throws Exception {
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldConsumer(), false);
- Thread.sleep(1000);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldProducer(), false);
- Thread.sleep(1000);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldProducer(), false);
- Thread.sleep(1000);
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldProducer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldConsumer(), false);
- thread(new HelloWorldProducer(), false);
- }
-
- public static void thread(Runnable runnable, boolean daemon) {
- Thread brokerThread = new Thread(runnable);
- brokerThread.setDaemon(daemon);
- brokerThread.start();
- }
-
- public static class HelloWorldProducer implements Runnable {
- public void run() {
- try {
- // Create a ConnectionFactory
- ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost");
-
- // Create a Connection
- Connection connection = connectionFactory.createConnection();
- connection.start();
-
- // Create a Session
- Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
-
- // Create the destination (Topic or Queue)
- Destination destination = session.createQueue("TEST.FOO");
-
- // Create a MessageProducer from the Session to the Topic or Queue
- MessageProducer producer = session.createProducer(destination);
- producer.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
-
- // Create a messages
- String text = "Hello world! From: " + Thread.currentThread().getName() + " : " + this.hashCode();
- TextMessage message = session.createTextMessage(text);
-
- // Tell the producer to send the message
- System.out.println("Sent message: "+ message.hashCode() + " : " + Thread.currentThread().getName());
- producer.send(message);
-
- // Clean up
- session.close();
- connection.close();
- }
- catch (Exception e) {
- System.out.println("Caught: " + e);
- e.printStackTrace();
- }
- }
- }
-
- public static class HelloWorldConsumer implements Runnable, ExceptionListener {
- public void run() {
- try {
-
- // Create a ConnectionFactory
- ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost");
-
- // Create a Connection
- Connection connection = connectionFactory.createConnection();
- connection.start();
-
- connection.setExceptionListener(this);
-
- // Create a Session
- Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
-
- // Create the destination (Topic or Queue)
- Destination destination = session.createQueue("TEST.FOO");
-
- // Create a MessageConsumer from the Session to the Topic or Queue
- MessageConsumer consumer = session.createConsumer(destination);
-
- // Wait for a message
- Message message = consumer.receive(1000);
-
- if (message instanceof TextMessage) {
- TextMessage textMessage = (TextMessage) message;
- String text = textMessage.getText();
- System.out.println("Received: " + text);
- } else {
- System.out.println("Received: " + message);
- }
-
- consumer.close();
- session.close();
- connection.close();
- } catch (Exception e) {
- System.out.println("Caught: " + e);
- e.printStackTrace();
- }
- }
-
- public synchronized void onException(JMSException ex) {
- System.out.println("JMS Exception occured. Shutting down client.");
- }
- }
-}
-]]></script>
-</div></div></div>
+<div class="wiki-content maincontent"><structured-macro ac:macro-id="3dfcd0d3-47cb-4201-93f8-94d64675480c" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Hello World"></page></link></parameter></structured-macro></div>
diff --git a/version-5-initial-configuration.xml b/version-5-initial-configuration.xml
index c1c261e..5acc9d0 100644
--- a/version-5-initial-configuration.xml
+++ b/version-5-initial-configuration.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="Version5InitialConfiguration-DocumentOrganization">Document Organization</h2><p></p><div class="toc-macro client-side-toc-macro" data-headerelements="H1,H2,H3,H4,H5,H6,H7" data-excludeheaderregex="Document Organization"></div><p>Firstly you need to add the jars to your classpath.</p><h2 id="Version5InitialConfiguration-RequiredJARs">Required JARs</h2><p>To make ActiveMQ easy to use, the default <strong>activemq-all.jar</strong> comes complete with all the libraries required. If you prefer to have explicit control over all the jars used by ActiveMQ here is the full list of individual jars required</p><ul><li>activemq-broker.jar</li><li>activemq-client.jar</li><li>activemq-kahadb-store.jar</li><li>activemq-spring.jar</li><li>hawtbuf-1.11.jar</li><li>slf4j-api.jar</li><li>slf4j-log4j12.jar</li><li>log4j-1.2.17.jar</li><li>J2EE APIs which could be the j2ee.jar from Sun or your J2EE container or you could use Geronimo's freely distributable geronimo-spec-j2ee.jar. If you are inside a servlet container and being dependent on the j2ee.jar causes you troubles, the parts of the J2EE jar we are dependent on are as follows...<ul><li>geronimo-spec-jms.jar</li><li>geronimo-spec-jta.jar</li><li>geronimo-spec-j2ee-management.jar</li></ul></li></ul><p>If you want to grab a J2EE specification jar we recommend the Apache <a shape="rect" class="external-link" href="http://cvs.apache.org/repository/geronimo-spec/jars/">repository</a></p><h2 id="Version5InitialConfiguration-OptionalJARS">Optional JARS</h2><ul><li>spring.jar - if you wish to use the XML configuration file for configuring the Message Broker</li></ul><ul><li>if you wish to use message persistence then you need to add a persistent jar to your classpath (see below). If you just want a lightweight message bus with no durability you can leave this step out but we highly recommend persistence for production deployments.</li></ul><h2 id="Version5InitialConfiguration-Persistencesupport">Persistence support</h2><p>The default persistence is the <a shape="rect" href="amq-message-store.xml">AMQ Message Store</a>. We do still support persistence via <a shape="rect" href="persistence.xml">JDBC and a high performance journal</a>. For full explict control over configuration check out the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>.</p><p>If you're just doing some testing or in-VM SEDA based messaging you may wish to disable persistence. You can use the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> for this.</p><p>You can do this by setting the usePersistence property to false either in the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> or on the <a shape="rect" href="configuring-transports.xml">broker URL</a>.</p><h2 id="Version5InitialConfiguration-Nextsteps">Next steps</h2><p>One of the first things you might want to do is <a shape="rect" href="run-broker.xml">start a broker</a>. Once you have a broker running you could try using the <a shape="rect" href="jndi-support.xml">JNDI Support</a> which shows how to run an example JMS program. Or there are some other <a shape="rect" href="examples.xml">example programs</a></p><p>If you don't want to use JNDI you can just instantiate an <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html" rel="nofollow">ActiveMQConnectionFactory</a>, configure its properties directly and then you're ready to use the standard JMS API to create Connections, Sessions, MessageProducer and MessageConsumer instances.</p><h2 id="Version5InitialConfiguration-Additionalresources">Additional resources</h2><h3 id="Version5InitialConfiguration-Relatedreading">Related reading</h3><ul><li>Sun's <a shape="rect" class="external-link" href="http://java.sun.com/products/jms/tutorial/" rel="nofollow">JMS Tutorial</a> is a handy place to start looking at how to use the JMS API directly</li><li>The ActiveMQ <a shape="rect" class="external-link" href="http://activemq.org" rel="nofollow">Website</a> for specifics on how to use ActiveMQ</li><li><a shape="rect" href="topologies.xml">ActiveMQ Topologies</a></li><li><a shape="rect" href="clustering.xml">ActiveMQ Clustering</a></li><li><a shape="rect" href="networks-of-brokers.xml">ActiveMQ Network of Brokers</a></li><li><a shape="rect" class="external-link" href="http://www.eecs.harvard.edu/~mdw/proj/seda/" rel="nofollow">Staged Event Driven Architecture (SEDA)</a></li></ul><h3 id="Version5InitialConfiguration-Specifications">Specifications</h3><ul><li><a shape="rect" class="external-link" href="http://java.sun.com/j2ee/connector/" rel="nofollow">Java Connector Architecture 1.5</a></li><li><a shape="rect" class="external-link" href="http://java.sun.com/products/jms/index.jsp" rel="nofollow">Java Messaging Service</a></li><li><a shape="rect" class="external-link" href="http://ws.apache.org/wsif/">WSIF</a></li><li><a shape="rect" class="external-link" href="http://www-128.ibm.com/developerworks/webservices/library/specification/ws-notification/" rel="nofollow">WS-Notification</a></li></ul><h3 id="Version5InitialConfiguration-Relatedopensourceprojects">Related open source projects</h3><ul><li><a shape="rect" class="external-link" href="http://geronimo.apache.org/">Apache Geronimo</a></li><li><a shape="rect" class="external-link" href="http://www.hermesjms.com/" rel="nofollow">Hermes JMS</a></li><li><a shape="rect" class="external-link" href="http://jencks.org/" rel="nofollow">Jencks</a> is a Spring JCA container allowing you to use connection & thread & POJO pooling for consuming JMS in highly concurrent servers</li><li><a shape="rect" class="external-link" href="http://lingo.codehaus.org/" rel="nofollow">Lingo</a> is a Spring/POJO remoting layer for JMS. It allows you to reuse all the power of JMS from your POJOs without using any of the JMS APIs directly</li><li><a shape="rect" class="external-link" href="http://www.springframework.org/" rel="nofollow">Spring</a></li><li><a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> is an open wire protocol (similar to HTTP) for communicating with MOMs from different languages. It has clients for languages like C, C#, Python, Perl, Ruby etc.</li><li><a shape="rect" class="external-link" href="http://xbean.org/" rel="nofollow">XBean</a> is used as the default XML configuration mechanism for ActiveMQ</li></ul></div>
+<div class="wiki-content maincontent"><h2>Document Organization</h2><p><structured-macro ac:macro-id="326b44f4-74e4-42fc-b124-f7ab4c105b3d" ac:name="toc" ac:schema-version="1"><parameter ac:name="exclude">Document Organization</parameter></structured-macro></p><p>Firstly you need to add the jars to your classpath.</p><h2>Required JARs</h2><p>To make ActiveMQ easy to use, the default <strong>activemq-all.jar</strong> comes complete with all the libraries required. If you prefer to have explicit control over all the jars used by ActiveMQ here is the full list of individual jars required</p><ul><li>activemq-broker.jar</li><li>activemq-client.jar</li><li>activemq-kahadb-store.jar</li><li>activemq-spring.jar</li><li>hawtbuf-1.11.jar</li><li>slf4j-api.jar</li><li>slf4j-log4j12.jar</li><li>log4j-1.2.17.jar</li><li>J2EE APIs which could be the j2ee.jar from Sun or your J2EE container or you could use Geronimo's freely distributable geronimo-spec-j2ee.jar. If you are inside a servlet container and being dependent on the j2ee.jar causes you troubles, the parts of the J2EE jar we are dependent on are as follows...<ul><li>geronimo-spec-jms.jar</li><li>geronimo-spec-jta.jar</li><li>geronimo-spec-j2ee-management.jar</li></ul></li></ul><p>If you want to grab a J2EE specification jar we recommend the Apache <a shape="rect" href="http://cvs.apache.org/repository/geronimo-spec/jars/">repository</a></p><h2>Optional JARS</h2><ul><li>spring.jar - if you wish to use the XML configuration file for configuring the Message Broker</li></ul><ul><li>if you wish to use message persistence then you need to add a persistent jar to your classpath (see below). If you just want a lightweight message bus with no durability you can leave this step out but we highly recommend persistence for production deployments.</li></ul><h2>Persistence support</h2><p>The default persistence is the <link><page ri:content-title="AMQ Message Store"></page></link>. We do still support persistence via <link><page ri:content-title="Persistence"></page><plain-text-link-body>JDBC and a high performance journal</plain-text-link-body></link>. For full explict control over configuration check out the <link><page ri:content-title="Xml Configuration"></page></link>.</p><p>If you're just doing some testing or in-VM SEDA based messaging you may wish to disable persistence. You can use the <link><page ri:content-title="Xml Configuration"></page></link> for this.</p><p>You can do this by setting the usePersistence property to false either in the <link><page ri:content-title="Xml Configuration"></page></link> or on the <link><page ri:content-title="Configuring Transports"></page><plain-text-link-body>broker URL</plain-text-link-body></link>.</p><h2>Next steps</h2><p>One of the first things you might want to do is <link><page ri:content-title="Run Broker"></page><plain-text-link-body>start a broker</plain-text-link-body></link>. Once you have a broker running you could try using the <link><page ri:content-title="JNDI Support"></page></link> which shows how to run an example JMS program. Or there are some other <link><page ri:content-title="Examples"></page><plain-text-link-body>example programs</plain-text-link-body></link></p><p>If you don't want to use JNDI you can just instantiate an <a shape="rect" href="http://activemq.codehaus.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a>, configure its properties directly and then you're ready to use the standard JMS API to create Connections, Sessions, MessageProducer and MessageConsumer instances.</p><h2>Additional resources</h2><h3>Related reading</h3><ul><li>Sun's <a shape="rect" href="http://java.sun.com/products/jms/tutorial/">JMS Tutorial</a> is a handy place to start looking at how to use the JMS API directly</li><li>The ActiveMQ <a shape="rect" href="http://activemq.org">Website</a> for specifics on how to use ActiveMQ</li><li><link><page ri:content-title="Topologies"></page><plain-text-link-body>ActiveMQ Topologies</plain-text-link-body></link></li><li><link><page ri:content-title="Clustering"></page><plain-text-link-body>ActiveMQ Clustering</plain-text-link-body></link></li><li><link><page ri:content-title="Networks of Brokers"></page><plain-text-link-body>ActiveMQ Network of Brokers</plain-text-link-body></link></li><li><a shape="rect" href="http://www.eecs.harvard.edu/~mdw/proj/seda/">Staged Event Driven Architecture (SEDA)</a></li></ul><h3>Specifications</h3><ul><li><a shape="rect" href="http://java.sun.com/j2ee/connector/">Java Connector Architecture 1.5</a></li><li><a shape="rect" href="http://java.sun.com/products/jms/index.jsp">Java Messaging Service</a></li><li><a shape="rect" href="http://ws.apache.org/wsif/">WSIF</a></li><li><a shape="rect" href="http://www-128.ibm.com/developerworks/webservices/library/specification/ws-notification/">WS-Notification</a></li></ul><h3>Related open source projects</h3><ul><li><a shape="rect" href="http://geronimo.apache.org/">Apache Geronimo</a></li><li><a shape="rect" href="http://www.hermesjms.com/">Hermes JMS</a></li><li><a shape="rect" href="http://jencks.org/">Jencks</a> is a Spring JCA container allowing you to use connection & thread & POJO pooling for consuming JMS in highly concurrent servers</li><li><a shape="rect" href="http://lingo.codehaus.org/">Lingo</a> is a Spring/POJO remoting layer for JMS. It allows you to reuse all the power of JMS from your POJOs without using any of the JMS APIs directly</li><li><a shape="rect" href="http://www.springframework.org/">Spring</a></li><li><a shape="rect" href="http://stomp.codehaus.org/">Stomp</a> is an open wire protocol (similar to HTTP) for communicating with MOMs from different languages. It has clients for languages like C, C#, Python, Perl, Ruby etc.</li><li><a shape="rect" href="http://xbean.org/">XBean</a> is used as the default XML configuration mechanism for ActiveMQ</li></ul></div>
diff --git a/version-5-installation.xml b/version-5-installation.xml
index 1cd26b7..541f4e3 100644
--- a/version-5-installation.xml
+++ b/version-5-installation.xml
@@ -1,22 +1,2 @@
-<div class="wiki-content maincontent"><p>
-</p><ul><li><a shape="rect" href="download.xml">Download</a> a binary distribution of ActiveMQ and unpack it into some directory.</li></ul>
-
-
-<ul><li>To run an ActiveMQ broker, type the following commands from the directory in which you have just unpacked the ActiveMQ distribution.</li></ul>
-
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-cd bin
-activemq
-]]></script>
-</div></div>
-
-<p>The ActiveMQ broker should now run. You can configure the broker by specifying an <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> file as a parameter to the <em>activemq</em> command.</p>
-
-<p>You can now run the <a shape="rect" href="examples.xml">Examples</a> using Ant.</p>
-
-<p>See the <a shape="rect" href="initial-configuration.xml">getting started guide</a> for details of which jars you need to add to your classpath to start using ActiveMQ in your Java code</p>
-
-<p>If you want to use JNDI to connect to your JMS provider then please view the <a shape="rect" href="jndi-support.xml">JNDI Support</a>. If you are a Spring user you should read about <a shape="rect" href="spring-support.xml">Spring Support</a></p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="a08119f1-ef54-4a91-a427-7e3e71bb73c0" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Installation"></page></link></parameter></structured-macro></p></div>
diff --git a/version-5-performance-tuning.xml b/version-5-performance-tuning.xml
index 08a2566..1bc65b7 100644
--- a/version-5-performance-tuning.xml
+++ b/version-5-performance-tuning.xml
@@ -1,10 +1,10 @@
-<div class="wiki-content maincontent"><p>For a more complete overview see <a shape="rect" href="performance.xml">Performance</a>.</p>
+<div class="wiki-content maincontent"><p>For a more complete overview see <link><page ri:content-title="Performance"></page></link>.</p>
<p>There are trade-offs between performance and reliabilty. <br clear="none">
By default, activemq strikes a balance between the two, so there are some things you can change to increase throughput.</p>
-<h2 id="Version5PerformanceTuning-Asyncpublishing">Async publishing</h2>
+<h2>Async publishing</h2>
<p>First some background:</p>
@@ -12,28 +12,29 @@
<p>So if you looking for good performance with topic messages, either set the delivery mode on the publisher to be non-persistent, or set the <strong>useAsyncSend</strong> property on the ActiveMQ ConnectionFactory to be <strong>true</strong>.</p>
-<h2 id="Version5PerformanceTuning-Pre-fetchsizesforConsumers">Pre-fetch sizes for Consumers</h2>
+<h2>Pre-fetch sizes for Consumers</h2>
<p>ActiveMQ will push as many messages to the consumer as fast as possible, where they will be queued for processing by an ActiveMQ Session. The maximum number of messages that ActiveMQ will push to a Consumer without the Consumer processing a message is set by the pre-fetch size. You can improve throughput by running ActiveMQ with larger pre-fetch sizes. Pre-fetch sizes are determined by the ActiveMQPrefetchPolicy bean, which is set on the ActiveMQ ConnectionFactory.</p>
<p>Default values:</p>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>consumer type</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>default value</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue browser </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 500</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 32766</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>durable topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> 1000</p></td></tr></tbody></table></div>
+<table><tbody><tr><th colspan="1" rowspan="1"><p>consumer type</p></th><th colspan="1" rowspan="1"><p>default value</p></th></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> 1000</p></td></tr><tr><td colspan="1" rowspan="1"><p> queue browser </p></td><td colspan="1" rowspan="1"><p> 500</p></td></tr><tr><td colspan="1" rowspan="1"><p>topic </p></td><td colspan="1" rowspan="1"><p> 32766</p></td></tr><tr><td colspan="1" rowspan="1"><p>durable topic </p></td><td colspan="1" rowspan="1"><p> 1000</p></td></tr></tbody></table>
-<h2 id="Version5PerformanceTuning-OptimizedAcknowledge">Optimized Acknowledge</h2>
+<h2>Optimized Acknowledge</h2>
<p>When consuming messages in auto acknowledge mode (set when creating the consumers' session), ActiveMQ will acknowledge receipt of messages back to the broker in batches (to improve performance). The batch size is 50% of the prefetch limit for the Consumer. You switch batch acknowledgment off by setting the <strong>optimizeAcknowledge</strong> property on the ActiveMQ ConnectionFactory to be <strong>false</strong></p>
-<h2 id="Version5PerformanceTuning-StraightthroughSessionConsumption">Straight through Session Consumption</h2>
+<h2>Straight through Session Consumption</h2>
<p>By default, a Consumer's session will dispatch messages to the consumer in a separate thread. If you are using Consumers with auto acknowledge, you can increase throughput by passing messages straight through the Session to the Consumer by setting the <strong>alwaysSessionAsync</strong> property on the ActiveMQ ConnectionFactory to be <strong>false</strong></p>
-<h2 id="Version5PerformanceTuning-FilebasedPersistence">File based Persistence</h2>
+<h2>File based Persistence</h2>
-<p>The default persistence store is the <a shape="rect" href="amq-message-store.xml">AMQ Message Store</a></p>
+<p>The default persistence store is the <link><page ri:content-title="AMQ Message Store"></page></link></p>
+
</div>
diff --git a/version-5-run-broker.xml b/version-5-run-broker.xml
index 9db71b4..cb24a17 100644
--- a/version-5-run-broker.xml
+++ b/version-5-run-broker.xml
@@ -1,22 +1,8 @@
-<div class="wiki-content maincontent"><h1 id="Version5RunBroker-RunninganActiveMQBroker">Running an ActiveMQ Broker</h1><p>Note if you want to use an <strong>embedded broker</strong> then see <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></p><p>The <a shape="rect" href="download.xml">binary distribution</a> of ActiveMQ comes with a script called 'activemq' which allows you to run a broker. <br clear="none">For details regarding the activemq init script file review  <a shape="rect" href="unix-shell-script.xml">Unix Shell Script</a>  and  <a shape="rect" href="activemq-command-line-tools-reference.xml">ActiveMQ Command Line Tools Reference</a></p><p> </p><p>Typing the following will run an ActiveMQ Broker using the out of the box configuration in the foreground</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console
-]]></script>
-</div></div><p>You can then use a <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a> to specify how to start and configure your broker using a single URI. For example</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console broker:(tcp://localhost:61616,network:static:tcp://remotehost:61616)?persistent=false&useJmx=true
-]]></script>
-</div></div><p>Or you can a <a shape="rect" href="broker-xbean-uri.xml">Broker XBean URI</a> to customize the Message Broker using the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> to suit your needs. You can run a broker with a specific XML configuration as</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console xbean:foo.xml
-]]></script>
-</div></div><p>Or you can use a <a shape="rect" href="broker-properties-uri.xml">Broker Properties URI</a> to customize the Message Broker using a properties file; which avoids the dependency on Spring, xbean-spring and XML.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: bash; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console properties:foo.properties]]></script>
-</div></div><h3 id="Version5RunBroker-Monitoringthebroker">Monitoring the broker</h3><p>You can monitor ActiveMQ using the <a shape="rect" href="web-console.xml">Web Console</a> by pointing your browser at</p><p><a shape="rect" class="external-link" href="http://localhost:8161/admin" rel="nofollow">http://localhost:8161/admin</a></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>From ActiveMQ 5.8 onwards the web apps is secured out of the box.<br clear="none"> The default username and password is admin/admin. You can configure this in the conf/jetty-real.properties file.</p></div></div><p>Or you can use the <a shape="rect" href="jmx.xml">JMX</a> support to view the running state of ActiveMQ.</p><p>For more information see the file <code>docs/WebConsole-README.txt</code> in the distribution.</p><h3 id="Version5RunBroker-RunningthebrokerinsideaServletEngine">Running the broker inside a Servlet Engine</h3><p>See the source code (or WAR) of the <a shape="rect" href="web-console.xml">Web Console</a> for an example of how to run the broker inside a web application using Spring.</p><h3 id="Version5RunBroker-RunningthebrokerinsideyourJ2EEApplicationServer">Running the broker inside your J2EE Application Server</h3><p>Whether its Apache Geronmio, JBoss, WebLogic or some other J2EE container you should be able to just reconfigure and then deploy the activemq-*.rar which is included in the binary distribution as a deployment unit in your app server. By default the rar is not configured to start an embedded broker. But by setting the brokerXmlConfig on the resource adapter configuration, the resource adapter will start an embedded broker.</p><p>For more details see <a shape="rect" href="j2ee.xml">J2EE</a></p><h3 id="Version5RunBroker-Runningthebrokerfromthesourcecode">Running the broker from the source code</h3><p>From the latest <a shape="rect" href="source.xml">checkout</a> of the code you can run a broker using the <a shape="rect" href="activemq-performance-module-users-manual.xml">ActiveMQ Performance Plugin</a></p><h3 id="Version5RunBroker-Runningthebrokerfrommaven">Running the broker from maven</h3><p>You can download and install the ActiveMQ Startup Maven Plugin via the following command if you are in a directory with a pom.xml. More detailed usage <a shape="rect" href="maven2-activemq-broker-plugin.xml">here</a></p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn org.apache.activemq.tooling:maven-activemq-plugin:5.0-SNAPSHOT:run
-]]></script>
-</div></div><p>You can also include it the pom and run it using:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[mvn activemq:run
-]]></script>
-</div></div><h2 id="Version5RunBroker-HandlingJMSbrokersgoingdown">Handling JMS brokers going down</h2><p>A common requirement is that if the JMS broker goes down you want to automatically detect the failure and try to reconnect under the covers so that your application does not have to worry about reconnection.</p><p>There is detailed documentation on this in <a shape="rect" href="configuring-version-5-transports.xml">Configuring Version 5 Transports</a>; briefly...</p><p>Just change your connection URI i to</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[failover:tcp://host:port
-]]></script>
-</div></div><p>And the JMS client will auto-reconnect to the broker if it is shutdown and restarted later on.</p></div>
+<div class="wiki-content maincontent"><h1>Running an ActiveMQ Broker</h1><p>Note if you want to use an <strong>embedded broker</strong> then see <link><page ri:content-title="How do I embed a Broker inside a Connection"></page></link></p><p>The <link><page ri:content-title="Download"></page><plain-text-link-body>binary distribution</plain-text-link-body></link> of ActiveMQ comes with a script called 'activemq' which allows you to run a broker. <br clear="none">For details regarding the activemq init script file review  <link><page ri:content-title="Unix Shell Script"></page></link>  and  <link><page ri:content-title="ActiveMQ Command Line Tools Reference"></page></link></p><p> </p><p>Typing the following will run an ActiveMQ Broker using the out of the box configuration in the foreground</p><structured-macro ac:macro-id="968eaf92-8c93-4dd5-aee6-a10bda8a56d0" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/activemq console
+</plain-text-body></structured-macro><p>You can then use a <link><page ri:content-title="Broker Configuration URI"></page></link> to specify how to start and configure your broker using a single URI. For example</p><structured-macro ac:macro-id="eb0175b5-2f19-47a7-8386-ed2ee18f4b67" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/activemq console broker:(tcp://localhost:61616,network:static:tcp://remotehost:61616)?persistent=false&useJmx=true
+</plain-text-body></structured-macro><p>Or you can a <link><page ri:content-title="Broker XBean URI"></page></link> to customize the Message Broker using the <link><page ri:content-title="Xml Configuration"></page></link> to suit your needs. You can run a broker with a specific XML configuration as</p><structured-macro ac:macro-id="4eb92bf8-f24b-4ca0-bb5b-00dad43cb85e" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/activemq console xbean:foo.xml
+</plain-text-body></structured-macro><p>Or you can use a <link><page ri:content-title="Broker Properties URI"></page></link> to customize the Message Broker using a properties file; which avoids the dependency on Spring, xbean-spring and XML.</p><structured-macro ac:macro-id="a215deb1-788d-4ef3-bd23-95a9bcbdc608" ac:name="code" ac:schema-version="1"><parameter ac:name="language">bash</parameter><plain-text-body>bin/activemq console properties:foo.properties</plain-text-body></structured-macro><h3>Monitoring the broker</h3><p><structured-macro ac:macro-id="00dff49d-cda2-4f51-900b-617d2dc37964" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Monitoring ActiveMQ"></page></link></parameter></structured-macro></p><h3>Running the broker inside a Servlet Engine</h3><p>See the source code (or WAR) of the <link><page ri:content-title="Web Console"></page></link> for an example of how to run the broker inside a web application using Spring.</p><h3>Running the broker inside your J2EE Application Server</h3><p>Whether its Apache Geronmio, JBoss, WebLogic or some other J2EE container you should be able to just reconfigure and then deploy the activemq-*.rar which is included in the binary distribution as a deployment unit in your app server. By default the rar is not configured to start an embedded broker. But by setting the brokerXmlConfig on the resource adapter configuration, the resource adapter will start an embedded broker.</p><p>For more details see <link><page ri:content-title="J2EE"></page></link></p><h3>Running the broker from the source code</h3><p>From the latest <link><page ri:content-title="Source"></page><plain-text-link-body>checkout</plain-text-link-body></link> of the code you can run a broker using the <link><page ri:content-title="ActiveMQ Performance Module Users Manual"></page><plain-text-link-body>ActiveMQ Performance Plugin</plain-text-link-body></link></p><h3>Running the broker from maven</h3><p>You can download and install the ActiveMQ Startup Maven Plugin via the following command if you are in a directory with a pom.xml. More detailed usage <link><page ri:content-title="Maven2 ActiveMQ Broker Plugin"></page><plain-text-link-body>here</plain-text-link-body></link></p><structured-macro ac:macro-id="35b3b149-9832-422f-a477-f9b81c5deb59" ac:name="code" ac:schema-version="1"><plain-text-body>mvn org.apache.activemq.tooling:maven-activemq-plugin:5.0-SNAPSHOT:run
+</plain-text-body></structured-macro><p>You can also include it the pom and run it using:</p><structured-macro ac:macro-id="94a43058-7ff3-49a5-a104-7c8a83bc9f36" ac:name="code" ac:schema-version="1"><plain-text-body>mvn activemq:run
+</plain-text-body></structured-macro><h2>Handling JMS brokers going down</h2><p>A common requirement is that if the JMS broker goes down you want to automatically detect the failure and try to reconnect under the covers so that your application does not have to worry about reconnection.</p><p>There is detailed documentation on this in <link><page ri:content-title="Configuring Version 5 Transports"></page></link>; briefly...</p><p>Just change your connection URI i to</p><structured-macro ac:macro-id="808df444-bb4e-43fd-9bf0-915d8ddfbe13" ac:name="code" ac:schema-version="1"><plain-text-body>failover:tcp://host:port
+</plain-text-body></structured-macro><p>And the JMS client will auto-reconnect to the broker if it is shutdown and restarted later on.</p></div>
diff --git a/version-5-topologies.xml b/version-5-topologies.xml
index 56d96a7..4afb2d6 100644
--- a/version-5-topologies.xml
+++ b/version-5-topologies.xml
@@ -1,17 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ supports a wide range of different deployment topologies as well as <a shape="rect" href="uri-protocols.xml">protocols</a> & wire formats. The following diagram shows a federated network of brokers with a few different kinds of topology.</p><p><a shape="rect" class="external-link" href="http://activemq.org/BrokerTopology.pdf" rel="nofollow"><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="version-5-topologies.data/BrokerTopology-1.png" data-image-src="/confluence/download/attachments/35975/BrokerTopology-1.png?version=1&modificationDate=1160651323000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3262" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="BrokerTopology-1.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35975" data-linked-resource-container-version="21"></span></a></p><p>Which topology you choose is up to you. We'll now describe a few of these protocols in a little more detail.</p><h2 id="Version5Topologies-InVM">In VM</h2><p>A useful option when unit testing is to limit JMS communication to within a single JVM. For this use the protocol</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[vm://localhost
-]]></script>
-</div></div><p>You can segment the VM protocol to different groups - e.g. if you want to have logically different JMS networks within the same JVM, you can group networks using different URIs. e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[vm://localhost/foo
-]]></script>
-</div></div><p>This will ensure that different segments do not interfere with one another. Though typically we use unique topic and queue destinations so that all traffic can coexist happily on the same logical network.</p><h2 id="Version5Topologies-Client-Server">Client-Server</h2><p>This is probably the most efficient and fastest solution for large numbers of clients requiring a diverse range of communication options from publish / subscribe to queue based communication. Typically the clients will connect with a Message Broker using a protocol, typically TCP or SSL but this could be NIO or other protocols.</p><p>We can load balance clients across brokers and provide broker failover so that we have a logical cluster of brokers with <a shape="rect" href="ha.xml">HA</a>.</p><p>e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tcp://somehost:port
-]]></script>
-</div></div><p>Or for SSL</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ssl://somehost:port
-]]></script>
-</div></div><p>You can use <a shape="rect" href="discovery.xml">Discovery</a> to find the brokers available that you can connect to which makes it easier to seamlessly connect to a cluster of brokers.</p><h2 id="Version5Topologies-EmbeddedBroker">Embedded Broker</h2><p>This is logically equivalent to Client-Server but some (or all) clients contain a locally embedded broker. So communcation between the client and server (broker) are all within the same JVM and so do not use real networking - though brokers may communicate with other brokers or clients connected to it.</p><p>This can avoid the extra hop required to go from producer to broker to consumer - which is a great optimisation for RMI / RPC style situations, where you want the performance benefits (reduced latency) of point to point networking but with the scalabilty of a flexible messaging fabric.</p><p>Embedded Brokers can also simplify deployment options as well, its one less process to run.</p><p>Another use case for embedded brokers is to provide store and forward isolation from each service - so that the remote brokers can fail quite happily without affecting the service with the embedded broker. e.g. the entire network could fail, but a service could continue publishing messages to its embedded broker.</p><p>You can find out how to <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">configure an embedded broker here</a></p><h2 id="Version5Topologies-PeertoPeer">Peer to Peer</h2><p>This allows peer based clusters to be created where there is no server - just clients connecting together.<br clear="none"> There are various ways to implement a peer to peer JMS network. One easy way is just to use a multicast transport for communication; then all nodes on the same multicast address will receive all messages and the local embedded message broker will route messages to the necessary MessageConsumers.</p><p>We currently have 3 choices for multicast protocols</p><ul><li>multicast</li><li>jgroups: uses the JGroups library to implement reliable multicast</li><li>jrms: uses Sun's JRMS library to implement reliable multicast</li></ul><p>Multicast is great in development though often you might want to disable this feature in production and have well known servers fixed on specific machines. Often socket based communication (using pointcast) is much faster & better for heavy-lifting - particularly on Java - so we tend to recommend to use multicast mostly for discovery and use TCP / SSL for your heavy duty messaging.</p><p>Often we can use the peer to peer topology as a bootstrap to create a cluster of clients & brokers and then autodeploy servers into the cluster for a true grid style network.</p><p>So you can get the effect of a peer based network using <a shape="rect" href="discovery.xml">Discovery</a> together with either stand alone Brokers or using embedded brokers.</p><h3 id="Version5Topologies-JXTA">JXTA</h3><p>We have a JXTA transport which will use the full JXTA stack for negotiating NAT and across firewalls and so forth for creating a true peer based JMS network.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[jxta://hostname:port
-]]></script>
-</div></div><p>Currently you need to run one server which everyone connects to via JXTA. We've not yet created a pure peer network with JXTA</p></div>
+<div class="wiki-content maincontent"><p><structured-macro ac:macro-id="374fed09-f67f-4b38-aa50-76336e25d77f" ac:name="include" ac:schema-version="1"><parameter ac:name=""><link><page ri:content-title="Topologies"></page></link></parameter></structured-macro></p></div>
diff --git a/version-5-web-samples.xml b/version-5-web-samples.xml
index 79ba074..04b6b09 100644
--- a/version-5-web-samples.xml
+++ b/version-5-web-samples.xml
@@ -1,11 +1,12 @@
-<div class="wiki-content maincontent"><p>There are a few example programs demonstrating the <a shape="rect" href="rest.xml">REST</a> messaging or <a shape="rect" href="ajax.xml">Ajax</a> in the <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/">activemq/activemq-web-demo</a> module. </p>
+<div class="wiki-content maincontent"><p>There are a few example programs demonstrating the <link><page ri:content-title="REST"></page></link> messaging or <link><page ri:content-title="Ajax"></page></link> in the <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-web-demo/">activemq/activemq-web-demo</a> module. </p>
-<h2 id="Version5WebSamples-RunningtheWebSamples">Running the Web Samples</h2>
+<h2>Running the Web Samples</h2>
<p>We have integrated the Web Samples into the binary distribution. </p>
<p>The steps to running the Web Samples are</p>
-<ul><li><a shape="rect" href="download.xml">Download</a> a binary distribution</li><li><a shape="rect" href="run-broker.xml">Run the Message Broker</a> e.g. by running bin/activemq</li><li>point your browser to <a shape="rect" class="external-link" href="http://localhost:8161/demo" rel="nofollow">http://localhost:8161/demo</a></li></ul>
+<ul><li><link><page ri:content-title="Download"></page></link> a binary distribution</li><li><link><page ri:content-title="Run Broker"></page><link-body>Run the Message Broker</link-body></link> e.g. by running bin/activemq</li><li>point your browser to <a shape="rect" class="external-link" href="http://localhost:8161/demo" rel="nofollow">http://localhost:8161/demo</a></li></ul>
+
</div>
diff --git a/version-5-xml-configuration.xml b/version-5-xml-configuration.xml
index c42c33f..4a0fef8 100644
--- a/version-5-xml-configuration.xml
+++ b/version-5-xml-configuration.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><ul><li>transport connectors which consist of transport channels and wire formats TODO: add a link to a page explaining what transport connectors are how to configure and use them.</li><li>network connectors using network channels or discovery TODO: add a link to a page explaining what network connectors are how to configure and use them.</li><li>discovery agents TODO: add a link to a page explaining what discovery agents are how to configure and use them.</li><li>persistence providers & locations TODO: add a link to a page explaining what persistence providers are how to configure and use them.</li><li>custom message containers (such as last image caching etc)</li></ul><p>We use <a shape="rect" class="external-link" href="http://xbean.org/" rel="nofollow">XBean</a> to perform the XML configuration.</p><p>For details of the XML see the <a shape="rect" href="xml-reference.xml">Xml Reference</a></p><parameter ac:name="title">Be careful with broker names and URIs</parameter><rich-text-body><p>Make sure you do not use any strange characters in the names of brokers as they are converted to URIs which <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html" rel="nofollow">do not allow things like underscores</a> in them etc.</p></rich-text-body><h2 id="Version5XMLConfiguration-Examples">Examples</h2><p>The default ActiveMQ configuration: <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">current default config</a>.</p><parameter ac:name="">xml</parameter><plain-text-body><beans
+<div class="wiki-content maincontent"><ul><li>transport connectors which consist of transport channels and wire formats TODO: add a link to a page explaining what transport connectors are how to configure and use them.</li><li>network connectors using network channels or discovery TODO: add a link to a page explaining what network connectors are how to configure and use them.</li><li>discovery agents TODO: add a link to a page explaining what discovery agents are how to configure and use them.</li><li>persistence providers & locations TODO: add a link to a page explaining what persistence providers are how to configure and use them.</li><li>custom message containers (such as last image caching etc)</li></ul><p>We use <a shape="rect" href="http://xbean.org/">XBean</a> to perform the XML configuration.</p><p>For details of the XML see the <link><page ri:content-title="Xml Reference"></page></link></p><parameter ac:name="title">Be careful with broker names and URIs</parameter><rich-text-body><p>Make sure you do not use any strange characters in the names of brokers as they are converted to URIs which <a shape="rect" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html">do not allow things like underscores</a> in them etc.</p></rich-text-body><h2>Examples</h2><p>The default ActiveMQ configuration: <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">current default config</a>.</p><parameter ac:name="">xml</parameter><plain-text-body><beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
@@ -97,5 +97,5 @@
Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
-->
<import resource="jetty.xml"/>
-</beans></plain-text-body><p>From a binary distribution there is an <em>activemq</em> script allowing you to run a Message Broker as a stand alone process from the command line easily providing the $ACTIVEMQ_HOME/bin directory is on your PATH.</p><h2 id="Version5XMLConfiguration-Configuringembeddedbrokers">Configuring embedded brokers</h2><p>You can also use the XML Configuration to configure <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">embedded brokers</a>. For example using the JNDI configuration mechanism you can do the following<br clear="none"> <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/test/java/org/apache/activemq/config/BrokerXmlConfigFromJNDITest.java">BrokerXmlConfigFromJNDITest</a><br clear="none"> Or of you want to explicitly configure the embedded broker via Java code you can do the following<br clear="none"> <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/test/java/org/apache/activemq/config/BrokerXmlConfigTest.java">BrokerXmlConfigTest</a></p><h2 id="Version5XMLConfiguration-UserSubmittedConfigurations">User Submitted Configurations</h2><p>We have a page which allows users to submit details of their configurations.</p><ul><li><a shape="rect" href="user-submitted-configurations.xml">User Submitted Configurations</a></li></ul><h2 id="Version5XMLConfiguration-Background">Background</h2><p>Since ActiveMQ has so many strategy pattern plugins for transports, wire formats, persistence and many other things, we wanted to leave the configuration format open so that you the developer can configure and extend ActiveMQ in any direction you wish.</p><p>So we use the <a shape="rect" class="external-link" href="http://static.springframework.org/spring/docs/2.5.x/reference/beans.html#beans-basics" rel="nofollow">Spring XML</a> configuration file format, which allows any beans / POJOs to be wired together and configured. However often Spring's XML can be kinda verbose at times, so we have implemented an ActiveMQ extension to the Spring XML which knows about the common, standard ActiveMQ things you're likely to do (e.g. tags like connector, wireFormat, serverTransport, persistence) - but at any time you can fall back to the normal Spring way of doing things (with tags like bean, property etc).</p><p>To see documentation of the XML file we use or to get access to the XSD/DTD see the <a shape="rect" href="xml-reference.xml">Xml Reference</a></p></div>
+</beans></plain-text-body><p>From a binary distribution there is an <em>activemq</em> script allowing you to run a Message Broker as a stand alone process from the command line easily providing the $ACTIVEMQ_HOME/bin directory is on your PATH.</p><h2>Configuring embedded brokers</h2><p>You can also use the XML Configuration to configure <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>embedded brokers</plain-text-link-body></link>. For example using the JNDI configuration mechanism you can do the following<br clear="none"> <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/test/java/org/apache/activemq/config/BrokerXmlConfigFromJNDITest.java">BrokerXmlConfigFromJNDITest</a><br clear="none"> Or of you want to explicitly configure the embedded broker via Java code you can do the following<br clear="none"> <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/test/java/org/apache/activemq/config/BrokerXmlConfigTest.java">BrokerXmlConfigTest</a></p><h2>User Submitted Configurations</h2><p>We have a page which allows users to submit details of their configurations.</p><ul><li><link><page ri:content-title="User Submitted Configurations"></page></link></li></ul><h2>Background</h2><p>Since ActiveMQ has so many strategy pattern plugins for transports, wire formats, persistence and many other things, we wanted to leave the configuration format open so that you the developer can configure and extend ActiveMQ in any direction you wish.</p><p>So we use the <a shape="rect" href="http://static.springframework.org/spring/docs/2.5.x/reference/beans.html#beans-basics">Spring XML</a> configuration file format, which allows any beans / POJOs to be wired together and configured. However often Spring's XML can be kinda verbose at times, so we have implemented an ActiveMQ extension to the Spring XML which knows about the common, standard ActiveMQ things you're likely to do (e.g. tags like connector, wireFormat, serverTransport, persistence) - but at any time you can fall back to the normal Spring way of doing things (with tags like bean, property etc).</p><p>To see documentation of the XML file we use or to get access to the XSD/DTD see the <link><page ri:content-title="Xml Reference"></page></link></p></div>
diff --git a/virtual-destinations.xml b/virtual-destinations.xml
index 820808f..43f7b06 100644
--- a/virtual-destinations.xml
+++ b/virtual-destinations.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p><em>Virtual Destinations</em> allow us to create logical destinations that clients can use to produce and consume from but which map onto one or more <em>physical destinations</em>. It allows us to provide more flexible loosely coupled messaging configurations.</p><h2 id="VirtualDestinations-VirtualTopics">Virtual Topics</h2><p>The idea behind <em>publish subscribe</em> is a great one. Allow producers to be decoupled from consumers so that they do not even know how many consumers are interested in the messages they publish. The JMS specification defines support for durable topics however they have limitations as we will describe...</p><h3 id="VirtualDestinations-ThelimitationsofJMSdurabletopics">The limitations of JMS durable topics</h3><p>A JMS durable subscriber MessageConsumer is created with a unique JMS clientID and durable subscriber name. To be JMS compliant only one JMS connection can be active at any point in time for one JMS clientID, and only one consumer can be active for a clientID and subscriber name. i.e., only <strong>one</strong> thread can be actively consuming from a given logical topic subscriber. This means we cannot implement</p><ul><li>load balancing of messages.</li><li>fast failover of the subscriber if that one process running that one consumer thread dies.</li></ul><p>Now <em>queue</em> semantics in JMS offer the ability to load balance work across a number of consumers in a reliable way - allowing many threads, processes and machines to be used to process messages. Then we have sophisticated sticky load balancing techniques like <a shape="rect" href="message-groups.xml">Message Groups</a> to load balance and parallelise work while maintaining ordering.</p><p>Another added benefit of having physical queues for each logical topic subscriber is we can them monitor the queue depths via <a shape="rect" href="jmx.xml">JMX</a> to monitor system performance together with being able to browse these physical queues.</p><h3 id="VirtualDestinations-VirtualTopicstotherescue">Virtual Topics to the rescue</h3><p>The idea behind virtual topics is that producers send to a topic in the usual JMS way. Consumers can continue to use the Topic semantics in the JMS specification. However if the topic is virtual, consumer can consume from a physical queue for a logical topic subscription, allowing many consumers to be running on many machines & threads to load balance the load.</p><p>E.g., let's say we have a topic called <strong>VirtualTopic.Orders</strong>. (Where the prefix VirtualTopic. indicates its a virtual topic). And we logically want to send orders to systems A and B. Now with regular durable topics we'd create a JMS consumer for clientID_A and "A" along with clientID_B and "B".</p><p>With virtual topics we can just go right ahead and consume to queue <strong>Consumer.A.VirtualTopic.Orders</strong> to be a consumer for system A or consume to <strong>Consumer.B.VirtualTopic.Orders</strong> to be a consumer for system B.</p><p>We can now have a pool of consumers for each system which then compete for messages for systems A or B such that all the messages for system A are processed exactly once and similarly for system B.</p><h3 id="VirtualDestinations-Customizingtheout-of-the-boxdefaults">Customizing the out-of-the-box defaults</h3><p>The out-of-the-box defaults are described above. Namely that the only virtual topics available must be within the <strong>VirtualTopic.></strong> namespace and that the consumer queues are named <strong>Consumer.*.VirtualTopic.></strong>.</p><p>You can configure this to use whatever naming convention you wish. The following <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/broker/virtual/global-virtual-topics.xml">example</a> shows how to make all topics virtual topics. The example below is using the name <strong>></strong> to indicate 'match all topics'. You could use this wildcard to apply different virtual topic policies in different hierarchies.</p><pre><span style="color: rgb(0,0,0);"><destinationInterceptors> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualTopic name=">" prefix="VirtualTopicConsumers.*." selectorAware="false"/> </span> </pre><pre> </virtualDestinations></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"></destinationInterceptors></span></pre><p> </p><p>Note that making a topic virtual does add a small CPU overhead when sending messages to the topic but it is fairly small.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Option</th><th colspan="1" rowspan="1" class="confluenceTh">Default</th><th colspan="1" rowspan="1" class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">selectorAware</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">only messages that match one of the existing subscribers are actually dispatched. Using this option prevents the build up of unmatched messages when selectors are used by exclusive consumers</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">local</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, don't fan out messages that were received over a network</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">concurrentSend</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, use an executor to fanout such that sends occur in parallel. This allows the journal to batch writes which will reduce disk io (5.12)</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">transactedSend</td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, use a transaction for fanout sends such that there is a single disk sync. A local broker transaction will be created if there is no client transaction (5.13)</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><span>dropOnResourceLimit</span></td><td colspan="1" rowspan="1" class="confluenceTd">false</td><td colspan="1" rowspan="1" class="confluenceTd">when true, ignore any ResourceAllocationException thrown during fanout (see: sendFailIfNoSpace policy entry) (5.16)</td></tr></tbody></table></div><p> </p><h2 id="VirtualDestinations-CompositeDestinations">Composite Destinations</h2><p>Composite Destinations allow for one-to-many relationships on individual destinations; the main use case is for <em>composite queues</em>. For example when a message is sent to queue A you may want to forward it also to queues B and C and topic D. Composite destinations are then a mapping from a virtual destination to a collection of other physical destinations. In this case the mapping is broker side and the client is unaware of the mapping between the destinations. This is different from client side <a shape="rect" href="composite-destinations.xml">Composite Destinations</a> where the client uses a URL notation to specify the actual physical destinations that a message must be sent to.</p><p>The following <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/broker/virtual/composite-queue.xml">example</a> shows how to set up a <strong><compositeQueue/></strong> element in the XML configuration so that when a message is sent to <code>MY.QUEUE</code> then it is really forwarded to the physical queue <code>FOO</code> and the topic <code>BAR</code>.</p><pre><span style="color: rgb(0,0,0);"><destinationInterceptors></span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <compositeQueue name="MY.QUEUE"></span></pre><pre><span style="color: rgb(0,0,0);"> <forwardTo></span></pre><pre><span style="color: rgb(0,0,0);"> <queue physicalName="FOO" /> </span></pre><pre><span style="color: rgb(0,0,0);"> <topic physicalName="BAR" /></span></pre><pre><span style="color: rgb(0,0,0);"> </forwardTo></span></pre><pre><span style="color: rgb(0,0,0);"> </compositeQueue></span></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinations></span></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinationInterceptor></span></pre><pre><span style="color: rgb(0,0,0);"></destinationInterceptors></span></pre><p> </p><p>By default, subscribers cannot consume messages directly from a composite queue or topic - it is a logical construct only. Given the configuration above, subscribers can only consume messages from <code>FOO</code> and <code>BAR</code>; but not <code>MY.QUEUE</code>.</p><p>This behaviour can be altered to implement use cases such as watching a queue by sending the same messages to a notification topic (wire tapping), by setting the optionally set <code>forwardOnly</code> attribute to false.</p><pre><compositeQueue name="IncomingOrders" forwardOnly="false"> </pre><pre> <forwardTo></pre><pre> <topic physicalName="Notifications" /></pre><pre> </forwardTo></pre><pre> </compositeQueue></pre><p> </p><p>Messages sent to <code>IncomingOrders</code> will all be copied and forwarded to <code>Notifications</code>, before being placed on the physical <code>IncomingOrders</code> queue for consumption by subscribers.</p><p>Where the <code>forwardOnly</code> attribute is not defined or is set to <code>true</code>, there is no logical difference between a <code>compositeQueue</code> and a <code>compositeTopic</code> - they can be used interchangeably. It is only when a composite destination is made physical through the use of <code>forwardOnly</code> that the choice of <code>compositeTopic</code>/<code>compositeQueue</code> has an impact on behavior.</p><h3 id="VirtualDestinations-Usingfiltereddestinations">Using filtered destinations</h3><p>From Apache ActiveMQ <strong>4.2</strong> onwards you can now use selectors to define virtual destinations.</p><p>You may wish to create a virtual destination which forwards messages to multiple destinations but applying a selector first to decide if the message really does have to go to a particular destination.</p><p>The following example shows how a message sent to the virtual destination <strong>MY.QUEUE</strong> will be forwarded to <strong>FOO</strong> and <strong>BAR</strong> if the selectors match</p><pre><destinationInterceptors> <virtualDestinationInterceptor> <virtualDestinations> </pre><pre> <compositeQueue name="MY.QUEUE"></pre><pre> <forwardTo></pre><pre> <filteredDestination selector="odd = 'yes'" queue="FOO"/></pre><pre> <filteredDestination selector="i = 5" topic="BAR"/></pre><pre> </forwardTo></pre><pre> </compositeQueue></pre><pre></virtualDestinations> </virtualDestinationInterceptor> </destinationInterceptors></pre><p> </p><h2 id="VirtualDestinations-AvoidingDuplicateMessageinaNetworkofBrokers">Avoiding Duplicate Message in a Network of Brokers</h2><p>You have to make sure that the messages sent to the <strong>Consumer.*.VirtualTopic.></strong> destination are not forwarded when you're using both queue-based and non-queue based subscribers to the virtual topic (that is, if you have normal topic subscribers to the virtual topic). If you use Virtual Topics in a network of brokers, it is likely you will get duplicate messages if you use the default network configuration. This is because a network node will not only forward message sent to the virtual topic, but also the associated physical queues. To fix this, you should disable forwarding messages on the associated physical queues.</p><p>Here is an example of how to do that:</p><pre><span style="color: rgb(0,0,0);"><networkConnectors> <networkConnector uri="static://(<a shape="rect" href="tcp://localhost:61617" rel="nofollow">tcp://localhost:61617</a>)"></span></pre><pre><span style="color: rgb(0,0,0);"> <excludedDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <queue physicalName="Consumer.*.VirtualTopic.>"/> </span></pre><pre><span style="color: rgb(0,0,0);"> </excludedDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"></networkConnector> </networkConnectors></span></pre><p> </p></div>
+<div class="wiki-content maincontent"><p><em>Virtual Destinations</em> allow us to create logical destinations that clients can use to produce and consume from but which map onto one or more <em>physical destinations</em>. It allows us to provide more flexible loosely coupled messaging configurations.</p><h2>Virtual Topics</h2><p>The idea behind <em>publish subscribe</em> is a great one. Allow producers to be decoupled from consumers so that they do not even know how many consumers are interested in the messages they publish. The JMS specification defines support for durable topics however they have limitations as we will describe...</p><h3>The limitations of JMS durable topics</h3><p>A JMS durable subscriber MessageConsumer is created with a unique JMS clientID and durable subscriber name. To be JMS compliant only one JMS connection can be active at any point in time for one JMS clientID, and only one consumer can be active for a clientID and subscriber name. i.e., only <strong>one</strong> thread can be actively consuming from a given logical topic subscriber. This means we cannot implement</p><ul><li>load balancing of messages.</li><li>fast failover of the subscriber if that one process running that one consumer thread dies.</li></ul><p>Now <em>queue</em> semantics in JMS offer the ability to load balance work across a number of consumers in a reliable way - allowing many threads, processes and machines to be used to process messages. Then we have sophisticated sticky load balancing techniques like <link><page ri:content-title="Message Groups"></page></link> to load balance and parallelise work while maintaining ordering.</p><p>Another added benefit of having physical queues for each logical topic subscriber is we can them monitor the queue depths via <link><page ri:content-title="JMX"></page></link> to monitor system performance together with being able to browse these physical queues.</p><h3>Virtual Topics to the rescue</h3><p>The idea behind virtual topics is that producers send to a topic in the usual JMS way. Consumers can continue to use the Topic semantics in the JMS specification. However if the topic is virtual, consumer can consume from a physical queue for a logical topic subscription, allowing many consumers to be running on many machines & threads to load balance the load.</p><p>E.g., let's say we have a topic called <strong>VirtualTopic.Orders</strong>. (Where the prefix VirtualTopic. indicates its a virtual topic). And we logically want to send orders to systems A and B. Now with regular durable topics we'd create a JMS consumer for clientID_A and "A" along with clientID_B and "B".</p><p>With virtual topics we can just go right ahead and consume to queue <strong>Consumer.A.VirtualTopic.Orders</strong> to be a consumer for system A or consume to <strong>Consumer.B.VirtualTopic.Orders</strong> to be a consumer for system B.</p><p>We can now have a pool of consumers for each system which then compete for messages for systems A or B such that all the messages for system A are processed exactly once and similarly for system B.</p><h3>Customizing the out-of-the-box defaults</h3><p>The out-of-the-box defaults are described above. Namely that the only virtual topics available must be within the <strong>VirtualTopic.></strong> namespace and that the consumer queues are named <strong>Consumer.*.VirtualTopic.></strong>.</p><p>You can configure this to use whatever naming convention you wish. The following <a shape="rect" href="https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/broker/virtual/global-virtual-topics.xml">example</a> shows how to make all topics virtual topics. The example below is using the name <strong>></strong> to indicate 'match all topics'. You could use this wildcard to apply different virtual topic policies in different hierarchies.</p><pre><span style="color: rgb(0,0,0);"><destinationInterceptors> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualTopic name=">" prefix="VirtualTopicConsumers.*." selectorAware="false"/> </span> </pre><pre> </virtualDestinations></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"></destinationInterceptors></span></pre><p> </p><p>Note that making a topic virtual does add a small CPU overhead when sending messages to the topic but it is fairly small.</p><table><tbody><tr><th colspan="1" rowspan="1">Option</th><th colspan="1" rowspan="1">Default</th><th colspan="1" rowspan="1">Description</th></tr><tr><td colspan="1" rowspan="1">selectorAware</td><td colspan="1" rowspan="1">false</td><td colspan="1" rowspan="1">only messages that match one of the existing subscribers are actually dispatched. Using this option prevents the build up of unmatched messages when selectors are used by exclusive consumers</td></tr><tr><td colspan="1" rowspan="1">local</td><td colspan="1" rowspan="1">false</td><td colspan="1" rowspan="1">when true, don't fan out messages that were received over a network</td></tr><tr><td colspan="1" rowspan="1">concurrentSend</td><td colspan="1" rowspan="1">false</td><td colspan="1" rowspan="1">when true, use an executor to fanout such that sends occur in parallel. This allows the journal to batch writes which will reduce disk io (5.12)</td></tr><tr><td colspan="1" rowspan="1">transactedSend</td><td colspan="1" rowspan="1">false</td><td colspan="1" rowspan="1">when true, use a transaction for fanout sends such that there is a single disk sync. A local broker transaction will be created if there is no client transaction (5.13)</td></tr><tr><td colspan="1" rowspan="1"><span>dropOnResourceLimit</span></td><td colspan="1" rowspan="1">false</td><td colspan="1" rowspan="1">when true, ignore any ResourceAllocationException thrown during fanout (see: sendFailIfNoSpace policy entry) (5.16)</td></tr></tbody></table><p> </p><h2>Composite Destinations</h2><p>Composite Destinations allow for one-to-many relationships on individual destinations; the main use case is for <em>composite queues</em>. For example when a message is sent to queue A you may want to forward it also to queues B and C and topic D. Composite destinations are then a mapping from a virtual destination to a collection of other physical destinations. In this case the mapping is broker side and the client is unaware of the mapping between the destinations. This is different from client side <link><page ri:content-title="Composite Destinations"></page></link> where the client uses a URL notation to specify the actual physical destinations that a message must be sent to.</p><p>The following <a shape="rect" href="http://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-unit-tests/src/test/resources/org/apache/activemq/broker/virtual/composite-queue.xml">example</a> shows how to set up a <strong><compositeQueue/></strong> element in the XML configuration so that when a message is sent to <code>MY.QUEUE</code> then it is really forwarded to the physical queue <code>FOO</code> and the topic <code>BAR</code>.</p><pre><span style="color: rgb(0,0,0);"><destinationInterceptors></span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinationInterceptor> </span></pre><pre><span style="color: rgb(0,0,0);"> <virtualDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <compositeQueue name="MY.QUEUE"></span></pre><pre><span style="color: rgb(0,0,0);"> <forwardTo></span></pre><pre><span style="color: rgb(0,0,0);"> <queue physicalName="FOO" /> </span></pre><pre><span style="color: rgb(0,0,0);"> <topic physicalName="BAR" /></span></pre><pre><span style="color: rgb(0,0,0);"> </forwardTo></span></pre><pre><span style="color: rgb(0,0,0);"> </compositeQueue></span></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinations></span></pre><pre><span style="color: rgb(0,0,0);"> </virtualDestinationInterceptor></span></pre><pre><span style="color: rgb(0,0,0);"></destinationInterceptors></span></pre><p> </p><p>By default, subscribers cannot consume messages directly from a composite queue or topic - it is a logical construct only. Given the configuration above, subscribers can only consume messages from <code>FOO</code> and <code>BAR</code>; but not <code>MY.QUEUE</code>.</p><p>This behaviour can be altered to implement use cases such as watching a queue by sending the same messages to a notification topic (wire tapping), by setting the optionally set <code>forwardOnly</code> attribute to false.</p><pre><compositeQueue name="IncomingOrders" forwardOnly="false"> </pre><pre> <forwardTo></pre><pre> <topic physicalName="Notifications" /></pre><pre> </forwardTo></pre><pre> </compositeQueue></pre><p> </p><p>Messages sent to <code>IncomingOrders</code> will all be copied and forwarded to <code>Notifications</code>, before being placed on the physical <code>IncomingOrders</code> queue for consumption by subscribers.</p><p>Where the <code>forwardOnly</code> attribute is not defined or is set to <code>true</code>, there is no logical difference between a <code>compositeQueue</code> and a <code>compositeTopic</code> - they can be used interchangeably. It is only when a composite destination is made physical through the use of <code>forwardOnly</code> that the choice of <code>compositeTopic</code>/<code>compositeQueue</code> has an impact on behavior.</p><h3>Using filtered destinations</h3><p>From Apache ActiveMQ <strong>4.2</strong> onwards you can now use selectors to define virtual destinations.</p><p>You may wish to create a virtual destination which forwards messages to multiple destinations but applying a selector first to decide if the message really does have to go to a particular destination.</p><p>The following example shows how a message sent to the virtual destination <strong>MY.QUEUE</strong> will be forwarded to <strong>FOO</strong> and <strong>BAR</strong> if the selectors match</p><pre><destinationInterceptors> <virtualDestinationInterceptor> <virtualDestinations> </pre><pre> <compositeQueue name="MY.QUEUE"></pre><pre> <forwardTo></pre><pre> <filteredDestination selector="odd = 'yes'" queue="FOO"/></pre><pre> <filteredDestination selector="i = 5" topic="BAR"/></pre><pre> </forwardTo></pre><pre> </compositeQueue></pre><pre></virtualDestinations> </virtualDestinationInterceptor> </destinationInterceptors></pre><p> </p><h2>Avoiding Duplicate Message in a Network of Brokers</h2><p>You have to make sure that the messages sent to the <strong>Consumer.*.VirtualTopic.></strong> destination are not forwarded when you're using both queue-based and non-queue based subscribers to the virtual topic (that is, if you have normal topic subscribers to the virtual topic). If you use Virtual Topics in a network of brokers, it is likely you will get duplicate messages if you use the default network configuration. This is because a network node will not only forward message sent to the virtual topic, but also the associated physical queues. To fix this, you should disable forwarding messages on the associated physical queues.</p><p>Here is an example of how to do that:</p><pre><span style="color: rgb(0,0,0);"><networkConnectors> <networkConnector uri="static://(<a shape="rect" href="tcp://localhost:61617">tcp://localhost:61617</a>)"></span></pre><pre><span style="color: rgb(0,0,0);"> <excludedDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"> <queue physicalName="Consumer.*.VirtualTopic.>"/> </span></pre><pre><span style="color: rgb(0,0,0);"> </excludedDestinations> </span></pre><pre><span style="color: rgb(0,0,0);"></networkConnector> </networkConnectors></span></pre><p> </p></div>
diff --git a/visualisation-wish-list.xml b/visualisation-wish-list.xml
index f7e082a..c50da77 100644
--- a/visualisation-wish-list.xml
+++ b/visualisation-wish-list.xml
@@ -1,4 +1,5 @@
<div class="wiki-content maincontent"><p>There are a zillion different things we could do to visualise the system. Lets use this page to braindump ideas for what kinds of visualisations we could do</p>
-<ul><li>show visually the popularity of certain destinations; using size/color/position/stats to indicate hot areas of the system</li><li>visually show the queue sizes & stats?</li><li>could we link the nodes somehow to some web page or something?</li></ul></div>
+<ul><li>show visually the popularity of certain destinations; using size/color/position/stats to indicate hot areas of the system</li><li>visually show the queue sizes & stats?</li><li>could we link the nodes somehow to some web page or something?</li></ul>
+</div>
diff --git a/visualisation.xml b/visualisation.xml
index 2a76416..806640c 100644
--- a/visualisation.xml
+++ b/visualisation.xml
@@ -1,28 +1,29 @@
-<div class="wiki-content maincontent"><p>Inspired greatly by <a shape="rect" class="external-link" href="http://www.enterpriseintegrationpatterns.com/talks.html" rel="nofollow">Gregor and Erik's great talk at TSSJS 2006</a> we've started to add some visualisation plugins into Apache ActiveMQ.</p>
+<div class="wiki-content maincontent"><p>Inspired greatly by <a shape="rect" href="http://www.enterpriseintegrationpatterns.com/talks.html">Gregor and Erik's great talk at TSSJS 2006</a> we've started to add some visualisation plugins into Apache ActiveMQ.</p>
-<h3 id="Visualisation-Connectionvisualisation">Connection visualisation</h3>
+<h3>Connection visualisation</h3>
-<p>There is a <strong><connectionDotFilePlugin/></strong> broker plugin which generates a <a shape="rect" class="external-link" href="http://www.graphviz.org/" rel="nofollow">DOT file</a> such as <a shape="rect" class="external-link" href="visualisation.data/ActiveMQConnections.dot" rel="nofollow">this example</a> representing the connections, sessions, producers, consumers and the destinations they are using.</p>
+<p>There is a <strong><connectionDotFilePlugin/></strong> broker plugin which generates a <a shape="rect" href="http://www.graphviz.org/">DOT file</a> such as <a shape="rect" href="visualisation.data/ActiveMQConnections.dot">this example</a> representing the connections, sessions, producers, consumers and the destinations they are using.</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="visualisation.data/ActiveMQConnections.png" data-image-src="/confluence/download/attachments/36195/ActiveMQConnections.png?version=1&modificationDate=1143546333000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3285" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="ActiveMQConnections.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="36195" data-linked-resource-container-version="15"></span></p>
+<p><image><attachment ri:filename="ActiveMQConnections.png"></attachment></image></p>
-<h3 id="Visualisation-Destinationvisualisation">Destination visualisation</h3>
+<h3>Destination visualisation</h3>
-<p>There is a <strong><destinationDotFilePlugin/></strong> broker plugin which generates a <a shape="rect" class="external-link" href="http://www.graphviz.org/" rel="nofollow">DOT file</a> such as <a shape="rect" class="external-link" href="visualisation.data/ActiveMQDestinations.dot" rel="nofollow">this example</a> whenever a destination is created or destroyed in the broker. You can then turn this dot file into a nicely rendered image such as the one below.</p>
+<p>There is a <strong><destinationDotFilePlugin/></strong> broker plugin which generates a <a shape="rect" href="http://www.graphviz.org/">DOT file</a> such as <a shape="rect" href="visualisation.data/ActiveMQDestinations.dot">this example</a> whenever a destination is created or destroyed in the broker. You can then turn this dot file into a nicely rendered image such as the one below.</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image confluence-thumbnail" src="visualisation.thumbs/ActiveMQDestinations.png" data-image-src="/confluence/download/attachments/36195/ActiveMQDestinations.png?version=1&modificationDate=1143412917000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3239" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="ActiveMQDestinations.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="36195" data-linked-resource-container-version="15"></span></p>
+<p><image ac:thumbnail="true"><attachment ri:filename="ActiveMQDestinations.png"></attachment></image></p>
-<h2 id="Visualisation-AnoteforOSXusers">A note for OS X users</h2>
+<h2>A note for OS X users</h2>
-<p>If you are using OS X then you can open the DOT file using <a shape="rect" class="external-link" href="http://www.pixelglow.com/graphviz/" rel="nofollow">graphviz</a> which will then automatically re-render if it changes, so you end up with a real time graphical representation of the topic and queue hierarchies.</p>
+<p>If you are using OS X then you can open the DOT file using <a shape="rect" href="http://www.pixelglow.com/graphviz/">graphviz</a> which will then automatically re-render if it changes, so you end up with a real time graphical representation of the topic and queue hierarchies.</p>
-<p>Also if you want to edit the layout a little before adding it to a wiki to distribute to your team, open the DOT file with <a shape="rect" class="external-link" href="http://www.omnigroup.com/applications/omnigraffle/" rel="nofollow">OmniGraffle</a> then just edit away <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>Also if you want to edit the layout a little before adding it to a wiki to distribute to your team, open the DOT file with <a shape="rect" href="http://www.omnigroup.com/applications/omnigraffle/">OmniGraffle</a> then just edit away <emoticon ac:name="smile"></emoticon></p>
-<h2 id="Visualisation-VisualisationWishList">Visualisation Wish List</h2>
+<h2>Visualisation Wish List</h2>
-<p>There are so many different things we could visualise; our only limitation is our imagination. So if you have any ideas for what we could visualise please add something to our <a shape="rect" href="visualisation-wish-list.xml">Visualisation Wish List</a></p>
+<p>There are so many different things we could visualise; our only limitation is our imagination. So if you have any ideas for what we could visualise please add something to our <link><page ri:content-title="Visualisation Wish List"></page></link></p>
-<h1 id="Visualisation-ExternalOpenSourceTools">External Open Source Tools</h1>
+<h1>External Open Source Tools</h1>
-<ul><li><a shape="rect" class="external-link" href="http://hawt.io/" rel="nofollow">hawtio</a> is an open source HTML5 web application for working with Apache ActiveMQ and Apache Camel. It lets you create topics/queues, browse queues or send messages to destinations as well as visualising Camel routes and working with Camel endpoints along with viewing logs and metric charting etc.</li><li><a shape="rect" class="external-link" href="https://github.com/fusesource/fuseide" rel="nofollow">Fuse IDE</a> is an open source set of eclipse plugins for working with Apache ActiveMQ and Apache Camel. Its got tooling for runtime browsing of queues, creating topics/queues. You can drag and drop messages to/from ActiveMQ destinations and Camel endpoints</li></ul></div>
+<ul><li><a shape="rect" href="http://hawt.io/">hawtio</a> is an open source HTML5 web application for working with Apache ActiveMQ and Apache Camel. It lets you create topics/queues, browse queues or send messages to destinations as well as visualising Camel routes and working with Camel endpoints along with viewing logs and metric charting etc.</li><li><a shape="rect" href="https://github.com/fusesource/fuseide">Fuse IDE</a> is an open source set of eclipse plugins for working with Apache ActiveMQ and Apache Camel. Its got tooling for runtime browsing of queues, creating topics/queues. You can drag and drop messages to/from ActiveMQ destinations and Camel endpoints</li></ul>
+</div>
diff --git a/vm-protocol.xml b/vm-protocol.xml
index 70002a7..1f88822 100644
--- a/vm-protocol.xml
+++ b/vm-protocol.xml
@@ -1,13 +1,13 @@
<div class="wiki-content maincontent">
<p>Protocol syntax : vm://logicalname</p>
-<p>Javadocs : <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/apidocs/org/codehaus/activemq/transport/vm/package-frame.html" rel="nofollow">org.codehaus.activemq.transport.vm</a></p>
+<p>Javadocs : <a shape="rect" href="http://activemq.codehaus.org/maven/apidocs/org/codehaus/activemq/transport/vm/package-frame.html">org.codehaus.activemq.transport.vm</a></p>
<p>The VM protocol allows clients to connect to each other inside the VM without the overhead of the network communication. The connection used is not a socket connection but some kind of virtual connection that allows an embedded messaging system.</p>
<p>It is to be noted that objects inside JMS ObjectMessage instances are transferred using serialization and not by reference. This may sound surprising but there are very good reasons for that.</p>
-<ol><li>In a well designed J2EE application server (from a production point of view), you typically have a classloader hierarchy that allows to run EARs and WARs in perfect isolation between each other and from the third-party libraries used by the server internals. If you have clients located in different, isolated classloader hierarchies then a shared reference will lead to a ClassCastException. Thus it <strong>must</strong> be serialized..</li><li>If you were to send an object by reference, it would be wrapped by an <a shape="rect" class="external-link" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/ObjectMessage.html" rel="nofollow">ObjectMessage</a>. Nothing would then prevent you from modifying the object further before sending it. That may sound like it is not a problem but the TCK tests exactly for that, meaning that your JMS implementation would not be J2EE-compliant. Therefore the object <strong>must</strong> be serialized.</li></ol>
+<ol><li>In a well designed J2EE application server (from a production point of view), you typically have a classloader hierarchy that allows to run EARs and WARs in perfect isolation between each other and from the third-party libraries used by the server internals. If you have clients located in different, isolated classloader hierarchies then a shared reference will lead to a ClassCastException. Thus it <strong>must</strong> be serialized..</li><li>If you were to send an object by reference, it would be wrapped by an <a shape="rect" href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/ObjectMessage.html">ObjectMessage</a>. Nothing would then prevent you from modifying the object further before sending it. That may sound like it is not a problem but the TCK tests exactly for that, meaning that your JMS implementation would not be J2EE-compliant. Therefore the object <strong>must</strong> be serialized.</li></ol>
<p>If intra-vm JMS performance were an issue when sending messages in your application, and that you know your messaging boundaries are constrained in your classloader scope, then you could perfectly think of superfast vm protocol that would send messages by reference. This currently does not exist within ActiveMQ for the reasons stated above.</p></div>
diff --git a/vm-transport-reference.xml b/vm-transport-reference.xml
index 155c5b6..0440f14 100644
--- a/vm-transport-reference.xml
+++ b/vm-transport-reference.xml
@@ -1,21 +1,13 @@
-<div class="wiki-content maincontent"><h3 id="VMTransportReference-TheVMTransport">The VM Transport</h3><p>The VM transport allows clients to connect to each other inside the VM without the overhead of the network communication. The connection used is not a socket connection but use direct method invocations which enables a high performance embedded messaging system.</p><p>The first client to use the VM connection will boot an embedded broker. Subsequent connections will attach that the same broker. Once all VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><h4 id="VMTransportReference-SimpleBrokerConfigurationSyntax">Simple Broker Configuration Syntax</h4><p>This is the normal syntax for a VM connection. It's simple, but provides only a limited amount of configuration of the embedded broker.</p><p><strong>vm://brokerName?transportOptions</strong></p><p>If you want to connect to an already instantiated, embedded broker (e.g. as in case the case of Apache ServiceMix), make sure the brokerName used in the <strong>vm://brokerName</strong> url matches the brokerName of the already running broker.</p><h5 id="VMTransportReference-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>marshal</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, forces each command sent over the transport to be marshalled and unmarshalled using a WireFormat</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>default</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the WireFormat to use</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>All the properties with this prefix are used to configure the wireFormat</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>create</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If the broker should be created on demand if it does not already exist.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>waitForStart</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>-1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If > 0, indicates the timeout in milliseconds to wait for a broker to start. Values -1 and 0 mean don't wait. Only supported in ActiveMQ 5.2+</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>broker.*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>All the properties with this prefix are used to configure the broker. See <a shape="rect" href="configuring-wire-formats.xml">Configuring Wire Formats</a> for more information</p></td></tr></tbody></table></div><h5 id="VMTransportReference-ExampleURI">Example URI</h5><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>vm://broker1?marshal=false&broker.persistent=false
-</pre>
-</div></div><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Be careful with embedded brokers</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you are using the VM transport and wish to explicitly configure an <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">Embedded Broker</a> there is a chance that you could create the JMS connections first before the broker starts up. Currently ActiveMQ will auto-create a broker if you use the VM transport and there is not one already configured. (In 5.2 it is possible to use the waitForStart and create=false options for the connection uri)</p><p>So to work around this if you are using Spring you may wish to use the <strong>depends-on</strong> attribute so that your JMS ConnectionFactory depends on the embedded broker to avoid this happening. e.g.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
- <property name="config" value="classpath:org/apache/activemq/xbean/activemq.xml" />
- <property name="start" value="true" />
+<div class="wiki-content maincontent"><h3>The VM Transport</h3><p>The VM transport allows clients to connect to each other inside the VM without the overhead of the network communication. The connection used is not a socket connection but use direct method invocations which enables a high performance embedded messaging system.</p><p>The first client to use the VM connection will boot an embedded broker. Subsequent connections will attach that the same broker. Once all VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><h4>Simple Broker Configuration Syntax</h4><p>This is the normal syntax for a VM connection. It's simple, but provides only a limited amount of configuration of the embedded broker.</p><p><strong>vm://brokerName?transportOptions</strong></p><p>If you want to connect to an already instantiated, embedded broker (e.g. as in case the case of Apache ServiceMix), make sure the brokerName used in the <strong>vm://brokerName</strong> url matches the brokerName of the already running broker.</p><h5>Transport Options</h5><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>marshal</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, forces each command sent over the transport to be marshalled and unmarshalled using a WireFormat</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat</p></td><td colspan="1" rowspan="1"><p>default</p></td><td colspan="1" rowspan="1"><p>The name of the WireFormat to use</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.*</p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p>All the properties with this prefix are used to configure the wireFormat</p></td></tr><tr><td colspan="1" rowspan="1"><p>create</p></td><td colspan="1" rowspan="1"><p>true</p></td><td colspan="1" rowspan="1"><p>If the broker should be created on demand if it does not already exist.</p></td></tr><tr><td colspan="1" rowspan="1"><p>waitForStart</p></td><td colspan="1" rowspan="1"><p>-1</p></td><td colspan="1" rowspan="1"><p>If > 0, indicates the timeout in milliseconds to wait for a broker to start. Values -1 and 0 mean don't wait. Only supported in ActiveMQ 5.2+</p></td></tr><tr><td colspan="1" rowspan="1"><p>broker.*</p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p>All the properties with this prefix are used to configure the broker. See <link><page ri:content-title="Configuring Wire Formats"></page></link> for more information</p></td></tr></tbody></table><h5>Example URI</h5><structured-macro ac:macro-id="592b3ea5-9343-4135-a998-1059b4739023" ac:name="noformat" ac:schema-version="1"><plain-text-body>vm://broker1?marshal=false&broker.persistent=false
+</plain-text-body></structured-macro><structured-macro ac:macro-id="8ca9d826-7d1d-48db-bd15-5017980d4e12" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Be careful with embedded brokers</parameter><rich-text-body><p>If you are using the VM transport and wish to explicitly configure an <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>Embedded Broker</plain-text-link-body></link> there is a chance that you could create the JMS connections first before the broker starts up. Currently ActiveMQ will auto-create a broker if you use the VM transport and there is not one already configured. (In 5.2 it is possible to use the waitForStart and create=false options for the connection uri)</p><p>So to work around this if you are using Spring you may wish to use the <strong>depends-on</strong> attribute so that your JMS ConnectionFactory depends on the embedded broker to avoid this happening. e.g.</p><structured-macro ac:macro-id="1a5e5eea-9463-4a02-b30a-58726c93db80" ac:name="code" ac:schema-version="1"><plain-text-body><bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
+ <property name="config" value="classpath:org/apache/activemq/xbean/activemq.xml" />
+ <property name="start" value="true" />
</bean>
- <bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory" depends-on="broker">
- <property name="brokerURL" value="vm://localhost"/>
+ <bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory" depends-on="broker">
+ <property name="brokerURL" value="vm://localhost"/>
</bean>
-]]></script>
-</div></div></div></div><h4 id="VMTransportReference-AdvancedBrokerConfigurationSyntax">Advanced Broker Configuration Syntax</h4><p>This is the advanced syntax for a VM connection. It's allows you configure the broker more extensively using a <a shape="rect" href="broker-configuration-uri.xml">Broker Configuration URI</a>.</p><p><strong>vm:(broker:(tcp://localhost)?brokerOptions)?transportOptions</strong><br clear="none"> or<br clear="none"> <strong>vm:broker:(tcp://localhost)?brokerOptions</strong></p><h5 id="VMTransportReference-TransportOptions.1">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>marshal</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>If true, forces each command sent over the transport to be marshalled and unmarshalled using a WireFormat</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>default</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the WireFormat to use</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>All the properties with this prefix are used to configure the wireFormat</p></td></tr></tbody></table></div><p>There are <a shape="rect" href="how-should-i-use-the-vm-transport.xml">more options</a> on optimising the use of the VM transport.</p><h5 id="VMTransportReference-ExampleURI.1">Example URI</h5><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>vm:(broker:(tcp://localhost:6000)?persistent=false)?marshal=false
-</pre>
-</div></div><h4 id="VMTransportReference-ConfiguringanEmbeddedBrokerUsinganExternalConfigFile">Configuring an Embedded Broker Using an External Config File</h4><p> To start an embedded broker using the vm transport and configure it using an external configuration file (i.e. activemq.xml), use the following URI:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ vm://localhost?brokerConfig=xbean:activemq.xml
-]]></script>
-</div></div></div>
+</plain-text-body></structured-macro></rich-text-body></structured-macro><h4>Advanced Broker Configuration Syntax</h4><p>This is the advanced syntax for a VM connection. It's allows you configure the broker more extensively using a <link><page ri:content-title="Broker Configuration URI"></page></link>.</p><p><strong>vm:(broker:(tcp://localhost)?brokerOptions)?transportOptions</strong><br clear="none"> or<br clear="none"> <strong>vm:broker:(tcp://localhost)?brokerOptions</strong></p><h5>Transport Options</h5><table><tbody><tr><th colspan="1" rowspan="1"><p>Option Name</p></th><th colspan="1" rowspan="1"><p>Default Value</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p>marshal</p></td><td colspan="1" rowspan="1"><p>false</p></td><td colspan="1" rowspan="1"><p>If true, forces each command sent over the transport to be marshalled and unmarshalled using a WireFormat</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat</p></td><td colspan="1" rowspan="1"><p>default</p></td><td colspan="1" rowspan="1"><p>The name of the WireFormat to use</p></td></tr><tr><td colspan="1" rowspan="1"><p>wireFormat.*</p></td><td colspan="1" rowspan="1"><p> </p></td><td colspan="1" rowspan="1"><p>All the properties with this prefix are used to configure the wireFormat</p></td></tr></tbody></table><p>There are <link><page ri:content-title="How should I use the VM transport"></page><plain-text-link-body>more options</plain-text-link-body></link> on optimising the use of the VM transport.</p><h5>Example URI</h5><structured-macro ac:macro-id="5c97b2c2-af39-4c1e-b6af-2a90be0c2100" ac:name="noformat" ac:schema-version="1"><plain-text-body>vm:(broker:(tcp://localhost:6000)?persistent=false)?marshal=false
+</plain-text-body></structured-macro><h4>Configuring an Embedded Broker Using an External Config File</h4><p> To start an embedded broker using the vm transport and configure it using an external configuration file (i.e. activemq.xml), use the following URI:</p><structured-macro ac:macro-id="ae9d03a5-7d07-4413-a210-21ecbeb9cb45" ac:name="code" ac:schema-version="1"><plain-text-body> vm://localhost?brokerConfig=xbean:activemq.xml
+</plain-text-body></structured-macro></div>
diff --git a/web-console.xml b/web-console.xml
index fea26e5..5bc5e6e 100644
--- a/web-console.xml
+++ b/web-console.xml
@@ -1,33 +1,23 @@
-<div class="wiki-content maincontent"><p>The ActiveMQ Web Console is a web based administration tool for working with ActiveMQ. When used with the <a shape="rect" href="jmx.xml">JMX</a> support it can be an invaluable tool for working with ActiveMQ</p><h3 id="WebConsole-RunningtheWebConsoleonActiveMQ5.0orlater">Running the Web Console on ActiveMQ 5.0 or later</h3><p>We have integrated the Web Console into the binary distribution. So <a shape="rect" href="download.xml">Download</a> a binary distribution then follow the instructions for <a shape="rect" href="version-5-run-broker.xml">Version 5 Run Broker</a>. Then you can point your web browser at the URL</p><ul><li><a shape="rect" class="external-link" href="http://localhost:8161/admin" rel="nofollow">http://localhost:8161/admin</a></li></ul><p>And hey presto, you should now have the Web Console running.</p><p>In the event that you are running a standalone broker and the Web Console is not reachable, check that the following lines are included in your ActiveMQ config xml:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
-<property name="locations">
+<div class="wiki-content maincontent"><p>The ActiveMQ Web Console is a web based administration tool for working with ActiveMQ. When used with the <link><page ri:content-title="JMX"></page></link> support it can be an invaluable tool for working with ActiveMQ</p><h3>Running the Web Console on ActiveMQ 5.0 or later</h3><p>We have integrated the Web Console into the binary distribution. So <link><page ri:content-title="Download"></page></link> a binary distribution then follow the instructions for <link><page ri:content-title="Version 5 Run Broker"></page></link>. Then you can point your web browser at the URL</p><ul><li><a shape="rect" href="http://localhost:8161/admin">http://localhost:8161/admin</a></li></ul><p>And hey presto, you should now have the Web Console running.</p><p>In the event that you are running a standalone broker and the Web Console is not reachable, check that the following lines are included in your ActiveMQ config xml:</p><structured-macro ac:macro-id="750e47f3-a1be-4f79-bc5b-afa488f6cec0" ac:name="code" ac:schema-version="1"><plain-text-body><bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
+<property name="locations">
<value>file:${activemq.base}/conf/credentials.properties</value>
</property>
</bean>
<!-- your broker config goes here -->
-<import resource="${activemq.base}/conf/jetty.xml" />]]></script>
-</div></div><p>The import will start up an embedded Jetty container. To verify that the config is working, the following should appear in your ActiveMQ console/logs on next startup:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[INFO | jetty-7.1.6.v20100715
-INFO | ActiveMQ WebConsole initialized.]]></script>
-</div></div><h3 id="WebConsole-Changingtheport">Changing the port</h3><p>If you want to change the port number of the web console, see the configuration files in the conf directory.</p><h3 id="WebConsole-SecuringWebConsole">Securing Web Console</h3><p>Starting with ActiveMQ 5.4.0, Web Console comes pre-configured with basic access authentication setup. It's turned off by default, so you need to turn it on explicitly, but it's really simple. Go to the <code>${ACTIVEMQ_HOME}/conf/jetty.xml</code> and find the following line</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<property name="authenticate" value="false" />]]></script>
-</div></div><p>and change it to</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<property name="authenticate" value="true" />]]></script>
-</div></div><p>That's it. From that point on, web server will look at <code>${ACTIVEMQ_HOME}/conf/jetty-realm.properties</code> file trying to match provided credentials with those listed in the file. By default, you can access the web console with <code>admin/admin</code> credentials. That can be changed (and more users can be added) in the <code>jetty-realm.properties</code> file.</p><p>You may also wish to enable <strong>ssl connector</strong> to further secure access to the web console and other web resources of the broker. To do that, go to the <code>${ACTIVEMQ_HOME}/conf/jetty.xml</code> and make sure you have the secure connector enabled. In versions 5.7 and newer just uncomment a predefined config. In any case make sure your connectors settings looks similar to this.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <property name="connectors">
+<import resource="${activemq.base}/conf/jetty.xml" /></plain-text-body></structured-macro><p>The import will start up an embedded Jetty container. To verify that the config is working, the following should appear in your ActiveMQ console/logs on next startup:</p><structured-macro ac:macro-id="92f4531d-8d49-4782-aac9-85e977187380" ac:name="code" ac:schema-version="1"><plain-text-body>INFO | jetty-7.1.6.v20100715
+INFO | ActiveMQ WebConsole initialized.</plain-text-body></structured-macro><h3>Changing the port</h3><p>If you want to change the port number of the web console, see the configuration files in the conf directory.</p><h3>Securing Web Console</h3><p>Starting with ActiveMQ 5.4.0, Web Console comes pre-configured with basic access authentication setup. It's turned off by default, so you need to turn it on explicitly, but it's really simple. Go to the <code>${ACTIVEMQ_HOME}/conf/jetty.xml</code> and find the following line</p><structured-macro ac:macro-id="7de36396-cc65-43b1-84aa-84c20160259b" ac:name="code" ac:schema-version="1"><plain-text-body><property name="authenticate" value="false" /></plain-text-body></structured-macro><p>and change it to</p><structured-macro ac:macro-id="7a767e3a-fb93-48b6-a2ca-43dbd2eec6a0" ac:name="code" ac:schema-version="1"><plain-text-body><property name="authenticate" value="true" /></plain-text-body></structured-macro><p>That's it. From that point on, web server will look at <code>${ACTIVEMQ_HOME}/conf/jetty-realm.properties</code> file trying to match provided credentials with those listed in the file. By default, you can access the web console with <code>admin/admin</code> credentials. That can be changed (and more users can be added) in the <code>jetty-realm.properties</code> file.</p><p>You may also wish to enable <strong>ssl connector</strong> to further secure access to the web console and other web resources of the broker. To do that, go to the <code>${ACTIVEMQ_HOME}/conf/jetty.xml</code> and make sure you have the secure connector enabled. In versions 5.7 and newer just uncomment a predefined config. In any case make sure your connectors settings looks similar to this.</p><structured-macro ac:macro-id="1cbe3658-9f93-47dd-8f90-38e810b12eeb" ac:name="code" ac:schema-version="1"><plain-text-body> <property name="connectors">
<list>
- <bean id="Connector" class="org.eclipse.jetty.server.nio.SelectChannelConnector">
- <property name="port" value="8161" />
+ <bean id="Connector" class="org.eclipse.jetty.server.nio.SelectChannelConnector">
+ <property name="port" value="8161" />
</bean>
- <bean id="SecureConnector" class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
- <property name="port" value="8162" />
- <property name="keystore" value="file:${activemq.conf}/broker.ks" />
- <property name="password" value="password" />
+ <bean id="SecureConnector" class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
+ <property name="port" value="8162" />
+ <property name="keystore" value="file:${activemq.conf}/broker.ks" />
+ <property name="password" value="password" />
</bean>
</list>
</property>
-]]></script>
-</div></div><p>Standard connector is left enabled in this example, but you can remove it in your configuration if you wish.</p><p>Note that these changes will affect the whole web server, so if you're using <a shape="rect" href="rest.xml">REST</a> API or blob fileserver be sure to provide appropriate credentials.</p><p>If you're interested in securing 5.3.1 (and 5.3.2) Web consoles, take a look at <a shape="rect" class="external-link" href="http://www.nighttale.net/activemq/securing-activemq-531-console.html" rel="nofollow">this article</a>. For older versions, please refer to <a shape="rect" class="external-link" href="http://it.toolbox.com/blogs/unix-sysadmin/securing-activemq-web-console-27727" rel="nofollow">this article</a></p><h3 id="WebConsole-UsingtheWebConsole">Using the Web Console</h3><p>The web console is depicted in the following image:</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" height="250" src="web-console.data/web_console.png" data-image-src="/confluence/download/attachments/36192/web_console.png?version=4&modificationDate=1469884551000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="24347140" data-linked-resource-version="4" data-linked-resource-type="attachment" data-linked-resource-default-alias="web_console.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="36192" data-linked-resource-container-version="38"></span></p><p>To get started, go to the <a shape="rect" class="external-link" href="http://localhost:8080/activemq-web-console/send.jsp" rel="nofollow">Send</a> page and send a message to a queue (you can send multiple if you like, see the message count field).</p><p>Now that you have sent messages to a queue you should be able to <a shape="rect" class="external-link" href="http://localhost:8080/activemq-web-console/browse.jsp" rel="nofollow">Browse</a> then and view the queue as an RSS or Atom feed.</p><p>The Web Console has many features relative to it's tabs as shown in the following table.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Tab</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Features</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Home</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/producer-flow-control.html#ProducerFlowControl-Systemusage">System Usage</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Queues</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Topics</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/advisory-message.html">Viewing Advisory Messages</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Subscribers</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Connections</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/protocols.html">Protocols</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Scheduled</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Send</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/delay-and-schedule-message-delivery.html">Delay and Schedule Message Delivery</a></p></td></tr></tbody></table></div><h1 id="WebConsole-ExternalWebConsoles">External Web Consoles</h1><p>There are a number of external web consoles for Apache ActiveMQ in separate open source projects:</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>External Project</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://hawt.io/" rel="nofollow">hawtio</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>hawtio is an open source HTML5 web application for visualising, managing, tracing and debugging Camel routes & endpoints, ActiveMQ brokers, JMX, OSGi and logging. Here is a <a shape="rect" class="external-link" href="http://www.bennet-schulz.com/2016/07/apache-activemq-and-hawtio.html" rel="nofollow">blog entry</a> how to install hawtio as web console for ActiveMQ.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://www.jboss.org/rhq" rel="nofollow">RHQ</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>RHQ is an open source operational monitoring tool which has support for Apache Camel (along with other Apache projects like Tomcat, httpd, ActiveMQ etc)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" class="external-link" href="http://www.hermesjms.com/confluence/display/HJMS/Home" rel="nofollow">Hermes JMS</a></td><td colspan="1" rowspan="1" class="confluenceTd">HermesJMS is an extensible console that helps you interact with JMS providers making it simple to publish and edit messages, browse or seach queues and topics, copy messages around and delete them.</td></tr></tbody></table></div></div>
+</plain-text-body></structured-macro><p>Standard connector is left enabled in this example, but you can remove it in your configuration if you wish.</p><p>Note that these changes will affect the whole web server, so if you're using <link><page ri:content-title="REST"></page></link> API or blob fileserver be sure to provide appropriate credentials.</p><p>If you're interested in securing 5.3.1 (and 5.3.2) Web consoles, take a look at <a shape="rect" href="http://www.nighttale.net/activemq/securing-activemq-531-console.html">this article</a>. For older versions, please refer to <a shape="rect" href="http://it.toolbox.com/blogs/unix-sysadmin/securing-activemq-web-console-27727">this article</a></p><h3>Using the Web Console</h3><p>The web console is depicted in the following image:</p><p><image ac:height="250"><attachment ri:filename="web_console.png"></attachment></image></p><p>To get started, go to the <a shape="rect" href="http://localhost:8080/activemq-web-console/send.jsp">Send</a> page and send a message to a queue (you can send multiple if you like, see the message count field).</p><p>Now that you have sent messages to a queue you should be able to <a shape="rect" href="http://localhost:8080/activemq-web-console/browse.jsp">Browse</a> then and view the queue as an RSS or Atom feed.</p><p>The Web Console has many features relative to it's tabs as shown in the following table.</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Tab</p></th><th colspan="1" rowspan="1"><p>Features</p></th></tr><tr><td colspan="1" rowspan="1"><p>Home</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/producer-flow-control.html#ProducerFlowControl-Systemusage">System Usage</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Queues</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>Topics</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/advisory-message.html">Viewing Advisory Messages</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Subscribers</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>Connections</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/protocols.html">Protocols</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>Scheduled</p></td><td colspan="1" rowspan="1"><p> </p></td></tr><tr><td colspan="1" rowspan="1"><p>Send</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/delay-and-schedule-message-delivery.html">Delay and Schedule Message Delivery</a></p></td></tr></tbody></table><h1>External Web Consoles</h1><p>There are a number of external web consoles for Apache ActiveMQ in separate open source projects:</p><table><tbody><tr><th colspan="1" rowspan="1"><p>External Project</p></th><th colspan="1" rowspan="1"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://hawt.io/">hawtio</a></p></td><td colspan="1" rowspan="1"><p>hawtio is an open source HTML5 web application for visualising, managing, tracing and debugging Camel routes & endpoints, ActiveMQ brokers, JMX, OSGi and logging. Here is a <a shape="rect" href="http://www.bennet-schulz.com/2016/07/apache-activemq-and-hawtio.html">blog entry</a> how to install hawtio as web console for ActiveMQ.</p></td></tr><tr><td colspan="1" rowspan="1"><p><a shape="rect" href="http://www.jboss.org/rhq">RHQ</a></p></td><td colspan="1" rowspan="1"><p>RHQ is an open source operational monitoring tool which has support for Apache Camel (along with other Apache projects like Tomcat, httpd, ActiveMQ etc)</p></td></tr><tr><td colspan="1" rowspan="1"><a shape="rect" href="http://www.hermesjms.com/confluence/display/HJMS/Home">Hermes JMS</a></td><td colspan="1" rowspan="1">HermesJMS is an extensible console that helps you interact with JMS providers making it simple to publish and edit messages, browse or seach queues and topics, copy messages around and delete them.</td></tr></tbody></table></div>
diff --git a/web-samples.xml b/web-samples.xml
index aa3177b..2f2c910 100644
--- a/web-samples.xml
+++ b/web-samples.xml
@@ -1,4 +1,2 @@
-<div class="wiki-content maincontent"><p>There are a few example programs demonstrating the <a shape="rect" href="rest.xml">REST</a>, <a shape="rect" href="ajax.xml">Ajax</a> and <a shape="rect" href="websockets.xml">WebSockets</a> messaging that comes with the ActiveMQ distribution.</p><p>Up until version 5.8 web demos were included in the default configuration and could be accessed directly using <a shape="rect" class="external-link" href="http://localhost:8161/demo" rel="nofollow">http://localhost:8161/demo</a> url after starting the broker.</p><p>From 5.8 onwards, demos are excluded from default configuration. To start a broker with web examples, use <code>activemq-demo.xml</code> configuration file, like</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console xbean:examples/conf/activemq-demo.xml]]></script>
-</div></div><h2 id="WebSamples-SeeAlso">See Also</h2><ul><li><a shape="rect" href="examples.xml">Examples</a></li><li><a shape="rect" href="jmx.xml">JMX</a></li><li><a shape="rect" href="web-console.xml">Web Console</a></li></ul></div>
+<div class="wiki-content maincontent"><p>There are a few example programs demonstrating the <link><page ri:content-title="REST"></page></link>, <link><page ri:content-title="Ajax"></page></link> and <link><page ri:content-title="WebSockets"></page></link> messaging that comes with the ActiveMQ distribution.</p><p>Up until version 5.8 web demos were included in the default configuration and could be accessed directly using <a shape="rect" class="external-link" href="http://localhost:8161/demo" rel="nofollow">http://localhost:8161/demo</a> url after starting the broker.</p><p>From 5.8 onwards, demos are excluded from default configuration. To start a broker with web examples, use <code>activemq-demo.xml</code> configuration file, like</p><structured-macro ac:macro-id="288caa27-887e-4a36-bb5c-9675602b2cc2" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq console xbean:examples/conf/activemq-demo.xml</plain-text-body></structured-macro><h2>See Also</h2><ul><li><link><page ri:content-title="Examples"></page></link></li><li><link><page ri:content-title="JMX"></page></link></li><li><link><page ri:content-title="Web Console"></page></link></li></ul></div>
diff --git a/weblogic-integration.xml b/weblogic-integration.xml
index f19469c..7c10a0b 100644
--- a/weblogic-integration.xml
+++ b/weblogic-integration.xml
@@ -1,16 +1,16 @@
-<div class="wiki-content maincontent"><h1 id="WebLogicIntegration-ActiveMQWebLogicIntegration">ActiveMQ WebLogic Integration</h1>
+<div class="wiki-content maincontent"><h1>ActiveMQ WebLogic Integration</h1>
<p>ActiveMQ clients and brokers can be run in WebLogic Server or WebLogic Express. This is usually done for licensing reasons:</p>
<ul><li>WebLogic Server includes JMS client and server features, but it may cost extra to use these JMS features to connect multiple servers together (as opposed to only using JMS internally within one server)</li><li>WebLogic Express disables the JMS features via the license, so while JMS classes are on the class path, there are no JMS features available.<br clear="none">
An ActiveMQ broker may be run within WebLogic to provide JMS features while avoiding these issues. As well, an ActiveMQ client may be run within WebLogic to connect to either an ActiveMQ broker running in the same WebLogic instance, and ActiveMQ broker running in a remote WebLogic instance, or a standalone ActiveMQ broker running elsewhere on the network.</li></ul>
-<h2 id="WebLogicIntegration-ActiveMQClientsinWebLogic">ActiveMQ Clients in WebLogic</h2>
+<h2>ActiveMQ Clients in WebLogic</h2>
<p>An ActiveMQ client can be run in any recent version of WebLogic. However, the specifics depend on which revision of JMS is supported by your version of WebLogic.</p>
-<h3 id="WebLogicIntegration-WebLogicServer/ExpressversionsincludingJMS1.0.x">WebLogic Server/Express versions including JMS 1.0.x</h3>
+<h3>WebLogic Server/Express versions including JMS 1.0.x</h3>
<p>This is known to include <strong>WebLogic 8.1</strong> and all previous versions.</p>
@@ -24,7 +24,7 @@
<p><strong>TODO:</strong> Add sample JMS 1.0.x code</p>
-<h3 id="WebLogicIntegration-WebLogicServerversionsincludingJMS1.1">WebLogic Server versions including JMS 1.1</h3>
+<h3>WebLogic Server versions including JMS 1.1</h3>
<p><strong>WebLogic 9.2</strong> and above are known to support JMS 1.1. (I don't know what JMS release WebLogic 9.0-9.1 support)</p>
@@ -34,7 +34,7 @@
<p>If you're using Spring or another non-J2EE architecture in your application, you may choose to skip the J2EE Connector and just connect directly to ActiveMQ using the technique described in the next section.</p>
-<h3 id="WebLogicIntegration-WebLogicExpressversionsincludingJMS1.1">WebLogic Express versions including JMS 1.1</h3>
+<h3>WebLogic Express versions including JMS 1.1</h3>
<p><strong>WebLogic 9.2</strong> and above are known to support JMS 1.1. (I don't know what JMS release WebLogic 9.0-9.1 support)</p>
@@ -42,7 +42,7 @@
<p><strong>TODO:</strong> Example of JMS 1.1 client and Spring Message-Driven POJO client for WebLogic</p>
-<h2 id="WebLogicIntegration-ActiveMQBrokersinWebLogic">ActiveMQ Brokers in WebLogic</h2>
+<h2>ActiveMQ Brokers in WebLogic</h2>
<p>On the surface it's not obvious why you might want to run an ActiveMQ broker within WebLogic instead of standalone, but the considerations include:</p>
<ul><li>When ActiveMQ is run within WebLogic, it can be deployed, started, stopped, and redeployed like other applications, using the WebLogic console or other tools, while the JVM and WebLogic are still running</li><li>ActiveMQ can hook into the WebLogic JMX management system (as well as e.g. JRockit) to provide a single management interface to the app server, applications, ActiveMQ, and even the JVM.</li><li>ActiveMQ can leverage WebLogic security realms for authentication and authorization – not only are there more security realm types available for WebLogic, but they're also easier to configure via the WebLogic console</li></ul>
@@ -52,13 +52,13 @@
<p>The specific integration techniques depend on whether you're using WebLogic Server or WebLogic Express, and whether your version supports JMS 1.0.x or JMS 1.1.</p>
-<h3 id="WebLogicIntegration-WebLogicServer/ExpressversionsincludingJMS1.0.x.1">WebLogic Server/Express versions including JMS 1.0.x</h3>
+<h3>WebLogic Server/Express versions including JMS 1.0.x</h3>
<p>Deploying an ActiveMQ broker in a release of WebLogic Server or WebLogic Express that supports only JMS 1.0.x has not been tested. This is known to include <strong>WebLogic 8.1</strong> and all previous versions. It will probably have trouble due to conflicting versions of JMS used by ActiveMQ and by WebLogic.</p>
<p><em>Please report your results if you try this</em></p>
-<h3 id="WebLogicIntegration-WebLogicServerversionsincludingJMS1.1.1">WebLogic Server versions including JMS 1.1</h3>
+<h3>WebLogic Server versions including JMS 1.1</h3>
<p><strong>WebLogic 9.2</strong> and above are known to support JMS 1.1. (I don't know what JMS release WebLogic 9.0-9.1 support)</p>
@@ -68,17 +68,17 @@
<p>The J2EE Connector approach has not be specifically tested, but should work well. It would need some additional classes to support the security and management integration as described in the next section, so those would need to be added to a JAR which is in turn added to the J2EE Connector RAR file. <em>Please report your results if you try this</em></p>
-<h3 id="WebLogicIntegration-WebLogicExpressversionsincludingJMS1.1.1">WebLogic Express versions including JMS 1.1</h3>
+<h3>WebLogic Express versions including JMS 1.1</h3>
<p><strong>WebLogic 9.2</strong> and above are known to support JMS 1.1. (I don't know what JMS release WebLogic 9.0-9.1 support)</p>
<p>Since WebLogic Express does not support J2EE Connectors, it is necessary to deploy ActiveMQ wrapped in an application that is deployed to WebLogic. Note that ActiveMQ runs in the XBean container, so XBean must be pointed to an appropriate configuration file to start up and it will then configure and start all the ActiveMQ components. The first challenge is then to construct an application that locates the right config file(s) and starts the ActiveMQ broker when it is deployed.</p>
-<h4 id="WebLogicIntegration-ActiveMQasaWebLogicApplication">ActiveMQ as a WebLogic Application</h4>
+<h4>ActiveMQ as a WebLogic Application</h4>
<p>The easiest type of WebLogic application to configure with all the needed ActiveMQ libraries and configuration and not much else is a web application. The JARs go in <code>WEB-INF/lib/</code> and config files typically in <code>WEB-INF/</code>. The only necessary configuration for the web application itself is to install a listener that will start and stop ActiveMQ when the web application is started and stopped. There are also a couple optional classes that can be used to integrate ActiveMQ with WebLogic's security system. Additionally, in this example, a simple web page included in the WAR will be available whenever ActiveMQ is running, so a simple HTTP request can determine whether the ActiveMQ module has been started.</p>
-<h4 id="WebLogicIntegration-ManagementOptions">Management Options</h4>
+<h4>Management Options</h4>
<p>ActiveMQ exposes a number of management and monitoring features via JMX. There are three ways to expose these JMX objects:</p>
<ol><li>Have ActiveMQ start its own JMX MBeanServer and network connector (typically on port 1099)</li><li>Have ActiveMQ use the JVM's MBeanServer (for Java 5 and higher, either Sun VM or JRockit VM)</li><li>Have ActiveMQ use the MBeanServer provided by a runtime environment such as WebLogic</li></ol>
@@ -90,23 +90,23 @@
<p>The sample below includes an optional configuration block that lets ActiveMQ hook into the WebLogic runtime MBeanServer. This means ActiveMQ MBeans will appear alongside WebLogic MBeans (and even JVM MBeans if they are enabled). With this approach, management clients will access ActiveMQ MBeans through the normal WebLogic listen port (e.g. 7001) rather than using a dedicated JMX port, though IIOP must be enabled for this to work. However, note that this is optional, and you can skip that configuration block and use one of the other approaches (JVM or embedded MBeanServer) to expose the ActiveMQ MBeans.</p>
-<h4 id="WebLogicIntegration-SecurityOptions">Security Options</h4>
+<h4>Security Options</h4>
<p>ActiveMQ has optional authentication and authorization plugins, which are based on JAAS. Fortunately, WebLogic provides a JAAS LoginModule that performs the authentication against the default WebLogic security realm, and returns the appropriate principals for authorization. Unfortunately, by default, ActiveMQ cannot authorize access to specific users within the security realm based on WebLogic principals, meaning either there's no security or a login is required but any user with a valid login has full access to ActiveMQ. However, with custom security classes like the ones shown below, ActiveMQ can use the WebLogic security realm to process a login and then you can configure the WebLogic principals (users and/or groups) that should be allowed to perform read/write/create/remove actions on a per-broker or per-destination basis.</p>
<p>You may choose to use authentication only, in which case any user with a valid WebLogic login can access ActiveMQ, and no custom code is necessary. You may also add authorization to that using some custom code, to apply specific security constraints to specific users or destinations. For purposes of this example, we have only implemented an authorization approach that allows any member of a single specific WebLogic group to access all resources in ActiveMQ. Between the authorization plugin provided here and the default one provided with ActiveMQ, you should have the foundation to enhance this if more feature-rich authorization is required.</p>
-<h4 id="WebLogicIntegration-PersistenceOptions">Persistence Options</h4>
+<h4>Persistence Options</h4>
<p>ActiveMQ uses a combination of a local journal (files on the file system) and a backing database by default. In the standard configuration, an embedded Derby database is used. This runs fine in WebLogic, but it's also possible to have ActiveMQ use a database connection pool defined in WebLogic, rather than using a separate Derby database. The configuration files shown later have commented-out sections referring to a WebLogic database connection pool – if you want to use those, you'll just need to set the correct JNDI name that was used for the database connection pool.</p>
<p>Note that ActiveMQ will create the tables it needs the first time it connects to a database, so no particular preparation is required for the database.</p>
-<h4 id="WebLogicIntegration-ActiveMQIntegrationArchitecture">ActiveMQ Integration Architecture</h4>
+<h4>ActiveMQ Integration Architecture</h4>
<p>The ActiveMQ-in-WebLogic combination looks like this:</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="weblogic-integration.data/activemq-in-weblogic.png" data-image-src="/confluence/download/attachments/36089/activemq-in-weblogic.png?version=1&modificationDate=1156951323000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3274" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="activemq-in-weblogic.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="36089" data-linked-resource-container-version="11"></span></p>
+<p><image><attachment ri:filename="activemq-in-weblogic.png"></attachment></image></p>
<p>To summarize this diagram:</p>
<ul><li>ActiveMQ runs as a web application, which runs in the web container inside WebLogic Express</li><li>ActiveMQ reads two configuration files from a directory on the WebLogic class path – one to configure ActiveMQ itself, and one to configure its logging output</li><li>ActiveMQ uses two main resources from WebLogic Express – the JMX management server (MBeanServer) and the WebLogic security realm (in the form of a JAAS LoginModule).</li><li>In order to start ActiveMQ when the web application is deployed, the <code>web.xml</code> includes a context listener for Spring, and the Spring <code>applicationContext.xml</code> file loads the ActiveMQ broker and points it to the ActiveMQ configuration file (which as mentioned above, is stored in a directory on the class path).</li><li>Within ActiveMQ:
@@ -114,46 +114,42 @@
</li><li>Note that ActiveMQ uses its own threads; since WebLogic Express does not support J2EE Connectors, it is not possible for ActiveMQ to access a WebLogic thread pool without more extensive customization</li></ul>
-<h4 id="WebLogicIntegration-BuildingtheActiveMQtoWebLogicIntegrationWAR">Building the ActiveMQ to WebLogic Integration WAR</h4>
+<h4>Building the ActiveMQ to WebLogic Integration WAR</h4>
<p>This section discusses the code, libraries, and configuration files necessary to build the ActiveMQ web application that will be deployed in WebLogic Express.</p>
-<h5 id="WebLogicIntegration-StartingandStoppingActiveMQ">Starting and Stopping ActiveMQ</h5>
+<h5>Starting and Stopping ActiveMQ</h5>
<p>ActiveMQ needs to start when the web application is deployed or started, and stop when the web application is stopped or undeployed. The easiest way to do this is to a use the commonly available Spring listeners, which start a Spring context, which can point ActiveMQ to an XBean configuration file, which starts ActiveMQ. A little roundabout, but it works well in practice with very little configuration.</p>
<p><strong>J2EE WEB-INF/web.xml</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
+<structured-macro ac:macro-id="05b618ba-3964-4b87-92a9-9f730a3b31d9" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
-<web-app version="2.4"
- xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" >
+<web-app version="2.4"
+ xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" >
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
</web-app>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p><strong>Spring WEB-INF/applicationContext.xml</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8" ?>
-<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
+<structured-macro ac:macro-id="b38d9c7f-bdb3-4ded-b1ef-16960374bd59" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8" ?>
+<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
- <bean id="brokerService" class="org.apache.activemq.xbean.BrokerFactoryBean">
- <property name="config" value="classpath:activemq-config.xml"/>
+ <bean id="brokerService" class="org.apache.activemq.xbean.BrokerFactoryBean">
+ <property name="config" value="classpath:activemq-config.xml"/>
</bean>
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>Again, the <code>web.xml</code> listener starts Spring and reads the Spring <code>META-INF/applicationContext.xml</code> file (the default location used by the <code>ContextLoaderListener</code>), and the <code>applicationContext.xml</code> indicates that the ActiveMQ configuration file should be read from the class path with the name <code>activemq-config.xml</code>. That file could be placed in <code>WEB-INF/classes</code> or in a directory on the file system that is added to the WebLogic class path (for ease of editing).</p>
<p>With this approach, the normal WebLogic deployment tools, admin console, etc. can be used to deploy, start, stop, and restart ActiveMQ (packaged into a web application WAR).</p>
-<h5 id="WebLogicIntegration-RequiredLibraries">Required Libraries</h5>
+<h5>Required Libraries</h5>
<p>ActiveMQ required a number of JARs which should be included in the web application <code>WEB-INF/lib</code> directory. </p>
@@ -165,7 +161,7 @@
<p>Of these, Derby could be omitted if ActiveMQ was configured to not use a database for persistence or to use a separate database (e.g. a WebLogic database pool) for persistence. The WebLogic JAR is needed only at build time (it's provided by the server at runtime). Spring could be omitted if a different strategy was used to start and stop ActiveMQ when the web app was started or stopped (a little custom code could replace this dependency). The rest are probably unavoidable, unless ActiveMQ changes its dependencies in a future version.</p>
-<h5 id="WebLogicIntegration-WebLogicIntegrationCode">WebLogic Integration Code</h5>
+<h5>WebLogic Integration Code</h5>
<p>There are two custom classes used for this example. We'll show in a minute how to configure ActiveMQ to use these. Note that these are optional – if you don't want to leverage WebLogic's security realm, you can skip these.</p>
@@ -175,8 +171,7 @@
<p>This class is an ActiveMQ "plugin", which installs two filters (authorization and authentication) which will be invoked on every request. This is similar to the default behavior provided by ActiveMQ's <code>JaasAuthenticationPlugin</code> and <code>AuthorizationPlugin</code>.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="bf4bb8ea-f777-40b5-893d-f98a0b1a12ae" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
/**
* An ActiveMQ security plugin that installs two security filters
* (authentication and authorization) that use WebLogic security realms to
@@ -214,15 +209,13 @@
this.authorizedGroup = authorizedGroup;
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The second class is the authentication filter used by the class above to authenticate all logins against the WebLogic default security realm.</p>
<p><strong>ActiveMQWebLogicAuthenticationFilter.java</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="07bc33d8-59bf-43bf-9a76-3944357daa97" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>
/**
* A broker filter that authenticates callers against WebLogic security.
* This is similar to the ActiveMQ JaasAuthenticationBroker except for two
@@ -243,7 +236,7 @@
private final static Configuration WEBLOGIC_JAAS_CONFIGURATION = new Configuration() {
public AppConfigurationEntry[] getAppConfigurationEntry(String name) {
return new AppConfigurationEntry[]{
- new AppConfigurationEntry("weblogic.security.auth.login.UsernamePasswordLoginModule",
+ new AppConfigurationEntry("weblogic.security.auth.login.UsernamePasswordLoginModule",
AppConfigurationEntry.LoginModuleControlFlag.REQUIRED, Collections.EMPTY_MAP)
};
}
@@ -295,7 +288,7 @@
if( context.getSecurityContext()==null ) {
// Do the login.
try {
- LoginContext lc = new LoginContext("ActiveMQ", new Subject(),
+ LoginContext lc = new LoginContext("ActiveMQ", new Subject(),
new URLCallbackHandler(info.getUserName(), info.getPassword()),
WEBLOGIC_JAAS_CONFIGURATION);
lc.login();
@@ -305,7 +298,7 @@
context.setSecurityContext(s);
securityContexts.add(s);
} catch (Exception e) {
- throw (SecurityException)new SecurityException("User name or password is invalid.").initCause(e);
+ throw (SecurityException)new SecurityException("User name or password is invalid.").initCause(e);
}
}
super.addConnection(context, info);
@@ -330,34 +323,32 @@
}
}
}
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h5 id="WebLogicIntegration-SampleActiveMQConfigurationFiles">Sample ActiveMQ Configuration Files</h5>
+<h5>Sample ActiveMQ Configuration Files</h5>
<p>This section shows three sample ActiveMQ configuration files – one for a single broker with the security and management plugins listed above, and one for a network of two brokers with the security and management plugins listed above. If you want to skip the security and management plugins, you can remove those attributes from the main <code><broker></code> element and remove the <code><bean></code> definitions for them below.</p>
<p>It also shows a Log4J configuration file, which controls the ActiveMQ log output.</p>
<p><strong>Single Broker</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<structured-macro ac:macro-id="6047c8fc-df5e-4cc8-8b72-e9ec9817cd34" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
+<beans xmlns="http://activemq.org/config/1.0">
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" brokerName="MyBroker" useShutdownHook="false"
- plugins="#WebLogicSecurity">
+ <broker useJmx="true" brokerName="MyBroker" useShutdownHook="false"
+ plugins="#WebLogicSecurity">
<!-- Register all ActiveMQ MBeans with the WebLogic runtime MBeanServer -->
<managementContext>
<managementContext>
<MBeanServer>
- <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
- <property name="jndiName" value="java:comp/env/jmx/runtime" />
- <property name="lookupOnStartup" value="true" />
- <property name="expectedType" value="javax.management.MBeanServer" />
+ <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
+ <property name="jndiName" value="java:comp/env/jmx/runtime" />
+ <property name="lookupOnStartup" value="true" />
+ <property name="expectedType" value="javax.management.MBeanServer" />
</bean>
</MBeanServer>
</managementContext>
@@ -365,57 +356,55 @@
<persistenceAdapter>
<!-- By default, use an embedded Derby database -->
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-data"/>
+ <journaledJDBC journalLogFiles="5"
+ dataDirectory="/server/bea/weblogic920/domains/jms/activemq-data"/>
<!-- Use this with the WebLogicDataSource below to use a WebLogic
database connection pool instead of the embedded Derby database
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-data"
- dataSource="#WebLogicDataSource" />
+ <journaledJDBC journalLogFiles="5"
+ dataDirectory="/server/bea/weblogic920/domains/jms/activemq-data"
+ dataSource="#WebLogicDataSource" />
-->
</persistenceAdapter>
<transportConnectors>
- <transportConnector name="MyBrokerTCP" uri="tcp://0.0.0.0:61616" />
+ <transportConnector name="MyBrokerTCP" uri="tcp://0.0.0.0:61616" />
</transportConnectors>
</broker>
- <bean id="WebLogicSecurity"
- class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
- <property name="authorizedGroup" value="ActiveMQUsers" />
+ <bean id="WebLogicSecurity"
+ class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
+ <property name="authorizedGroup" value="ActiveMQUsers" />
</bean>
<!-- Uncomment and configure this if you want to use a WebLogic database
connection pool for persistent messages
- <bean id="WebLogicDataSource"
- class="org.springframework.jndi.JndiObjectFactoryBean">
- <property name="jndiName" value="db/pool/jndi/name"/>
+ <bean id="WebLogicDataSource"
+ class="org.springframework.jndi.JndiObjectFactoryBean">
+ <property name="jndiName" value="db/pool/jndi/name"/>
</bean>
-->
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p><strong>Network of Brokers (Broker 1/2)</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<structured-macro ac:macro-id="da8c3f84-e89b-40b6-b997-434fbeabfa67" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
+<beans xmlns="http://activemq.org/config/1.0">
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" brokerName="FirstBroker" useShutdownHook="false"
- plugins="#WebLogicSecurity">
+ <broker useJmx="true" brokerName="FirstBroker" useShutdownHook="false"
+ plugins="#WebLogicSecurity">
<!-- Register all ActiveMQ MBeans with the WebLogic runtime MBeanServer -->
<managementContext>
<managementContext>
<MBeanServer>
- <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
- <property name="jndiName" value="java:comp/env/jmx/runtime" />
- <property name="lookupOnStartup" value="true" />
- <property name="expectedType" value="javax.management.MBeanServer" />
+ <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
+ <property name="jndiName" value="java:comp/env/jmx/runtime" />
+ <property name="lookupOnStartup" value="true" />
+ <property name="expectedType" value="javax.management.MBeanServer" />
</bean>
</MBeanServer>
</managementContext>
@@ -423,63 +412,61 @@
<persistenceAdapter>
<!-- By default, use an embedded Derby database -->
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b1-data"/>
+ <journaledJDBC journalLogFiles="5"
+ dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b1-data"/>
<!-- Use this with the WebLogicDataSource below to use a WebLogic
database connection pool instead of the embedded Derby database
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b1-data"
- dataSource="#WebLogicDataSource" />
+ <journaledJDBC journalLogFiles="5"
+ dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b1-data"
+ dataSource="#WebLogicDataSource" />
-->
</persistenceAdapter>
<transportConnectors>
- <transportConnector name="FirstBrokerTCP" uri="tcp://0.0.0.0:60010" />
+ <transportConnector name="FirstBrokerTCP" uri="tcp://0.0.0.0:60010" />
</transportConnectors>
<networkConnectors>
- <networkConnector name="Broker1ToBroker2"
- uri="static://(tcp://localhost:60011)" failover="true"
- userName="fixme" password="fixme"/>
+ <networkConnector name="Broker1ToBroker2"
+ uri="static://(tcp://localhost:60011)" failover="true"
+ userName="fixme" password="fixme"/>
</networkConnectors>
</broker>
- <bean id="WebLogicSecurity"
- class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
- <property name="authorizedGroup" value="ActiveMQUsers" />
+ <bean id="WebLogicSecurity"
+ class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
+ <property name="authorizedGroup" value="ActiveMQUsers" />
</bean>
<!-- Uncomment and configure this if you want to use a WebLogic database
connection pool for persistent messages
- <bean id="WebLogicDataSource"
- class="org.springframework.jndi.JndiObjectFactoryBean">
- <property name="jndiName" value="db/pool/jndi/name"/>
+ <bean id="WebLogicDataSource"
+ class="org.springframework.jndi.JndiObjectFactoryBean">
+ <property name="jndiName" value="db/pool/jndi/name"/>
</bean>
-->
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p><strong>Network of Brokers (Broker 2/2)</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://activemq.org/config/1.0">
+<structured-macro ac:macro-id="e01f5ebf-021d-470d-9558-a4ceb9913054" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body>
+<?xml version="1.0" encoding="UTF-8"?>
+<beans xmlns="http://activemq.org/config/1.0">
<!-- Allows us to use system properties as variables in this configuration file -->
- <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
+ <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>
- <broker useJmx="true" brokerName="SecondBroker" useShutdownHook="false"
- plugins="#WebLogicSecurity">
+ <broker useJmx="true" brokerName="SecondBroker" useShutdownHook="false"
+ plugins="#WebLogicSecurity">
<!-- Register all ActiveMQ MBeans with the WebLogic runtime MBeanServer -->
<managementContext>
<managementContext>
<MBeanServer>
- <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
- <property name="jndiName" value="java:comp/env/jmx/runtime" />
- <property name="lookupOnStartup" value="true" />
- <property name="expectedType" value="javax.management.MBeanServer" />
+ <bean class="org.springframework.jndi.JndiObjectFactoryBean" xmlns="">
+ <property name="jndiName" value="java:comp/env/jmx/runtime" />
+ <property name="lookupOnStartup" value="true" />
+ <property name="expectedType" value="javax.management.MBeanServer" />
</bean>
</MBeanServer>
</managementContext>
@@ -487,48 +474,46 @@
<persistenceAdapter>
<!-- By default, use an embedded Derby database -->
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b2-data"/>
+ <journaledJDBC journalLogFiles="5"
+ dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b2-data"/>
<!-- Use this with the WebLogicDataSource below to use a WebLogic
database connection pool instead of the embedded Derby database
- <journaledJDBC journalLogFiles="5"
- dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b2-data"
- dataSource="#WebLogicDataSource" />
+ <journaledJDBC journalLogFiles="5"
+ dataDirectory="/server/bea/weblogic920/domains/jms/activemq-b2-data"
+ dataSource="#WebLogicDataSource" />
-->
</persistenceAdapter>
<transportConnectors>
- <transportConnector name="SecondBrokerTCP" uri="tcp://0.0.0.0:60011" />
+ <transportConnector name="SecondBrokerTCP" uri="tcp://0.0.0.0:60011" />
</transportConnectors>
<networkConnectors>
- <networkConnector name="Broker2ToBroker1"
- uri="static://(tcp://localhost:60010)" failover="true"
- userName="fixme" password="fixme" />
+ <networkConnector name="Broker2ToBroker1"
+ uri="static://(tcp://localhost:60010)" failover="true"
+ userName="fixme" password="fixme" />
</networkConnectors>
</broker>
- <bean id="WebLogicSecurity"
- class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
- <property name="authorizedGroup" value="activemq" />
+ <bean id="WebLogicSecurity"
+ class="com.example.activemq.weblogic.ActiveMQToWebLogicSecurity">
+ <property name="authorizedGroup" value="activemq" />
</bean>
<!-- Uncomment and configure this if you want to use a WebLogic database
connection pool for persistent messages
- <bean id="WebLogicDataSource"
- class="org.springframework.jndi.JndiObjectFactoryBean">
- <property name="jndiName" value="db/pool/jndi/name"/>
+ <bean id="WebLogicDataSource"
+ class="org.springframework.jndi.JndiObjectFactoryBean">
+ <property name="jndiName" value="db/pool/jndi/name"/>
</bean>
-->
</beans>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p><strong>Log4J Configuration File (<code>log4j.properties</code>)</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-# Can change this to "INFO, out" or "INFO, out, stdout"
+<structured-macro ac:macro-id="28f18411-225c-4d43-9dac-267f83691154" ac:name="code" ac:schema-version="1"><plain-text-body>
+# Can change this to "INFO, out" or "INFO, out, stdout"
# to enable logging to the file defined down below
log4j.rootLogger=INFO, stdout
log4j.logger.org.apache.activemq.spring=WARN
@@ -549,10 +534,9 @@
log4j.appender.out.append=true
log4j.appender.out.layout=org.apache.log4j.PatternLayout
log4j.appender.out.layout.ConversionPattern=%d [%-15.15t] %-5p %-30.30c{1} - %m%n
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h4 id="WebLogicIntegration-InstallationProcedure">Installation Procedure</h4>
+<h4>Installation Procedure</h4>
<p>This procedure makes the following assumptions:</p>
<ul><li>The ActiveMQ configuration file and Log4J configuration file will be stored in a subdirectory of the WebLogic domain directory for ease of editing. They may be packaged into <code>WEB-INF/classes</code> in the WAR for ease of distribution instead.</li><li>The ActiveMQ JMX management features will be exposed via the WebLogic runtime JMX MBeanServer. This is not required, but it should allow existing WebLogic management scripts to see the ActiveMQ MBeans. <em>NOTE: Additional configuration is required if the Sun JVM JMX server or JRockit management server will be used instead, or if the embedded ActiveMQ JMX server will be used instead and more than one ActiveMQ instance will be run on the same server.</em></li><li>ActiveMQ will be installed on a single WebLogic instance or on two WebLogic instances in a Network-of-Brokers configuration.
@@ -566,12 +550,11 @@
<p>Installation Procedure</p>
<ol><li>Create a subdirectory of the WebLogic domain directory to hold ActiveMQ config files (e.g. <code>domain-dir/activemq/config</code>)</li><li>Create a subdirectory of the WebLogic domain directory to hold ActiveMQ runtime data – persistent messages, etc. (e.g. <code>domain-dir/activemq/data</code>)</li><li>Edit the <code>activemq-config.xml</code> to point to the correct runtime data directory created in step 2 (look for the part of the file that reads <code>dataDirectory="..."</code>)</li><li>In <code>activemq-config.xml</code>, review the port for the current ActiveMQ server defined in the <code><transportConnector .../></code> line, if ActiveMQ clustering will be used, review the hostname and port for the other ActiveMQ server(s) in the cluster defined in the <code><networkConnector .../></code> line.</li><li>If ActiveMQ clustering and security are both enabled, in <code>activemq-config.xml</code>, find (or add) the <code>userName</code> and <code>password</code> settings on the <code><networkConnector .../></code> and change them to valid values. (When security is enabled, the ActiveMQ brokers in a cluster require valid logins to connect to each other to form the cluster.)</li><li>If security is enabled, in <code>activemq-config.xml</code>, find the <code>authorizedGroup</code> setting on the <code>WebLogicSecurity</code> bean and set that to the name of the WebLogic group whose members should be able to access ActiveMQ. Note that the account used by the network connectors in the previous step must be members of this group. (This entry in the config file is described in the previous section)</li><li>(Optional) Update the <code>log4j.properties</code> file to save ActiveMQ logs to a file rather than just emitting to the WebLogic server's standard output (e.g. change the first line to <code>log4j.rootLogger=INFO, out, stdout</code> and change the destination file in the <code>log4j.appender.out.file=...</code> line)</li><li>Save the <code>activemq-config.xml</code> and <code>log4j.properties</code> files to the ActiveMQ configuration directory created in step 1</li><li>Edit the <code>startWebLogic.sh</code> file in the domain directory and add the following line to the top (immediately after the <code>DOMAIN_HOME=...</code> line), adjusting the line to use the directory created in step 1:
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>export EXT_POST_CLASSPATH=${DOMAIN_HOME}/activemq/config
-</pre>
-</div></div></li><li>Start WebLogic</li><li>Deploy the <code>activemq-4.0.1-web.war</code> file, by copying it to the <code>domain-dir/autodeploy</code> directory or using the deployment tools in the WebLogic console.</li><li>Verify that the WebLogic server standard output (or the ActiveMQ log file configured in step 5) shows that ActiveMQ started, with output like this:
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker (localhost) is starting
+<structured-macro ac:macro-id="2329189d-2639-4c66-9828-e82e68691b27" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+export EXT_POST_CLASSPATH=${DOMAIN_HOME}/activemq/config
+</plain-text-body></structured-macro></li><li>Start WebLogic</li><li>Deploy the <code>activemq-4.0.1-web.war</code> file, by copying it to the <code>domain-dir/autodeploy</code> directory or using the deployment tools in the WebLogic console.</li><li>Verify that the WebLogic server standard output (or the ActiveMQ log file configured in step 5) shows that ActiveMQ started, with output like this:
+<structured-macro ac:macro-id="a4b30fd3-4026-4386-beac-742f6f8ce5f6" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+INFO BrokerService - ActiveMQ 4.0.1 JMS Message Broker (localhost) is starting
INFO BrokerService - For help or more information please see:
http://incubator.apache.org/activemq/
INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver]
@@ -582,11 +565,10 @@
INFO TransportConnector - Connector default Started
INFO BrokerService - ActiveMQ JMS Message Broker
(localhost, ID:remus-28763-1156532531109-1:0) started
-</pre>
-</div></div></li><li>Test a management connection by running the <code>jconsole</code> tool distributed with Java 5, using an advanced connection, entering the URL <code>service:jmx:rmi:///jndi/iiop://localhost:7001/weblogic.management.mbeanservers.runtime</code> (adjusting <code>localhost:7001</code> to the WebLogic server hostname and port) and the WebLogic administrator username and password. Once connected, on the MBeans tab, there should be entries under <code>org/activemq</code></li><li>Test a security if desired by running the example producer and consumer from an ActiveMQ 4.0.1 distribution. Note that the connect URL is in <code>examples/build.xml</code> while the connect username and password need to be added to <code>examples/src/ConsumerTool.java</code> and <code>examples/src/ProducerTool.java</code> to connect successfully to a secure instance.</li><li>If ActiveMQ clustering will be used, repeat this process for the other WebLogic/ActiveMQ instance in the cluster. This should set up the two ActiveMQ servers to connect to each other. Confirm this by looking for output like this once both brokers are running:
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>INFO DemandForwardingBridge - Network connection between vm://FirstBroker#0 and
+</plain-text-body></structured-macro></li><li>Test a management connection by running the <code>jconsole</code> tool distributed with Java 5, using an advanced connection, entering the URL <code>service:jmx:rmi:///jndi/iiop://localhost:7001/weblogic.management.mbeanservers.runtime</code> (adjusting <code>localhost:7001</code> to the WebLogic server hostname and port) and the WebLogic administrator username and password. Once connected, on the MBeans tab, there should be entries under <code>org/activemq</code></li><li>Test a security if desired by running the example producer and consumer from an ActiveMQ 4.0.1 distribution. Note that the connect URL is in <code>examples/build.xml</code> while the connect username and password need to be added to <code>examples/src/ConsumerTool.java</code> and <code>examples/src/ProducerTool.java</code> to connect successfully to a secure instance.</li><li>If ActiveMQ clustering will be used, repeat this process for the other WebLogic/ActiveMQ instance in the cluster. This should set up the two ActiveMQ servers to connect to each other. Confirm this by looking for output like this once both brokers are running:
+<structured-macro ac:macro-id="dfcfe7a8-5052-46e8-bec0-5e4a85b635d2" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+INFO DemandForwardingBridge - Network connection between vm://FirstBroker#0 and
tcp://localhost:63222(SecondBroker) has been established.
-</pre>
-</div></div></li></ol></div>
+</plain-text-body></structured-macro></li></ol>
+</div>
diff --git a/websockets.xml b/websockets.xml
index 69118f5..e1dccd5 100644
--- a/websockets.xml
+++ b/websockets.xml
@@ -1,65 +1,60 @@
-<div class="wiki-content maincontent"><h1 id="WebSockets-Introduction">Introduction</h1>
-<p>Besides <a shape="rect" href="ajax.xml">Ajax</a> API, starting with version <strong>5.4.0</strong> onwards, you can use HTML5 <a shape="rect" class="external-link" href="http://dev.w3.org/html5/websockets/" rel="nofollow">WebSockets</a> to exchange messages with the broker from your browser. </p>
+<div class="wiki-content maincontent"><h1>Introduction</h1>
+<p>Besides <link><page ri:content-title="Ajax"></page></link> API, starting with version <strong>5.4.0</strong> onwards, you can use HTML5 <a shape="rect" href="http://dev.w3.org/html5/websockets/">WebSockets</a> to exchange messages with the broker from your browser. </p>
-<p>HTML 5 introduced web sockets, as a standardized way to communicate asynchronously with the server from a web page. This is practically an ideal channel for implementing asynchronous messaging for web pages. Since JavaScript easily handles text and JSON formatted data, <a shape="rect" class="external-link" href="http://activemq.apache.org/stomp/">Stomp</a> protocol is a good choice for the wire protocol to be used over web sockets. Since version <strong>5.9.0</strong>, we also support efficient binary MQTT protocol over Web sockets.</p>
+<p>HTML 5 introduced web sockets, as a standardized way to communicate asynchronously with the server from a web page. This is practically an ideal channel for implementing asynchronous messaging for web pages. Since JavaScript easily handles text and JSON formatted data, <a shape="rect" href="http://activemq.apache.org/stomp/">Stomp</a> protocol is a good choice for the wire protocol to be used over web sockets. Since version <strong>5.9.0</strong>, we also support efficient binary MQTT protocol over Web sockets.</p>
<p>This solution should bring better messaging capabilities to JavaScript clients then simple Ajax API, as implementing Stomp or MQTT in JavaScript brings much more messaging-oriented API and features such as transactions, for example.</p>
-<h1 id="WebSockets-Configuration">Configuration</h1>
+<h1>Configuration</h1>
<p>ActiveMQ comes with <em>WebSocket</em> transport which implements Stomp over WebSockets functionality.</p>
<p>To configure it, you need to place something like this to your ActiveMQ configuration file</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnectors>
- <transportConnector name="websocket" uri="ws://0.0.0.0:61614"/>
-</transportConnectors>]]></script>
-</div></div>
+<structured-macro ac:macro-id="180101a5-7751-46e0-a63e-058c298b448e" ac:name="code" ac:schema-version="1"><plain-text-body><transportConnectors>
+ <transportConnector name="websocket" uri="ws://0.0.0.0:61614"/>
+</transportConnectors></plain-text-body></structured-macro>
<p>One thing worth noting is that web sockets (just as Ajax) implements the <em>same origin policy</em>, so you can access only brokers running on the same host as the web application running the client.</p>
-<h1 id="WebSockets-SecureWebSockets">Secure Web Sockets</h1>
+<h1>Secure Web Sockets</h1>
<p>Version 5.7.0 introduced <em>Secure Web Socket</em> transport. To configure it you need two things. First, you need to configure a new transport connector like this</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<transportConnectors>
- <transportConnector name="secure_websocket" uri="wss://0.0.0.0:61614"/>
-</transportConnectors>]]></script>
-</div></div>
+<structured-macro ac:macro-id="a6eac470-f23e-4712-9e84-de9576dde0af" ac:name="code" ac:schema-version="1"><plain-text-body><transportConnectors>
+ <transportConnector name="secure_websocket" uri="wss://0.0.0.0:61614"/>
+</transportConnectors></plain-text-body></structured-macro>
<p>Note that we use <em>wss</em> url prefix to denote a secured version of the protocol. Next you need to provide SSL context for this transport. You can do that by providing <em>sslContext</em> in your broker configuration in a similar fashion as you'd do for <em>ssl</em> or <em>https</em> transports.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<sslContext>
- <sslContext keyStore="file:${activemq.conf}/broker.ks"
- keyStorePassword="password" trustStore="file:${activemq.conf}/broker.ts"
- trustStorePassword="password"
+<structured-macro ac:macro-id="22509a3c-0762-4f83-9cd8-6c6b01ced6c3" ac:name="code" ac:schema-version="1"><plain-text-body><sslContext>
+ <sslContext keyStore="file:${activemq.conf}/broker.ks"
+ keyStorePassword="password" trustStore="file:${activemq.conf}/broker.ts"
+ trustStorePassword="password"
/>
-</sslContext>]]></script>
-</div></div>
+</sslContext></plain-text-body></structured-macro>
<p>That's it, your secure websocket transport is ready. Take a look at the next section to see how to use a demo to test it out.</p>
-<h1 id="WebSockets-Demos">Demos</h1>
+<h1>Demos</h1>
-<p>As of version 5.6.0, an adapted demo of <a shape="rect" class="external-link" href="http://github.com/jmesnil/stomp-websocket" rel="nofollow">stomp-websocket</a> library is integrated with ActiveMQ web demo application. <br clear="none">
-As of version 5.9.0, we have a similar demo using MQTT and <a shape="rect" class="external-link" href="http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git" rel="nofollow">Eclipse Paho client</a></p>
+<p>As of version 5.6.0, an adapted demo of <a shape="rect" href="http://github.com/jmesnil/stomp-websocket">stomp-websocket</a> library is integrated with ActiveMQ web demo application. <br clear="none">
+As of version 5.9.0, we have a similar demo using MQTT and <a shape="rect" href="http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git">Eclipse Paho client</a></p>
<p>To see demos:</p>
-<ul><li>Start the broker with <code>ws</code> transport (you can use activemq-demo.xml configuration for that)</li><li>Go to <a shape="rect" class="external-link" href="http://localhost:8161/demo/websocket" rel="nofollow">http://localhost:8161/demo/websocket</a> to check Stomp example</li><li>Go to <a shape="rect" class="external-link" href="http://localhost:8161/demo/mqtt" rel="nofollow">http://localhost:8161/demo/mqtt</a> to check MQTT example</li></ul>
+<ul><li>Start the broker with <code>ws</code> transport (you can use activemq-demo.xml configuration for that)</li><li>Go to <a shape="rect" href="http://localhost:8161/demo/websocket">http://localhost:8161/demo/websocket</a> to check Stomp example</li><li>Go to <a shape="rect" href="http://localhost:8161/demo/mqtt">http://localhost:8161/demo/mqtt</a> to check MQTT example</li></ul>
-<h1 id="WebSockets-Clients">Clients</h1>
+<h1>Clients</h1>
-<ul><li><a shape="rect" class="external-link" href="http://github.com/krukow/stomple" rel="nofollow">Stomple</a> by <a shape="rect" class="external-link" href="http://blog.higher-order.net/" rel="nofollow">Karl Krukow</a></li><li><a shape="rect" class="external-link" href="http://github.com/jmesnil/stomp-websocket" rel="nofollow">stomp-websocket</a> by <a shape="rect" class="external-link" href="http://jmesnil.net/weblog/" rel="nofollow">Jeff Mesnil</a></li><li><a shape="rect" class="external-link" href="http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git" rel="nofollow">Eclipse Paho MQTT JavaScript client</a></li></ul>
+<ul><li><a shape="rect" href="http://github.com/krukow/stomple">Stomple</a> by <a shape="rect" href="http://blog.higher-order.net/">Karl Krukow</a></li><li><a shape="rect" href="http://github.com/jmesnil/stomp-websocket">stomp-websocket</a> by <a shape="rect" href="http://jmesnil.net/weblog/">Jeff Mesnil</a></li><li><a shape="rect" href="http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git">Eclipse Paho MQTT JavaScript client</a></li></ul>
-<h1 id="WebSockets-MoreResources">More Resources</h1>
+<h1>More Resources</h1>
-<ul><li><a shape="rect" class="external-link" href="http://www.nighttale.net/activemq/activemq-54-stomp-over-web-sockets.html" rel="nofollow">ActiveMQ 5.4: Stomp over Web Sockets</a></li><li><a shape="rect" class="external-link" href="http://blog.higher-order.net/2010/06/01/stomple-rc1-combining-websockets-and-reliable-messaging/" rel="nofollow">Stomple RC1: Combining WebSockets and Reliable Messaging</a></li><li><a shape="rect" class="external-link" href="http://jmesnil.net/stomp-websocket/doc/" rel="nofollow">Stomp On Web Sockets</a></li></ul>
+<ul><li><a shape="rect" href="http://www.nighttale.net/activemq/activemq-54-stomp-over-web-sockets.html">ActiveMQ 5.4: Stomp over Web Sockets</a></li><li><a shape="rect" href="http://blog.higher-order.net/2010/06/01/stomple-rc1-combining-websockets-and-reliable-messaging/">Stomple RC1: Combining WebSockets and Reliable Messaging</a></li><li><a shape="rect" href="http://jmesnil.net/stomp-websocket/doc/">Stomp On Web Sockets</a></li></ul>
+
diff --git a/what-are-administered-objects.xml b/what-are-administered-objects.xml
index b562b25..ee1f3db 100644
--- a/what-are-administered-objects.xml
+++ b/what-are-administered-objects.xml
@@ -1,15 +1,16 @@
-<div class="wiki-content maincontent"><h2 id="Whatareadministeredobjects-Whatareadministeredobjects?">What are administered objects?</h2>
+<div class="wiki-content maincontent"><h2>What are administered objects?</h2>
-<p>Administered objects refers to objects that are configured in <a shape="rect" href="jndi-support.xml">JNDI</a> and then accessed by a JMS client. So they are simply client-side objects typically either a ConnectionFactory or a Destination (such as a Queue or Topic).</p>
+<p>Administered objects refers to objects that are configured in <link><page ri:content-title="JNDI Support"></page><link-body>JNDI</link-body></link> and then accessed by a JMS client. So they are simply client-side objects typically either a ConnectionFactory or a Destination (such as a Queue or Topic).</p>
-<p>Note that administered objects are only used for JNDI. JNDI can then be used as a level of indirection between the JNDI API and the concrete API of the JMS provider. So looking up objects in JNDI avoids you having a runtime dependency on ActiveMQ. Given that we are only talking about one ConnectionFactory object and a few Destination objects, this is not a huge big deal though <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>Note that administered objects are only used for JNDI. JNDI can then be used as a level of indirection between the JNDI API and the concrete API of the JMS provider. So looking up objects in JNDI avoids you having a runtime dependency on ActiveMQ. Given that we are only talking about one ConnectionFactory object and a few Destination objects, this is not a huge big deal though <emoticon ac:name="smile"></emoticon></p>
<p>Often folks get very confused with JNDI. e.g. in RMI / EJB scenarios JNDI provides client side proxies; this is not the case with JMS, as the JMS client is the client side proxy to the broker.</p>
-<p>An alternative approach to creating administered objects in JNDI is to just use the <a shape="rect" href="spring-support.xml">Spring Support</a> and let dependency injection be an alternative to JNDI.</p>
+<p>An alternative approach to creating administered objects in JNDI is to just use the <link><page ri:content-title="Spring Support"></page></link> and let dependency injection be an alternative to JNDI.</p>
-<h3 id="Whatareadministeredobjects-SeeAlso">See Also</h3>
+<h3>See Also</h3>
-<ul><li><a shape="rect" href="how-do-i-create-new-destinations.xml">How do I create new destinations</a></li><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li><li><a shape="rect" href="how-does-connectionfactory-relate-to-the-broker.xml">How does ConnectionFactory relate to the Broker</a></li></ul>
+<ul><li><link><page ri:content-title="How do I create new destinations"></page></link></li><li><link><page ri:content-title="How do I embed a Broker inside a Connection"></page></link></li><li><link><page ri:content-title="How does ConnectionFactory relate to the Broker"></page></link></li></ul>
+
</div>
diff --git a/what-are-those-topics-activemqadvisory.xml b/what-are-those-topics-activemqadvisory.xml
index bdca5f3..6ae9125 100644
--- a/what-are-those-topics-activemqadvisory.xml
+++ b/what-are-those-topics-activemqadvisory.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>When you look at a broker using <a shape="rect" href="jmx.xml">JMX</a> you will see a number of topics starting with <strong>ActiveMQ.Advisory.</strong>. These are the destinations used by the <a shape="rect" href="advisory-message.xml">Advisory Message</a> feature of ActiveMQ which allows you to listen to the behaviour of the system.</p></div>
+<div class="wiki-content maincontent"><p>When you look at a broker using <link><page ri:content-title="JMX"></page></link> you will see a number of topics starting with <strong>ActiveMQ.Advisory.</strong>. These are the destinations used by the <link><page ri:content-title="Advisory Message"></page></link> feature of ActiveMQ which allows you to listen to the behaviour of the system.</p></div>
diff --git a/what-happens-with-a-fast-producer-and-slow-consumer.xml b/what-happens-with-a-fast-producer-and-slow-consumer.xml
index cdc43a4..2996c32 100644
--- a/what-happens-with-a-fast-producer-and-slow-consumer.xml
+++ b/what-happens-with-a-fast-producer-and-slow-consumer.xml
@@ -1,7 +1,7 @@
<div class="wiki-content maincontent">
-<p>It depends a little on the <a shape="rect" href="qos.xml">QoS</a> but in general we implement <em>flow control</em> which means that when we have a very fast producer and a slow consumer, when we get to a high water mark of outstanding messages we will start to tell the producer to slow down (which occurs inside the JMS client automatically, no application code changes are required). The slow down messages will increase exponentially over time until things get back into balance again.</p>
+<p>It depends a little on the <link><page ri:content-title="QoS"></page></link> but in general we implement <em>flow control</em> which means that when we have a very fast producer and a slow consumer, when we get to a high water mark of outstanding messages we will start to tell the producer to slow down (which occurs inside the JMS client automatically, no application code changes are required). The slow down messages will increase exponentially over time until things get back into balance again.</p>
<p>Flow control avoids unnecessary resouce exhaustion and is particularly useful in non-durable messaging modes to avoid running out of memory / disk on a node.</p></div>
diff --git a/what-is-the-difference-between-a-virtual-topic-and-a-composite-destination.xml b/what-is-the-difference-between-a-virtual-topic-and-a-composite-destination.xml
index 62e517a..9e16b79 100644
--- a/what-is-the-difference-between-a-virtual-topic-and-a-composite-destination.xml
+++ b/what-is-the-difference-between-a-virtual-topic-and-a-composite-destination.xml
@@ -1,12 +1,13 @@
-<div class="wiki-content maincontent"><h2 id="WhatisthedifferencebetweenaVirtualTopicandaCompositeDestination-WhatisthedifferencebetweenaVirtualTopicandaCompositeDestination">What is the difference between a Virtual Topic and a Composite Destination</h2>
+<div class="wiki-content maincontent"><h2>What is the difference between a Virtual Topic and a Composite Destination</h2>
-<p>Both kinds of <a shape="rect" href="virtual-destinations.xml">Virtual Destinations</a> offer similar capabilities, namely that the producer sees a single Destination to send to and the consumer sees a different Destination to consume from and there can be a many to many map of producer Destination to many different consumer destinations (as well as a mix of Topics and Queues.</p>
+<p>Both kinds of <link><page ri:content-title="Virtual Destinations"></page></link> offer similar capabilities, namely that the producer sees a single Destination to send to and the consumer sees a different Destination to consume from and there can be a many to many map of producer Destination to many different consumer destinations (as well as a mix of Topics and Queues.</p>
<p>The main difference between a Virtual Topic and a Composite Desetination is that with a Composite Destination the list of consumer destinations is static and hard wired. Whereas with a Virtual Topic at run time a new consumer or queue can be created dynamically and addded to the subscription without having to reconfigure the broker.</p>
<p>e.g. for a virtual topic, <strong>VirtualTopic.Orders</strong> at run time a new consumer can be created on the non-existent queue <strong>Consumer.FOO.VirtualTopic.Orders</strong> (where FOO is the unique name of the consumer) and the queue will be created which is also automatically wired up to the virtual topic as a consumer queue.</p>
-<h3 id="WhatisthedifferencebetweenaVirtualTopicandaCompositeDestination-See">See</h3>
+<h3>See</h3>
-<ul><li><a shape="rect" href="how-does-a-queue-compare-to-a-topic.xml">How does a Queue compare to a Topic</a></li></ul></div>
+<ul><li><link><page ri:content-title="How does a Queue compare to a Topic"></page></link></li></ul>
+</div>
diff --git a/what-is-the-difference-between-discovery-multicast-and-zeroconf.xml b/what-is-the-difference-between-discovery-multicast-and-zeroconf.xml
index 2374c27..0c25330 100644
--- a/what-is-the-difference-between-discovery-multicast-and-zeroconf.xml
+++ b/what-is-the-difference-between-discovery-multicast-and-zeroconf.xml
@@ -2,42 +2,36 @@
<p>The scheme 'multicast' refers to either listening for or advertising discovery events on a multicast address. zeroconf is similar to multicast, except for protocol specific to Apple's Rendezvous (bonjour).</p>
-<h3 id="Whatisthedifferencebetweendiscovery,multicastandzeroconf-Broker">Broker</h3>
+<h3>Broker</h3>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="22ee5d65-5851-470c-a809-e0b90e776c32" ac:name="code" ac:schema-version="1"><plain-text-body>
<networkConnectors>
- <networkConnector name="default" uri="multicast://default"/>
+ <networkConnector name="default" uri="multicast://default"/>
</networkConnectors>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>The above configuration in the broker xml file will make it automatically establish network connectors to other brokers that advertise themselves on the multicast address: when this broker gets a discovery event from another broker, the event has information that enables it to establish network connector to that broker.</p>
<p>Self-advertisement is facilitated by the following config:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="c21df2d5-ec0c-46d7-958e-1e248b26908d" ac:name="code" ac:schema-version="1"><plain-text-body>
<transportConnectors>
- <transportConnector name="default" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
+ <transportConnector name="default" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
</transportConnectors>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="Whatisthedifferencebetweendiscovery,multicastandzeroconf-Client">Client</h3>
+<h3>Client</h3>
<p>An example usage of discovery on the client side (using the transport 'discovery' that uses discovery agent) ...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="bd132e4e-2190-4c96-b5cc-b400f1ee251f" ac:name="code" ac:schema-version="1"><plain-text-body>
<transportConnectors>
- <transportConnector name="default" uri="discovery:(multicast://default)"/>
+ <transportConnector name="default" uri="discovery:(multicast://default)"/>
</transportConnectors>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<p>ps: discovery (which is a confusing name) is just like a 'reliable' transport such as <a shape="rect" href="failover-transport-reference.xml">failover</a>. If it is unable to connect to a broker, it will try another broker (assuming it<br clear="none">
+<p>ps: discovery (which is a confusing name) is just like a 'reliable' transport such as <link><page ri:content-title="Failover Transport Reference"></page><link-body>failover</link-body></link>. If it is unable to connect to a broker, it will try another broker (assuming it<br clear="none">
heard its advertisement over multicast).</p></div>
diff --git a/what-is-the-difference-between-persistent-and-non-persistent-delivery.xml b/what-is-the-difference-between-persistent-and-non-persistent-delivery.xml
index d2febd7..9c1b077 100644
--- a/what-is-the-difference-between-persistent-and-non-persistent-delivery.xml
+++ b/what-is-the-difference-between-persistent-and-non-persistent-delivery.xml
@@ -1,12 +1,13 @@
-<div class="wiki-content maincontent"><h2 id="Whatisthedifferencebetweenpersistentandnon-persistentdelivery-Whatisthedifferencebetweenpersistentandnon-persistentdelivery?">What is the difference between persistent and non-persistent delivery?</h2>
+<div class="wiki-content maincontent"><h2>What is the difference between persistent and non-persistent delivery?</h2>
<p>ActiveMQ supports both persistent and non-persistent delivery. As per the JMS specification, the default delivery mode is persistent. The persistence flag is set on the MessageProducer for all messages using the setDeliveryMode. It can also be specified on a per message basis using the long form of the send method. Persistence is a property of a an individual message.</p>
<p>The main difference is that if you are using persistent delivery, messages are persisted to disk/database so that they will survive a broker restart. When using non-persistent delivery, if you kill a broker then you will lose all in-transit messages.</p>
-<p>The effect of this difference is that persistent messaging is usually slower than non-persistent delivery, particularly when not using <a shape="rect" href="async-sends.xml">Async Sends</a>.</p>
+<p>The effect of this difference is that persistent messaging is usually slower than non-persistent delivery, particularly when not using <link><page ri:content-title="Async Sends"></page></link>.</p>
-<h3 id="Whatisthedifferencebetweenpersistentandnon-persistentdelivery-Seealso">See also</h3>
+<h3>See also</h3>
-<ul><li><a shape="rect" href="async-sends.xml">Async Sends</a></li><li><a shape="rect" href="how-do-i-disable-persistence.xml">How do I disable persistence</a></li></ul></div>
+<ul><li><link><page ri:content-title="Async Sends"></page></link></li><li><link><page ri:content-title="How do I disable persistence"></page></link></li></ul>
+</div>
diff --git a/what-is-the-license.xml b/what-is-the-license.xml
index ddc9e69..fcee6b9 100644
--- a/what-is-the-license.xml
+++ b/what-is-the-license.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="Whatisthelicense-Whatisthelicense?">What is the license?</h2>
+<div class="wiki-content maincontent"><h2>What is the license?</h2>
-<p>This software is open source using the <a shape="rect" class="external-link" href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache 2.0 licence</a> (a liberal BSD style license which is very commercial friendly)</p></div>
+<p>This software is open source using the <a shape="rect" href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache 2.0 licence</a> (a liberal BSD style license which is very commercial friendly)</p></div>
diff --git a/what-is-the-prefetch-limit-for.xml b/what-is-the-prefetch-limit-for.xml
index 53ccc9c..9014622 100644
--- a/what-is-the-prefetch-limit-for.xml
+++ b/what-is-the-prefetch-limit-for.xml
@@ -1,12 +1,6 @@
-<div class="wiki-content maincontent"><p>One of the design goals of ActiveMQ is to be a highly performant message bus. This means using a <a shape="rect" href="seda.xml">SEDA</a> architecture to perform as much work as possible asynchronously. To make efficient use of network resources the broker utilizes a 'push' model to dispatch messages to consumers. This ensures that a consumer always has a local buffer of messages ready to process. The alternative would be for consumers to explicitly pull messages from the broker. Pulling messages individually is not very efficient and can increase the per message latency significantly.</p><p>However, there is a danger that without limiting the number of messages that are pushed to a consumer its client-side resources could become exhausted. This is the natural consequence of message consumption typically being much slower than message delivery. To avoid this situation ActiveMQ therefore employs a <strong>prefetch limit</strong> to limit the maximum number of messages that can be dispatched to an individual consumer at once. The consumer in turn uses the prefetch limit to size its prefetch message buffer.</p><p>Once the broker has dispatched a prefetch limit number of messages to a consumer it will not dispatch any more messages to that consumer until the consumer has acknowledged at least 50% of the prefetched messages, e.g., prefetch/2, that it received. When the broker has received said acknowledgements it will dispatch a further prefetch/2 number of messages to the consumer to 'top-up', as it were, its prefetch buffer. Note that it's possible to specify a prefetch limit on a per consumer basis (see below).</p><p>Large prefetch values are recommended for high performance with high message volumes. However, for lower message volumes, where each message takes a long time to process, the prefetch should be set to 1. This ensures that a consumer is only processing one message at a time. Specifying a prefetch limit of zero, however, will cause the consumer to poll for messages, one at a time, instead of the message being pushed to the consumer.</p><div class="confluence-information-macro confluence-information-macro-information"><p class="title">What is a Slow Consumer?</p><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>A slow consumer is one that has more than twice its configured prefetch limit number of messages pending.</p></div></div><div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Implementing Consumers Using a Dynamic Language </p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Consumers that are unable to cache prefetched messages must set their prefetch to 1. An example of such a consumer is one implemented using a scripting language like Ruby, say, that connects via STOMP. In this case there's no notion of a client-side message buffer.</p></div></div><h3 id="WhatisthePrefetchLimitFor?-SpecifyingthePrefetchPolicy">Specifying the PrefetchPolicy</h3><p>You can specify an instance of the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html">ActiveMQPrefetchPolicy</a> on an <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> or <a shape="rect" class="external-link" 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 each different quality of service has a different value. e.g.</p><ul><li><p>persistent queues (default value: <strong><code>1000</code></strong>)</p></li><li><p>non-persistent queues (default value: <strong><code>1000</code></strong>)</p></li><li><p>persistent topics (default value: <strong><code>100</code></strong>)</p></li><li><p>non-persistent topics (default value: <strong><code>Short.MAX_VALUE - 1</code></strong>)</p></li></ul><p>The prefetch limit can also be configured on the connection URI used to establish a connection the broker. To change the prefetch limit for all consumer types configure a connection URI as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tcp://localhost:61616?jms.prefetchPolicy.all=50
-]]></script>
-</div></div><p>To change the prefetch limit for queue consumers only configure the connection URI as follows:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1
-]]></script>
-</div></div><p>It can also be configured on a per consumer basis using <a shape="rect" href="destination-options.xml">Destination Options</a>:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[queue = new ActiveMQQueue("TEST.QUEUE?consumer.prefetchSize=10");
+<div class="wiki-content maincontent"><p>One of the design goals of ActiveMQ is to be a highly performant message bus. This means using a <link><page ri:content-title="SEDA"></page></link> architecture to perform as much work as possible asynchronously. To make efficient use of network resources the broker utilizes a 'push' model to dispatch messages to consumers. This ensures that a consumer always has a local buffer of messages ready to process. The alternative would be for consumers to explicitly pull messages from the broker. Pulling messages individually is not very efficient and can increase the per message latency significantly.</p><p>However, there is a danger that without limiting the number of messages that are pushed to a consumer its client-side resources could become exhausted. This is the natural consequence of message consumption typically being much slower than message delivery. To avoid this situation ActiveMQ therefore employs a <strong>prefetch limit</strong> to limit the maximum number of messages that can be dispatched to an individual consumer at once. The consumer in turn uses the prefetch limit to size its prefetch message buffer.</p><p>Once the broker has dispatched a prefetch limit number of messages to a consumer it will not dispatch any more messages to that consumer until the consumer has acknowledged at least 50% of the prefetched messages, e.g., prefetch/2, that it received. When the broker has received said acknowledgements it will dispatch a further prefetch/2 number of messages to the consumer to 'top-up', as it were, its prefetch buffer. Note that it's possible to specify a prefetch limit on a per consumer basis (see below).</p><p>Large prefetch values are recommended for high performance with high message volumes. However, for lower message volumes, where each message takes a long time to process, the prefetch should be set to 1. This ensures that a consumer is only processing one message at a time. Specifying a prefetch limit of zero, however, will cause the consumer to poll for messages, one at a time, instead of the message being pushed to the consumer.</p><structured-macro ac:macro-id="9a8bdaf4-4307-4ea4-b5e1-1b3dcddab55a" ac:name="info" ac:schema-version="1"><parameter ac:name="title">What is a Slow Consumer?</parameter><rich-text-body><p>A slow consumer is one that has more than twice its configured prefetch limit number of messages pending.</p></rich-text-body></structured-macro><structured-macro ac:macro-id="f6933470-b92f-4b95-8237-00be1015e06f" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Implementing Consumers Using a Dynamic Language </parameter><rich-text-body><p>Consumers that are unable to cache prefetched messages must set their prefetch to 1. An example of such a consumer is one implemented using a scripting language like Ruby, say, that connects via STOMP. In this case there's no notion of a client-side message buffer.</p></rich-text-body></structured-macro><h3>Specifying the PrefetchPolicy</h3><p>You can specify an instance of the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html">ActiveMQPrefetchPolicy</a> on an <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html">ActiveMQConnectionFactory</a> or <a shape="rect" 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 each different quality of service has a different value. e.g.</p><ul><li><p>persistent queues (default value: <strong><code>1000</code></strong>)</p></li><li><p>non-persistent queues (default value: <strong><code>1000</code></strong>)</p></li><li><p>persistent topics (default value: <strong><code>100</code></strong>)</p></li><li><p>non-persistent topics (default value: <strong><code>Short.MAX_VALUE - 1</code></strong>)</p></li></ul><p>The prefetch limit can also be configured on the connection URI used to establish a connection the broker. To change the prefetch limit for all consumer types configure a connection URI as follows:</p><structured-macro ac:macro-id="76e34a06-22f2-4bf2-854a-db8d3098a728" ac:name="code" ac:schema-version="1"><plain-text-body>tcp://localhost:61616?jms.prefetchPolicy.all=50
+</plain-text-body></structured-macro><p>To change the prefetch limit for queue consumers only configure the connection URI as follows:</p><structured-macro ac:macro-id="8ad2e691-64cc-4539-bda0-4ed0566f2739" ac:name="code" ac:schema-version="1"><plain-text-body>tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1
+</plain-text-body></structured-macro><p>It can also be configured on a per consumer basis using <link><page ri:content-title="Destination Options"></page></link>:</p><structured-macro ac:macro-id="9bc2916a-b7a2-442d-bda6-21530d916206" ac:name="code" ac:schema-version="1"><parameter ac:name="">java</parameter><plain-text-body>queue = new ActiveMQQueue("TEST.QUEUE?consumer.prefetchSize=10");
consumer = session.createConsumer(queue);
-]]></script>
-</div></div><h3 id="WhatisthePrefetchLimitFor?-PooledConsumersandPrefetch">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 this reason, the <a shape="rect" class="external-link" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/jms/pool/PooledConnectionFactory.html">org.apache.activemq.pool.PooledConnectionFactory</a> does <strong>not</strong> pool consumers.</p><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<strong><code> receive(timeout)</code></strong>. Its generally recommended to turn off consumer caching in Springs CachingConnectionFactory and any other frameworks that allow to pool JMS consumers.</p><p>Note that Springs DefaultMessageListenerContainer (DMLC) and its <strong><code>CACHE_CONSUMER</code></strong> cache level is not affected by this problem! Springs DMLC does not pool consumers in the sense that it does not use an internal pool with multiple consumer instances. Instead it caches the consumer, i.e. it re-uses the same JMS consumer object to receive all messages for the life time of the DMLC instance. So it behaves pretty much like properly hand written JMS code, where you create the JMS connection, session, consumer and then use this consumer instance to receive all your messages.<br clear="none">Hence there is no problem with using  <strong><code>CACHE_CONSUMER</code></strong> in Springs DMLC, even with multiple consumer threads, unless you are using XA transactions. XA transactions do not work with <strong><code>CACHE_CONSUMER</code></strong>. However local JMS transactions and non-transacted consumers are just fine to use  <strong><code>CACHE_CONSUMER</code></strong> in Springs DMLC.</p><p>Also note that Camel's <a shape="rect" class="external-link" href="http://camel.apache.org/jms.html">JMS</a> or <a shape="rect" class="external-link" href="http://camel.apache.org/activemq.html">ActiveMQ</a> components use Springs DMLC internally. So everything said above about Springs DMLC and  <strong><code>CACHE_CONSUMER</code></strong> applies to these two Camel components as well.</p><h3 id="WhatisthePrefetchLimitFor?-Ramvs.PerformanceTrade-off">Ram vs. Performance Trade-off</h3><p>Setting a relatively high value of prefetch leads to higher performance. Therefore the default values are typically greater than 1000 and much higher for topics and higher still for the non-persistent messages. The prefetch size dictates how many messages will be held in RAM on the client so if your RAM is limited you may want to set a low value such as 1 or 10 etc.</p><p> </p></div>
+</plain-text-body></structured-macro><h3>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 this reason, the <a shape="rect" href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/jms/pool/PooledConnectionFactory.html">org.apache.activemq.pool.PooledConnectionFactory</a> does <strong>not</strong> pool consumers.</p><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<strong><code> receive(timeout)</code></strong>. Its generally recommended to turn off consumer caching in Springs CachingConnectionFactory and any other frameworks that allow to pool JMS consumers.</p><p>Note that Springs DefaultMessageListenerContainer (DMLC) and its <strong><code>CACHE_CONSUMER</code></strong> cache level is not affected by this problem! Springs DMLC does not pool consumers in the sense that it does not use an internal pool with multiple consumer instances. Instead it caches the consumer, i.e. it re-uses the same JMS consumer object to receive all messages for the life time of the DMLC instance. So it behaves pretty much like properly hand written JMS code, where you create the JMS connection, session, consumer and then use this consumer instance to receive all your messages.<br clear="none">Hence there is no problem with using  <strong><code>CACHE_CONSUMER</code></strong> in Springs DMLC, even with multiple consumer threads, unless you are using XA transactions. XA transactions do not work with <strong><code>CACHE_CONSUMER</code></strong>. However local JMS transactions and non-transacted consumers are just fine to use  <strong><code>CACHE_CONSUMER</code></strong> in Springs DMLC.</p><p>Also note that Camel's <a shape="rect" href="http://camel.apache.org/jms.html">JMS</a> or <a shape="rect" href="http://camel.apache.org/activemq.html">ActiveMQ</a> components use Springs DMLC internally. So everything said above about Springs DMLC and  <strong><code>CACHE_CONSUMER</code></strong> applies to these two Camel components as well.</p><h3>Ram vs. Performance Trade-off</h3><p>Setting a relatively high value of prefetch leads to higher performance. Therefore the default values are typically greater than 1000 and much higher for topics and higher still for the non-persistent messages. The prefetch size dictates how many messages will be held in RAM on the client so if your RAM is limited you may want to set a low value such as 1 or 10 etc.</p><p> </p></div>
diff --git a/what-jars-do-i-need.xml b/what-jars-do-i-need.xml
index 20330c2..b7e7078 100644
--- a/what-jars-do-i-need.xml
+++ b/what-jars-do-i-need.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="WhatjarsdoIneed-WhatjarsdoIneed">What jars do I need</h2>
+<div class="wiki-content maincontent"><h2>What jars do I need</h2>
-<p>The basic jars you need to use are described on the <a shape="rect" href="initial-configuration.xml">Initial Configuration</a> page.</p></div>
+<p>The basic jars you need to use are described on the <link><page ri:content-title="Initial Configuration"></page></link> page.</p></div>
diff --git a/what-open-source-integration-solution-works-best-with-activemq.xml b/what-open-source-integration-solution-works-best-with-activemq.xml
index f927459..39bf771 100644
--- a/what-open-source-integration-solution-works-best-with-activemq.xml
+++ b/what-open-source-integration-solution-works-best-with-activemq.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>The <a shape="rect" class="external-link" href="http://camel.apache.org">Apache Camel</a> project has been designed to work easily with ActiveMQ - and comes <a shape="rect" class="external-link" href="http://activemq.apache.org/camel/how-does-camel-work-with-activemq.html">embedded</a> in both the clients and the broker from ActiveMQ 5.0 onwards.</p><p><a shape="rect" class="external-link" href="http://camel.apache.org">Apache Camel</a> supports an extensive range of <a shape="rect" class="external-link" href="http://camel.apache.org/enterprise-integration-patterns.html">integration patterns</a> to make integration very simple!</p><p> </p><p><strong>It also supports a wide range of <a shape="rect" class="external-link" href="http://camel.apache.org/components.html">transport binding components</a></strong></p></div>
+<div class="wiki-content maincontent"><p>The <a shape="rect" href="http://camel.apache.org">Apache Camel</a> project has been designed to work easily with ActiveMQ - and comes <a shape="rect" href="http://activemq.apache.org/camel/how-does-camel-work-with-activemq.html">embedded</a> in both the clients and the broker from ActiveMQ 5.0 onwards.</p><p><a shape="rect" href="http://camel.apache.org">Apache Camel</a> supports an extensive range of <a shape="rect" href="http://camel.apache.org/enterprise-integration-patterns.html">integration patterns</a> to make integration very simple!</p><p> </p><p><strong>It also supports a wide range of <a shape="rect" href="http://camel.apache.org/components.html">transport binding components</a></strong></p></div>
diff --git a/what-platforms-does-activemq-support.xml b/what-platforms-does-activemq-support.xml
index 75625bd..a38d9dc 100644
--- a/what-platforms-does-activemq-support.xml
+++ b/what-platforms-does-activemq-support.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><h2 id="WhatplatformsdoesActiveMQsupport-WhatplatformsdoesActiveMQSupport?">What platforms does ActiveMQ Support?</h2><p>ActiveMQ 5.0-5.7 supports any Java platform of Java 5.0 or later. To run on 1.4 see <a shape="rect" href="can-i-use-activemq-5x-or-later-on-java-14.xml">these instructions</a>. ActiveMQ 5.8-5.10 require Java 6 or higher and the releases from 5.11 onwards require Java 7 or later. </p><p>ActiveMQ is based on J2EE 1.4 or later and so implements JMS 1.1 and a JCA 1.5 Resource Adaptor.</p><p>We regularly test ActiveMQ on Windows, OS X, Linux though we're aware of folks who use AIX and Solaris too.</p><h2 id="WhatplatformsdoesActiveMQsupport-SeeAlso">See Also</h2><ul><li><a shape="rect" href="can-i-use-activemq-5x-or-later-on-java-14.xml">Can I use ActiveMQ 5.x or later on Java 1.4</a></li></ul></div>
+<div class="wiki-content maincontent"><h2>What platforms does ActiveMQ Support?</h2><p>ActiveMQ 5.0-5.7 supports any Java platform of Java 5.0 or later. To run on 1.4 see <link><page ri:content-title="Can I use ActiveMQ 5.x or later on Java 1.4"></page><plain-text-link-body>these instructions</plain-text-link-body></link>. ActiveMQ 5.8-5.10 require Java 6 or higher and the releases from 5.11 onwards require Java 7 or later. </p><p>ActiveMQ is based on J2EE 1.4 or later and so implements JMS 1.1 and a JCA 1.5 Resource Adaptor.</p><p>We regularly test ActiveMQ on Windows, OS X, Linux though we're aware of folks who use AIX and Solaris too.</p><h2>See Also</h2><ul><li><link><page ri:content-title="Can I use ActiveMQ 5.x or later on Java 1.4"></page></link></li></ul></div>
diff --git a/what-version-should-i-use.xml b/what-version-should-i-use.xml
index be57000..1ff9055 100644
--- a/what-version-should-i-use.xml
+++ b/what-version-should-i-use.xml
@@ -1,2 +1,2 @@
-<div class="wiki-content maincontent"><p>ActiveMQ version numbers follow the <strong>MAJOR.MINOR.PATCH</strong> convention used by many software projects.  In general, patch releases are done only when there are significant enough bugs found in the current minor version to justify a release sooner than the next minor release (though 5.9.1 was an exception, as it was just as large as a minor release).  As a result, you should generally use the most recent patch version of whichever minor release you choose; there is very seldom a reason to pick a patch version other than the latest within a given minor version.</p><p>You should also generally use the most recent minor version if possible since it will include bug fixes that may let you avoid being caught by problems in the older minor versions, though as always you may have reasons to deviate from this general rule (bugs introduced in the newer minor version, difficulty getting your company's security department to approve a new version, etc.).</p><p>In all cases, when deciding what version to use you should review the release notes of the later version and of all intermediate versions (e.g. if deciding between 5.9.1 and 5.11.1, you should review the release notes for 5.10.0, 5.11.0, and 5.11.1) to understand what bugs are fixed in the later version, and you should review the release notes for versions after the later version as well as the unresolved issues in <a shape="rect" class="external-link" href="http://thoughts and suggestions" rel="nofollow">JIRA</a> to understand what bugs were introduced after the earlier version.</p></div>
+<div class="wiki-content maincontent"><p>ActiveMQ version numbers follow the <strong>MAJOR.MINOR.PATCH</strong> convention used by many software projects.  In general, patch releases are done only when there are significant enough bugs found in the current minor version to justify a release sooner than the next minor release (though 5.9.1 was an exception, as it was just as large as a minor release).  As a result, you should generally use the most recent patch version of whichever minor release you choose; there is very seldom a reason to pick a patch version other than the latest within a given minor version.</p><p>You should also generally use the most recent minor version if possible since it will include bug fixes that may let you avoid being caught by problems in the older minor versions, though as always you may have reasons to deviate from this general rule (bugs introduced in the newer minor version, difficulty getting your company's security department to approve a new version, etc.).</p><p>In all cases, when deciding what version to use you should review the release notes of the later version and of all intermediate versions (e.g. if deciding between 5.9.1 and 5.11.1, you should review the release notes for 5.10.0, 5.11.0, and 5.11.1) to understand what bugs are fixed in the later version, and you should review the release notes for versions after the later version as well as the unresolved issues in <a shape="rect" href="http://thoughts and suggestions">JIRA</a> to understand what bugs were introduced after the earlier version.</p></div>
diff --git a/while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.xml b/while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.xml
index 2422d5f..f91f52d 100644
--- a/while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.xml
+++ b/while-posting-large-binary-file-to-activemq-is-there-a-way-to-measure-its-progress.xml
@@ -1,6 +1,6 @@
<div class="wiki-content maincontent">
<p>If you are using the JMS Streams feature with 4.x of ActiveMQ<br clear="none">
-<a shape="rect" class="external-link" href="http://activemq.org/JMS+Streams" rel="nofollow">http://activemq.org/JMS+Streams</a></p>
+<a shape="rect" href="http://activemq.org/JMS+Streams">http://activemq.org/JMS+Streams</a></p>
<p> 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</p></div>
diff --git a/why-do-i-not-get-all-of-the-messages-i-sent.xml b/why-do-i-not-get-all-of-the-messages-i-sent.xml
index 77d8134..2b4e881 100644
--- a/why-do-i-not-get-all-of-the-messages-i-sent.xml
+++ b/why-do-i-not-get-all-of-the-messages-i-sent.xml
@@ -1,6 +1,6 @@
-<div class="wiki-content maincontent"><h3 id="WhydoInotgetallofthemessagesIsent-ForActiveMQ3.x/4.x"><strong>For ActiveMQ 3.x/4.x</strong></h3>
+<div class="wiki-content maincontent"><h3><strong>For ActiveMQ 3.x/4.x</strong></h3>
-<p>As <a shape="rect" class="external-link" href="http://forums.logicblaze.com/posts/list/0/14.page#37" rel="nofollow">Matt reported</a> its possible that there is a race condition in your application; are you sure you had created your consumer and called start() on the JMS Connection before the producer started publishing messages?</p>
+<p>As <a shape="rect" href="http://forums.logicblaze.com/posts/list/0/14.page#37">Matt reported</a> its possible that there is a race condition in your application; are you sure you had created your consumer and called start() on the JMS Connection before the producer started publishing messages?</p>
<p>Another option if startup race conditions are a problem is to use durable messaging.</p></div>
diff --git a/why-do-i-not-receive-messages-on-my-durable-topic-subscription.xml b/why-do-i-not-receive-messages-on-my-durable-topic-subscription.xml
index 0668218..b5de8fc 100644
--- a/why-do-i-not-receive-messages-on-my-durable-topic-subscription.xml
+++ b/why-do-i-not-receive-messages-on-my-durable-topic-subscription.xml
@@ -5,7 +5,7 @@
<p>But you don't receive the messages?</p>
-<h3 id="WhydoInotreceivemessagesonmydurabletopicsubscription-Fix">Fix</h3>
+<h3>Fix</h3>
-<p>To be able to deliver messages to offline durable topic subscribers you must mark the message as being persistent. To do this set the PERSISTENT_DELIVERY mode on the MessageProducer as described <a shape="rect" href="how-do-i-make-messages-durable.xml">here</a>.</p></div>
+<p>To be able to deliver messages to offline durable topic subscribers you must mark the message as being persistent. To do this set the PERSISTENT_DELIVERY mode on the MessageProducer as described <link><page ri:content-title="How do I make messages durable"></page><link-body>here</link-body></link>.</p></div>
diff --git a/why-do-kahadb-log-files-remain-after-cleanup.xml b/why-do-kahadb-log-files-remain-after-cleanup.xml
index abc3607..2cd6dd5 100644
--- a/why-do-kahadb-log-files-remain-after-cleanup.xml
+++ b/why-do-kahadb-log-files-remain-after-cleanup.xml
@@ -1,14 +1,11 @@
-<div class="wiki-content maincontent"><p>Clean-up of un-referenced KahaDB journal log files <strong><code>data-<id>.log</code></strong> will occur every 30 seconds by default. If a data file is in-use it will not be cleaned up.</p><p>A data file may be in-use because:</p><ol><li>It contains a pending message for a destination or durable topic subscription</li><li>It contains an ACK for a message which is in an in-use data file - the ACK cannot be removed as a recovery would then mark the message for redelivery</li><li>The journal references a pending transaction</li><li>It is a journal file, and there may be a pending write to it</li></ol><p><span style="line-height: 1.4285715;">The <strong><code>TRACE</code></strong> level logging of the <strong><code>org.apache.activemq.store.kahadb.MessageDatabase</code></strong> class provides insight into the cleanup process and will allow you to determine why a given data file is considered in-use and as a result, not a candidate for cleanup.</span></p><p>To debug, add the following (or similar) to your <strong><code>log4j.properties</code></strong> file (if needed):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
+<div class="wiki-content maincontent"><p>Clean-up of un-referenced KahaDB journal log files <strong><code>data-<id>.log</code></strong> will occur every 30 seconds by default. If a data file is in-use it will not be cleaned up.</p><p>A data file may be in-use because:</p><ol><li>It contains a pending message for a destination or durable topic subscription</li><li>It contains an ACK for a message which is in an in-use data file - the ACK cannot be removed as a recovery would then mark the message for redelivery</li><li>The journal references a pending transaction</li><li>It is a journal file, and there may be a pending write to it</li></ol><p><span style="line-height: 1.4285715;">The <strong><code>TRACE</code></strong> level logging of the <strong><code>org.apache.activemq.store.kahadb.MessageDatabase</code></strong> class provides insight into the cleanup process and will allow you to determine why a given data file is considered in-use and as a result, not a candidate for cleanup.</span></p><p>To debug, add the following (or similar) to your <strong><code>log4j.properties</code></strong> file (if needed):</p><structured-macro ac:macro-id="9b21f01f-44f8-4895-b070-5da866655674" ac:name="code" ac:schema-version="1"><plain-text-body>log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
log4j.appender.kahadb.file=${activemq.base}/data/kahadb.log
log4j.appender.kahadb.maxFileSize=1024KB
log4j.appender.kahadb.maxBackupIndex=5
log4j.appender.kahadb.append=true
log4j.appender.kahadb.layout=org.apache.log4j.PatternLayout
log4j.appender.kahadb.layout.ConversionPattern=%d [%-15.15t] %-5p %-30.30c{1} - %m%n
-log4j.logger.org.apache.activemq.store.kahadb.MessageDatabase=TRACE, kahadb]]></script>
-</div></div><p>Either restart ActiveMQ and let the cleanup process run (give it a minute or two for example) or alternatively apply this logging configuration to a running broker via JMX. The <strong><code>Broker</code></strong> MBean exposes an operation called <strong><code>reloadLog4jProperties</code></strong> in JMX that can be used to tell the broker to reload its <strong><code>log4j.properties</code></strong>. Often its enough to apply this logging configuration for 2-5 minutes and then analyze the broker's log file.</p><p>Examine the log file and look for cleanup of the data files. The process starts with the complete set of known data files and queries the index on a per destination basis to prune this list. Anything that remains is a candidate for cleanup. The trace logging gives the destination and the log file numbers that remain candidates for removal as it iterates through the index.</p><p>At some point you'll hit a destination and the number of data file ids will suddenly drop because that destination references them. It could be a DLQ or an offline durable subscriber. In any event, the logging will help you pinpoint the destinations that are hogging disk space.</p><p>Here is a quick sample:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ TRACE | Last update: 164:41712, full gc candidates set: [86, 87, 163, 164] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker
+log4j.logger.org.apache.activemq.store.kahadb.MessageDatabase=TRACE, kahadb</plain-text-body></structured-macro><p>Either restart ActiveMQ and let the cleanup process run (give it a minute or two for example) or alternatively apply this logging configuration to a running broker via JMX. The <strong><code>Broker</code></strong> MBean exposes an operation called <strong><code>reloadLog4jProperties</code></strong> in JMX that can be used to tell the broker to reload its <strong><code>log4j.properties</code></strong>. Often its enough to apply this logging configuration for 2-5 minutes and then analyze the broker's log file.</p><p>Examine the log file and look for cleanup of the data files. The process starts with the complete set of known data files and queries the index on a per destination basis to prune this list. Anything that remains is a candidate for cleanup. The trace logging gives the destination and the log file numbers that remain candidates for removal as it iterates through the index.</p><p>At some point you'll hit a destination and the number of data file ids will suddenly drop because that destination references them. It could be a DLQ or an offline durable subscriber. In any event, the logging will help you pinpoint the destinations that are hogging disk space.</p><p>Here is a quick sample:</p><structured-macro ac:macro-id="5adb33e0-1b5d-4d39-a955-fa614a8d4ed4" ac:name="code" ac:schema-version="1"><plain-text-body> TRACE | Last update: 164:41712, full gc candidates set: [86, 87, 163, 164] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker
TRACE | gc candidates after first tx:164:41712, [86, 87, 163] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker
TRACE | gc candidates after dest:0:A, [86, 87, 163] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker
TRACE | gc candidates after dest:1:B, [86, 87, 163] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker
@@ -18,9 +15,7 @@
TRACE | gc candidates after dest:0:I, [86, 87] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker
TRACE | gc candidates after dest:0:J, [87] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker
TRACE | gc candidates: [87] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker
- DEBUG | Cleanup removing the data files: [87] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker]]></script>
-</div></div><p>We get one candidate, <strong><code>data-87.log</code></strong> from the existing set of journal data files <strong><code>[86, 87, 163, 164]</code></strong>. There is a current transaction using <strong><code>164</code></strong>, destination (Queue named <strong><code>E</code></strong>) <code>'<strong>0:E</strong>'</code> has some messages in <strong><code>163</code></strong>, destination <code>'<strong>0:I</strong>'</code> has messages in <strong><code>86</code></strong> and <strong><code>87</code></strong> is un-referenced. In this case, there must be some long standing un-acknowledged messages or a very slow consumer on destination <code>'<strong>0:I</strong>'</code>.</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The <code>'<strong>0:</strong>'</code> prefix is shorthand for a queue, <code>'<strong>1:</strong>'</code> for a topic. Example: <strong><code>dest:1:B</code></strong> refers to a topic named <strong><code>B</code></strong>.</p></div></div><p> </p><p> </p><hr><h3 id="WhydoKahaDBlogfilesremainaftercleanup-Non-persistentmessages">Non-persistent messages</h3><p>Similar for non-persistent messages that are not stored in your configured KahaDB persistence adapter but get swapped to temp storage once they exceed the broker's configured <strong><code>memoryUsage</code></strong> limit. A similar logging configuration can show details of the cleanup of temp storage.</p><p> </p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
+ DEBUG | Cleanup removing the data files: [87] | org.apache.activemq.store.kahadb.MessageDatabase | ActiveMQ Journal Checkpoint Worker</plain-text-body></structured-macro><p>We get one candidate, <strong><code>data-87.log</code></strong> from the existing set of journal data files <strong><code>[86, 87, 163, 164]</code></strong>. There is a current transaction using <strong><code>164</code></strong>, destination (Queue named <strong><code>E</code></strong>) <code>'<strong>0:E</strong>'</code> has some messages in <strong><code>163</code></strong>, destination <code>'<strong>0:I</strong>'</code> has messages in <strong><code>86</code></strong> and <strong><code>87</code></strong> is un-referenced. In this case, there must be some long standing un-acknowledged messages or a very slow consumer on destination <code>'<strong>0:I</strong>'</code>.</p><structured-macro ac:macro-id="51f9f9bc-f09a-45c2-8400-15ef785297f1" ac:name="info" ac:schema-version="1"><rich-text-body><p>The <code>'<strong>0:</strong>'</code> prefix is shorthand for a queue, <code>'<strong>1:</strong>'</code> for a topic. Example: <strong><code>dest:1:B</code></strong> refers to a topic named <strong><code>B</code></strong>.</p></rich-text-body></structured-macro><p> </p><p> </p><hr><h3>Non-persistent messages</h3><p>Similar for non-persistent messages that are not stored in your configured KahaDB persistence adapter but get swapped to temp storage once they exceed the broker's configured <strong><code>memoryUsage</code></strong> limit. A similar logging configuration can show details of the cleanup of temp storage.</p><p> </p><structured-macro ac:macro-id="b2f79ba9-fa23-4152-b8fe-49a7b68f7713" ac:name="code" ac:schema-version="1"><plain-text-body>log4j.appender.kahadb=org.apache.log4j.RollingFileAppender
log4j.appender.kahadb.file=${activemq.base}/data/kahadb.log
log4j.appender.kahadb.maxFileSize=1024KB
log4j.appender.kahadb.maxBackupIndex=5
@@ -29,6 +24,5 @@
log4j.appender.kahadb.layout.ConversionPattern=%d [%-15.15t] %-5p %-30.30c{1} - %m%n
log4j.logger.org.apache.activemq.store.kahadb=TRACE, kahadb
log4j.logger.org.apache.activemq.store.kahadb.MessageDatabase=INFO, kahadb
- ]]></script>
-</div></div><p> </p><p>Note the last line of above logging configuration disables the verbose logging of the KahaDB cleanup task. If that line gets removed, the cleanup details of both KahaDB and temp storage will be logged to the same file but you need to be careful not to mix the logging output.</p></div>
+ </plain-text-body></structured-macro><p> </p><p>Note the last line of above logging configuration disables the verbose logging of the KahaDB cleanup task. If that line gets removed, the cleanup details of both KahaDB and temp storage will be logged to the same file but you need to be careful not to mix the logging output.</p></div>
diff --git a/wildcards.xml b/wildcards.xml
index 43162ba..ff30762 100644
--- a/wildcards.xml
+++ b/wildcards.xml
@@ -1,8 +1,6 @@
-<div class="wiki-content maincontent"><p>We support destination wildcards to provide easy support for federated name hierarchies. This concept has been popular in financial market data for some time as a way of organizing events (such as price changes) into hierarchies and to use wildcards for easy subscription of the range of information you're interested in.</p><p>For example imagine you are sending price messages from a stock exchange feed. You might use some kind of destination such as</p><ul><li><code>PRICE.STOCK.NASDAQ.ORCL</code> to publish Oracle Corporation's price on NASDAQ and</li><li><code>PRICE.STOCK.NYSE.IBM</code> to publish IBM's price on the New York Stock Exchange</li></ul><p>A subscriber could then use exact destinations to subscribe to exactly the prices it requires. Or it could use wildcards to define hierarchical pattern matches to the destinations to subscribe from.</p><h3 id="Wildcards-Wildcardssupported">Wildcards supported</h3><p>We support the following wildcards which are fairly standard practice; wildcards are not part of the JMS specification so are custom enhancements.</p><ul><li><code>.</code> is used to separate names in a path</li><li><code>*</code> is used to match any name in a path</li><li><code>></code> is used to recursively match any destination starting from this name</li></ul><p>For example using the example above, these subscriptions are possible</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Subscription</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Meaning</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>PRICE.></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any price for any product on any exchange</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>PRICE.STOCK.></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any price for a stock on any exchange</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>PRICE.STOCK.NASDAQ.*</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any stock price on NASDAQ</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>PRICE.STOCK.*.IBM</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Any IBM stock price on any exchange</p></td></tr></tbody></table></div><p><strong>Note:</strong> Don't specify any string after '>' on your wildcard expression, it will be ignored. E.g. using a wildcard <code>PRICE.>.IBM</code> will also match <code>PRICE.STOCK.NASDAQ.FB.</code> Using '>' really matches everything till the end of the destination name.</p><h3 id="Wildcards-Custompathseparator">Custom path separator</h3><p>As of version 5.5.0 we support <a shape="rect" class="external-link" href="http://activemq.apache.org/interceptors.html">plugin</a> that allows clients to use customer path separator. So instead of</p><p><code>FOO.BAR.*</code></p><p>you can use</p><p><code>FOO/BAR/*</code></p><p>To</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[ <plugins>
+<div class="wiki-content maincontent"><p>We support destination wildcards to provide easy support for federated name hierarchies. This concept has been popular in financial market data for some time as a way of organizing events (such as price changes) into hierarchies and to use wildcards for easy subscription of the range of information you're interested in.</p><p>For example imagine you are sending price messages from a stock exchange feed. You might use some kind of destination such as</p><ul><li><code>PRICE.STOCK.NASDAQ.ORCL</code> to publish Oracle Corporation's price on NASDAQ and</li><li><code>PRICE.STOCK.NYSE.IBM</code> to publish IBM's price on the New York Stock Exchange</li></ul><p>A subscriber could then use exact destinations to subscribe to exactly the prices it requires. Or it could use wildcards to define hierarchical pattern matches to the destinations to subscribe from.</p><h3>Wildcards supported</h3><p>We support the following wildcards which are fairly standard practice; wildcards are not part of the JMS specification so are custom enhancements.</p><ul><li><code>.</code> is used to separate names in a path</li><li><code>*</code> is used to match any name in a path</li><li><code>></code> is used to recursively match any destination starting from this name</li></ul><p>For example using the example above, these subscriptions are possible</p><table><tbody><tr><th colspan="1" rowspan="1"><p>Subscription</p></th><th colspan="1" rowspan="1"><p>Meaning</p></th></tr><tr><td colspan="1" rowspan="1"><p><code>PRICE.></code></p></td><td colspan="1" rowspan="1"><p>Any price for any product on any exchange</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>PRICE.STOCK.></code></p></td><td colspan="1" rowspan="1"><p>Any price for a stock on any exchange</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>PRICE.STOCK.NASDAQ.*</code></p></td><td colspan="1" rowspan="1"><p>Any stock price on NASDAQ</p></td></tr><tr><td colspan="1" rowspan="1"><p><code>PRICE.STOCK.*.IBM</code></p></td><td colspan="1" rowspan="1"><p>Any IBM stock price on any exchange</p></td></tr></tbody></table><p><strong>Note:</strong> Don't specify any string after '>' on your wildcard expression, it will be ignored. E.g. using a wildcard <code>PRICE.>.IBM</code> will also match <code>PRICE.STOCK.NASDAQ.FB.</code> Using '>' really matches everything till the end of the destination name.</p><h3>Custom path separator</h3><p>As of version 5.5.0 we support <a shape="rect" href="http://activemq.apache.org/interceptors.html">plugin</a> that allows clients to use customer path separator. So instead of</p><p><code>FOO.BAR.*</code></p><p>you can use</p><p><code>FOO/BAR/*</code></p><p>To</p><structured-macro ac:macro-id="6486674f-1532-4de3-b3c2-c695c716cbb6" ac:name="code" ac:schema-version="1"><plain-text-body> <plugins>
.....
<destinationPathSeparatorPlugin/>
</plugins>
-]]></script>
-</div></div><p>Please note that you should add this plugin as last if you want it to work properly with other plugins (such as <a shape="rect" class="external-link" href="http://activemq.apache.org/security.html">security</a> for example).</p><p>A default path separator this plugin will use is <code>/</code>. You can customize it further using <code>pathSeparator</code> property.</p></div>
+</plain-text-body></structured-macro><p>Please note that you should add this plugin as last if you want it to work properly with other plugins (such as <a shape="rect" href="http://activemq.apache.org/security.html">security</a> for example).</p><p>A default path separator this plugin will use is <code>/</code>. You can customize it further using <code>pathSeparator</code> property.</p></div>
diff --git a/wire-protocol.xml b/wire-protocol.xml
index 0552546..2196468 100644
--- a/wire-protocol.xml
+++ b/wire-protocol.xml
@@ -1,23 +1,23 @@
<div class="wiki-content maincontent">
-<p>This page describes the logical <a shape="rect" href="openwire.xml">OpenWire</a> protocol for users developing clients in other languages than Java such as C# or C native clients. Note that OpenWire is designed for maximum performance and features; its the protocol used inside ActiveMQ. If you want a simpler protocol to work with to get started with a cross language client then try <a shape="rect" href="stomp.xml">Stomp</a> which is designed for ease-of-implementation so its easy to support many clients.</p>
+<p>This page describes the logical <link><page ri:content-title="OpenWire"></page></link> protocol for users developing clients in other languages than Java such as C# or C native clients. Note that OpenWire is designed for maximum performance and features; its the protocol used inside ActiveMQ. If you want a simpler protocol to work with to get started with a cross language client then try <link><page ri:content-title="Stomp"></page></link> which is designed for ease-of-implementation so its easy to support many clients.</p>
-<h1 id="WireProtocol-Protocoloverview">Protocol overview</h1>
+<h1>Protocol overview</h1>
<p>A client of ActiveMQ will exchange Command objects (following the <em>Command Pattern</em>). We'll describe how these commands are exchanged...</p>
<p>The protocol uses mostly one way messaging (fire and forget) for most kinds of commands - but there are times when RPCs (request, response) messaging is used. We'll indiciate the RPC scenarios clearly.</p>
-<h2 id="WireProtocol-Establishingconnections">Establishing connections</h2>
+<h2>Establishing connections</h2>
<p>The client must send a ConnectionInfo command with details of the machine, host name, user name, password and most importantly the unique clientId the client wishes to use and then wait for a valid Response before continuing. The clientId must be generated using a unique string generator.</p>
-<h2 id="WireProtocol-Sendingmessages">Sending messages</h2>
+<h2>Sending messages</h2>
<p>Once you've established a connection, you need to create a logical MessageProducer. This involves sending a ProducerInfo command with a unique producerId, sessionId and the clientId (connection ID).</p>
<p>From that point on you can send a Message command any time you like, provided you adorn the message with the clientId, sessionId, producerId along with a transactionId if required (see below on transactions).</p>
-<h2 id="WireProtocol-Consumingmessages">Consuming messages</h2>
+<h2>Consuming messages</h2>
<p>Commands are delivered on your inbound socket for consumption. Some of these will be Responses of previous RPCs, the rest will be incoming Messages for dispatch.</p>
@@ -25,21 +25,21 @@
<p>To acknowledge a message send a MessageAck to the server (one way). Fill in the MessageAck with details of the consumerId, sessionId, clientId and any transactionIds.</p>
-<h2 id="WireProtocol-WorkingwithResponses">Working with Responses</h2>
+<h2>Working with Responses</h2>
<p>When you create a connection, a producer and a consumer you will receive a Response to indicate the status of the request (such as did it work or fail). Since the protocol is asynchronous you can receive Response commands out of order; you could have multiple threads using the same connection/socket sending commands in parallel.</p>
-<p>So its usual in multi-threaded clients to have some kind of correlation Map to match Command ids with Response Ids so that you can know which operation in what thread worked or failed etc. See the Transport implementations in Java to see how we do that. e.g. see <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/ResponseCorrelator.java">ResponseCorrelator</a></p>
+<p>So its usual in multi-threaded clients to have some kind of correlation Map to match Command ids with Response Ids so that you can know which operation in what thread worked or failed etc. See the Transport implementations in Java to see how we do that. e.g. see <a shape="rect" href="https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/ResponseCorrelator.java">ResponseCorrelator</a></p>
-<h2 id="WireProtocol-IDs">IDs</h2>
+<h2>IDs</h2>
<p>It is currently a requirement of the client to automatically generate client, session, producer and consumer IDs which are typically Strings and indended to be globally unique. Similarly each Command has its own integer counter ID which is used for the client to correlate requests to responses; the client will typically use an incrementing rolling counter for these.</p>
-<h2 id="WireProtocol-Closingproducers,consumers,sessions,connections">Closing producers, consumers, sessions, connections</h2>
+<h2>Closing producers, consumers, sessions, connections</h2>
<p>To close a resource send a RemoveInfo command with the correct objectId for the producer, consumer, session, connection etc.</p>
-<h2 id="WireProtocol-JMSTransactions">JMS Transactions</h2>
+<h2>JMS Transactions</h2>
<p>Each transacted session generates a unique transaction ID which is passed along on any transaction message. To start, commit or rollback the client should send a TransactionInfo command oneway (no Response is generated).</p>
@@ -47,11 +47,11 @@
<p>Any messages sent or message acknowledgements made should also propogate the transaction Id.</p>
-<h2 id="WireProtocol-XATransactions">XA Transactions</h2>
+<h2>XA Transactions</h2>
<p>As above but using the XATransactionInfo. Also we pass an XAid rather than a transactionID.</p>
-<h1 id="WireProtocol-Finalthoughts">Final thoughts</h1>
+<h1>Final thoughts</h1>
-<p>If in doubt about a piece of the protocol, the easiest way to figure out what happens is to check the JMS client code. In particular check out the code of <a shape="rect" class="external-link" href="http://activemq.codehaus.org/maven/xref/org/activemq/ActiveMQSession.html" rel="nofollow">ActiveMQSession</a> which contains pretty much all the above logic. Pay particular attention to calls to <strong>syncSendCommand()</strong> and <strong>asyncSendCommand()</strong> when Commands are sent to the Message Broker</p></div>
+<p>If in doubt about a piece of the protocol, the easiest way to figure out what happens is to check the JMS client code. In particular check out the code of <a shape="rect" href="http://activemq.codehaus.org/maven/xref/org/activemq/ActiveMQSession.html">ActiveMQSession</a> which contains pretty much all the above logic. Pay particular attention to calls to <strong>syncSendCommand()</strong> and <strong>asyncSendCommand()</strong> when Commands are sent to the Message Broker</p></div>
diff --git a/ws-notification.xml b/ws-notification.xml
index 189b0b7..9d34eb5 100644
--- a/ws-notification.xml
+++ b/ws-notification.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h2 id="WSNotification-WS-Notification">WS-Notification</h2>
+<div class="wiki-content maincontent"><h2>WS-Notification</h2>
-<p>This page has now moved to the <a shape="rect" class="external-link" href="http://servicemix.apache.org/">ServiceMix site</a>. You can read about <a shape="rect" class="external-link" href="http://incubator.apache.org/servicemix/ws-notification.html">WS-Notification support here</a></p></div>
+<p>This page has now moved to the <a shape="rect" href="http://servicemix.apache.org/">ServiceMix site</a>. You can read about <a shape="rect" href="http://incubator.apache.org/servicemix/ws-notification.html">WS-Notification support here</a></p></div>
diff --git a/wsif.xml b/wsif.xml
index 60538d4..5707a5c 100644
--- a/wsif.xml
+++ b/wsif.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>The <a shape="rect" class="external-link" href="http://ws.apache.org/wsif/">Apache Web Service Invocation Framework (WSIF)</a> allows you to perform web service invocations using a number of different implementation protocols like Axis, local Java, EJB, JMS, JCA CCI etc.</p>
+<div class="wiki-content maincontent"><p>The <a shape="rect" href="http://ws.apache.org/wsif/">Apache Web Service Invocation Framework (WSIF)</a> allows you to perform web service invocations using a number of different implementation protocols like Axis, local Java, EJB, JMS, JCA CCI etc.</p>
-<p>For more information on how to use it with ActiveMQ, take a look at: <a shape="rect" class="external-link" href="http://servicemix.apache.org/wsif.html">http://servicemix.apache.org/wsif.html</a></p></div>
+<p>For more information on how to use it with ActiveMQ, take a look at: <a shape="rect" href="http://servicemix.apache.org/wsif.html">http://servicemix.apache.org/wsif.html</a></p></div>
diff --git a/xbean-xml-reference-41.xml b/xbean-xml-reference-41.xml
index 02f8060..a5cb050 100644
--- a/xbean-xml-reference-41.xml
+++ b/xbean-xml-reference-41.xml
@@ -1,615 +1,616 @@
-<div class="wiki-content maincontent"><h3 id="XBeanXMLReference4.1-ElementsByType">Elements By Type</h3>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.network.jms.InboundQueueBridge-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.network.jms.InboundQueueBridgeTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.InboundQueueBridge-types">org.apache.activemq.network.jms.InboundQueueBridge</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-inboundQueueBridge-element"><inboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Queue Bridge</p> <p></p></td></tr></tbody></table></div>
+<div class="wiki-content maincontent"><h3>Elements By Type</h3>
+<p><structured-macro ac:macro-id="6f250b79-d46d-4401-b957-573cb55a7594" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.InboundQueueBridge-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.InboundQueueBridge-types"><link-body>org.apache.activemq.network.jms.InboundQueueBridge</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundQueueBridge-element"><link-body><inboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6566803c-ad63-4df9-86de-34e7131084bc" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.BrokerService-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.BrokerServiceTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-broker-element"><broker></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Message Broker which consists of a number of transport connectors, network connectors and a persistence adaptor</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="f12c840b-1acf-4fff-9781-3335b5c1c08a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.BrokerService-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="broker-element"><link-body><broker></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="26091859-b5d9-48e2-b74e-8fc4d440ce06" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Message Broker which consists of a number of transport connectors, network connectors and a persistence adaptor</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.BrokerPlugin-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.BrokerPluginTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.BrokerPlugin-types">org.apache.activemq.broker.BrokerPlugin</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationPlugin-element"><authorizationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An authorization plugin where each operation on a destination is checked against an authorizationMap</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-connectionDotFilePlugin-element"><connectionDotFilePlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current connections</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-destinationDotFilePlugin-element"><destinationDotFilePlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jaasAuthenticationPlugin-element"><jaasAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a JAAS based authentication plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-loggingBrokerPlugin-element"><loggingBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A simple Broker interceptor which allows you to enable/disable logging.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleAuthenticationPlugin-element"><simpleAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a simple authentication plugin configured with a map of user-passwords and a map of user-groups</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="f9bd4430-a68a-46fb-b64a-b22560624247" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.BrokerPlugin-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.BrokerPlugin-types"><link-body>org.apache.activemq.broker.BrokerPlugin</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationPlugin-element"><link-body><authorizationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8700f4d6-8eea-460d-9779-71ebdbb6d4ee" ac:name="html" ac:schema-version="1"><plain-text-body>An authorization plugin where each operation on a destination is checked against an authorizationMap</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="connectionDotFilePlugin-element"><link-body><connectionDotFilePlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9dd604e9-aaa0-4e55-a7de-f28c3ca3ed7b" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current connections</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="destinationDotFilePlugin-element"><link-body><destinationDotFilePlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ab301f12-0068-4516-aaab-8dd654b99ce4" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jaasAuthenticationPlugin-element"><link-body><jaasAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bbae1bbf-8f87-4f33-8583-e7d53500cd32" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based authentication plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="loggingBrokerPlugin-element"><link-body><loggingBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="847c4ee4-9fd7-482f-9383-05f9ebb1e10c" ac:name="html" ac:schema-version="1"><plain-text-body>A simple Broker interceptor which allows you to enable/disable logging.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleAuthenticationPlugin-element"><link-body><simpleAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="26d8081d-6938-490e-940a-feef4839d90c" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a simple authentication plugin configured with a map of user-passwords and a map of user-groups</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.store.jdbc.JDBCAdapter-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.store.jdbc.JDBCAdapterTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.JDBCAdapter-types">org.apache.activemq.store.jdbc.JDBCAdapter</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-blobJDBCAdapter-element"><blobJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are: </p><ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-bytesJDBCAdapter-element"><bytesJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter are:</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-db2JDBCAdapter-element"><db2JDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-defaultJDBCAdapter-element"><defaultJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. </p><p></p> sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that use this adapter are: <ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-imageBasedJDBCAdaptor-element"><imageBasedJDBCAdaptor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides JDBCAdapter since that uses IMAGE datatype to hold binary data. The databases/JDBC drivers that use this adapter are: </p><ul><li>Sybase</li><li>MS SQL</li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-oracleJDBCAdapter-element"><oracleJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. </p><p></p> Subclassing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that use this adapter are: <ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-streamJDBCAdapter-element"><streamJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the setBinaryStream()/getBinaryStream() operations. The databases/JDBC drivers that use this adapter are: </p><ul><li>Axion</li></ul> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="864d3bef-9532-44ed-8bf3-b4bb0677930d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.jdbc.JDBCAdapter-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCAdapter</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="blobJDBCAdapter-element"><link-body><blobJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="585680b1-3fdf-49f0-a524-02d983ad785e" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="bytesJDBCAdapter-element"><link-body><bytesJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="406b3457-e16a-4009-bf72-696a51e60533" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter are:</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="db2JDBCAdapter-element"><link-body><db2JDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1d549cd8-0cfb-4e9d-823f-ed19d67cdc27" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="defaultJDBCAdapter-element"><link-body><defaultJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f7fad239-c6d4-4856-9245-d726c17a55bf" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. <p/> sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="imageBasedJDBCAdaptor-element"><link-body><imageBasedJDBCAdaptor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="61878c8d-b624-46a9-a29c-0898b6490d21" ac:name="html" ac:schema-version="1"><plain-text-body>Provides JDBCAdapter since that uses IMAGE datatype to hold binary data. The databases/JDBC drivers that use this adapter are: <ul> <li>Sybase</li> <li>MS SQL</li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oracleJDBCAdapter-element"><link-body><oracleJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8474344a-4bc2-4758-adcf-d8efdcffe801" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. <p/> Subclassing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="streamJDBCAdapter-element"><link-body><streamJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e5611a53-b04f-4983-9a12-9d608973ccc7" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the setBinaryStream()/getBinaryStream() operations. The databases/JDBC drivers that use this adapter are: <ul> <li>Axion</li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.virtual.VirtualDestination-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.virtual.VirtualDestinationTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.virtual.VirtualDestination-types">org.apache.activemq.broker.region.virtual.VirtualDestination</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeQueue-element"><compositeQueue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a virtual queue which forwards to a number of other destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeTopic-element"><compositeTopic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a virtual topic which forwards to a number of other destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-virtualTopic-element"><virtualTopic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/virtual-destinations.html">Virtual Topics</a> using a prefix and postfix. The virtual destination creates a wildcard that is then used to look up all active queue subscriptions which match.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="4212f9b2-7f2c-4d1c-8c83-a22ec7f49f72" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.virtual.VirtualDestination-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.virtual.VirtualDestination-types"><link-body>org.apache.activemq.broker.region.virtual.VirtualDestination</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeQueue-element"><link-body><compositeQueue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c0fd4aa0-b9cb-4f8e-8121-c2972337319f" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual queue which forwards to a number of other destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeTopic-element"><link-body><compositeTopic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6b8ffd8a-494e-41f2-bb20-432526d3ba59" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual topic which forwards to a number of other destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="virtualTopic-element"><link-body><virtualTopic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ed682a29-44cb-4fd8-aabd-e6768825b580" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/virtual-destinations.html">Virtual Topics</a> using a prefix and postfix. The virtual destination creates a wildcard that is then used to look up all active queue subscriptions which match.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PolicyMap-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.policy.PolicyMapTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PolicyMap-types">org.apache.activemq.broker.region.policy.PolicyMap</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-policyMap-element"><policyMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="782bbbe5-54b5-4f1f-b60e-9b5f326a8265" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PolicyMap-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PolicyMap-types"><link-body>org.apache.activemq.broker.region.policy.PolicyMap</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyMap-element"><link-body><policyMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9e8782ea-60db-4d7b-b9db-2d050fe57322" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.policy.PendingMessageLimitStrategyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types">org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-constantPendingMessageLimitStrategy-element"><constantPendingMessageLimitStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-prefetchRatePendingMessageLimitStrategy-element"><prefetchRatePendingMessageLimitStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This PendingMessageLimitStrategy sets the maximum pending message limit value to be a multiplier of the prefetch limit of the subscription.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="2a01ae42-efcc-405f-8d87-82133d405c62" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types"><link-body>org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="constantPendingMessageLimitStrategy-element"><link-body><constantPendingMessageLimitStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="919914d3-4dd8-4a64-a58b-27a64b391727" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="prefetchRatePendingMessageLimitStrategy-element"><link-body><prefetchRatePendingMessageLimitStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b91ba3d7-622c-4054-abf1-79f2e6761005" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy sets the maximum pending message limit value to be a multiplier of the prefetch limit of the subscription.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types">org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-fixedCountSubscriptionRecoveryPolicy-element"><fixedCountSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-fixedSizedSubscriptionRecoveryPolicy-element"><fixedSizedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed amount of memory available in RAM for message history which is evicted in time order.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-lastImageSubscriptionRecoveryPolicy-element"><lastImageSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-noSubscriptionRecoveryPolicy-element"><noSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This is the default Topic recovery policy which does not recover any messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-queryBasedSubscriptionRecoveryPolicy-element"><queryBasedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user specific query mechanism to load any messages they may have missed.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-timedSubscriptionRecoveryPolicy-element"><timedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed buffer of messages around in memory and use that to recover new subscriptions.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="c491bee8-e749-4807-bd78-6dc3d8db79d5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types"><link-body>org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fixedCountSubscriptionRecoveryPolicy-element"><link-body><fixedCountSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="01ae5942-3a67-43c2-bb4b-46c1ad8af043" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fixedSizedSubscriptionRecoveryPolicy-element"><link-body><fixedSizedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a5ec0f1d-9f40-4a56-99a9-3ede7e16155e" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed amount of memory available in RAM for message history which is evicted in time order.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="lastImageSubscriptionRecoveryPolicy-element"><link-body><lastImageSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4e5fbcdc-7e2f-41ee-94cb-da212fcaf995" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="noSubscriptionRecoveryPolicy-element"><link-body><noSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bcbd198b-1eb2-41ae-9ae8-e3abf70d0934" ac:name="html" ac:schema-version="1"><plain-text-body>This is the default Topic recovery policy which does not recover any messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queryBasedSubscriptionRecoveryPolicy-element"><link-body><queryBasedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d593b6ae-4225-484c-9df8-3cde12442598" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user specific query mechanism to load any messages they may have missed.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="timedSubscriptionRecoveryPolicy-element"><link-body><timedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="585bc150-6280-4dde-88a4-94512ab54718" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed buffer of messages around in memory and use that to recover new subscriptions.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.store.jdbc.StatementsTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-statements-element"><statements></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="96e32336-683d-43b0-9f83-40596a484a5a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.jdbc.Statements-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="statements-element"><link-body><statements></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="754cd5a5-a2b2-42ee-97df-e1893c3d25c9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
+
+<p><structured-macro ac:macro-id="663aaa64-19c4-4ad2-a8a2-1d5ff6d3a7bf" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.jmx.ManagementContext-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.jmx.ManagementContext-types"><link-body>org.apache.activemq.broker.jmx.ManagementContext</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="managementContext-element"><link-body><managementContext></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c6eb60d1-b088-4a52-a9a6-322a55ffb5c6" ac:name="html" ac:schema-version="1"><plain-text-body>A Flow provides different dispatch policies within the NMR</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.jmx.ManagementContext-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.jmx.ManagementContextTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.jmx.ManagementContext-types">org.apache.activemq.broker.jmx.ManagementContext</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-managementContext-element"><managementContext></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Flow provides different dispatch policies within the NMR</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="64db8c83-8bba-4ce3-bd49-c66aa1d59c2d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.PersistenceAdapterFactory-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapterFactory-types"><link-body>org.apache.activemq.store.PersistenceAdapterFactory</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="journaledJDBC-element"><link-body><journaledJDBC></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c3cdda92-2aa5-44b5-9b07-d73b16e809a5" ac:name="html" ac:schema-version="1"><plain-text-body>Creates a default persistence model using the Journal and JDBC</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.store.PersistenceAdapterFactory-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.store.PersistenceAdapterFactoryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.PersistenceAdapterFactory-types">org.apache.activemq.store.PersistenceAdapterFactory</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-journaledJDBC-element"><journaledJDBC></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates a default persistence model using the Journal and JDBC</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="06bb7bdc-6f49-4328-8070-93fd37eca73e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.security.AuthorizationEntry-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.security.AuthorizationEntry-types"><link-body>org.apache.activemq.security.AuthorizationEntry</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationEntry-element"><link-body><authorizationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7e89966c-f76e-42af-a5be-10898b76fb91" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.security.AuthorizationEntry-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.security.AuthorizationEntryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.security.AuthorizationEntry-types">org.apache.activemq.security.AuthorizationEntry</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationEntry-element"><authorizationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="52d6fbe4-c2f6-4e3a-8fc0-f7a7384e39ce" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.DeadLetterStrategy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.DeadLetterStrategy-types"><link-body>org.apache.activemq.broker.region.policy.DeadLetterStrategy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="individualDeadLetterStrategy-element"><link-body><individualDeadLetterStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9d08c3a1-1238-445b-9899-ec727c5387a4" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link DeadLetterStrategy} where each destination has its own individual DLQ using the subject naming hierarchy.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="sharedDeadLetterStrategy-element"><link-body><sharedDeadLetterStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="59f5f710-5472-46f5-a9ea-b58b3a6c79e0" ac:name="html" ac:schema-version="1"><plain-text-body>A default implementation of {@link DeadLetterStrategy} which uses a constant destination.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.DeadLetterStrategy-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.policy.DeadLetterStrategyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.DeadLetterStrategy-types">org.apache.activemq.broker.region.policy.DeadLetterStrategy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-individualDeadLetterStrategy-element"><individualDeadLetterStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link DeadLetterStrategy} where each destination has its own individual DLQ using the subject naming hierarchy.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-sharedDeadLetterStrategy-element"><sharedDeadLetterStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A default implementation of {@link DeadLetterStrategy} which uses a constant destination.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="1ea7a9c5-effc-49ad-8b3f-041a8ec6e73a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">javax.jms.Topic-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="120610ad-c5c4-4095-af2c-755060ee6fd1" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic Destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-javax.jms.Topic-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Thejavax.jms.TopicTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Topic-types">javax.jms.Topic</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-topic-element"><topic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Topic Destination</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="85504d7c-2825-4a78-af5a-c2bf5f959e79" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.PersistenceAdapter-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jdbcPersistenceAdapter-element"><link-body><jdbcPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5cf5c4f4-656d-4369-98ba-c80f44212fcd" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="journalPersistenceAdapter-element"><link-body><journalPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="772775db-d84b-4530-a4e8-4f26e6ceee29" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="kahaPersistenceAdapter-element"><link-body><kahaPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5ea46e23-5da4-459f-8ce3-8bc5a08de4b0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="memoryPersistenceAdapter-element"><link-body><memoryPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1d1ac90e-189d-4cad-afc8-9336e93f8d62" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="quickJournalPersistenceAdapter-element"><link-body><quickJournalPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4104a861-d268-4091-bb71-9d35d215e5be" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="rapidPersistenceAdapter-element"><link-body><rapidPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="00bcd4d3-2e1f-4a3b-98dd-f4f20838922a" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.store.PersistenceAdapter-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.store.PersistenceAdapterTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jdbcPersistenceAdapter-element"><jdbcPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-journalPersistenceAdapter-element"><journalPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-kahaPersistenceAdapter-element"><kahaPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-memoryPersistenceAdapter-element"><memoryPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-quickJournalPersistenceAdapter-element"><quickJournalPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-rapidPersistenceAdapter-element"><rapidPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a2b9dcb1-cff9-4829-bbf2-b8845c10663c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PolicyEntry-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PolicyEntry-types"><link-body>org.apache.activemq.broker.region.policy.PolicyEntry</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyEntry-element"><link-body><policyEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a5e2e8ab-eb9e-4322-af11-cb1da7cc9d89" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link PolicyMap} for assigning policies to a specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PolicyEntry-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.policy.PolicyEntryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PolicyEntry-types">org.apache.activemq.broker.region.policy.PolicyEntry</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-policyEntry-element"><policyEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link PolicyMap} for assigning policies to a specific destination or a hierarchical wildcard area of destinations.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="c6ff972d-3af0-4671-9ecc-b79013a4918b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.DemandForwardingBridgeSupport-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.DemandForwardingBridgeSupport-types"><link-body>org.apache.activemq.network.DemandForwardingBridgeSupport</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeDemandForwardingBridge-element"><link-body><compositeDemandForwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="24a5436c-a037-496a-a0ac-64e378bcf6c2" ac:name="html" ac:schema-version="1"><plain-text-body>A demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="demandForwardingBridge-element"><link-body><demandForwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b43c2f9e-cbb4-4574-847c-bf8dc8dc6db2" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards messages from the local broker to the remote broker based on demand.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.network.DemandForwardingBridgeSupport-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.network.DemandForwardingBridgeSupportTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.DemandForwardingBridgeSupport-types">org.apache.activemq.network.DemandForwardingBridgeSupport</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeDemandForwardingBridge-element"><compositeDemandForwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-demandForwardingBridge-element"><demandForwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forwards messages from the local broker to the remote broker based on demand.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="8bab28c4-db6b-4231-a6ad-5e5d007bb717" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.OutboundQueueBridge-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.OutboundQueueBridge-types"><link-body>org.apache.activemq.network.jms.OutboundQueueBridge</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundQueueBridge-element"><link-body><outboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d272fd81-bb58-4bf7-802e-bc1d47095d25" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.network.jms.OutboundQueueBridge-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.network.jms.OutboundQueueBridgeTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.OutboundQueueBridge-types">org.apache.activemq.network.jms.OutboundQueueBridge</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-outboundQueueBridge-element"><outboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Queue Bridge</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a1a06a59-30ca-4892-8e9d-30198522bc14" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.memory.UsageManager-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="usageManager-element"><link-body><usageManager></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3833b648-88c3-4cff-8051-cf0d028b9fdc" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.memory.UsageManagerTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-usageManager-element"><usageManager></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="baf01508-5c4b-449c-aaab-597576948331" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCPersistenceAdapter</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jdbcPersistenceAdapter-element"><link-body><jdbcPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="337829aa-4de6-45fc-a30b-efc074539c50" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.store.jdbc.JDBCPersistenceAdapterTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types">org.apache.activemq.store.jdbc.JDBCPersistenceAdapter</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jdbcPersistenceAdapter-element"><jdbcPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="1b515cca-42f0-439c-a8b1-d01de92098ae" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.command.ActiveMQDestination-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="092bb7ae-e506-4649-b742-1a3d3921418a" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue Destination</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0ec5b04b-0b0c-4d8b-912b-c6c36ab14a18" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic Destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.command.ActiveMQDestinationTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-queue-element"><queue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Queue Destination</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-topic-element"><topic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Topic Destination</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="9910b824-d9cc-4d7e-8790-d2d11aa1b4f7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.InboundTopicBridge-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.InboundTopicBridge-types"><link-body>org.apache.activemq.network.jms.InboundTopicBridge</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundTopicBridge-element"><link-body><inboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e1d861d3-6342-4754-ae04-b9d2bee42f8f" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.network.jms.InboundTopicBridge-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.network.jms.InboundTopicBridgeTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.InboundTopicBridge-types">org.apache.activemq.network.jms.InboundTopicBridge</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-inboundTopicBridge-element"><inboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Topic Bridge</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="80d1dbbe-286a-454d-b2a6-3e2c0ee1ae2c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.JmsConnector-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsQueueConnector-element"><link-body><jmsQueueConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cdc70448-de7e-456c-97b5-dafbbab2a3ca" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Queue providers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsTopicConnector-element"><link-body><jmsTopicConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0d954536-c70a-4e86-b90b-d691a1dfdcb0" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Topic providers</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsConnector-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.network.jms.JmsConnectorTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jmsQueueConnector-element"><jmsQueueConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Queue providers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jmsTopicConnector-element"><jmsTopicConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Topic providers</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="af267f34-a266-481d-9787-f4a8a8ea6922" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.security.AuthorizationMap-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.security.AuthorizationMap-types"><link-body>org.apache.activemq.security.AuthorizationMap</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationMap-element"><link-body><authorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="546afddf-be49-4b04-bb78-e5c414b713e4" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleAuthorizationMap-element"><link-body><simpleAuthorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="765a67c1-3c61-4ada-9f57-ce54504af969" ac:name="html" ac:schema-version="1"><plain-text-body>An AuthorizationMap which is configured with individual DestinationMaps for each operation.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.security.AuthorizationMap-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.security.AuthorizationMapTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.security.AuthorizationMap-types">org.apache.activemq.security.AuthorizationMap</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationMap-element"><authorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleAuthorizationMap-element"><simpleAuthorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An AuthorizationMap which is configured with individual DestinationMaps for each operation.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="e392144e-dd08-4582-9758-314df2c35731" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.DispatchPolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.DispatchPolicy-types"><link-body>org.apache.activemq.broker.region.policy.DispatchPolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="roundRobinDispatchPolicy-element"><link-body><roundRobinDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5d2ef72f-43fb-422b-b2e8-58f796f3b1bd" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that matches the message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleDispatchPolicy-element"><link-body><simpleDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b509adaf-7f58-41a3-8c22-eb6484560ef0" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that matches the message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="strictOrderDispatchPolicy-element"><link-body><strictOrderDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5dfb9fd5-6482-45f8-aa27-8a7c07e11acc" ac:name="html" ac:schema-version="1"><plain-text-body>Dispatch policy that causes every subscription to see messages in the same order.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.DispatchPolicy-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.policy.DispatchPolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.DispatchPolicy-types">org.apache.activemq.broker.region.policy.DispatchPolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-roundRobinDispatchPolicy-element"><roundRobinDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Simple dispatch policy that sends a message to every subscription that matches the message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleDispatchPolicy-element"><simpleDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Simple dispatch policy that sends a message to every subscription that matches the message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-strictOrderDispatchPolicy-element"><strictOrderDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Dispatch policy that causes every subscription to see messages in the same order.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="3c641e10-dda9-487e-a231-591ede92da3e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">javax.jms.Queue-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c2b236ee-a21e-40be-a04e-47ac65f0226b" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue Destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-javax.jms.Queue-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Thejavax.jms.QueueTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Queue-types">javax.jms.Queue</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-queue-element"><queue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Queue Destination</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="aaaf8c72-eae8-449b-9e3b-f07bfc3560e4" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types"><link-body>org.apache.activemq.broker.region.policy.MessageEvictionStrategy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oldestMessageEvictionStrategy-element"><link-body><oldestMessageEvictionStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a562ad76-41df-4756-b9e9-df556ff497fc" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message first (which is the default).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oldestMessageWithLowestPriorityEvictionStrategy-element"><link-body><oldestMessageWithLowestPriorityEvictionStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5bbc0e5b-b58f-4635-a3b2-cccc7450b424" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message with the lowest priority first.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.policy.MessageEvictionStrategyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types">org.apache.activemq.broker.region.policy.MessageEvictionStrategy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-oldestMessageEvictionStrategy-element"><oldestMessageEvictionStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An eviction strategy which evicts the oldest message first (which is the default).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-oldestMessageWithLowestPriorityEvictionStrategy-element"><oldestMessageWithLowestPriorityEvictionStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An eviction strategy which evicts the oldest message with the lowest priority first.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="4f445466-63d6-447d-9aca-e1aea0642463" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.JmsMesageConvertor-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleJmsMessageConvertor-element"><link-body><simpleJmsMessageConvertor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="21708858-0fa5-402b-b0a4-822d96a5543d" ac:name="html" ac:schema-version="1"><plain-text-body>Converts Message from one JMS to another</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.network.jms.JmsMesageConvertorTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleJmsMessageConvertor-element"><simpleJmsMessageConvertor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Converts Message from one JMS to another</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="2d7c4792-6eaf-4479-a325-8009357bd969" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.DestinationInterceptor-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.DestinationInterceptor-types"><link-body>org.apache.activemq.broker.region.DestinationInterceptor</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="virtualDestinationInterceptor-element"><link-body><virtualDestinationInterceptor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cf479929-3280-4723-a973-60009c7ae476" ac:name="html" ac:schema-version="1"><plain-text-body>Implements <a href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a>.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.broker.region.DestinationInterceptor-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.broker.region.DestinationInterceptorTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.DestinationInterceptor-types">org.apache.activemq.broker.region.DestinationInterceptor</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-virtualDestinationInterceptor-element"><virtualDestinationInterceptor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements <a shape="rect" href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a>.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="7c309d39-5b62-4e0a-b230-062adcbeb630" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.OutboundTopicBridge-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.OutboundTopicBridge-types"><link-body>org.apache.activemq.network.jms.OutboundTopicBridge</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundTopicBridge-element"><link-body><outboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c678198-e0c2-49bd-ab0e-95b6045b72e5" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.network.jms.OutboundTopicBridge-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.network.jms.OutboundTopicBridgeTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.OutboundTopicBridge-types">org.apache.activemq.network.jms.OutboundTopicBridge</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-outboundTopicBridge-element"><outboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Topic Bridge</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="dc1f659b-8112-4c38-ab60-0349a279690c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.filter.DestinationMap-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.filter.DestinationMap-types"><link-body>org.apache.activemq.filter.DestinationMap</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationMap-element"><link-body><authorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bc70b291-503d-4737-bb1e-1bf06d72a7e2" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyMap-element"><link-body><policyMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="51eea35a-da92-4df2-a4b8-444a93403ebf" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-org.apache.activemq.filter.DestinationMap-types"></span></p>
-<h4 id="XBeanXMLReference4.1-Theorg.apache.activemq.filter.DestinationMapTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.filter.DestinationMap-types">org.apache.activemq.filter.DestinationMap</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationMap-element"><authorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-policyMap-element"><policyMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="913a42b8-333d-4478-a802-80cee4ed6339" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">authorizationEntry-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="authorizationEntry-element"><link-body><authorizationEntry></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="b27f68c3-84b1-4a4b-bb87-51e84601024f" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> admin </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="93cc5468-95cb-46f2-aee7-2394eab70b05" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> adminACLs </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="81cd1719-fb4d-410c-9538-4abab9fbfe2b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c9c7d25a-1869-4879-993a-263eaf0d1b2b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="56be1d13-5715-4f0d-84a8-847aa00da6f8" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> read </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9f723f00-2370-4a7f-afec-340c78290b5b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> readACLs </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="78df4d57-cc38-44fe-a045-3c59753d35a2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topic </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="02addfaf-b5ea-4057-adba-80bc2624f1ba" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> write </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b070ae32-c470-4e28-878f-92fedc6e026d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> writeACLs </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="83d5d6c3-297c-4a06-87d6-d68a81d0e6e7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-authorizationEntry-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<authorizationEntry>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationEntry-element"><authorizationEntry></a></em> Element</h3>
-<p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> admin </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> read </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> readACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> write </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> writeACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="adb05f0d-b103-4091-b480-fd6bc3b456de" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">authorizationMap-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="authorizationMap-element"><link-body><authorizationMap></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="80a94ddf-5bd8-4ab1-99e2-f637cf01bc4b" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> authorizationEntries </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="113a72b3-aa93-462e-899e-eee927faa285" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the individual entries on the authorization map</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> defaultEntry </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.security.AuthorizationEntry-types"><link-body>org.apache.activemq.security.AuthorizationEntry</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9516f085-bf7a-4c10-9034-74c17fffe0b2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> entries </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="321ef8b7-629e-433e-8690-0a3989d0db61" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to allow the destination map to be populated from a dependency injection framework such as Spring</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-authorizationMap-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<authorizationMap>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationMap-element"><authorizationMap></a></em> Element</h3>
-<p> </p><p>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.1">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> authorizationEntries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the individual entries on the authorization map</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> defaultEntry </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.security.AuthorizationEntry-types">org.apache.activemq.security.AuthorizationEntry</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> entries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to allow the destination map to be populated from a dependency injection framework such as Spring</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5425d19f-45c3-4443-b43e-ab28f9156c98" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">authorizationPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="authorizationPlugin-element"><link-body><authorizationPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f4e8c837-9a52-4eb8-99ea-e28c81760fe1" ac:name="html" ac:schema-version="1"><plain-text-body>An authorization plugin where each operation on a destination is checked against an authorizationMap</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> map </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.security.AuthorizationMap-types"><link-body>org.apache.activemq.security.AuthorizationMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="20e05e45-b7a3-4695-8123-f6e713182003" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-authorizationPlugin-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<authorizationPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationPlugin-element"><authorizationPlugin></a></em> Element</h3>
-<p> </p><p>An authorization plugin where each operation on a destination is checked against an authorizationMap</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.2">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> map </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.security.AuthorizationMap-types">org.apache.activemq.security.AuthorizationMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="c60f16d2-dbe0-4db2-a2b8-709edc6009d6" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">axionJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="axionJDBCAdapter-element"><link-body><axionJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="761e5f82-0d83-4575-8bd8-ee27af2a4b54" ac:name="html" ac:schema-version="1"><plain-text-body>Axion specific Adapter. Axion does not seem to support ALTER statements or sub-selects. This means: - We cannot auto upgrade the schema was we roll out new versions of ActiveMQ - We cannot delete durable sub messages that have be acknowledged by all consumers.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2a5e8d5a-8abd-4798-abe5-09a6bf00af7c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fcf8ac84-e4d4-4031-a869-daebcd037a42" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0cea308b-da1e-4e98-9cf8-41d916d73026" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-axionJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<axionJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-axionJDBCAdapter-element"><axionJDBCAdapter></a></em> Element</h3>
-<p> </p><p>Axion specific Adapter. Axion does not seem to support ALTER statements or sub-selects. This means: - We cannot auto upgrade the schema was we roll out new versions of ActiveMQ - We cannot delete durable sub messages that have be acknowledged by all consumers.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.3">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="69f129f2-e03a-499e-a035-b551b7e34390" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">blobJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="blobJDBCAdapter-element"><link-body><blobJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9c8ff437-11df-400f-8302-358b6cf9b59a" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e1b08abe-2c8b-49b2-83a9-08881af9202b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="27867791-c4a3-437c-8520-c3c7bf62face" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cb488f92-6c55-4480-b7e2-e5e58bdb810b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-blobJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<blobJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-blobJDBCAdapter-element"><blobJDBCAdapter></a></em> Element</h3>
-<p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are: </p><ul><li></li></ul><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.4">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="611cdefe-8f25-4cbc-84f5-861464a2fab9" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">broker-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="broker-element"><link-body><broker></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f95af95d-349f-46ad-9bfe-38bed770901d" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Message Broker which consists of a number of transport connectors, network connectors and a persistence adaptor</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adminView </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.jmx.BrokerView</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3cd30a41-37ec-4b2c-81cf-6eb7d6c30792" ac:name="html" ac:schema-version="1"><plain-text-body>Returns the administration view of the broker; used to create and destroy resources such as queues and topics. Note this method returns null if JMX is disabled.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> advisorySupport </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="61614332-a045-45b5-8c74-7c75a6de3e7f" ac:name="html" ac:schema-version="1"><plain-text-body>Allows the support of advisory messages to be disabled for performance reasons.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bcac9471-1ab1-4e43-b045-64993ef8afc2" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the name of this broker; which must be unique in the network</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerObjectName </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d07b54f1-a1c2-45f2-8544-fbba4157b9e0" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMX ObjectName for this broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dfe97683-e3d5-4d75-ab80-88553c9a703a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the directory in which the data files will be stored by default for the JDBC and Journal persistence adaptors.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> deleteAllMessagesOnStartup </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="24951720-16ee-4947-b181-30c7109a1408" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not all messages are deleted on startup - mostly only useful for testing.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationInterceptors </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.broker.region.DestinationInterceptor-types"><link-body>org.apache.activemq.broker.region.DestinationInterceptor</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="73af5984-ce2e-438e-ab9c-747f504712b9" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination interceptors to use</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PolicyMap-types"><link-body>org.apache.activemq.broker.region.policy.PolicyMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="25effa7a-9c42-477f-8729-a13b3a8b9256" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination specific policies available either for exact destinations or for wildcard areas of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="194f20bb-f8d5-4d4b-84e8-65187d5fcb70" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destinations which should be loaded/created on startup</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsBridgeConnectors </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="79760d5e-8ce5-4b83-b058-563641515843" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> keepDurableSubsActive </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d1bc7210-81db-4bb9-987e-450ed90e3843" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> managementContext </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.jmx.ManagementContext-types"><link-body>org.apache.activemq.broker.jmx.ManagementContext</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b2c3fd3c-4873-480e-ad6e-a5a662c78fc0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> masterConnectorURI </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="37595c13-f6c0-45d1-925f-44bba824f184" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> memoryManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="63a54b7c-1bfc-4cd5-a051-ad96c6c84c91" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageAuthorizationPolicy </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.security.MessageAuthorizationPolicy</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="11acaf0b-3485-4ab4-91ce-c3e8329ed3fa" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the policy used to decide if the current connection is authorized to consume a given message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkConnectorURIs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6a456dce-6983-4091-85c5-5568c6868c52" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkConnectors </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="86ad83ee-5895-4229-9173-dd7c718272cb" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the network connectors which this broker will use to connect to other brokers in a federated network</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistenceAdapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f1272846-3adc-49b4-995f-d3d56639ac25" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the persistence adaptor implementation to use for this broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistenceFactory </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapterFactory-types"><link-body>org.apache.activemq.store.PersistenceAdapterFactory</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a2ceaaba-4944-4089-9a7e-959ad38d4976" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistent </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cb69e6b0-e1f8-493b-b9c1-16ded1f8a98f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not persistence is enabled or disabled.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> plugins </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.broker.BrokerPlugin-types"><link-body>org.apache.activemq.broker.BrokerPlugin</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8b64d236-9ff1-4bae-be32-e5ac2a0ffa44" ac:name="html" ac:schema-version="1"><plain-text-body>Sets a number of broker plugins to install such as for security authentication or authorization</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> populateJMSXUserID </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0e4278b4-df9d-4d6d-9f7a-0bcec4c47ae5" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not the broker should populate the JMSXUserID header.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> proxyConnectors </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="99e937be-4bb1-49f2-9cb9-ef43535c9da1" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the network connectors which this broker will use to connect to other brokers in a federated network</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> shutdownOnMasterFailure </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c3184a6-8437-4de4-8cb9-983400c4f3e5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> start </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ae839157-99ea-47c5-85ee-168f1bebc663" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not the broker is started along with the ApplicationContext it is defined within. Normally you would want the broker to start up along with the ApplicationContext but sometimes when working with JUnit tests you may wish to start and stop the broker explicitly yourself.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6b032282-7a40-4e75-9449-c27aeebb49b6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> transportConnectorURIs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="142796e2-add6-47f1-b922-6fe53ed633ac" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> transportConnectors </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7478871e-f19e-4eed-8b7c-45b91e3c398f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the transport connectors which this broker will listen on for new clients</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useJmx </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="972d1372-f0dc-449e-b694-62e04a8a8240" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not the Broker's services should be exposed into JMX or not.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useLoggingForShutdownErrors </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3af5aa1c-c923-4a6e-9c46-ebda243c6681" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not we should use commons-logging when reporting errors when shutting down the broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useShutdownHook </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9997f17a-0bbc-4286-a96f-cdd664a3565b" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not we should use a shutdown handler to close down the broker cleanly if the JVM is terminated. It is recommended you leave this enabled.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useVirtualTopics </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="457eb4e0-b563-4bef-847b-8782eab79e92" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not <a href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a> should be supported by default if they have not been explicitly configured.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> vmConnectorURI </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c5505439-1c5a-40d2-be82-3a0825313ddc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-broker-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<broker>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-broker-element"><broker></a></em> Element</h3>
-<p> </p><p>An ActiveMQ Message Broker which consists of a number of transport connectors, network connectors and a persistence adaptor</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.5">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminView </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.jmx.BrokerView</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Returns the administration view of the broker; used to create and destroy resources such as queues and topics. Note this method returns null if JMX is disabled.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> advisorySupport </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Allows the support of advisory messages to be disabled for performance reasons.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the name of this broker; which must be unique in the network</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerObjectName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMX ObjectName for this broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the directory in which the data files will be stored by default for the JDBC and Journal persistence adaptors.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deleteAllMessagesOnStartup </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not all messages are deleted on startup - mostly only useful for testing.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationInterceptors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.DestinationInterceptor-types">org.apache.activemq.broker.region.DestinationInterceptor</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination interceptors to use</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PolicyMap-types">org.apache.activemq.broker.region.policy.PolicyMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination specific policies available either for exact destinations or for wildcard areas of destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destinations which should be loaded/created on startup</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsBridgeConnectors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> keepDurableSubsActive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> managementContext </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.jmx.ManagementContext-types">org.apache.activemq.broker.jmx.ManagementContext</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> masterConnectorURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> memoryManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageAuthorizationPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.security.MessageAuthorizationPolicy</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the policy used to decide if the current connection is authorized to consume a given message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkConnectorURIs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkConnectors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the network connectors which this broker will use to connect to other brokers in a federated network</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistenceAdapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the persistence adaptor implementation to use for this broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistenceFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.PersistenceAdapterFactory-types">org.apache.activemq.store.PersistenceAdapterFactory</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not persistence is enabled or disabled.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> plugins </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.BrokerPlugin-types">org.apache.activemq.broker.BrokerPlugin</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets a number of broker plugins to install such as for security authentication or authorization</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> populateJMSXUserID </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not the broker should populate the JMSXUserID header.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> proxyConnectors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the network connectors which this broker will use to connect to other brokers in a federated network</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> shutdownOnMasterFailure </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> start </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not the broker is started along with the ApplicationContext it is defined within. Normally you would want the broker to start up along with the ApplicationContext but sometimes when working with JUnit tests you may wish to start and stop the broker explicitly yourself.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transportConnectorURIs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transportConnectors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the transport connectors which this broker will listen on for new clients</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useJmx </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not the Broker's services should be exposed into JMX or not.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useLoggingForShutdownErrors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not we should use commons-logging when reporting errors when shutting down the broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useShutdownHook </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not we should use a shutdown handler to close down the broker cleanly if the JVM is terminated. It is recommended you leave this enabled.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useVirtualTopics </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not <a shape="rect" href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a> should be supported by default if they have not been explicitly configured.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> vmConnectorURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="d5b91d0f-8971-4304-8b3d-c40655785185" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">bytesJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="bytesJDBCAdapter-element"><link-body><bytesJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="063cf91b-2262-4e71-961b-5adb8f8ff0bc" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter are:</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1b3ce047-8fcd-48be-aa11-5540a7372151" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c5fd1093-b68c-42c6-90f0-9297dd7dc01e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="671543dc-40e4-481c-bdb9-b7e89e499066" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-bytesJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<bytesJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-bytesJDBCAdapter-element"><bytesJDBCAdapter></a></em> Element</h3>
-<p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter are:</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.6">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="7892e95a-8f65-427e-bf89-9e7b23dc6268" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">compositeDemandForwardingBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="compositeDemandForwardingBridge-element"><link-body><compositeDemandForwardingBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="26db9afd-1e64-4174-88f9-b902ed19a569" ac:name="html" ac:schema-version="1"><plain-text-body>A demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokers</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="412f5ca5-3c70-4857-ac32-9e0d665a6eb7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b212f5cc-bb0e-47d1-a322-811f3fb54132" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c709f9f9-5d4c-4577-85f5-02a9282c0ec0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="63ddb723-99fe-49b9-9f60-3972c630045a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ca5074c7-13f2-4b7d-bcec-ae74eb4d244b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="937299ae-cd86-473f-9608-a697ff7185bf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localBrokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b7424b56-35fb-449b-9b1d-0550ab408fff" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="42c72a0d-f1c0-4034-8d37-ebfc8931628f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkTTL </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6cbe1072-f1cd-40f1-9767-316b9bcb306d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f22f06b4-4441-4f2e-b352-d04ccc211a89" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0674f616-662f-40a8-a059-cc8038415584" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fa47bec4-32ff-4267-8e2f-aa76874af8a4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="09cfc929-3638-491e-b457-17af406717a2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3c543395-193c-41a1-99ac-643224a85061" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-compositeDemandForwardingBridge-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<compositeDemandForwardingBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-compositeDemandForwardingBridge-element"><compositeDemandForwardingBridge></a></em> Element</h3>
-<p> </p><p>A demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokers</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.7">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localBrokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkTTL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="e61c8130-b146-4668-b39a-e2edf7f29aed" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">compositeQueue-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="compositeQueue-element"><link-body><compositeQueue></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ecb3701e-354e-4917-855a-a4e72f2c42e3" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual queue which forwards to a number of other destinations.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> copyMessage </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="556c6b19-39ea-4bec-8c4f-a8dadff81683" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a copy of the message will be sent to each destination. Defaults to true so that the forward destination is set as the destination of the message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> forwardOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="72dace09-cf82-4427-b117-2525681ac39e" ac:name="html" ac:schema-version="1"><plain-text-body>Sets if the virtual destination is forward only (and so there is no physical queue to match the virtual queue) or if there is also a physical queue with the same name).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> forwardTo </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Collection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b67f6cee-7071-439f-b309-79201033e7d6" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the list of destinations to forward to</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6699baa0-d386-49ba-b4e1-331938e73fb8" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the name of this composite destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-compositeQueue-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<compositeQueue>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-compositeQueue-element"><compositeQueue></a></em> Element</h3>
-<p> </p><p>Represents a virtual queue which forwards to a number of other destinations.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.8">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> copyMessage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a copy of the message will be sent to each destination. Defaults to true so that the forward destination is set as the destination of the message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> forwardOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets if the virtual destination is forward only (and so there is no physical queue to match the virtual queue) or if there is also a physical queue with the same name).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> forwardTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Collection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the list of destinations to forward to</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the name of this composite destination</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="b6b3cf91-ef4d-4540-a314-3c4dad2e1f02" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">compositeTopic-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="compositeTopic-element"><link-body><compositeTopic></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ad70755f-f10d-4ee8-a255-beecbdcee7c5" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual topic which forwards to a number of other destinations.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> copyMessage </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="28ed13e0-5fc5-4d96-91bf-17bac8a286b2" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a copy of the message will be sent to each destination. Defaults to true so that the forward destination is set as the destination of the message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> forwardOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0f3592d6-1114-4ff8-b642-66221fcc2b83" ac:name="html" ac:schema-version="1"><plain-text-body>Sets if the virtual destination is forward only (and so there is no physical queue to match the virtual queue) or if there is also a physical queue with the same name).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> forwardTo </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Collection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b66fbd1d-6ed4-4969-84c8-e671a7fe7a5c" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the list of destinations to forward to</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c85632d-3d1a-4910-abbc-e822a95081f9" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the name of this composite destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-compositeTopic-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<compositeTopic>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-compositeTopic-element"><compositeTopic></a></em> Element</h3>
-<p> </p><p>Represents a virtual topic which forwards to a number of other destinations.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.9">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> copyMessage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a copy of the message will be sent to each destination. Defaults to true so that the forward destination is set as the destination of the message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> forwardOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets if the virtual destination is forward only (and so there is no physical queue to match the virtual queue) or if there is also a physical queue with the same name).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> forwardTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Collection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the list of destinations to forward to</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the name of this composite destination</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="dccb5b51-0f23-46ec-ad09-24c41ce7a3dc" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">connectionDotFilePlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="connectionDotFilePlugin-element"><link-body><connectionDotFilePlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="8177c9f5-73e2-4ac2-9032-ffad8eccc1b2" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current connections</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> file </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f0de8181-f5e0-43e6-80c0-0e2b57a2d522" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination file name to create the destination diagram</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-connectionDotFilePlugin-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<connectionDotFilePlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-connectionDotFilePlugin-element"><connectionDotFilePlugin></a></em> Element</h3>
-<p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current connections</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.10">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> file </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination file name to create the destination diagram</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a596b316-9505-4ae5-ac5a-02a0ce20a38b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">constantPendingMessageLimitStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="constantPendingMessageLimitStrategy-element"><link-body><constantPendingMessageLimitStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="4dfaa337-3a3e-483b-afc3-ed409ee6285a" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> limit </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9d775cde-b0d2-4368-83af-a60d82d1abc9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-constantPendingMessageLimitStrategy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<constantPendingMessageLimitStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-constantPendingMessageLimitStrategy-element"><constantPendingMessageLimitStrategy></a></em> Element</h3>
-<p> </p><p>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.11">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="9fb39baf-a54f-4ee7-b081-230acee315cc" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">db2JDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="db2JDBCAdapter-element"><link-body><db2JDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ca3a928a-70e2-408d-a0dc-7c4c078ca286" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="29e3b967-35f4-46f9-b522-7e869332fb57" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="733d47e3-d1a0-4ea4-b456-04b15e6c5911" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6b4dc676-e80d-4e0c-a5ac-93a46c5c7d6c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-db2JDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<db2JDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-db2JDBCAdapter-element"><db2JDBCAdapter></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.12">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="7f993342-cba7-4428-8863-5b8f21169a11" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">defaultJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="defaultJDBCAdapter-element"><link-body><defaultJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="c5f07c97-76d5-44ee-91f9-cd70c777d0e8" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. <p/> sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="41aeb391-2545-4a42-b902-3fd820f31773" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a4f09439-d58d-483b-80f4-b135e03ec7c5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0ac035d0-4adf-4678-932d-eb65799d7933" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-defaultJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<defaultJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-defaultJDBCAdapter-element"><defaultJDBCAdapter></a></em> Element</h3>
-<p> </p><p>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. </p><p></p> sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that use this adapter are: <ul><li></li></ul><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.13">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="cc9488e3-137c-40ac-9e0a-3c98163c50dd" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">demandForwardingBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="demandForwardingBridge-element"><link-body><demandForwardingBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="174fb4f3-06e0-49ac-92dd-98833ef89227" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards messages from the local broker to the remote broker based on demand.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e2ad2502-36de-4db3-89a6-60bae96f73ec" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="683276a2-733f-475d-b953-c3ca35a64ab7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6868a03b-b71d-42da-a86f-e2a0bf6e7576" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="de10ec83-966e-420b-8698-30d48b448c87" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bbafb8ec-3186-4b61-b201-f31bd81df271" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="52c74a27-92c2-4461-be4f-296e3978bc49" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localBrokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e4d853c9-6d50-4f57-b083-aa656511835c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="abdac847-9d44-4cf1-87b0-8357f498c919" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkTTL </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f2a3b05a-2b1a-4635-b702-152fac872ae5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3fa9ecca-05b5-4b3d-a533-f15f00bc12a0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="de2ba21d-32ab-48b0-9d6d-23037ddff1b0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4995636d-729a-4046-8dc6-5cfebbf70bcb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f68fbe49-2aca-4a21-b279-91100bb5a22b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f720b1a2-6180-4ae3-9039-3b466312b3e8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-demandForwardingBridge-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<demandForwardingBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-demandForwardingBridge-element"><demandForwardingBridge></a></em> Element</h3>
-<p> </p><p>Forwards messages from the local broker to the remote broker based on demand.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.14">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localBrokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkTTL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="275e2808-69e2-4314-aa24-635533ed234c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">destinationDotFilePlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="destinationDotFilePlugin-element"><link-body><destinationDotFilePlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="efdde440-dd14-4f84-8686-a0f88c806b15" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> file </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1ee8223d-36f9-4808-8bd4-c5fbabd84475" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination file name to create the destination diagram</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-destinationDotFilePlugin-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<destinationDotFilePlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-destinationDotFilePlugin-element"><destinationDotFilePlugin></a></em> Element</h3>
-<p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.15">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> file </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination file name to create the destination diagram</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="f268bfcc-e8d0-497c-9d9a-af3e3defbe17" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">destinationEntry-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="destinationEntry-element"><link-body><destinationEntry></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="98690c05-69c1-43f3-97ba-df87f330e5f8" ac:name="html" ac:schema-version="1"><plain-text-body>A default entry in a DestinationMap which holds a single value.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f36335c5-058d-4021-ac51-cb0012fd0a63" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2ecfde9a-b31a-4c1d-a23c-66ece4e45ba6" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topic </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="65f17db9-7ac3-48ff-b016-032855e4424b" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> value </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.Object</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2fefe2b8-a4d1-4a60-9f40-c9d0d93f06fa" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-destinationEntry-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<destinationEntry>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-destinationEntry-element"><destinationEntry></a></em> Element</h3>
-<p> </p><p>A default entry in a DestinationMap which holds a single value.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.16">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> value </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.Object</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="6607da38-59a7-4154-82a1-8469da0f914f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">fixedCountSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="fixedCountSubscriptionRecoveryPolicy-element"><link-body><fixedCountSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f475099e-7937-4c24-b70e-be78fcf088d1" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> maximumSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="200966b7-8911-4f05-8957-190ecddc65fd" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the maximum number of messages that this destination will hold around in RAM</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-fixedCountSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<fixedCountSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-fixedCountSubscriptionRecoveryPolicy-element"><fixedCountSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.17">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the maximum number of messages that this destination will hold around in RAM</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="dd8790ab-968b-427b-bf2b-6df8f5ad0dde" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">fixedSizedSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="fixedSizedSubscriptionRecoveryPolicy-element"><link-body><fixedSizedSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="a8baa682-3c40-49e7-9f5c-24196071f4d8" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed amount of memory available in RAM for message history which is evicted in time order.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> buffer </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.memory.list.MessageList</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b58b91df-8fff-4c83-b0f5-49f17755e7b3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maximumSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3621a3cb-414a-4290-b60f-20738c004cd0" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the maximum amount of RAM in bytes that this buffer can hold in RAM</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useSharedBuffer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="af6dc713-75f0-4154-a35a-004474c4819d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-fixedSizedSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<fixedSizedSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-fixedSizedSubscriptionRecoveryPolicy-element"><fixedSizedSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed amount of memory available in RAM for message history which is evicted in time order.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.18">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> buffer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.memory.list.MessageList</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the maximum amount of RAM in bytes that this buffer can hold in RAM</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useSharedBuffer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="7c1e43d3-1218-4030-8eb3-0a3a365e4b85" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">forwardingBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="forwardingBridge-element"><link-body><forwardingBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="0370d892-1f00-429d-93d5-1e1b557a727e" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards all messages from the local broker to the remote broker.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> clientId </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2fb9a7e1-1bea-4773-b7cb-18683084d136" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationFilter </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a6481760-a773-4745-8fe1-f1d4906a9387" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="657e77dd-9bc1-47cf-97d1-c322b69a558f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c35e68ed-e8c6-4044-b23a-2235a6a24362" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="58e8e8a3-e594-4f4f-ab6e-31e5a11d22cb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="148cb3a0-c0cd-48b8-bbe8-f625dc473781" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-forwardingBridge-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<forwardingBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-forwardingBridge-element"><forwardingBridge></a></em> Element</h3>
-<p> </p><p>Forwards all messages from the local broker to the remote broker.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.19">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clientId </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="f3ec2c58-3dba-41f0-bf4f-bf1beb93eb50" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">imageBasedJDBCAdaptor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="imageBasedJDBCAdaptor-element"><link-body><imageBasedJDBCAdaptor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="65c62b7b-fba5-4ba5-b52f-c70947f7da4b" ac:name="html" ac:schema-version="1"><plain-text-body>Provides JDBCAdapter since that uses IMAGE datatype to hold binary data. The databases/JDBC drivers that use this adapter are: <ul> <li>Sybase</li> <li>MS SQL</li> </ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b2b7ac23-37d3-4f9b-88d0-c9f54ed5de9d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dd273bdc-accb-4784-ae39-5549ffc118ae" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4a5fc942-fd24-47ec-b94c-74e94060cec3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-imageBasedJDBCAdaptor-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<imageBasedJDBCAdaptor>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-imageBasedJDBCAdaptor-element"><imageBasedJDBCAdaptor></a></em> Element</h3>
-<p> </p><p>Provides JDBCAdapter since that uses IMAGE datatype to hold binary data. The databases/JDBC drivers that use this adapter are: </p><ul><li>Sybase</li><li>MS SQL</li></ul><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.20">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="2403ce52-7e66-4d44-8905-7ae31803c159" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">inboundQueueBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="inboundQueueBridge-element"><link-body><inboundQueueBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="a68cae55-55b3-4319-9197-21d1df02bd77" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Queue Bridge</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b590497b-d4ed-40cc-8e48-9a69aa892886" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9ad68434-e4b1-4110-89da-94f41612704f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="065a8893-5885-459f-be37-fa221c8a098c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1ec63de3-318a-4202-bd9e-d958e3e379d4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundQueueName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="74eda646-7f15-4c41-bb26-a8eff0f7d10b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsConnector </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4164f782-a5d2-4d88-bcdf-4461fffa1e48" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="177cb948-9598-47c3-b16a-f1d043b91003" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a69d1531-046f-4057-8488-e456145c65f7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3c0101ab-0d64-4d2a-bf9b-bd7ecab95821" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="173ac518-cd04-46a2-a3f9-46c7b094544a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-inboundQueueBridge-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<inboundQueueBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-inboundQueueBridge-element"><inboundQueueBridge></a></em> Element</h3>
-<p> </p><p>Create an Inbound Queue Bridge</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.21">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Queue-types">javax.jms.Queue</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundQueueName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Queue-types">javax.jms.Queue</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="997f3bf3-9dbe-450c-8ea3-192a646a7c26" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">inboundTopicBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="inboundTopicBridge-element"><link-body><inboundTopicBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="90d301bb-e7a2-4566-90e5-2ea852eb2626" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Topic Bridge</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c74a463f-aacd-4dd2-a9a5-3ab9d0383818" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="aa1c551c-3dee-4b42-a71d-99cd581eda53" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e340972c-0a81-4d7f-8aa0-636d29e5d408" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerTopic </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5d3508b7-92a7-4096-9b6a-5c4d79c58f60" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3a1fdc66-38ee-4fbc-aaeb-3d53c7823c7b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundTopicName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="66411c45-f679-4a25-9230-cc5f732c5016" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsConnector </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ac0b661f-80a1-446a-b67d-301355af4c54" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="245fc22e-d30b-4bd6-9432-5336a1abdba4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c98308fd-656f-499c-a8ea-079009cae879" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerTopic </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="62885225-791e-49b7-ae94-9f6c142b02b9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c1cbb2f6-9098-44ac-b02a-e38008c1c544" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-inboundTopicBridge-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<inboundTopicBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-inboundTopicBridge-element"><inboundTopicBridge></a></em> Element</h3>
-<p> </p><p>Create an Inbound Topic Bridge</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.22">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Topic-types">javax.jms.Topic</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundTopicName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Topic-types">javax.jms.Topic</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="1db9df86-723e-46a9-9c23-7cd1f7d029e2" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">individualDeadLetterStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="individualDeadLetterStrategy-element"><link-body><individualDeadLetterStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="99a982c6-142d-4f12-96f7-bf7c594aeb10" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link DeadLetterStrategy} where each destination has its own individual DLQ using the subject naming hierarchy.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> queuePrefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="252faebb-34da-4112-82b2-30db0aa01bf3" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix to use for all dead letter queues for queue messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topicPrefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="16b81931-a930-4eb8-8c70-253db71168a8" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix to use for all dead letter queues for topic messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useQueueForQueueMessages </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b2b6cb0d-2f02-4d29-a247-0b902544e250" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a queue or topic should be used for queue messages sent to a DLQ. The default is to use a Queue</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useQueueForTopicMessages </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dca520bc-2e31-450b-8869-1e23ef60c2cc" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a queue or topic should be used for topic messages sent to a DLQ. The default is to use a Queue</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-individualDeadLetterStrategy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<individualDeadLetterStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-individualDeadLetterStrategy-element"><individualDeadLetterStrategy></a></em> Element</h3>
-<p> </p><p>A {@link DeadLetterStrategy} where each destination has its own individual DLQ using the subject naming hierarchy.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.23">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queuePrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix to use for all dead letter queues for queue messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topicPrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix to use for all dead letter queues for topic messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useQueueForQueueMessages </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a queue or topic should be used for queue messages sent to a DLQ. The default is to use a Queue</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useQueueForTopicMessages </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a queue or topic should be used for topic messages sent to a DLQ. The default is to use a Queue</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="cc3eb029-c972-4c02-be54-6d3b3832f156" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">informixJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="informixJDBCAdapter-element"><link-body><informixJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="24fa83bb-18f0-44bd-a4ef-a58eed489bf8" ac:name="html" ac:schema-version="1"><plain-text-body>JDBC Adapter for Informix database. Because Informix database restricts length of composite primary keys, length of <i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters. Therefore be sure not to use longer names for container name and subscription id than 150 characters.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7ead124b-1e3c-4553-8d87-248f22077df3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="082564c5-e593-4189-bd81-95ad33c61f7c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d0ea3ba2-150a-40f9-ae80-b58d4b178697" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-informixJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<informixJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-informixJDBCAdapter-element"><informixJDBCAdapter></a></em> Element</h3>
-<p> </p><p>JDBC Adapter for Informix database. Because Informix database restricts length of composite primary keys, length of <i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters. Therefore be sure not to use longer names for container name and subscription id than 150 characters.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.24">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="f82b9ead-d2bd-4313-80ae-8f12415537e5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jaasAuthenticationPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jaasAuthenticationPlugin-element"><link-body><jaasAuthenticationPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9616178e-f85e-4d0e-a1ef-55a02494c8e6" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based authentication plugin</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> configuration </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3c244f5c-017f-4afb-88fc-bbd5b364d75c" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JAAS configuration domain name used</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoverLoginConfig </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cdaa434c-4718-4428-ad75-570b1e0a387d" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables the auto-discovery of the login.config file for JAAS to initialize itself. This flag is enabled by default such that if the <b>java.security.auth.login.config</b> system property is not defined then it is set to the location of the <b>login.config</b> file on the classpath.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-jaasAuthenticationPlugin-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<jaasAuthenticationPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-jaasAuthenticationPlugin-element"><jaasAuthenticationPlugin></a></em> Element</h3>
-<p> </p><p>Provides a JAAS based authentication plugin</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.25">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> configuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JAAS configuration domain name used</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoverLoginConfig </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables the auto-discovery of the login.config file for JAAS to initialize itself. This flag is enabled by default such that if the <b>java.security.auth.login.config</b> system property is not defined then it is set to the location of the <b>login.config</b> file on the classpath.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="8c9e9df0-3b37-4673-ac28-cc20341faaa3" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jdbcPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jdbcPersistenceAdapter-element"><link-body><jdbcPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5fb95f7e-e65c-4e28-a61f-41698ab0a198" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bab297d2-3196-4761-94c3-10912c17ef45" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0e5d31fd-49e9-4fae-8ad8-db2627e28abc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> cleanupPeriod </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bbb94132-3106-4d98-a351-b969a763bc1c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4218d82e-05b5-4022-a2cd-9d0c02058faa" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a1330892-f3a2-45b9-87ea-96fcfa7e6dc7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataSource </p></td><td colspan="1" rowspan="1"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b0fcd83b-7ad9-4f72-a9f1-75aa2177dd3a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> databaseLocker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.store.jdbc.DatabaseLocker</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="de345d5c-fd51-42db-99f8-cf110846ea09" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the database locker strategy to use to lock the database on startup</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> ds </p></td><td colspan="1" rowspan="1"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9d71f505-29e2-409b-afb5-c297ff63a92b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> scheduledThreadPoolExecutor </p></td><td colspan="1" rowspan="1"><p> <em>edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ce716aba-20d0-46e4-93e7-4f508b8886d5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="54ac67e5-deeb-46a6-8b40-70339bd5db8b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="62df7bdc-0c97-4535-b63f-f63ad3dd9393" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useDatabaseLock </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dbc6ccc8-ef87-4a41-a753-e2dde9db1cb4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="51bad3c5-c7d4-46a1-87dc-19d7710628da" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activeio.command.WireFormat</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="02828dbc-3883-4404-b369-dc8417bf30a5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-jdbcPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<jdbcPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-jdbcPersistenceAdapter-element"><jdbcPersistenceAdapter></a></em> Element</h3>
-<p> </p><p>A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.26">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.JDBCAdapter-types">org.apache.activemq.store.jdbc.JDBCAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cleanupPeriod </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataSource </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> databaseLocker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.store.jdbc.DatabaseLocker</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the database locker strategy to use to lock the database on startup</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ds </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> scheduledThreadPoolExecutor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useDatabaseLock </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activeio.command.WireFormat</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="96da4da7-40b2-4364-a7e5-c11311fbcb09" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jmsQueueConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jmsQueueConnector-element"><link-body><jmsQueueConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="c7414d40-a006-44ea-8263-c6110cfcf154" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Queue providers</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c8bbd36a-b559-4d2b-a17d-10f482efb37a" ac:name="html" ac:schema-version="1"><plain-text-body>One way to configure the local connection - this is called by The BrokerService when the Connector is embedded</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="acc62c29-35c6-4bfc-9e23-b584012e166b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundQueueBridges </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.InboundQueueBridge-types"><link-body>org.apache.activemq.network.jms.InboundQueueBridge</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="98f8b168-60a1-4b9f-ab5a-470f484aa5f0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jndiLocalTemplate </p></td><td colspan="1" rowspan="1"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4af24863-13b0-459f-9444-1f238db35922" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jndiOutboundTemplate </p></td><td colspan="1" rowspan="1"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6ac2b2d5-188f-4d5f-85ef-50ad110f94d6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localConnectionFactoryName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a29e24c1-1c5c-4d03-9200-0d817b5097b8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d4e55a63-490c-4e1a-849e-1b8c4310aa27" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localQueueConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="70168284-44ab-45df-90c8-f597e2602b03" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localQueueConnectionFactory </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnectionFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="84c411ae-e6f8-4734-9de3-c6df16118b57" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="31ba4c0f-d390-474e-992b-b1a746fda1cc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="662f6f72-98f7-42c7-8e06-ef42bef616cf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cd60000d-3686-410f-907e-87721bbfc9cf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7da43f34-b529-420d-a780-dab70de593cb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueBridges </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.OutboundQueueBridge-types"><link-body>org.apache.activemq.network.jms.OutboundQueueBridge</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2dcedcf1-2ddc-4f77-a913-ef07615ee77b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b32b1486-ab98-4739-b279-968dd453d5da" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueConnectionFactory </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnectionFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7ac4ce59-84cb-4ca8-b9e1-685306b38d69" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueConnectionFactoryName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="01a38be1-acad-4588-b8cb-86ac713cc8e5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="730d4f47-c6e0-402d-931d-767c64763c3d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> replyToDestinationCacheSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6b23670c-4f4a-4c2a-b66b-b1e544dd623e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-jmsQueueConnector-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<jmsQueueConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-jmsQueueConnector-element"><jmsQueueConnector></a></em> Element</h3>
-<p> </p><p>A Bridge to other JMS Queue providers</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.27">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>One way to configure the local connection - this is called by The BrokerService when the Connector is embedded</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundQueueBridges </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.InboundQueueBridge-types">org.apache.activemq.network.jms.InboundQueueBridge</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jndiLocalTemplate </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jndiOutboundTemplate </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localConnectionFactoryName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localQueueConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localQueueConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnectionFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueBridges </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.OutboundQueueBridge-types">org.apache.activemq.network.jms.OutboundQueueBridge</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnectionFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueConnectionFactoryName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> replyToDestinationCacheSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="171e834e-13ba-4c09-ad8b-7703606960f8" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jmsTopicConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jmsTopicConnector-element"><link-body><jmsTopicConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="1378a401-d591-4241-84e4-263f9b2c8aef" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Topic providers</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5c98455a-ac62-4e0c-9ac0-046fe02070c4" ac:name="html" ac:schema-version="1"><plain-text-body>One way to configure the local connection - this is called by The BrokerService when the Connector is embedded</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0d70cb10-1130-4087-8313-9a549dde637d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundTopicBridges </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.InboundTopicBridge-types"><link-body>org.apache.activemq.network.jms.InboundTopicBridge</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="85c2c05c-0b65-42cd-825b-1277db56a1f9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jndiLocalTemplate </p></td><td colspan="1" rowspan="1"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="599ce845-cc54-4e16-85a9-fec570e2e29b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jndiOutboundTemplate </p></td><td colspan="1" rowspan="1"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d35b94ea-50f9-434a-979c-978ec702a39b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localConnectionFactoryName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="457fc6e9-3227-4b92-9efb-06fae334508b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2e60fd23-d6f1-4eaf-9db4-a16cbf9787dd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localTopicConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="31ad08bb-9140-4a6f-bdc8-122abb5edbdd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localTopicConnectionFactory </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnectionFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d4eac8dc-82e3-47c0-8c48-d8aab505d80a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="024e5b75-04b0-4f51-b9db-470ba5ae7f2a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ab86f575-f60c-49c7-896c-43612086678e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a83cc117-c450-49cb-8f6f-9722530c6430" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e191135d-50cf-4ed2-80ec-b7c3945c9552" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicBridges </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.OutboundTopicBridge-types"><link-body>org.apache.activemq.network.jms.OutboundTopicBridge</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="65214474-ef3a-4f90-a02d-d792aa8c1c86" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f391c4f6-aa5e-434c-8d9c-50433e17c49e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicConnectionFactory </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnectionFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fdb61e70-c6ae-485f-b332-21dfdda1ca87" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicConnectionFactoryName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="74197858-498b-461f-a18c-d05d9819bf3c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f2aa8ed0-c2c1-403e-9da6-da2943c02af9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> replyToDestinationCacheSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="619a1de8-12c7-408c-bb09-20e2f754ed16" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-jmsTopicConnector-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<jmsTopicConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-jmsTopicConnector-element"><jmsTopicConnector></a></em> Element</h3>
-<p> </p><p>A Bridge to other JMS Topic providers</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.28">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>One way to configure the local connection - this is called by The BrokerService when the Connector is embedded</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundTopicBridges </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.InboundTopicBridge-types">org.apache.activemq.network.jms.InboundTopicBridge</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jndiLocalTemplate </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jndiOutboundTemplate </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localConnectionFactoryName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localTopicConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localTopicConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnectionFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicBridges </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.OutboundTopicBridge-types">org.apache.activemq.network.jms.OutboundTopicBridge</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnectionFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicConnectionFactoryName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> replyToDestinationCacheSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="12cbaad0-22e2-4215-bfb5-8e1a19a542d7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">journalPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="journalPersistenceAdapter-element"><link-body><journalPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5be8462d-15c0-4f4b-a4d9-a9a45c372f36" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> journal </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a5fcc6ef-4094-469a-a801-fd13428d61e5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> longTermPersistence </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c0409dac-f06d-4c30-84b7-a11a5da5cfa3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="13188cf5-2e91-440b-acac-386d5769c67b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointWorkers </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8fbf67f9-8ee3-4eb7-acb0-8e6bd0218b43" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="155c0133-2bc1-44b8-bfc7-951fe6de89d8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0e7e8fd8-8b30-4102-a66b-430869e67533" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c6bb75f-bfc1-4b77-b9df-c4a90ab4b806" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-journalPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<journalPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-journalPersistenceAdapter-element"><journalPersistenceAdapter></a></em> Element</h3>
-<p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.29">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> longTermPersistence </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointWorkers </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="7602a90f-e934-4015-96c4-96d75b42b0e3" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">journaledJDBC-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="journaledJDBC-element"><link-body><journaledJDBC></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="8a47145d-114a-4426-b273-62db689426dd" ac:name="html" ac:schema-version="1"><plain-text-body>Creates a default persistence model using the Journal and JDBC</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="129d86b7-f4b4-417a-8d2d-a16971dbee0d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5296c55f-22d9-44dc-b50e-982330563ced" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f13ca3e7-cc6b-45e6-9e18-7dd11e51a883" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataSource </p></td><td colspan="1" rowspan="1"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5425788c-a420-49fc-bdb9-69fd14ba207f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jdbcAdapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCPersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5f5c1928-22ad-4c23-a81e-89c1a89afb0d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journal </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a957775b-4ef5-4c32-913f-06be5bbac7ca" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journalArchiveDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9fddbd63-b88c-4310-afdd-3b8695401305" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journalLogFileSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1c46ead6-ff69-458e-b6d5-759633b2e8f3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journalLogFiles </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="404aff09-d6a0-4c89-9819-c39dff423bed" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ff956269-e7f7-49ce-b27d-df1776606edb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3d782512-d07a-45b3-8e0c-4d6260fe0ef0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useJournal </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="60174645-6da8-48fd-9a95-c093e254e522" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useQuickJournal </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="20b1bf36-dbb8-4a03-b04c-c24b46f0f1d1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-journaledJDBC-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<journaledJDBC>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-journaledJDBC-element"><journaledJDBC></a></em> Element</h3>
-<p> </p><p>Creates a default persistence model using the Journal and JDBC</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.30">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.JDBCAdapter-types">org.apache.activemq.store.jdbc.JDBCAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataSource </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jdbcAdapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types">org.apache.activemq.store.jdbc.JDBCPersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journalArchiveDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journalLogFileSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journalLogFiles </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useJournal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useQuickJournal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="b5126ec8-b5fe-4aed-b1fd-bbb46fa7d00a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">kahaPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="kahaPersistenceAdapter-element"><link-body><kahaPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="3ec3362c-d8f8-4886-8ccb-ddde2f3a1ad8" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> dir </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="31a66a28-1f53-4c8d-b7d8-554c26b29ec1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ecd490b4-41f3-4815-9366-085f5a36639d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1f98ba83-31b6-4457-bf40-5f14e0390d8c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-kahaPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<kahaPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-kahaPersistenceAdapter-element"><kahaPersistenceAdapter></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.31">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dir </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5f5c280d-b08c-4498-a069-980f969e2240" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">lastImageSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="lastImageSubscriptionRecoveryPolicy-element"><link-body><lastImageSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="a367a5ec-74dc-4413-a504-83279e94b686" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-lastImageSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<lastImageSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-lastImageSubscriptionRecoveryPolicy-element"><lastImageSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</p><p></p>
+<p><structured-macro ac:macro-id="0732c7b7-b8fc-4619-b32a-0c6058605109" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">loggingBrokerPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="loggingBrokerPlugin-element"><link-body><loggingBrokerPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="3fbef875-1bed-426c-b404-1ad8453f901a" ac:name="html" ac:schema-version="1"><plain-text-body>A simple Broker interceptor which allows you to enable/disable logging.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> ackLog </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="919dd561-0152-44f5-bdf9-a78c17b4a5a1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="56e989e5-2f98-4d36-8d6a-7360ee72ac18" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> log </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1ab41c6f-0d5a-442b-add9-b60c961df64a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> next </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.Broker</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8722178a-d4a9-4ff6-9290-2a750c7f4928" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> sendLog </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0fb95821-4516-459e-aabd-00e6c7f93f9b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-loggingBrokerPlugin-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<loggingBrokerPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-loggingBrokerPlugin-element"><loggingBrokerPlugin></a></em> Element</h3>
-<p> </p><p>A simple Broker interceptor which allows you to enable/disable logging.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.32">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ackLog </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> log </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> next </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.Broker</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> sendLog </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="19568275-703b-4912-9b2b-027db6120ee7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">managementContext-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="managementContext-element"><link-body><managementContext></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="6846943b-00b7-41e4-9644-3f031853ee02" ac:name="html" ac:schema-version="1"><plain-text-body>A Flow provides different dispatch policies within the NMR</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> MBeanServer </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.MBeanServer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c3987006-fe2c-4f45-8ea0-207fb33f79f1" ac:name="html" ac:schema-version="1"><plain-text-body>Get the MBeanServer</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectorPath </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a292b609-e60e-4dc5-ac48-d11803bb751f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectorPort </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="17d9eb7b-a706-44d3-9094-f17d8da1121e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createConnector </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="da870eb4-f576-4637-84c3-a1eaab1787b6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createMBeanServer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c8ae26b7-8a98-4ca0-bc38-cb86224f5ca7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findTigerMbeanServer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="48b9acbb-9e7e-47f8-91c5-fc2876d10ba0" ac:name="html" ac:schema-version="1"><plain-text-body>Enables/disables the searching for the Java 5 platform MBeanServer</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmxDomainName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f93647cb-bf3b-4d34-86c3-8ad335628987" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> server </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.MBeanServer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5ef0659a-3340-4d10-875e-3ec28474bfc1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useMBeanServer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7929e82e-e4ca-4cfa-86f3-6710165582bf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-managementContext-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<managementContext>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-managementContext-element"><managementContext></a></em> Element</h3>
-<p> </p><p>A Flow provides different dispatch policies within the NMR</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.33">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> MBeanServer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.MBeanServer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Get the MBeanServer</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectorPath </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectorPort </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createMBeanServer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findTigerMbeanServer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables/disables the searching for the Java 5 platform MBeanServer</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmxDomainName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> server </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.MBeanServer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useMBeanServer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="b99c21a1-048c-45ca-93bf-3b3f5c38602a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">memoryPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="memoryPersistenceAdapter-element"><link-body><memoryPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="e2b5678a-abc5-4b55-9eaa-54ee3af132bb" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2e31ebec-90b0-4136-aaa0-b181438b2efd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6276b62b-6253-402e-b6ac-73f8f5819c7d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-memoryPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<memoryPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-memoryPersistenceAdapter-element"><memoryPersistenceAdapter></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.34">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5d3a602a-bdec-49d3-9a22-9010c159713c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">multicastNetworkConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="multicastNetworkConnector-element"><link-body><multicastNetworkConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="0d6feeed-1ab2-44f3-b5d9-66c5ce0f8ed1" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses some kind of multicast-like transport that communicates with potentially many remote brokers over a single logical {@link Transport} instance such as when using multicast. This implementation does not depend on multicast at all; any other group based transport could be used.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> bridge </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.DemandForwardingBridgeSupport-types"><link-body>org.apache.activemq.network.DemandForwardingBridgeSupport</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d2bec68c-b098-4547-af8c-9efeca6966f8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b44abd5e-6e33-4bfc-a181-0f40eb01f4b6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="207c7960-53c4-44cc-a8c3-80233c5d5c58" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionFilter </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="98e19093-d067-40dd-84fb-addb7e22eff8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="be66e746-f2e5-4591-a415-5bba802c906d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fad05e0c-b586-4bad-98af-5b42b29820c7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="060ecc6b-086c-407c-8f07-3293f6cd7e5e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6794ad8f-3296-4254-93af-658462aee1cd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c581a890-661c-4a79-a539-dec6b64c5299" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d0d45a59-67ba-4232-bd7a-db28064c68f2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localTransport </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2ab263c4-ce7b-4605-8414-76f476a50cff" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="25de2876-4764-4a56-a034-ba9cc537a687" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="85ccda84-8252-4e59-b59b-a8b1071aab2c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkTTL </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d84fd0b8-b56f-4c70-89e0-2a7bb18b2b18" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="10cbbc81-31c9-4448-ad1f-e2537a019175" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="af9a2c71-ea77-4b4a-aaea-05422853ce95" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteTransport </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e360999c-692f-4d3f-bce1-45583875cea9" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the remote transport implementation</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteURI </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="469d4e92-5ec2-47d0-ac7b-6c47d82e979d" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the remote transport URI to some group transport like <code>multicast://address:port</code></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="88852fe2-2a98-4350-a9cf-46e6779cc778" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="59b1878b-5636-43b5-a145-3cfa90ade6e3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-multicastNetworkConnector-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<multicastNetworkConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-multicastNetworkConnector-element"><multicastNetworkConnector></a></em> Element</h3>
-<p> </p><p>A network connector which uses some kind of multicast-like transport that communicates with potentially many remote brokers over a single logical {@link Transport} instance such as when using multicast. This implementation does not depend on multicast at all; any other group based transport could be used.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.35">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> bridge </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.DemandForwardingBridgeSupport-types">org.apache.activemq.network.DemandForwardingBridgeSupport</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localTransport </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkTTL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteTransport </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the remote transport implementation</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the remote transport URI to some group transport like <code>multicast://address:port</code></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="b287b896-b464-4201-b130-313624142e50" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">networkConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="networkConnector-element"><link-body><networkConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="44958d9f-cc55-402f-91a1-0f49c76cef4a" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses a discovery agent to detect the remote brokers available and setup a connection to each available remote broker</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="70c5db38-74a2-4959-bf8e-95e9e427eaf6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="af9b3bd3-567f-4740-a751-c71aa85ec2db" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionFilter </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6613ebb9-c9bc-4510-94ec-9159016f3888" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2aa0f761-3228-4014-a052-188ae1e442ef" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoveryAgent </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.discovery.DiscoveryAgent</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c8910e21-15b5-4aac-b890-41946dd7605c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoveryURI </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9b1ebae0-184a-4a6a-85b6-1cd55b4b0fd8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6a887a7b-7117-4933-aa55-74fe2956e578" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0d127117-807e-42c1-82a6-9b7162b73063" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3f6954db-114b-4223-81a2-e7aba7d6c0ec" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cb1224de-011a-4ef7-b603-f76ce64de729" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bf6f0fe7-43ae-4bba-a62b-fc6dc7df6341" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> failover </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="34dd1fd2-9a7d-4de1-8940-00af05fdbf28" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c3b2318a-f3b1-40ad-ae6a-790f96c7a4b0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f2b5c956-2da4-401f-a976-3c98cc532d08" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkTTL </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9c8fc037-73c3-41ed-88dd-beeb92a99fb0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="12110add-083d-4dd9-980a-22798a3ced77" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bd4830cc-2e3b-4afc-84ca-53b3b2212887" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="56babac8-d7ec-4406-9608-b338018fc804" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> uri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="edd2d3e0-b9e9-482e-bcb8-c09ac14e48de" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a19dd9c3-621f-4efd-9c82-2a80a8445208" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-networkConnector-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<networkConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-networkConnector-element"><networkConnector></a></em> Element</h3>
-<p> </p><p>A network connector which uses a discovery agent to detect the remote brokers available and setup a connection to each available remote broker</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.36">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoveryAgent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.discovery.DiscoveryAgent</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoveryURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Set</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> failover </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkTTL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> uri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="dbf72cd4-9059-47cf-9547-1a91a861fcff" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">noSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="noSubscriptionRecoveryPolicy-element"><link-body><noSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="4c63dfd3-c004-45c9-b3a3-bd7599045610" ac:name="html" ac:schema-version="1"><plain-text-body>This is the default Topic recovery policy which does not recover any messages.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-noSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<noSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-noSubscriptionRecoveryPolicy-element"><noSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This is the default Topic recovery policy which does not recover any messages.</p><p></p>
+<p><structured-macro ac:macro-id="a2f7a128-60c6-4d36-b822-d58c0b46ef31" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">oldestMessageEvictionStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="oldestMessageEvictionStrategy-element"><link-body><oldestMessageEvictionStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="839602e5-d6b8-45e4-a595-e051172b7ddb" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message first (which is the default).</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> evictExpiredMessagesHighWatermark </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c34620fc-f03d-4a13-8c4a-6c225c061bf4" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the high water mark on which we will eagerly evict expired messages from RAM</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-oldestMessageEvictionStrategy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<oldestMessageEvictionStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-oldestMessageEvictionStrategy-element"><oldestMessageEvictionStrategy></a></em> Element</h3>
-<p> </p><p>An eviction strategy which evicts the oldest message first (which is the default).</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.37">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> evictExpiredMessagesHighWatermark </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the high water mark on which we will eagerly evict expired messages from RAM</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a4546da6-465e-4081-9d31-51e91f7d9c03" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">oldestMessageWithLowestPriorityEvictionStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="oldestMessageWithLowestPriorityEvictionStrategy-element"><link-body><oldestMessageWithLowestPriorityEvictionStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="367d675c-a371-44cd-995b-9994c786017b" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message with the lowest priority first.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> evictExpiredMessagesHighWatermark </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c8fb0995-6d0e-4930-a682-40839d37315e" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the high water mark on which we will eagerly evict expired messages from RAM</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-oldestMessageWithLowestPriorityEvictionStrategy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<oldestMessageWithLowestPriorityEvictionStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-oldestMessageWithLowestPriorityEvictionStrategy-element"><oldestMessageWithLowestPriorityEvictionStrategy></a></em> Element</h3>
-<p> </p><p>An eviction strategy which evicts the oldest message with the lowest priority first.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.38">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> evictExpiredMessagesHighWatermark </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the high water mark on which we will eagerly evict expired messages from RAM</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5ca081fc-e595-4be5-8236-7db5470ee88b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">oracleJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="oracleJDBCAdapter-element"><link-body><oracleJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="61f9bb68-a0e1-4222-b13d-94ec3d41a6f5" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. <p/> Subclassing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ffd495b1-c95b-4731-95b5-23726f1a8042" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4e8e8f61-b3bb-405e-b61f-f05ea627e20b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6318e384-956e-4622-b144-56b02992ee0a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-oracleJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<oracleJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-oracleJDBCAdapter-element"><oracleJDBCAdapter></a></em> Element</h3>
-<p> </p><p>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. </p><p></p> Subclassing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that use this adapter are: <ul><li></li></ul><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.39">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="54a317ef-8619-4518-8013-80a04bebf688" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">outboundQueueBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="outboundQueueBridge-element"><link-body><outboundQueueBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="1ec46eb1-7260-4047-89cf-2d86dd8a0e4f" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Queue Bridge</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5ffc4fe5-0ef2-4517-85c1-d414b33a93b8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c36ee83d-5a7b-447e-b49e-f55d04726d7f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6dd5561b-1f60-4d84-bd9a-e483eb457e38" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="aa0ad857-d583-41b9-bdf5-028c729970d0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsConnector </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="180f74f7-d853-43aa-b45d-c1303a6d428d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9cd2772a-fd79-4a7e-b587-3247f21fd139" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3c31e23c-0d1a-4833-ad2a-c6e2415614f0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="573f98d5-ac08-4c97-9c80-a98cc4da4704" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d35c8b41-9f07-4004-8a10-5a0fb4ad6f1b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="05b49ac3-bb06-494a-a9d3-3a156f7a9e17" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-outboundQueueBridge-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<outboundQueueBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-outboundQueueBridge-element"><outboundQueueBridge></a></em> Element</h3>
-<p> </p><p>Create an Outbound Queue Bridge</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.40">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Queue-types">javax.jms.Queue</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Queue-types">javax.jms.Queue</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="29378e23-5652-48e6-a404-98347bffeafb" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">outboundTopicBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="outboundTopicBridge-element"><link-body><outboundTopicBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="8d2cd38a-02e1-4c77-85be-e86c2a7f1cee" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Topic Bridge</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="895b6ff9-798c-40f9-a70a-c8554e42be1c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0156ef6d-b346-403e-bd9c-5b584e869c3c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="42e712a3-e116-4aa7-aa18-79b1c7311e7e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerTopic </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="95da5afa-c790-4db3-95f2-f3d8cb6b7b07" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fa51352b-131d-4036-9e64-e1c7d76b0987" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsConnector </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f8569a56-12f7-4eda-8762-3a402c564614" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8b8c8c02-f28d-46a1-8604-03004e8dac31" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c93352da-28a4-4277-b561-a820adb72b02" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="28200795-0f71-4467-bb55-5abbd3eda9f9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerTopic </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="01406055-56b7-4c8c-ac9d-1e17aa8f299c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="405d4d03-998a-4e6a-84f7-a91496085092" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-outboundTopicBridge-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<outboundTopicBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-outboundTopicBridge-element"><outboundTopicBridge></a></em> Element</h3>
-<p> </p><p>Create an Outbound Topic Bridge</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.41">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Topic-types">javax.jms.Topic</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-javax.jms.Topic-types">javax.jms.Topic</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5a93f2d1-c28b-43ff-b6b9-f020cb50398a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">policyEntry-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="policyEntry-element"><link-body><policyEntry></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="a4db7004-e99d-4815-af9f-fa212fe2dc3b" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link PolicyMap} for assigning policies to a specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> deadLetterStrategy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.DeadLetterStrategy-types"><link-body>org.apache.activemq.broker.region.policy.DeadLetterStrategy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c0d60167-107e-4970-af6d-6177c2512051" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the policy used to determine which dead letter queue destination should be used</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ceb861ea-233d-4aa1-99fe-e1c63496d805" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.DispatchPolicy-types"><link-body>org.apache.activemq.broker.region.policy.DispatchPolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e12bc37f-79d0-4b71-b1f2-b03713e34c18" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> memoryLimit </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5a234c20-3a77-42ba-a978-1b0b8529e5e9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageEvictionStrategy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types"><link-body>org.apache.activemq.broker.region.policy.MessageEvictionStrategy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="029e7f07-007c-4540-b2c7-6d43a72235e5" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the eviction strategy used to decide which message to evict when the slow consumer needs to discard messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageGroupHashBucketCount </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dd9c562a-fab4-4165-a1b2-79ad715dfdde" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the number of hash buckets to use for the message group functionality. This is only applicable to using message groups to parallelize processing of a queue while preserving order across an individual JMSXGroupID header value. This value sets the number of hash buckets that will be used (i.e. the maximum possible concurrency).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> pendingMessageLimitStrategy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types"><link-body>org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cbfb581b-7733-4eba-9737-3ca72c840ad2" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the strategy to calculate the maximum number of messages that are allowed to be pending on consumers (in addition to their prefetch sizes). Once the limit is reached, non-durable topics can then start discarding old messages. This allows us to keep dispatching messages to slow consumers while not blocking fast consumers and discarding the messages oldest first.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2e93519d-0655-4122-986d-a282c016296e" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> sendAdvisoryIfNoConsumers </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d9678ff6-cb58-4206-a110-0c0e58fe6c5b" ac:name="html" ac:schema-version="1"><plain-text-body>Sends an advisory message if a non-persistent message is sent and there are no active consumers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> subscriptionRecoveryPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types"><link-body>org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7669b626-97e3-4ac8-bfee-8253ce2b5203" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topic </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="270c0d33-0644-4d6e-8434-b85ae80deb71" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-policyEntry-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<policyEntry>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-policyEntry-element"><policyEntry></a></em> Element</h3>
-<p> </p><p>Represents an entry in a {@link PolicyMap} for assigning policies to a specific destination or a hierarchical wildcard area of destinations.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.42">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deadLetterStrategy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.DeadLetterStrategy-types">org.apache.activemq.broker.region.policy.DeadLetterStrategy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the policy used to determine which dead letter queue destination should be used</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.DispatchPolicy-types">org.apache.activemq.broker.region.policy.DispatchPolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> memoryLimit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageEvictionStrategy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types">org.apache.activemq.broker.region.policy.MessageEvictionStrategy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the eviction strategy used to decide which message to evict when the slow consumer needs to discard messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageGroupHashBucketCount </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the number of hash buckets to use for the message group functionality. This is only applicable to using message groups to parallelize processing of a queue while preserving order across an individual JMSXGroupID header value. This value sets the number of hash buckets that will be used (i.e. the maximum possible concurrency).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> pendingMessageLimitStrategy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types">org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the strategy to calculate the maximum number of messages that are allowed to be pending on consumers (in addition to their prefetch sizes). Once the limit is reached, non-durable topics can then start discarding old messages. This allows us to keep dispatching messages to slow consumers while not blocking fast consumers and discarding the messages oldest first.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> sendAdvisoryIfNoConsumers </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sends an advisory message if a non-persistent message is sent and there are no active consumers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> subscriptionRecoveryPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types">org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="db6a2a5f-431e-483c-aad0-744bed365c53" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">policyMap-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="policyMap-element"><link-body><policyMap></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="00cd8090-652e-4015-9718-5777904ea139" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> defaultEntry </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PolicyEntry-types"><link-body>org.apache.activemq.broker.region.policy.PolicyEntry</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b651a52b-502d-4be7-9640-12daa7737adf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> entries </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="86e1680e-472c-47bc-8df7-984b9d84c9a3" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to allow the destination map to be populated from a dependency injection framework such as Spring</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> policyEntries </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7eb4a164-6185-41d7-8d7a-dd59a537bc51" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the individual entries on the policy map</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-policyMap-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<policyMap>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-policyMap-element"><policyMap></a></em> Element</h3>
-<p> </p><p>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.43">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> defaultEntry </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.policy.PolicyEntry-types">org.apache.activemq.broker.region.policy.PolicyEntry</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> entries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to allow the destination map to be populated from a dependency injection framework such as Spring</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> policyEntries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the individual entries on the policy map</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="7fcf9aac-c3a0-410a-86e3-420752d65a78" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">prefetchRatePendingMessageLimitStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="prefetchRatePendingMessageLimitStrategy-element"><link-body><prefetchRatePendingMessageLimitStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="e601dfb3-7052-4186-baa8-d34305cd2633" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy sets the maximum pending message limit value to be a multiplier of the prefetch limit of the subscription.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> multiplier </p></td><td colspan="1" rowspan="1"><p> <em>double</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="080347bc-5f3e-4838-b90b-5cb5d7f3fc0f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the multiplier of the prefetch size which will be used to define the maximum number of pending messages for non-durable topics before messages are discarded.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-prefetchRatePendingMessageLimitStrategy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<prefetchRatePendingMessageLimitStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-prefetchRatePendingMessageLimitStrategy-element"><prefetchRatePendingMessageLimitStrategy></a></em> Element</h3>
-<p> </p><p>This PendingMessageLimitStrategy sets the maximum pending message limit value to be a multiplier of the prefetch limit of the subscription.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.44">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> multiplier </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>double</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the multiplier of the prefetch size which will be used to define the maximum number of pending messages for non-durable topics before messages are discarded.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="dccfb38a-d338-432e-b906-4030239f1619" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">proxyConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="proxyConnector-element"><link-body><proxyConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="76ca8d68-dc18-4bf5-b79c-55923405060c" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> bind </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="82801d52-cfc0-4b66-9eb3-8444ff4448e1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a93fbee5-008a-4453-a650-c46cfd04c849" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1bed2179-5581-4d4f-b1f1-efe798b0b8ba" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remote </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1d5fe9c8-16b0-4ef7-91d3-3fca86eddfec" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> server </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.TransportServer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f31b9333-1726-4bd6-9b2c-d78728ec0f22" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-proxyConnector-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<proxyConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-proxyConnector-element"><proxyConnector></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.45">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> bind </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remote </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> server </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.TransportServer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="48504765-7344-4c0f-aff0-a35c626dd2b7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">queryBasedSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="queryBasedSubscriptionRecoveryPolicy-element"><link-body><queryBasedSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="3d5ba14c-c1f1-4b27-a07f-3a8cc9ff9a89" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user specific query mechanism to load any messages they may have missed.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> query </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.region.policy.MessageQuery</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="024e15f3-bae3-4990-8bb4-8c6d6297fd65" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the query strategy to load initial messages</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-queryBasedSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<queryBasedSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-queryBasedSubscriptionRecoveryPolicy-element"><queryBasedSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user specific query mechanism to load any messages they may have missed.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.46">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> query </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.region.policy.MessageQuery</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the query strategy to load initial messages</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="e78d5cba-a818-4768-bd2c-9b1c6a50b3bf" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">queue-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="931ee869-28c9-4f38-817e-eda8432c57ed" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue Destination</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> compositeDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1aa2e8a3-df49-4429-9d71-5028624c7787" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="55e1c633-94f6-44c0-9fce-945b195d6138" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> physicalName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3c37ec8c-25eb-43c7-88bc-1c0e569e6400" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> properties </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a15bd97d-9046-4ac5-8627-46adf615c698" ac:name="html" ac:schema-version="1"><plain-text-body>Get the properties from this instance for storing in JNDI</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-queue-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<queue>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-queue-element"><queue></a></em> Element</h3>
-<p> </p><p>An ActiveMQ Queue Destination</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.47">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> compositeDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> physicalName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> properties </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Get the properties from this instance for storing in JNDI</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="6c780842-5ff0-424d-9981-4c58fbf8e164" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">quickJournalPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="quickJournalPersistenceAdapter-element"><link-body><quickJournalPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="e78dc951-902f-460d-8f14-8d66af085798" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> journal </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="863190b1-6da0-4083-9e3f-d3128d160acd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> longTermPersistence </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d2630db0-95c0-4952-b4e7-a58809a5bbc4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="181595c1-52f7-4a73-a8b3-fc2d792b0f48" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointWorkers </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3497add2-a49d-4681-af98-d9076d0bc0bb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5f2ba65a-3fc2-4fb2-afd7-940c48c2c520" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6ed1ee35-1cb6-452b-a289-1ada2ff55171" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f0ea6048-4412-4692-af9f-a171248232fa" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-quickJournalPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<quickJournalPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-quickJournalPersistenceAdapter-element"><quickJournalPersistenceAdapter></a></em> Element</h3>
-<p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.48">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> longTermPersistence </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointWorkers </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="93b30250-d450-4896-a074-d83e1ef6b9dd" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">rapidPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="rapidPersistenceAdapter-element"><link-body><rapidPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5664a291-70e6-48ea-83ec-09ca4e55432a" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> journal </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fea280a8-89ec-42c8-b90f-d5731898b368" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3758b3ba-778b-4e11-81a9-29d612c05533" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointWorkers </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5f45e169-f311-40bb-b191-eea6b60d156f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="162bd6ac-cbf7-4658-8620-53a2d44f0db8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="93e1a8ed-2eba-4cb3-82ba-66bf72cd024a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="091b01e9-bf16-48c2-b0d9-32f9185f907f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-rapidPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<rapidPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-rapidPersistenceAdapter-element"><rapidPersistenceAdapter></a></em> Element</h3>
-<p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.49">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointWorkers </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="b9931199-46c6-4e28-b535-19148f62aa78" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">roundRobinDispatchPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="roundRobinDispatchPolicy-element"><link-body><roundRobinDispatchPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="e3fe5bf1-5517-4e4f-8260-dbab15fdf2a3" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that matches the message.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-roundRobinDispatchPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<roundRobinDispatchPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-roundRobinDispatchPolicy-element"><roundRobinDispatchPolicy></a></em> Element</h3>
-<p> </p><p>Simple dispatch policy that sends a message to every subscription that matches the message.</p><p></p>
+<p><structured-macro ac:macro-id="83e10f4f-efca-454a-bd39-48a54df0243a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">sharedDeadLetterStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="sharedDeadLetterStrategy-element"><link-body><sharedDeadLetterStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="3e2f93f9-bf26-4aa0-88c4-ac40c08d83f3" ac:name="html" ac:schema-version="1"><plain-text-body>A default implementation of {@link DeadLetterStrategy} which uses a constant destination.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> deadLetterQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="29206f4b-9ab9-406a-bbdf-a5194ebf26e9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-sharedDeadLetterStrategy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<sharedDeadLetterStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-sharedDeadLetterStrategy-element"><sharedDeadLetterStrategy></a></em> Element</h3>
-<p> </p><p>A default implementation of {@link DeadLetterStrategy} which uses a constant destination.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.50">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deadLetterQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="43db18c2-585f-4eaa-91df-63f920777c02" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleAuthenticationPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleAuthenticationPlugin-element"><link-body><simpleAuthenticationPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="14a97e4f-bdbb-497a-a82b-87e8315a3c72" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a simple authentication plugin configured with a map of user-passwords and a map of user-groups</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> userGroups </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5df4c95c-8e30-43d6-9554-94b8d6ea7df3" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the groups a user is in. The key is the user name and the value is a Set of groups</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userPasswords </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="83f7ec35-afba-4c34-aab1-2aedfc39f42b" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the map indexed by user name with the value the password</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-simpleAuthenticationPlugin-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<simpleAuthenticationPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-simpleAuthenticationPlugin-element"><simpleAuthenticationPlugin></a></em> Element</h3>
-<p> </p><p>Provides a simple authentication plugin configured with a map of user-passwords and a map of user-groups</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.51">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userGroups </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the groups a user is in. The key is the user name and the value is a Set of groups</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userPasswords </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the map indexed by user name with the value the password</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="66744d62-5e77-42fd-b5a4-f26fa857165b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleAuthorizationMap-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleAuthorizationMap-element"><link-body><simpleAuthorizationMap></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="1d108e8f-40dd-4f3b-a176-29b4453fd881" ac:name="html" ac:schema-version="1"><plain-text-body>An AuthorizationMap which is configured with individual DestinationMaps for each operation.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adminACLs </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.filter.DestinationMap-types"><link-body>org.apache.activemq.filter.DestinationMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="97b45b15-420d-4e5e-93ee-dc10c6b73e0f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> readACLs </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.filter.DestinationMap-types"><link-body>org.apache.activemq.filter.DestinationMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="efca98cb-0ca5-4ee5-8c24-c7740b463837" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> writeACLs </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.filter.DestinationMap-types"><link-body>org.apache.activemq.filter.DestinationMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="66739f3f-7d69-4153-8690-1d1db6cf44c9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-simpleAuthorizationMap-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<simpleAuthorizationMap>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-simpleAuthorizationMap-element"><simpleAuthorizationMap></a></em> Element</h3>
-<p> </p><p>An AuthorizationMap which is configured with individual DestinationMaps for each operation.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.52">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.filter.DestinationMap-types">org.apache.activemq.filter.DestinationMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> readACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.filter.DestinationMap-types">org.apache.activemq.filter.DestinationMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> writeACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.filter.DestinationMap-types">org.apache.activemq.filter.DestinationMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="b5ba6e62-2f54-47e9-8e3b-3e01620e2fba" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleDispatchPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleDispatchPolicy-element"><link-body><simpleDispatchPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="19b8be0f-cabd-44c1-83a5-e71a70d04266" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that matches the message.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-simpleDispatchPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<simpleDispatchPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-simpleDispatchPolicy-element"><simpleDispatchPolicy></a></em> Element</h3>
-<p> </p><p>Simple dispatch policy that sends a message to every subscription that matches the message.</p><p></p>
+<p><structured-macro ac:macro-id="eb82cb9b-09ec-48dd-ad96-cd1a96b1e14c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleJmsMessageConvertor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleJmsMessageConvertor-element"><link-body><simpleJmsMessageConvertor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5a64b6ea-c609-424f-9e3a-1227627c2b5b" ac:name="html" ac:schema-version="1"><plain-text-body>Converts Message from one JMS to another</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> connection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.Connection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b520a5b9-5e9a-4f1d-8a2e-b8dadc1c041a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-simpleJmsMessageConvertor-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<simpleJmsMessageConvertor>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-simpleJmsMessageConvertor-element"><simpleJmsMessageConvertor></a></em> Element</h3>
-<p> </p><p>Converts Message from one JMS to another</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.53">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.Connection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="367e387b-b33f-4d2f-ba17-32726ddbac46" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">statements-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="statements-element"><link-body><statements></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="71e1576d-98a3-4b94-814e-34b76831480e" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> addMessageStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bba5513d-31e7-48a4-9864-95d429f46be5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> binaryDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="355ad299-5d2f-48c4-8281-89177f5dd479" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> containerNameDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4473d911-710c-49bd-a07e-b391be66cb56" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createDurableSubStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a03fed8a-b1b8-48c9-8041-28adc97e82e1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createSchemaStatements </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="87d02f12-0fbd-4653-9b4b-f51d72e148e7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> deleteOldMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0f47ae14-8641-4c2f-bf6d-d51add4dba0c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> deleteSubscriptionStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="113377b2-3b36-4f4f-8e0d-cc98c6b33733" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dropSchemaStatements </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fdcb340b-179e-4648-92c1-77daca207dfc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableSubAcksTableName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7e781f30-5a01-40ad-9f7c-77a496c8f337" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findAllDestinationsStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c57d757-1d41-467f-a50b-c2d44a697e30" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findAllDurableSubMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ab637900-3ea9-4e69-8515-b35496147074" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findAllDurableSubsStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="653d6436-09e9-4b4a-8b15-88e9fc8ed9b4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findAllMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f96bb34c-b801-4204-8887-00f5bc09ed6d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findDurableSubStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a1890799-4132-44ab-89aa-b500b88c3252" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findLastSequenceIdInAcksStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5ade8696-3c99-40d1-a033-e5beae33ed73" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findLastSequenceIdInMsgsStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="44d81f71-bf75-4617-a7c5-ed52a0b9caec" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findMessageSequenceIdStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b6f2ca46-16dd-4065-878c-a6fa3c444d9e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findMessageStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e3dd7289-c3b4-47ea-b983-0695fff44da3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> lockCreateStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0f998093-3ce7-4108-a815-2fb566e88441" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> lockTableName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="99e31571-3cac-4aea-abf9-892097dc4b4f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> lockUpdateStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="936a4041-b93f-4d20-9fb7-fb31577b338e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> longDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="620fbad9-da17-4b19-9af3-28876b33548c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageTableName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f585dfac-814b-4a24-9607-a9886144d07d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> msgIdDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9d87cece-54eb-4bff-ba92-d650a4aacaf2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> removeAllMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="55397cf4-183b-4c03-a583-821cddd2d9ab" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> removeAllSubscriptionsStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="df6c25ce-ff7d-4685-9d88-4972a5dd3b34" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> removeMessageStatment </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f9c87590-c10c-4bbc-8136-6ba0e8d2157e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> sequenceDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="601ba2da-0304-479a-8b3e-d5f41a608d0e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> stringIdDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a729b173-628f-4b19-9b84-f4e911772fc5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> tablePrefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="952637e7-6f6a-4676-affd-dbe5001c01f1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> updateLastAckOfDurableSubStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="84a2ec7a-15ff-43ea-bbac-32c6d5feed34" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> updateMessageStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b68f3a98-1f4a-4fb5-9652-849155181d98" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7e0d4234-06a6-4895-9039-1da1f5399585" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useLockCreateWhereClause </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cd62ac48-deea-4498-9512-f63dabe09236" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-statements-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<statements>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-statements-element"><statements></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.54">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> addMessageStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> binaryDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> containerNameDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createDurableSubStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createSchemaStatements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deleteOldMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deleteSubscriptionStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dropSchemaStatements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableSubAcksTableName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findAllDestinationsStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findAllDurableSubMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findAllDurableSubsStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findAllMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findDurableSubStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findLastSequenceIdInAcksStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findLastSequenceIdInMsgsStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findMessageSequenceIdStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findMessageStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> lockCreateStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> lockTableName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> lockUpdateStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> longDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageTableName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> msgIdDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> removeAllMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> removeAllSubscriptionsStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> removeMessageStatment </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> sequenceDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> stringIdDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tablePrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> updateLastAckOfDurableSubStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> updateMessageStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useLockCreateWhereClause </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="c193a5b6-21ec-4dfd-b619-cb5d122305a1" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">streamJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="streamJDBCAdapter-element"><link-body><streamJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f7907a7e-c7af-4059-a833-d4316d459ea6" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the setBinaryStream()/getBinaryStream() operations. The databases/JDBC drivers that use this adapter are: <ul> <li>Axion</li> </ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="eb295cc5-95db-4ff0-b583-6c3639bec7b1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="24c49f70-8b2a-4836-b231-8eab368ed276" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bc2b8d4c-c8d4-4e0b-91f0-b853d7989a57" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-streamJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<streamJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-streamJDBCAdapter-element"><streamJDBCAdapter></a></em> Element</h3>
-<p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the setBinaryStream()/getBinaryStream() operations. The databases/JDBC drivers that use this adapter are: </p><ul><li>Axion</li></ul><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.55">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="91d5655c-3c47-46d5-a37d-f43fe580c992" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">strictOrderDispatchPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="strictOrderDispatchPolicy-element"><link-body><strictOrderDispatchPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="b9f0ab0b-c7be-444c-af2f-fbb08d0ab544" ac:name="html" ac:schema-version="1"><plain-text-body>Dispatch policy that causes every subscription to see messages in the same order.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-strictOrderDispatchPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<strictOrderDispatchPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-strictOrderDispatchPolicy-element"><strictOrderDispatchPolicy></a></em> Element</h3>
-<p> </p><p>Dispatch policy that causes every subscription to see messages in the same order.</p><p></p>
+<p><structured-macro ac:macro-id="baa44274-f618-45d9-8293-d14aaa4adc5b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">timedSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="timedSubscriptionRecoveryPolicy-element"><link-body><timedSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="c3833aac-ac5d-4777-832c-7ebd159e6d04" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed buffer of messages around in memory and use that to recover new subscriptions.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> recoverDuration </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1e2ba280-bdea-4a59-ba3b-c69c29a504c6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-timedSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<timedSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-timedSubscriptionRecoveryPolicy-element"><timedSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed buffer of messages around in memory and use that to recover new subscriptions.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.56">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> recoverDuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="79749659-f4f4-426c-9111-d07368d040c9" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">topic-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="52739ece-db7f-4310-bf54-18fd1e2cbc63" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic Destination</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> compositeDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="104718cf-de54-4036-86e3-6cc7e9f6a391" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d8643857-05a2-47d4-aef0-0c29134ee51e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> physicalName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="00de11c4-6771-4d44-b8e0-9eda48e29d20" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> properties </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bef21bdd-a2e4-4185-957c-0759f00d6779" ac:name="html" ac:schema-version="1"><plain-text-body>Get the properties from this instance for storing in JNDI</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-topic-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<topic>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-topic-element"><topic></a></em> Element</h3>
-<p> </p><p>An ActiveMQ Topic Destination</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.57">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> compositeDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> physicalName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> properties </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Get the properties from this instance for storing in JNDI</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="c8048212-d1a6-4701-95fb-31a66dbcdd79" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">transportConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="transportConnector-element"><link-body><transportConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ced2bb69-8238-4842-9e64-5d4f552f5590" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> broker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.Broker</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6470f181-c8d6-466d-a4df-fcfbe38ab8b3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerInfo </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.command.BrokerInfo</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c84b2d54-636f-47cb-9f4e-74caf5ddc933" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e73f9747-b651-434e-811b-24737950e158" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="429ff0e3-c767-4d83-9a26-905ff1be642f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> disableAsyncDispatch </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="55a8d3ca-2366-4527-a0bd-941bc494c265" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoveryAgent </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.discovery.DiscoveryAgent</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a973c950-06b1-4c99-8784-9ddc8af8b5ed" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoveryUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d04406a4-5268-445a-b2f0-58d59e949527" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageAuthorizationPolicy </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.security.MessageAuthorizationPolicy</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7509e4e2-7290-490a-8257-8ee21978af6f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the policy used to decide if the current connection is authorized to consume a given message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="15956d27-818d-427f-b9b1-ff8c8289935a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> server </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.TransportServer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c6297283-a7aa-4258-8c0d-922fd9e54d38" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="07cf398b-ff26-48ee-a53e-571d0beec7bd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> uri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="60baba75-5f81-49f2-b5ae-d9408181bb26" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the server transport URI to use if there is not a {@link TransportServer} configured via the {@link #setServer(TransportServer)} method. This value is used to lazy create a {@link TransportServer} instance</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-transportConnector-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<transportConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-transportConnector-element"><transportConnector></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.58">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> broker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.Broker</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerInfo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.command.BrokerInfo</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> disableAsyncDispatch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoveryAgent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.discovery.DiscoveryAgent</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoveryUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageAuthorizationPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.security.MessageAuthorizationPolicy</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the policy used to decide if the current connection is authorized to consume a given message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> server </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.TransportServer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> uri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the server transport URI to use if there is not a {@link TransportServer} configured via the {@link #setServer(TransportServer)} method. This value is used to lazy create a {@link TransportServer} instance</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="0f468208-b142-43a8-9073-a89c9b808d71" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">usageManager-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="usageManager-element"><link-body><usageManager></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f78d8e8d-a5c3-4488-a79f-fc07278ddf37" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> limit </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5117f648-2adf-4174-b41b-9ff0639aacf5" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the memory limit in bytes</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> limitKb </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c856e3dd-ed8d-44ef-a077-7784992a57b8" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the memory limit in kilobytes</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> limitMb </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ad1b0751-2a6a-40d5-b724-21c48f3613ec" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the memory limit in megabytes</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> parent </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.memory.UsageManager-types"><link-body>org.apache.activemq.memory.UsageManager</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e45f475d-e755-4aac-8a11-9a5819305f2c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> percentUsage </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4ef63cf6-fd4a-4577-8daa-403d28ee4ee8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> percentUsageMinDelta </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="00ccc5c3-f59b-4fb1-b1ae-e46e1e1a56d9" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the minimum number of percentage points the usage has to change before a UsageListener event is fired by the manager.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-usageManager-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<usageManager>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-usageManager-element"><usageManager></a></em> Element</h3>
-<p> </p><p>Used to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.59">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the memory limit in bytes</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limitKb </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the memory limit in kilobytes</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limitMb </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the memory limit in megabytes</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> parent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.memory.UsageManager-types">org.apache.activemq.memory.UsageManager</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> percentUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> percentUsageMinDelta </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the minimum number of percentage points the usage has to change before a UsageListener event is fired by the manager.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="d64f918d-dbb0-4613-b06f-30be25d97c6d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">virtualDestinationInterceptor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="virtualDestinationInterceptor-element"><link-body><virtualDestinationInterceptor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="7c9c7473-eb2b-4984-a379-579ed8336543" ac:name="html" ac:schema-version="1"><plain-text-body>Implements <a href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a>.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> virtualDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.broker.region.virtual.VirtualDestination-types"><link-body>org.apache.activemq.broker.region.virtual.VirtualDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b0d43b55-7746-426d-9db6-3d0bf297ebdb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-virtualDestinationInterceptor-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<virtualDestinationInterceptor>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-virtualDestinationInterceptor-element"><virtualDestinationInterceptor></a></em> Element</h3>
-<p> </p><p>Implements <a shape="rect" href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a>.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.60">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> virtualDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference4.1-org.apache.activemq.broker.region.virtual.VirtualDestination-types">org.apache.activemq.broker.region.virtual.VirtualDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="e2fa3c17-76d9-4a14-9f9a-050efacc8e97" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">virtualTopic-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="virtualTopic-element"><link-body><virtualTopic></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="be80aaa2-2ab4-427e-b59e-3a0a021f2bbc" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/virtual-destinations.html">Virtual Topics</a> using a prefix and postfix. The virtual destination creates a wildcard that is then used to look up all active queue subscriptions which match.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="78d67fe5-182a-464f-9431-188aea7623d2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> postfix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4b10451e-29dd-4ca9-bf1d-df1535ed30e5" ac:name="html" ac:schema-version="1"><plain-text-body>Sets any postix used to identify the queue consumers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1ce5167d-bcd8-443c-863a-aedafd3224d4" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix wildcard used to identify the queue consumers for a given topic</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference4.1-virtualTopic-element"></span></p>
-<h3 id="XBeanXMLReference4.1-The<virtualTopic>Element">The <em><a shape="rect" href="#XBeanXMLReference4.1-virtualTopic-element"><virtualTopic></a></em> Element</h3>
-<p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/virtual-destinations.html">Virtual Topics</a> using a prefix and postfix. The virtual destination creates a wildcard that is then used to look up all active queue subscriptions which match.</p><p></p>
-<h4 id="XBeanXMLReference4.1-Properties.61">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> postfix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets any postix used to identify the queue consumers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix wildcard used to identify the queue consumers for a given topic</p> <p></p></td></tr></tbody></table></div>
+<h3>Element Index</h3>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationEntry-element"><link-body><authorizationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1ab32fcd-08d1-4001-9540-aec3097cedba" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationMap-element"><link-body><authorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="11833122-b2de-4b88-82c9-4ae3a6d812b3" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationPlugin-element"><link-body><authorizationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="73f520e8-892d-47f0-81dd-40da493753c2" ac:name="html" ac:schema-version="1"><plain-text-body>An authorization plugin where each operation on a destination is checked against an authorizationMap</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="axionJDBCAdapter-element"><link-body><axionJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="65c7a132-ec2b-4029-8ee3-f6ae3295f76d" ac:name="html" ac:schema-version="1"><plain-text-body>Axion specific Adapter. Axion does not seem to support ALTER statements or sub-selects. This means: - We cannot auto upgrade the schema was we roll out new versions of ActiveMQ - We cannot delete durable sub messages that have be acknowledged by all consumers.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="blobJDBCAdapter-element"><link-body><blobJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8c704177-90ef-4844-93e1-ab40a0c07b10" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="broker-element"><link-body><broker></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b5190da9-fe04-4c35-aba6-cb5304489b85" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Message Broker which consists of a number of transport connectors, network connectors and a persistence adaptor</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="bytesJDBCAdapter-element"><link-body><bytesJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="74e3dfa2-bf61-4634-8419-383eaad4e504" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter are:</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeDemandForwardingBridge-element"><link-body><compositeDemandForwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a69ce882-63f5-44e5-ae4d-f5254fe2637b" ac:name="html" ac:schema-version="1"><plain-text-body>A demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeQueue-element"><link-body><compositeQueue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6a33d43a-6154-4682-806c-4bfec9e71062" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual queue which forwards to a number of other destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeTopic-element"><link-body><compositeTopic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5314ac5f-578b-400c-aabd-7d94a8717491" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual topic which forwards to a number of other destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="connectionDotFilePlugin-element"><link-body><connectionDotFilePlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6891af53-4e83-4cab-98cb-fedddedf0441" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current connections</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="constantPendingMessageLimitStrategy-element"><link-body><constantPendingMessageLimitStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="33fb374c-85c1-410a-89aa-93e130acfe96" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="db2JDBCAdapter-element"><link-body><db2JDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c171b035-6ec0-42fb-9399-828a36f1d212" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="defaultJDBCAdapter-element"><link-body><defaultJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f305c442-349a-4b5f-96b6-d9cb209f4dc3" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. <p/> sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="demandForwardingBridge-element"><link-body><demandForwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="944b5e8e-32ac-455f-a3d9-4ca7857aa4f7" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards messages from the local broker to the remote broker based on demand.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="destinationDotFilePlugin-element"><link-body><destinationDotFilePlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="06a3060f-ade8-4068-b910-a4c75aac10d3" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="destinationEntry-element"><link-body><destinationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a40c95e2-6d7c-4f08-9cc6-ee5a7974a6da" ac:name="html" ac:schema-version="1"><plain-text-body>A default entry in a DestinationMap which holds a single value.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fixedCountSubscriptionRecoveryPolicy-element"><link-body><fixedCountSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6b3201ab-7d63-498e-9e42-a2e186442173" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fixedSizedSubscriptionRecoveryPolicy-element"><link-body><fixedSizedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bafcaefd-3ff3-4ca7-a546-20137301ba4d" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed amount of memory available in RAM for message history which is evicted in time order.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="forwardingBridge-element"><link-body><forwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="186980aa-ae92-4188-a31a-8c003792b976" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards all messages from the local broker to the remote broker.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="imageBasedJDBCAdaptor-element"><link-body><imageBasedJDBCAdaptor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="508bc087-f303-461a-b38d-afd55ec33c22" ac:name="html" ac:schema-version="1"><plain-text-body>Provides JDBCAdapter since that uses IMAGE datatype to hold binary data. The databases/JDBC drivers that use this adapter are: <ul> <li>Sybase</li> <li>MS SQL</li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundQueueBridge-element"><link-body><inboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b528fcf2-9487-4114-8451-7996b3ce97d6" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundTopicBridge-element"><link-body><inboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3aaefa53-b629-4b92-9d5b-ac318183b2aa" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="individualDeadLetterStrategy-element"><link-body><individualDeadLetterStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c22c3335-f250-43f5-b78e-eb87a0e1f0fb" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link DeadLetterStrategy} where each destination has its own individual DLQ using the subject naming hierarchy.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="informixJDBCAdapter-element"><link-body><informixJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6a3256ef-2a49-45e0-ba7e-cf73b2d72687" ac:name="html" ac:schema-version="1"><plain-text-body>JDBC Adapter for Informix database. Because Informix database restricts length of composite primary keys, length of <i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters. Therefore be sure not to use longer names for container name and subscription id than 150 characters.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jaasAuthenticationPlugin-element"><link-body><jaasAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b1b06d39-3bfc-44a9-b946-dbdfeb7390d5" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based authentication plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jdbcPersistenceAdapter-element"><link-body><jdbcPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1b8b5db3-3cc2-4960-8af7-f2e0217a78c3" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsQueueConnector-element"><link-body><jmsQueueConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="44873f28-6645-4d63-8f2a-51d7dcdea3ff" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Queue providers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsTopicConnector-element"><link-body><jmsTopicConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="053ca8ff-6554-494e-aab9-a73ecea5e18f" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Topic providers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="journalPersistenceAdapter-element"><link-body><journalPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="767ffa1d-6cfb-40c2-b054-b59d05b0b31e" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="journaledJDBC-element"><link-body><journaledJDBC></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4c01c1a4-2bdf-4a4d-a9ee-60ef26d545d6" ac:name="html" ac:schema-version="1"><plain-text-body>Creates a default persistence model using the Journal and JDBC</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="kahaPersistenceAdapter-element"><link-body><kahaPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2a8b07e6-a0c7-4e20-8ac9-4dc578798e07" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="lastImageSubscriptionRecoveryPolicy-element"><link-body><lastImageSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="849b1526-3606-45ac-9df8-a976371f668b" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="loggingBrokerPlugin-element"><link-body><loggingBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="755c9d24-f733-4df3-bb63-5bd5e6051ba4" ac:name="html" ac:schema-version="1"><plain-text-body>A simple Broker interceptor which allows you to enable/disable logging.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="managementContext-element"><link-body><managementContext></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b9bf7887-9e78-48e3-9fbe-bc7b217a3689" ac:name="html" ac:schema-version="1"><plain-text-body>A Flow provides different dispatch policies within the NMR</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="memoryPersistenceAdapter-element"><link-body><memoryPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a03ce623-16d1-41e4-b40b-5691ee1974d2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="multicastNetworkConnector-element"><link-body><multicastNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b842326a-dd87-4fc1-821b-debb4e0a5997" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses some kind of multicast-like transport that communicates with potentially many remote brokers over a single logical {@link Transport} instance such as when using multicast. This implementation does not depend on multicast at all; any other group based transport could be used.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="networkConnector-element"><link-body><networkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="afd55305-c007-4695-94b6-3ec547186d44" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses a discovery agent to detect the remote brokers available and setup a connection to each available remote broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="noSubscriptionRecoveryPolicy-element"><link-body><noSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="11eaa6ec-c105-44c6-9bd6-e67083de58d3" ac:name="html" ac:schema-version="1"><plain-text-body>This is the default Topic recovery policy which does not recover any messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oldestMessageEvictionStrategy-element"><link-body><oldestMessageEvictionStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dee7c8a3-523c-437e-adf9-5e9f3a346d99" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message first (which is the default).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oldestMessageWithLowestPriorityEvictionStrategy-element"><link-body><oldestMessageWithLowestPriorityEvictionStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ea979d33-70e6-49c2-bf38-7e6cf3b97cc9" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message with the lowest priority first.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oracleJDBCAdapter-element"><link-body><oracleJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="56453f63-cd56-406f-b9e1-8cb1f0fd08cf" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. <p/> Subclassing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that use this adapter are: <ul> <li></li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundQueueBridge-element"><link-body><outboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2af1e94d-b5c5-44cd-8af5-b6cf4547a448" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundTopicBridge-element"><link-body><outboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="34f708ec-d948-45bc-b48c-6f4df9373c3f" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyEntry-element"><link-body><policyEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9da8eb77-f7ea-47d3-b1d1-978171909fc2" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link PolicyMap} for assigning policies to a specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyMap-element"><link-body><policyMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0ab389ea-9410-42b6-a424-0afb8d4367a5" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="prefetchRatePendingMessageLimitStrategy-element"><link-body><prefetchRatePendingMessageLimitStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="368431d4-2a88-4311-9a52-537bf09c8cc2" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy sets the maximum pending message limit value to be a multiplier of the prefetch limit of the subscription.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="proxyConnector-element"><link-body><proxyConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="db06551e-8ea8-4c19-9956-a18554e9d3c9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queryBasedSubscriptionRecoveryPolicy-element"><link-body><queryBasedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d5f67066-58d4-4d73-ae3d-7c451896a707" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user specific query mechanism to load any messages they may have missed.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6348d063-1003-4f67-90a8-23c03745e2dc" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue Destination</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="quickJournalPersistenceAdapter-element"><link-body><quickJournalPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="608221bc-aec9-430d-aece-84a6332e0616" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="rapidPersistenceAdapter-element"><link-body><rapidPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4728c44b-e072-45b0-ab29-f531a7d9cdc4" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="roundRobinDispatchPolicy-element"><link-body><roundRobinDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="767b6702-8625-41d1-948e-9d10092650c9" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that matches the message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="sharedDeadLetterStrategy-element"><link-body><sharedDeadLetterStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4b4b1cbf-9c0f-4cd9-8698-d77bca97f48a" ac:name="html" ac:schema-version="1"><plain-text-body>A default implementation of {@link DeadLetterStrategy} which uses a constant destination.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleAuthenticationPlugin-element"><link-body><simpleAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2b56caa6-0882-4008-89f5-d2e5a1237f87" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a simple authentication plugin configured with a map of user-passwords and a map of user-groups</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleAuthorizationMap-element"><link-body><simpleAuthorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bba50a6d-2840-4728-a48f-d95f71a7e1d6" ac:name="html" ac:schema-version="1"><plain-text-body>An AuthorizationMap which is configured with individual DestinationMaps for each operation.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleDispatchPolicy-element"><link-body><simpleDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ee1e0096-ba8c-45e6-8f99-8d79e9fab3c0" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that matches the message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleJmsMessageConvertor-element"><link-body><simpleJmsMessageConvertor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c92d9d2b-41ea-4b6e-b31f-42d5202ada06" ac:name="html" ac:schema-version="1"><plain-text-body>Converts Message from one JMS to another</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="statements-element"><link-body><statements></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="71686283-8049-43bf-a05e-cfade2ca5e9b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="streamJDBCAdapter-element"><link-body><streamJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b05526a2-9ca8-4c51-9dc6-c38f53c360b4" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the setBinaryStream()/getBinaryStream() operations. The databases/JDBC drivers that use this adapter are: <ul> <li>Axion</li> </ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="strictOrderDispatchPolicy-element"><link-body><strictOrderDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7d846615-7a64-42a6-badb-b75d296ea7cc" ac:name="html" ac:schema-version="1"><plain-text-body>Dispatch policy that causes every subscription to see messages in the same order.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="timedSubscriptionRecoveryPolicy-element"><link-body><timedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dd7656aa-3196-4f74-aa83-162fa4fa6b2f" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed buffer of messages around in memory and use that to recover new subscriptions.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3412aac6-b698-4498-b1d1-b6bc272514a5" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic Destination</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="transportConnector-element"><link-body><transportConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6167036e-a1b8-479e-b243-dfb15b03bcf2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="usageManager-element"><link-body><usageManager></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="682e7754-7eaa-4c98-8427-228503f1e2a9" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="virtualDestinationInterceptor-element"><link-body><virtualDestinationInterceptor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fac4ed74-08f4-478c-bf3a-13fdeed032e4" ac:name="html" ac:schema-version="1"><plain-text-body>Implements <a href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a>.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="virtualTopic-element"><link-body><virtualTopic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="138ccfd7-c73e-4f1f-9b48-1fb93f02feb5" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/virtual-destinations.html">Virtual Topics</a> using a prefix and postfix. The virtual destination creates a wildcard that is then used to look up all active queue subscriptions which match.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<h3 id="XBeanXMLReference4.1-ElementIndex">Element Index</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationEntry-element"><authorizationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning different operations (read, write, admin) of user roles to a specific destination or a hierarchical wildcard area of destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationMap-element"><authorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies. Each entry in the map represents the authorization ACLs for each operation.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-authorizationPlugin-element"><authorizationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An authorization plugin where each operation on a destination is checked against an authorizationMap</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-axionJDBCAdapter-element"><axionJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Axion specific Adapter. Axion does not seem to support ALTER statements or sub-selects. This means: - We cannot auto upgrade the schema was we roll out new versions of ActiveMQ - We cannot delete durable sub messages that have be acknowledged by all consumers.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-blobJDBCAdapter-element"><blobJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob() operations. This is a little more involved since to insert a blob you have to: 1: insert empty blob. 2: select the blob 3: finally update the blob with data value. The databases/JDBC drivers that use this adapter are: </p><ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-broker-element"><broker></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Message Broker which consists of a number of transport connectors, network connectors and a persistence adaptor</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-bytesJDBCAdapter-element"><bytesJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the setBytes()/getBytes() operations. The databases/JDBC drivers that use this adapter are:</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeDemandForwardingBridge-element"><compositeDemandForwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A demand forwarding bridge which works with multicast style transports where a single Transport could be communicating with multiple remote brokers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeQueue-element"><compositeQueue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a virtual queue which forwards to a number of other destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-compositeTopic-element"><compositeTopic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a virtual topic which forwards to a number of other destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-connectionDotFilePlugin-element"><connectionDotFilePlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current connections</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-constantPendingMessageLimitStrategy-element"><constantPendingMessageLimitStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-db2JDBCAdapter-element"><db2JDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-defaultJDBCAdapter-element"><defaultJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. </p><p></p> sub-classing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that use this adapter are: <ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-demandForwardingBridge-element"><demandForwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forwards messages from the local broker to the remote broker based on demand.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-destinationDotFilePlugin-element"><destinationDotFilePlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-destinationEntry-element"><destinationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A default entry in a DestinationMap which holds a single value.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-fixedCountSubscriptionRecoveryPolicy-element"><fixedCountSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-fixedSizedSubscriptionRecoveryPolicy-element"><fixedSizedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed amount of memory available in RAM for message history which is evicted in time order.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-forwardingBridge-element"><forwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forwards all messages from the local broker to the remote broker.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-imageBasedJDBCAdaptor-element"><imageBasedJDBCAdaptor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides JDBCAdapter since that uses IMAGE datatype to hold binary data. The databases/JDBC drivers that use this adapter are: </p><ul><li>Sybase</li><li>MS SQL</li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-inboundQueueBridge-element"><inboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Queue Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-inboundTopicBridge-element"><inboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Topic Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-individualDeadLetterStrategy-element"><individualDeadLetterStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link DeadLetterStrategy} where each destination has its own individual DLQ using the subject naming hierarchy.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-informixJDBCAdapter-element"><informixJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>JDBC Adapter for Informix database. Because Informix database restricts length of composite primary keys, length of <i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters. Therefore be sure not to use longer names for container name and subscription id than 150 characters.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jaasAuthenticationPlugin-element"><jaasAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a JAAS based authentication plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jdbcPersistenceAdapter-element"><jdbcPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link PersistenceAdapter} implementation using JDBC for persistence storage. This persistence adapter will correctly remember prepared XA transactions, but it will not keep track of local transaction commits so that operations performed against the Message store are done as a single uow.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jmsQueueConnector-element"><jmsQueueConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Queue providers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-jmsTopicConnector-element"><jmsTopicConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Topic providers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-journalPersistenceAdapter-element"><journalPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-journaledJDBC-element"><journaledJDBC></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates a default persistence model using the Journal and JDBC</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-kahaPersistenceAdapter-element"><kahaPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-lastImageSubscriptionRecoveryPolicy-element"><lastImageSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the last message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-loggingBrokerPlugin-element"><loggingBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A simple Broker interceptor which allows you to enable/disable logging.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-managementContext-element"><managementContext></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Flow provides different dispatch policies within the NMR</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-memoryPersistenceAdapter-element"><memoryPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-multicastNetworkConnector-element"><multicastNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses some kind of multicast-like transport that communicates with potentially many remote brokers over a single logical {@link Transport} instance such as when using multicast. This implementation does not depend on multicast at all; any other group based transport could be used.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-networkConnector-element"><networkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses a discovery agent to detect the remote brokers available and setup a connection to each available remote broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-noSubscriptionRecoveryPolicy-element"><noSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This is the default Topic recovery policy which does not recover any messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-oldestMessageEvictionStrategy-element"><oldestMessageEvictionStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An eviction strategy which evicts the oldest message first (which is the default).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-oldestMessageWithLowestPriorityEvictionStrategy-element"><oldestMessageWithLowestPriorityEvictionStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An eviction strategy which evicts the oldest message with the lowest priority first.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-oracleJDBCAdapter-element"><oracleJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements all the default JDBC operations that are used by the JDBCPersistenceAdapter. </p><p></p> Subclassing is encouraged to override the default implementation of methods to account for differences in JDBC Driver implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that use this adapter are: <ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-outboundQueueBridge-element"><outboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Queue Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-outboundTopicBridge-element"><outboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Topic Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-policyEntry-element"><policyEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link PolicyMap} for assigning policies to a specific destination or a hierarchical wildcard area of destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-policyMap-element"><policyMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual destinations or wildcard hierarchies of destinations can be configured using different policies.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-prefetchRatePendingMessageLimitStrategy-element"><prefetchRatePendingMessageLimitStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This PendingMessageLimitStrategy sets the maximum pending message limit value to be a multiplier of the prefetch limit of the subscription.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-proxyConnector-element"><proxyConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-queryBasedSubscriptionRecoveryPolicy-element"><queryBasedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user specific query mechanism to load any messages they may have missed.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-queue-element"><queue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Queue Destination</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-quickJournalPersistenceAdapter-element"><quickJournalPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-rapidPersistenceAdapter-element"><rapidPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a {@link Journal} and then check pointing asynchronously on a timeout with some other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-roundRobinDispatchPolicy-element"><roundRobinDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Simple dispatch policy that sends a message to every subscription that matches the message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-sharedDeadLetterStrategy-element"><sharedDeadLetterStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A default implementation of {@link DeadLetterStrategy} which uses a constant destination.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleAuthenticationPlugin-element"><simpleAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a simple authentication plugin configured with a map of user-passwords and a map of user-groups</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleAuthorizationMap-element"><simpleAuthorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An AuthorizationMap which is configured with individual DestinationMaps for each operation.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleDispatchPolicy-element"><simpleDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Simple dispatch policy that sends a message to every subscription that matches the message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-simpleJmsMessageConvertor-element"><simpleJmsMessageConvertor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Converts Message from one JMS to another</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-statements-element"><statements></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-streamJDBCAdapter-element"><streamJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the setBinaryStream()/getBinaryStream() operations. The databases/JDBC drivers that use this adapter are: </p><ul><li>Axion</li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-strictOrderDispatchPolicy-element"><strictOrderDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Dispatch policy that causes every subscription to see messages in the same order.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-timedSubscriptionRecoveryPolicy-element"><timedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed buffer of messages around in memory and use that to recover new subscriptions.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-topic-element"><topic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Topic Destination</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-transportConnector-element"><transportConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-usageManager-element"><usageManager></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a productive working set usage can be controlled. Main use case is manage memory usage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-virtualDestinationInterceptor-element"><virtualDestinationInterceptor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements <a shape="rect" href="http://incubator.apache.org/activemq/virtual-destinations.html">Virtual Topics</a>.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference4.1-virtualTopic-element"><virtualTopic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/virtual-destinations.html">Virtual Topics</a> using a prefix and postfix. The virtual destination creates a wildcard that is then used to look up all active queue subscriptions which match.</p> <p></p></td></tr></tbody></table></div>
</div>
diff --git a/xbean-xml-reference-50.xml b/xbean-xml-reference-50.xml
index 4dc81fe..85ac4cd 100644
--- a/xbean-xml-reference-50.xml
+++ b/xbean-xml-reference-50.xml
@@ -1,78 +1,78 @@
-<div class="wiki-content maincontent"><h3 id="XBeanXMLReference5.0-ElementsByType">Elements By Type</h3>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.TransportConnector-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.TransportConnectorTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.TransportConnector-types">org.apache.activemq.broker.TransportConnector</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-transportConnector-element"><transportConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<div class="wiki-content maincontent"><h3>Elements By Type</h3>
+<p><structured-macro ac:macro-id="1af36601-ac43-48cd-8a7e-f31228ad2064" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.TransportConnector-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.TransportConnector-types"><link-body>org.apache.activemq.broker.TransportConnector</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="transportConnector-element"><link-body><transportConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f6560e94-3a02-4857-8311-01befc0b5322" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.jms.InboundQueueBridge-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.jms.InboundQueueBridgeTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.InboundQueueBridge-types">org.apache.activemq.network.jms.InboundQueueBridge</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-inboundQueueBridge-element"><inboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Queue Bridge</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a3ed5b2f-50d6-420d-bb72-0582f25c3b8c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.InboundQueueBridge-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.InboundQueueBridge-types"><link-body>org.apache.activemq.network.jms.InboundQueueBridge</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundQueueBridge-element"><link-body><inboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="274cba60-1d84-4f55-9f21-9334ed9726f5" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.NetworkConnector-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.NetworkConnectorTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.NetworkConnector-types">org.apache.activemq.network.NetworkConnector</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-ldapNetworkConnector-element"><ldapNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>class to create dynamic network connectors listed in an directory
+<p><structured-macro ac:macro-id="c3e8f2c5-0b32-4942-bab1-e23bc082769d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.NetworkConnector-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.NetworkConnector-types"><link-body>org.apache.activemq.network.NetworkConnector</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="ldapNetworkConnector-element"><link-body><ldapNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7d8d49bf-64c2-443e-82b7-41655b6641c1" ac:name="html" ac:schema-version="1"><plain-text-body>class to create dynamic network connectors listed in an directory
server using the LDAP v3 protocol as defined in RFC 2251, the
entries listed in the directory server must implement the ipHost
-and ipService objectClasses as defined in RFC 2307.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-multicastNetworkConnector-element"><multicastNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses some kind of multicast-like transport that
+and ipService objectClasses as defined in RFC 2307.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="multicastNetworkConnector-element"><link-body><multicastNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c26ad5c3-d197-419f-b866-44727ec9835e" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses some kind of multicast-like transport that
communicates with potentially many remote brokers over a single logical
{@link Transport} instance such as when using multicast.
This implementation does not depend on multicast at all; any other group
-based transport could be used.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-networkConnector-element"><networkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses a discovery agent to detect the remote brokers
-available and setup a connection to each available remote broker</p> <p></p></td></tr></tbody></table></div>
+based transport could be used.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="networkConnector-element"><link-body><networkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2c338979-05e7-4caf-ad1b-32f3710cfafd" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses a discovery agent to detect the remote brokers
+available and setup a connection to each available remote broker</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.BrokerServiceTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-broker-element"><broker></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Message Broker. It consists of a number of transport
+<p><structured-macro ac:macro-id="e4f2caa9-2daf-4e51-8985-d68c88d62cdc" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.BrokerService-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="broker-element"><link-body><broker></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dd719487-4fce-42cb-9fbf-fff47e08ced8" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Message Broker. It consists of a number of transport
connectors, network connectors and a bunch of properties which can be used to
-configure the broker as its lazily created.</p> <p></p></td></tr></tbody></table></div>
+configure the broker as its lazily created.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.usage.TempUsage-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.usage.TempUsageTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.TempUsage-types">org.apache.activemq.usage.TempUsage</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-tempUsage-element"><tempUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+<p><structured-macro ac:macro-id="bbfe8479-a6e7-4db8-b47f-2251459cf92b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.usage.TempUsage-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.usage.TempUsage-types"><link-body>org.apache.activemq.usage.TempUsage</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="tempUsage-element"><link-body><tempUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7ed69e76-3340-4e7a-b184-55d695dab22e" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr></tbody></table></div>
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy-types">org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fileCursor-element"><fileCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-vmCursor-element"><vmCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages held</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="49e0b3ce-e829-4cc4-ba94-16a78ecc4083" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy-types"><link-body>org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fileCursor-element"><link-body><fileCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0f500262-6f6f-4b3d-ae33-2dbb4394f760" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="vmCursor-element"><link-body><vmCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a4f9cbed-6c50-4c68-8b11-f44089a15ae8" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages held</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.usage.MemoryUsage-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.usage.MemoryUsageTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.MemoryUsage-types">org.apache.activemq.usage.MemoryUsage</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-memoryUsage-element"><memoryUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+<p><structured-macro ac:macro-id="5372a776-8db8-433a-a4ca-808e85070f6d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.usage.MemoryUsage-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.usage.MemoryUsage-types"><link-body>org.apache.activemq.usage.MemoryUsage</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="memoryUsage-element"><link-body><memoryUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bc8b66d5-41bc-4913-813f-f55fc58df853" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr></tbody></table></div>
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.BrokerPlugin-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.BrokerPluginTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerPlugin-types">org.apache.activemq.broker.BrokerPlugin</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationPlugin-element"><authorizationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An authorization plugin where each operation on a destination is checked
-against an authorizationMap</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-connectionDotFilePlugin-element"><connectionDotFilePlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which
-creates a DOT file showing the current connections</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-destinationDotFilePlugin-element"><destinationDotFilePlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a>
-file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jaasAuthenticationPlugin-element"><jaasAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a JAAS based authentication plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jaasCertificateAuthenticationPlugin-element"><jaasCertificateAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a JAAS based SSL certificate authentication plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-loggingBrokerPlugin-element"><loggingBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A simple Broker interceptor which allows you to enable/disable logging.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-multicastTraceBrokerPlugin-element"><multicastTraceBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which allows you to trace all operations to a Multicast
-socket.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleAuthenticationPlugin-element"><simpleAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a simple authentication plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-timeStampingBrokerPlugin-element"><timeStampingBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which updates a JMS Client's timestamp on the message
+<p><structured-macro ac:macro-id="3d4213dc-61d5-469f-b540-a4c0fbf80ea0" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.BrokerPlugin-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.BrokerPlugin-types"><link-body>org.apache.activemq.broker.BrokerPlugin</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationPlugin-element"><link-body><authorizationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3b59f171-d771-4e3b-b492-5426cb6e88bd" ac:name="html" ac:schema-version="1"><plain-text-body>An authorization plugin where each operation on a destination is checked
+against an authorizationMap</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="connectionDotFilePlugin-element"><link-body><connectionDotFilePlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="205531a5-6d78-40c3-9b4e-da4ec91b33de" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which
+creates a DOT file showing the current connections</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="destinationDotFilePlugin-element"><link-body><destinationDotFilePlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1e694faf-78a3-4369-8331-fecba0ef31c8" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a>
+file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jaasAuthenticationPlugin-element"><link-body><jaasAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="abf506c2-c7b6-4a33-a5a8-1b3b21fad54f" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based authentication plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jaasCertificateAuthenticationPlugin-element"><link-body><jaasCertificateAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2b83ca88-5435-42de-b94a-a29c7051214a" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based SSL certificate authentication plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="loggingBrokerPlugin-element"><link-body><loggingBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="67fd155a-b71b-4c77-a568-7bfe653ca63e" ac:name="html" ac:schema-version="1"><plain-text-body>A simple Broker interceptor which allows you to enable/disable logging.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="multicastTraceBrokerPlugin-element"><link-body><multicastTraceBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="79f84bde-9a20-43d1-8421-57f70ec90d92" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which allows you to trace all operations to a Multicast
+socket.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleAuthenticationPlugin-element"><link-body><simpleAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bd831e17-38a3-49ea-88f5-53af63ae5d87" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a simple authentication plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="timeStampingBrokerPlugin-element"><link-body><timeStampingBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6abf4925-3686-4002-9f51-8548d61b4f68" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which updates a JMS Client's timestamp on the message
with a broker timestamp. Useful when the clocks on client machines are known
to not be correct and you can only trust the time set on the broker machines.
Enabling this plugin will break JMS compliance since the timestamp that the
producer sees on the messages after as send() will be different from the
timestamp the consumer will observe when he receives the message. This plugin
-is not enabled in the default ActiveMQ configuration.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-udpTraceBrokerPlugin-element"><udpTraceBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which allows you to trace all operations to a UDP
-socket.</p> <p></p></td></tr></tbody></table></div>
+is not enabled in the default ActiveMQ configuration.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="udpTraceBrokerPlugin-element"><link-body><udpTraceBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7cad0fd9-5ca6-404c-a94f-ef564ffe57d3" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which allows you to trace all operations to a UDP
+socket.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.store.jdbc.JDBCAdapter-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.store.jdbc.JDBCAdapterTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.JDBCAdapter-types">org.apache.activemq.store.jdbc.JDBCAdapter</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-axionJDBCAdapter-element"><axionJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Axion specific Adapter.
+<p><structured-macro ac:macro-id="657bb509-3117-4977-ab98-62adc5d05592" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.jdbc.JDBCAdapter-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCAdapter</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="axionJDBCAdapter-element"><link-body><axionJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="08098fb5-7940-4c5b-92cd-711e97c814e7" ac:name="html" ac:schema-version="1"><plain-text-body>Axion specific Adapter.
Axion does not seem to support ALTER statements or sub-selects. This means:
- We cannot auto upgrade the schema was we roll out new versions of ActiveMQ
-- We cannot delete durable sub messages that have be acknowledged by all consumers.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-blobJDBCAdapter-element"><blobJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob()
+- We cannot delete durable sub messages that have be acknowledged by all consumers.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="blobJDBCAdapter-element"><link-body><blobJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1bdd2b0c-56b9-4c26-9c1a-eda46566a98a" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob()
operations. This is a little more involved since to insert a blob you have
to:
@@ -80,431 +80,445 @@
value.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-bytesJDBCAdapter-element"><bytesJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="bytesJDBCAdapter-element"><link-body><bytesJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="52fb1b0e-c26a-4181-a90c-c5ae6f176c8a" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the
setBytes()/getBytes() operations. The databases/JDBC drivers that use this
-adapter are:</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-db2JDBCAdapter-element"><db2JDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-defaultJDBCAdapter-element"><defaultJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements all the default JDBC operations that are used by the
-JDBCPersistenceAdapter. </p><p></p> sub-classing is encouraged to override the
+adapter are:</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="db2JDBCAdapter-element"><link-body><db2JDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="22bf9333-ad4f-4ce6-95fb-d8128626cfc0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="defaultJDBCAdapter-element"><link-body><defaultJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b52d3bbb-0e44-4c20-97bd-0dff157abf19" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the
+JDBCPersistenceAdapter. <p/> sub-classing is encouraged to override the
default implementation of methods to account for differences in JDBC Driver
-implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using
-the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that
+implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using
+the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that
use this adapter are:
-<ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-imageBasedJDBCAdaptor-element"><imageBasedJDBCAdaptor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides JDBCAdapter since that uses
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="imageBasedJDBCAdaptor-element"><link-body><imageBasedJDBCAdaptor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="86d1c092-5ba2-43cb-a818-f17771828584" ac:name="html" ac:schema-version="1"><plain-text-body>Provides JDBCAdapter since that uses
IMAGE datatype to hold binary data.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li>Sybase</li><li>MS SQL</li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-informixJDBCAdapter-element"><informixJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>JDBC Adapter for Informix database.
+<ul>
+<li>Sybase</li>
+<li>MS SQL</li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="informixJDBCAdapter-element"><link-body><informixJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b82b93e5-1cae-44ad-a558-e708ac9de03d" ac:name="html" ac:schema-version="1"><plain-text-body>JDBC Adapter for Informix database.
Because Informix database restricts length of composite primary keys, length of
-<i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters.
-Therefore be sure not to use longer names for container name and subscription id than 150 characters.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-oracleJDBCAdapter-element"><oracleJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements all the default JDBC operations that are used
+<i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters.
+Therefore be sure not to use longer names for container name and subscription id than 150 characters.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oracleJDBCAdapter-element"><link-body><oracleJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fab27ad6-5f41-4789-bd5c-4c16e65eaefb" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used
by the JDBCPersistenceAdapter.
-</p><p></p>
+<p/>
Subclassing is encouraged to override the default
implementation of methods to account for differences
in JDBC Driver implementations.
-<p></p>
+<p/>
The JDBCAdapter inserts and extracts BLOB data using the
getBytes()/setBytes() operations.
-<p></p>
+<p/>
The databases/JDBC drivers that use this adapter are:
-<ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-streamJDBCAdapter-element"><streamJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="streamJDBCAdapter-element"><link-body><streamJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2f8bcb9f-08c7-4bbc-b88a-d1c987e953db" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the
setBinaryStream()/getBinaryStream() operations.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li>Axion</li></ul> <p></p></td></tr></tbody></table></div>
+<ul>
+<li>Axion</li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy-types">org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fileQueueCursor-element"><fileQueueCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-storeCursor-element"><storeCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-vmQueueCursor-element"><vmQueueCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a2887197-8746-48af-902c-064910ac0a81" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy-types"><link-body>org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fileQueueCursor-element"><link-body><fileQueueCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="370416bd-72a4-46b3-a24f-4a5832592e43" ac:name="html" ac:schema-version="1"><plain-text-body>Pending</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="storeCursor-element"><link-body><storeCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="067d6849-cee8-46cc-9554-cc1169eca96e" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="vmQueueCursor-element"><link-body><vmQueueCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="14ba1ec1-8911-4c3e-bdb9-8afeb20965fc" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-javax.jms.TopicConnectionFactory-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Thejavax.jms.TopicConnectionFactoryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.TopicConnectionFactory-types">javax.jms.TopicConnectionFactory</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-connectionFactory-element"><connectionFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced connection
+<p><structured-macro ac:macro-id="21f07fb9-2f19-4783-bfbe-5776382413a2" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">javax.jms.TopicConnectionFactory-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="javax.jms.TopicConnectionFactory-types"><link-body>javax.jms.TopicConnectionFactory</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="connectionFactory-element"><link-body><connectionFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="962ede2d-aaf1-4b13-a332-420d10b9ab73" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-xaConnectionFactory-element"><xaConnectionFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced XA connection
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="xaConnectionFactory-element"><link-body><xaConnectionFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c00bb503-17f5-403a-b2eb-eae683734e38" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p> <p></p></td></tr></tbody></table></div>
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.virtual.VirtualDestination-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.virtual.VirtualDestinationTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.virtual.VirtualDestination-types">org.apache.activemq.broker.region.virtual.VirtualDestination</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-compositeQueue-element"><compositeQueue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a virtual queue which forwards to a number of other destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-compositeTopic-element"><compositeTopic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a virtual topic which forwards to a number of other destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-virtualTopic-element"><virtualTopic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/virtual-destinations.html">Virtual
-Topics</a> using a prefix and postfix. The virtual destination creates a
+<p><structured-macro ac:macro-id="72544763-cc54-4e58-8f1f-df53e7e512fb" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.virtual.VirtualDestination-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.virtual.VirtualDestination-types"><link-body>org.apache.activemq.broker.region.virtual.VirtualDestination</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeQueue-element"><link-body><compositeQueue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d0c162a2-c72e-418c-87d4-d309485a9556" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual queue which forwards to a number of other destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeTopic-element"><link-body><compositeTopic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ed4fc5c2-3c71-438c-89c0-dade3582e778" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual topic which forwards to a number of other destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="virtualTopic-element"><link-body><virtualTopic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7620e04a-64d4-4277-8ddb-431381a87867" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/virtual-destinations.html">Virtual
+Topics</a> using a prefix and postfix. The virtual destination creates a
wildcard that is then used to look up all active queue subscriptions which
-match.</p> <p></p></td></tr></tbody></table></div>
+match.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PolicyMap-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.PolicyMapTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PolicyMap-types">org.apache.activemq.broker.region.policy.PolicyMap</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-policyMap-element"><policyMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual
+<p><structured-macro ac:macro-id="97e92eb6-511a-427f-b7ca-9f2457c58411" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PolicyMap-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PolicyMap-types"><link-body>org.apache.activemq.broker.region.policy.PolicyMap</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyMap-element"><link-body><policyMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d665591f-bf32-42ef-9f0e-9908a0ea3536" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
-different policies.</p> <p></p></td></tr></tbody></table></div>
+different policies.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.usage.UsageCapacity-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.usage.UsageCapacityTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.UsageCapacity-types">org.apache.activemq.usage.UsageCapacity</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-defaultUsageCapacity-element"><defaultUsageCapacity></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Identify if a limit has been reached</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-usageCapacity-element"><usageCapacity></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Identify if a limit has been reached</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="96a35db6-b5b3-4990-98cf-e6f8685b2cb8" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.usage.UsageCapacity-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.usage.UsageCapacity-types"><link-body>org.apache.activemq.usage.UsageCapacity</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="defaultUsageCapacity-element"><link-body><defaultUsageCapacity></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b458776a-4c3f-4776-8133-1eeacfb60f02" ac:name="html" ac:schema-version="1"><plain-text-body>Identify if a limit has been reached</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="usageCapacity-element"><link-body><usageCapacity></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="03700bfe-49fd-4f6f-8719-80bf48556a70" ac:name="html" ac:schema-version="1"><plain-text-body>Identify if a limit has been reached</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.PendingMessageLimitStrategyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types">org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-constantPendingMessageLimitStrategy-element"><constantPendingMessageLimitStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-prefetchRatePendingMessageLimitStrategy-element"><prefetchRatePendingMessageLimitStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This PendingMessageLimitStrategy sets the maximum pending message limit value to be
-a multiplier of the prefetch limit of the subscription.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a9fa4fdd-e14c-40a0-aed2-3aff0bb959bd" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types"><link-body>org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="constantPendingMessageLimitStrategy-element"><link-body><constantPendingMessageLimitStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d611c0ce-de6d-4a34-b592-08c09d68ae73" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="prefetchRatePendingMessageLimitStrategy-element"><link-body><prefetchRatePendingMessageLimitStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cbf3b55f-2274-4a82-9098-75d03b3baa3d" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy sets the maximum pending message limit value to be
+a multiplier of the prefetch limit of the subscription.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.usage.SystemUsageTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-systemUsage-element"><systemUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Holder for Usage instances for memory, store and temp files Main use case is
-manage memory usage.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="07a73475-f0d8-4635-b639-a2cc99b625e9" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.usage.SystemUsage-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="systemUsage-element"><link-body><systemUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="467bfe5e-dbcc-4c6f-ad4b-8b4f50b9b29d" ac:name="html" ac:schema-version="1"><plain-text-body>Holder for Usage instances for memory, store and temp files Main use case is
+manage memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-javax.jms.Destination-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Thejavax.jms.DestinationTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Destination-types">javax.jms.Destination</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-queue-element"><queue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Queue</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-topic-element"><topic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Topic</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="579f60c6-372c-4c93-9267-72214ccd61b6" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">javax.jms.Destination-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="javax.jms.Destination-types"><link-body>javax.jms.Destination</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f7c734b1-e44e-40b0-bdd9-011e2ab2eda3" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="191e90de-86da-4d35-8693-852cf51c3bd4" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types">org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fixedCountSubscriptionRecoveryPolicy-element"><fixedCountSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
-count of last messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fixedSizedSubscriptionRecoveryPolicy-element"><fixedSizedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
+<p><structured-macro ac:macro-id="768b1c9c-adaa-4fa9-8824-4607344023c5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types"><link-body>org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fixedCountSubscriptionRecoveryPolicy-element"><link-body><fixedCountSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f484c701-dbdd-4ff4-b7d1-c778ac3bb198" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
+count of last messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fixedSizedSubscriptionRecoveryPolicy-element"><link-body><fixedSizedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3a23fc37-4dfd-4c66-bfba-5b0be317f72c" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
amount of memory available in RAM for message history which is evicted in
-time order.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-lastImageSubscriptionRecoveryPolicy-element"><lastImageSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the
-last message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-noSubscriptionRecoveryPolicy-element"><noSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This SubscriptionRecoveryPolicy disable recovery of messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-queryBasedSubscriptionRecoveryPolicy-element"><queryBasedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user
-specific query mechanism to load any messages they may have missed.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-timedSubscriptionRecoveryPolicy-element"><timedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed
+time order.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="lastImageSubscriptionRecoveryPolicy-element"><link-body><lastImageSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3b6487a6-17da-4f79-b12b-07e2bf9b335d" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the
+last message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="noSubscriptionRecoveryPolicy-element"><link-body><noSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e535a151-a833-494c-97ba-ad0b421e5c17" ac:name="html" ac:schema-version="1"><plain-text-body>This SubscriptionRecoveryPolicy disable recovery of messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queryBasedSubscriptionRecoveryPolicy-element"><link-body><queryBasedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6cc55122-d051-479b-9181-2142ca9d7c4e" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user
+specific query mechanism to load any messages they may have missed.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="timedSubscriptionRecoveryPolicy-element"><link-body><timedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="563e1f52-f4bc-42b2-81b4-89143e78ae55" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed
buffer of messages around in memory and use that to recover new
-subscriptions.</p> <p></p></td></tr></tbody></table></div>
+subscriptions.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-javax.jms.QueueConnectionFactory-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Thejavax.jms.QueueConnectionFactoryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.QueueConnectionFactory-types">javax.jms.QueueConnectionFactory</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-connectionFactory-element"><connectionFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced connection
+<p><structured-macro ac:macro-id="1a9faf48-9c17-43c8-808b-48015be2f571" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">javax.jms.QueueConnectionFactory-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="javax.jms.QueueConnectionFactory-types"><link-body>javax.jms.QueueConnectionFactory</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="connectionFactory-element"><link-body><connectionFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b22185ee-9c1f-4eed-93ff-aed4585757f0" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-xaConnectionFactory-element"><xaConnectionFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced XA connection
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="xaConnectionFactory-element"><link-body><xaConnectionFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6985c43a-8e6a-4e95-b8f6-f8b6523781fb" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p> <p></p></td></tr></tbody></table></div>
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.jmx.ManagementContext-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.jmx.ManagementContextTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.jmx.ManagementContext-types">org.apache.activemq.broker.jmx.ManagementContext</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-managementContext-element"><managementContext></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Flow provides different dispatch policies within the NMR</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="dc74eddf-0e57-410d-8e3e-ba54db4fa497" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.jmx.ManagementContext-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.jmx.ManagementContext-types"><link-body>org.apache.activemq.broker.jmx.ManagementContext</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="managementContext-element"><link-body><managementContext></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="33b323d5-0e54-45a1-b35e-d242085582c1" ac:name="html" ac:schema-version="1"><plain-text-body>A Flow provides different dispatch policies within the NMR</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.store.jdbc.StatementsTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-statements-element"><statements></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="268771ed-6cc2-4642-b1a3-585b29f6b828" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.jdbc.Statements-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="statements-element"><link-body><statements></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="504603f3-f81a-48ce-a9ec-0d03c615a620" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapterFactory-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.store.PersistenceAdapterFactoryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapterFactory-types">org.apache.activemq.store.PersistenceAdapterFactory</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-amqPersistenceAdapterFactory-element"><amqPersistenceAdapterFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapterFactory}</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-journaledJDBC-element"><journaledJDBC></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates a default persistence model using the Journal and JDBC</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="6eed23a4-04bf-4f54-9de7-2ddae3cd5cda" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.PersistenceAdapterFactory-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapterFactory-types"><link-body>org.apache.activemq.store.PersistenceAdapterFactory</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="amqPersistenceAdapterFactory-element"><link-body><amqPersistenceAdapterFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ea628f4d-e04d-44b7-9baf-601b9b706c06" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapterFactory}</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="journaledJDBC-element"><link-body><journaledJDBC></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c50916d3-6c65-4c68-8a4d-949a0ad15e34" ac:name="html" ac:schema-version="1"><plain-text-body>Creates a default persistence model using the Journal and JDBC</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.security.AuthorizationEntry-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.security.AuthorizationEntryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.security.AuthorizationEntry-types">org.apache.activemq.security.AuthorizationEntry</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationEntry-element"><authorizationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
+<p><structured-macro ac:macro-id="62aba4dd-0410-4747-bf22-fe6339943050" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.security.AuthorizationEntry-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.security.AuthorizationEntry-types"><link-body>org.apache.activemq.security.AuthorizationEntry</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationEntry-element"><link-body><authorizationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f7a9d678-64e0-47bf-9527-87634e24bad0" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
different operations (read, write, admin) of user roles to a specific
-destination or a hierarchical wildcard area of destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-tempDestinationAuthorizationEntry-element"><tempDestinationAuthorizationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
+destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="tempDestinationAuthorizationEntry-element"><link-body><tempDestinationAuthorizationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6365c935-456c-4606-888a-01edb83fb947" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
different operations (read, write, admin) of user roles to a temporary
-destination</p> <p></p></td></tr></tbody></table></div>
+destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy-types">org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fileDurableSubscriberCursor-element"><fileDurableSubscriberCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages for durable subscribers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-storeDurableSubscriberCursor-element"><storeDurableSubscriberCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages for a durable</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-vmDurableCursor-element"><vmDurableCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="8baf9c04-aeb3-4149-a0c7-dfe89b6949e1" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy-types"><link-body>org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fileDurableSubscriberCursor-element"><link-body><fileDurableSubscriberCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="36c32866-b3aa-49da-b370-d84356c2b6db" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages for durable subscribers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="storeDurableSubscriberCursor-element"><link-body><storeDurableSubscriberCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="86ea96a2-0806-411e-ace0-74528fd1b577" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages for a durable</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="vmDurableCursor-element"><link-body><vmDurableCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9efe5bf8-a967-4afe-b2a5-bc534af04a3f" ac:name="html" ac:schema-version="1"><plain-text-body>Pending</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.group.MessageGroupMapFactory-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.group.MessageGroupMapFactoryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.group.MessageGroupMapFactory-types">org.apache.activemq.broker.region.group.MessageGroupMapFactory</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-messageGroupHashBucketFactory-element"><messageGroupHashBucketFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A factory to create instances of {@link SimpleMessageGroupMap} when
-implementing the <a shape="rect" href="http://activemq.apache.org/message-groups.html">Message
-Groups</a> functionality.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleMessageGroupMapFactory-element"><simpleMessageGroupMapFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A factory to create instances of {@link SimpleMessageGroupMap} when implementing the
-<a shape="rect" href="http://activemq.apache.org/message-groups.html">Message Groups</a> functionality.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="b484ceee-9e0d-40ec-8da6-2c1d22af2913" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.group.MessageGroupMapFactory-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.group.MessageGroupMapFactory-types"><link-body>org.apache.activemq.broker.region.group.MessageGroupMapFactory</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="messageGroupHashBucketFactory-element"><link-body><messageGroupHashBucketFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2adc8091-ecd5-4eae-a2da-d2548149e50c" ac:name="html" ac:schema-version="1"><plain-text-body>A factory to create instances of {@link SimpleMessageGroupMap} when
+implementing the <a
+href="http://activemq.apache.org/message-groups.html">Message
+Groups</a> functionality.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleMessageGroupMapFactory-element"><link-body><simpleMessageGroupMapFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="670aa7b2-aafb-4f4b-a757-0f4cff2a30fa" ac:name="html" ac:schema-version="1"><plain-text-body>A factory to create instances of {@link SimpleMessageGroupMap} when implementing the
+<a href="http://activemq.apache.org/message-groups.html">Message Groups</a> functionality.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.usage.StoreUsage-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.usage.StoreUsageTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.StoreUsage-types">org.apache.activemq.usage.StoreUsage</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-storeUsage-element"><storeUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+<p><structured-macro ac:macro-id="f6e72670-7bb0-459c-a76a-d3e303719d7d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.usage.StoreUsage-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.usage.StoreUsage-types"><link-body>org.apache.activemq.usage.StoreUsage</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="storeUsage-element"><link-body><storeUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="92e2d642-dad0-44c2-80f1-a7870a2e48a9" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr></tbody></table></div>
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.DeadLetterStrategy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.DeadLetterStrategyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.DeadLetterStrategy-types">org.apache.activemq.broker.region.policy.DeadLetterStrategy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-individualDeadLetterStrategy-element"><individualDeadLetterStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link DeadLetterStrategy} where each destination has its own individual
-DLQ using the subject naming hierarchy.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-sharedDeadLetterStrategy-element"><sharedDeadLetterStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A default implementation of {@link DeadLetterStrategy} which uses
-a constant destination.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="2ce3df80-e7ad-43af-a848-35308c67197f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.DeadLetterStrategy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.DeadLetterStrategy-types"><link-body>org.apache.activemq.broker.region.policy.DeadLetterStrategy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="individualDeadLetterStrategy-element"><link-body><individualDeadLetterStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bb10fccf-a847-4160-b273-bd1ed5c900be" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link DeadLetterStrategy} where each destination has its own individual
+DLQ using the subject naming hierarchy.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="sharedDeadLetterStrategy-element"><link-body><sharedDeadLetterStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a7ede358-057d-49d2-90bc-a97397aeb1aa" ac:name="html" ac:schema-version="1"><plain-text-body>A default implementation of {@link DeadLetterStrategy} which uses
+a constant destination.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-javax.jms.Topic-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Thejavax.jms.TopicTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Topic-types">javax.jms.Topic</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-topic-element"><topic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Topic</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="3475fbd7-f5cd-4f2e-ad34-397b34ab9c71" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">javax.jms.Topic-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ca0591bd-e41f-4ea3-8f89-300e1e5df6b0" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.ActiveMQPrefetchPolicy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.ActiveMQPrefetchPolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.ActiveMQPrefetchPolicy-types">org.apache.activemq.ActiveMQPrefetchPolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-prefetchPolicy-element"><prefetchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Defines the prefetch message policies for different types of consumers</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="4d9b23e0-3414-4778-8637-51341cdf0f90" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.ActiveMQPrefetchPolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.ActiveMQPrefetchPolicy-types"><link-body>org.apache.activemq.ActiveMQPrefetchPolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="prefetchPolicy-element"><link-body><prefetchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6998b4b3-9a3b-415c-b783-4600d04c442d" ac:name="html" ac:schema-version="1"><plain-text-body>Defines the prefetch message policies for different types of consumers</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.Broker-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.BrokerTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.Broker-types">org.apache.activemq.broker.Broker</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-loggingBrokerPlugin-element"><loggingBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A simple Broker interceptor which allows you to enable/disable logging.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-multicastTraceBrokerPlugin-element"><multicastTraceBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which allows you to trace all operations to a Multicast
-socket.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-timeStampingBrokerPlugin-element"><timeStampingBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which updates a JMS Client's timestamp on the message
+<p><structured-macro ac:macro-id="51b78cbc-e2d0-417f-944c-5028d80ea468" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.Broker-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.Broker-types"><link-body>org.apache.activemq.broker.Broker</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="loggingBrokerPlugin-element"><link-body><loggingBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="09483de1-c05d-4f48-995b-e660803bd80d" ac:name="html" ac:schema-version="1"><plain-text-body>A simple Broker interceptor which allows you to enable/disable logging.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="multicastTraceBrokerPlugin-element"><link-body><multicastTraceBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="06daafc6-52a2-4d74-9f99-06bb19ac3b7c" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which allows you to trace all operations to a Multicast
+socket.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="timeStampingBrokerPlugin-element"><link-body><timeStampingBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8ad35cc4-f9b3-4bd2-a39d-7ba04f42ff64" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which updates a JMS Client's timestamp on the message
with a broker timestamp. Useful when the clocks on client machines are known
to not be correct and you can only trust the time set on the broker machines.
Enabling this plugin will break JMS compliance since the timestamp that the
producer sees on the messages after as send() will be different from the
timestamp the consumer will observe when he receives the message. This plugin
-is not enabled in the default ActiveMQ configuration.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-udpTraceBrokerPlugin-element"><udpTraceBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which allows you to trace all operations to a UDP
-socket.</p> <p></p></td></tr></tbody></table></div>
+is not enabled in the default ActiveMQ configuration.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="udpTraceBrokerPlugin-element"><link-body><udpTraceBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8533d35a-a6f8-4c84-9735-a411b580e58f" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which allows you to trace all operations to a UDP
+socket.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapter-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.store.PersistenceAdapterTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-amqPersistenceAdapter-element"><amqPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a
+<p><structured-macro ac:macro-id="cfdc0625-09c2-4a37-994f-4f7b64614507" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.PersistenceAdapter-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="amqPersistenceAdapter-element"><link-body><amqPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="596a1597-b8f0-4513-9686-ae32ad02c8f3" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a
{@link Journal} and then check pointing asynchronously on a timeout with some
-other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jdbcPersistenceAdapter-element"><jdbcPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link PersistenceAdapter} implementation using JDBC for persistence
+other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jdbcPersistenceAdapter-element"><link-body><jdbcPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="57a2584e-2559-4086-a1ff-90faf201afda" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link PersistenceAdapter} implementation using JDBC for persistence
storage.
This persistence adapter will correctly remember prepared XA transactions,
but it will not keep track of local transaction commits so that operations
-performed against the Message store are done as a single uow.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-journalPersistenceAdapter-element"><journalPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a
+performed against the Message store are done as a single uow.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="journalPersistenceAdapter-element"><link-body><journalPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c225236d-222b-45dd-b98a-ad10cc30eed4" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a
{@link Journal} and then check pointing asynchronously on a timeout with some
-other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-kahaPersistenceAdapter-element"><kahaPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-memoryPersistenceAdapter-element"><memoryPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="kahaPersistenceAdapter-element"><link-body><kahaPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b0d59ae7-9670-4d2e-b131-c62d3acb8081" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="memoryPersistenceAdapter-element"><link-body><memoryPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6d9d305f-42bd-4ebe-9fa2-85de255b6f3b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PolicyEntry-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.PolicyEntryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PolicyEntry-types">org.apache.activemq.broker.region.policy.PolicyEntry</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-policyEntry-element"><policyEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link PolicyMap} for assigning policies to a
-specific destination or a hierarchical wildcard area of destinations.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="1dc75c90-fddb-49a3-9e92-c58d03179bd0" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.PolicyEntry-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.PolicyEntry-types"><link-body>org.apache.activemq.broker.region.policy.PolicyEntry</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyEntry-element"><link-body><policyEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="02be1c11-eefe-4343-931d-bb87e8a95d81" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link PolicyMap} for assigning policies to a
+specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.DemandForwardingBridgeSupport-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.DemandForwardingBridgeSupportTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.DemandForwardingBridgeSupport-types">org.apache.activemq.network.DemandForwardingBridgeSupport</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-compositeDemandForwardingBridge-element"><compositeDemandForwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A demand forwarding bridge which works with multicast style transports where
-a single Transport could be communicating with multiple remote brokers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-demandForwardingBridge-element"><demandForwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forwards messages from the local broker to the remote broker based on demand.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="bccb4510-ea9a-41ff-9de1-756e77cac0bb" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.DemandForwardingBridgeSupport-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.DemandForwardingBridgeSupport-types"><link-body>org.apache.activemq.network.DemandForwardingBridgeSupport</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeDemandForwardingBridge-element"><link-body><compositeDemandForwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ffca8f24-a960-45e7-a77e-cac64dcf7327" ac:name="html" ac:schema-version="1"><plain-text-body>A demand forwarding bridge which works with multicast style transports where
+a single Transport could be communicating with multiple remote brokers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="demandForwardingBridge-element"><link-body><demandForwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="749b009e-d03c-44e7-adc1-e6537ffbcc58" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards messages from the local broker to the remote broker based on demand.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.jms.OutboundQueueBridge-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.jms.OutboundQueueBridgeTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.OutboundQueueBridge-types">org.apache.activemq.network.jms.OutboundQueueBridge</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-outboundQueueBridge-element"><outboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Queue Bridge</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5ad9c038-96c2-425c-b504-28210f39f312" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.OutboundQueueBridge-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.OutboundQueueBridge-types"><link-body>org.apache.activemq.network.jms.OutboundQueueBridge</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundQueueBridge-element"><link-body><outboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a1fd1ea9-7cb1-4115-87de-4949ca167ccb" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.store.jdbc.JDBCPersistenceAdapterTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types">org.apache.activemq.store.jdbc.JDBCPersistenceAdapter</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jdbcPersistenceAdapter-element"><jdbcPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link PersistenceAdapter} implementation using JDBC for persistence
+<p><structured-macro ac:macro-id="935f643d-b350-43d2-83c9-0529ded8fdee" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCPersistenceAdapter</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jdbcPersistenceAdapter-element"><link-body><jdbcPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="20bf94aa-7347-4924-8cc9-f5831d3c97f5" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link PersistenceAdapter} implementation using JDBC for persistence
storage.
This persistence adapter will correctly remember prepared XA transactions,
but it will not keep track of local transaction commits so that operations
-performed against the Message store are done as a single uow.</p> <p></p></td></tr></tbody></table></div>
+performed against the Message store are done as a single uow.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.command.ActiveMQDestinationTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-queue-element"><queue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Queue</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-topic-element"><topic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Topic</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="13d43015-f1e0-4bc3-98a6-aef6f8905521" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.command.ActiveMQDestination-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="96de6dfd-a0e8-466c-9ce8-7751f428ad3c" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2146b998-8d8b-42ff-910f-e0eada9d4c64" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.jms.InboundTopicBridge-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.jms.InboundTopicBridgeTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.InboundTopicBridge-types">org.apache.activemq.network.jms.InboundTopicBridge</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-inboundTopicBridge-element"><inboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Topic Bridge</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="70501166-1fd0-4c39-a766-1d6da9138efe" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.InboundTopicBridge-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.InboundTopicBridge-types"><link-body>org.apache.activemq.network.jms.InboundTopicBridge</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundTopicBridge-element"><link-body><inboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="52bce5da-3153-4c24-90f2-95517152e108" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsConnector-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.jms.JmsConnectorTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jmsQueueConnector-element"><jmsQueueConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Queue providers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jmsTopicConnector-element"><jmsTopicConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Topic providers</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="8f93f1a9-6594-4412-8ee8-dc81cfe6ec2d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.JmsConnector-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsQueueConnector-element"><link-body><jmsQueueConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="41eec97b-92b5-4a66-a53f-072f4335abf7" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Queue providers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsTopicConnector-element"><link-body><jmsTopicConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="58aadb9b-ea7a-42bd-95fd-d9f1eba103af" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Topic providers</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.RedeliveryPolicy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.RedeliveryPolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.RedeliveryPolicy-types">org.apache.activemq.RedeliveryPolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-redeliveryPolicy-element"><redeliveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Configuration options used to control how messages are re-delivered when they
-are rolled back.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="23f1d57f-a4ae-492a-ad66-deed966ba031" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.RedeliveryPolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.RedeliveryPolicy-types"><link-body>org.apache.activemq.RedeliveryPolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="redeliveryPolicy-element"><link-body><redeliveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dd80bc62-46e9-499e-be54-cb9548fd5a31" ac:name="html" ac:schema-version="1"><plain-text-body>Configuration options used to control how messages are re-delivered when they
+are rolled back.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.security.AuthorizationMap-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.security.AuthorizationMapTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.security.AuthorizationMap-types">org.apache.activemq.security.AuthorizationMap</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationMap-element"><authorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual
+<p><structured-macro ac:macro-id="368bd1be-e04a-49a2-bf1e-f168ae3097c7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.security.AuthorizationMap-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.security.AuthorizationMap-types"><link-body>org.apache.activemq.security.AuthorizationMap</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationMap-element"><link-body><authorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d4c0a60a-d938-4164-947f-9ce899c9502d" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
different policies. Each entry in the map represents the authorization ACLs
-for each operation.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-lDAPAuthorizationMap-element"><lDAPAuthorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An {@link AuthorizationMap} which uses LDAP</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleAuthorizationMap-element"><simpleAuthorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An AuthorizationMap which is configured with individual DestinationMaps for
-each operation.</p> <p></p></td></tr></tbody></table></div>
+for each operation.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="lDAPAuthorizationMap-element"><link-body><lDAPAuthorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="af850a59-61fd-48b7-9b82-66844186d01b" ac:name="html" ac:schema-version="1"><plain-text-body>An {@link AuthorizationMap} which uses LDAP</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleAuthorizationMap-element"><link-body><simpleAuthorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9b20b82d-900e-48fb-92d4-9dfce4149ee3" ac:name="html" ac:schema-version="1"><plain-text-body>An AuthorizationMap which is configured with individual DestinationMaps for
+each operation.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.security.TempDestinationAuthorizationEntry-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.security.TempDestinationAuthorizationEntryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.security.TempDestinationAuthorizationEntry-types">org.apache.activemq.security.TempDestinationAuthorizationEntry</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-tempDestinationAuthorizationEntry-element"><tempDestinationAuthorizationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
+<p><structured-macro ac:macro-id="2eff8fd0-0a65-47ba-9b60-5f26e38af3e5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.security.TempDestinationAuthorizationEntry-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.security.TempDestinationAuthorizationEntry-types"><link-body>org.apache.activemq.security.TempDestinationAuthorizationEntry</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="tempDestinationAuthorizationEntry-element"><link-body><tempDestinationAuthorizationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bac077ba-edf1-46e9-abd2-76465ccc2988" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
different operations (read, write, admin) of user roles to a temporary
-destination</p> <p></p></td></tr></tbody></table></div>
+destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.DispatchPolicy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.DispatchPolicyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.DispatchPolicy-types">org.apache.activemq.broker.region.policy.DispatchPolicy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-roundRobinDispatchPolicy-element"><roundRobinDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Simple dispatch policy that sends a message to every subscription that
-matches the message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleDispatchPolicy-element"><simpleDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Simple dispatch policy that sends a message to every subscription that
-matches the message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-strictOrderDispatchPolicy-element"><strictOrderDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Dispatch policy that causes every subscription to see messages in the same
-order.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="dca1e588-f1c8-41c4-bf0f-c01a827b8e3f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.DispatchPolicy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.DispatchPolicy-types"><link-body>org.apache.activemq.broker.region.policy.DispatchPolicy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="roundRobinDispatchPolicy-element"><link-body><roundRobinDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ebfe70ff-bf81-4c68-a36e-987cf6fae067" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that
+matches the message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleDispatchPolicy-element"><link-body><simpleDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b5a316e3-a146-4c87-89e0-378b7cdb24d9" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that
+matches the message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="strictOrderDispatchPolicy-element"><link-body><strictOrderDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="85d17a00-42ee-4a4b-8545-08d56e2aedbd" ac:name="html" ac:schema-version="1"><plain-text-body>Dispatch policy that causes every subscription to see messages in the same
+order.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-javax.jms.ConnectionFactory-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Thejavax.jms.ConnectionFactoryTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.ConnectionFactory-types">javax.jms.ConnectionFactory</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-connectionFactory-element"><connectionFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced connection
+<p><structured-macro ac:macro-id="c51852a0-de0d-4ff5-b010-46ede6934ce5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">javax.jms.ConnectionFactory-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="javax.jms.ConnectionFactory-types"><link-body>javax.jms.ConnectionFactory</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="connectionFactory-element"><link-body><connectionFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="58d93c9f-67be-43fe-98aa-2bcc0c15df9d" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-xaConnectionFactory-element"><xaConnectionFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced XA connection
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="xaConnectionFactory-element"><link-body><xaConnectionFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="861dbf62-f413-42e2-a6ca-c04d7b89a9fa" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p> <p></p></td></tr></tbody></table></div>
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-javax.jms.Queue-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Thejavax.jms.QueueTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Queue-types">javax.jms.Queue</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-queue-element"><queue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Queue</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="da07d7a9-d8eb-4995-829c-14fd57c9b76a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">javax.jms.Queue-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8bbd14e8-4966-4013-847e-efd174940e58" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.policy.MessageEvictionStrategyTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types">org.apache.activemq.broker.region.policy.MessageEvictionStrategy</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-oldestMessageEvictionStrategy-element"><oldestMessageEvictionStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An eviction strategy which evicts the oldest message first (which is the
-default).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-oldestMessageWithLowestPriorityEvictionStrategy-element"><oldestMessageWithLowestPriorityEvictionStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An eviction strategy which evicts the oldest message with the lowest priority first.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="66b2d73b-91ef-41b6-ab7d-6e199b619934" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types"><link-body>org.apache.activemq.broker.region.policy.MessageEvictionStrategy</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oldestMessageEvictionStrategy-element"><link-body><oldestMessageEvictionStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="acf00f2e-7e8d-4ad4-b1ea-e3d52d93445e" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message first (which is the
+default).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oldestMessageWithLowestPriorityEvictionStrategy-element"><link-body><oldestMessageWithLowestPriorityEvictionStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c902156e-253b-4a8a-86d2-0d76737dd3a7" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message with the lowest priority first.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.Service-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.ServiceTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.Service-types">org.apache.activemq.Service</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-broker-element"><broker></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Message Broker. It consists of a number of transport
+<p><structured-macro ac:macro-id="8cb9d84a-a1a6-4b21-86a5-1c9e9d35d87d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.Service-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.Service-types"><link-body>org.apache.activemq.Service</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="broker-element"><link-body><broker></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d53d10a6-6a32-41b4-8fe0-44735cf6f0e7" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Message Broker. It consists of a number of transport
connectors, network connectors and a bunch of properties which can be used to
-configure the broker as its lazily created.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-commandAgent-element"><commandAgent></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An agent which listens to commands on a JMS destination</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-forwardingBridge-element"><forwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forwards all messages from the local broker to the remote broker.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-inboundQueueBridge-element"><inboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Queue Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-inboundTopicBridge-element"><inboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Topic Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jmsQueueConnector-element"><jmsQueueConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Queue providers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jmsTopicConnector-element"><jmsTopicConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Topic providers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-ldapNetworkConnector-element"><ldapNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>class to create dynamic network connectors listed in an directory
+configure the broker as its lazily created.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="commandAgent-element"><link-body><commandAgent></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="987b2abf-513b-45c0-b1a1-9e49c9343a77" ac:name="html" ac:schema-version="1"><plain-text-body>An agent which listens to commands on a JMS destination</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="forwardingBridge-element"><link-body><forwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8660a95a-e214-4613-994f-119fd350ecd9" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards all messages from the local broker to the remote broker.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundQueueBridge-element"><link-body><inboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="30d66213-8208-4c97-b921-890cd21ac321" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundTopicBridge-element"><link-body><inboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="da37151e-e81c-4b0f-9490-84f16e87b061" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsQueueConnector-element"><link-body><jmsQueueConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dd409d1d-e49d-4c3a-af8c-e2fcbeb2870e" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Queue providers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsTopicConnector-element"><link-body><jmsTopicConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f0119cfd-6fd2-470a-81a2-cf0794cde8a9" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Topic providers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="ldapNetworkConnector-element"><link-body><ldapNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bdfc1612-3d0c-4205-9d79-81b2bd5e4a0d" ac:name="html" ac:schema-version="1"><plain-text-body>class to create dynamic network connectors listed in an directory
server using the LDAP v3 protocol as defined in RFC 2251, the
entries listed in the directory server must implement the ipHost
-and ipService objectClasses as defined in RFC 2307.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-managementContext-element"><managementContext></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Flow provides different dispatch policies within the NMR</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-masterConnector-element"><masterConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Connects a Slave Broker to a Master when using <a shape="rect" href="http://activemq.apache.org/masterslave.html">Master Slave</a> for High
-Availability of messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-memoryUsage-element"><memoryUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+and ipService objectClasses as defined in RFC 2307.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="managementContext-element"><link-body><managementContext></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ce168cdd-0ce5-4741-a268-c1d0b81e4a43" ac:name="html" ac:schema-version="1"><plain-text-body>A Flow provides different dispatch policies within the NMR</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="masterConnector-element"><link-body><masterConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8fc60468-1ec4-41ed-8181-7e42431d06f2" ac:name="html" ac:schema-version="1"><plain-text-body>Connects a Slave Broker to a Master when using <a
+href="http://activemq.apache.org/masterslave.html">Master Slave</a> for High
+Availability of messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="memoryUsage-element"><link-body><memoryUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e525b1de-371e-4523-9d12-e14b0f046be3" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-multicastNetworkConnector-element"><multicastNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses some kind of multicast-like transport that
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="multicastNetworkConnector-element"><link-body><multicastNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="70d095f6-a7de-4a8d-ba1a-2e2c882f446d" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses some kind of multicast-like transport that
communicates with potentially many remote brokers over a single logical
{@link Transport} instance such as when using multicast.
This implementation does not depend on multicast at all; any other group
-based transport could be used.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-networkConnector-element"><networkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses a discovery agent to detect the remote brokers
-available and setup a connection to each available remote broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-outboundQueueBridge-element"><outboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Queue Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-outboundTopicBridge-element"><outboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Topic Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-proxyConnector-element"><proxyConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-storeUsage-element"><storeUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+based transport could be used.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="networkConnector-element"><link-body><networkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b637fd10-79e2-4f6c-bd1d-f0a2c41a98c6" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses a discovery agent to detect the remote brokers
+available and setup a connection to each available remote broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundQueueBridge-element"><link-body><outboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fd7c6b10-3612-4ab9-a385-bedd09aead10" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundTopicBridge-element"><link-body><outboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="47f3f78b-512d-400c-84e9-a1b62aef8d89" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="proxyConnector-element"><link-body><proxyConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f1995391-3e0c-40cb-a534-f11e95e2a94b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="storeUsage-element"><link-body><storeUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fc614fdf-6174-4b49-8edb-2714476fd5a4" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-systemUsage-element"><systemUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Holder for Usage instances for memory, store and temp files Main use case is
-manage memory usage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-tempUsage-element"><tempUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="systemUsage-element"><link-body><systemUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ef223609-2f9f-4055-bd35-3d87898ef872" ac:name="html" ac:schema-version="1"><plain-text-body>Holder for Usage instances for memory, store and temp files Main use case is
+manage memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="tempUsage-element"><link-body><tempUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="987d82f6-b5ea-4f1a-8cfd-00a611a35282" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr></tbody></table></div>
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.jms.JmsMesageConvertorTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleJmsMessageConvertor-element"><simpleJmsMessageConvertor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Converts Message from one JMS to another</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="8d424894-b05e-4cb8-9f95-6dc60fd1065f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.JmsMesageConvertor-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleJmsMessageConvertor-element"><link-body><simpleJmsMessageConvertor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="877d0a1d-60ad-44c0-8ab9-396989e5561c" ac:name="html" ac:schema-version="1"><plain-text-body>Converts Message from one JMS to another</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.jms.OutboundTopicBridge-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.jms.OutboundTopicBridgeTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.OutboundTopicBridge-types">org.apache.activemq.network.jms.OutboundTopicBridge</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-outboundTopicBridge-element"><outboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Topic Bridge</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="4d8363d8-2b0f-4aeb-a260-fd440d986380" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.jms.OutboundTopicBridge-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.jms.OutboundTopicBridge-types"><link-body>org.apache.activemq.network.jms.OutboundTopicBridge</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundTopicBridge-element"><link-body><outboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e8d2e0c3-1245-453b-b9d3-762bf1c9a134" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.broker.region.DestinationInterceptor-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.broker.region.DestinationInterceptorTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.DestinationInterceptor-types">org.apache.activemq.broker.region.DestinationInterceptor</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-mirroredQueue-element"><mirroredQueue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/mirrored-queues.html">Mirrored
-Queue</a> using a prefix and postfix to define the topic name on which to mirror the queue to.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-virtualDestinationInterceptor-element"><virtualDestinationInterceptor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements <a shape="rect" href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a>.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="3b6b7709-c8b1-403a-8415-7d6bc402445e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.broker.region.DestinationInterceptor-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.broker.region.DestinationInterceptor-types"><link-body>org.apache.activemq.broker.region.DestinationInterceptor</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="mirroredQueue-element"><link-body><mirroredQueue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7c6c849f-03ca-413b-a253-0ca5fba48010" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/mirrored-queues.html">Mirrored
+Queue</a> using a prefix and postfix to define the topic name on which to mirror the queue to.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="virtualDestinationInterceptor-element"><link-body><virtualDestinationInterceptor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f71c33d5-c444-4163-8f64-0f7336ed8ca3" ac:name="html" ac:schema-version="1"><plain-text-body>Implements <a
+href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a>.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.filter.DestinationMap-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.filter.DestinationMapTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.filter.DestinationMap-types">org.apache.activemq.filter.DestinationMap</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationMap-element"><authorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual
+<p><structured-macro ac:macro-id="df95e0bc-6168-423c-8701-553e13d03f42" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.filter.DestinationMap-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.filter.DestinationMap-types"><link-body>org.apache.activemq.filter.DestinationMap</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationMap-element"><link-body><authorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8fad016a-ef95-41db-824a-673ce971c4aa" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
different policies. Each entry in the map represents the authorization ACLs
-for each operation.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-policyMap-element"><policyMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual
+for each operation.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyMap-element"><link-body><policyMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a6179d52-f576-4ef7-a212-c1ed12f95ebb" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
-different policies.</p> <p></p></td></tr></tbody></table></div>
+different policies.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-org.apache.activemq.network.NetworkBridgeConfiguration-types"></span></p>
-<h4 id="XBeanXMLReference5.0-Theorg.apache.activemq.network.NetworkBridgeConfigurationTypeImplementations">The <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.NetworkBridgeConfiguration-types">org.apache.activemq.network.NetworkBridgeConfiguration</a></em> Type Implementations</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-ldapNetworkConnector-element"><ldapNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>class to create dynamic network connectors listed in an directory
+<p><structured-macro ac:macro-id="9cbb3bd6-69a8-4aad-849d-7e4784171b10" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">org.apache.activemq.network.NetworkBridgeConfiguration-types</parameter></structured-macro></p>
+<h4>The <em><link ac:anchor="org.apache.activemq.network.NetworkBridgeConfiguration-types"><link-body>org.apache.activemq.network.NetworkBridgeConfiguration</link-body></link></em> Type Implementations</h4>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="ldapNetworkConnector-element"><link-body><ldapNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c6be0d3-7817-42cf-a964-e3faa1c7c516" ac:name="html" ac:schema-version="1"><plain-text-body>class to create dynamic network connectors listed in an directory
server using the LDAP v3 protocol as defined in RFC 2251, the
entries listed in the directory server must implement the ipHost
-and ipService objectClasses as defined in RFC 2307.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-multicastNetworkConnector-element"><multicastNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses some kind of multicast-like transport that
+and ipService objectClasses as defined in RFC 2307.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="multicastNetworkConnector-element"><link-body><multicastNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="66c87715-e3f5-4259-8a78-de3e409ee1c5" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses some kind of multicast-like transport that
communicates with potentially many remote brokers over a single logical
{@link Transport} instance such as when using multicast.
This implementation does not depend on multicast at all; any other group
-based transport could be used.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-networkConnector-element"><networkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses a discovery agent to detect the remote brokers
-available and setup a connection to each available remote broker</p> <p></p></td></tr></tbody></table></div>
+based transport could be used.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="networkConnector-element"><link-body><networkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="93705898-8a5f-4a30-bc70-782ccacd7ca6" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses a discovery agent to detect the remote brokers
+available and setup a connection to each available remote broker</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-amqPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<amqPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-amqPersistenceAdapter-element"><amqPersistenceAdapter></a></em> Element</h3>
-<p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a
+<p><structured-macro ac:macro-id="3745d24f-c616-4a51-9eb3-dc18e89a9bf0" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">amqPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="amqPersistenceAdapter-element"><link-body><amqPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="0c5157da-63f5-4513-8378-8df78e308b86" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a
{@link Journal} and then check pointing asynchronously on a timeout with some
-other long term persistent storage.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> archiveDataLogs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> asyncDataManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.kaha.impl.async.AsyncDataManager</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> checkpointInterval </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cleanupInterval </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> directory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> directoryArchive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> indexBinSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> indexKeySize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> indexPageSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>When set using XBean, you can use values such as: "20
-mb", "1024 kb", or "1 gb"</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>When set using XBean, you can use values such as: "20
-mb", "1024 kb", or "1 gb"</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxFileLength </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>When set using XBean, you can use values such as: "20
-mb", "1024 kb", or "1 gb"</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistentIndex </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> referenceStoreAdapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.store.ReferenceStoreAdapter</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> syncOnWrite </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useNio </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.wireformat.WireFormat</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+other long term persistent storage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> archiveDataLogs </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a1d67710-b326-43d3-9ad9-8f1a3f7965cf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> asyncDataManager </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.kaha.impl.async.AsyncDataManager</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="98aae3f8-08c4-4e09-854d-f6b20a6d6969" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1f8ed185-ec47-42d4-98df-12a6b5d8779d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7f7f698c-4e7b-4565-a5fc-e461af647a09" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> checkpointInterval </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="353946bc-3137-48d2-9b9b-3008eddc5f46" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> cleanupInterval </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="81d5c57b-1f7c-4ed7-8f8b-8848b4ccec4c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> directory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3ffa0b5e-ce49-4d97-9d4f-5d54b9ebfedc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> directoryArchive </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d12c188a-c1c0-4a32-9879-8cb351450970" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> indexBinSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3cb9f711-8773-4e63-9b79-481f0a1b13e1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> indexKeySize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5ba78e81-4d6b-4ddc-a775-aa9484828b3b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> indexPageSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a6d4a934-3b95-4db4-8bcb-3bb814f3a32d" ac:name="html" ac:schema-version="1"><plain-text-body>When set using XBean, you can use values such as: "20
+mb", "1024 kb", or "1 gb"</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="26fb2dc6-afb6-45e0-8e9a-6367c34644a8" ac:name="html" ac:schema-version="1"><plain-text-body>When set using XBean, you can use values such as: "20
+mb", "1024 kb", or "1 gb"</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxFileLength </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="da7298ce-ace3-4140-bc0a-2557e133c0aa" ac:name="html" ac:schema-version="1"><plain-text-body>When set using XBean, you can use values such as: "20
+mb", "1024 kb", or "1 gb"</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistentIndex </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="406b4a1d-1e3a-48d4-9052-3d6effaef04c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> referenceStoreAdapter </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.store.ReferenceStoreAdapter</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="908c7395-a639-47c9-8903-39e3751e8b8c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> syncOnWrite </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f9f08e29-8b4a-40ef-bf26-e7b91f865247" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="58879a16-fbf4-4979-955c-d1b8e0d338a8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a0020715-0e9c-45be-8bc1-caff5b6a33c1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useNio </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="991406ce-f71d-483d-ba40-be90464abd01" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.wireformat.WireFormat</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6cb672d3-0158-415f-b476-192e16306b13" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-amqPersistenceAdapterFactory-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<amqPersistenceAdapterFactory>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-amqPersistenceAdapterFactory-element"><amqPersistenceAdapterFactory></a></em> Element</h3>
-<p> </p><p>An implementation of {@link PersistenceAdapterFactory}</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.1">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journalThreadPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxFileLength </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistentIndex </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> referenceStoreAdapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.store.ReferenceStoreAdapter</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> syncOnWrite </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useNio </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="89a7f343-cf5c-43df-b0b0-08618e49c9ef" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">amqPersistenceAdapterFactory-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="amqPersistenceAdapterFactory-element"><link-body><amqPersistenceAdapterFactory></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="bb761e3f-4611-4b2f-881a-27d105a87373" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapterFactory}</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9d0a14ee-53d3-4214-a407-320fb89e1c32" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7c3b42e8-6f97-4956-9ef1-5f780ad20995" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journalThreadPriority </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="01541722-97f2-4d3a-a46d-af363a6dfd88" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxFileLength </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8c664a74-45b8-4c0e-8e78-02fadedc51fc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistentIndex </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5384c9d3-e0c2-4bd3-80ad-94c099a150b0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> referenceStoreAdapter </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.store.ReferenceStoreAdapter</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3b79e81a-e46f-40fd-8027-1d447fe8bebc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> syncOnWrite </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="57971894-2dee-4712-a454-dabb94370330" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f340d0f7-3816-4868-a6f7-fc04db5fc248" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useNio </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4c07f53d-d103-4105-83db-e42a63d9bbff" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-authenticationUser-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<authenticationUser>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-authenticationUser-element"><authenticationUser></a></em> Element</h3>
-<p> </p><p>A helper object used to configure simple authentiaction plugin</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.2">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> groups </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> username </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="d49eddee-b5dd-43d9-bb27-813508f90c55" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">authenticationUser-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="authenticationUser-element"><link-body><authenticationUser></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="86a2be6a-12c9-47d4-8057-5ac0fd49a268" ac:name="html" ac:schema-version="1"><plain-text-body>A helper object used to configure simple authentiaction plugin</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> groups </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="358fbca7-c698-458c-a755-b95c72fb067e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3c642757-f549-42cb-8298-8ba4d2d8fb05" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> username </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f2a34598-39ea-4039-920d-f99bc0b0c440" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-authorizationEntry-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<authorizationEntry>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationEntry-element"><authorizationEntry></a></em> Element</h3>
-<p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
+<p><structured-macro ac:macro-id="9bdc4cc7-5081-4cea-85c2-06bc37a4be70" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">authorizationEntry-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="authorizationEntry-element"><link-body><authorizationEntry></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="dc05464b-04b2-436a-bd97-39fcc70166f4" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
different operations (read, write, admin) of user roles to a specific
-destination or a hierarchical wildcard area of destinations.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.3">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> admin </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> groupClass </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> read </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> readACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> write </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> writeACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> admin </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a4698fbc-3417-4fc0-aba5-646d253d19ec" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> adminACLs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5d0e74e3-04ad-440b-b0b5-74cb1212216f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d37145bb-6757-4cd6-b2e4-7edda6b0b3f0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> groupClass </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e38abf88-0da0-49cb-b6d1-d6062d616c11" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="092c0bac-83ba-49ad-b1b2-8414ca35c9ee" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> read </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="16dd2d71-d6a5-42c4-aeb2-b84c7be742ba" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> readACLs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0afd7173-4629-457b-8b18-b1fd76cd9710" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topic </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="28a272e4-8742-4dff-af02-559497f197a1" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> write </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fec54e5a-027a-48a2-a56f-21b9af3feb98" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> writeACLs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c075c6f5-3fac-440d-924b-83210c932d67" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-authorizationMap-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<authorizationMap>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationMap-element"><authorizationMap></a></em> Element</h3>
-<p> </p><p>Represents a destination based configuration of policies so that individual
+<p><structured-macro ac:macro-id="2873ee07-9d8d-4545-8e42-12adc8b5fcae" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">authorizationMap-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="authorizationMap-element"><link-body><authorizationMap></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="240d1ba6-0707-4ba1-9ba3-a662d17bbd14" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
different policies. Each entry in the map represents the authorization ACLs
-for each operation.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.4">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> authorizationEntries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the individual entries on the authorization map</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> defaultEntry </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.security.AuthorizationEntry-types">org.apache.activemq.security.AuthorizationEntry</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> entries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to allow the destination map to be populated from a
-dependency injection framework such as Spring</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tempDestinationAuthorizationEntry </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.security.TempDestinationAuthorizationEntry-types">org.apache.activemq.security.TempDestinationAuthorizationEntry</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+for each operation.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> authorizationEntries </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6bb890f5-7bca-4f0c-ad95-573cb680e805" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the individual entries on the authorization map</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> defaultEntry </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.security.AuthorizationEntry-types"><link-body>org.apache.activemq.security.AuthorizationEntry</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="94be7f3a-7de9-4afa-9057-65aa7152eced" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> entries </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3801ec75-2f8c-4163-9e44-96393cdff52e" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to allow the destination map to be populated from a
+dependency injection framework such as Spring</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> tempDestinationAuthorizationEntry </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.security.TempDestinationAuthorizationEntry-types"><link-body>org.apache.activemq.security.TempDestinationAuthorizationEntry</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5e51c502-b52a-4a6e-ab70-0ad13cc6c8b4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-authorizationPlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<authorizationPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationPlugin-element"><authorizationPlugin></a></em> Element</h3>
-<p> </p><p>An authorization plugin where each operation on a destination is checked
-against an authorizationMap</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.5">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> map </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.security.AuthorizationMap-types">org.apache.activemq.security.AuthorizationMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="f8f16ede-ac98-47d1-88a2-a5128043e1ac" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">authorizationPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="authorizationPlugin-element"><link-body><authorizationPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="63f5551b-07ef-4f43-80e0-b7d3ecb45c47" ac:name="html" ac:schema-version="1"><plain-text-body>An authorization plugin where each operation on a destination is checked
+against an authorizationMap</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> map </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.security.AuthorizationMap-types"><link-body>org.apache.activemq.security.AuthorizationMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b7fe277b-993c-4827-b8c7-e01f1a3842a0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-axionJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<axionJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-axionJDBCAdapter-element"><axionJDBCAdapter></a></em> Element</h3>
-<p> </p><p>Axion specific Adapter.
+<p><structured-macro ac:macro-id="f7a9e390-633c-4fd5-9c58-3a549acb2e7d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">axionJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="axionJDBCAdapter-element"><link-body><axionJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5305956c-4042-4198-abd0-12d5d2ccc0e8" ac:name="html" ac:schema-version="1"><plain-text-body>Axion specific Adapter.
Axion does not seem to support ALTER statements or sub-selects. This means:
- We cannot auto upgrade the schema was we roll out new versions of ActiveMQ
-- We cannot delete durable sub messages that have be acknowledged by all consumers.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.6">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+- We cannot delete durable sub messages that have be acknowledged by all consumers.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8c068413-b525-492d-a019-97d6719274a4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f74e0f48-2c41-4147-8e8a-d2ff809aa4d1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0061d2bf-fb85-402c-8675-43589e48e8d3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-blobJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<blobJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-blobJDBCAdapter-element"><blobJDBCAdapter></a></em> Element</h3>
-<p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob()
+<p><structured-macro ac:macro-id="608ef835-8904-4710-8b30-4bd83a833a97" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">blobJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="blobJDBCAdapter-element"><link-body><blobJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="c4df4f63-50a4-4b9e-b2b1-24d99b60a557" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob()
operations. This is a little more involved since to insert a blob you have
to:
@@ -512,897 +526,928 @@
value.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li></li></ul><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.7">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f75092ad-14a3-4be2-85ec-311cb60a1232" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a40fb71e-4555-4a28-8db1-a74aff47bd92" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d71a39ec-14d4-44d1-b7a2-ca815ab4b349" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-broker-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<broker>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-broker-element"><broker></a></em> Element</h3>
-<p> </p><p>An ActiveMQ Message Broker. It consists of a number of transport
+<p><structured-macro ac:macro-id="f0cafd7e-ec14-476b-8ca9-2e3c7528d3ec" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">broker-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="broker-element"><link-body><broker></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="24460760-995f-4791-ab9c-f74a379abaff" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Message Broker. It consists of a number of transport
connectors, network connectors and a bunch of properties which can be used to
-configure the broker as its lazily created.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.8">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminView </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.jmx.BrokerView</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Returns the administration view of the broker; used to create and destroy
+configure the broker as its lazily created.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adminView </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.jmx.BrokerView</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2710a3b0-58f7-4d05-be2d-894a7677cde3" ac:name="html" ac:schema-version="1"><plain-text-body>Returns the administration view of the broker; used to create and destroy
resources such as queues and topics. Note this method returns null if JMX
-is disabled.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> advisorySupport </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Allows the support of advisory messages to be disabled for performance
-reasons.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the name of this broker; which must be unique in the network</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerObjectName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMX ObjectName for this broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clustered </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerSystemUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the directory in which the data files will be stored by default for
-the JDBC and Journal persistence adaptors.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the directory in which the data files will be stored by default for
-the JDBC and Journal persistence adaptors.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deleteAllMessagesOnStartup </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not all messages are deleted on startup - mostly only
-useful for testing.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.region.DestinationFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationInterceptors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.DestinationInterceptor-types">org.apache.activemq.broker.region.DestinationInterceptor</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination interceptors to use</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PolicyMap-types">org.apache.activemq.broker.region.policy.PolicyMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination specific policies available either for exact
-destinations or for wildcard areas of destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destinations which should be loaded/created on startup</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> enableStatistics </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not the Broker's services enable statistics or not.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsBridgeConnectors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> keepDurableSubsActive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> managementContext </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.jmx.ManagementContext-types">org.apache.activemq.broker.jmx.ManagementContext</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> masterConnectorURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageAuthorizationPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.security.MessageAuthorizationPolicy</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the policy used to decide if the current connection is authorized to
-consume a given message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkConnectorURIs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkConnectors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.NetworkConnector-types">org.apache.activemq.network.NetworkConnector</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the network connectors which this broker will use to connect to
-other brokers in a federated network</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistenceAdapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the persistence adaptor implementation to use for this broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistenceFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapterFactory-types">org.apache.activemq.store.PersistenceAdapterFactory</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistenceTaskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistenceThreadPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not persistence is enabled or disabled.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> plugins </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerPlugin-types">org.apache.activemq.broker.BrokerPlugin</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets a number of broker plugins to install such as for security
-authentication or authorization</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> populateJMSXUserID </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not the broker should populate the JMSXUserID header.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerSystemUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> proxyConnectors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the network connectors which this broker will use to connect to
-other brokers in a federated network</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> services </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.Service-types">org.apache.activemq.Service</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the services associated with this broker such as a
-{@link MasterConnector}</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> shutdownOnMasterFailure </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> start </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not the broker is started along with the ApplicationContext it is defined within.
+is disabled.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> advisorySupport </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="599348a9-d37e-4794-a932-136e316e50f2" ac:name="html" ac:schema-version="1"><plain-text-body>Allows the support of advisory messages to be disabled for performance
+reasons.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3b934a6f-6760-47d0-8f3a-1274b16e4ff7" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the name of this broker; which must be unique in the network</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerObjectName </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a4b168d1-42c5-4de1-8d23-5af8f395a97a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMX ObjectName for this broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> clustered </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2d260fb2-17e7-4469-98ec-3e10064b1377" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerSystemUsage </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5db8eec2-218c-4d7f-bd3d-fa67fa68d2a3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9144ccb8-05d9-4c49-b201-42caa08a5642" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the directory in which the data files will be stored by default for
+the JDBC and Journal persistence adaptors.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="548910ce-4d69-4599-8706-3366270e7b16" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the directory in which the data files will be stored by default for
+the JDBC and Journal persistence adaptors.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> deleteAllMessagesOnStartup </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c5791ada-9c75-4854-b58a-44f3336aa5e7" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not all messages are deleted on startup - mostly only
+useful for testing.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.region.DestinationFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a4a9ba3c-960a-4927-a498-0c482e1188b0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationInterceptors </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.broker.region.DestinationInterceptor-types"><link-body>org.apache.activemq.broker.region.DestinationInterceptor</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="102a3279-6033-4fb1-a52e-b6abfb1788d1" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination interceptors to use</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PolicyMap-types"><link-body>org.apache.activemq.broker.region.policy.PolicyMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="564a4486-e3dc-4d42-a9c6-f1c630acbd7f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination specific policies available either for exact
+destinations or for wildcard areas of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="39d76dcb-5044-4946-85af-1a76d4d3cc8c" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destinations which should be loaded/created on startup</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> enableStatistics </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bde469a7-bbc2-4cb6-8220-49cadf766970" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not the Broker's services enable statistics or not.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsBridgeConnectors </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="aff2d436-bc89-4cb6-8b1c-f6864e79ab28" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> keepDurableSubsActive </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="eb535014-73a8-41fb-b52b-a549e8119296" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> managementContext </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.jmx.ManagementContext-types"><link-body>org.apache.activemq.broker.jmx.ManagementContext</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6c9eeaa4-3dc2-4905-bc61-ff42c3fa86e8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> masterConnectorURI </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="592475b8-354a-4e0e-b68f-a2c4f1004453" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageAuthorizationPolicy </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.security.MessageAuthorizationPolicy</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="45c78deb-230c-4c70-a429-8bac5112c62a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the policy used to decide if the current connection is authorized to
+consume a given message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkConnectorURIs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e2209d68-3c24-45eb-b5d0-7bc300d22692" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkConnectors </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.NetworkConnector-types"><link-body>org.apache.activemq.network.NetworkConnector</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2ad333c7-29ae-4506-a428-294caf2dc663" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the network connectors which this broker will use to connect to
+other brokers in a federated network</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistenceAdapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="baa98fd7-893a-4971-9c89-1c9905597a7f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the persistence adaptor implementation to use for this broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistenceFactory </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapterFactory-types"><link-body>org.apache.activemq.store.PersistenceAdapterFactory</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3accf46f-2e32-47db-beba-bc241a1cfd9b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistenceTaskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c10b5055-70fd-49e0-af0d-5ed1d9f49d43" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistenceThreadPriority </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ade218a6-7803-4e7d-9fed-27cd208714b3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistent </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8659ee73-31ee-4b1e-b1a4-8a0ff71512ed" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not persistence is enabled or disabled.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> plugins </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.broker.BrokerPlugin-types"><link-body>org.apache.activemq.broker.BrokerPlugin</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ad586b72-430e-40ed-921d-3fb9b53403fc" ac:name="html" ac:schema-version="1"><plain-text-body>Sets a number of broker plugins to install such as for security
+authentication or authorization</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> populateJMSXUserID </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e9ea2eed-88ed-4f1f-a137-c9dc9ece771f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not the broker should populate the JMSXUserID header.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerSystemUsage </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="65cd539a-e24d-4440-a208-a1fcc9249a2c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> proxyConnectors </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3e0ec582-d8bd-498d-9c46-dad9bf4abeda" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the network connectors which this broker will use to connect to
+other brokers in a federated network</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> services </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.Service-types"><link-body>org.apache.activemq.Service</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bf55c682-a59c-4ff2-860d-229f76490219" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the services associated with this broker such as a
+{@link MasterConnector}</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> shutdownOnMasterFailure </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="61defbf3-e082-4535-9e4a-b8691165ba04" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> start </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3adacdd6-3e65-445c-9576-486afa411836" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not the broker is started along with the ApplicationContext it is defined within.
Normally you would want the broker to start up along with the ApplicationContext but sometimes when working
-with JUnit tests you may wish to start and stop the broker explicitly yourself.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> supportFailOver </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> systemUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tempDataStore </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.kaha.Store</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tmpDataDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transportConnectorURIs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transportConnectors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.TransportConnector-types">org.apache.activemq.broker.TransportConnector</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the transport connectors which this broker will listen on for new
-clients</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useJmx </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not the Broker's services should be exposed into JMX or
-not.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useLocalHostBrokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useLoggingForShutdownErrors </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not we should use commons-logging when reporting errors
-when shutting down the broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useMirroredQueues </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not <a shape="rect" href="http://activemq.apache.org/mirrored-queues.html">Mirrored
-Queues</a> should be supported by default if they have not been
-explicitly configured.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useShutdownHook </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not we should use a shutdown handler to close down the
+with JUnit tests you may wish to start and stop the broker explicitly yourself.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> supportFailOver </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="66c8f8bb-bf4e-4665-a123-f02b5a1c923a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> systemUsage </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5d3593af-5b54-40ed-9e95-74a71af26fd4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c4e44081-a980-48c3-9fc4-ecef41ed81fb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> tempDataStore </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.kaha.Store</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="db41341d-a35c-4b02-bc1c-a4baf9a39027" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> tmpDataDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d0e76f52-d90d-457b-8f8f-9c8b97f5b71b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> transportConnectorURIs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="25fa2ac8-9db7-4a99-8eec-02234a6a6103" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> transportConnectors </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.broker.TransportConnector-types"><link-body>org.apache.activemq.broker.TransportConnector</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="21697d7f-9c35-4985-b03b-b322278ec67b" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the transport connectors which this broker will listen on for new
+clients</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useJmx </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c85e985d-5b14-4f98-9d46-116f0fd131af" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not the Broker's services should be exposed into JMX or
+not.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useLocalHostBrokerName </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b32e0e96-bcdd-486d-a04f-dc39005bc125" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useLoggingForShutdownErrors </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2b4cdf6e-b6ec-4410-86d6-1cfe9d35a82f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not we should use commons-logging when reporting errors
+when shutting down the broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useMirroredQueues </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="924c2f9e-e548-4aa7-85bf-a42818622a9f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not <a
+href="http://activemq.apache.org/mirrored-queues.html">Mirrored
+Queues</a> should be supported by default if they have not been
+explicitly configured.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useShutdownHook </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="77fcde0c-6e9c-4067-a34f-6e21f04d5e67" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not we should use a shutdown handler to close down the
broker cleanly if the JVM is terminated. It is recommended you leave this
-enabled.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useVirtualTopics </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not <a shape="rect" href="http://activemq.apache.org/virtual-destinations.html">Virtual
-Topics</a> should be supported by default if they have not been
-explicitly configured.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> vmConnectorURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+enabled.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useVirtualTopics </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fe300df8-46d1-46d7-ae12-dbed03a3e0be" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not <a
+href="http://activemq.apache.org/virtual-destinations.html">Virtual
+Topics</a> should be supported by default if they have not been
+explicitly configured.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> vmConnectorURI </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="158cddca-cd85-448d-bebe-9e7989a304ae" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-bytesJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<bytesJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-bytesJDBCAdapter-element"><bytesJDBCAdapter></a></em> Element</h3>
-<p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the
+<p><structured-macro ac:macro-id="012ff863-2693-446e-9260-5b35684f236a" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">bytesJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="bytesJDBCAdapter-element"><link-body><bytesJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="affc127f-81d5-4342-9233-4eecca5c751b" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the
setBytes()/getBytes() operations. The databases/JDBC drivers that use this
-adapter are:</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.9">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+adapter are:</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1b7d47b9-ce79-42f5-9ac2-c723377b3d76" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c69bb7f3-a25d-48a0-9393-8f490148a5a9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="eeb22c68-a47a-4be7-b320-d74071d4090c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-commandAgent-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<commandAgent>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-commandAgent-element"><commandAgent></a></em> Element</h3>
-<p> </p><p>An agent which listens to commands on a JMS destination</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.10">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerUrl </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> commandDestination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Destination-types">javax.jms.Destination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.Connection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.ConnectionFactory-types">javax.jms.ConnectionFactory</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="9096406a-b5ba-4b52-8dee-0cb876732dfc" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">commandAgent-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="commandAgent-element"><link-body><commandAgent></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f2d58048-cf40-4dd8-89c3-0da7e96edadc" ac:name="html" ac:schema-version="1"><plain-text-body>An agent which listens to commands on a JMS destination</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerUrl </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9ff3c25d-3513-4dd6-9ec4-bb255e734479" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> commandDestination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Destination-types"><link-body>javax.jms.Destination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="75267250-f99a-4cbd-82f9-98b2fa13922c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.Connection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="56d772f2-c18a-4394-ac41-9f6a1c16a23f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionFactory </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.ConnectionFactory-types"><link-body>javax.jms.ConnectionFactory</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8610e037-6feb-46dc-8076-74ca2c2b9451" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-compositeDemandForwardingBridge-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<compositeDemandForwardingBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-compositeDemandForwardingBridge-element"><compositeDemandForwardingBridge></a></em> Element</h3>
-<p> </p><p>A demand forwarding bridge which works with multicast style transports where
-a single Transport could be communicating with multiple remote brokers</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.11">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> configuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.NetworkBridgeConfiguration-types">org.apache.activemq.network.NetworkBridgeConfiguration</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createdByDuplex </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkBridgeListener </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.network.NetworkBridgeListener</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="7f017ef2-71a9-41b3-92d4-0133de424193" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">compositeDemandForwardingBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="compositeDemandForwardingBridge-element"><link-body><compositeDemandForwardingBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="cdb89ebc-01c7-40fc-a113-4238ae211c22" ac:name="html" ac:schema-version="1"><plain-text-body>A demand forwarding bridge which works with multicast style transports where
+a single Transport could be communicating with multiple remote brokers</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> configuration </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.NetworkBridgeConfiguration-types"><link-body>org.apache.activemq.network.NetworkBridgeConfiguration</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d271a0d7-e288-42f1-b368-011e5e449720" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createdByDuplex </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="601aa838-1afb-43ab-808b-f7ee69e3490f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b918ba83-26cd-4c8b-beaa-da390489ff1d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="07e3e71c-2298-42aa-88c2-7a1d9834dfe3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="65bbfa0f-40ff-4f01-a646-36ee8730898d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d8c90d77-ac04-4b1b-becf-97d11c2c9aa7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkBridgeListener </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.network.NetworkBridgeListener</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="72d7dfb4-09d5-4364-a9b3-61c2023e24bd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a05784b3-98e0-4b70-b261-d26bc6869108" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4e067b86-f8bb-400c-b444-07358bf664f5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-compositeQueue-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<compositeQueue>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-compositeQueue-element"><compositeQueue></a></em> Element</h3>
-<p> </p><p>Represents a virtual queue which forwards to a number of other destinations.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.12">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> copyMessage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a copy of the message will be sent to each destination.
+<p><structured-macro ac:macro-id="5ab24654-a11e-443f-827c-89ad7c7ba6b1" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">compositeQueue-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="compositeQueue-element"><link-body><compositeQueue></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="bf1b164d-f516-4dfc-b8d9-1a08642c13fe" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual queue which forwards to a number of other destinations.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> copyMessage </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5404fccb-ae85-4483-b575-dc74d68a0d29" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a copy of the message will be sent to each destination.
Defaults to true so that the forward destination is set as the
-destination of the message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> forwardOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets if the virtual destination is forward only (and so there is no
+destination of the message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> forwardOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="75f9ec01-cce5-49e8-adcf-d10152673def" ac:name="html" ac:schema-version="1"><plain-text-body>Sets if the virtual destination is forward only (and so there is no
physical queue to match the virtual queue) or if there is also a physical
-queue with the same name).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> forwardTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the list of destinations to forward to</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the name of this composite destination</p> <p></p></td></tr></tbody></table></div>
+queue with the same name).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> forwardTo </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2804e268-1143-45b5-9063-bcaa90583d4a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the list of destinations to forward to</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7c988f07-9905-46b1-b15a-ed5ba21e6273" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the name of this composite destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-compositeTopic-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<compositeTopic>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-compositeTopic-element"><compositeTopic></a></em> Element</h3>
-<p> </p><p>Represents a virtual topic which forwards to a number of other destinations.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.13">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> copyMessage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a copy of the message will be sent to each destination.
+<p><structured-macro ac:macro-id="62bcf626-7341-4c60-8617-da3484de4474" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">compositeTopic-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="compositeTopic-element"><link-body><compositeTopic></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="b360b288-e223-4a12-a56a-5287dc814956" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual topic which forwards to a number of other destinations.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> copyMessage </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="75f2ae12-b0b5-429d-a437-813a9de88490" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a copy of the message will be sent to each destination.
Defaults to true so that the forward destination is set as the
-destination of the message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> forwardOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets if the virtual destination is forward only (and so there is no
+destination of the message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> forwardOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="10f695eb-b55f-4ba2-90ba-642e825ba11e" ac:name="html" ac:schema-version="1"><plain-text-body>Sets if the virtual destination is forward only (and so there is no
physical queue to match the virtual queue) or if there is also a physical
-queue with the same name).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> forwardTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the list of destinations to forward to</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the name of this composite destination</p> <p></p></td></tr></tbody></table></div>
+queue with the same name).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> forwardTo </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="25906245-f3bb-4991-87ce-78f0fac5522e" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the list of destinations to forward to</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2450f3db-1356-43e9-b54b-d20368917ea2" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the name of this composite destination</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-connectionDotFilePlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<connectionDotFilePlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-connectionDotFilePlugin-element"><connectionDotFilePlugin></a></em> Element</h3>
-<p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which
-creates a DOT file showing the current connections</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.14">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> file </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination file name to create the destination diagram</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="e87e6224-f38f-4998-8ade-391e809aaafc" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">connectionDotFilePlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="connectionDotFilePlugin-element"><link-body><connectionDotFilePlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f115cb28-5757-472e-8f44-d08cc4c17060" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which
+creates a DOT file showing the current connections</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> file </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0d54932f-5fc8-48a6-a538-ced6408c3ff0" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination file name to create the destination diagram</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-connectionFactory-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<connectionFactory>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-connectionFactory-element"><connectionFactory></a></em> Element</h3>
-<p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced connection
+<p><structured-macro ac:macro-id="5185e430-ac39-447c-b7fc-16469cd8f2ed" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">connectionFactory-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="connectionFactory-element"><link-body><connectionFactory></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="36f0f040-f625-45e8-92bc-122da77f1d0b" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.15">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> alwaysSessionAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>If this flag is set then a separate thread is not used for dispatching
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> alwaysSessionAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3d7758fe-622e-4f2b-b792-00cd183739e4" ac:name="html" ac:schema-version="1"><plain-text-body>If this flag is set then a separate thread is not used for dispatching
messages for each Session in the Connection. However, a separate thread
is always used if there is more than one session, or the session isn't in
-auto acknowledge or duplicates ok mode</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> alwaysSyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Set true if always require messages to be sync sent</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> beanName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> blobTransferPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.blob.BlobTransferPolicy</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the policy used to describe how out-of-band BLOBs (Binary Large
-OBjects) are transferred from producers to brokers to consumers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerURL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the <a shape="rect" href="http://activemq.apache.org/configuring-transports.html">connection
-URL</a> used to connect to the ActiveMQ broker.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clientID </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMS clientID to use for the created connection. Note that this
+auto acknowledge or duplicates ok mode</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> alwaysSyncSend </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f4910133-f6ea-4c1a-9249-d4f412cfaa45" ac:name="html" ac:schema-version="1"><plain-text-body>Set true if always require messages to be sync sent</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> beanName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a4f042b4-92d5-4a49-96cb-a40e17acb8a2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> blobTransferPolicy </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.blob.BlobTransferPolicy</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2d0b9f1f-e259-4f68-8104-506d9c7f2292" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the policy used to describe how out-of-band BLOBs (Binary Large
+OBjects) are transferred from producers to brokers to consumers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerURL </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9f62e4ca-ca14-4ae8-a04a-2519c7a5fd45" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the <a
+href="http://activemq.apache.org/configuring-transports.html">connection
+URL</a> used to connect to the ActiveMQ broker.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> clientID </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f49c6695-4d93-4049-b1d4-f25c3b918ce6" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMS clientID to use for the created connection. Note that this
can only be used by one connection at once so generally its a better idea
-to set the clientID on a Connection</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clientIDPrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix used by autogenerated JMS Client ID values which are used
-if the JMS client does not explicitly specify on.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clientIdGenerator </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.util.IdGenerator</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> closeTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the timeout before a close is considered complete. Normally a
+to set the clientID on a Connection</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> clientIDPrefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="692e5e1b-eb46-40ac-8c4b-babde2f868f5" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix used by autogenerated JMS Client ID values which are used
+if the JMS client does not explicitly specify on.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> clientIdGenerator </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.util.IdGenerator</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b5bb875d-15fc-4020-ad1b-a2719bc83e6f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> closeTimeout </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f84d69d8-acf3-4c2f-86da-3a7546078702" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the timeout before a close is considered complete. Normally a
close() on a connection waits for confirmation from the broker; this
allows that operation to timeout to save the client hanging if there is
-no broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> copyMessageOnSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Should a JMS message be copied to a new JMS Message object as part of the
+no broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> copyMessageOnSend </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c77d27e4-ec1b-4e8f-bc98-789f2a615d9b" ac:name="html" ac:schema-version="1"><plain-text-body>Should a JMS message be copied to a new JMS Message object as part of the
send() method in JMS. This is enabled by default to be compliant with the
JMS specification. You can disable it if you do not mutate JMS messages
-after they are sent for a performance boost</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> disableTimeStampsByDefault </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not timestamps on messages should be disabled or not. If
-you disable them it adds a small performance boost.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables the default setting of whether or not consumers have
-their messages <a shape="rect" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatched
-synchronously or asynchronously by the broker</a>. For non-durable
+after they are sent for a performance boost</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> disableTimeStampsByDefault </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="40efc626-723c-46cf-b9d3-54c3f71473b0" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not timestamps on messages should be disabled or not. If
+you disable them it adds a small performance boost.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d228d9c9-38bc-4bda-8e51-d54fd8a63625" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables the default setting of whether or not consumers have
+their messages <a
+href="http://activemq.apache.org/consumer-dispatch-async.html">dispatched
+synchronously or asynchronously by the broker</a>. 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.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> exclusiveConsumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables whether or not queue consumers should be exclusive or
-not for example to preserve ordering when not using <a shape="rect" href="http://activemq.apache.org/message-groups.html">Message Groups</a></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> nestedMapAndListEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables/disables whether or not Message properties and MapMessage entries
-support <a shape="rect" href="http://activemq.apache.org/structured-message-properties-and-mapmessages.html">Nested
-Structures</a> of Map and List objects</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> objectMessageSerializationDefered </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>When an object is set on an ObjectMessage, the JMS spec requires the
+not block delivery to other consumers.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> exclusiveConsumer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ac8c96bf-daf8-430c-92d6-e3eef6bc2d49" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables whether or not queue consumers should be exclusive or
+not for example to preserve ordering when not using <a
+href="http://activemq.apache.org/message-groups.html">Message Groups</a></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> nestedMapAndListEnabled </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3f17d721-7cae-49c3-98c5-bccaed881ac8" ac:name="html" ac:schema-version="1"><plain-text-body>Enables/disables whether or not Message properties and MapMessage entries
+support <a
+href="http://activemq.apache.org/structured-message-properties-and-mapmessages.html">Nested
+Structures</a> of Map and List objects</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> objectMessageSerializationDefered </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6635dea5-28e0-4a70-a143-064487868c89" ac:name="html" ac:schema-version="1"><plain-text-body>When an object is set on an ObjectMessage, the JMS spec requires the
object to be serialized by that set method. Enabling this flag causes the
object to not get serialized. The object may subsequently get serialized
-if the message needs to be sent over a socket or stored to disk.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> optimizeAcknowledge </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> optimizedMessageDispatch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>If this flag is set then an larger prefetch limit is used - only
-applicable for durable topic subscribers.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMS password used for connections created from this factory</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.ActiveMQPrefetchPolicy-types">org.apache.activemq.ActiveMQPrefetchPolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the <a shape="rect" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch
-policy</a> for consumers created by this connection.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerWindowSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> properties </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Get the properties from this instance for storing in JNDI</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> redeliveryPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.RedeliveryPolicy-types">org.apache.activemq.RedeliveryPolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the global redelivery policy to be used when a message is delivered
-but the session is rolled back</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statsEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transformer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.MessageTransformer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the transformer used to transform messages before they are sent on
+if the message needs to be sent over a socket or stored to disk.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> optimizeAcknowledge </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="913625af-a06b-4961-be2c-d1cd4ec02d33" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> optimizedMessageDispatch </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="79b678c0-3ba4-4ee1-a884-db9b5d257b95" ac:name="html" ac:schema-version="1"><plain-text-body>If this flag is set then an larger prefetch limit is used - only
+applicable for durable topic subscribers.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="48387050-702a-438a-9e40-69c629bfb42d" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMS password used for connections created from this factory</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.ActiveMQPrefetchPolicy-types"><link-body>org.apache.activemq.ActiveMQPrefetchPolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0abced91-3871-49f6-a792-df8ee88c1031" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the <a
+href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch
+policy</a> for consumers created by this connection.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerWindowSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f5aa7ddb-0524-47e4-8856-c88631ffe7bd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> properties </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d6ad6973-bbc0-4a23-a5d6-781141de2ba0" ac:name="html" ac:schema-version="1"><plain-text-body>Get the properties from this instance for storing in JNDI</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> redeliveryPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.RedeliveryPolicy-types"><link-body>org.apache.activemq.RedeliveryPolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cba041ab-decf-42d4-b030-74daf45362c9" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the global redelivery policy to be used when a message is delivered
+but the session is rolled back</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statsEnabled </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2286dda0-f463-44b4-881f-1ac6c25160a2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> transformer </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.MessageTransformer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b4804a3d-cdc9-43a4-a950-4dc50f6ea8ed" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the transformer used to transform messages before they are sent on
to the JMS bus or when they are received from the bus but before they are
-delivered to the JMS client</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transportListener </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.TransportListener</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Allows a listener to be configured on the ConnectionFactory so that when this factory is used
+delivered to the JMS client</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> transportListener </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.TransportListener</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3378eeb0-2005-41bd-aaa5-e653b54a2f2a" ac:name="html" ac:schema-version="1"><plain-text-body>Allows a listener to be configured on the ConnectionFactory so that when this factory is used
with frameworks which don't expose the Connection such as Spring JmsTemplate, you can still register
-a transport listener.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useAsyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forces the use of <a shape="rect" href="http://activemq.apache.org/async-sends.html">Async Sends</a> which
+a transport listener.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useAsyncSend </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e636a288-0231-4434-805f-940fc130f8a9" ac:name="html" ac:schema-version="1"><plain-text-body>Forces the use of <a
+href="http://activemq.apache.org/async-sends.html">Async Sends</a> 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.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useBeanNameAsClientIdPrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useCompression </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables the use of compression of the message bodies</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useRetroactiveConsumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not retroactive consumers are enabled. Retroactive
+lead to message loss.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useBeanNameAsClientIdPrefix </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8623c624-f2f3-4e4b-a825-de470573c1b9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useCompression </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e8ca0beb-a800-4f54-96c6-a3a4e0627073" ac:name="html" ac:schema-version="1"><plain-text-body>Enables the use of compression of the message bodies</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useRetroactiveConsumer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4d6b0f95-80e1-4159-8e6a-c3024c5cd78d" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not retroactive consumers are enabled. Retroactive
consumers allow non-durable topic subscribers to receive old messages
-that were published before the non-durable subscriber started.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMS userName used by connections created by this factory</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> warnAboutUnstartedConnectionTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables the timeout from a connection creation to when a warning is
+that were published before the non-durable subscriber started.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e8b59b76-7f32-4dfd-bc10-d8452f891358" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMS userName used by connections created by this factory</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> warnAboutUnstartedConnectionTimeout </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f96a8a7e-5d8f-49c5-a4d5-0649ea36f4d6" ac:name="html" ac:schema-version="1"><plain-text-body>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 <a shape="rect" href="http://activemq.apache.org/i-am-not-receiving-any-messages-what-is-wrong.html">start
-the connection</a> so this option makes the default case to create a
+a very common gotcha to forget to <a
+href="http://activemq.apache.org/i-am-not-receiving-any-messages-what-is-wrong.html">start
+the connection</a> 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).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> watchTopicAdvisories </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+0 (say -1).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> watchTopicAdvisories </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b32ab277-da26-4cc5-9277-87d1003523e9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-constantPendingMessageLimitStrategy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<constantPendingMessageLimitStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-constantPendingMessageLimitStrategy-element"><constantPendingMessageLimitStrategy></a></em> Element</h3>
-<p> </p><p>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.16">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="72df986f-66c0-4db0-a3d6-82d9ecf193a3" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">constantPendingMessageLimitStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="constantPendingMessageLimitStrategy-element"><link-body><constantPendingMessageLimitStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="d0df7a5b-89f2-440c-a2c9-554cdd57d319" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> limit </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="057ecd3b-6885-4902-adc0-6f065ea6d48f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-db2JDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<db2JDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-db2JDBCAdapter-element"><db2JDBCAdapter></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.17">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="3290d425-0ef0-43aa-9dfa-332dc4fdb1ea" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">db2JDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="db2JDBCAdapter-element"><link-body><db2JDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="745ef506-5572-4fa6-ae40-e291d225b1eb" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="77ba9cbf-8728-4dfa-83df-be24d30bf003" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f36917d6-9669-47ad-ad40-2e8890978703" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1569eeb3-6796-4043-afcc-515ac3f3ebee" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-defaultJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<defaultJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-defaultJDBCAdapter-element"><defaultJDBCAdapter></a></em> Element</h3>
-<p> </p><p>Implements all the default JDBC operations that are used by the
-JDBCPersistenceAdapter. </p><p></p> sub-classing is encouraged to override the
+<p><structured-macro ac:macro-id="141def0f-17db-42d6-b970-2409a1c565e3" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">defaultJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="defaultJDBCAdapter-element"><link-body><defaultJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="8faab6dc-7a31-4193-96c7-12be14182c9e" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the
+JDBCPersistenceAdapter. <p/> sub-classing is encouraged to override the
default implementation of methods to account for differences in JDBC Driver
-implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using
-the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that
+implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using
+the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that
use this adapter are:
-<ul><li></li></ul><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.18">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e69de221-3022-4309-b3ac-f93cb25a9027" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8d09bfa7-218a-4204-9263-1a338e8aea8c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="855ac114-25b0-4ec2-8728-a337d5156c3e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-defaultUsageCapacity-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<defaultUsageCapacity>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-defaultUsageCapacity-element"><defaultUsageCapacity></a></em> Element</h3>
-<p> </p><p>Identify if a limit has been reached</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.19">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="812d1b3d-9325-4295-b661-051a2db4dc4c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">defaultUsageCapacity-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="defaultUsageCapacity-element"><link-body><defaultUsageCapacity></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="30f88070-11ac-490a-83ea-717f6a110b5d" ac:name="html" ac:schema-version="1"><plain-text-body>Identify if a limit has been reached</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> limit </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5be292b8-43d0-4e38-aee4-122b25c48531" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-demandForwardingBridge-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<demandForwardingBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-demandForwardingBridge-element"><demandForwardingBridge></a></em> Element</h3>
-<p> </p><p>Forwards messages from the local broker to the remote broker based on demand.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.20">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> configuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.NetworkBridgeConfiguration-types">org.apache.activemq.network.NetworkBridgeConfiguration</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createdByDuplex </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkBridgeListener </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.network.NetworkBridgeListener</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="2907ab88-7412-4a69-b5e4-f54aab577366" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">demandForwardingBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="demandForwardingBridge-element"><link-body><demandForwardingBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="2b117dc4-17d6-4c10-ab68-52c46c9fa9f8" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards messages from the local broker to the remote broker based on demand.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> configuration </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.NetworkBridgeConfiguration-types"><link-body>org.apache.activemq.network.NetworkBridgeConfiguration</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fe4d0a20-43be-4612-92bc-4690ff5ec163" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createdByDuplex </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7ea91fb8-58d2-4190-964d-7d0ce92a97be" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b1c0c042-d801-41e0-9eef-6158e6c54442" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c80a8f9-3eeb-4b72-8cb4-f67e2d95b10c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5829609b-1d4c-4a05-9290-c021d5f21e83" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1eb4419d-6426-48a0-96e6-c89b257ed207" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkBridgeListener </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.network.NetworkBridgeListener</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e4a7d558-1d65-427d-9b41-b778c30e1100" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e1404c08-fdd3-4d03-b635-20e605e0f11f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d78bacf2-d6f0-468a-982f-5bdfc8368999" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-destinationDotFilePlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<destinationDotFilePlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-destinationDotFilePlugin-element"><destinationDotFilePlugin></a></em> Element</h3>
-<p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a>
-file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.21">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> file </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination file name to create the destination diagram</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5144968c-9d5e-4331-8854-f75bf677f6d5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">destinationDotFilePlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="destinationDotFilePlugin-element"><link-body><destinationDotFilePlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="73ceec9b-27d7-416b-b806-e291ab4f12df" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a>
+file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> file </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4d6009f5-997b-4154-afc4-ce931eb43f15" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination file name to create the destination diagram</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-destinationEntry-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<destinationEntry>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-destinationEntry-element"><destinationEntry></a></em> Element</h3>
-<p> </p><p>A default entry in a DestinationMap which holds a single value.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.22">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> value </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.Object</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="e497ce38-7a2d-43f5-bf0c-d4f1ca255c4f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">destinationEntry-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="destinationEntry-element"><link-body><destinationEntry></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="09890032-58d5-417f-b360-750c346d48ed" ac:name="html" ac:schema-version="1"><plain-text-body>A default entry in a DestinationMap which holds a single value.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="376f7cf8-55a8-4ed2-9d3a-2042cf05ae3c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c551df7e-84d4-4162-8740-cb0f0eb76662" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topic </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="85c4b35b-a479-46f9-87ab-1db0bafbc075" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> value </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.Object</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e833fe4e-f670-4c1d-a149-eb44c3f1b3d1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-fileCursor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<fileCursor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-fileCursor-element"><fileCursor></a></em> Element</h3>
-<p> </p><p>Pending messages</p><p></p>
+<p><structured-macro ac:macro-id="e528c4e9-d34e-4509-86d3-16a3d99df4ff" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">fileCursor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="fileCursor-element"><link-body><fileCursor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9fc86d77-b049-45bf-9dd1-1bb807c47051" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-fileDurableSubscriberCursor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<fileDurableSubscriberCursor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-fileDurableSubscriberCursor-element"><fileDurableSubscriberCursor></a></em> Element</h3>
-<p> </p><p>Pending messages for durable subscribers</p><p></p>
+<p><structured-macro ac:macro-id="8743b491-0a91-4d84-b31c-36af3e62968b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">fileDurableSubscriberCursor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="fileDurableSubscriberCursor-element"><link-body><fileDurableSubscriberCursor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="24f55005-32ff-4640-b1da-9af5aca028b4" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages for durable subscribers</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-fileQueueCursor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<fileQueueCursor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-fileQueueCursor-element"><fileQueueCursor></a></em> Element</h3>
-<p> </p><p>Pending</p><p></p>
+<p><structured-macro ac:macro-id="3f498cca-7d45-4194-b9b5-dc72eea9420f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">fileQueueCursor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="fileQueueCursor-element"><link-body><fileQueueCursor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="c177145f-4e4e-4211-a50b-ecce2792cf15" ac:name="html" ac:schema-version="1"><plain-text-body>Pending</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-filteredDestination-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<filteredDestination>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-filteredDestination-element"><filteredDestination></a></em> Element</h3>
-<p> </p><p>Represents a destination which is filtered using some predicate such as a selector
-so that messages are only dispatched to the destination if they match the filter.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.23">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>The destination to send messages to if they match the filter</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> filter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.filter.BooleanExpression</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination property to the given queue name</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMS selector used to filter messages before forwarding them to this destination</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the destination property to the given topic name</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="07b368b5-ad78-418f-9afd-2a3cbb39eb10" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">filteredDestination-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="filteredDestination-element"><link-body><filteredDestination></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="462c0770-9703-4eeb-82a6-7a430ea5d09c" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination which is filtered using some predicate such as a selector
+so that messages are only dispatched to the destination if they match the filter.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d86ea2fe-e98e-4cf9-9780-2b3c565c0af3" ac:name="html" ac:schema-version="1"><plain-text-body>The destination to send messages to if they match the filter</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> filter </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.filter.BooleanExpression</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5465f156-21d3-4783-93be-0996f0bb87fc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="83eb9f7c-d576-41ff-93be-4451862dc1a6" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination property to the given queue name</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7962e42c-9460-4fb3-be6e-e78858a11ede" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMS selector used to filter messages before forwarding them to this destination</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topic </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2a1f068a-40da-40f4-9248-3381d6c5af5a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the destination property to the given topic name</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-fixedCountSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<fixedCountSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-fixedCountSubscriptionRecoveryPolicy-element"><fixedCountSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
-count of last messages.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.24">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the maximum number of messages that this destination will hold
-around in RAM</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="01f79da2-2722-496b-9e88-aa21647050bc" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">fixedCountSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="fixedCountSubscriptionRecoveryPolicy-element"><link-body><fixedCountSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f0c6dfdf-1d9e-4586-9c57-4980df5dcc65" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
+count of last messages.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> maximumSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b2d1c81b-c014-4b61-b165-6bad03d44396" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the maximum number of messages that this destination will hold
+around in RAM</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-fixedSizedSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<fixedSizedSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-fixedSizedSubscriptionRecoveryPolicy-element"><fixedSizedSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
+<p><structured-macro ac:macro-id="42b10667-cdd7-4c4b-87f7-a0ed9462c937" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">fixedSizedSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="fixedSizedSubscriptionRecoveryPolicy-element"><link-body><fixedSizedSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="941c59a6-9564-47f2-87cb-a8c097b41d50" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
amount of memory available in RAM for message history which is evicted in
-time order.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.25">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> buffer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.memory.list.MessageList</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the maximum amount of RAM in bytes that this buffer can hold in RAM</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useSharedBuffer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+time order.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> buffer </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.memory.list.MessageList</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="320dd002-7842-4b36-8849-62c21370ed8b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maximumSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0f406212-2abe-437e-abeb-7c9f122f4e4a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the maximum amount of RAM in bytes that this buffer can hold in RAM</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useSharedBuffer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b83edb42-4028-4dd9-aaf5-40dcaad7365f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-forwardingBridge-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<forwardingBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-forwardingBridge-element"><forwardingBridge></a></em> Element</h3>
-<p> </p><p>Forwards all messages from the local broker to the remote broker.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.26">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clientId </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkBridgeFailedListener </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.network.NetworkBridgeListener</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteBroker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5f64856c-513f-4e4b-a49f-f44bd3374b99" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">forwardingBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="forwardingBridge-element"><link-body><forwardingBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="741d2313-1787-4dc3-8408-8f27e9385b1d" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards all messages from the local broker to the remote broker.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> clientId </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="564fa3ad-ad61-40ed-9916-a6e2382b4439" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationFilter </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4eb1e55d-6c2b-4123-a9c7-a4b7bd782f64" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a44566f4-8e66-458a-98ca-e80e6b887283" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a3ab2a05-8b10-4032-849e-d283b94ed78a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkBridgeFailedListener </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.network.NetworkBridgeListener</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ee6598d5-b0b4-4eb1-98b2-68b874bf63fd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e88692ff-cafb-4466-9d59-5694f9813eef" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteBroker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bbdef11c-35e3-4cde-a1a1-4c3e4dcbcfa3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-imageBasedJDBCAdaptor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<imageBasedJDBCAdaptor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-imageBasedJDBCAdaptor-element"><imageBasedJDBCAdaptor></a></em> Element</h3>
-<p> </p><p>Provides JDBCAdapter since that uses
+<p><structured-macro ac:macro-id="cf43fb3e-e4e2-41a3-928c-c05cc1b26944" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">imageBasedJDBCAdaptor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="imageBasedJDBCAdaptor-element"><link-body><imageBasedJDBCAdaptor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9d0ea09f-8934-4e3a-b974-e4136bda18b7" ac:name="html" ac:schema-version="1"><plain-text-body>Provides JDBCAdapter since that uses
IMAGE datatype to hold binary data.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li>Sybase</li><li>MS SQL</li></ul><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.27">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<ul>
+<li>Sybase</li>
+<li>MS SQL</li>
+</ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f58ba116-b350-47a2-85e5-f892520d2983" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="20a2ffd5-2cf2-4eec-b27a-422d7a10bb54" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="15b2b8e2-2139-451a-be8f-8e365565f5a7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-inboundQueueBridge-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<inboundQueueBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-inboundQueueBridge-element"><inboundQueueBridge></a></em> Element</h3>
-<p> </p><p>Create an Inbound Queue Bridge</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.28">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Queue-types">javax.jms.Queue</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundQueueName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localQueueName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumRetries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the maximum number of retries if a send fails before closing the
-bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Queue-types">javax.jms.Queue</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="50819887-0f31-4036-bcba-0f16235d6940" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">inboundQueueBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="inboundQueueBridge-element"><link-body><inboundQueueBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="33eee706-2d22-4382-aa26-928be68b9a46" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Queue Bridge</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="63b1c6fc-dfd4-4517-a6fd-4a38a06fee8c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6c047f97-81c0-4e23-a6ad-98be463877a9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="13490db8-d3ce-4ce2-8b8a-82742fa3b1f6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5b7a556b-5e89-4763-b4b2-8ce216e9aa0e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundQueueName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d55b785a-183b-44e9-8fb4-cf7ffb0d47cf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsConnector </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f8781d23-7b40-4fa7-8e26-4d91f7dd8ad1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b2f29253-c403-4cc2-8cf0-f9323e4a9da6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localQueueName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ca3ec578-45bc-4a7a-9996-1ffc8b4c9752" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maximumRetries </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bf68443f-d5fe-4794-8f07-dc7f31665d3c" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the maximum number of retries if a send fails before closing the
+bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="77f26371-93f6-410a-9e32-d80319de3e12" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f7d00c59-00df-40c4-a701-6bfe38606de9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="34aae0bf-e000-4045-87e9-444c3e3fbbf2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-inboundTopicBridge-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<inboundTopicBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-inboundTopicBridge-element"><inboundTopicBridge></a></em> Element</h3>
-<p> </p><p>Create an Inbound Topic Bridge</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.29">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Topic-types">javax.jms.Topic</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundTopicName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localTopicName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumRetries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the maximum number of retries if a send fails before closing the
-bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Topic-types">javax.jms.Topic</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="f90d44cd-6146-4488-8b58-e09ec70cce9e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">inboundTopicBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="inboundTopicBridge-element"><link-body><inboundTopicBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="c53693ea-4581-4d4b-86e2-21d289de46b8" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Topic Bridge</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="de2cf793-f78e-45d0-bee4-2be7300a2434" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="99b8479d-6fae-4803-aa08-b5fe3dec4351" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6482c708-83ce-404c-8d03-ce2ec86b8122" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerTopic </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bcd1b851-d9e9-4cda-8e33-0cd720bf00ec" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="699ad37d-99b8-4b00-8f23-81d75bd5dc6c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundTopicName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ed07ba3d-f966-4cd4-8459-e01bfd5c5e2d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsConnector </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="056cd578-0f7f-4a22-9007-4cbeb76bf23b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="19855ed6-39e4-4936-be02-4ce3fbabd256" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localTopicName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3f396f93-4f2c-4c8e-bdae-f749cbc4a273" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maximumRetries </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1dd5e4f3-2f79-48d9-aa88-b605852e85ab" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the maximum number of retries if a send fails before closing the
+bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b19aeb05-ec5d-4c26-b9b2-a4d66329c2ce" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerTopic </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bc995a65-44fc-4a60-8717-8fe0a19f9332" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b7d8d963-65e2-4ee1-9207-61924b5133c4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-individualDeadLetterStrategy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<individualDeadLetterStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-individualDeadLetterStrategy-element"><individualDeadLetterStrategy></a></em> Element</h3>
-<p> </p><p>A {@link DeadLetterStrategy} where each destination has its own individual
-DLQ using the subject naming hierarchy.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.30">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> processExpired </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> processNonPersistent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queuePrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix to use for all dead letter queues for queue messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topicPrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix to use for all dead letter queues for topic messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useQueueForQueueMessages </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a queue or topic should be used for queue messages sent to a
-DLQ. The default is to use a Queue</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useQueueForTopicMessages </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a queue or topic should be used for topic messages sent to a
-DLQ. The default is to use a Queue</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="841166e6-1fc4-4db6-9434-8ac64718a547" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">individualDeadLetterStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="individualDeadLetterStrategy-element"><link-body><individualDeadLetterStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="92b4bbf6-e904-4373-b27a-2277b5d4e595" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link DeadLetterStrategy} where each destination has its own individual
+DLQ using the subject naming hierarchy.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> processExpired </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="844c980c-c9a7-4c50-b929-f4f455fa87df" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> processNonPersistent </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b492fa83-5f70-4946-828a-e35d36b1785c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queuePrefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3d774826-4d25-4b52-98f5-b9aa991a749c" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix to use for all dead letter queues for queue messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topicPrefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0a8b7873-c586-46c1-a38d-6aaff7071348" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix to use for all dead letter queues for topic messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useQueueForQueueMessages </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9668e0e0-00fe-46f9-9e55-61c1e776019c" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a queue or topic should be used for queue messages sent to a
+DLQ. The default is to use a Queue</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useQueueForTopicMessages </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="da7d4c2c-14d3-4c90-916b-900d49a96cfd" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a queue or topic should be used for topic messages sent to a
+DLQ. The default is to use a Queue</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-informixJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<informixJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-informixJDBCAdapter-element"><informixJDBCAdapter></a></em> Element</h3>
-<p> </p><p>JDBC Adapter for Informix database.
+<p><structured-macro ac:macro-id="790c4515-9c23-4a46-a181-4820b91aeb14" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">informixJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="informixJDBCAdapter-element"><link-body><informixJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="2802b2f2-3579-422b-956a-4cf6840d9109" ac:name="html" ac:schema-version="1"><plain-text-body>JDBC Adapter for Informix database.
Because Informix database restricts length of composite primary keys, length of
-<i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters.
-Therefore be sure not to use longer names for container name and subscription id than 150 characters.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.31">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters.
+Therefore be sure not to use longer names for container name and subscription id than 150 characters.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="14baabfc-c9dc-455d-8d4c-98fec82c3074" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e5634a03-7d32-49aa-a574-385c9804bee7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="660482f4-eba2-43c9-a64b-826490b89fe1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-jaasAuthenticationPlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<jaasAuthenticationPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-jaasAuthenticationPlugin-element"><jaasAuthenticationPlugin></a></em> Element</h3>
-<p> </p><p>Provides a JAAS based authentication plugin</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.32">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> configuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JAAS configuration domain name used</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoverLoginConfig </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables the auto-discovery of the login.config file for JAAS to initialize itself.
-This flag is enabled by default such that if the <b>java.security.auth.login.config</b> system property
-is not defined then it is set to the location of the <b>login.config</b> file on the classpath.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="1925936d-52b8-4a93-b867-449961cbec58" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jaasAuthenticationPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jaasAuthenticationPlugin-element"><link-body><jaasAuthenticationPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ab432ef1-0e39-4292-98bf-47c3d17a63da" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based authentication plugin</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> configuration </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0b8e2ced-eb1d-4360-ace5-af4fff0a9b0e" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JAAS configuration domain name used</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoverLoginConfig </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3537f45e-4eb2-4f03-98af-50bfb214a7c2" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables the auto-discovery of the login.config file for JAAS to initialize itself.
+This flag is enabled by default such that if the <b>java.security.auth.login.config</b> system property
+is not defined then it is set to the location of the <b>login.config</b> file on the classpath.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-jaasCertificateAuthenticationPlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<jaasCertificateAuthenticationPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-jaasCertificateAuthenticationPlugin-element"><jaasCertificateAuthenticationPlugin></a></em> Element</h3>
-<p> </p><p>Provides a JAAS based SSL certificate authentication plugin</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.33">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> configuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JAAS configuration domain name used</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoverLoginConfig </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables the auto-discovery of the login.config file for JAAS to initialize itself.
-This flag is enabled by default such that if the <b>java.security.auth.login.config</b> system property
-is not defined then it is set to the location of the <b>login.config</b> file on the classpath.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="7659e097-20c5-4b6c-985b-b1f508a0f8f2" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jaasCertificateAuthenticationPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jaasCertificateAuthenticationPlugin-element"><link-body><jaasCertificateAuthenticationPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f8115f5a-1c5b-4fa8-935e-fd89cc1e85a8" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based SSL certificate authentication plugin</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> configuration </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="988961d8-0c75-43c5-8113-dd13e06f7618" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JAAS configuration domain name used</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoverLoginConfig </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="43ccde5c-7fdd-4cf2-b359-1ae0253d9339" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables the auto-discovery of the login.config file for JAAS to initialize itself.
+This flag is enabled by default such that if the <b>java.security.auth.login.config</b> system property
+is not defined then it is set to the location of the <b>login.config</b> file on the classpath.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-jdbcPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<jdbcPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-jdbcPersistenceAdapter-element"><jdbcPersistenceAdapter></a></em> Element</h3>
-<p> </p><p>A {@link PersistenceAdapter} implementation using JDBC for persistence
+<p><structured-macro ac:macro-id="59513225-ab41-4e32-9ba1-934d5283f26e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jdbcPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jdbcPersistenceAdapter-element"><link-body><jdbcPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9c347053-89ad-479b-8bb0-451bd06d2ba8" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link PersistenceAdapter} implementation using JDBC for persistence
storage.
This persistence adapter will correctly remember prepared XA transactions,
but it will not keep track of local transaction commits so that operations
-performed against the Message store are done as a single uow.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.34">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.JDBCAdapter-types">org.apache.activemq.store.jdbc.JDBCAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> cleanupPeriod </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the number of milliseconds until the database is attempted to be
-cleaned up for durable topics</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createTablesOnStartup </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not tables are created on startup</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataSource </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> databaseLocker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.store.jdbc.DatabaseLocker</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the database locker strategy to use to lock the database on startup</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> directory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ds </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> scheduledThreadPoolExecutor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.concurrent.ScheduledThreadPoolExecutor</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useDatabaseLock </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not an exclusive database lock should be used to enable
-JDBC Master/Slave. Enabled by default.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.wireformat.WireFormat</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+performed against the Message store are done as a single uow.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5a68c942-2bf0-4595-ab7c-7c26e7ecfd0f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="be457232-f072-4b0c-80ec-837f0572a64e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d447402e-cd13-494b-a8d7-2ed5b22074a4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> cleanupPeriod </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8f84c381-5343-4fba-bb47-7e18aa47258e" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the number of milliseconds until the database is attempted to be
+cleaned up for durable topics</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createTablesOnStartup </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="24ff7658-805c-49cd-b87b-e7193894a7d4" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not tables are created on startup</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8cf469ca-fad7-4678-a874-aa96d2bea1c2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cf2e6c4f-9098-4764-b562-d595fe6ad64f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataSource </p></td><td colspan="1" rowspan="1"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bce8f4b3-66a0-4681-9b08-6c49fc653c45" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> databaseLocker </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.store.jdbc.DatabaseLocker</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2bed46d3-eb57-4808-93c8-9cc16ceecda6" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the database locker strategy to use to lock the database on startup</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> directory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="40b78bf7-37df-4b0c-8cca-14a73d5767f8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> ds </p></td><td colspan="1" rowspan="1"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7a814a99-edfc-45cf-9001-75e237623933" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> scheduledThreadPoolExecutor </p></td><td colspan="1" rowspan="1"><p> <em>java.util.concurrent.ScheduledThreadPoolExecutor</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3635ccb8-f202-48c9-8cf2-e9c7e1e8741e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f515c0c3-6e8e-413f-a58a-7b15dd677950" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1186c3b3-c2bc-44e0-915b-0f14c49d4939" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useDatabaseLock </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bba95c4b-7e42-4461-b721-4e8ab42575aa" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not an exclusive database lock should be used to enable
+JDBC Master/Slave. Enabled by default.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2134a382-1f4b-4e91-96b9-e75433526768" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.wireformat.WireFormat</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d24bb7c0-92d4-4eb5-8736-cc0edf2f456a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-jmsQueueConnector-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<jmsQueueConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-jmsQueueConnector-element"><jmsQueueConnector></a></em> Element</h3>
-<p> </p><p>A Bridge to other JMS Queue providers</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.35">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>One way to configure the local connection - this is called by The
-BrokerService when the Connector is embedded</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundQueueBridges </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.InboundQueueBridge-types">org.apache.activemq.network.jms.InboundQueueBridge</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jndiLocalTemplate </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jndiOutboundTemplate </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localConnectionFactoryName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localQueueConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localQueueConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.QueueConnectionFactory-types">javax.jms.QueueConnectionFactory</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueBridges </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.OutboundQueueBridge-types">org.apache.activemq.network.jms.OutboundQueueBridge</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.QueueConnectionFactory-types">javax.jms.QueueConnectionFactory</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueConnectionFactoryName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> replyToDestinationCacheSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="28964167-afd3-450d-b82f-f7bc9a7f7cb4" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jmsQueueConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jmsQueueConnector-element"><link-body><jmsQueueConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5261d64e-d7ca-4154-bc3f-3833750dd147" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Queue providers</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4c971d40-5ebc-4326-9eef-40e81125ba81" ac:name="html" ac:schema-version="1"><plain-text-body>One way to configure the local connection - this is called by The
+BrokerService when the Connector is embedded</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b7df6e93-2a9e-4c99-a7c7-4db97844cef4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundQueueBridges </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.InboundQueueBridge-types"><link-body>org.apache.activemq.network.jms.InboundQueueBridge</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bb6cd56d-8daf-43ee-8e2b-2963c7f7aa99" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jndiLocalTemplate </p></td><td colspan="1" rowspan="1"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bb26b096-6bf4-42c5-b24f-a31908c0ab52" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jndiOutboundTemplate </p></td><td colspan="1" rowspan="1"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d98d6367-1230-48b8-871c-a059df90bb74" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localConnectionFactoryName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="abcd035a-d0d2-459a-a63a-966864a16c7b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e68d6187-674c-42f9-8ade-778aede8d02c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localQueueConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fef54021-8045-454d-93d8-56f69654b7df" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localQueueConnectionFactory </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.QueueConnectionFactory-types"><link-body>javax.jms.QueueConnectionFactory</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3239505e-6b58-4e40-9584-fdfee8f8f8e4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bf2c95da-d2b1-41b0-9804-8e5c9e0e5e77" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6b32c9e7-99a6-4e1a-97a9-fcf50da5040b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0a6c863c-d3e6-4c16-9b5d-6e0541d45924" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7aa68e33-345b-4d6d-9ff5-d4c4c1c5adbc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueBridges </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.OutboundQueueBridge-types"><link-body>org.apache.activemq.network.jms.OutboundQueueBridge</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f44b1c4a-0cfd-4f70-a750-948cb559346a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="21e9db14-a7b6-4ad1-82bd-fa2ee0156ba2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueConnectionFactory </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.QueueConnectionFactory-types"><link-body>javax.jms.QueueConnectionFactory</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bcd1004a-0c67-49d0-8427-ecaf28ce009c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueConnectionFactoryName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="700f3a51-022e-4ff9-a659-fd44688da520" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8f56aa6e-7716-4def-b29c-a0b57aa2478a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> replyToDestinationCacheSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ce1b18d7-b0fe-4d06-94af-a7d694a96058" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-jmsTopicConnector-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<jmsTopicConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-jmsTopicConnector-element"><jmsTopicConnector></a></em> Element</h3>
-<p> </p><p>A Bridge to other JMS Topic providers</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.36">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>One way to configure the local connection - this is called by The
-BrokerService when the Connector is embedded</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inboundTopicBridges </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.InboundTopicBridge-types">org.apache.activemq.network.jms.InboundTopicBridge</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jndiLocalTemplate </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jndiOutboundTemplate </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localConnectionFactoryName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localTopicConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localTopicConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.TopicConnectionFactory-types">javax.jms.TopicConnectionFactory</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicBridges </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.OutboundTopicBridge-types">org.apache.activemq.network.jms.OutboundTopicBridge</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicConnectionFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.TopicConnectionFactory-types">javax.jms.TopicConnectionFactory</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicConnectionFactoryName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> replyToDestinationCacheSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="fec7da2a-f7c1-47fc-bcf4-cd14d7f6309e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">jmsTopicConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="jmsTopicConnector-element"><link-body><jmsTopicConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="0e9078ff-a218-4cd7-9ae0-eac32567ac38" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Topic providers</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d119f625-ff37-41b0-b82a-2e8c02bd13a2" ac:name="html" ac:schema-version="1"><plain-text-body>One way to configure the local connection - this is called by The
+BrokerService when the Connector is embedded</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f5f5e8a8-c7a0-47f7-8608-e17b54d171f4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inboundTopicBridges </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.InboundTopicBridge-types"><link-body>org.apache.activemq.network.jms.InboundTopicBridge</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="31e699b9-46a0-4ec9-85c9-acf0de33da28" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jndiLocalTemplate </p></td><td colspan="1" rowspan="1"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dda8cb4b-d01c-4fd3-a4d2-5e9d6a886142" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jndiOutboundTemplate </p></td><td colspan="1" rowspan="1"><p> <em>org.springframework.jndi.JndiTemplate</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8475c40b-9721-4e68-a154-bb09f8b11e33" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localConnectionFactoryName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2a5e6ff0-6fff-4d80-b765-ad89b708523d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0d58681d-b014-4c27-a986-a45bddfa9094" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localTopicConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="413fe000-9b85-43ff-b528-f4aa8d8eb9ae" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localTopicConnectionFactory </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.TopicConnectionFactory-types"><link-body>javax.jms.TopicConnectionFactory</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="01ac264d-25aa-40cb-a4dd-be2a2a6ef213" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ade8b126-81d8-4602-b813-60848e6d46e1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2ecf913c-a9a8-4d41-b122-dc9747a70dfa" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="505f5b36-c80f-4973-98c8-54b5544916a2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a510a8e1-3142-445b-ac74-dbeb7fcb27a1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicBridges </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.network.jms.OutboundTopicBridge-types"><link-body>org.apache.activemq.network.jms.OutboundTopicBridge</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="44f6a46f-53da-448c-bfe9-55eea06e00de" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="64ff2c48-0723-4936-9ec8-d7d5e84a62c2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicConnectionFactory </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.TopicConnectionFactory-types"><link-body>javax.jms.TopicConnectionFactory</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="56367555-a508-43d7-8205-c0e339bb2921" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicConnectionFactoryName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d4b7b7dc-a3be-47bc-9c59-94a87f49e2bf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d18b05b8-d698-496c-9a0d-a3980d09a8a3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> replyToDestinationCacheSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bfdbaab8-0faf-4e78-bab2-9192a1d4d5b8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-journalPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<journalPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-journalPersistenceAdapter-element"><journalPersistenceAdapter></a></em> Element</h3>
-<p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a
+<p><structured-macro ac:macro-id="825a4ea1-2dbf-4a2a-994a-200e9fec98dd" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">journalPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="journalPersistenceAdapter-element"><link-body><journalPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5959b4ff-f4dd-4947-8558-2451d7b45c5d" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a
{@link Journal} and then check pointing asynchronously on a timeout with some
-other long term persistent storage.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.37">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> directory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> longTermPersistence </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxCheckpointWorkers </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+other long term persistent storage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f0f028e1-59a2-4410-8c0c-a14f7556bf3f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> directory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="633ca125-7e60-4dd3-a63f-38fc0ddfc95e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journal </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d71ebd29-9f81-42bd-a6e8-1c7f448c665f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> longTermPersistence </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="24f157f4-1520-4a9d-84c9-53570a751469" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointMessageAddSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="89f3f93b-27bb-4f54-adaf-28a4ef75ca15" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxCheckpointWorkers </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c8f18102-ed3d-4743-891d-0e3e6b419588" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9a594df3-5ba6-4e75-b5dd-50319e25ce28" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="baae5998-3c90-45a5-ac0e-6374b27dcb22" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7206afcf-1f97-4332-a2bc-4b99119d0ad9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-journaledJDBC-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<journaledJDBC>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-journaledJDBC-element"><journaledJDBC></a></em> Element</h3>
-<p> </p><p>Creates a default persistence model using the Journal and JDBC</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.38">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.JDBCAdapter-types">org.apache.activemq.store.jdbc.JDBCAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createTablesOnStartup </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not tables are created on startup</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dataSource </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jdbcAdapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types">org.apache.activemq.store.jdbc.JDBCPersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journalArchiveDirectory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journalLogFileSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the size of the journal log files</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journalLogFiles </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the number of journal log files to use</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> journalThreadPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the thread priority of the journal thread</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useDatabaseLock </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not an exclusive database lock should be used to enable
-JDBC Master/Slave. Enabled by default.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useJournal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables the use of the journal. The default is to use the
-journal</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useQuickJournal </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables the use of quick journal, which keeps messages in the
+<p><structured-macro ac:macro-id="cbd40128-edbf-469a-a78c-f1434d3c547c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">journaledJDBC-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="journaledJDBC-element"><link-body><journaledJDBC></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9f1a65a6-8e0e-43a3-a0bd-e7ac8687c3de" ac:name="html" ac:schema-version="1"><plain-text-body>Creates a default persistence model using the Journal and JDBC</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8b68f530-e7f3-46e2-9015-341be4dd082b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createTablesOnStartup </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ccc592d0-04dd-4f59-9d95-1e014aac3826" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not tables are created on startup</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="135967ce-ddde-4278-9ba8-9d075a764121" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataDirectoryFile </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="419cadee-f1fd-4ee4-a30c-953bdc268125" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dataSource </p></td><td colspan="1" rowspan="1"><p> <em>javax.sql.DataSource</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="44f85b73-facb-4cc9-bdbe-9b3f18404e1d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jdbcAdapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.JDBCPersistenceAdapter-types"><link-body>org.apache.activemq.store.jdbc.JDBCPersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="829c1d08-5825-4bf9-8cf4-4526fe8374e5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journal </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activeio.journal.Journal</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="74143e13-b1ce-4057-a237-e636002c5035" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journalArchiveDirectory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2192b9e5-135a-447c-b595-cc097baba82f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journalLogFileSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9423fc94-5169-45a2-b821-bbdfab7bdd62" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the size of the journal log files</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journalLogFiles </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cd348b77-e8a5-4355-a53e-ed7ef93ff6af" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the number of journal log files to use</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> journalThreadPriority </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e5fe17eb-1cb0-487f-9b26-cd9938728b3b" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the thread priority of the journal thread</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6a4868bb-fa82-4bac-9bc5-42af2d5dc454" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="92c49383-2518-4f1b-a9da-2cda31a0ee1b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useDatabaseLock </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="62b1e3f6-75db-4dff-9dfe-0ad9c4edf247" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not an exclusive database lock should be used to enable
+JDBC Master/Slave. Enabled by default.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useJournal </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2a1c403a-1f2d-43dc-9d66-0875fe686298" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables the use of the journal. The default is to use the
+journal</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useQuickJournal </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f77cb028-3700-49c1-bf47-b1231f0495c2" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables the use of quick journal, which keeps messages in the
journal and just stores a reference to the messages in JDBC. Defaults to
-false so that messages actually reside long term in the JDBC database.</p> <p></p></td></tr></tbody></table></div>
+false so that messages actually reside long term in the JDBC database.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-kahaPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<kahaPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-kahaPersistenceAdapter-element"><kahaPersistenceAdapter></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.39">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> directory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxDataFileLength </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> persistentIndex </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> size </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.concurrent.atomic.AtomicLong</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="0c0a3ac5-0f1c-4442-998f-9d58c7cd26f7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">kahaPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="kahaPersistenceAdapter-element"><link-body><kahaPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="b58e9e97-a2ca-48d0-bcf0-6754eb4add69" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5c710505-d003-476f-9143-6c8ff3188d27" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> directory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="35cc42a3-4ade-46ad-bb03-c1dd4e999a48" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxDataFileLength </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cf29ebd9-981e-45b0-86db-48e720af8aa8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> persistentIndex </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="97db50e4-5d4c-47ec-b3cf-89b39d7f94b3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> size </p></td><td colspan="1" rowspan="1"><p> <em>java.util.concurrent.atomic.AtomicLong</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e7f40176-2011-4a8e-b7b6-428a1b1025e1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="19fc4914-33a5-4ecb-9350-1d5dcb9ebdcc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-lDAPAuthorizationMap-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<lDAPAuthorizationMap>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-lDAPAuthorizationMap-element"><lDAPAuthorizationMap></a></em> Element</h3>
-<p> </p><p>An {@link AuthorizationMap} which uses LDAP</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.40">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminAttribute </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminBase </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> authentication </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionPassword </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionProtocol </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionURL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionUsername </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> context </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.naming.directory.DirContext</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> initialContextFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> options </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queueSearchMatchingFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.text.MessageFormat</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queueSearchSubtreeBool </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> readAttribute </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> readBase </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topicSearchMatchingFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.text.MessageFormat</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topicSearchSubtreeBool </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> writeAttribute </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> writeBase </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a01cb087-00eb-4e9e-b4dd-23eb9dfaa9dd" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">lDAPAuthorizationMap-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="lDAPAuthorizationMap-element"><link-body><lDAPAuthorizationMap></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="e9e65651-c6c9-40e1-96c5-96361e915bea" ac:name="html" ac:schema-version="1"><plain-text-body>An {@link AuthorizationMap} which uses LDAP</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adminAttribute </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="98cb3905-2433-4c81-b2f2-a16df2175a67" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> adminBase </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="38345ac9-7908-4903-8a4c-46d9392561ea" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> authentication </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bece64a5-0bc8-4d03-98e2-98eceb112fe9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionPassword </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a45b2bec-15ad-48b8-a9ab-ec6e47dae226" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionProtocol </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a30b2364-c5ee-4b7d-ba08-58aca0e50bce" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionURL </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="79e3f59a-f616-4dc5-b8ac-718be0c236bd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionUsername </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c1aff00b-033f-4245-beef-ebbdf20abecc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> context </p></td><td colspan="1" rowspan="1"><p> <em>javax.naming.directory.DirContext</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="36acd484-c25b-4517-8f90-e37d82706c86" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> initialContextFactory </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5498a2b8-ae6b-484c-9f98-c442ac30a912" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> options </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f61d5210-5b4a-42b2-af76-dcfcb566cd6d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queueSearchMatchingFormat </p></td><td colspan="1" rowspan="1"><p> <em>java.text.MessageFormat</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="67abee7c-7f0c-48f3-bbff-2a634f65ee7e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queueSearchSubtreeBool </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6942420e-f4b2-4d77-aaff-b1851413f4c7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> readAttribute </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dd7be830-45ac-4114-852a-b3975243f196" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> readBase </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a21c7fc0-fd1d-4f8b-957b-51109a3f3f26" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topicSearchMatchingFormat </p></td><td colspan="1" rowspan="1"><p> <em>java.text.MessageFormat</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="63448cf0-9880-4e44-8552-14b6a55fa3ea" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topicSearchSubtreeBool </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b52a37f4-5f2a-48b8-838f-9544dc44baca" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> writeAttribute </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6609983b-ab0b-4cf6-a8a3-08a48a7bf141" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> writeBase </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1a9aa2d8-4c86-4544-bfeb-06197b479bb9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-lastImageSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<lastImageSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-lastImageSubscriptionRecoveryPolicy-element"><lastImageSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the
-last message.</p><p></p>
+<p><structured-macro ac:macro-id="8e5805f0-e5b6-46ac-940b-10fcbf79059b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">lastImageSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="lastImageSubscriptionRecoveryPolicy-element"><link-body><lastImageSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="81fd3663-35f3-415f-aa85-ea279f3fee42" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the
+last message.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-ldapNetworkConnector-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<ldapNetworkConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-ldapNetworkConnector-element"><ldapNetworkConnector></a></em> Element</h3>
-<p> </p><p>class to create dynamic network connectors listed in an directory
+<p><structured-macro ac:macro-id="3288537f-9cf9-4fb6-87a3-b5f834ee2fd1" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">ldapNetworkConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="ldapNetworkConnector-element"><link-body><ldapNetworkConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="8f6e96ca-7429-4e8d-a1c3-549718004090" ac:name="html" ac:schema-version="1"><plain-text-body>class to create dynamic network connectors listed in an directory
server using the LDAP v3 protocol as defined in RFC 2251, the
entries listed in the directory server must implement the ipHost
-and ipService objectClasses as defined in RFC 2307.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.41">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> base </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>sets the base LDAP dn used for lookup operations</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> bridgeTempDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> duplex </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkTTL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> objectName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>sets the LDAP password for access credentials</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> searchFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>sets the LDAP search filter as defined in RFC 2254</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> searchScope </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>sets the LDAP search scope</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> uri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>sets the LDAP server URI</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> user </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>sets the LDAP user for access credentials</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+and ipService objectClasses as defined in RFC 2307.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> base </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="57ed437c-1d99-4572-bdfd-ad494f837a5f" ac:name="html" ac:schema-version="1"><plain-text-body>sets the base LDAP dn used for lookup operations</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> bridgeTempDestinations </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="22ceef44-743c-4e52-be0c-59148dc893f6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="090f5a6a-9a31-423a-abbf-27240f2b41ac" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="14dfd993-dfea-4e06-a579-11376519abc7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b15fd09a-e0f1-4254-8040-f180696f61c3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionFilter </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6775a2ac-0f07-4da9-9578-089fdeb44b08" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8828f3ed-c79b-4be4-83c0-3eadc84b98fa" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationFilter </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2ccf216f-3430-483f-8365-46ca6e6d0b2a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="148dab09-acd1-4ffb-a48a-cee31fa77e94" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> duplex </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="824775c2-212a-4cfa-9318-1d1a59fd5dd6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4b3bde17-f4d3-4a65-83f3-6b9d3bd9d230" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="452361ce-4009-4c93-9546-37e6452f8cad" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e4becbf9-3df2-4086-b164-6b51440ef27a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b7dd6abf-5f04-40a2-a0d9-beddbdef617c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b8969bbe-29d5-47cf-a3c1-11b5ce1d824a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="63271c64-3277-4983-b7ba-cc7a15a81346" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkTTL </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="93ef1d0d-4475-4d83-9cc3-98c8302e2817" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> objectName </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="31f709bb-84c5-4bd0-bfbd-bfbd4187c97e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d1ecefa8-67c0-4932-9865-79895dc09ae1" ac:name="html" ac:schema-version="1"><plain-text-body>sets the LDAP password for access credentials</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="31face86-66dd-4fc2-bea9-c78b3e62bcf1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> searchFilter </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9bc3eaac-2c60-402c-88a3-1c4fb10408f3" ac:name="html" ac:schema-version="1"><plain-text-body>sets the LDAP search filter as defined in RFC 2254</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> searchScope </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8335bee0-dd56-4b0c-bf33-72055b7711eb" ac:name="html" ac:schema-version="1"><plain-text-body>sets the LDAP search scope</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cc07b133-70ed-43ca-b1af-39ae7bf771b6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> uri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="16bf8524-9f68-4059-b21b-d811b17e2f28" ac:name="html" ac:schema-version="1"><plain-text-body>sets the LDAP server URI</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> user </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="be2fa359-104c-4fb1-8e6c-113c1ce40b60" ac:name="html" ac:schema-version="1"><plain-text-body>sets the LDAP user for access credentials</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="945e758e-ac2a-4eb2-bd46-47d6e69a47b7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-loggingBrokerPlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<loggingBrokerPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-loggingBrokerPlugin-element"><loggingBrokerPlugin></a></em> Element</h3>
-<p> </p><p>A simple Broker interceptor which allows you to enable/disable logging.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.42">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> ackLog </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> log </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> next </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.Broker-types">org.apache.activemq.broker.Broker</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> sendLog </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="2b1a00ae-8c54-468d-95b3-846e5e8adccb" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">loggingBrokerPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="loggingBrokerPlugin-element"><link-body><loggingBrokerPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="3cff091d-61d1-4b8b-8768-71d1730c9121" ac:name="html" ac:schema-version="1"><plain-text-body>A simple Broker interceptor which allows you to enable/disable logging.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> ackLog </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c0bc5e23-aa74-4d98-8a60-803ab03c43a2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="97573867-8f60-43df-8b21-8b65e16d34ed" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> log </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="77c32759-f28b-47cf-b502-93817cd6c322" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> next </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.Broker-types"><link-body>org.apache.activemq.broker.Broker</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e4f8e064-991a-43b3-a5ba-74462add2b6c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> sendLog </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.commons.logging.Log</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="96a5c669-047d-459d-a8f8-0fa82ff878bf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-managementContext-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<managementContext>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-managementContext-element"><managementContext></a></em> Element</h3>
-<p> </p><p>A Flow provides different dispatch policies within the NMR</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.43">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> MBeanServer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.MBeanServer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Get the MBeanServer</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectorPath </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectorPort </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createMBeanServer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findTigerMbeanServer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables/disables the searching for the Java 5 platform MBeanServer</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmxDomainName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> rmiServerPort </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> server </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.MBeanServer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useMBeanServer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="b36323dd-b211-4c0e-9dea-367abcff454f" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">managementContext-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="managementContext-element"><link-body><managementContext></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9de3ab2a-dbe9-4ac7-8f5f-4e4dddebcadd" ac:name="html" ac:schema-version="1"><plain-text-body>A Flow provides different dispatch policies within the NMR</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> MBeanServer </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.MBeanServer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="37edeec5-a32a-4ad2-8bc1-6c750a33f855" ac:name="html" ac:schema-version="1"><plain-text-body>Get the MBeanServer</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectorPath </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d279fd0c-a694-4f5a-a7d4-3db2fd2c2035" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectorPort </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1121c6d9-d7b0-4d7f-b72b-6a92420097b2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createConnector </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="955b8212-69cc-4757-b684-b2449902a7f7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createMBeanServer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3916e642-8dac-4331-b2cd-de863baf0acf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findTigerMbeanServer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b5a8a439-e516-4474-a2f3-216c1b0e04e5" ac:name="html" ac:schema-version="1"><plain-text-body>Enables/disables the searching for the Java 5 platform MBeanServer</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmxDomainName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a6dbfdcf-2516-4a35-b522-a8bf0d90ea09" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> rmiServerPort </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="084ddd05-d231-4a70-9f22-974e07471992" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> server </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.MBeanServer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7a99b9d0-1c2a-4108-ad10-45e84af8e0d6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useMBeanServer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="01f46e37-ce3f-466d-a063-25c36da47e58" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-masterConnector-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<masterConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-masterConnector-element"><masterConnector></a></em> Element</h3>
-<p> </p><p>Connects a Slave Broker to a Master when using <a shape="rect" href="http://activemq.apache.org/masterslave.html">Master Slave</a> for High
-Availability of messages.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.44">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="d7fcee29-f213-49c1-9ec0-6640a720a1d2" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">masterConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="masterConnector-element"><link-body><masterConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="0d9e53db-bb3a-47bd-b672-4bcae8ed0426" ac:name="html" ac:schema-version="1"><plain-text-body>Connects a Slave Broker to a Master when using <a
+href="http://activemq.apache.org/masterslave.html">Master Slave</a> for High
+Availability of messages.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="eda683f5-c89e-4770-9fb4-db7dc82ada0e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localURI </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bc792041-cab7-4ce6-822f-617c42d91298" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="403242be-34ee-46c4-ab72-d246c065d667" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteURI </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5ebeb697-6a23-43e5-9b71-d6a02c91ded1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteUri </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="89a74cb5-d9e8-4eb6-9e68-5a90fbe6dfc7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ba78674b-3db5-40f5-b2b2-07ab4a4e7321" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-memoryPersistenceAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<memoryPersistenceAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-memoryPersistenceAdapter-element"><memoryPersistenceAdapter></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.45">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> directory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usageManager </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="917b4da2-984e-4c36-a59e-482f04b9bab7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">memoryPersistenceAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="memoryPersistenceAdapter-element"><link-body><memoryPersistenceAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ff5c0321-7935-4fb7-9137-3c681d7340d7" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="288436f4-5a02-46e3-a118-a806d361acec" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> directory </p></td><td colspan="1" rowspan="1"><p> <em>java.io.File</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5091ee31-ef5a-402f-95a8-253df4e30b39" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usageManager </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f4b85543-6039-431c-a473-e27c20d9ddfa" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="88f29c40-d95c-416c-bcec-04a843354dc7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-memoryUsage-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<memoryUsage>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-memoryUsage-element"><memoryUsage></a></em> Element</h3>
-<p> </p><p>Used to keep track of how much of something is being used so that a
+<p><structured-macro ac:macro-id="0307876c-ca5d-47b3-a133-25501d7109df" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">memoryUsage-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="memoryUsage-element"><link-body><memoryUsage></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="e42eb276-1025-46f5-b411-64dc7cbb16f0" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.46">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the memory limit in bytes. Setting the limit in bytes will set the
+memory usage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> limit </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b4b7d1bb-65cd-4f8e-a6ee-5619cde41a08" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the memory limit in bytes. Setting the limit in bytes will set the
usagePortion to 0 since the UsageManager is not going to be portion based
off the parent. When set using XBean, you can use values such as: "20
-mb", "1024 kb", or "1 gb"</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limiter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.UsageCapacity-types">org.apache.activemq.usage.UsageCapacity</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> parent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>T</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> percentUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> percentUsageMinDelta </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the minimum number of percentage points the usage has to change
-before a UsageListener event is fired by the manager.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> pollingTime </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> portion </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>float</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usagePortion </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>float</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+mb", "1024 kb", or "1 gb"</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> limiter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.UsageCapacity-types"><link-body>org.apache.activemq.usage.UsageCapacity</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c6bdb80f-22cb-4f5b-b8e9-8877db04535f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b1fec399-24b1-4bcb-b3ff-20c2d6da8ed2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> parent </p></td><td colspan="1" rowspan="1"><p> <em>T</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a1448843-6cca-41b8-969a-e3a73562334c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> percentUsage </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dc10971c-d2c4-4e24-a308-05591b2f7de0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> percentUsageMinDelta </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="35de8740-af0d-4b7a-aa0e-407defb0dddb" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the minimum number of percentage points the usage has to change
+before a UsageListener event is fired by the manager.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> pollingTime </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="be4e8dbb-d6b6-413f-b7a4-3067621de446" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> portion </p></td><td colspan="1" rowspan="1"><p> <em>float</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b699f1a1-b3a3-4629-9008-c4bfac7245ad" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usage </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b24a9d8a-4953-401f-9d09-71921ac83d7a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usagePortion </p></td><td colspan="1" rowspan="1"><p> <em>float</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="26edafe8-f952-4386-a394-b59aa48299d2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-messageGroupHashBucketFactory-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<messageGroupHashBucketFactory>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-messageGroupHashBucketFactory-element"><messageGroupHashBucketFactory></a></em> Element</h3>
-<p> </p><p>A factory to create instances of {@link SimpleMessageGroupMap} when
-implementing the <a shape="rect" href="http://activemq.apache.org/message-groups.html">Message
-Groups</a> functionality.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.47">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> bucketCount </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the number of hash buckets to use for the message group
+<p><structured-macro ac:macro-id="c08cc3bb-3ac1-4f03-b86b-ec853d1d181d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">messageGroupHashBucketFactory-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="messageGroupHashBucketFactory-element"><link-body><messageGroupHashBucketFactory></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="68e48994-15a0-454e-bfc4-b227b9487fe3" ac:name="html" ac:schema-version="1"><plain-text-body>A factory to create instances of {@link SimpleMessageGroupMap} when
+implementing the <a
+href="http://activemq.apache.org/message-groups.html">Message
+Groups</a> functionality.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> bucketCount </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a4b4f191-5221-4202-b23a-37bb1e5bbd62" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the number of hash buckets to use for the message group
functionality. This is only applicable to using message groups to
parallelize processing of a queue while preserving order across an
individual JMSXGroupID header value. This value sets the number of hash
-buckets that will be used (i.e. the maximum possible concurrency).</p> <p></p></td></tr></tbody></table></div>
+buckets that will be used (i.e. the maximum possible concurrency).</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-mirroredQueue-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<mirroredQueue>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-mirroredQueue-element"><mirroredQueue></a></em> Element</h3>
-<p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/mirrored-queues.html">Mirrored
-Queue</a> using a prefix and postfix to define the topic name on which to mirror the queue to.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.48">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> copyMessage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether a copy of the message will be sent to each destination.
+<p><structured-macro ac:macro-id="9dba8656-1dc5-43b4-a434-f26317b7df5e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">mirroredQueue-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="mirroredQueue-element"><link-body><mirroredQueue></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="716fe28f-666b-4c9d-aaa1-5a79b8b9b0c9" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/mirrored-queues.html">Mirrored
+Queue</a> using a prefix and postfix to define the topic name on which to mirror the queue to.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c74be58-40f4-42d0-843f-9cb291d45b46" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> copyMessage </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8a477685-b3df-47c4-b979-d35df743586a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether a copy of the message will be sent to each destination.
Defaults to true so that the forward destination is set as the
-destination of the message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> postfix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets any postix used to identify the queue consumers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix wildcard used to identify the queue consumers for a given
-topic</p> <p></p></td></tr></tbody></table></div>
+destination of the message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> postfix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="775bbf17-26be-426c-a687-88525cc33a45" ac:name="html" ac:schema-version="1"><plain-text-body>Sets any postix used to identify the queue consumers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d471426d-24f9-4e30-ab90-d798a7bd2a5a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix wildcard used to identify the queue consumers for a given
+topic</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-multicastNetworkConnector-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<multicastNetworkConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-multicastNetworkConnector-element"><multicastNetworkConnector></a></em> Element</h3>
-<p> </p><p>A network connector which uses some kind of multicast-like transport that
+<p><structured-macro ac:macro-id="75158285-2a2f-44a0-844e-e0ed47ca64e7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">multicastNetworkConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="multicastNetworkConnector-element"><link-body><multicastNetworkConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="08708d44-ed18-4fba-8d01-364dbe39408e" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses some kind of multicast-like transport that
communicates with potentially many remote brokers over a single logical
{@link Transport} instance such as when using multicast.
This implementation does not depend on multicast at all; any other group
-based transport could be used.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.49">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> bridge </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.DemandForwardingBridgeSupport-types">org.apache.activemq.network.DemandForwardingBridgeSupport</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> bridgeTempDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> duplex </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localTransport </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkTTL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> objectName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteTransport </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the remote transport implementation</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remoteURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the remote transport URI to some group transport like
-<code>multicast://address:port</code></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+based transport could be used.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> bridge </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.DemandForwardingBridgeSupport-types"><link-body>org.apache.activemq.network.DemandForwardingBridgeSupport</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dc7bf9f9-0d4f-47fe-a273-1af91eb279e2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> bridgeTempDestinations </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bf042050-be3a-44c2-a3c8-a63761f14c36" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a01d631c-21db-46ca-84c3-b92f1c69d0e6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3b35b418-5b17-4900-bb7b-110984bf3af9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="570d3aa9-f64f-48fc-b842-b83aed332062" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionFilter </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="58a1b5e9-91b4-457c-a12c-e1522c9a5241" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="00d25ce7-9e65-415d-9165-89143fb0743b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationFilter </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6f3f4d99-6fe0-4ce5-b015-5a6f720139a6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="413101bf-787d-4953-8f8c-e94e12bb488f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> duplex </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f529db81-4b86-47b4-b90b-a85c44684697" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="63900c2f-ef38-4999-866d-b27a4e2fc8f7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="800154f7-a6b5-46bc-b31b-775862244b30" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1fdfb5f4-5b2c-4ae6-ba79-8cc21a3e00d5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6a0d068d-1dfd-4919-900c-ce2b342f61d1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localTransport </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="54483715-8e04-429c-bec1-940b717aeb66" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3d3c8d73-2b13-4c68-a6b3-aebd82aef41b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="211c79ab-3b4a-4182-a9a0-c9d21150e9a9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkTTL </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4cf3aaac-ba9f-4ba4-8b91-0d5a24ea916d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> objectName </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3de47842-a011-4b2d-9b36-3f40d341f044" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="73e0b76b-4b2f-4e21-bb9f-495f14ce2e67" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b4bfabba-18fa-46b4-ad7a-b6d94f7c740f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteTransport </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.Transport</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="36bbcab6-2423-47de-8af2-fc6436249b19" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the remote transport implementation</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remoteURI </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6d87b670-4719-41f9-88f3-89c14be9c228" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the remote transport URI to some group transport like
+<code>multicast://address:port</code></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b9338e6c-0af1-4ec7-9bc9-ebc5479defd0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dfee0c59-8e30-414c-9f4b-91b68438f746" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-multicastTraceBrokerPlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<multicastTraceBrokerPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-multicastTraceBrokerPlugin-element"><multicastTraceBrokerPlugin></a></em> Element</h3>
-<p> </p><p>A Broker interceptor which allows you to trace all operations to a Multicast
-socket.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.50">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> address </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.SocketAddress</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> broadcast </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxTraceDatagramSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> next </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.Broker-types">org.apache.activemq.broker.Broker</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> timeToLive </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.wireformat.WireFormat</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormatFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.wireformat.WireFormatFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="0eed5b9c-77a5-410a-90ff-f6fe36af3d20" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">multicastTraceBrokerPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="multicastTraceBrokerPlugin-element"><link-body><multicastTraceBrokerPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="35be0f56-4dbc-4e63-b151-0fa4acea03fb" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which allows you to trace all operations to a Multicast
+socket.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> address </p></td><td colspan="1" rowspan="1"><p> <em>java.net.SocketAddress</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ed7cf2e8-360c-4a07-a458-97785dad1e74" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0288de51-c50e-4520-b1b0-bfc83358ac64" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> broadcast </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1e904564-5fbe-49ee-ad7a-e492732719c0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="96e63610-6683-4b28-b3f0-46e94d5f570c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxTraceDatagramSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0cc8da95-d4bc-4a91-b8f0-710d330b4b6b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> next </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.Broker-types"><link-body>org.apache.activemq.broker.Broker</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c8c8ac27-2b89-4f24-9b6d-50689ea4badd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> timeToLive </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bb6c0689-53af-4a36-b5f8-6f3aba4b95b8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.wireformat.WireFormat</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8f3f6469-34a0-4a16-9539-f1156c13a3ba" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormatFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.wireformat.WireFormatFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9bd5befe-6889-45ec-a8a5-94ccad152edb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-networkConnector-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<networkConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-networkConnector-element"><networkConnector></a></em> Element</h3>
-<p> </p><p>A network connector which uses a discovery agent to detect the remote brokers
-available and setup a connection to each available remote broker</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.51">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> bridgeTempDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerService </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.BrokerService-types">org.apache.activemq.broker.BrokerService</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectionFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationFilter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoveryAgent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.discovery.DiscoveryAgent</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoveryURI </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> duplex </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicOnly </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> excludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> networkTTL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> objectName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> uri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="dcdf0a7d-4060-4259-9a7b-ab7bb603f03e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">networkConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="networkConnector-element"><link-body><networkConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="63beed8d-5652-4a90-ad69-61fc2fc9c290" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses a discovery agent to detect the remote brokers
+available and setup a connection to each available remote broker</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> bridgeTempDestinations </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bb2d1506-1297-4eb5-bfb9-bfabf33a61ed" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="51219a97-7d13-42de-ae58-3e74274ff9ee" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerService </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.BrokerService-types"><link-body>org.apache.activemq.broker.BrokerService</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="738c8dea-81a3-408a-883f-3758982d6e95" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> conduitSubscriptions </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d91d2ed6-0f90-420a-8b17-ed9de20ddb6c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectionFilter </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.network.ConnectionFilter</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="de1be2e3-6666-4054-be18-1e93119083f1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> decreaseNetworkConsumerPriority </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ffc2a3b4-232f-43af-97b8-75b99e149449" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationFilter </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="826298b2-69cf-44e2-a2cf-561e5c6a5ef6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoveryAgent </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.discovery.DiscoveryAgent</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="73f5715c-3383-4452-ba6a-09353b38b489" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoveryURI </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="019ec49d-4276-41f0-87d3-cd87b7b23874" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ba018c11-5199-4796-870c-19cf567027bf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> duplex </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dffcab9f-a75d-4809-8030-3855c38b3795" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="df87075a-fdab-4a1f-afc9-b5af77a4d3d8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicOnly </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="96aa6a7d-bd25-45c5-b2f1-65f773c10742" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dynamicallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="272feddd-0c8b-498e-8eac-72762614eeb6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> excludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a41cd9ef-f4cb-4a08-af53-bc4caf2aa006" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5a204344-0830-4277-ad95-46af98ac6a59" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="08b3e665-d0b6-497c-98cc-551095b4f8f7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> networkTTL </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fb76c46b-322c-4a23-83db-15128df614e4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> objectName </p></td><td colspan="1" rowspan="1"><p> <em>javax.management.ObjectName</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ef148f37-fe62-4293-a7ca-d570b8b25927" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c3b09ec2-2dbe-47d0-9eb1-e8512fa963be" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="af72b267-03da-46b1-b13f-33970e0fd5c6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> staticallyIncludedDestinations </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="796e2720-b8d5-4be9-8cb7-c7557474f7ac" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> uri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="58b3f4ef-37c3-4d4e-8da1-9041747f8ceb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a84991ad-9fce-40f4-91e1-d986f321b113" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-noSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<noSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-noSubscriptionRecoveryPolicy-element"><noSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This SubscriptionRecoveryPolicy disable recovery of messages.</p><p></p>
+<p><structured-macro ac:macro-id="c2e8d5b5-248f-481c-9583-166553b2c815" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">noSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="noSubscriptionRecoveryPolicy-element"><link-body><noSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="665cf7b0-f21a-47f9-bc79-a3e2815633cf" ac:name="html" ac:schema-version="1"><plain-text-body>This SubscriptionRecoveryPolicy disable recovery of messages.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-oldestMessageEvictionStrategy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<oldestMessageEvictionStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-oldestMessageEvictionStrategy-element"><oldestMessageEvictionStrategy></a></em> Element</h3>
-<p> </p><p>An eviction strategy which evicts the oldest message first (which is the
-default).</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.52">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> evictExpiredMessagesHighWatermark </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the high water mark on which we will eagerly evict expired messages from RAM</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="bdfaf411-c8bf-4f77-90d8-88e500f72248" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">oldestMessageEvictionStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="oldestMessageEvictionStrategy-element"><link-body><oldestMessageEvictionStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="4ab9a65c-d7fb-46a7-8a7a-0410d08efd01" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message first (which is the
+default).</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> evictExpiredMessagesHighWatermark </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1d8a1bab-dc63-47a0-9aac-cf4b0e36d9ea" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the high water mark on which we will eagerly evict expired messages from RAM</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-oldestMessageWithLowestPriorityEvictionStrategy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<oldestMessageWithLowestPriorityEvictionStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-oldestMessageWithLowestPriorityEvictionStrategy-element"><oldestMessageWithLowestPriorityEvictionStrategy></a></em> Element</h3>
-<p> </p><p>An eviction strategy which evicts the oldest message with the lowest priority first.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.53">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> evictExpiredMessagesHighWatermark </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the high water mark on which we will eagerly evict expired messages from RAM</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="48f305c7-e9ae-47f6-8514-b738c519551b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">oldestMessageWithLowestPriorityEvictionStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="oldestMessageWithLowestPriorityEvictionStrategy-element"><link-body><oldestMessageWithLowestPriorityEvictionStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="46b877f4-4dd6-4e74-b5a5-ca75cd120fe4" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message with the lowest priority first.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> evictExpiredMessagesHighWatermark </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="25d8bf60-4231-44f6-9fa3-7b397d893470" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the high water mark on which we will eagerly evict expired messages from RAM</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-oracleJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<oracleJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-oracleJDBCAdapter-element"><oracleJDBCAdapter></a></em> Element</h3>
-<p> </p><p>Implements all the default JDBC operations that are used
+<p><structured-macro ac:macro-id="81199ae4-1cb6-42a7-bfab-6122b49e5c62" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">oracleJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="oracleJDBCAdapter-element"><link-body><oracleJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f8495c20-ef59-4874-93f2-f5d6bfa91580" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used
by the JDBCPersistenceAdapter.
-</p><p></p>
+<p/>
Subclassing is encouraged to override the default
implementation of methods to account for differences
in JDBC Driver implementations.
-<p></p>
+<p/>
The JDBCAdapter inserts and extracts BLOB data using the
getBytes()/setBytes() operations.
-<p></p>
+<p/>
The databases/JDBC drivers that use this adapter are:
-<ul><li></li></ul><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.54">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cfa99616-bae8-496d-b148-b4b1248e028f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d29d33bc-08ca-4d6d-9fb9-6c55a08cf89f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="305df282-1456-46aa-aede-501a440e14bb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-outboundQueueBridge-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<outboundQueueBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-outboundQueueBridge-element"><outboundQueueBridge></a></em> Element</h3>
-<p> </p><p>Create an Outbound Queue Bridge</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.55">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Queue-types">javax.jms.Queue</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localQueueName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumRetries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the maximum number of retries if a send fails before closing the
-bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundQueueName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Queue-types">javax.jms.Queue</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="511f64d4-87f4-4e15-b2d9-d99b93a8a3bb" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">outboundQueueBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="outboundQueueBridge-element"><link-body><outboundQueueBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5a9635c0-d17a-44c6-9ce0-84c2ef323737" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Queue Bridge</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="890297aa-8f45-469c-9d40-ba4f9fbc35cc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a010041d-2312-4dd4-8242-992e48de572a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dff22339-dff1-4113-8f8c-ac2d6e1a7d88" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="469307ad-ada5-4049-83c2-0312f5f70347" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsConnector </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0ead10e6-44cd-4501-a269-5864546e9e5a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3acb1e87-5376-46d7-8114-8c5a936ee35e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localQueueName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1d9ec2d8-f0ab-4294-a68b-d09f2fea59cc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maximumRetries </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="da0d6064-ebf4-42f7-b808-041bb4f2c507" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the maximum number of retries if a send fails before closing the
+bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundQueueName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1990f06d-86a0-40b1-aae7-230895b2f589" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.QueueConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="83b5f027-3af0-43d1-8b4e-ed6f7a9d5635" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Queue-types"><link-body>javax.jms.Queue</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6b33175a-e254-4774-be01-d8b24064a623" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6db24339-20ea-4964-9b5b-ce8184d476b8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-outboundTopicBridge-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<outboundTopicBridge>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-outboundTopicBridge-element"><outboundTopicBridge></a></em> Element</h3>
-<p> </p><p>Create an Outbound Topic Bridge</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.56">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> consumerTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Topic-types">javax.jms.Topic</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsConnector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsConnector-types">org.apache.activemq.network.jms.JmsConnector</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.network.jms.JmsMesageConvertor-types">org.apache.activemq.network.jms.JmsMesageConvertor</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localTopicName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumRetries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the maximum number of retries if a send fails before closing the
-bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> outboundTopicName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerConnection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerTopic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-javax.jms.Topic-types">javax.jms.Topic</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> selector </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="fef2bf67-4651-4e6c-9f54-a63ea7fbda0b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">outboundTopicBridge-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="outboundTopicBridge-element"><link-body><outboundTopicBridge></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="785f7477-c2ac-4ec9-82f2-39634811e20b" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Topic Bridge</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> consumer </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.MessageConsumer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="63b0ed36-26df-4c63-a14a-c85dc7fa2777" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fd10ee12-8ebd-4663-b0dd-bbcf793349a0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="94761e41-1276-4781-a223-6d0db663e30b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> consumerTopic </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6f47dba1-795e-489c-ba4a-a9c358a96c33" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> doHandleReplyTo </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1cadff31-6e98-45f9-a8dd-e0a316ff0c2e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsConnector </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsConnector-types"><link-body>org.apache.activemq.network.jms.JmsConnector</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e7dba967-05c8-45d9-bf39-95e0bde7836d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> jmsMessageConvertor </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.network.jms.JmsMesageConvertor-types"><link-body>org.apache.activemq.network.jms.JmsMesageConvertor</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e9988c65-42d1-4a3d-8937-8930a0172853" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localTopicName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3595e293-9dcc-4a26-b35a-54bf2d03b01b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maximumRetries </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="71ab7c5a-350b-45ec-8c9b-b5a06c2da3ce" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the maximum number of retries if a send fails before closing the
+bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> outboundTopicName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="540d35ec-7044-443c-ae15-7dfa2e75d151" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerConnection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.TopicConnection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="11a1469f-86aa-4143-b690-b9eb601f1b42" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerTopic </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="javax.jms.Topic-types"><link-body>javax.jms.Topic</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8844b369-68dd-4c88-ae13-3e6c72516bbc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> selector </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6ff3c00a-ffcb-4cd5-9127-c1312dfa513c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-policyEntry-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<policyEntry>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-policyEntry-element"><policyEntry></a></em> Element</h3>
-<p> </p><p>Represents an entry in a {@link PolicyMap} for assigning policies to a
-specific destination or a hierarchical wildcard area of destinations.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.57">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deadLetterStrategy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.DeadLetterStrategy-types">org.apache.activemq.broker.region.policy.DeadLetterStrategy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the policy used to determine which dead letter queue destination
-should be used</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.DispatchPolicy-types">org.apache.activemq.broker.region.policy.DispatchPolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> enableAudit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxAuditDepth </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxProducersToAudit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxQueueAuditDepth </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> memoryLimit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageEvictionStrategy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types">org.apache.activemq.broker.region.policy.MessageEvictionStrategy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the eviction strategy used to decide which message to evict when the
-slow consumer needs to discard messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageGroupMapFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.group.MessageGroupMapFactory-types">org.apache.activemq.broker.region.group.MessageGroupMapFactory</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the factory used to create new instances of {MessageGroupMap} used
-to implement the <a shape="rect" href="http://activemq.apache.org/message-groups.html">Message Groups</a>
-functionality.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> optimizedDispatch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> pendingDurableSubscriberPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy-types">org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> pendingMessageLimitStrategy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types">org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the strategy to calculate the maximum number of messages that are
+<p><structured-macro ac:macro-id="5579ca80-6b12-4165-88bc-3d260d95cde9" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">policyEntry-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="policyEntry-element"><link-body><policyEntry></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="7007c433-60ea-4776-8f60-48d286b18339" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link PolicyMap} for assigning policies to a
+specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> deadLetterStrategy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.DeadLetterStrategy-types"><link-body>org.apache.activemq.broker.region.policy.DeadLetterStrategy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c0586547-64ab-4a96-8912-d43649b57fc1" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the policy used to determine which dead letter queue destination
+should be used</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cf36fad1-36ba-42e1-a5f1-42614abae515" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.DispatchPolicy-types"><link-body>org.apache.activemq.broker.region.policy.DispatchPolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e7da6b77-3ba5-47fb-8aa8-126ec5546d23" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> enableAudit </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fc48085e-0c6a-4d3a-81ce-9c1cf74af14f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxAuditDepth </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c748ef3d-85c0-4acf-9f0c-92d26121dd66" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxProducersToAudit </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5fb04af6-139e-4094-a20d-09ec2680c7dd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxQueueAuditDepth </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4b199023-ee87-411c-ada6-e19c238aa210" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> memoryLimit </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="52ec0482-57ed-4727-bc2e-a456fe63b460" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageEvictionStrategy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.MessageEvictionStrategy-types"><link-body>org.apache.activemq.broker.region.policy.MessageEvictionStrategy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="35a9caa1-954a-401b-82b3-00b705ddf6d2" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the eviction strategy used to decide which message to evict when the
+slow consumer needs to discard messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageGroupMapFactory </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.group.MessageGroupMapFactory-types"><link-body>org.apache.activemq.broker.region.group.MessageGroupMapFactory</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="59f0d95b-38a1-42a1-81f2-b27cd8d908b5" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the factory used to create new instances of {MessageGroupMap} used
+to implement the <a
+href="http://activemq.apache.org/message-groups.html">Message Groups</a>
+functionality.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> optimizedDispatch </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b68f5232-13c6-4ee9-9556-d6b12600981b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> pendingDurableSubscriberPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy-types"><link-body>org.apache.activemq.broker.region.policy.PendingDurableSubscriberMessageStoragePolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4d4d0812-9ec8-403b-8811-6158388bf865" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> pendingMessageLimitStrategy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy-types"><link-body>org.apache.activemq.broker.region.policy.PendingMessageLimitStrategy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ae7794df-6a43-44d9-811f-6a26f75f8db8" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the strategy to calculate the maximum number of messages that are
allowed to be pending on consumers (in addition to their prefetch sizes).
Once the limit is reached, non-durable topics can then start discarding
old messages. This allows us to keep dispatching messages to slow
consumers while not blocking fast consumers and discarding the messages
-oldest first.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> pendingQueuePolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy-types">org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> pendingSubscriberPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy-types">org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerFlowControl </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> sendAdvisoryIfNoConsumers </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sends an advisory message if a non-persistent message is sent and there
-are no active consumers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> subscriptionRecoveryPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types">org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr></tbody></table></div>
+oldest first.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> pendingQueuePolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy-types"><link-body>org.apache.activemq.broker.region.policy.PendingQueueMessageStoragePolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e19199cc-e020-48ac-87af-5c7c1aa4f330" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> pendingSubscriberPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy-types"><link-body>org.apache.activemq.broker.region.policy.PendingSubscriberMessageStoragePolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b1a44f56-cd26-469e-880d-d2780e723651" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerFlowControl </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f2d4cf08-83de-4153-8ce4-b91ea7854c85" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c4df3b24-70ec-49df-a846-9d0dca6bd461" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> sendAdvisoryIfNoConsumers </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9d0baeff-3064-4f1e-9b9b-e533ca2da045" ac:name="html" ac:schema-version="1"><plain-text-body>Sends an advisory message if a non-persistent message is sent and there
+are no active consumers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> subscriptionRecoveryPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy-types"><link-body>org.apache.activemq.broker.region.policy.SubscriptionRecoveryPolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1cc020e6-b9e3-436f-8eca-a9ba9625a87a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topic </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="88b03e36-6f10-4350-9180-5fd71211fe6b" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-policyMap-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<policyMap>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-policyMap-element"><policyMap></a></em> Element</h3>
-<p> </p><p>Represents a destination based configuration of policies so that individual
+<p><structured-macro ac:macro-id="38c86f3f-7f87-404a-8de2-6cc642821370" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">policyMap-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="policyMap-element"><link-body><policyMap></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="a7b88623-b42e-4726-b6a9-de18eb6bc666" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
-different policies.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.58">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> defaultEntry </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.policy.PolicyEntry-types">org.apache.activemq.broker.region.policy.PolicyEntry</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> entries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to allow the destination map to be populated from a
-dependency injection framework such as Spring</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> policyEntries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the individual entries on the policy map</p> <p></p></td></tr></tbody></table></div>
+different policies.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> defaultEntry </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.region.policy.PolicyEntry-types"><link-body>org.apache.activemq.broker.region.policy.PolicyEntry</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2496bd28-4b05-492a-8c75-8b4b9344e70e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> entries </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e137a2af-4efd-41f4-8d0b-5856f1b1b7ef" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to allow the destination map to be populated from a
+dependency injection framework such as Spring</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> policyEntries </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cdc6f382-98f8-4555-8e32-10aa512f0eba" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the individual entries on the policy map</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-prefetchPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<prefetchPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-prefetchPolicy-element"><prefetchPolicy></a></em> Element</h3>
-<p> </p><p>Defines the prefetch message policies for different types of consumers</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.59">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> all </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableTopicPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> inputStreamPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumPendingMessageLimit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets how many messages a broker will keep around, above the prefetch
-limit, for non-durable topics before starting to discard older messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> optimizeDurableTopicPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queueBrowserPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queuePrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topicPrefetch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a081e88b-937b-42df-ad19-456ffa7eb9c7" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">prefetchPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="prefetchPolicy-element"><link-body><prefetchPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ddb7c15a-e41c-44d6-a1de-1107938cd5cc" ac:name="html" ac:schema-version="1"><plain-text-body>Defines the prefetch message policies for different types of consumers</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> all </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="292ef56e-d259-4cb4-b6be-1848075a47bd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableTopicPrefetch </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e9d3e7a2-79fe-46c0-868a-7d6687cafd01" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> inputStreamPrefetch </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8341bc5d-9548-49ac-ac67-c70e6d39885c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maximumPendingMessageLimit </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="adf9cddf-10ba-435a-a81d-1291aec2067a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets how many messages a broker will keep around, above the prefetch
+limit, for non-durable topics before starting to discard older messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> optimizeDurableTopicPrefetch </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="915fa0b7-3e9d-4bd7-a2b4-bf08cb2001e6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queueBrowserPrefetch </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2224357f-990e-4caf-adf6-aae90a7ac78d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queuePrefetch </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f2e56782-127f-4efa-8868-608845a701fc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topicPrefetch </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="635e601a-7fa5-42a1-9877-60a6e22dcd7a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-prefetchRatePendingMessageLimitStrategy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<prefetchRatePendingMessageLimitStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-prefetchRatePendingMessageLimitStrategy-element"><prefetchRatePendingMessageLimitStrategy></a></em> Element</h3>
-<p> </p><p>This PendingMessageLimitStrategy sets the maximum pending message limit value to be
-a multiplier of the prefetch limit of the subscription.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.60">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> multiplier </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>double</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the multiplier of the prefetch size which will be used to define the maximum number of pending
-messages for non-durable topics before messages are discarded.</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="2177b92d-df42-49d2-9436-9f368976d411" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">prefetchRatePendingMessageLimitStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="prefetchRatePendingMessageLimitStrategy-element"><link-body><prefetchRatePendingMessageLimitStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="2fe29b64-0f9c-4166-b13a-cb5747365266" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy sets the maximum pending message limit value to be
+a multiplier of the prefetch limit of the subscription.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> multiplier </p></td><td colspan="1" rowspan="1"><p> <em>double</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d2ce7ca4-3ad9-4f3e-b015-dc8dac20868d" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the multiplier of the prefetch size which will be used to define the maximum number of pending
+messages for non-durable topics before messages are discarded.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-proxyConnector-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<proxyConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-proxyConnector-element"><proxyConnector></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.61">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> bind </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> localUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> remote </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> server </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.TransportServer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="4f82ed0b-e27a-4cc1-866f-f0ae9946efd0" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">proxyConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="proxyConnector-element"><link-body><proxyConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="7f139556-d1ae-4db0-9932-954b1dd2d727" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> bind </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f1c083fd-551f-4e08-864e-dc96a05da1a5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> localUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bdf340f8-b6ec-4517-b1ba-b5e77ad41843" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="313b71fe-f724-4c7a-b8f6-2c401cd21468" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> remote </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="267dc4e9-9c9c-469a-897b-ba5d3b67f195" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> server </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.TransportServer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c357d335-05a8-4786-8a77-107d048d2510" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-queryBasedSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<queryBasedSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-queryBasedSubscriptionRecoveryPolicy-element"><queryBasedSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user
-specific query mechanism to load any messages they may have missed.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.62">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> query </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.region.policy.MessageQuery</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the query strategy to load initial messages</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="370e309b-c400-4124-b5cd-ae296feb4735" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">queryBasedSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="queryBasedSubscriptionRecoveryPolicy-element"><link-body><queryBasedSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="29798382-f62d-4be9-b376-23fa3e199e9c" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user
+specific query mechanism to load any messages they may have missed.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> query </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.region.policy.MessageQuery</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="458f0e61-b1e2-430f-9f12-dcb8219b71b4" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the query strategy to load initial messages</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-queue-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<queue>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-queue-element"><queue></a></em> Element</h3>
-<p> </p><p>An ActiveMQ Queue</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.63">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> compositeDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> physicalName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> properties </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Get the properties from this instance for storing in JNDI</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="e3fe28ce-c028-48ef-a54e-6e3bf836e94d" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">queue-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="73fde806-9542-4382-a5f8-22914d408285" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> compositeDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="03d6d3a5-bca0-4a07-9ad2-704289dd50a3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c4b3eabc-1444-4358-9cc4-cd12c52d0eb0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> physicalName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ad2a8e5d-6687-4080-ae52-448fb9fb5d75" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> properties </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2c9d7117-fa11-4ce2-ba58-d05a6ca2268f" ac:name="html" ac:schema-version="1"><plain-text-body>Get the properties from this instance for storing in JNDI</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-redeliveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<redeliveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-redeliveryPolicy-element"><redeliveryPolicy></a></em> Element</h3>
-<p> </p><p>Configuration options used to control how messages are re-delivered when they
-are rolled back.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.64">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> backOffMultiplier </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>short</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> collisionAvoidancePercent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>short</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> initialRedeliveryDelay </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maximumRedeliveries </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useCollisionAvoidance </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExponentialBackOff </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="68c308e2-a29e-4e14-bb76-aeeb1592553b" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">redeliveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="redeliveryPolicy-element"><link-body><redeliveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="4a7bb072-3867-4a13-bbfa-6c15c02bb8b3" ac:name="html" ac:schema-version="1"><plain-text-body>Configuration options used to control how messages are re-delivered when they
+are rolled back.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> backOffMultiplier </p></td><td colspan="1" rowspan="1"><p> <em>short</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3aaa31a4-d436-43b1-ab37-098147a25374" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> collisionAvoidancePercent </p></td><td colspan="1" rowspan="1"><p> <em>short</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="34440a2d-20df-47a5-b7f0-d145a779f98c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> initialRedeliveryDelay </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dbaff494-ebd8-4ca9-868a-182be568727e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maximumRedeliveries </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9448fa8b-9679-4bcc-a0b0-cf012a1fd359" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useCollisionAvoidance </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8cfb1ccc-04b4-4886-b320-5818bc83b710" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExponentialBackOff </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6f33a8c6-3cf2-41d5-8e6a-b5d68d3ac9b5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-roundRobinDispatchPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<roundRobinDispatchPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-roundRobinDispatchPolicy-element"><roundRobinDispatchPolicy></a></em> Element</h3>
-<p> </p><p>Simple dispatch policy that sends a message to every subscription that
-matches the message.</p><p></p>
+<p><structured-macro ac:macro-id="4bca0b95-74f7-48c9-b9dc-b0282f8b21f5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">roundRobinDispatchPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="roundRobinDispatchPolicy-element"><link-body><roundRobinDispatchPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ec48e258-584e-47f3-ab5b-dfc926168bd2" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that
+matches the message.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-sharedDeadLetterStrategy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<sharedDeadLetterStrategy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-sharedDeadLetterStrategy-element"><sharedDeadLetterStrategy></a></em> Element</h3>
-<p> </p><p>A default implementation of {@link DeadLetterStrategy} which uses
-a constant destination.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.65">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deadLetterQueue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> processExpired </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> processNonPersistent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="42f0eac5-a1e7-4735-981d-14a9c04cc3c6" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">sharedDeadLetterStrategy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="sharedDeadLetterStrategy-element"><link-body><sharedDeadLetterStrategy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="674cc786-159f-4518-abdf-fa44a8804480" ac:name="html" ac:schema-version="1"><plain-text-body>A default implementation of {@link DeadLetterStrategy} which uses
+a constant destination.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> deadLetterQueue </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="868242ee-d286-4818-8461-2322e96a86d0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> processExpired </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e23310f4-8e23-4484-a932-99c5aa5937a2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> processNonPersistent </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="84829cfe-52cf-45b9-a861-ac2bf14514cb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-simpleAuthenticationPlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<simpleAuthenticationPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-simpleAuthenticationPlugin-element"><simpleAuthenticationPlugin></a></em> Element</h3>
-<p> </p><p>Provides a simple authentication plugin</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.66">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userGroups </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the groups a user is in. The key is the user name and the value is a
-Set of groups</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userPasswords </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the map indexed by user name with the value the password</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> users </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets individual users for authentication</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="8bd415d8-ee6d-48f9-b46f-51115e5b880e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleAuthenticationPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleAuthenticationPlugin-element"><link-body><simpleAuthenticationPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9c9c258e-0468-4326-902b-9d12b0fe76d9" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a simple authentication plugin</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> userGroups </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bc950038-2f59-451a-85d8-f7f242a29742" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the groups a user is in. The key is the user name and the value is a
+Set of groups</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userPasswords </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Map</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="284162c6-8d19-45f3-8ce4-6a0706b990b8" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the map indexed by user name with the value the password</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> users </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b26114c8-d7f6-4f8c-9476-bfc3505f17e4" ac:name="html" ac:schema-version="1"><plain-text-body>Sets individual users for authentication</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-simpleAuthorizationMap-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<simpleAuthorizationMap>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-simpleAuthorizationMap-element"><simpleAuthorizationMap></a></em> Element</h3>
-<p> </p><p>An AuthorizationMap which is configured with individual DestinationMaps for
-each operation.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.67">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.filter.DestinationMap-types">org.apache.activemq.filter.DestinationMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> readACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.filter.DestinationMap-types">org.apache.activemq.filter.DestinationMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tempDestinationAuthorizationEntry </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.security.TempDestinationAuthorizationEntry-types">org.apache.activemq.security.TempDestinationAuthorizationEntry</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> writeACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.filter.DestinationMap-types">org.apache.activemq.filter.DestinationMap</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="5bc9043c-3a1f-47a4-bc6f-bd9d11f4cdfa" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleAuthorizationMap-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleAuthorizationMap-element"><link-body><simpleAuthorizationMap></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="a930d6a5-a430-4448-b0dc-a7f417493bc2" ac:name="html" ac:schema-version="1"><plain-text-body>An AuthorizationMap which is configured with individual DestinationMaps for
+each operation.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adminACLs </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.filter.DestinationMap-types"><link-body>org.apache.activemq.filter.DestinationMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e37cfb12-2969-4b88-8e74-ac7ff9e74f71" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> readACLs </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.filter.DestinationMap-types"><link-body>org.apache.activemq.filter.DestinationMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6e3df292-1dd9-4848-9d51-ee3a9dbefabd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> tempDestinationAuthorizationEntry </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.security.TempDestinationAuthorizationEntry-types"><link-body>org.apache.activemq.security.TempDestinationAuthorizationEntry</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b06829a3-f4a7-4551-ad34-aa3640a2dd55" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> writeACLs </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.filter.DestinationMap-types"><link-body>org.apache.activemq.filter.DestinationMap</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cb6d4003-53ac-4973-9a38-56197a0e2536" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-simpleDispatchPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<simpleDispatchPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-simpleDispatchPolicy-element"><simpleDispatchPolicy></a></em> Element</h3>
-<p> </p><p>Simple dispatch policy that sends a message to every subscription that
-matches the message.</p><p></p>
+<p><structured-macro ac:macro-id="664d7a1f-b8cb-424c-ae3f-40a0d5b4bf72" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleDispatchPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleDispatchPolicy-element"><link-body><simpleDispatchPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="f464f427-1cf9-44cd-975b-42761c67e43b" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that
+matches the message.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-simpleJmsMessageConvertor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<simpleJmsMessageConvertor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-simpleJmsMessageConvertor-element"><simpleJmsMessageConvertor></a></em> Element</h3>
-<p> </p><p>Converts Message from one JMS to another</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.68">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connection </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>javax.jms.Connection</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="6cea8a74-38f2-4c92-8067-4fbb23f4dc9c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleJmsMessageConvertor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleJmsMessageConvertor-element"><link-body><simpleJmsMessageConvertor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="ae3b5217-76b7-435e-b83b-16f90e44ce32" ac:name="html" ac:schema-version="1"><plain-text-body>Converts Message from one JMS to another</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> connection </p></td><td colspan="1" rowspan="1"><p> <em>javax.jms.Connection</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1a38dc93-2140-4d2d-b9b1-dddbc619b677" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-simpleMessageGroupMapFactory-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<simpleMessageGroupMapFactory>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-simpleMessageGroupMapFactory-element"><simpleMessageGroupMapFactory></a></em> Element</h3>
-<p> </p><p>A factory to create instances of {@link SimpleMessageGroupMap} when implementing the
-<a shape="rect" href="http://activemq.apache.org/message-groups.html">Message Groups</a> functionality.</p><p></p>
+<p><structured-macro ac:macro-id="eeb4a1d1-7f3a-45ec-9870-eac0a35ca63c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">simpleMessageGroupMapFactory-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="simpleMessageGroupMapFactory-element"><link-body><simpleMessageGroupMapFactory></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="22eb9bfe-e834-45f2-9f02-166cc6b00b25" ac:name="html" ac:schema-version="1"><plain-text-body>A factory to create instances of {@link SimpleMessageGroupMap} when implementing the
+<a href="http://activemq.apache.org/message-groups.html">Message Groups</a> functionality.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-statements-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<statements>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-statements-element"><statements></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.69">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> addMessageStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> binaryDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> containerNameDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createDurableSubStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> createSchemaStatements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deleteOldMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> deleteSubscriptionStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destinationMessageCountStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dropSchemaStatements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableSubAcksTableName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> durableSubscriberMessageCountStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findAllDestinationsStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findAllDurableSubMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findAllDurableSubsStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findAllMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findDurableSubMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findDurableSubStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findLastSequenceIdInAcksStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findLastSequenceIdInMsgsStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findMessageSequenceIdStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findMessageStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> findNextMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> lastAckedDurableSubscriberMessageStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> lockCreateStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> lockTableName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> lockUpdateStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> longDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageTableName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> msgIdDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> nextDurableSubscriberMessageStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> removeAllMessagesStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> removeAllSubscriptionsStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> removeMessageStatment </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> sequenceDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> stringIdDataType </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tablePrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> updateLastAckOfDurableSubStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> updateMessageStatement </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useLockCreateWhereClause </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="a6d33a37-28e3-4854-9f05-42aeeb7525e5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">statements-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="statements-element"><link-body><statements></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="de8074b8-fcd5-494e-ab41-c1a00091afb0" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> addMessageStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4baa3142-84d6-452a-976d-a86c554b9977" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> binaryDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="64594772-1aa9-42b3-b46a-b3c11b745070" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> containerNameDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b56d5d28-c27c-468f-a688-566bd850c3d5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createDurableSubStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="74f74ea1-d7df-42c9-a1e0-8ea1e4b18f4b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> createSchemaStatements </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b0da1496-bd06-4b7b-b09b-1b1d2160b6a8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> deleteOldMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="911db006-db2c-4f12-a7d8-b281c0d951c2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> deleteSubscriptionStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a0aec0a8-b305-4b55-93af-5760e57ffce7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destinationMessageCountStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e1e7a389-7a36-4e96-aed1-0ce32e20883b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dropSchemaStatements </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.String</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="117dde54-ae79-4606-8ee7-0540cea42e96" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableSubAcksTableName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1f28854c-f744-4cde-9b69-78d2a84fae42" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> durableSubscriberMessageCountStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3b586dbe-2bf6-4aeb-80b0-216cb18ac372" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findAllDestinationsStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="02dbdcab-1090-4f44-a629-8652981a0715" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findAllDurableSubMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9cd2c3c1-732f-4160-a6d0-83629af01b22" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findAllDurableSubsStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0fee64d7-0dc1-4e30-b3bd-89311b703aa4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findAllMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="65b59a5f-98ef-4098-acbd-9594e4893185" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findDurableSubMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="24a6db31-0754-46f2-949e-8012c46653da" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findDurableSubStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="64a38a1e-6a97-4578-bfd5-456fa1e60bae" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findLastSequenceIdInAcksStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b989a626-cc75-4895-b965-7a70454cf073" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findLastSequenceIdInMsgsStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="852a46b0-51f2-4522-abc4-94ba20b1964e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findMessageSequenceIdStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7045d5ea-1cc0-483e-b117-d11c7cbac186" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findMessageStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="aa2ce438-ef6a-42ee-b901-5e9076ed353d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> findNextMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="26f4aaf1-f061-4a6d-b7cd-db8e878a3113" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> lastAckedDurableSubscriberMessageStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="60a43f0b-97d7-44b7-b650-e5aa68e6b098" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> lockCreateStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f0af1fb2-62c0-402b-9b67-985ac830ed6a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> lockTableName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ba7f2f9b-9e7c-4d9e-a969-9f03eef9c0c9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> lockUpdateStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f1e7c9f9-8f67-4776-8d1a-5a7ab10ac09c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> longDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="44fe9eca-4ae6-4c03-b30c-31e447d9c601" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageTableName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f3de5de5-9a08-405d-aed5-02811a4b0723" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> msgIdDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3b740616-0e8d-4cb7-a7d8-84c39bf3cd1d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> nextDurableSubscriberMessageStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b0a3c473-adae-4072-ae10-7791806381c6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> removeAllMessagesStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ebde06b8-9abf-4161-83ae-a939a064e792" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> removeAllSubscriptionsStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4c3ba1e3-dda8-485b-97e3-f71802382679" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> removeMessageStatment </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1881c24c-09f5-4dc5-8c7b-4cab0753fc17" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> sequenceDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7a09fdb7-9d12-4246-b44d-150c2d3dfcfc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> stringIdDataType </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="795b7c87-4205-47d3-ab2a-3c6fdab2eaf1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> tablePrefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9941d4f6-b8e5-4575-a96b-9e34d0938169" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> updateLastAckOfDurableSubStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ff0e7369-9ae2-4e1b-b58e-0c60b64011bb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> updateMessageStatement </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ae83eb0f-3fb6-470d-9521-c9cb2e5d0d59" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f8081f7d-7213-47fb-9900-2f5b2a8a072a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useLockCreateWhereClause </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7bbb16f7-2088-4d9d-aff3-fe336fb4798b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-storeCursor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<storeCursor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-storeCursor-element"><storeCursor></a></em> Element</h3>
-<p> </p><p>Pending messages</p><p></p>
+<p><structured-macro ac:macro-id="54667eab-9703-4c27-8bbe-8717e1e55664" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">storeCursor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="storeCursor-element"><link-body><storeCursor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="9e3eb895-0378-4067-9796-c40bd1f41264" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-storeDurableSubscriberCursor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<storeDurableSubscriberCursor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-storeDurableSubscriberCursor-element"><storeDurableSubscriberCursor></a></em> Element</h3>
-<p> </p><p>Pending messages for a durable</p><p></p>
+<p><structured-macro ac:macro-id="d1995fc4-ca50-415c-8027-daa73f430ed6" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">storeDurableSubscriberCursor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="storeDurableSubscriberCursor-element"><link-body><storeDurableSubscriberCursor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="e8a61031-f126-4d6c-828c-a0bd58726b42" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages for a durable</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-storeUsage-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<storeUsage>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-storeUsage-element"><storeUsage></a></em> Element</h3>
-<p> </p><p>Used to keep track of how much of something is being used so that a
+<p><structured-macro ac:macro-id="4fd97396-cab2-4ce1-ac10-e5a9192f9b82" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">storeUsage-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="storeUsage-element"><link-body><storeUsage></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="efb3078d-ddd0-49a0-91b0-f2854400ba3f" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.70">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the memory limit in bytes. Setting the limit in bytes will set the
+memory usage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> limit </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f22be0ca-b9b3-466d-aeb9-749fbb681520" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the memory limit in bytes. Setting the limit in bytes will set the
usagePortion to 0 since the UsageManager is not going to be portion based
off the parent. When set using XBean, you can use values such as: "20
-mb", "1024 kb", or "1 gb"</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limiter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.UsageCapacity-types">org.apache.activemq.usage.UsageCapacity</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> parent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>T</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> percentUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> percentUsageMinDelta </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the minimum number of percentage points the usage has to change
-before a UsageListener event is fired by the manager.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> pollingTime </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> store </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usagePortion </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>float</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+mb", "1024 kb", or "1 gb"</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> limiter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.UsageCapacity-types"><link-body>org.apache.activemq.usage.UsageCapacity</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6077ba72-a00f-459a-a7c5-ce7238cf2c31" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7a4762cf-59f6-403e-9b0e-75802c481606" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> parent </p></td><td colspan="1" rowspan="1"><p> <em>T</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d01a5d43-a76f-4379-a2c3-fa7fbf6efddb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> percentUsage </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cd2e24be-5c17-432c-a90f-250df2c51db4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> percentUsageMinDelta </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="27133a56-2806-4ae9-8e40-0e7a24316695" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the minimum number of percentage points the usage has to change
+before a UsageListener event is fired by the manager.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> pollingTime </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b23e1490-3a88-4421-8c5e-2ae6aace9853" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> store </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="13791e6e-5b8d-4f69-a1a5-2a7bcbcfb7a1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usagePortion </p></td><td colspan="1" rowspan="1"><p> <em>float</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3ffea929-266d-466b-b4c4-42ad43baf8bc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-streamJDBCAdapter-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<streamJDBCAdapter>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-streamJDBCAdapter-element"><streamJDBCAdapter></a></em> Element</h3>
-<p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the
+<p><structured-macro ac:macro-id="b3ee63fa-2283-4dec-86ff-db7c67032e9e" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">streamJDBCAdapter-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="streamJDBCAdapter-element"><link-body><streamJDBCAdapter></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="0fc4551e-be84-41ab-9fb8-e5885e479d37" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the
setBinaryStream()/getBinaryStream() operations.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li>Axion</li></ul><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.71">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> batchStatments </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statements </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.jdbc.Statements-types">org.apache.activemq.store.jdbc.Statements</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<ul>
+<li>Axion</li>
+</ul></plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> batchStatments </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="38f016df-6531-4fa6-94f6-60cbec9a397d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statements </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.jdbc.Statements-types"><link-body>org.apache.activemq.store.jdbc.Statements</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="595301ec-8f1e-47b8-a973-2361e6f462a1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useExternalMessageReferences </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="125b67f0-2d3c-4470-9cf9-1397d4edcae6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-strictOrderDispatchPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<strictOrderDispatchPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-strictOrderDispatchPolicy-element"><strictOrderDispatchPolicy></a></em> Element</h3>
-<p> </p><p>Dispatch policy that causes every subscription to see messages in the same
-order.</p><p></p>
+<p><structured-macro ac:macro-id="44c1bb61-9a17-4752-947d-a3c8c7e83c24" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">strictOrderDispatchPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="strictOrderDispatchPolicy-element"><link-body><strictOrderDispatchPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="fca34ab1-8684-4e6a-a019-f8da2d8551d1" ac:name="html" ac:schema-version="1"><plain-text-body>Dispatch policy that causes every subscription to see messages in the same
+order.</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-systemUsage-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<systemUsage>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-systemUsage-element"><systemUsage></a></em> Element</h3>
-<p> </p><p>Holder for Usage instances for memory, store and temp files Main use case is
-manage memory usage.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.72">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adapter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.store.PersistenceAdapter-types">org.apache.activemq.store.PersistenceAdapter</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> memoryUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.MemoryUsage-types">org.apache.activemq.usage.MemoryUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> parent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.SystemUsage-types">org.apache.activemq.usage.SystemUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> sendFailIfNoSpace </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not a send() should fail if there is no space free. The
+<p><structured-macro ac:macro-id="896b9fec-2dd6-44a6-a966-08744bac43d1" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">systemUsage-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="systemUsage-element"><link-body><systemUsage></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="39793405-c41b-4ea0-ae40-84e43d84c1d3" ac:name="html" ac:schema-version="1"><plain-text-body>Holder for Usage instances for memory, store and temp files Main use case is
+manage memory usage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adapter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.store.PersistenceAdapter-types"><link-body>org.apache.activemq.store.PersistenceAdapter</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1062ff9c-e539-4cca-951e-cea8fe578117" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> memoryUsage </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.MemoryUsage-types"><link-body>org.apache.activemq.usage.MemoryUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ba6eac46-4fff-4d56-b081-cefe632e5921" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2a027b5e-b7f8-42bd-92e6-4222d6a4187a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> parent </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.SystemUsage-types"><link-body>org.apache.activemq.usage.SystemUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ee05e446-78bf-41f4-a73d-15ef4e4f68b1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> sendFailIfNoSpace </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cc641527-d8d0-48c4-be19-9cd5439d4df0" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not a send() should fail if there is no space free. The
default value is false which means to block the send() method until space
-becomes available</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> sendFailIfNoSpaceExplicitySet </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> storeUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.StoreUsage-types">org.apache.activemq.usage.StoreUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tempStore </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.kaha.Store</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> tempUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.TempUsage-types">org.apache.activemq.usage.TempUsage</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+becomes available</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> sendFailIfNoSpaceExplicitySet </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e765892d-8471-4eb8-9cff-d8edf74ec3e3" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> storeUsage </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.StoreUsage-types"><link-body>org.apache.activemq.usage.StoreUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="43e0a0d1-98b5-4a05-89c6-96e69214898e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> tempStore </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.kaha.Store</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e8c40cf7-a29c-4719-baff-d62d33e0eba1" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> tempUsage </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.TempUsage-types"><link-body>org.apache.activemq.usage.TempUsage</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c9bc0559-da80-4a48-a757-3816979d6823" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-tempDestinationAuthorizationEntry-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<tempDestinationAuthorizationEntry>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-tempDestinationAuthorizationEntry-element"><tempDestinationAuthorizationEntry></a></em> Element</h3>
-<p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
+<p><structured-macro ac:macro-id="6cc1fa7c-bc6f-4f69-a9f5-399b1b095acc" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">tempDestinationAuthorizationEntry-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="tempDestinationAuthorizationEntry-element"><link-body><tempDestinationAuthorizationEntry></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="814c44f3-1a08-4b6b-b4b9-666c28209ef8" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
different operations (read, write, admin) of user roles to a temporary
-destination</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.73">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> admin </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> groupClass </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> queue </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> read </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> readACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> topic </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper method to set the destination from a configuration file</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> write </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> writeACLs </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+destination</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> admin </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9e3971e9-64cc-469d-9457-05bcf876a681" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> adminACLs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ddf37aa8-fbb3-4b01-82c3-107fd17475fb" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="afe49a2a-8580-4d6f-9d4d-d359abafa784" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> groupClass </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4f4be224-2455-4471-9a89-c54a3a2c2b26" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> queue </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="02c84c6d-191a-4367-879f-0e9ade5da40b" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> read </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a2c79006-dbb0-4070-b502-a53ac7e6a613" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> readACLs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a5adedf8-dcbf-42b0-9d64-e51470d7f02e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> topic </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="18ace2ee-0ba0-4eae-b7ab-d0e1ebdfdeca" ac:name="html" ac:schema-version="1"><plain-text-body>A helper method to set the destination from a configuration file</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> write </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="beaa70cf-9fd8-4822-82b8-970923e5e894" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> writeACLs </p></td><td colspan="1" rowspan="1"><p> (<em>java.lang.Object</em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="270f711b-59a2-40f3-ad52-82084e994596" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-tempUsage-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<tempUsage>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-tempUsage-element"><tempUsage></a></em> Element</h3>
-<p> </p><p>Used to keep track of how much of something is being used so that a
+<p><structured-macro ac:macro-id="4e5d2000-b19e-4a0d-b85b-d59efa6d0e84" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">tempUsage-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="tempUsage-element"><link-body><tempUsage></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="5378f79e-17d2-4c59-ad74-e723bcbba18d" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.74">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the memory limit in bytes. Setting the limit in bytes will set the
+memory usage.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> limit </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b68b425a-3273-4ffe-b473-696d59eaac7f" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the memory limit in bytes. Setting the limit in bytes will set the
usagePortion to 0 since the UsageManager is not going to be portion based
off the parent. When set using XBean, you can use values such as: "20
-mb", "1024 kb", or "1 gb"</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limiter </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.usage.UsageCapacity-types">org.apache.activemq.usage.UsageCapacity</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> parent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>T</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> percentUsage </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> percentUsageMinDelta </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the minimum number of percentage points the usage has to change
-before a UsageListener event is fired by the manager.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> pollingTime </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> store </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.kaha.Store</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> usagePortion </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>float</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+mb", "1024 kb", or "1 gb"</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> limiter </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.usage.UsageCapacity-types"><link-body>org.apache.activemq.usage.UsageCapacity</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6db7be9a-ac1f-4f90-bb58-db103e7d9302" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="452c3961-6927-4a88-9a1a-f85663e390b7" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> parent </p></td><td colspan="1" rowspan="1"><p> <em>T</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0c2f350b-84dc-4eae-bd60-7ab07c2873b2" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> percentUsage </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a7a9e3a7-8ac7-4a98-af35-8911bdb75f2a" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> percentUsageMinDelta </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f6f9b54f-d169-4511-bb6e-d283ba18ec6e" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the minimum number of percentage points the usage has to change
+before a UsageListener event is fired by the manager.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> pollingTime </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0950e191-9c82-489d-87a7-554f7c351e9f" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> store </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.kaha.Store</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ec58b9d3-031f-4cdb-aacc-6da2d5afe2cf" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> usagePortion </p></td><td colspan="1" rowspan="1"><p> <em>float</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="be4102ba-884f-4f64-b641-ec46732d20f9" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-timeStampingBrokerPlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<timeStampingBrokerPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-timeStampingBrokerPlugin-element"><timeStampingBrokerPlugin></a></em> Element</h3>
-<p> </p><p>A Broker interceptor which updates a JMS Client's timestamp on the message
+<p><structured-macro ac:macro-id="b56e827d-8e7d-4a9e-bda9-3334221d4161" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">timeStampingBrokerPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="timeStampingBrokerPlugin-element"><link-body><timeStampingBrokerPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="85e896b7-c26c-468a-8c7c-0e9ecc628b57" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which updates a JMS Client's timestamp on the message
with a broker timestamp. Useful when the clocks on client machines are known
to not be correct and you can only trust the time set on the broker machines.
Enabling this plugin will break JMS compliance since the timestamp that the
producer sees on the messages after as send() will be different from the
timestamp the consumer will observe when he receives the message. This plugin
-is not enabled in the default ActiveMQ configuration.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.75">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> next </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.Broker-types">org.apache.activemq.broker.Broker</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+is not enabled in the default ActiveMQ configuration.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="994230f5-39ed-4fee-a614-390509bca380" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> next </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.Broker-types"><link-body>org.apache.activemq.broker.Broker</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fb6287b2-9021-42ef-b300-3fff854a5d27" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-timedSubscriptionRecoveryPolicy-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<timedSubscriptionRecoveryPolicy>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-timedSubscriptionRecoveryPolicy-element"><timedSubscriptionRecoveryPolicy></a></em> Element</h3>
-<p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed
+<p><structured-macro ac:macro-id="0585167b-1f25-47d8-96ba-4ced6a2c6a46" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">timedSubscriptionRecoveryPolicy-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="timedSubscriptionRecoveryPolicy-element"><link-body><timedSubscriptionRecoveryPolicy></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="a833de09-5337-4d76-8273-76922f232889" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed
buffer of messages around in memory and use that to recover new
-subscriptions.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.76">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> recoverDuration </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+subscriptions.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> recoverDuration </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="154a19bf-1adf-44f9-9f15-59875b3830c0" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-topic-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<topic>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-topic-element"><topic></a></em> Element</h3>
-<p> </p><p>An ActiveMQ Topic</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.77">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> compositeDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.command.ActiveMQDestination-types">org.apache.activemq.command.ActiveMQDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> physicalName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> properties </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Get the properties from this instance for storing in JNDI</p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="d72c82f7-bd09-4c7f-af4b-2136dd58d3d5" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">topic-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="06bc1040-b6b2-46b1-8add-f1294d452d57" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> compositeDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.command.ActiveMQDestination-types"><link-body>org.apache.activemq.command.ActiveMQDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d3e640f0-6fc6-4bc5-80cd-0fa1ebaff162" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d816d7ad-fba6-47f3-a60b-026096b97053" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> physicalName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d4c79bdc-41c6-4f0a-9073-d6283a99e5bd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> properties </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f13d63b2-83e1-49f4-a647-c78dbd979aa4" ac:name="html" ac:schema-version="1"><plain-text-body>Get the properties from this instance for storing in JNDI</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-transportConnector-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<transportConnector>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-transportConnector-element"><transportConnector></a></em> Element</h3>
-<p> </p><p></p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.78">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> broker </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.Broker-types">org.apache.activemq.broker.Broker</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerInfo </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.command.BrokerInfo</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> connectUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> disableAsyncDispatch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoveryAgent </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.discovery.DiscoveryAgent</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> discoveryUri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> enableStatusMonitor </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> messageAuthorizationPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.security.MessageAuthorizationPolicy</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the policy used to decide if the current connection is authorized to
-consume a given message</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> server </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.TransportServer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> uri </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the server transport URI to use if there is not a
+<p><structured-macro ac:macro-id="02e3645f-aedc-4453-8d45-5262a3f05039" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">transportConnector-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="transportConnector-element"><link-body><transportConnector></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="25c25193-ce83-4e50-8388-ca0c818bd86d" ac:name="html" ac:schema-version="1"></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> broker </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.Broker-types"><link-body>org.apache.activemq.broker.Broker</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a55822ac-8769-45ad-8c56-6833d226ea4b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerInfo </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.command.BrokerInfo</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5cd12941-eaf9-4cd2-8924-37daf88a75ed" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d530d382-1737-4c9d-ad4a-ca3603c90cce" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> connectUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f5b0ae24-fdbc-4353-af63-efea9ad4d574" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> disableAsyncDispatch </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="65f15b80-7d0b-44c1-a7be-78c899206466" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoveryAgent </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.discovery.DiscoveryAgent</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0b4efcde-a912-4f01-8b71-2805027635c4" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> discoveryUri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c9402e3a-3f4f-48ca-81d0-13565b8fd838" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> enableStatusMonitor </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="20bf8a74-3645-41af-82df-6cc472c026d8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> messageAuthorizationPolicy </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.security.MessageAuthorizationPolicy</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="548ec0a5-5af4-47ad-a0bc-040cb5d5a57a" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the policy used to decide if the current connection is authorized to
+consume a given message</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="17d0eb1e-fd1b-481e-b43a-4a5595633349" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> server </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.TransportServer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4eeaffd5-db41-4cb2-89bf-4833b5034a0b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> taskRunnerFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.thread.TaskRunnerFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="eccc7192-62a8-412e-88aa-ae64c4762f42" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> uri </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5069075a-e4f1-42c3-8e2d-2cb5234e4419" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the server transport URI to use if there is not a
{@link TransportServer} configured via the
{@link #setServer(TransportServer)} method. This value is used to lazy
-create a {@link TransportServer} instance</p> <p></p></td></tr></tbody></table></div>
+create a {@link TransportServer} instance</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-udpTraceBrokerPlugin-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<udpTraceBrokerPlugin>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-udpTraceBrokerPlugin-element"><udpTraceBrokerPlugin></a></em> Element</h3>
-<p> </p><p>A Broker interceptor which allows you to trace all operations to a UDP
-socket.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.79">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> address </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.SocketAddress</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> broadcast </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> destination </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> maxTraceDatagramSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> next </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.Broker-types">org.apache.activemq.broker.Broker</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormat </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.wireformat.WireFormat</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> wireFormatFactory </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.wireformat.WireFormatFactory</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="3203c513-56db-402c-aab1-8eec7b262639" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">udpTraceBrokerPlugin-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="udpTraceBrokerPlugin-element"><link-body><udpTraceBrokerPlugin></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="4c99d088-b291-4001-a857-3c3f77e0c3d4" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which allows you to trace all operations to a UDP
+socket.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> address </p></td><td colspan="1" rowspan="1"><p> <em>java.net.SocketAddress</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6ad7f822-afb5-40fe-91bb-2106af970b87" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> adminConnectionContext </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.broker.ConnectionContext</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7fabfb1f-c718-42c4-b79e-62f775aca1fd" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> broadcast </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b7f4e4c9-984e-4c7e-b77b-0d183c04c1f8" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> destination </p></td><td colspan="1" rowspan="1"><p> <em>java.net.URI</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8e255d6f-78ef-46ec-bc48-1e141edc16b6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> maxTraceDatagramSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="538cc25c-3e18-4a52-8fae-fb5775251b11" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> next </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.broker.Broker-types"><link-body>org.apache.activemq.broker.Broker</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3614b6a8-9b22-4f2a-93a4-dfccad7121c6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormat </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.wireformat.WireFormat</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0b7e7e11-ae11-4a61-8e61-210a3f7e4349" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> wireFormatFactory </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.wireformat.WireFormatFactory</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="30588cb9-7f8b-4fe8-9569-2f7bf70da50e" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-usageCapacity-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<usageCapacity>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-usageCapacity-element"><usageCapacity></a></em> Element</h3>
-<p> </p><p>Identify if a limit has been reached</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.80">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> limit </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="efbb4bde-eb88-4f77-b47b-2da93d1a2a74" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">usageCapacity-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="usageCapacity-element"><link-body><usageCapacity></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="45c59277-b18a-42c8-aa06-945113915afc" ac:name="html" ac:schema-version="1"><plain-text-body>Identify if a limit has been reached</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> limit </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6a15ed5d-3d74-42c0-aeaf-6023b4742b32" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-virtualDestinationInterceptor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<virtualDestinationInterceptor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-virtualDestinationInterceptor-element"><virtualDestinationInterceptor></a></em> Element</h3>
-<p> </p><p>Implements <a shape="rect" href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a>.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.81">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> virtualDestinations </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> (<em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.broker.region.virtual.VirtualDestination-types">org.apache.activemq.broker.region.virtual.VirtualDestination</a></em>)* </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+<p><structured-macro ac:macro-id="265d708b-2525-49e4-8100-6013a9eea192" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">virtualDestinationInterceptor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="virtualDestinationInterceptor-element"><link-body><virtualDestinationInterceptor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="6565fcfb-e4a4-4c63-ba2c-51b8a3083000" ac:name="html" ac:schema-version="1"><plain-text-body>Implements <a
+href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a>.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> virtualDestinations </p></td><td colspan="1" rowspan="1"><p> (<em><link ac:anchor="org.apache.activemq.broker.region.virtual.VirtualDestination-types"><link-body>org.apache.activemq.broker.region.virtual.VirtualDestination</link-body></link></em>)* </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="73297395-ee0d-47e3-bc03-3c68f810418c" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-virtualTopic-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<virtualTopic>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-virtualTopic-element"><virtualTopic></a></em> Element</h3>
-<p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/virtual-destinations.html">Virtual
-Topics</a> using a prefix and postfix. The virtual destination creates a
+<p><structured-macro ac:macro-id="3b7b539a-d258-406e-9dff-644dbfcde1ca" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">virtualTopic-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="virtualTopic-element"><link-body><virtualTopic></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="615d77d9-cf5c-4ab2-98c2-a61927867d2e" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/virtual-destinations.html">Virtual
+Topics</a> using a prefix and postfix. The virtual destination creates a
wildcard that is then used to look up all active queue subscriptions which
-match.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.82">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> name </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> postfix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets any postix used to identify the queue consumers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix wildcard used to identify the queue consumers for a given
-topic</p> <p></p></td></tr></tbody></table></div>
+match.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> name </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="56171cc7-3448-420e-9f41-82275c8bddf5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> postfix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ca6c4bc2-ba72-49fa-b452-69d2f2f902e9" ac:name="html" ac:schema-version="1"><plain-text-body>Sets any postix used to identify the queue consumers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b66d7b3f-9506-43dd-8942-8e48dfde6bb7" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix wildcard used to identify the queue consumers for a given
+topic</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-vmCursor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<vmCursor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-vmCursor-element"><vmCursor></a></em> Element</h3>
-<p> </p><p>Pending messages held</p><p></p>
+<p><structured-macro ac:macro-id="37b5c0e4-e22d-48fe-9b54-0a4c09dae150" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">vmCursor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="vmCursor-element"><link-body><vmCursor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="171d2300-a089-40ba-a1eb-32375b2c4ac1" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages held</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-vmDurableCursor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<vmDurableCursor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-vmDurableCursor-element"><vmDurableCursor></a></em> Element</h3>
-<p> </p><p>Pending</p><p></p>
+<p><structured-macro ac:macro-id="812b8003-8f5d-49ff-9159-576bb627cbb2" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">vmDurableCursor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="vmDurableCursor-element"><link-body><vmDurableCursor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="a579d1e6-7751-4e82-9d9d-a0a27bdeb8af" ac:name="html" ac:schema-version="1"><plain-text-body>Pending</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-vmQueueCursor-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<vmQueueCursor>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-vmQueueCursor-element"><vmQueueCursor></a></em> Element</h3>
-<p> </p><p>Pending messages</p><p></p>
+<p><structured-macro ac:macro-id="4c3530af-f4a8-4da2-82f1-4bcc7744d387" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">vmQueueCursor-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="vmQueueCursor-element"><link-body><vmQueueCursor></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="c94b7c31-8b18-47b9-b9f1-1cffd5ee6a25" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p><p></p>
-<p><span class="confluence-anchor-link" id="XBeanXMLReference5.0-xaConnectionFactory-element"></span></p>
-<h3 id="XBeanXMLReference5.0-The<xaConnectionFactory>Element">The <em><a shape="rect" href="#XBeanXMLReference5.0-xaConnectionFactory-element"><xaConnectionFactory></a></em> Element</h3>
-<p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced XA connection
+<p><structured-macro ac:macro-id="f8de642e-e409-4cf1-938d-a191bd67b90c" ac:name="anchor" ac:schema-version="1"><parameter ac:name="">xaConnectionFactory-element</parameter></structured-macro></p>
+<h3>The <em><link ac:anchor="xaConnectionFactory-element"><link-body><xaConnectionFactory></link-body></link></em> Element</h3>
+<p> </p><p><structured-macro ac:macro-id="c26fe2c5-88a7-4b22-9db3-96ba12f7877e" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p><p></p>
-<h4 id="XBeanXMLReference5.0-Properties.83">Properties</h4>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p> Property Name </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Type </p></th><th colspan="1" rowspan="1" class="confluenceTh"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> alwaysSessionAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>If this flag is set then a separate thread is not used for dispatching
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p><p></p>
+<h4>Properties</h4>
+<table><tbody><tr><th colspan="1" rowspan="1"><p> Property Name </p></th><th colspan="1" rowspan="1"><p> Type </p></th><th colspan="1" rowspan="1"><p> Description </p></th></tr><tr><td colspan="1" rowspan="1"><p> alwaysSessionAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f8ffd6e4-65ed-4366-bdc7-563359ead2d9" ac:name="html" ac:schema-version="1"><plain-text-body>If this flag is set then a separate thread is not used for dispatching
messages for each Session in the Connection. However, a separate thread
is always used if there is more than one session, or the session isn't in
-auto acknowledge or duplicates ok mode</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> alwaysSyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Set true if always require messages to be sync sent</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> beanName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> blobTransferPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.blob.BlobTransferPolicy</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the policy used to describe how out-of-band BLOBs (Binary Large
-OBjects) are transferred from producers to brokers to consumers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> brokerURL </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the <a shape="rect" href="http://activemq.apache.org/configuring-transports.html">connection
-URL</a> used to connect to the ActiveMQ broker.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clientID </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMS clientID to use for the created connection. Note that this
+auto acknowledge or duplicates ok mode</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> alwaysSyncSend </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="98483dd0-a6cd-4597-9fec-72189ab272eb" ac:name="html" ac:schema-version="1"><plain-text-body>Set true if always require messages to be sync sent</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> beanName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="153ad27f-c6df-4ee7-8faf-48e286eabcfc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> blobTransferPolicy </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.blob.BlobTransferPolicy</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="882a6c50-90aa-44b0-be64-21504668ebd8" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the policy used to describe how out-of-band BLOBs (Binary Large
+OBjects) are transferred from producers to brokers to consumers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> brokerURL </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="012d3e4c-dc25-4dbd-9208-48b73ddf77ad" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the <a
+href="http://activemq.apache.org/configuring-transports.html">connection
+URL</a> used to connect to the ActiveMQ broker.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> clientID </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="38fa34f7-9e98-41a3-91af-6fb20e042fb8" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMS clientID to use for the created connection. Note that this
can only be used by one connection at once so generally its a better idea
-to set the clientID on a Connection</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clientIDPrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the prefix used by autogenerated JMS Client ID values which are used
-if the JMS client does not explicitly specify on.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> clientIdGenerator </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.util.IdGenerator</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> closeTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the timeout before a close is considered complete. Normally a
+to set the clientID on a Connection</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> clientIDPrefix </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="abd28a5f-2620-4fd5-961a-95df83f4da55" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the prefix used by autogenerated JMS Client ID values which are used
+if the JMS client does not explicitly specify on.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> clientIdGenerator </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.util.IdGenerator</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e3bc5651-a6f0-4405-8215-8cc995d23113" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> closeTimeout </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="df6c5d61-e0f2-42a9-8106-574b7d739d08" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the timeout before a close is considered complete. Normally a
close() on a connection waits for confirmation from the broker; this
allows that operation to timeout to save the client hanging if there is
-no broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> copyMessageOnSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Should a JMS message be copied to a new JMS Message object as part of the
+no broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> copyMessageOnSend </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f00d30a8-5299-4af7-aa09-660a2c285e95" ac:name="html" ac:schema-version="1"><plain-text-body>Should a JMS message be copied to a new JMS Message object as part of the
send() method in JMS. This is enabled by default to be compliant with the
JMS specification. You can disable it if you do not mutate JMS messages
-after they are sent for a performance boost</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> disableTimeStampsByDefault </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not timestamps on messages should be disabled or not. If
-you disable them it adds a small performance boost.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> dispatchAsync </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables the default setting of whether or not consumers have
-their messages <a shape="rect" href="http://activemq.apache.org/consumer-dispatch-async.html">dispatched
-synchronously or asynchronously by the broker</a>. For non-durable
+after they are sent for a performance boost</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> disableTimeStampsByDefault </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="404506fd-93fa-49fc-b768-b8e3dde850a5" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not timestamps on messages should be disabled or not. If
+you disable them it adds a small performance boost.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> dispatchAsync </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6abce808-854d-4c9b-ba9f-49225480ea6d" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables the default setting of whether or not consumers have
+their messages <a
+href="http://activemq.apache.org/consumer-dispatch-async.html">dispatched
+synchronously or asynchronously by the broker</a>. 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.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> exclusiveConsumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables or disables whether or not queue consumers should be exclusive or
-not for example to preserve ordering when not using <a shape="rect" href="http://activemq.apache.org/message-groups.html">Message Groups</a></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> nestedMapAndListEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables/disables whether or not Message properties and MapMessage entries
-support <a shape="rect" href="http://activemq.apache.org/structured-message-properties-and-mapmessages.html">Nested
-Structures</a> of Map and List objects</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> objectMessageSerializationDefered </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>When an object is set on an ObjectMessage, the JMS spec requires the
+not block delivery to other consumers.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> exclusiveConsumer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3463f444-b674-4b96-b74a-0d631e6d2dc6" ac:name="html" ac:schema-version="1"><plain-text-body>Enables or disables whether or not queue consumers should be exclusive or
+not for example to preserve ordering when not using <a
+href="http://activemq.apache.org/message-groups.html">Message Groups</a></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> nestedMapAndListEnabled </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="234fa9aa-27df-4273-9c63-7cd327c9d1fd" ac:name="html" ac:schema-version="1"><plain-text-body>Enables/disables whether or not Message properties and MapMessage entries
+support <a
+href="http://activemq.apache.org/structured-message-properties-and-mapmessages.html">Nested
+Structures</a> of Map and List objects</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> objectMessageSerializationDefered </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c7bfe87e-8613-4ded-965d-f541c0f20eeb" ac:name="html" ac:schema-version="1"><plain-text-body>When an object is set on an ObjectMessage, the JMS spec requires the
object to be serialized by that set method. Enabling this flag causes the
object to not get serialized. The object may subsequently get serialized
-if the message needs to be sent over a socket or stored to disk.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> optimizeAcknowledge </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> optimizedMessageDispatch </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>If this flag is set then an larger prefetch limit is used - only
-applicable for durable topic subscribers.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> password </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMS password used for connections created from this factory</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> prefetchPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.ActiveMQPrefetchPolicy-types">org.apache.activemq.ActiveMQPrefetchPolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the <a shape="rect" href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch
-policy</a> for consumers created by this connection.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> producerWindowSize </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>int</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> properties </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Get the properties from this instance for storing in JNDI</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> redeliveryPolicy </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-org.apache.activemq.RedeliveryPolicy-types">org.apache.activemq.RedeliveryPolicy</a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the global redelivery policy to be used when a message is delivered
-but the session is rolled back</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> statsEnabled </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transformer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.MessageTransformer</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the transformer used to transform messages before they are sent on
+if the message needs to be sent over a socket or stored to disk.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> optimizeAcknowledge </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1142f685-0fb7-4610-80e1-21326cfe7cfc" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> optimizedMessageDispatch </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d7805d6d-65de-4f5a-ba4c-57907d0abbc0" ac:name="html" ac:schema-version="1"><plain-text-body>If this flag is set then an larger prefetch limit is used - only
+applicable for durable topic subscribers.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> password </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2acc2fb4-7456-42d0-a897-56e3e903e0eb" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMS password used for connections created from this factory</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> prefetchPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.ActiveMQPrefetchPolicy-types"><link-body>org.apache.activemq.ActiveMQPrefetchPolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9cf304d8-9a62-44f3-9285-a05dbe7e9b87" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the <a
+href="http://activemq.apache.org/what-is-the-prefetch-limit-for.html">prefetch
+policy</a> for consumers created by this connection.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> producerWindowSize </p></td><td colspan="1" rowspan="1"><p> <em>int</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cb8936c1-e551-46ba-b07e-20880f620cab" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> properties </p></td><td colspan="1" rowspan="1"><p> <em>java.util.Properties</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="273796a2-7b27-42cd-8891-77da0d2062ea" ac:name="html" ac:schema-version="1"><plain-text-body>Get the properties from this instance for storing in JNDI</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> redeliveryPolicy </p></td><td colspan="1" rowspan="1"><p> <em><link ac:anchor="org.apache.activemq.RedeliveryPolicy-types"><link-body>org.apache.activemq.RedeliveryPolicy</link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2e058987-e504-4256-b854-1de0f6f56eeb" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the global redelivery policy to be used when a message is delivered
+but the session is rolled back</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> statsEnabled </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="329ffe14-a77a-434c-8ed3-b85f1e47e9a5" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> transformer </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.MessageTransformer</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="491df12d-fe57-411d-bf94-bc4e53dad3e2" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the transformer used to transform messages before they are sent on
to the JMS bus or when they are received from the bus but before they are
-delivered to the JMS client</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> transportListener </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>org.apache.activemq.transport.TransportListener</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Allows a listener to be configured on the ConnectionFactory so that when this factory is used
+delivered to the JMS client</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> transportListener </p></td><td colspan="1" rowspan="1"><p> <em>org.apache.activemq.transport.TransportListener</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7c2c088c-b1c6-4f4d-ad31-ce6c9eec7a5b" ac:name="html" ac:schema-version="1"><plain-text-body>Allows a listener to be configured on the ConnectionFactory so that when this factory is used
with frameworks which don't expose the Connection such as Spring JmsTemplate, you can still register
-a transport listener.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useAsyncSend </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forces the use of <a shape="rect" href="http://activemq.apache.org/async-sends.html">Async Sends</a> which
+a transport listener.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useAsyncSend </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="735cf3a3-c726-44e7-82e1-0f79a5fdada1" ac:name="html" ac:schema-version="1"><plain-text-body>Forces the use of <a
+href="http://activemq.apache.org/async-sends.html">Async Sends</a> 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.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useBeanNameAsClientIdPrefix </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useCompression </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables the use of compression of the message bodies</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> useRetroactiveConsumer </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets whether or not retroactive consumers are enabled. Retroactive
+lead to message loss.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useBeanNameAsClientIdPrefix </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="883f609e-98e7-4334-9e8d-97561b3cd95b" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useCompression </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cda1c261-f0de-4096-94d4-73807aa1c948" ac:name="html" ac:schema-version="1"><plain-text-body>Enables the use of compression of the message bodies</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> useRetroactiveConsumer </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3a7041d5-6bc4-476b-9022-17b5aff2aef6" ac:name="html" ac:schema-version="1"><plain-text-body>Sets whether or not retroactive consumers are enabled. Retroactive
consumers allow non-durable topic subscribers to receive old messages
-that were published before the non-durable subscriber started.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> userName </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Sets the JMS userName used by connections created by this factory</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> warnAboutUnstartedConnectionTimeout </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>long</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Enables the timeout from a connection creation to when a warning is
+that were published before the non-durable subscriber started.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> userName </p></td><td colspan="1" rowspan="1"><p> <em>java.lang.String</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2fe9cfce-1cbb-429d-baeb-1e98a309d2ec" ac:name="html" ac:schema-version="1"><plain-text-body>Sets the JMS userName used by connections created by this factory</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> warnAboutUnstartedConnectionTimeout </p></td><td colspan="1" rowspan="1"><p> <em>long</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7f0b1a40-dbf9-4544-aef6-8adc9ddc145b" ac:name="html" ac:schema-version="1"><plain-text-body>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 <a shape="rect" href="http://activemq.apache.org/i-am-not-receiving-any-messages-what-is-wrong.html">start
-the connection</a> so this option makes the default case to create a
+a very common gotcha to forget to <a
+href="http://activemq.apache.org/i-am-not-receiving-any-messages-what-is-wrong.html">start
+the connection</a> 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).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> watchTopicAdvisories </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr></tbody></table></div>
+0 (say -1).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> watchTopicAdvisories </p></td><td colspan="1" rowspan="1"><p> <em>boolean</em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ae523081-fab2-4796-b895-712eefb9ad03" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr></tbody></table>
-<h3 id="XBeanXMLReference5.0-ElementIndex">Element Index</h3>
-<div class="table-wrap"><table class="confluenceTable"><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-amqPersistenceAdapter-element"><amqPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a
+<h3>Element Index</h3>
+<table><tbody><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="amqPersistenceAdapter-element"><link-body><amqPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b3eed2d4-fc02-4835-b5db-09dcd12f7e9a" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a
{@link Journal} and then check pointing asynchronously on a timeout with some
-other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-amqPersistenceAdapterFactory-element"><amqPersistenceAdapterFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapterFactory}</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-authenticationUser-element"><authenticationUser></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A helper object used to configure simple authentiaction plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationEntry-element"><authorizationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
+other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="amqPersistenceAdapterFactory-element"><link-body><amqPersistenceAdapterFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dd5e9d3c-2de6-4d90-bbe1-449270ce5049" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapterFactory}</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authenticationUser-element"><link-body><authenticationUser></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="74b4363a-82d5-4bf3-aac5-f75a98745a06" ac:name="html" ac:schema-version="1"><plain-text-body>A helper object used to configure simple authentiaction plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationEntry-element"><link-body><authorizationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ea138c39-2e75-4e41-8a3f-34daa7359b02" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
different operations (read, write, admin) of user roles to a specific
-destination or a hierarchical wildcard area of destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationMap-element"><authorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual
+destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationMap-element"><link-body><authorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e6025ef3-f625-407f-b7c7-5c714ee7884b" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
different policies. Each entry in the map represents the authorization ACLs
-for each operation.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-authorizationPlugin-element"><authorizationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An authorization plugin where each operation on a destination is checked
-against an authorizationMap</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-axionJDBCAdapter-element"><axionJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Axion specific Adapter.
+for each operation.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="authorizationPlugin-element"><link-body><authorizationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="09ca51c2-ab4b-4dda-89c6-03bc25019cfa" ac:name="html" ac:schema-version="1"><plain-text-body>An authorization plugin where each operation on a destination is checked
+against an authorizationMap</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="axionJDBCAdapter-element"><link-body><axionJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f5b8240b-aa63-4104-9240-f92306b6edb0" ac:name="html" ac:schema-version="1"><plain-text-body>Axion specific Adapter.
Axion does not seem to support ALTER statements or sub-selects. This means:
- We cannot auto upgrade the schema was we roll out new versions of ActiveMQ
-- We cannot delete durable sub messages that have be acknowledged by all consumers.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-blobJDBCAdapter-element"><blobJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob()
+- We cannot delete durable sub messages that have be acknowledged by all consumers.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="blobJDBCAdapter-element"><link-body><blobJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6f20a745-230c-4aa7-a2bf-123ec4d479bb" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the getBlob()/setBlob()
operations. This is a little more involved since to insert a blob you have
to:
@@ -1410,109 +1455,124 @@
value.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-broker-element"><broker></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Message Broker. It consists of a number of transport
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="broker-element"><link-body><broker></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cb992afe-921b-443d-9493-95d1d196005d" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Message Broker. It consists of a number of transport
connectors, network connectors and a bunch of properties which can be used to
-configure the broker as its lazily created.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-bytesJDBCAdapter-element"><bytesJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the
+configure the broker as its lazily created.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="bytesJDBCAdapter-element"><link-body><bytesJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2c5c360a-315d-43b1-90d9-317a0e7ecee1" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the
setBytes()/getBytes() operations. The databases/JDBC drivers that use this
-adapter are:</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-commandAgent-element"><commandAgent></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An agent which listens to commands on a JMS destination</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-compositeDemandForwardingBridge-element"><compositeDemandForwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A demand forwarding bridge which works with multicast style transports where
-a single Transport could be communicating with multiple remote brokers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-compositeQueue-element"><compositeQueue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a virtual queue which forwards to a number of other destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-compositeTopic-element"><compositeTopic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a virtual topic which forwards to a number of other destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-connectionDotFilePlugin-element"><connectionDotFilePlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a> file creator plugin which
-creates a DOT file showing the current connections</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-connectionFactory-element"><connectionFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced connection
+adapter are:</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="commandAgent-element"><link-body><commandAgent></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fadf9fdf-dc9e-4d2e-a2a7-fbe091dd2b80" ac:name="html" ac:schema-version="1"><plain-text-body>An agent which listens to commands on a JMS destination</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeDemandForwardingBridge-element"><link-body><compositeDemandForwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3a26ba60-4f2f-4c4c-a366-f7fa1d930960" ac:name="html" ac:schema-version="1"><plain-text-body>A demand forwarding bridge which works with multicast style transports where
+a single Transport could be communicating with multiple remote brokers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeQueue-element"><link-body><compositeQueue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="eb0b762f-0c8d-45de-ad49-6f0b194e36e8" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual queue which forwards to a number of other destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="compositeTopic-element"><link-body><compositeTopic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="166490de-96fc-44ca-81b9-19e11f808d43" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a virtual topic which forwards to a number of other destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="connectionDotFilePlugin-element"><link-body><connectionDotFilePlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3ab3be69-3916-4f3a-96f1-b97e94b9217d" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a> file creator plugin which
+creates a DOT file showing the current connections</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="connectionFactory-element"><link-body><connectionFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6e8b4d4d-3b88-4292-9ac7-b4bd85433e66" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-constantPendingMessageLimitStrategy-element"><constantPendingMessageLimitStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-db2JDBCAdapter-element"><db2JDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-defaultJDBCAdapter-element"><defaultJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements all the default JDBC operations that are used by the
-JDBCPersistenceAdapter. </p><p></p> sub-classing is encouraged to override the
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="constantPendingMessageLimitStrategy-element"><link-body><constantPendingMessageLimitStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e37f74bd-4fdd-48f0-8c81-e71f299ac2fd" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy is configured to a constant value for all subscriptions.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="db2JDBCAdapter-element"><link-body><db2JDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c0fe0f6b-131f-4b8d-be7c-ed46814f470d" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="defaultJDBCAdapter-element"><link-body><defaultJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b9ee9992-57b5-4226-8390-97ff164e0442" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used by the
+JDBCPersistenceAdapter. <p/> sub-classing is encouraged to override the
default implementation of methods to account for differences in JDBC Driver
-implementations. <p></p> The JDBCAdapter inserts and extracts BLOB data using
-the getBytes()/setBytes() operations. <p></p> The databases/JDBC drivers that
+implementations. <p/> The JDBCAdapter inserts and extracts BLOB data using
+the getBytes()/setBytes() operations. <p/> The databases/JDBC drivers that
use this adapter are:
-<ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-defaultUsageCapacity-element"><defaultUsageCapacity></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Identify if a limit has been reached</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-demandForwardingBridge-element"><demandForwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forwards messages from the local broker to the remote broker based on demand.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-destinationDotFilePlugin-element"><destinationDotFilePlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.graphviz.org/">DOT</a>
-file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-destinationEntry-element"><destinationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A default entry in a DestinationMap which holds a single value.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fileCursor-element"><fileCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fileDurableSubscriberCursor-element"><fileDurableSubscriberCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages for durable subscribers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fileQueueCursor-element"><fileQueueCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-filteredDestination-element"><filteredDestination></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination which is filtered using some predicate such as a selector
-so that messages are only dispatched to the destination if they match the filter.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fixedCountSubscriptionRecoveryPolicy-element"><fixedCountSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
-count of last messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-fixedSizedSubscriptionRecoveryPolicy-element"><fixedSizedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="defaultUsageCapacity-element"><link-body><defaultUsageCapacity></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7b465d0e-0ae2-4947-a464-85c064478741" ac:name="html" ac:schema-version="1"><plain-text-body>Identify if a limit has been reached</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="demandForwardingBridge-element"><link-body><demandForwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="167bf910-1ce6-4d6c-a2d7-e7dfd7484191" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards messages from the local broker to the remote broker based on demand.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="destinationDotFilePlugin-element"><link-body><destinationDotFilePlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2f9ddd41-746b-45b8-96d0-4e9f2e997f61" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.graphviz.org/">DOT</a>
+file creator plugin which creates a DOT file showing the current topic & queue hierarchies.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="destinationEntry-element"><link-body><destinationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="689c4505-72d3-4e1c-831d-02773d885aec" ac:name="html" ac:schema-version="1"><plain-text-body>A default entry in a DestinationMap which holds a single value.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fileCursor-element"><link-body><fileCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8580b803-7bb3-4cbc-8b22-5a1281d8a004" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fileDurableSubscriberCursor-element"><link-body><fileDurableSubscriberCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="00371a7d-99be-437c-be61-c431d1a01b60" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages for durable subscribers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fileQueueCursor-element"><link-body><fileQueueCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4d128d21-2d33-4d37-9345-11d9a697f987" ac:name="html" ac:schema-version="1"><plain-text-body>Pending</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="filteredDestination-element"><link-body><filteredDestination></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bb02666c-6ace-4252-b23b-deecae59e744" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination which is filtered using some predicate such as a selector
+so that messages are only dispatched to the destination if they match the filter.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fixedCountSubscriptionRecoveryPolicy-element"><link-body><fixedCountSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a15e5380-d486-4039-84c1-86d2e28ae1a2" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
+count of last messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="fixedSizedSubscriptionRecoveryPolicy-element"><link-body><fixedSizedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f725b292-69b2-4920-98b0-5be72bd5a35a" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a fixed
amount of memory available in RAM for message history which is evicted in
-time order.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-forwardingBridge-element"><forwardingBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Forwards all messages from the local broker to the remote broker.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-imageBasedJDBCAdaptor-element"><imageBasedJDBCAdaptor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides JDBCAdapter since that uses
+time order.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="forwardingBridge-element"><link-body><forwardingBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8832ead5-e420-452d-8480-c2c8addce3a0" ac:name="html" ac:schema-version="1"><plain-text-body>Forwards all messages from the local broker to the remote broker.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="imageBasedJDBCAdaptor-element"><link-body><imageBasedJDBCAdaptor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="1dd59dff-8ac3-4104-8202-cd86956dad5e" ac:name="html" ac:schema-version="1"><plain-text-body>Provides JDBCAdapter since that uses
IMAGE datatype to hold binary data.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li>Sybase</li><li>MS SQL</li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-inboundQueueBridge-element"><inboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Queue Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-inboundTopicBridge-element"><inboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Inbound Topic Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-individualDeadLetterStrategy-element"><individualDeadLetterStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link DeadLetterStrategy} where each destination has its own individual
-DLQ using the subject naming hierarchy.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-informixJDBCAdapter-element"><informixJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>JDBC Adapter for Informix database.
+<ul>
+<li>Sybase</li>
+<li>MS SQL</li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundQueueBridge-element"><link-body><inboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="436480cc-9be7-4727-989a-b4db790f99d3" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="inboundTopicBridge-element"><link-body><inboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d732e8c5-402d-4a33-8ab0-d76abd413835" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Inbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="individualDeadLetterStrategy-element"><link-body><individualDeadLetterStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fb3927a3-4948-4414-8b66-87b4d7121748" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link DeadLetterStrategy} where each destination has its own individual
+DLQ using the subject naming hierarchy.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="informixJDBCAdapter-element"><link-body><informixJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="050877fd-2321-4be5-8448-9c1910def4f3" ac:name="html" ac:schema-version="1"><plain-text-body>JDBC Adapter for Informix database.
Because Informix database restricts length of composite primary keys, length of
-<i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters.
-Therefore be sure not to use longer names for container name and subscription id than 150 characters.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jaasAuthenticationPlugin-element"><jaasAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a JAAS based authentication plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jaasCertificateAuthenticationPlugin-element"><jaasCertificateAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a JAAS based SSL certificate authentication plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jdbcPersistenceAdapter-element"><jdbcPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A {@link PersistenceAdapter} implementation using JDBC for persistence
+<i>container name</i> field and <i>subscription id</i> field must be reduced to 150 characters.
+Therefore be sure not to use longer names for container name and subscription id than 150 characters.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jaasAuthenticationPlugin-element"><link-body><jaasAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="139e33e2-51f0-45b5-9909-8626da5709f3" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based authentication plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jaasCertificateAuthenticationPlugin-element"><link-body><jaasCertificateAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3c4d5fc0-dd7b-4190-becb-fd6976e07ad9" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a JAAS based SSL certificate authentication plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jdbcPersistenceAdapter-element"><link-body><jdbcPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="31cf06a6-243e-4901-b3e2-2b6c2d4ffbcc" ac:name="html" ac:schema-version="1"><plain-text-body>A {@link PersistenceAdapter} implementation using JDBC for persistence
storage.
This persistence adapter will correctly remember prepared XA transactions,
but it will not keep track of local transaction commits so that operations
-performed against the Message store are done as a single uow.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jmsQueueConnector-element"><jmsQueueConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Queue providers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-jmsTopicConnector-element"><jmsTopicConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Bridge to other JMS Topic providers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-journalPersistenceAdapter-element"><journalPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An implementation of {@link PersistenceAdapter} designed for use with a
+performed against the Message store are done as a single uow.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsQueueConnector-element"><link-body><jmsQueueConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c7825df0-8b68-4465-b0a7-ba3e3cff413d" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Queue providers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="jmsTopicConnector-element"><link-body><jmsTopicConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bde3c045-1a79-4417-a78b-e5dec9f57696" ac:name="html" ac:schema-version="1"><plain-text-body>A Bridge to other JMS Topic providers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="journalPersistenceAdapter-element"><link-body><journalPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="edd677c9-a032-4a6f-bf58-d13f0edf19fe" ac:name="html" ac:schema-version="1"><plain-text-body>An implementation of {@link PersistenceAdapter} designed for use with a
{@link Journal} and then check pointing asynchronously on a timeout with some
-other long term persistent storage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-journaledJDBC-element"><journaledJDBC></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates a default persistence model using the Journal and JDBC</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-kahaPersistenceAdapter-element"><kahaPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-lDAPAuthorizationMap-element"><lDAPAuthorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An {@link AuthorizationMap} which uses LDAP</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-lastImageSubscriptionRecoveryPolicy-element"><lastImageSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the
-last message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-ldapNetworkConnector-element"><ldapNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>class to create dynamic network connectors listed in an directory
+other long term persistent storage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="journaledJDBC-element"><link-body><journaledJDBC></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c4c094f0-ed06-4a30-9480-d01def162538" ac:name="html" ac:schema-version="1"><plain-text-body>Creates a default persistence model using the Journal and JDBC</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="kahaPersistenceAdapter-element"><link-body><kahaPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8f290aca-6e1e-469d-b04b-da0f63a53d32" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="lDAPAuthorizationMap-element"><link-body><lDAPAuthorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="aa01bd03-060c-4879-bc75-ddd892f28519" ac:name="html" ac:schema-version="1"><plain-text-body>An {@link AuthorizationMap} which uses LDAP</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="lastImageSubscriptionRecoveryPolicy-element"><link-body><lastImageSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0ff1dd35-95ef-46fa-a418-a197fe6c207d" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will only keep the
+last message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="ldapNetworkConnector-element"><link-body><ldapNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ae9e7ccb-395e-42ce-821b-ff61000cc57b" ac:name="html" ac:schema-version="1"><plain-text-body>class to create dynamic network connectors listed in an directory
server using the LDAP v3 protocol as defined in RFC 2251, the
entries listed in the directory server must implement the ipHost
-and ipService objectClasses as defined in RFC 2307.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-loggingBrokerPlugin-element"><loggingBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A simple Broker interceptor which allows you to enable/disable logging.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-managementContext-element"><managementContext></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Flow provides different dispatch policies within the NMR</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-masterConnector-element"><masterConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Connects a Slave Broker to a Master when using <a shape="rect" href="http://activemq.apache.org/masterslave.html">Master Slave</a> for High
-Availability of messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-memoryPersistenceAdapter-element"><memoryPersistenceAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-memoryUsage-element"><memoryUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+and ipService objectClasses as defined in RFC 2307.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="loggingBrokerPlugin-element"><link-body><loggingBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="5ed868ce-5f30-419f-aedb-c39c45317449" ac:name="html" ac:schema-version="1"><plain-text-body>A simple Broker interceptor which allows you to enable/disable logging.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="managementContext-element"><link-body><managementContext></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="48b8a5b5-d157-46db-ace9-cc4be614829f" ac:name="html" ac:schema-version="1"><plain-text-body>A Flow provides different dispatch policies within the NMR</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="masterConnector-element"><link-body><masterConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c9456d52-fcf6-4adc-a909-4632232af0a6" ac:name="html" ac:schema-version="1"><plain-text-body>Connects a Slave Broker to a Master when using <a
+href="http://activemq.apache.org/masterslave.html">Master Slave</a> for High
+Availability of messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="memoryPersistenceAdapter-element"><link-body><memoryPersistenceAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="dfbefc44-e994-497f-b60e-885cc0923636" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="memoryUsage-element"><link-body><memoryUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="fb95fef7-d14f-46f0-a76b-d003b8e20022" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-messageGroupHashBucketFactory-element"><messageGroupHashBucketFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A factory to create instances of {@link SimpleMessageGroupMap} when
-implementing the <a shape="rect" href="http://activemq.apache.org/message-groups.html">Message
-Groups</a> functionality.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-mirroredQueue-element"><mirroredQueue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/mirrored-queues.html">Mirrored
-Queue</a> using a prefix and postfix to define the topic name on which to mirror the queue to.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-multicastNetworkConnector-element"><multicastNetworkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses some kind of multicast-like transport that
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="messageGroupHashBucketFactory-element"><link-body><messageGroupHashBucketFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="4ef02fe4-f288-4727-bb55-78acf6250acc" ac:name="html" ac:schema-version="1"><plain-text-body>A factory to create instances of {@link SimpleMessageGroupMap} when
+implementing the <a
+href="http://activemq.apache.org/message-groups.html">Message
+Groups</a> functionality.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="mirroredQueue-element"><link-body><mirroredQueue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="091b61be-cd63-4c27-8e92-3b65f045a1c1" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/mirrored-queues.html">Mirrored
+Queue</a> using a prefix and postfix to define the topic name on which to mirror the queue to.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="multicastNetworkConnector-element"><link-body><multicastNetworkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="741a8843-806c-4c92-ad88-3acaa8a813e4" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses some kind of multicast-like transport that
communicates with potentially many remote brokers over a single logical
{@link Transport} instance such as when using multicast.
This implementation does not depend on multicast at all; any other group
-based transport could be used.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-multicastTraceBrokerPlugin-element"><multicastTraceBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which allows you to trace all operations to a Multicast
-socket.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-networkConnector-element"><networkConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A network connector which uses a discovery agent to detect the remote brokers
-available and setup a connection to each available remote broker</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-noSubscriptionRecoveryPolicy-element"><noSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This SubscriptionRecoveryPolicy disable recovery of messages.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-oldestMessageEvictionStrategy-element"><oldestMessageEvictionStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An eviction strategy which evicts the oldest message first (which is the
-default).</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-oldestMessageWithLowestPriorityEvictionStrategy-element"><oldestMessageWithLowestPriorityEvictionStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An eviction strategy which evicts the oldest message with the lowest priority first.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-oracleJDBCAdapter-element"><oracleJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements all the default JDBC operations that are used
+based transport could be used.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="multicastTraceBrokerPlugin-element"><link-body><multicastTraceBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="f3d88539-c40d-4305-be83-3a1c8ae8e95c" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which allows you to trace all operations to a Multicast
+socket.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="networkConnector-element"><link-body><networkConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="bbce7a34-c45f-4067-acd0-7e91a806a43b" ac:name="html" ac:schema-version="1"><plain-text-body>A network connector which uses a discovery agent to detect the remote brokers
+available and setup a connection to each available remote broker</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="noSubscriptionRecoveryPolicy-element"><link-body><noSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7f058f1f-32fa-4335-a173-402126dc9c26" ac:name="html" ac:schema-version="1"><plain-text-body>This SubscriptionRecoveryPolicy disable recovery of messages.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oldestMessageEvictionStrategy-element"><link-body><oldestMessageEvictionStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a2a8c5c3-5d7a-4039-943a-b9b9189deb80" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message first (which is the
+default).</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oldestMessageWithLowestPriorityEvictionStrategy-element"><link-body><oldestMessageWithLowestPriorityEvictionStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="18e9a92b-4b78-441f-a1e2-38560517d4ee" ac:name="html" ac:schema-version="1"><plain-text-body>An eviction strategy which evicts the oldest message with the lowest priority first.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="oracleJDBCAdapter-element"><link-body><oracleJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d9709884-df10-4534-8ed3-995203e42155" ac:name="html" ac:schema-version="1"><plain-text-body>Implements all the default JDBC operations that are used
by the JDBCPersistenceAdapter.
-</p><p></p>
+<p/>
Subclassing is encouraged to override the default
implementation of methods to account for differences
in JDBC Driver implementations.
-<p></p>
+<p/>
The JDBCAdapter inserts and extracts BLOB data using the
getBytes()/setBytes() operations.
-<p></p>
+<p/>
The databases/JDBC drivers that use this adapter are:
-<ul><li></li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-outboundQueueBridge-element"><outboundQueueBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Queue Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-outboundTopicBridge-element"><outboundTopicBridge></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Create an Outbound Topic Bridge</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-policyEntry-element"><policyEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link PolicyMap} for assigning policies to a
-specific destination or a hierarchical wildcard area of destinations.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-policyMap-element"><policyMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents a destination based configuration of policies so that individual
+<ul>
+<li></li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundQueueBridge-element"><link-body><outboundQueueBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="6ba65379-7a43-4403-a419-4ffa5bf7ac84" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Queue Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="outboundTopicBridge-element"><link-body><outboundTopicBridge></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="49025017-b39d-46f3-be4b-aaa73da98b24" ac:name="html" ac:schema-version="1"><plain-text-body>Create an Outbound Topic Bridge</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyEntry-element"><link-body><policyEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="caef0705-d04c-44c1-ba0f-52b588816b26" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link PolicyMap} for assigning policies to a
+specific destination or a hierarchical wildcard area of destinations.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="policyMap-element"><link-body><policyMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3922eb00-3327-4313-894b-d0077de96634" ac:name="html" ac:schema-version="1"><plain-text-body>Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
-different policies.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-prefetchPolicy-element"><prefetchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Defines the prefetch message policies for different types of consumers</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-prefetchRatePendingMessageLimitStrategy-element"><prefetchRatePendingMessageLimitStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This PendingMessageLimitStrategy sets the maximum pending message limit value to be
-a multiplier of the prefetch limit of the subscription.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-proxyConnector-element"><proxyConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-queryBasedSubscriptionRecoveryPolicy-element"><queryBasedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user
-specific query mechanism to load any messages they may have missed.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-queue-element"><queue></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Queue</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-redeliveryPolicy-element"><redeliveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Configuration options used to control how messages are re-delivered when they
-are rolled back.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-roundRobinDispatchPolicy-element"><roundRobinDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Simple dispatch policy that sends a message to every subscription that
-matches the message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-sharedDeadLetterStrategy-element"><sharedDeadLetterStrategy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A default implementation of {@link DeadLetterStrategy} which uses
-a constant destination.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleAuthenticationPlugin-element"><simpleAuthenticationPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Provides a simple authentication plugin</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleAuthorizationMap-element"><simpleAuthorizationMap></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An AuthorizationMap which is configured with individual DestinationMaps for
-each operation.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleDispatchPolicy-element"><simpleDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Simple dispatch policy that sends a message to every subscription that
-matches the message.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleJmsMessageConvertor-element"><simpleJmsMessageConvertor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Converts Message from one JMS to another</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-simpleMessageGroupMapFactory-element"><simpleMessageGroupMapFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A factory to create instances of {@link SimpleMessageGroupMap} when implementing the
-<a shape="rect" href="http://activemq.apache.org/message-groups.html">Message Groups</a> functionality.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-statements-element"><statements></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-storeCursor-element"><storeCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-storeDurableSubscriberCursor-element"><storeDurableSubscriberCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages for a durable</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-storeUsage-element"><storeUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+different policies.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="prefetchPolicy-element"><link-body><prefetchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b2787e4c-1a1e-459d-ae40-a2be21ce11a7" ac:name="html" ac:schema-version="1"><plain-text-body>Defines the prefetch message policies for different types of consumers</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="prefetchRatePendingMessageLimitStrategy-element"><link-body><prefetchRatePendingMessageLimitStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="ebfc3ab9-18e6-457b-a4e9-aafd6f6856b5" ac:name="html" ac:schema-version="1"><plain-text-body>This PendingMessageLimitStrategy sets the maximum pending message limit value to be
+a multiplier of the prefetch limit of the subscription.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="proxyConnector-element"><link-body><proxyConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="586ab473-3953-40f0-9930-82915501b143" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queryBasedSubscriptionRecoveryPolicy-element"><link-body><queryBasedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="afd47c90-58c6-4bb1-8d11-b6fa0095b66f" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will perform a user
+specific query mechanism to load any messages they may have missed.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="queue-element"><link-body><queue></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b7210f61-95bd-4fd0-a38f-39225b38f9f1" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Queue</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="redeliveryPolicy-element"><link-body><redeliveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cfc551bb-e9be-4a67-996a-9106487f0979" ac:name="html" ac:schema-version="1"><plain-text-body>Configuration options used to control how messages are re-delivered when they
+are rolled back.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="roundRobinDispatchPolicy-element"><link-body><roundRobinDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="3dfb60e1-0089-47f0-8f42-bc62bf06e961" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that
+matches the message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="sharedDeadLetterStrategy-element"><link-body><sharedDeadLetterStrategy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e1ed65a9-8c29-4ef3-9ec0-aec5c6e8050c" ac:name="html" ac:schema-version="1"><plain-text-body>A default implementation of {@link DeadLetterStrategy} which uses
+a constant destination.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleAuthenticationPlugin-element"><link-body><simpleAuthenticationPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9ecee1fe-bac9-4409-bb0a-2923268e0f85" ac:name="html" ac:schema-version="1"><plain-text-body>Provides a simple authentication plugin</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleAuthorizationMap-element"><link-body><simpleAuthorizationMap></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="06a4b0ab-75ac-4ce2-801f-690b9e69c371" ac:name="html" ac:schema-version="1"><plain-text-body>An AuthorizationMap which is configured with individual DestinationMaps for
+each operation.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleDispatchPolicy-element"><link-body><simpleDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c8562373-a061-49bb-919b-2788fc7d2c25" ac:name="html" ac:schema-version="1"><plain-text-body>Simple dispatch policy that sends a message to every subscription that
+matches the message.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleJmsMessageConvertor-element"><link-body><simpleJmsMessageConvertor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cdb9f255-4c23-4233-a1b5-e17e9e2c581d" ac:name="html" ac:schema-version="1"><plain-text-body>Converts Message from one JMS to another</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="simpleMessageGroupMapFactory-element"><link-body><simpleMessageGroupMapFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="21196d22-5e87-486c-a4f3-48bae6700647" ac:name="html" ac:schema-version="1"><plain-text-body>A factory to create instances of {@link SimpleMessageGroupMap} when implementing the
+<a href="http://activemq.apache.org/message-groups.html">Message Groups</a> functionality.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="statements-element"><link-body><statements></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="80695ad8-0830-4456-9428-770ac7fcd4c6" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="storeCursor-element"><link-body><storeCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e6ba476d-b294-49dc-8075-a2e89ae56d1d" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="storeDurableSubscriberCursor-element"><link-body><storeDurableSubscriberCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="2fb9f126-cffa-4cf9-a67a-25dbbdb40508" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages for a durable</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="storeUsage-element"><link-body><storeUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9e9e1150-7df6-4d16-b059-a4d1303c053f" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-streamJDBCAdapter-element"><streamJDBCAdapter></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This JDBCAdapter inserts and extracts BLOB data using the
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="streamJDBCAdapter-element"><link-body><streamJDBCAdapter></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a0f85084-18c8-437d-86f3-4c589877e2b4" ac:name="html" ac:schema-version="1"><plain-text-body>This JDBCAdapter inserts and extracts BLOB data using the
setBinaryStream()/getBinaryStream() operations.
The databases/JDBC drivers that use this adapter are:
-</p><ul><li>Axion</li></ul> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-strictOrderDispatchPolicy-element"><strictOrderDispatchPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Dispatch policy that causes every subscription to see messages in the same
-order.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-systemUsage-element"><systemUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Holder for Usage instances for memory, store and temp files Main use case is
-manage memory usage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-tempDestinationAuthorizationEntry-element"><tempDestinationAuthorizationEntry></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
+<ul>
+<li>Axion</li>
+</ul></plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="strictOrderDispatchPolicy-element"><link-body><strictOrderDispatchPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="cb8f9043-4637-4a36-b5a1-8583ae860287" ac:name="html" ac:schema-version="1"><plain-text-body>Dispatch policy that causes every subscription to see messages in the same
+order.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="systemUsage-element"><link-body><systemUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a3579854-8376-44c4-88dd-f41c943b0e24" ac:name="html" ac:schema-version="1"><plain-text-body>Holder for Usage instances for memory, store and temp files Main use case is
+manage memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="tempDestinationAuthorizationEntry-element"><link-body><tempDestinationAuthorizationEntry></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d16c43e4-062b-4577-a6a8-b7beaa4b3f26" ac:name="html" ac:schema-version="1"><plain-text-body>Represents an entry in a {@link DefaultAuthorizationMap} for assigning
different operations (read, write, admin) of user roles to a temporary
-destination</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-tempUsage-element"><tempUsage></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Used to keep track of how much of something is being used so that a
+destination</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="tempUsage-element"><link-body><tempUsage></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="d3fd182a-9a35-42de-b57c-a9321c5436e8" ac:name="html" ac:schema-version="1"><plain-text-body>Used to keep track of how much of something is being used so that a
productive working set usage can be controlled. Main use case is manage
-memory usage.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-timeStampingBrokerPlugin-element"><timeStampingBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which updates a JMS Client's timestamp on the message
+memory usage.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="timeStampingBrokerPlugin-element"><link-body><timeStampingBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b60072e8-3285-4937-973f-96ce3802845a" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which updates a JMS Client's timestamp on the message
with a broker timestamp. Useful when the clocks on client machines are known
to not be correct and you can only trust the time set on the broker machines.
Enabling this plugin will break JMS compliance since the timestamp that the
producer sees on the messages after as send() will be different from the
timestamp the consumer will observe when he receives the message. This plugin
-is not enabled in the default ActiveMQ configuration.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-timedSubscriptionRecoveryPolicy-element"><timedSubscriptionRecoveryPolicy></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed
+is not enabled in the default ActiveMQ configuration.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="timedSubscriptionRecoveryPolicy-element"><link-body><timedSubscriptionRecoveryPolicy></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="df37151c-05e8-4780-9504-8af5c84e2fdd" ac:name="html" ac:schema-version="1"><plain-text-body>This implementation of {@link SubscriptionRecoveryPolicy} will keep a timed
buffer of messages around in memory and use that to recover new
-subscriptions.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-topic-element"><topic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>An ActiveMQ Topic</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-transportConnector-element"><transportConnector></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p></p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-udpTraceBrokerPlugin-element"><udpTraceBrokerPlugin></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A Broker interceptor which allows you to trace all operations to a UDP
-socket.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-usageCapacity-element"><usageCapacity></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Identify if a limit has been reached</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-virtualDestinationInterceptor-element"><virtualDestinationInterceptor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Implements <a shape="rect" href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a>.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-virtualTopic-element"><virtualTopic></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Creates <a shape="rect" href="http://activemq.org/site/virtual-destinations.html">Virtual
-Topics</a> using a prefix and postfix. The virtual destination creates a
+subscriptions.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="topic-element"><link-body><topic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="7f81127d-98b7-4ac4-a27b-1bd3fb50ee60" ac:name="html" ac:schema-version="1"><plain-text-body>An ActiveMQ Topic</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="transportConnector-element"><link-body><transportConnector></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="0651ce9a-b6ef-4470-838f-7eee0cc8de62" ac:name="html" ac:schema-version="1"></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="udpTraceBrokerPlugin-element"><link-body><udpTraceBrokerPlugin></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="de605b85-f3e9-4b63-918d-69a98967d1cb" ac:name="html" ac:schema-version="1"><plain-text-body>A Broker interceptor which allows you to trace all operations to a UDP
+socket.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="usageCapacity-element"><link-body><usageCapacity></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="a01833a0-98a6-486a-85cf-4061bde9680d" ac:name="html" ac:schema-version="1"><plain-text-body>Identify if a limit has been reached</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="virtualDestinationInterceptor-element"><link-body><virtualDestinationInterceptor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="9fa92508-0ab9-47d7-ac65-871782b38743" ac:name="html" ac:schema-version="1"><plain-text-body>Implements <a
+href="http://activemq.apache.org/virtual-destinations.html">Virtual Topics</a>.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="virtualTopic-element"><link-body><virtualTopic></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="e5fb1b0e-f0aa-406a-bc89-c43b91a1c6c2" ac:name="html" ac:schema-version="1"><plain-text-body>Creates <a href="http://activemq.org/site/virtual-destinations.html">Virtual
+Topics</a> using a prefix and postfix. The virtual destination creates a
wildcard that is then used to look up all active queue subscriptions which
-match.</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-vmCursor-element"><vmCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages held</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-vmDurableCursor-element"><vmDurableCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-vmQueueCursor-element"><vmQueueCursor></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>Pending messages</p> <p></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p> <em><a shape="rect" href="#XBeanXMLReference5.0-xaConnectionFactory-element"><xaConnectionFactory></a></em> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p><p>A <a shape="rect" href="http://www.springframework.org/">Spring</a> enhanced XA connection
+match.</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="vmCursor-element"><link-body><vmCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b3d1cc6b-54ac-4799-9719-5802a2d80e18" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages held</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="vmDurableCursor-element"><link-body><vmDurableCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="c35d8fec-a7b6-478e-ae04-c0ea1aec7e7d" ac:name="html" ac:schema-version="1"><plain-text-body>Pending</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="vmQueueCursor-element"><link-body><vmQueueCursor></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="b397dded-f83e-4901-a77b-9d1fc99ddeb8" ac:name="html" ac:schema-version="1"><plain-text-body>Pending messages</plain-text-body></structured-macro></p> <p></p></td></tr><tr><td colspan="1" rowspan="1"><p> <em><link ac:anchor="xaConnectionFactory-element"><link-body><xaConnectionFactory></link-body></link></em> </p></td><td colspan="1" rowspan="1"><p> </p><p><structured-macro ac:macro-id="8e2d055d-3a82-447b-9a74-afed10893eca" ac:name="html" ac:schema-version="1"><plain-text-body>A <a href="http://www.springframework.org/">Spring</a> 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 <a shape="rect" href="http://activemq.apache.org/jmx.html">JMX</a>.</p> <p></p></td></tr></tbody></table></div>
+easier comprehension from <a href="http://activemq.apache.org/jmx.html">JMX</a>.</plain-text-body></structured-macro></p> <p></p></td></tr></tbody></table>
+
</div>
diff --git a/xml-configuration.xml b/xml-configuration.xml
index 9c51628..8b0f4a1 100644
--- a/xml-configuration.xml
+++ b/xml-configuration.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><p>We support an XML deployment descriptor for configuring the ActiveMQ Message Broker. There are many things which can be configured such as</p><ul><li><a shape="rect" href="configuring-version-5-transports.xml">transport connectors</a> which consist of transport channels and wire formats</li><li><a shape="rect" href="networks-of-brokers.xml">network connectors</a> using network channels or discovery agents</li><li><a shape="rect" href="persistence.xml">persistence providers</a> & locations</li><li>custom message containers (such as last image caching etc)</li></ul><p>So we decided that using XML would make this configuration much easier. From version 4.0 onwards we use <a shape="rect" class="external-link" href="http://xbean.org/" rel="nofollow">XBean</a> to perform the XML configuration.</p><p>For details of the XML see the <a shape="rect" href="xml-reference.xml">Xml Reference</a></p><parameter ac:name="title">Be careful with broker names and URIs</parameter><rich-text-body><p>Make sure you do not use any strange characters in the names of brokers as they are converted to URIs which <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html" rel="nofollow">do not allow things like underscores</a> in them etc.</p></rich-text-body><h2 id="XmlConfiguration-Examples">Examples</h2><p>The default ActiveMQ configuration: <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">current default config</a>.</p><parameter ac:name="">xml</parameter><plain-text-body><beans
+<div class="wiki-content maincontent"><p>We support an XML deployment descriptor for configuring the ActiveMQ Message Broker. There are many things which can be configured such as</p><ul><li><link><page ri:content-title="Configuring Version 5 Transports"></page><plain-text-link-body>transport connectors</plain-text-link-body></link> which consist of transport channels and wire formats</li><li><link><page ri:content-title="Networks of Brokers"></page><plain-text-link-body>network connectors</plain-text-link-body></link> using network channels or discovery agents</li><li><link><page ri:content-title="Persistence"></page><plain-text-link-body>persistence providers</plain-text-link-body></link> & locations</li><li>custom message containers (such as last image caching etc)</li></ul><p>So we decided that using XML would make this configuration much easier. From version 4.0 onwards we use <a shape="rect" href="http://xbean.org/">XBean</a> to perform the XML configuration.</p><p>For details of the XML see the <link><page ri:content-title="Xml Reference"></page></link></p><parameter ac:name="title">Be careful with broker names and URIs</parameter><rich-text-body><p>Make sure you do not use any strange characters in the names of brokers as they are converted to URIs which <a shape="rect" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html">do not allow things like underscores</a> in them etc.</p></rich-text-body><h2>Examples</h2><p>The default ActiveMQ configuration: <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">current default config</a>.</p><parameter ac:name="">xml</parameter><plain-text-body><beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
@@ -102,6 +102,6 @@
</plain-text-body><p><strong>AMQ 3.x</strong></p><plain-text-body>activemq myConfig.xml
</plain-text-body><p>Or to use the default config file its just</p><plain-text-body>activemq
</plain-text-body><p>If you have a source distribution you can run a broker using Maven specifying one of these configuration files as follows<br clear="none"> under the assembly module run :</p><plain-text-body>maven server -Dconfig=xbean:file:src/release/conf/activemq.xml
-</plain-text-body><p>If your <a shape="rect" href="initial-configuration.xml">classpath is set up correctly</a> you can achieve the same thing from the command line</p><plain-text-body>java org.apache.activemq.broker.Main xbean:file:src/release/conf/activemq.xml
-</plain-text-body><h2 id="XmlConfiguration-Configuringembeddedbrokers">Configuring embedded brokers</h2><p>You can also use the XML Configuration to configure <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">embedded brokers</a>. For example using the JNDI configuration mechanism you can do the following<br clear="none"> <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/config/BrokerXmlConfigFromJNDITest.java">BrokerXmlConfigFromJNDITest</a><br clear="none"> Or of you want to explicitly configure the embedded broker via Java code you can do the following<br clear="none"> <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/assembly/src/test/java/org/apache/activemq/config/BrokerXmlConfigStartTest.java">BrokerXmlConfigStartTest</a></p><h2 id="XmlConfiguration-UserSubmittedConfigurations">User Submitted Configurations</h2><p>We have a page which allows users to submit details of their configurations.</p><ul><li><a shape="rect" href="user-submitted-configurations.xml">User Submitted Configurations</a></li></ul><h2 id="XmlConfiguration-Background">Background</h2><p>Since ActiveMQ has so many strategy pattern plugins for transports, wire formats, persistence and many other things, we wanted to leave the configuration format open so that you the developer can configure and extend ActiveMQ in any direction you wish.</p><p>So we use the <a shape="rect" class="external-link" href="http://www.springframework.org/docs/reference/beans.html#beans-basics" rel="nofollow">Spring XML</a> configuration file format, which allows any beans / POJOs to be wired together and configured. However often Spring's XML can be kinda verbose at times, so we have implemented an ActiveMQ extension to the Spring XML which knows about the common, standard ActiveMQ things you're likely to do (e.g. tags like connector, wireFormat, serverTransport, persistence) - but at any time you can fall back to the normal Spring way of doing things (with tags like bean, property etc).</p><p>To see documentation of the XML file we use or to get access to the XSD/DTD see the <a shape="rect" href="xml-reference.xml">Xml Reference</a></p></div>
+</plain-text-body><p>If your <link><page ri:content-title="Initial Configuration"></page><plain-text-link-body>classpath is set up correctly</plain-text-link-body></link> you can achieve the same thing from the command line</p><plain-text-body>java org.apache.activemq.broker.Main xbean:file:src/release/conf/activemq.xml
+</plain-text-body><h2>Configuring embedded brokers</h2><p>You can also use the XML Configuration to configure <link><page ri:content-title="How do I embed a Broker inside a Connection"></page><plain-text-link-body>embedded brokers</plain-text-link-body></link>. For example using the JNDI configuration mechanism you can do the following<br clear="none"> <a shape="rect" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/config/BrokerXmlConfigFromJNDITest.java">BrokerXmlConfigFromJNDITest</a><br clear="none"> Or of you want to explicitly configure the embedded broker via Java code you can do the following<br clear="none"> <a shape="rect" href="https://svn.apache.org/repos/asf/activemq/trunk/assembly/src/test/java/org/apache/activemq/config/BrokerXmlConfigStartTest.java">BrokerXmlConfigStartTest</a></p><h2>User Submitted Configurations</h2><p>We have a page which allows users to submit details of their configurations.</p><ul><li><link><page ri:content-title="User Submitted Configurations"></page></link></li></ul><h2>Background</h2><p>Since ActiveMQ has so many strategy pattern plugins for transports, wire formats, persistence and many other things, we wanted to leave the configuration format open so that you the developer can configure and extend ActiveMQ in any direction you wish.</p><p>So we use the <a shape="rect" href="http://www.springframework.org/docs/reference/beans.html#beans-basics">Spring XML</a> configuration file format, which allows any beans / POJOs to be wired together and configured. However often Spring's XML can be kinda verbose at times, so we have implemented an ActiveMQ extension to the Spring XML which knows about the common, standard ActiveMQ things you're likely to do (e.g. tags like connector, wireFormat, serverTransport, persistence) - but at any time you can fall back to the normal Spring way of doing things (with tags like bean, property etc).</p><p>To see documentation of the XML file we use or to get access to the XSD/DTD see the <link><page ri:content-title="Xml Reference"></page></link></p></div>
diff --git a/xml-reference.xml b/xml-reference.xml
index 4fdf979..2a67941 100644
--- a/xml-reference.xml
+++ b/xml-reference.xml
@@ -1,75 +1,62 @@
-<div class="wiki-content maincontent"><h2 id="XmlReference-ActiveMQXmlReference">ActiveMQ Xml Reference</h2><p>This page contains a link to the XML reference guides and XML schema documents for <a shape="rect" href="xml-configuration.xml">Xml Configuration</a> with ActiveMQ releases</p><h3 id="XmlReference-ReleasedSchemas">Released Schemas</h3><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Reference Document</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Reference</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>XML Schema</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>XML Schema namespace</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="xbean-xml-reference-41.xml">XBean XML Reference 4.1</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-4.1.2.xsd.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-4.1.2.xsd">http://activemq.apache.org/schema/core/activemq-core-4.1.2.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.org/config/1.0" rel="nofollow">http://activemq.org/config/1.0</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="xbean-xml-reference-50.xml">XBean XML Reference 5.0</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.0.0.xsd.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.0.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.0.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.org/config/1.0" rel="nofollow">http://activemq.org/config/1.0</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.1.0.xsd.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.1.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.1.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.3.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.3.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.3.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.3.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.3.1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.3.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.3.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.3.1.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.3.2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.3.2-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.3.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.3.2.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.4.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.4.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.4.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.4.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.4.1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.4.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.4.2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.4.2-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.4.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.4.2.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.5.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.5.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.5.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.5.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.6.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.6.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.6.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.6.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.7.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.7.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.7.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.7.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.8.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.8.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.8.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.8.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.9.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.9.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.9.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.9.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span>XBean XML Reference 5.10.0</span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.10.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.10.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.10.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.10.1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.10.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.10.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.10.1.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><span>XBean XML Reference 5.10.2</span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.0-schema.html">Reference</a> </span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span> <a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.10.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.0.xsd</a> </span></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.11.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.11.1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.1.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.11.2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.2-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.2.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.11.3</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.3-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.11.3.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.3.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.12.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.12.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.12.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.12.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.12.1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.12.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.12.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.12.1.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.13.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.13.1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.1.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.13.2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.2.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.13.3</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.3.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.3.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.13.4</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.4-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.13.4.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.4.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.14.0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.0.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.14.1</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.1.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.14.2</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.2-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.2.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.14.3</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.3-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.3.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.3.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.14.4</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.4-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.4.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.4.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>XBean XML Reference 5.14.5</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.5-schema.html">Reference</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core/activemq-core-5.14.5.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.5.xsd</a></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr></tbody></table></div><h2 id="XmlReference-UsingtheXSDsinconfigurationfiles">Using the XSDs in configuration files</h2><p>If you are using XBean to parse the XML configurations, the XML validation is optional so you do not need to specify the XML Schema Locations. However if you are using <a shape="rect" class="unresolved" href="#">Spring</a>'s 2.0 XML handling to parse the XML then you need to refer to the XSD locations in your XML document because Spring uses schema namespace or schema location to resolve namespace handlers. Without correct namespace definition you will get messages like below:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[Unable to locate NamespaceHandler for namespace [http://activemq.org/config/1.0]]]></script>
-</div></div><p>You can refer to a specific version of the XSD in your XML as follows</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<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="
+<div class="wiki-content maincontent"><h2>ActiveMQ Xml Reference</h2><p>This page contains a link to the XML reference guides and XML schema documents for <link><page ri:content-title="Xml Configuration"></page></link> with ActiveMQ releases</p><h3>Released Schemas</h3><table><tbody><tr><th colspan="1" rowspan="1"><p>Reference Document</p></th><th colspan="1" rowspan="1"><p>Reference</p></th><th colspan="1" rowspan="1"><p>XML Schema</p></th><th colspan="1" rowspan="1"><p>XML Schema namespace</p></th></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="XBean XML Reference 4.1"></page></link></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-4.1.2.xsd.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-4.1.2.xsd">http://activemq.apache.org/schema/core/activemq-core-4.1.2.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.org/config/1.0">http://activemq.org/config/1.0</a></p></td></tr><tr><td colspan="1" rowspan="1"><p><link><page ri:content-title="XBean XML Reference 5.0"></page></link></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.0.0.xsd.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.0.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.0.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.org/config/1.0">http://activemq.org/config/1.0</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.1</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.1.0.xsd.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.1.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.1.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.2</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.3.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.3.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.3.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.3.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.3.1</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.3.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.3.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.3.1.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.3.2</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.3.2-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.3.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.3.2.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.4.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.4.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.4.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.4.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.4.1</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.4.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.4.2</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.4.2-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.4.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.4.2.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.5.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.5.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.5.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.5.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.6.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.6.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.6.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.6.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.7.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.7.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.7.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.7.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.8.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.8.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.8.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.8.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.9.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.9.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.9.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.9.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p><span>XBean XML Reference 5.10.0</span></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.10.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.10.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.10.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.10.1</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.10.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.10.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.10.1.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p><span>XBean XML Reference 5.10.2</span></p></td><td colspan="1" rowspan="1"><p><span><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.0-schema.html">Reference</a> </span></p></td><td colspan="1" rowspan="1"><p><span> <a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.10.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.0.xsd</a> </span></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.11.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.11.1</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.1.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.11.2</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.2-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.2.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.11.3</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.3-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.11.3.xsd">http://activemq.apache.org/schema/core/activemq-core-5.11.3.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.12.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.12.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.12.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.12.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.12.1</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.12.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.12.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.12.1.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.13.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.13.1</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.1.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.13.2</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.2.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.13.3</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.3.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.3.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.13.4</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.4-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.13.4.xsd">http://activemq.apache.org/schema/core/activemq-core-5.13.4.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.14.0</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.0-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.0.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.0.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.14.1</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.1-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.1.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.1.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.14.2</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.2-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.2.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.2.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.14.3</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.3-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.3.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.3.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.14.4</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.4-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.4.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.4.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr><tr><td colspan="1" rowspan="1"><p>XBean XML Reference 5.14.5</p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.5-schema.html">Reference</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core/activemq-core-5.14.5.xsd">http://activemq.apache.org/schema/core/activemq-core-5.14.5.xsd</a></p></td><td colspan="1" rowspan="1"><p><a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a></p></td></tr></tbody></table><h2>Using the XSDs in configuration files</h2><p>If you are using XBean to parse the XML configurations, the XML validation is optional so you do not need to specify the XML Schema Locations. However if you are using <link><page ri:content-title="Spring"></page><plain-text-link-body>Spring</plain-text-link-body></link>'s 2.0 XML handling to parse the XML then you need to refer to the XSD locations in your XML document because Spring uses schema namespace or schema location to resolve namespace handlers. Without correct namespace definition you will get messages like below:</p><structured-macro ac:macro-id="f77496d3-0e80-43ab-8c08-4d05a5c3a743" ac:name="code" ac:schema-version="1"><plain-text-body>Unable to locate NamespaceHandler for namespace [http://activemq.org/config/1.0]</plain-text-body></structured-macro><p>You can refer to a specific version of the XSD in your XML as follows</p><structured-macro ac:macro-id="223f8cfc-198c-44ef-a519-8c8245890821" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><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 http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.org/config/1.0 http://activemq.apache.org/schema/core/activemq-core-4.1.2.xsd">
-]]></script>
-</div></div><p>or if you prefer you can use a generic XSD without the version number</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<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://activemq.org/config/1.0 http://activemq.apache.org/schema/core/activemq-core-4.1.2.xsd">
+</plain-text-body></structured-macro><p>or if you prefer you can use a generic XSD without the version number</p><structured-macro ac:macro-id="45dc3180-ac0a-4703-bd8a-b6ec2a291b28" ac:name="code" ac:schema-version="1"><parameter ac:name="">xml</parameter><plain-text-body><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 http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
- http://activemq.org/config/1.0 http://activemq.apache.org/schema/activemq-core.xsd">
-]]></script>
-</div></div><p>Your IDE won't be able to fetch this XSD, you'll have to manually associate a specific release; however it does mean that you won't have to upgrade your XML config file with each ActiveMQ release; as it will resolve this XSD using the bundled XSD inside the activemq-core.jar.</p><h3 id="XmlReference-Payattentiontothenamespace">Pay attention to the namespace</h3><p>If you use ActiveMQ 5.0 or earlier you XML namespace definition should point to <code>
- <a shape="rect" class="external-link" href="http://activemq.org/config/1.0" rel="nofollow">http://activemq.org/config/1.0</a>
+ http://activemq.org/config/1.0 http://activemq.apache.org/schema/activemq-core.xsd">
+</plain-text-body></structured-macro><p>Your IDE won't be able to fetch this XSD, you'll have to manually associate a specific release; however it does mean that you won't have to upgrade your XML config file with each ActiveMQ release; as it will resolve this XSD using the bundled XSD inside the activemq-core.jar.</p><h3>Pay attention to the namespace</h3><p>If you use ActiveMQ 5.0 or earlier you XML namespace definition should point to <code>
+ <a shape="rect" href="http://activemq.org/config/1.0">http://activemq.org/config/1.0</a>
</code>. If you use ActiveMQ 5.1 or later the namespace should point to <code>
- <a shape="rect" class="external-link" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a>
- </code>.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ActiveMQ 5.2 example</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:amq="http://activemq.apache.org/schema/core"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="
+ <a shape="rect" href="http://activemq.apache.org/schema/core">http://activemq.apache.org/schema/core</a>
+ </code>.</p><structured-macro ac:macro-id="575bd8e6-9776-402f-a517-7823a6a58087" ac:name="code" ac:schema-version="1"><parameter ac:name="title">ActiveMQ 5.2 example</parameter><parameter ac:name="">xml</parameter><plain-text-body><beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:amq="http://activemq.apache.org/schema/core"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd
- ">
+ ">
</beans>
-]]></script>
-</div></div><div class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>ActiveMQ 5.0 example</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[<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="
+</plain-text-body></structured-macro><structured-macro ac:macro-id="9ff0412c-d1db-45cb-bd24-6140adfb9f13" ac:name="code" ac:schema-version="1"><parameter ac:name="title">ActiveMQ 5.0 example</parameter><parameter ac:name="">xml</parameter><plain-text-body><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
http://www.springframework.org/schema/beans/spring-beans.xsd
http://activemq.org/config/1.0
http://activemq.apache.org/schema/core/activemq-core-5.0.0.xsd
- ">
+ ">
</beans>
-]]></script>
-</div></div><p>Both examples above are almost the same. Only one difference is xml namespace. You can find more information about the namespace change on <a shape="rect" class="external-link" href="http://old.nabble.com/ActiveMQ-namespace-change-td16769650.html" rel="nofollow">activemq-dev topic: ActiveMQ namespace change</a>.</p><h3 id="XmlReference-SchemaValidation">Schema Validation</h3><p><strong>Note:</strong> The xml configuration ordering constraint is removed in <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/AMQ-3570">5.6</a>, the broker element</p><h4 id="XmlReference-AlphabeticallyOrderedXMLElements(5.4-5.5.1)">Alphabetically Ordered XML Elements (5.4 - 5.5.1)</h4><p>XMLSchema:sequence is replaced with an XMLSchema:all</p><p>Note: from version 5.4.2, you can disable validation from the command line by appending a query parameter to the xbean url. This will allow you to reuse your existing xml configuration 'as is' if needed.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[bin/activemq console xbean:conf/activemq.xml?validate=false]]></script>
-</div></div><p>Beginning in ActiveMQ 5.4, the XML elements inside the <code><broker></code> element must be ordered alphabetically. If you look at the XSD, this has always been the case with ActiveMQ. The difference in 5.4 is that the XML configuration is actually being validated against the XML schema.</p><p>For example, the following XML configuration did not present a problem in ActiveMQ 5.3.x:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0"?>
-<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+</plain-text-body></structured-macro><p>Both examples above are almost the same. Only one difference is xml namespace. You can find more information about the namespace change on <a shape="rect" href="http://old.nabble.com/ActiveMQ-namespace-change-td16769650.html">activemq-dev topic: ActiveMQ namespace change</a>.</p><h3>Schema Validation</h3><p><strong>Note:</strong> The xml configuration ordering constraint is removed in <a shape="rect" href="https://issues.apache.org/jira/browse/AMQ-3570">5.6</a>, the broker element</p><h4>Alphabetically Ordered XML Elements (5.4 - 5.5.1)</h4><p>XMLSchema:sequence is replaced with an XMLSchema:all</p><p>Note: from version 5.4.2, you can disable validation from the command line by appending a query parameter to the xbean url. This will allow you to reuse your existing xml configuration 'as is' if needed.</p><structured-macro ac:macro-id="42999cc8-ddea-4684-98ec-5213b779c3d3" ac:name="code" ac:schema-version="1"><plain-text-body>bin/activemq console xbean:conf/activemq.xml?validate=false</plain-text-body></structured-macro><p>Beginning in ActiveMQ 5.4, the XML elements inside the <code><broker></code> element must be ordered alphabetically. If you look at the XSD, this has always been the case with ActiveMQ. The difference in 5.4 is that the XML configuration is actually being validated against the XML schema.</p><p>For example, the following XML configuration did not present a problem in ActiveMQ 5.3.x:</p><structured-macro ac:macro-id="872bf198-5f71-4978-83d3-6be3843dfce4" ac:name="code" ac:schema-version="1"><plain-text-body>
+<?xml version="1.0"?>
+<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd
-http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">
+http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">
- <broker xmlns="http://activemq.apache.org/schema/core" brokerName="brokerB1" destroyApplicationContextOnStop="true">
+ <broker xmlns="http://activemq.apache.org/schema/core" brokerName="brokerB1" destroyApplicationContextOnStop="true">
<plugins>
<loggingBrokerPlugin/>
</plugins>
<persistenceAdapter>
- <kahaDB directory="${activemq.base}/data/kahadb" enableJournalDiskSyncs="false" indexWriteBatchSize="10000" indexCacheSize="1000"/>
+ <kahaDB directory="${activemq.base}/data/kahadb" enableJournalDiskSyncs="false" indexWriteBatchSize="10000" indexCacheSize="1000"/>
</persistenceAdapter>
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue=">" producerFlowControl="true" memoryLimit="5mb">
+ <policyEntry queue=">" producerFlowControl="true" memoryLimit="5mb">
<deadLetterStrategy>
- <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true"/>
+ <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true"/>
</deadLetterStrategy>
</policyEntry>
</policyEntries>
@@ -77,49 +64,45 @@
</destinationPolicy>
<managementContext>
- <managementContext createConnector="false"/>
+ <managementContext createConnector="false"/>
</managementContext>
<systemUsage>
<systemUsage>
<memoryUsage>
- <memoryUsage limit="420 mb"/>
+ <memoryUsage limit="420 mb"/>
</memoryUsage>
<storeUsage>
- <storeUsage limit="1 gb"/>
+ <storeUsage limit="1 gb"/>
</storeUsage>
<tempUsage>
- <tempUsage limit="250 mb"/>
+ <tempUsage limit="250 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
<transportConnectors>
- <transportConnector name="tcp" uri="tcp://0.0.0.0:61616"/>
+ <transportConnector name="tcp" uri="tcp://0.0.0.0:61616"/>
</transportConnectors>
</broker>
</beans>
-]]></script>
-</div></div><p>However, in ActiveMQ 5.4, the XML configuration above would cause an exception similar to the following:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'persistenceAdapter'. One of '{"http://activemq.apache.org/schema/core":producerSystemUsage, "http://activemq.apache.org/schema/core":proxyConnectors, "http://activemq.apache.org/schema/core":regionBroker, "http://activemq.apache.org/schema/core":services, "http://activemq.apache.org/schema/core":shutdownHooks, "http://activemq.apache.org/schema/core":sslContext, "http://activemq.apache.org/schema/core":systemUsage, "http://activemq.apache.org/schema/core":taskRunnerFactory, "http://activemq.apache.org/schema/core":tempDataStore, "http://activemq.apache.org/schema/core":transportConnectorURIs, "http://activemq.apache.org/schema/core":transportConnectors, WC<a shape="rect" class="unresolved" href="#">"http://activemq.apache.org/schema/core"</a>}' is expected.</p>
-</div></div><p>To avoid this XML validation error in ActiveMQ 5.4, simply change the ordering of the XML elements so that they are in alphabetical order. Below is an example of the same XML configuration but in alphabetical order:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<?xml version="1.0"?>
-<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
+</plain-text-body></structured-macro><p>However, in ActiveMQ 5.4, the XML configuration above would cause an exception similar to the following:</p><structured-macro ac:macro-id="9186c96a-be1e-4904-89b5-c27c59dec78e" ac:name="panel" ac:schema-version="1"><rich-text-body><p>Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'persistenceAdapter'. One of '{"http://activemq.apache.org/schema/core":producerSystemUsage, "http://activemq.apache.org/schema/core":proxyConnectors, "http://activemq.apache.org/schema/core":regionBroker, "http://activemq.apache.org/schema/core":services, "http://activemq.apache.org/schema/core":shutdownHooks, "http://activemq.apache.org/schema/core":sslContext, "http://activemq.apache.org/schema/core":systemUsage, "http://activemq.apache.org/schema/core":taskRunnerFactory, "http://activemq.apache.org/schema/core":tempDataStore, "http://activemq.apache.org/schema/core":transportConnectorURIs, "http://activemq.apache.org/schema/core":transportConnectors, WC<link><page ri:content-title=""http://activemq.apache.org/schema/core"" ri:space-key="##other"></page><plain-text-link-body>"http://activemq.apache.org/schema/core"</plain-text-link-body></link>}' is expected.</p></rich-text-body></structured-macro><p>To avoid this XML validation error in ActiveMQ 5.4, simply change the ordering of the XML elements so that they are in alphabetical order. Below is an example of the same XML configuration but in alphabetical order:</p><structured-macro ac:macro-id="8d94cd74-29af-46b1-b4c0-e180d1c4710a" ac:name="code" ac:schema-version="1"><plain-text-body>
+<?xml version="1.0"?>
+<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd
-http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">
+http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">
- <broker xmlns="http://activemq.apache.org/schema/core" brokerName="brokerB1" destroyApplicationContextOnStop="true">
+ <broker xmlns="http://activemq.apache.org/schema/core" brokerName="brokerB1" destroyApplicationContextOnStop="true">
<destinationPolicy>
<policyMap>
<policyEntries>
- <policyEntry queue=">" producerFlowControl="true" memoryLimit="5mb">
+ <policyEntry queue=">" producerFlowControl="true" memoryLimit="5mb">
<deadLetterStrategy>
- <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true"/>
+ <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true"/>
</deadLetterStrategy>
</policyEntry>
</policyEntries>
@@ -127,11 +110,11 @@
</destinationPolicy>
<managementContext>
- <managementContext createConnector="false"/>
+ <managementContext createConnector="false"/>
</managementContext>
<persistenceAdapter>
- <kahaDB directory="${activemq.base}/data/kahadb" enableJournalDiskSyncs="false" indexWriteBatchSize="10000" indexCacheSize="1000"/>
+ <kahaDB directory="${activemq.base}/data/kahadb" enableJournalDiskSyncs="false" indexWriteBatchSize="10000" indexCacheSize="1000"/>
</persistenceAdapter>
<plugins>
@@ -141,26 +124,23 @@
<systemUsage>
<systemUsage>
<memoryUsage>
- <memoryUsage limit="420 mb"/>
+ <memoryUsage limit="420 mb"/>
</memoryUsage>
<storeUsage>
- <storeUsage limit="1 gb"/>
+ <storeUsage limit="1 gb"/>
</storeUsage>
<tempUsage>
- <tempUsage limit="250 mb"/>
+ <tempUsage limit="250 mb"/>
</tempUsage>
</systemUsage>
</systemUsage>
<transportConnectors>
- <transportConnector name="tcp" uri="tcp://0.0.0.0:61616"/>
+ <transportConnector name="tcp" uri="tcp://0.0.0.0:61616"/>
</transportConnectors>
</broker>
</beans>
-]]></script>
-</div></div><p>Configurations can be easily tested against ActiveMQ 5.4 using the ActiveMQ startup script. Below is an example:</p><div class="panel" style="border-width: 1px;"><div class="panelContent">
-<p>$ cd $ACTIVEMQ_HOME<br clear="none"> $ ./bin/activemq console xbean:file:/Users/bsnyder/SpringSource/clients/Finra/activemq-example-unordered.xml <br clear="none"> INFO: Using default configuration<br clear="none"> (you can configure options in one of these file: /etc/default/activemq /Users/bsnyder/.activemqrc)</p><p>INFO: Invoke the following command to create a configuration file<br clear="none"> ./bin/activemq setup [ /etc/default/activemq | /Users/bsnyder/.activemqrc ]</p><p>INFO: Using java '/System/Library/Frameworks/JavaVM.framework/Home/bin/java'<br clear="none"> INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C)<br clear="none"> Java Runtime: Apple Inc. 1.6.0_20 /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home<br clear="none"> Heap sizes: current=258880k free=253106k max=258880k<br clear="none"> JVM args: -Xms256M -Xmx256M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties -Dcom.sun.management.jmxremote -Dactivemq.classpath=/Users/bsnyder/amq/apache-activemq-5.4.1/conf; -Dactivemq.home=/Users/bsnyder/amq/apache-activemq-5.4.1 -Dactivemq.base=/Users/bsnyder/amq/apache-activemq-5.4.1<br clear="none"> ACTIVEMQ_HOME: /Users/bsnyder/amq/apache-activemq-5.4.1<br clear="none"> ACTIVEMQ_BASE: /Users/bsnyder/amq/apache-activemq-5.4.1<br clear="none"> Loading message broker from: xbean:file:/Users/bsnyder/SpringSource/clients/Finra/activemq-example-unordered.xml<br clear="none"> ...</p>
-</div></div></div>
+</plain-text-body></structured-macro><p>Configurations can be easily tested against ActiveMQ 5.4 using the ActiveMQ startup script. Below is an example:</p><structured-macro ac:macro-id="0d43d5f3-c2b7-4731-b338-623ee2421f4b" ac:name="panel" ac:schema-version="1"><rich-text-body><p>$ cd $ACTIVEMQ_HOME<br clear="none"> $ ./bin/activemq console xbean:file:/Users/bsnyder/SpringSource/clients/Finra/activemq-example-unordered.xml <br clear="none"> INFO: Using default configuration<br clear="none"> (you can configure options in one of these file: /etc/default/activemq /Users/bsnyder/.activemqrc)</p><p>INFO: Invoke the following command to create a configuration file<br clear="none"> ./bin/activemq setup [ /etc/default/activemq | /Users/bsnyder/.activemqrc ]</p><p>INFO: Using java '/System/Library/Frameworks/JavaVM.framework/Home/bin/java'<br clear="none"> INFO: Starting in foreground, this is just for debugging purposes (stop process by pressing CTRL+C)<br clear="none"> Java Runtime: Apple Inc. 1.6.0_20 /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home<br clear="none"> Heap sizes: current=258880k free=253106k max=258880k<br clear="none"> JVM args: -Xms256M -Xmx256M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties -Dcom.sun.management.jmxremote -Dactivemq.classpath=/Users/bsnyder/amq/apache-activemq-5.4.1/conf; -Dactivemq.home=/Users/bsnyder/amq/apache-activemq-5.4.1 -Dactivemq.base=/Users/bsnyder/amq/apache-activemq-5.4.1<br clear="none"> ACTIVEMQ_HOME: /Users/bsnyder/amq/apache-activemq-5.4.1<br clear="none"> ACTIVEMQ_BASE: /Users/bsnyder/amq/apache-activemq-5.4.1<br clear="none"> Loading message broker from: xbean:file:/Users/bsnyder/SpringSource/clients/Finra/activemq-example-unordered.xml<br clear="none"> ...</p></rich-text-body></structured-macro></div>
diff --git a/xmpp.xml b/xmpp.xml
index 3cb584b..70ab60e 100644
--- a/xmpp.xml
+++ b/xmpp.xml
@@ -1,93 +1,91 @@
-<div class="wiki-content maincontent"><h2 id="XMPP-XMPPProtocolSupport(Jabber!)">XMPP Protocol Support (Jabber!)</h2>
+<div class="wiki-content maincontent"><h2>XMPP Protocol Support (Jabber!)</h2>
-<div class="confluence-information-macro confluence-information-macro-warning"><p class="title">Deprecated</p><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>This transport was deprecated in 5.8.0 and has been removed in a 5.9.0!</p></div></div>
-<p>We have support for <a shape="rect" class="external-link" href="http://www.xmpp.org/" rel="nofollow">XMPP</a> (Jabber) as a transport in ActiveMQ.</p>
+<structured-macro ac:macro-id="32c335e0-52cc-45b0-9962-3a0899c44e92" ac:name="warning" ac:schema-version="1"><parameter ac:name="title">Deprecated</parameter><rich-text-body>
+<p>This transport was deprecated in 5.8.0 and has been removed in a 5.9.0!</p></rich-text-body></structured-macro>
+<p>We have support for <a shape="rect" href="http://www.xmpp.org/">XMPP</a> (Jabber) as a transport in ActiveMQ.</p>
<p>To use just add a connector as follows</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker xmlns="http://activemq.org/config/1.0">
+<structured-macro ac:macro-id="633f3d25-a0b8-48b6-aeae-85fb93858d4e" ac:name="code" ac:schema-version="1"><plain-text-body>
+<broker xmlns="http://activemq.org/config/1.0">
<transportConnectors>
- <transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
- <transportConnector name="stomp" uri="stomp://localhost:61613"/>
- <transportConnector name="xmpp" uri="xmpp://localhost:61222"/>
+ <transportConnector name="openwire" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>
+ <transportConnector name="stomp" uri="stomp://localhost:61613"/>
+ <transportConnector name="xmpp" uri="xmpp://localhost:61222"/>
</transportConnectors>
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
<p>And you can now use XMPP to connect to the broker & send and receive messages.</p>
-<div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Some versions of the broker (5.0-5.2) does not include <a shape="rect" class="external-link" href="http://woodstox.codehaus.org/" rel="nofollow">WoodStox</a> library by default, which could impact ActiveMQ XMPP funcionality. You should have a library named like <code>wstx-asl-x.x.x.jar</code> in the <code>lib/optional</code> directory of your broker. If that's not the case, download it from <a shape="rect" class="external-link" href="http://woodstox.codehaus.org/" rel="nofollow">here</a> and put it in the classpath</p></div></div>
+<structured-macro ac:macro-id="b5d113d5-3a2f-4dad-9916-0d828203f4b0" ac:name="warning" ac:schema-version="1"><parameter ac:name="">Classpath</parameter><rich-text-body>
+<p>Some versions of the broker (5.0-5.2) does not include <a shape="rect" href="http://woodstox.codehaus.org/">WoodStox</a> library by default, which could impact ActiveMQ XMPP funcionality. You should have a library named like <code>wstx-asl-x.x.x.jar</code> in the <code>lib/optional</code> directory of your broker. If that's not the case, download it from <a shape="rect" href="http://woodstox.codehaus.org/">here</a> and put it in the classpath</p></rich-text-body></structured-macro>
-<h3 id="XMPP-XMPPSupportinApacheActiveMQ">XMPP Support in Apache ActiveMQ</h3>
+<h3>XMPP Support in Apache ActiveMQ</h3>
<p>ActiveMQ provides a bidirectional bridge between ActiveMQ messages and XMPP.</p>
-<ul><li>if a client joins a chatroom / conference room, the name of the conference room is mapped to a JMS topic of the same name</li><li>typing into a chatroom sends a message to the topic</li><li>presence in a chatroom maintains a subscription on the JMS topic (using noLocal to avoid getting copies of things you say) so that messages sent by other clients (via <a shape="rect" href="xmpp.xml">XMPP</a>, the <a shape="rect" href="web-console.xml">Web Console</a>, the <a shape="rect" href="examples.xml">Examples</a> or any other <a shape="rect" href="cross-language-clients.xml">Cross Language Clients</a>) are then sent to the chatroom.</li></ul>
+<ul><li>if a client joins a chatroom / conference room, the name of the conference room is mapped to a JMS topic of the same name</li><li>typing into a chatroom sends a message to the topic</li><li>presence in a chatroom maintains a subscription on the JMS topic (using noLocal to avoid getting copies of things you say) so that messages sent by other clients (via <link></link>, the <link><page ri:content-title="Web Console"></page></link>, the <link><page ri:content-title="Examples"></page></link> or any other <link><page ri:content-title="Cross Language Clients"></page></link>) are then sent to the chatroom.</li></ul>
-<h3 id="XMPP-UsingaJabberClient">Using a Jabber Client</h3>
+<h3>Using a Jabber Client</h3>
-<p>Basically, you should be able to connect from any Jabber-compatible client to the broker. The below example is using <a shape="rect" class="external-link" href="http://jivesoftware.com/products/spark/" rel="nofollow">Spark</a> 2.0.0 version. For more details on connecting with different clients take a look at <a shape="rect" href="#XMPP-Jabberclientscompatibility">#Jabber clients compatibility</a>.</p>
+<p>Basically, you should be able to connect from any Jabber-compatible client to the broker. The below example is using <a shape="rect" href="http://jivesoftware.com/products/spark/">Spark</a> 2.0.0 version. For more details on connecting with different clients take a look at <link ac:anchor="Jabber clients compatibility"><link-body>#Jabber clients compatibility</link-body></link>.</p>
<p>To connect to Apache ActiveMQ try the following...</p>
-<p>1. Run the <a shape="rect" href="web-console.xml">Web Console</a><br clear="none">
-2. Start <a shape="rect" class="external-link" href="http://jivesoftware.com/products/spark/" rel="nofollow">Spark</a> or whatever Jabber Client you wish<br clear="none">
+<p>1. Run the <link><page ri:content-title="Web Console"></page></link><br clear="none">
+2. Start <a shape="rect" href="http://jivesoftware.com/products/spark/">Spark</a> or whatever Jabber Client you wish<br clear="none">
3. Login to localhost:61222</p>
-<div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Some Jabber clients (like iChat) insist on usernames in forms of <em>username@host</em>, so in that case just append <em>@localhost</em> to your username</p></div></div>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="xmpp.data/step1.png" data-image-src="/confluence/download/attachments/35901/step1.png?version=1&modificationDate=1162051914000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3243" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="step1.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35901" data-linked-resource-container-version="34"></span></p>
-<div class="confluence-information-macro confluence-information-macro-warning"><span class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
+<structured-macro ac:macro-id="de4500b9-8d17-4ab8-82c3-a4ada7947169" ac:name="warning" ac:schema-version="1"><parameter ac:name="">Username</parameter><rich-text-body>
+<p>Some Jabber clients (like iChat) insist on usernames in forms of <em>username@host</em>, so in that case just append <em>@localhost</em> to your username</p></rich-text-body></structured-macro>
+<p><image><attachment ri:filename="step1.png"></attachment></image></p>
+<structured-macro ac:macro-id="7214f204-39ac-4b3c-898e-c7ad1a8e366c" ac:name="warning" ac:schema-version="1"><parameter ac:name="">Careful about auto-discovery</parameter><rich-text-body>
<p>Some Jabber clients like to auto-discover the host and port. You need to explicitly disable this feature so you can explicitly configure <strong>localhost</strong> as the host and <strong>61222</strong> as the port.</p>
-<p>e.g. on Spark go to the <strong>Advanced</strong> tab and disable the <strong>Automatically discover host and port</strong></p></div></div>
+<p>e.g. on Spark go to the <strong>Advanced</strong> tab and disable the <strong>Automatically discover host and port</strong></p></rich-text-body></structured-macro>
<p>4. You should now see the following screen...</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="xmpp.data/step2.png" data-image-src="/confluence/download/attachments/35901/step2.png?version=1&modificationDate=1162052275000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3230" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="step2.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35901" data-linked-resource-container-version="34"></span></p>
+<p><image><attachment ri:filename="step2.png"></attachment></image></p>
<p>5. Now click on the <strong>Join Conference Room</strong> button (next to the Add Contact button) and the following dialog should appear</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="xmpp.data/step3.png" data-image-src="/confluence/download/attachments/35901/step3.png?version=1&modificationDate=1162052275000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3283" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="step3.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35901" data-linked-resource-container-version="34"></span></p>
+<p><image><attachment ri:filename="step3.png"></attachment></image></p>
<p>6. Now press the <strong>Create or Join Room</strong> button to get the following dialog. Enter a JMS topic name, in this case <strong>foo.bar</strong> and you're good to go...</p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="xmpp.data/step4.png" data-image-src="/confluence/download/attachments/35901/step4.png?version=1&modificationDate=1162052275000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3275" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="step4.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35901" data-linked-resource-container-version="34"></span></p>
+<p><image><attachment ri:filename="step4.png"></attachment></image></p>
<p>7. Now your chat window should appear for talking and listening to the topic <strong>foo.bar</strong>. So start typing to test things out. </p>
-<p><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="xmpp.data/step5.png" data-image-src="/confluence/download/attachments/35901/step5.png?version=1&modificationDate=1162052275000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3257" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="step5.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35901" data-linked-resource-container-version="34"></span></p>
+<p><image><attachment ri:filename="step5.png"></attachment></image></p>
-<p> 8. Now if you go to the <a shape="rect" class="external-link" href="http://localhost:8161/admin/topics.jsp" rel="nofollow">Topic Console</a> in the Web Console you should see the topic has been created</p>
+<p> 8. Now if you go to the <a shape="rect" href="http://localhost:8161/admin/topics.jsp">Topic Console</a> in the Web Console you should see the topic has been created</p>
-<p> <span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="xmpp.data/step6-new.png" data-image-src="/confluence/download/attachments/35901/step6-new.png?version=1&modificationDate=1238485212000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="10166" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="step6-new.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35901" data-linked-resource-container-version="34"></span></p>
+<p> <image><attachment ri:filename="step6-new.png"></attachment></image></p>
<p>9. If you now click on the <strong>Send To</strong> link next to the <strong>foo.bar</strong> topic you can send a message to the topic from the web console. </p>
-<p> <span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="xmpp.data/step7-new.png" data-image-src="/confluence/download/attachments/35901/step7-new.png?version=1&modificationDate=1238485212000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="10167" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="step7-new.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35901" data-linked-resource-container-version="34"></span></p>
+<p> <image><attachment ri:filename="step7-new.png"></attachment></image></p>
-<p>10. Press send and you should see the chat appear on the chat window <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5997/6f42626d00e36f53fe51440403446ca61552e2a2.1/_/images/icons/emoticons/smile.png" data-emoticon-name="smile" alt="(smile)"></p>
+<p>10. Press send and you should see the chat appear on the chat window <emoticon ac:name="smile"></emoticon></p>
-<p> <span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="xmpp.data/step8.png" data-image-src="/confluence/download/attachments/35901/step8.png?version=1&modificationDate=1162052301000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="3241" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="step8.png" data-base-url="https://cwiki.apache.org/confluence" data-linked-resource-content-type="image/png" data-linked-resource-container-id="35901" data-linked-resource-container-version="34"></span></p>
+<p> <image><attachment ri:filename="step8.png"></attachment></image></p>
-<h3 id="XMPP-Jabberclientscompatibility">Jabber clients compatibility</h3>
+<h3>Jabber clients compatibility</h3>
<p>Here you can find specfic issues and workarounds for various Jabber clients. If you have some of your own, please post them here.</p>
-<h4 id="XMPP-Spark">Spark</h4>
+<h4>Spark</h4>
-<p>Url: <a shape="rect" class="external-link" href="http://www.igniterealtime.org/projects/spark/index.jsp" rel="nofollow">http://www.igniterealtime.org/projects/spark/index.jsp</a><br clear="none">
-Spark 2.0.0 works fine with ActiveMQ; Click <a shape="rect" class="external-link" href="http://www.igniterealtime.org/downloads/download-landing.jsp?file=spark/spark_2_ 0_0.exe" rel="nofollow">here</a> to download: <a shape="rect" class="external-link" href="http://www.igniterealtime.org/downloads/download-landing.jsp?file=spark/spark_2_0_0.exe" rel="nofollow">Spark 2.0.0 for Windows</a>.<br clear="none">
+<p>Url: <a shape="rect" href="http://www.igniterealtime.org/projects/spark/index.jsp">http://www.igniterealtime.org/projects/spark/index.jsp</a><br clear="none">
+Spark 2.0.0 works fine with ActiveMQ; Click <a shape="rect" href="http://www.igniterealtime.org/downloads/download-landing.jsp?file=spark/spark_2_ 0_0.exe">here</a> to download: <a shape="rect" href="http://www.igniterealtime.org/downloads/download-landing.jsp?file=spark/spark_2_0_0.exe">Spark 2.0.0 for Windows</a>.<br clear="none">
Spark 2.5.x connects fine, but it won't open the <strong>Join Conference Room</strong> dialog.</p>
-<h4 id="XMPP-iChat">iChat</h4>
+<h4>iChat</h4>
-<p>Url: <a shape="rect" class="external-link" href="http://www.apple.com/macosx/features/ichat.html" rel="nofollow">http://www.apple.com/macosx/features/ichat.html</a><br clear="none">
+<p>Url: <a shape="rect" href="http://www.apple.com/macosx/features/ichat.html">http://www.apple.com/macosx/features/ichat.html</a><br clear="none">
Tested version 4.0.7 works fine, but it insists you use <em>username@host</em> format for usernames</p>
-<h4 id="XMPP-Adium">Adium</h4>
+<h4>Adium</h4>
-<p>Url: <a shape="rect" class="external-link" href="http://www.adiumx.com/" rel="nofollow">http://www.adiumx.com/</a><br clear="none">
-Tested version 1.3.3 works fine. The only spotted issue is reconnecting to <a shape="rect" href="command-agent.xml">Command Agent</a> topic. We recommend that you restart the Adium if you need to do this </p></div>
+<p>Url: <a shape="rect" href="http://www.adiumx.com/">http://www.adiumx.com/</a><br clear="none">
+Tested version 1.3.3 works fine. The only spotted issue is reconnecting to <link><page ri:content-title="Command Agent"></page></link> topic. We recommend that you restart the Adium if you need to do this </p></div>
diff --git a/zeroconf-transport-reference.xml b/zeroconf-transport-reference.xml
index 05307ea..3bc9d6b 100644
--- a/zeroconf-transport-reference.xml
+++ b/zeroconf-transport-reference.xml
@@ -1,8 +1,8 @@
-<div class="wiki-content maincontent"><h3 id="ZeroConfTransportReference-TheZeroConfTransport">The ZeroConf Transport</h3>
+<div class="wiki-content maincontent"><h3>The ZeroConf Transport</h3>
-<p>The ZeroConf transport works just like <a shape="rect" href="discovery-transport-reference.xml">Discovery Transport</a>, except that it uses a <a shape="rect" href="zeroconf.xml">ZeroConf</a> based discovery agent to locate the list of broker uris to connect to.</p>
+<p>The ZeroConf transport works just like <link><page ri:content-title="Discovery Transport Reference"></page><link-body>Discovery Transport</link-body></link>, except that it uses a <link><page ri:content-title="ZeroConf"></page></link> based discovery agent to locate the list of broker uris to connect to.</p>
-<h4 id="ZeroConfTransportReference-ConfigurationSyntax">Configuration Syntax</h4>
+<h4>Configuration Syntax</h4>
<p><strong>zeroconf:serviceName?transportOptions</strong><br clear="none">
or<br clear="none">
@@ -11,23 +11,20 @@
<p>where <em>serviceName</em> is the Zeroconf service name; which seems to start with an underscore (_) and must end with a dot (.). So we can use this service name to distinguish development, UAT & production brokers - or group them into domains etc.</p>
-<p>Note that to be able to use ZeroConf to find brokers, the brokers need to have <a shape="rect" href="discovery.xml">Discovery</a> enabled. To configure discovery in a Broker you should use the <a shape="rect" href="xml-configuration.xml">Xml Configuration</a>. Its basically something like...</p>
+<p>Note that to be able to use ZeroConf to find brokers, the brokers need to have <link><page ri:content-title="Discovery"></page></link> enabled. To configure discovery in a Broker you should use the <link><page ri:content-title="Xml Configuration"></page></link>. Its basically something like...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
-<broker name="foo">
+<structured-macro ac:macro-id="6985defe-7571-4905-ae3f-ca6d372f1ebe" ac:name="code" ac:schema-version="1"><plain-text-body>
+<broker name="foo">
<transportConnectors>
- <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" discoveryUri="zeroconf:_activemq_development. />
+ <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" discoveryUri="zeroconf:_activemq_development. />
</transportConnectors>
...
</broker>
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h5 id="ZeroConfTransportReference-ExampleclientURI">Example client URI</h5>
+<h5>Example client URI</h5>
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
-<pre>zeroconf:_activemq_development.
-</pre>
-</div></div></div>
+<structured-macro ac:macro-id="dc56016e-8011-4157-a33f-097e11f39c98" ac:name="noformat" ac:schema-version="1"><plain-text-body>
+zeroconf:_activemq_development.
+</plain-text-body></structured-macro></div>
diff --git a/zeroconf.xml b/zeroconf.xml
index 21a686b..3d057b4 100644
--- a/zeroconf.xml
+++ b/zeroconf.xml
@@ -1,14 +1,15 @@
-<div class="wiki-content maincontent"><h2 id="ZeroConf-ZeroConf">ZeroConf</h2>
+<div class="wiki-content maincontent"><h2>ZeroConf</h2>
-<p><a shape="rect" class="external-link" href="http://www.zeroconf.org/" rel="nofollow">ZeroConf</a> is a standard service discovery mechanism. ZeroConf is used on Apple's OS X; which used to call it Rendezvous but now calls it Bonjour.</p>
+<p><a shape="rect" href="http://www.zeroconf.org/">ZeroConf</a> is a standard service discovery mechanism. ZeroConf is used on Apple's OS X; which used to call it Rendezvous but now calls it Bonjour.</p>
-<div class="confluence-information-macro confluence-information-macro-note"><span class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div class="confluence-information-macro-body">
-<p>Support for <a shape="rect" href="zeroconf.xml">ZeroConf</a> is <strong>deprecated</strong> and scheduled to be removed from ActiveMQ 5.8 onwards.</p></div></div>
+<structured-macro ac:macro-id="8672311e-5a3a-4b9a-a554-60515efd3942" ac:name="note" ac:schema-version="1"><parameter ac:name="">ZeroConf is deprecated</parameter><rich-text-body>
+<p>Support for <link></link> is <strong>deprecated</strong> and scheduled to be removed from ActiveMQ 5.8 onwards.</p></rich-text-body></structured-macro>
-<p>We use the <a shape="rect" class="external-link" href="http://jmdns.sf.net/" rel="nofollow">jmDNS</a> project to implement the Zeroconf specification to detect services. This means other Zeroconf<br clear="none">
+<p>We use the <a shape="rect" href="http://jmdns.sf.net/">jmDNS</a> project to implement the Zeroconf specification to detect services. This means other Zeroconf<br clear="none">
based tools can be used in conjunction with this discovery agent.</p>
-<p>You can use ZeroConf with ActiveMQ's <a shape="rect" href="discovery.xml">Discovery</a> mechanism. For more details see</p>
+<p>You can use ZeroConf with ActiveMQ's <link><page ri:content-title="Discovery"></page></link> mechanism. For more details see</p>
-<ul><li><a shape="rect" href="discovery.xml">Discovery</a></li><li><a shape="rect" href="zeroconf-transport-reference.xml">ZeroConf Transport Reference</a></li></ul></div>
+<ul><li><link><page ri:content-title="Discovery"></page></link></li><li><link><page ri:content-title="ZeroConf Transport Reference"></page></link></li></ul>
+</div>
diff --git a/zos.xml b/zos.xml
index 4a67fdd..8bbf986 100644
--- a/zos.xml
+++ b/zos.xml
@@ -1,4 +1,4 @@
-<div class="wiki-content maincontent"><h1 id="zOS-RunningActiveMQonz/OS">Running ActiveMQ on z/OS</h1>
+<div class="wiki-content maincontent"><h1>Running ActiveMQ on z/OS</h1>
<p>It is relatively straightforward to run the ActiveMQ broker on z/OS.</p>
@@ -9,24 +9,23 @@
3. Run using JZOS<br clear="none">
4. Test</p>
-<h3 id="zOS-CopyActiveMQtoz/OS">Copy ActiveMQ to z/OS</h3>
+<h3>Copy ActiveMQ to z/OS</h3>
-<ul><li>Ensure that the 1.5 JVM is available on z/OS, together with the <a shape="rect" class="external-link" href="http://www.dovetail.com/docs/jzos/index.html" rel="nofollow">JZOS</a> component.</li><li>Download the .zip version of ActiveMQ from Apache.</li><li>FTP the broker to a suitable directory in USS.</li><li>Log into USS using rlogin or whatever has been configured at your site to do a login into USS.</li><li>Extract the zip file using the command: jar -xvf apache-activemq-5.0.0.zip</li><li>This will extract the whole package in ASCII, so do not except any of the files to be viewable on z/OS, except using special editors suitable for ASCII.</li><li>Maybe rename the directory to which the files were extracted to something shorter or create a softlink for more convenient access.</li></ul>
+<ul><li>Ensure that the 1.5 JVM is available on z/OS, together with the <a shape="rect" href="http://www.dovetail.com/docs/jzos/index.html">JZOS</a> component.</li><li>Download the .zip version of ActiveMQ from Apache.</li><li>FTP the broker to a suitable directory in USS.</li><li>Log into USS using rlogin or whatever has been configured at your site to do a login into USS.</li><li>Extract the zip file using the command: jar -xvf apache-activemq-5.0.0.zip</li><li>This will extract the whole package in ASCII, so do not except any of the files to be viewable on z/OS, except using special editors suitable for ASCII.</li><li>Maybe rename the directory to which the files were extracted to something shorter or create a softlink for more convenient access.</li></ul>
-<h3 id="zOS-Modifytheconfiguration">Modify the configuration</h3>
+<h3>Modify the configuration</h3>
<p>Currently, the Jetty plugin does not work on z/OS, so need to be disabled in the activemq.xml file.</p>
<ul><li>FTP the activemq.xml file from the conf directory in the ActiveMQ installation to your PC in binary mode.</li><li>Edit the XML file using your XML editor or a text editor like Wordpad.</li><li>Search for "jetty" in the XML.</li><li>Change the comment block so that jetty is completely commented out.</li><li>Save the file.</li><li>FTP the file back into the location on z/OS it came from, again in binary mode, so that it is preserved as an ASCII file.</li></ul>
-<h3 id="zOS-RunusingJZOS">Run using JZOS</h3>
+<h3>Run using JZOS</h3>
<p>I have renamed the lib/optional directory in USS and shortened some of the lib/optional jar names to make the JCL easier to handle. The JCL to run the ActiveMQ broker is then:</p>
-<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>ACTIVEMQ.JCL</b></div><div class="codeContent panelContent pdl">
-<script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[
+<structured-macro ac:macro-id="9ff805fd-64d6-42b8-8c77-40ca683d592b" ac:name="code" ac:schema-version="1"><parameter ac:name="title">ACTIVEMQ.JCL</parameter><parameter ac:name="borderStyle">solid</parameter><plain-text-body>
//ACTIVEMQ JOB (),
// CLASS=A,
// MSGCLASS=X,
@@ -41,9 +40,9 @@
//* Batch job to run Tomcat under JZOS
//*
//* Tailor the proc and job for your installation:
-//* 1.) Modify the Job card per your installation's requirements
+//* 1.) Modify the Job card per your installation's requirements
//* 2.) Modify the PROCLIB card to point to JZOS proclib
-//* 3.) Set VERSION='14' for Java 1.4 or VERSION='50' for Java 5
+//* 3.) Set VERSION='14' for Java 1.4 or VERSION='50' for Java 5
//* 4.) Set JAVA_HOME to point the location of the Java SDK
//* 5.) Set CATALINA_HOME to point to the shared Tomcat install dir
//* 6.) (Optional) set CATALINA_BASE to point to instance specific
@@ -52,9 +51,9 @@
//*********************************************************************
//*
//JAVA EXEC PROC=JVMPRC50,
-// LOGLVL='+D',
-// JAVACLS='org.apache.activemq.console.Main',
-// ARGS='start'
+// LOGLVL='+D',
+// JAVACLS='org.apache.activemq.console.Main',
+// ARGS='start'
//STDENV DD *
# This is a shell script which configures
# any environment variables for the Java JVM.
@@ -62,58 +61,58 @@
. /etc/profile
export JAVA_HOME=/space/javaV5_31/J5.0
AMQ_HOME=/home/user/activemq/amq
-ACTIVEMQ_BASE="$AMQ_HOME"
+ACTIVEMQ_BASE="$AMQ_HOME"
-export PATH=/bin:"${JAVA_HOME}"/bin:
+export PATH=/bin:"${JAVA_HOME}"/bin:
-LIBPATH=/lib:/usr/lib:"${JAVA_HOME}"/bin
-LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic
-export LIBPATH="$LIBPATH":
+LIBPATH=/lib:/usr/lib:"${JAVA_HOME}"/bin
+LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic
+export LIBPATH="$LIBPATH":
-CLASSPATH="${JAVA_HOME}/lib/tools.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/conf"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/activemq-all-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/bin/run.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/bin/wrapper.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activation-1.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-console-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-core-5.0.0-tests.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-core-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-jaas-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-web-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-core-1.2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-jms-1.2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-spring-1.2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/commons-logging-1.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/geronimo-j2ee-management_1.0_spec-1.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/geronimo-jms_1.1_spec-1.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/geronimo-jta_1.0.1B_spec-1.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/jaxb-api-2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/jaxb-impl-2.0.3.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/stax-1.2.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/stax-api-1.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/spring-2.0.6.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/xbean.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jetty-6.1.4.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jetty-util-6.1.4.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activeio-core-3.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/geronimo-j2ee-connector.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activeio-core-tests.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/geronimo-j2ee-jacc.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activemq-optional-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activemq-xmpp-5.0.0.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jmdns-1.0-RC2.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-beanutils-1.6.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/log4j-1.2.14.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-collections-3.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/servlet-api-2.5-6.1.4.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-dbcp-1.2.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-httpclient-2.0.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-pool-1.2.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/xmlpull-1.1.3.4d_b4_min.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/derby-10.1.3.1.jar"
-CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/xstream-1.1.2.jar"
-export CLASSPATH="$CLASSPATH":
+CLASSPATH="${JAVA_HOME}/lib/tools.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/conf"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/activemq-all-5.0.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/bin/run.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/bin/wrapper.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activation-1.1.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-console-5.0.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-core-5.0.0-tests.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-core-5.0.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-jaas-5.0.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/activemq-web-5.0.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-core-1.2.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-jms-1.2.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/camel-spring-1.2.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/commons-logging-1.1.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/geronimo-j2ee-management_1.0_spec-1.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/geronimo-jms_1.1_spec-1.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/geronimo-jta_1.0.1B_spec-1.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/jaxb-api-2.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/jaxb-impl-2.0.3.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/stax-1.2.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/stax-api-1.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/spring-2.0.6.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/xbean.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jetty-6.1.4.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jetty-util-6.1.4.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activeio-core-3.1.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/geronimo-j2ee-connector.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activeio-core-tests.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/geronimo-j2ee-jacc.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activemq-optional-5.0.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/activemq-xmpp-5.0.0.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/jmdns-1.0-RC2.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-beanutils-1.6.1.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/log4j-1.2.14.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-collections-3.1.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/servlet-api-2.5-6.1.4.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-dbcp-1.2.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-httpclient-2.0.1.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/commons-pool-1.2.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/xmlpull-1.1.3.4d_b4_min.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/derby-10.1.3.1.jar"
+CLASSPATH="$CLASSPATH":"$AMQ_HOME/lib/opt/xstream-1.1.2.jar"
+export CLASSPATH="$CLASSPATH":
# Set JZOS specific options
# Use this variable to specify encoding for DD STDOUT and STDERR
@@ -121,41 +120,40 @@
# Use this variable to prevent JZOS from handling MVS operator commands
#export JZOS_ENABLE_MVS_COMMANDS=false
# Use this variable to supply additional arguments to main
-#export JZOS_MAIN_ARGS=""
+#export JZOS_MAIN_ARGS=""
# Configure JVM options
# Note that ActiveMQ requires default ASCII file.encoding
-IJO="-Xms64m -Xmx512m"
-IJO="$IJO -Dfile.encoding=ISO8859-1"
-IJO="$IJO -Dcom.sun.management.jmxremote"
-IJO="$IJO -Dorg.apache.activemq.UseDedicatedTaskRunner=true"
-IJO="$IJO -Dderby.system.home=${ACTIVEMQ_BASE}/data"
-IJO="$IJO -Dderby.storage.fileSyncTransactionLog=true"
-IJO="$IJO -Djavax.net.ssl.keyStorePassword=password"
-IJO="$IJO -Djavax.net.ssl.trustStorePassword=password"
-IJO="$IJO -Djavax.net.ssl.keyStore=${ACTIVEMQ_BASE}/conf/broker.ks"
-IJO="$IJO -Djavax.net.ssl.trustStore=${ACTIVEMQ_BASE}/conf/broker.ts"
-IJO="$IJO -Dactivemq.classpath=${CLASSPATH}"
-IJO="$IJO -Dactivemq.base=${ACTIVEMQ_BASE}"
-IJO="$IJO -Dactivemq.home=${AMQ_HOME}"
-IJO="$IJO -Djava.io.tmpdir=${ACTIVEMQ_BASE}/temp"
+IJO="-Xms64m -Xmx512m"
+IJO="$IJO -Dfile.encoding=ISO8859-1"
+IJO="$IJO -Dcom.sun.management.jmxremote"
+IJO="$IJO -Dorg.apache.activemq.UseDedicatedTaskRunner=true"
+IJO="$IJO -Dderby.system.home=${ACTIVEMQ_BASE}/data"
+IJO="$IJO -Dderby.storage.fileSyncTransactionLog=true"
+IJO="$IJO -Djavax.net.ssl.keyStorePassword=password"
+IJO="$IJO -Djavax.net.ssl.trustStorePassword=password"
+IJO="$IJO -Djavax.net.ssl.keyStore=${ACTIVEMQ_BASE}/conf/broker.ks"
+IJO="$IJO -Djavax.net.ssl.trustStore=${ACTIVEMQ_BASE}/conf/broker.ts"
+IJO="$IJO -Dactivemq.classpath=${CLASSPATH}"
+IJO="$IJO -Dactivemq.base=${ACTIVEMQ_BASE}"
+IJO="$IJO -Dactivemq.home=${AMQ_HOME}"
+IJO="$IJO -Djava.io.tmpdir=${ACTIVEMQ_BASE}/temp"
# Configure SDK5.0 to use shared classes (at group level)
# You must comment this out if you are not running SDK 5
groupname=`id -gn`
-IJO="$IJO -Xshareclasses:name=$groupname,groupAccess"
-export IBM_JAVA_OPTIONS="$IJO "
+IJO="$IJO -Xshareclasses:name=$groupname,groupAccess"
+export IBM_JAVA_OPTIONS="$IJO "
export JAVA_DUMP_HEAP=false
export JAVA_PROPAGATE=NO
export IBM_JAVA_ZOS_TDUMP=NO
//
-]]></script>
-</div></div>
+</plain-text-body></structured-macro>
-<h3 id="zOS-Test">Test</h3>
+<h3>Test</h3>
<p>Once the broker has been started on z/OS, modify one of the example application to have the hostname of the z/OS system and run it to confirm that the broker is functioning correctly.</p>
-<p>You can also gather information about the broker as usual using <a shape="rect" href="jmx.xml">jmx</a>.</p></div>
+<p>You can also gather information about the broker as usual using <link><page ri:content-title="jmx"></page></link>.</p></div>
